Forum Discussion
Solved
On-Prem sync to cloud native
So we’ve started a process to move users from a hybrid model to fully cloud in readiness to retire the local environment.
Just in testing we can move a user to an unsynced OU, and then restore in cloud.
To this point we’re all good.
Here’s the weird bit. So regardless of the fact that the user is in cloud and can logon, MFA is working etc, Outlook (as an example) is prompting for the legacy domain\username verses authenticating with email address as you’d expect.
What are we missing?
Just in testing we can move a user to an unsynced OU, and then restore in cloud.
To this point we’re all good.
Here’s the weird bit. So regardless of the fact that the user is in cloud and can logon, MFA is working etc, Outlook (as an example) is prompting for the legacy domain\username verses authenticating with email address as you’d expect.
What are we missing?
- I can think of 2 things. Modern Authentication became default from Outlook 2016 so if you have Outlook 2013 you might need to create a registry object to enable Modern Authentication. https://docs.microsoft.com/en-us/office365/enterprise/modern-auth-for-office-2013-and-2016
Also, can you double check in your tenant if it is enabled? Get-OrganizationConfig | Format-Table Name,OAuth* -Auto (see here for more information https://docs.microsoft.com/en-us/Exchange/clients-and-mobile-in-exchange-online/enable-or-disable-modern-authentication-in-exchange-online?redirectSourcePath=%252farticle%252f58018196-f918-49cd-8238-56f57f38d662
Let us know if you managed to fix it :)
4 Replies
- If it ends up cropping up again, I would check auto discover and make sure you swung that to 365 as well.
- I can think of 2 things. Modern Authentication became default from Outlook 2016 so if you have Outlook 2013 you might need to create a registry object to enable Modern Authentication. https://docs.microsoft.com/en-us/office365/enterprise/modern-auth-for-office-2013-and-2016
Also, can you double check in your tenant if it is enabled? Get-OrganizationConfig | Format-Table Name,OAuth* -Auto (see here for more information https://docs.microsoft.com/en-us/Exchange/clients-and-mobile-in-exchange-online/enable-or-disable-modern-authentication-in-exchange-online?redirectSourcePath=%252farticle%252f58018196-f918-49cd-8238-56f57f38d662
Let us know if you managed to fix it :)Dennis Hogewoningyou're a genius!
That worked. Our new desktop builds are Windows 10 with current Office 365 apps so luckily no problems with legacy there.
As you said modern auth was disabled and that was the cause.
Thanks, you saved me going mad!
Mark
- Happy I was able to help, have a nice weekend :)
