As of the recent Windows 10 1511 update Office 365 Pro Plus 2016 no longer activates, in fact when you try to activate it you end up with a cryptic Http Bad Request error after logging in. These few fixes can help get your users back up and running like it did for us.
During a recent Microsoft Office 365 migration, Now Micro’s Cloud Sherpa, Micah Linehan, encountered a tenancy migration where he had to work through reinstalling Exchange on premise. In this particular case, a vase majority of users had previously been created without Exchange. As Micah moved forward and installed Exchanges, the users were directory synchronized; however, a remote user in Exchange was not. He put together the following recommendations and best practices for working through these issues, as he found there were few technical resources (articles, blogs, etc.) out there. Hopefully this post will alleviate some of the confusion and ease any off boarding or tenancy conversion issues within Office 365.
Now Micro’s Micah Linehan identifies common issues with identities in an ADFS environment and provides insight on how ADFS and directory synchronization actually work.
User Creations and Troubleshooting
User management after deploying ADFS can be more confusing to the direct staff and those who support it. For example,
- Are the addresses stuck as .onmicrosoft.com and not switching?
- Are staff unable to add in alternate email addresses?
- What about directory synchronization errors?
It is amazing how simple process and workflow user account provisioning can remediate most of those issues. Here are a few things that can ease a lot of issues with user identities: