Forum Discussion
Adding domain to Office 365 caused outlook to point to office 365 instead of on-premises exchange
thank you very much. This is exactly what is happening. I will try the solution, but changing the registry record could be time consuming with staff at several places. Any ideas to auto deploy it?
thank you.
If you want to remove the licenses, it depends how your infrastructure is built, do you already have Azure AD Connect established?
If yes, I would create a new Security Group like "M365 Business" and apply it to all affected users. Then in M365 admin console, remove every license assignment to you users. Instead use this newly created AD group and assign the M365 license to the group, there you can remove Exchange Online plan for the whole group at once. After this is processed, all users have this predefined set of licenses.
If you have no AAD sync in place, you can either start with this, but then you might face other issues during initial sync as the local AD users might not map with the already existing cloud users and result in a mess - we had assistance from a certified partner for this step. Then it might be the fastest to to click though every user and remove the Exchange Online plan manually..
- atirhiSep 17, 2020Copper Contributor
thank you. we don't have AAD. Will do a manual test. Last question: Will updating office applications in the future reset the registry record again?
thanks again
- burningiceSep 17, 2020Brass Contributor
atirhi as far as I know, this reg setting is not overwritten if Office updates.
also, if you once get a proper Exchange Hybrid Environment with Azure Ad Sync and stuff, you don't have to remove the setting . If there is only one distinct Cloud mailbox per user, Outlook will happily use it- atirhiSep 17, 2020Copper Contributor
- PeterRisingSep 17, 2020MVP
Well I have learned something here I must admit. I had no idea about this quirk. Thank you for sharing this knowledge!
- burningiceSep 17, 2020Brass Contributor
PeterRising you're welcome 🙂
When I read this post, I had flashbacks to our own environment when the phone started ringing just after verifying the domain...
If your tenant starts from scratch and you have no already existing users in Azure AD, you will not notice anything. It only becomes tricky if a user also has a separate cloud identity with a separate mailbox