SOLVED

Office 365 minimum hybrid deployment problem with Azure AD sync

%3CLINGO-SUB%20id%3D%22lingo-sub-120068%22%20slang%3D%22en-US%22%3EOffice%20365%20minimum%20hybrid%20deployment%20problem%20with%20Azure%20AD%20sync%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-120068%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20want%20to%20transfer%2020%20mailboxes%20to%20office%20365%20but%20not%20at%20once%20because%20of%20low%20internet%20speed.%20Microsoft%20wizard%20within%20office%20365%20portal%20suggests%20the%20minimum%20hybrid%20configuration%20and%20it%20makes%20all%20changes%20needed%20to%20our%20exchange%20server%202010%20to%20use%20this%20scenario.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHowever%20when%20we%20reach%20the%20azure%20AD%20sync%20step%20we%20have%20a%20problem%20that%20our%20primary%20domain%20on%20premises%20has%20the%20form%20of%20.local%20and%20as%20microsoft%20suggests%20we%20have%20added%20an%20additional%20routable%20(.gr)%20UPN%20suffix%20to%20our%20active%20directory%20so%20it%20can%20be%20synced%20with%20azure.%20We%20have%20also%20changed%20the%20attributes%20on%20the%20account%20tab%20on%20each%20user%20in%20active%20directory%20to%20point%20to%20our%20new%20routable%20UPN%20suffix.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ewhen%20we%20go%20to%20the%20step%20to%20connect%20our%20forest%20Azure%20AD%20connect%20says%20that%20users%20will%20not%20be%20able%20to%20use%20their%20sign%20in%20credentials%20because%20our%20.local%20domain%20name%20is%20not%20in%20office%20365%20which%20is%20normal.%20(Check%20photo%20attached).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOur%20question%20is%20If%20we%20proceed%20from%20this%20step%20how%20users%20will%20login%20to%20their%20computers%20after%20the%20AD%20sync%3F%20right%20now%20they%20login%20with%20domain.local%5Cusername%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ehope%20i%20was%20clear%20enough%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-120068%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20AD%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EHybrid%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMigration%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-120088%22%20slang%3D%22en-US%22%3ERe%3A%20Office%20365%20minimum%20hybrid%20deployment%20problem%20with%20Azure%20AD%20sync%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-120088%22%20slang%3D%22en-US%22%3EIf%20you%20change%20the%20UPN%20in%20your%20local%20AD%2C%20you%20are%20not%20going%20to%20introduce%20any%20problem%20in%20the%20way%20your%20users%20Log%20in%20locally%20in%20their%20computers.%20The%20UPN%20is%20not%20the%20attribute%20used%20to%20log%20in%20local%20computers%3C%2FLINGO-BODY%3E
Deleted
Not applicable

We want to transfer 20 mailboxes to office 365 but not at once because of low internet speed. Microsoft wizard within office 365 portal suggests the minimum hybrid configuration and it makes all changes needed to our exchange server 2010 to use this scenario. 

 

However when we reach the azure AD sync step we have a problem that our primary domain on premises has the form of .local and as microsoft suggests we have added an additional routable (.gr) UPN suffix to our active directory so it can be synced with azure. We have also changed the attributes on the account tab on each user in active directory to point to our new routable UPN suffix. 

 

when we go to the step to connect our forest Azure AD connect says that users will not be able to use their sign in credentials because our .local domain name is not in office 365 which is normal. (Check photo attached).

 

Our question is If we proceed from this step how users will login to their computers after the AD sync? right now they login with domain.local\username 

 

hope i was clear enough

 

1 Reply
best response
Solution
If you change the UPN in your local AD, you are not going to introduce any problem in the way your users Log in locally in their computers. The UPN is not the attribute used to log in local computers
www.000webhost.com