SOLVED

Migrate from Skype for Business Hybrid to Skype for Business online

%3CLINGO-SUB%20id%3D%22lingo-sub-77183%22%20slang%3D%22en-US%22%3EMigrate%20from%20Skype%20for%20Business%20Hybrid%20to%20Skype%20for%20Business%20online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-77183%22%20slang%3D%22en-US%22%3E%3CP%3EHas%20anyone%20attempted%20this%20and%20what%20was%20your%20experience%3F%26nbsp%3B%20We%20are%20currently%20in%20the%20process%20of%20moving%20all%20of%20our%20users%20from%20on-premises%20to%20the%20cloud.%26nbsp%3B%20I%20found%20a%20great%20article%20that%20goes%20through%20some%20steps%20modify%20DNS%20to%20support%20online%20only%20connnectivity.%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fblogs.technet.microsoft.com%2Fpraj%2F2016%2F03%2F25%2Fmigration-of-skype-for-business-hybrid-environment-to-skype-for-business-online%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fblogs.technet.microsoft.com%2Fpraj%2F2016%2F03%2F25%2Fmigration-of-skype-for-business-hybrid-environment-to-skype-for-business-online%2F%3C%2FA%3E%3C%2FP%3E%3CP%3EThe%20article%20doesn't%20go%20into%20detail%20about%20managing%20accounts%20or%20removing%20all%20of%20the%20on-premises%20servers.%26nbsp%3B%20Our%20goal%20is%20to%20completely%20remove%20our%20on-premises%20servers.%26nbsp%3B%20However%2C%20I'm%20not%20sure%20if%20this%20is%20possible%20if%20we%20sync%20our%20on-premises%20AD%20accounts%20to%20Azure%20AD.%26nbsp%3B%20We%20don't%20create%20accounts%20in%20Office%20365%2C%20so%20to%20enable%20new%20accounts%2C%20we%20might%20still%20have%20to%20keep%20the%20on-premises%20environment%20in%20place%2C%20at%20least%20one%20pool%20to%20move%20users%20from%20onprem%20to%20the%20cloud.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-77183%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EDeployment%20%26amp%3B%20Operations%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EFederation%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-100691%22%20slang%3D%22en-US%22%3ERe%3A%20Migrate%20from%20Skype%20for%20Business%20Hybrid%20to%20Skype%20for%20Business%20online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-100691%22%20slang%3D%22en-US%22%3EYep%20you%20are%20good%20to%20run%20those%20assuming%20you%20have%20first%20decommissioned%20all%20the%20on%20premise%20servers%20-%20see%20%3CA%20href%3D%22https%3A%2F%2Fblog.adexis.com.au%2F2016%2F10%2F25%2Fdecommissioning-skype-for-business-2015-on-premise-after-migrating-to-o365%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fblog.adexis.com.au%2F2016%2F10%2F25%2Fdecommissioning-skype-for-business-2015-on-premise-after-migrating-to-o365%2F%3C%2FA%3E%20for%20detailed%20steps.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-100625%22%20slang%3D%22en-US%22%3ERe%3A%20Migrate%20from%20Skype%20for%20Business%20Hybrid%20to%20Skype%20for%20Business%20online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-100625%22%20slang%3D%22en-US%22%3E%3CP%3EAwesome!%26nbsp%3B%20Thanks%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F33823%22%20target%3D%22_blank%22%3E%40Josh%20Blalock%3C%2FA%3E!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-100624%22%20slang%3D%22en-US%22%3ERe%3A%20Migrate%20from%20Skype%20for%20Business%20Hybrid%20to%20Skype%20for%20Business%20online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-100624%22%20slang%3D%22en-US%22%3E%3CP%3EYeah%2C%20I've%20used%20both%20commands%20recently%20in%20an%20org%20that%20moved%20all%20users%20to%20Skype%20for%20Business%20Online.%20They%20go%20through%20and%20clean%20things%20up%20nicely%2C%20and%20I%20don't%20believe%20it%20should%20impact%20S4BO%20in%20a%20negative%20way.%20It%20definitely%20hasn't%20in%20the%20environment%20that%20I%20have%20used%20them%20in%20last%20week.%20It%20cleaned%20up%20all%20the%20groups%2C%20ACLs%2C%20etc.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-100620%22%20slang%3D%22en-US%22%3ERe%3A%20Migrate%20from%20Skype%20for%20Business%20Hybrid%20to%20Skype%20for%20Business%20online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-100620%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20writing%20up%20the%20procedure%20to%20completely%20remove%20Skype%20for%20Business%20from%20our%20on-premises%20infrastructure.%3CBR%20%2F%3EAfter%20removing%20the%20Edge%20and%20Front%20End%20pools%2C%20effectively%20fully%20removing%20the%20deployment%20from%20the%20topology%2C%20I'm%20wondering%20if%20it's%20safe%20to%20remove%20the%20changes%20to%20the%20AD%20schema%3F%26nbsp%3B%20I%20don't%20believe%20Skype%20for%20Business%20online%20uses%20the%20SfB%20AD%20attributes.%3CBR%20%2F%3E%3CBR%20%2F%3ECommands%20I'm%20interested%20in%20using%3A%3CBR%20%2F%3E%3CBR%20%2F%3EDisable-CsAdDomain%3CBR%20%2F%3EDisable-CsAdForest%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHas%20anyone%20used%20these%20commands%20to%20undo%20the%20domain%2Fforest%20preparation%20tasks%20put%20in%20place%20by%20Skype%20for%20Business%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-100577%22%20slang%3D%22en-US%22%3ERe%3A%20Migrate%20from%20Skype%20for%20Business%20Hybrid%20to%20Skype%20for%20Business%20online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-100577%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F54310%22%20target%3D%22_blank%22%3E%40Jason%20Wynn%3C%2FA%3E%26nbsp%3BYep%20%3A)%3C%2Fimg%3E%20%26nbsp%3BI'm%20way%20too%20impatient%20for%20that%2C%20that's%20when%20time%20slows%20down%20for%20me...%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-100063%22%20slang%3D%22en-US%22%3ERe%3A%20Migrate%20from%20Skype%20for%20Business%20Hybrid%20to%20Skype%20for%20Business%20online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-100063%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F7965%22%20target%3D%22_blank%22%3E%40Anthony%20Caragol%3C%2FA%3E%26nbsp%3B-%20I've%20had%20it%20take%20an%20hour%20or%20more%20per%20user%20depending%20on%20the%20size%20of%20the%20organisation%20before%20it%20shows%20up%20on%20SfBO%20Admin%20portal.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-99880%22%20slang%3D%22en-US%22%3ERe%3A%20Migrate%20from%20Skype%20for%20Business%20Hybrid%20to%20Skype%20for%20Business%20online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-99880%22%20slang%3D%22en-US%22%3E%3CP%3EI've%20only%20just%20seen%20this%20thread%2C%20but%20had%20this%20every%20time%20I've%20performed%20a%20migration%20to%20SFBO%20from%20on-prem%20that's%20been%20in%20hybrid%20at%20any%20point.%20In%20a%20none%20hybrid%20scenario%20(pure%20on-prem)%2C%20when%20you%20disable%20a%20user%20for%20Skype%20for%20Business%2C%20all%20the%20Skype%20related%20user%20attributes%20are%20cleared%20out%20from%20the%20user%20object%20and%20you%20wont%20have%20any%20problem%20enabling%20them%20online%20and%20having%20them%20appearing%20in%20the%20online%20control%20panel.%20However%20if%20the%20environment%20has%20been%20in%20a%20hybrid%20at%20any%20point%20and%20you%20disable%20a%20user%2C%20all%20the%20attributes%20are%20cleared%20out%20with%20the%20exception%20of%20the%20DeploymentLocator%20which%20stays%20populated%20with%20an%20SRV%20value.%20Taht%20value%20is%20sync'd%20to%20the%20cloud%20as%20part%20of%20your%20account%20sync%20process%2C%20and%20when%20you%20assign%20a%20license%20the%20Skype%20provisioning%20process%20hits%20a%20brick%20wall%20because%20a%20required%20attribute%20is%20already%20populated.%20As%20you%20mentioned%2C%20clearing%20the%20attribute%20and%20then%20allowing%20for%20a%20sync%20cycle%20will%20fix%20the%20problem.%20From%20experience%2C%20I've%20noted%20there's%20no%20need%20to%20remove%20and%20re-assign%20licenses%20etc.%20The%20accounts%20will%20simply%20drop%20in%2010-15%20minutes%20after%20the%20sync%20of%20the%20null%20Deployment%20Locator%20attribute.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAppreciate%20you've%20already%20made%20people%20aware%20of%20the%20fix%2C%20but%20in%20addition%20this%20isn't%20a%20querk%20unique%20to%20yourself%20or%20the%20way%20you%20went%20about%20doing%20anything%20-%20it%20will%20happen%20100%25%20of%20the%20time%20for%20any%20hybrid%20migration.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EKind%20regards%3CBR%20%2F%3EBen%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-99718%22%20slang%3D%22en-US%22%3ERe%3A%20Migrate%20from%20Skype%20for%20Business%20Hybrid%20to%20Skype%20for%20Business%20online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-99718%22%20slang%3D%22en-US%22%3E%3CP%3EI%20opened%20a%20case%20with%20Microsoft%20and%20they%20helped%20me%20identify%20and%20correct%20the%20issue.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3COL%3E%3CLI%3ESince%20we%20no%20longer%20enable%20users%20in%20the%20Skype%20for%20Business%20onpremises%2C%20we%20stil%20need%20to%20create%20a%20SIP%20address%20value%20under%20the%20proxyAddresses%20attribute%20of%20new%20accounts%20before%20they%20are%20synced%20to%20Azure.%3C%2FLI%3E%3CLI%3EEnsure%20the%20msRTCSIP-%20attributes%20are%20all%20configured%20to%20%3CNOT%20set%3D%22%22%3E.%26nbsp%3B%20I%20think%20one%20attribute%26nbsp%3BmsRTCSIP-DeploymentLocator%20had%20a%20value%20of%20%22SRV%3A%22%20and%20had%20to%20be%20changed%20to%20%3CNOT%20set%3D%22%22%3E.%3C%2FNOT%3E%3C%2FNOT%3E%3C%2FLI%3E%3C%2FOL%3E%3CP%3EI%20hope%20this%20helps%20anyone%20else%20moving%20from%20onpremises%20to%20fully%20in%20the%20cloud.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-98445%22%20slang%3D%22en-US%22%3ERe%3A%20Migrate%20from%20Skype%20for%20Business%20Hybrid%20to%20Skype%20for%20Business%20online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-98445%22%20slang%3D%22en-US%22%3ENo%2C%20It%20didn't%20work.%20I'm%20opening%20a%20ticket%20with%20Microsoft.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-98386%22%20slang%3D%22en-US%22%3ERe%3A%20Migrate%20from%20Skype%20for%20Business%20Hybrid%20to%20Skype%20for%20Business%20online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-98386%22%20slang%3D%22en-US%22%3E%3CP%3EIt%20can%20take%20a%20few%20minutes%20before%20it%20shows%20up%20in%20the%20SfBO%20admin%20center%20after%20licensing%2C%20give%20it%20an%20hour%20or%20so.%20%26nbsp%3BIf%20they're%20still%20not%20there%2C%20unlicense%20and%20re-license%2C%20if%20still%20not%20there%2C%20you%20may%20need%20to%20contact%20support.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-98378%22%20slang%3D%22en-US%22%3ERE%3A%20Migrate%20from%20Skype%20for%20Business%20Hybrid%20to%20Skype%20for%20Business%20online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-98378%22%20slang%3D%22en-US%22%3E%3CP%3EPS%20D%3A%5C%26gt%3B%20Get-CsAccessEdgeConfiguration%3CBR%20%2F%3EIdentity%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20%3A%20Global%3CBR%20%2F%3EAllowAnonymousUsers%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20%3A%20True%3CBR%20%2F%3EAllowFederatedUsers%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20%3A%20False%3CBR%20%2F%3EAllowOutsideUsers%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20%3A%20False%3CBR%20%2F%3EBeClearingHouse%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20%3A%20False%3CBR%20%2F%3EEnablePartnerDiscovery%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20%3A%20False%3CBR%20%2F%3EDiscoveredPartnerVerificationLevel%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20%3A%20UseSourceVerification%3CBR%20%2F%3EEnableArchivingDisclaimer%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20%3A%20False%3CBR%20%2F%3EEnableUserReplicator%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20%3A%20False%3CBR%20%2F%3EKeepCrlsUpToDateForPeers%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20%3A%20True%3CBR%20%2F%3EMarkSourceVerifiableOnOutgoingMessages%20%3A%20True%3CBR%20%2F%3EOutgoingTlsCountForFederatedPartners%26nbsp%3B%26nbsp%3B%20%3A%204%3CBR%20%2F%3EDnsSrvCacheRecordCount%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20%3A%20131072%3CBR%20%2F%3EDiscoveredPartnerStandardRate%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20%3A%2020%3CBR%20%2F%3EEnableDiscoveredPartnerContactsLimit%26nbsp%3B%26nbsp%3B%20%3A%20True%3CBR%20%2F%3EMaxContactsPerDiscoveredPartner%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20%3A%201000%3CBR%20%2F%3EDiscoveredPartnerReportPeriodMinutes%26nbsp%3B%26nbsp%3B%20%3A%2060%3CBR%20%2F%3EMaxAcceptedCertificatesStored%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20%3A%201000%3CBR%20%2F%3EMaxRejectedCertificatesStored%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20%3A%20500%3CBR%20%2F%3ECertificatesDeletedPercentage%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20%3A%2020%3CBR%20%2F%3ESkypeSearchUrl%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20%3A%20%3CA%20href%3D%22https%3A%2F%2Fskypegraph.skype.com%2Fsearch%2Fv1.0%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fskypegraph.skype.com%2Fsearch%2Fv1.0%3C%2FA%3E%3CBR%20%2F%3ERoutingMethod%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20%3A%20UseDnsSrvRouting%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3EPS%20D%3A%5C%26gt%3B%20Get-CsHostingProvider%3CBR%20%2F%3EIdentity%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20%3A%20Exchange%20Online%3CBR%20%2F%3EName%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20%3A%20Exchange%20Online%3CBR%20%2F%3EProxyFqdn%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20%3A%20exap.um.outlook.com%3CBR%20%2F%3EVerificationLevel%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20%3A%20UseSourceVerification%3CBR%20%2F%3EEnabled%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20%3A%20False%3CBR%20%2F%3EEnabledSharedAddressSpace%20%3A%20True%3CBR%20%2F%3EHostsOCSUsers%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20%3A%20False%3CBR%20%2F%3EIsLocal%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20%3A%20False%3CBR%20%2F%3EAutodiscoverUrl%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20%3A%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-98372%22%20slang%3D%22en-US%22%3ERe%3A%20Migrate%20from%20Skype%20for%20Business%20Hybrid%20to%20Skype%20for%20Business%20online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-98372%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20made%20our%20DNS%20changes%20last%20weekend%20and%20I've%20turned%20off%20Hybrid%20connectivity.%26nbsp%3B%20However%2C%20when%20we%20sync%20users%20from%20onprem%20AD%20to%20Azure%20and%20assign%20a%20Skype%20for%20Business%20plan%202%20license%2C%20they%20are%20not%20displayed%20in%20the%20Skype%20for%20Business%20Admin%20Center.%26nbsp%3B%20Does%20anyone%20know%20why%20this%20is%20not%20working%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-83305%22%20slang%3D%22en-US%22%3ERe%3A%20Migrate%20from%20Skype%20for%20Business%20Hybrid%20to%20Skype%20for%20Business%20online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-83305%22%20slang%3D%22en-US%22%3E%3CP%3EAh%20yes%2C%20that%20makes%20sense%2C%20I%20got%20ya!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWell%2C%20best%20of%20luck%20as%20you%20move%20forward%2C%20and%20look%20forward%20to%20bumping%20into%20within%20the%20Tech%20Community%20later%20on!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EJosh%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-83301%22%20slang%3D%22en-US%22%3ERe%3A%20Migrate%20from%20Skype%20for%20Business%20Hybrid%20to%20Skype%20for%20Business%20online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-83301%22%20slang%3D%22en-US%22%3E%3CP%3EJosh%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThat's%20correct%20and%20exactly%20what%20I%20mean.%26nbsp%3B%20However%2C%20Microsoft%20just%20assumes%20that%20you%20know%20to%20do%20this.%26nbsp%3B%20I'm%20not%20saying%20they%20are%20wrong%20and%20it%20all%20makes%20sense%20to%20me%2C%20but%20they%20should%20document%20it%20just%20like%20everything%20else%20on%20Technet.%3C%2FP%3E%3CP%3EThanks%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EEarl%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-83299%22%20slang%3D%22en-US%22%3ERe%3A%20Migrate%20from%20Skype%20for%20Business%20Hybrid%20to%20Skype%20for%20Business%20online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-83299%22%20slang%3D%22en-US%22%3E%3CP%3EEarl%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhen%20you%20say%20remove%20Hybrid%20mode%20and%20go%20to%20Cloud%20only%2C%20are%20you%20referring%20to%20Skype%20for%20Business%20Hybrid%2C%20or%20are%20you%20talking%20about%20even%20disconnecting%20Azure%20AD%3F%20For%20removing%20Hybrid%20from%20a%20Skype%20for%20Business%20Online%20tenant%2C%20you%20would%20simply%20change%20the%20required%20DNS%20over%20to%20point%20at%20Skype%20for%20Business%20Online%2C%20and%20then%20remove%20the%20configuration%20that%20was%20set%20via%20PowerShell%20to%20setup%20the%20%22SharedSipAddressSpace%22%20in%20SFBO.%20At%20that%20point%2C%20your%20Skype%20for%20Business%20Online%20environment%20is%20completely%20standing%20on%20its%20own%20(and%20on-prem%20servers%20can%20be%20decommissioned)%2C%20but%20your%20user%20accounts%20themselves%20will%20still%20show%20%22Synced%22%2C%20as%20they%20are%20created%20in%20your%20on-prem%20AD%20and%20synced%20to%20the%20Cloud%20using%20Azure%20AD%20Connect.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESorry%20if%20I%20seem%20to%20be%20rambling%2C%20I%20just%20wanted%20to%20make%20sure%20it%20was%20all%20cleared%20up%20on%20your%20end.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EJosh%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-82849%22%20slang%3D%22en-US%22%3ERe%3A%20Migrate%20from%20Skype%20for%20Business%20Hybrid%20to%20Skype%20for%20Business%20online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-82849%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Josh%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20for%20the%20clarification.%26nbsp%3B%20My%20confusion%20was%20that%20we%20sync%20users%20to%20Office%20365%20today%20via%20Azure%20AD%20and%20assign%20licenses%2C%20however%2C%20they%20are%20not%20%22%20in%20cloud%22%20because%20we're%20in%20Hybrid%20mode.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20would%20like%20to%20see%20Microsoft%20include%20documentation%20on%20their%20site%20to%20remove%20Hybrid%20mode%20and%20go%20to%20cloud%20only.%26nbsp%3B%20I%20hope%20this%20helps%20someone%20else%20that%20goes%20throught%20the%20sames%20steps%20as%20me.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EEarl%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-82665%22%20slang%3D%22en-US%22%3ERe%3A%20Migrate%20from%20Skype%20for%20Business%20Hybrid%20to%20Skype%20for%20Business%20online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-82665%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20Earl!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ELooking%20to%20the%20future%20when%20you%20no%20longer%20have%20an%20on-prem%20infrastructure%20for%20Skype%20for%20Business%2C%20your%20users%20will%20still%20be%20synced%20to%20Office%20365%20via%20Azure%20AD%20Connect%2C%20as%20Dino%20pointed%20out.%20At%20this%20point%2C%20however%2C%20all%20you%20have%20to%20do%20to%20enable%20a%20user%20for%20Skype%20for%20Business%20is%20assign%20them%20the%20appropriate%20license.%20For%20instance%2C%20if%20you%20assign%20an%20E5%20license%2C%20and%20Skype%20for%20Business%20is%20toggled%20On%20within%20the%20E5%20drop-down%2C%20then%20that%20user%20is%20now%20enabled%20for%20SKype%20for%20Business%20Online.%20You%20will%20then%20be%20able%20to%20manage%20their%20Skype%20for%20Business%20settings%20within%20the%20Skype%20for%20Business%20Admin%20Center.%20There%20is%20no%20where%20within%20the%20Skype%20for%20Business%20Admin%20Center%2C%20however%2C%20to%20%22Enable%22%20a%20user%20for%20Skype%20for%20Business%3B%20that%20is%20all%20done%20via%20licensing%20once%20you%20are%20in%20a%20pure%20Skype%20for%20Business%20Online%20environment.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHope%20that%20helps%20to%20clarify!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERespectfully%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EJosh%20Blalock%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-82187%22%20slang%3D%22en-US%22%3ERe%3A%20Migrate%20from%20Skype%20for%20Business%20Hybrid%20to%20Skype%20for%20Business%20online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-82187%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20for%20the%20response.%26nbsp%3B%20I%20don't%20see%20the%20option%20to%20Enable%20users%20in%20the%20Skype%20for%20Business%20Admins%20center.%26nbsp%3B%20Is%20this%20somehow%20turned%20on%20after%20Hybrid%20mode%20is%20removed%3F%26nbsp%3B%20Furthermore%2C%20are%20there%20Powershell%20commands%20to%20enable%20a%20user%20in%20Skype%20for%20Business%20online%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20found%20a%20link%20somewhere%20that%20states%20when%20provisioning%20an%20Office%20365%20user%2C%20after%20creating%20the%20account%20and%20assigning%20a%20license%2C%20the%20user%20is%20enabled%20%22in%20cloud%22.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-78117%22%20slang%3D%22en-US%22%3ERe%3A%20Migrate%20from%20Skype%20for%20Business%20Hybrid%20to%20Skype%20for%20Business%20online%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-78117%22%20slang%3D%22en-US%22%3E%3CP%3EYes%20certainly%20possible%20to%20complete%20your%20migration%20and%20after%20the%20last%20user%20has%20been%20moved%20to%20Skype4B%20Online%20you%20can%20begin%20the%20process%20to%20transistion%20DNS%20to%20be%20a%20cloud%20only%20Skype4B%20deployment.%26nbsp%3B%20This%20esstientially%20is%20repointing%20specific%20records%20to%20Skype4B%20online%20servers%20vs%20your%20on-prem%20infrastructure.%26nbsp%3B%20Once%20this%20is%20done%20and%20you%20are%20confident%20there%20are%20no%20dependencies%20on-prem%20from%20a%20Skype%20perspective%20you%20can%20decommission%20all%20the%20Skype4B%20Servers.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFrom%20an%20accounts%20perspective%2C%20and%20ongoing%20user%20management%20you%20will%20still%20need%20your%20DirSync%2FADConnect%20server%20to%20synchronize%20accounts%20to%20the%20cloud%20from%20your%20on-prem%20AD.%26nbsp%3B%20If%20using%20SSO%20you%20will%20also%20still%20continue%20to%20your%20on-prem%20ADFS%20infrastructure%20as%20well.%26nbsp%3B%20User%20management%20from%20a%20Skype%20perspective%20will%20now%20be%20handled%20entirely%20in%20the%20cloud%20using%20the%20Skype%20for%20Business%20Online%20Admin%20Center.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Contributor

Has anyone attempted this and what was your experience?  We are currently in the process of moving all of our users from on-premises to the cloud.  I found a great article that goes through some steps modify DNS to support online only connnectivity.

https://blogs.technet.microsoft.com/praj/2016/03/25/migration-of-skype-for-business-hybrid-environme...

The article doesn't go into detail about managing accounts or removing all of the on-premises servers.  Our goal is to completely remove our on-premises servers.  However, I'm not sure if this is possible if we sync our on-premises AD accounts to Azure AD.  We don't create accounts in Office 365, so to enable new accounts, we might still have to keep the on-premises environment in place, at least one pool to move users from onprem to the cloud.

19 Replies

Yes certainly possible to complete your migration and after the last user has been moved to Skype4B Online you can begin the process to transistion DNS to be a cloud only Skype4B deployment.  This esstientially is repointing specific records to Skype4B online servers vs your on-prem infrastructure.  Once this is done and you are confident there are no dependencies on-prem from a Skype perspective you can decommission all the Skype4B Servers. 

 

From an accounts perspective, and ongoing user management you will still need your DirSync/ADConnect server to synchronize accounts to the cloud from your on-prem AD.  If using SSO you will also still continue to your on-prem ADFS infrastructure as well.  User management from a Skype perspective will now be handled entirely in the cloud using the Skype for Business Online Admin Center. 

Thanks for the response.  I don't see the option to Enable users in the Skype for Business Admins center.  Is this somehow turned on after Hybrid mode is removed?  Furthermore, are there Powershell commands to enable a user in Skype for Business online?

 

I found a link somewhere that states when provisioning an Office 365 user, after creating the account and assigning a license, the user is enabled "in cloud".

Hello Earl!

 

Looking to the future when you no longer have an on-prem infrastructure for Skype for Business, your users will still be synced to Office 365 via Azure AD Connect, as Dino pointed out. At this point, however, all you have to do to enable a user for Skype for Business is assign them the appropriate license. For instance, if you assign an E5 license, and Skype for Business is toggled On within the E5 drop-down, then that user is now enabled for SKype for Business Online. You will then be able to manage their Skype for Business settings within the Skype for Business Admin Center. There is no where within the Skype for Business Admin Center, however, to "Enable" a user for Skype for Business; that is all done via licensing once you are in a pure Skype for Business Online environment.

 

Hope that helps to clarify!

 

Respectfully,

 

Josh Blalock

Hi Josh,

 

Thanks for the clarification.  My confusion was that we sync users to Office 365 today via Azure AD and assign licenses, however, they are not " in cloud" because we're in Hybrid mode. 

 

I would like to see Microsoft include documentation on their site to remove Hybrid mode and go to cloud only.  I hope this helps someone else that goes throught the sames steps as me.

 

Earl

Best Response confirmed by Earl Zirkle (Contributor)
Solution

Earl,

 

When you say remove Hybrid mode and go to Cloud only, are you referring to Skype for Business Hybrid, or are you talking about even disconnecting Azure AD? For removing Hybrid from a Skype for Business Online tenant, you would simply change the required DNS over to point at Skype for Business Online, and then remove the configuration that was set via PowerShell to setup the "SharedSipAddressSpace" in SFBO. At that point, your Skype for Business Online environment is completely standing on its own (and on-prem servers can be decommissioned), but your user accounts themselves will still show "Synced", as they are created in your on-prem AD and synced to the Cloud using Azure AD Connect.

 

Sorry if I seem to be rambling, I just wanted to make sure it was all cleared up on your end.

 

Josh

Josh,

 

That's correct and exactly what I mean.  However, Microsoft just assumes that you know to do this.  I'm not saying they are wrong and it all makes sense to me, but they should document it just like everything else on Technet.

Thanks,

 

Earl

Ah yes, that makes sense, I got ya!

 

Well, best of luck as you move forward, and look forward to bumping into within the Tech Community later on!

 

Josh

We made our DNS changes last weekend and I've turned off Hybrid connectivity.  However, when we sync users from onprem AD to Azure and assign a Skype for Business plan 2 license, they are not displayed in the Skype for Business Admin Center.  Does anyone know why this is not working?

PS D:\> Get-CsAccessEdgeConfiguration
Identity                               : Global
AllowAnonymousUsers                    : True
AllowFederatedUsers                    : False
AllowOutsideUsers                      : False
BeClearingHouse                        : False
EnablePartnerDiscovery                 : False
DiscoveredPartnerVerificationLevel     : UseSourceVerification
EnableArchivingDisclaimer              : False
EnableUserReplicator                   : False
KeepCrlsUpToDateForPeers               : True
MarkSourceVerifiableOnOutgoingMessages : True
OutgoingTlsCountForFederatedPartners   : 4
DnsSrvCacheRecordCount                 : 131072
DiscoveredPartnerStandardRate          : 20
EnableDiscoveredPartnerContactsLimit   : True
MaxContactsPerDiscoveredPartner        : 1000
DiscoveredPartnerReportPeriodMinutes   : 60
MaxAcceptedCertificatesStored          : 1000
MaxRejectedCertificatesStored          : 500
CertificatesDeletedPercentage          : 20
SkypeSearchUrl                         : https://skypegraph.skype.com/search/v1.0
RoutingMethod                          : UseDnsSrvRouting



PS D:\> Get-CsHostingProvider
Identity                  : Exchange Online
Name                      : Exchange Online
ProxyFqdn                 : exap.um.outlook.com
VerificationLevel         : UseSourceVerification
Enabled                   : False
EnabledSharedAddressSpace : True
HostsOCSUsers             : False
IsLocal                   : False
AutodiscoverUrl           :

It can take a few minutes before it shows up in the SfBO admin center after licensing, give it an hour or so.  If they're still not there, unlicense and re-license, if still not there, you may need to contact support.

No, It didn't work. I'm opening a ticket with Microsoft.

I opened a case with Microsoft and they helped me identify and correct the issue.

 

  1. Since we no longer enable users in the Skype for Business onpremises, we stil need to create a SIP address value under the proxyAddresses attribute of new accounts before they are synced to Azure.
  2. Ensure the msRTCSIP- attributes are all configured to <not set>.  I think one attribute msRTCSIP-DeploymentLocator had a value of "SRV:" and had to be changed to <not set>.

I hope this helps anyone else moving from onpremises to fully in the cloud.

I've only just seen this thread, but had this every time I've performed a migration to SFBO from on-prem that's been in hybrid at any point. In a none hybrid scenario (pure on-prem), when you disable a user for Skype for Business, all the Skype related user attributes are cleared out from the user object and you wont have any problem enabling them online and having them appearing in the online control panel. However if the environment has been in a hybrid at any point and you disable a user, all the attributes are cleared out with the exception of the DeploymentLocator which stays populated with an SRV value. Taht value is sync'd to the cloud as part of your account sync process, and when you assign a license the Skype provisioning process hits a brick wall because a required attribute is already populated. As you mentioned, clearing the attribute and then allowing for a sync cycle will fix the problem. From experience, I've noted there's no need to remove and re-assign licenses etc. The accounts will simply drop in 10-15 minutes after the sync of the null Deployment Locator attribute.

 

Appreciate you've already made people aware of the fix, but in addition this isn't a querk unique to yourself or the way you went about doing anything - it will happen 100% of the time for any hybrid migration.

 

Kind regards
Ben

@Anthony Caragol - I've had it take an hour or more per user depending on the size of the organisation before it shows up on SfBO Admin portal.

@Jason Wynn Yep :)  I'm way too impatient for that, that's when time slows down for me...

I'm writing up the procedure to completely remove Skype for Business from our on-premises infrastructure.
After removing the Edge and Front End pools, effectively fully removing the deployment from the topology, I'm wondering if it's safe to remove the changes to the AD schema?  I don't believe Skype for Business online uses the SfB AD attributes.

Commands I'm interested in using:

Disable-CsAdDomain
Disable-CsAdForest

 

Has anyone used these commands to undo the domain/forest preparation tasks put in place by Skype for Business?

Yeah, I've used both commands recently in an org that moved all users to Skype for Business Online. They go through and clean things up nicely, and I don't believe it should impact S4BO in a negative way. It definitely hasn't in the environment that I have used them in last week. It cleaned up all the groups, ACLs, etc.

Yep you are good to run those assuming you have first decommissioned all the on premise servers - see https://blog.adexis.com.au/2016/10/25/decommissioning-skype-for-business-2015-on-premise-after-migra... for detailed steps.