Migrate from Skype for Business Hybrid to Skype for Business online

Awesome!  Thanks Josh Blalock!

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.

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?

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

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.

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

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.

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.