Enable AD Connect sync with existing Office 365 accounts and mailbox

%3CLINGO-SUB%20id%3D%22lingo-sub-214765%22%20slang%3D%22en-US%22%3EEnable%20AD%20Connect%20sync%20with%20existing%20Office%20365%20accounts%20and%20mailbox%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-214765%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20managing%20an%20Office%20365%20tenant%20with%2060%20users%20with%20E3%20subscription.%20For%20the%20moment%20all%20users%20have%20a%20username%20with%20%40mydomain.onmicrosoft.com%20domain%20and%20a%20mailbox%20associated.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENow%2C%20I%20want%20to%20synchronize%20password%20of%20the%20local%20AD%20with%20Office%20365%20accounts.%20So%20I%20have%20to%20install%20AD%20Connect%20and%20configure%20the%20sync.%20How%20to%20sync%20a%20local%20AD%20user%20with%20an%20existing%20Office%20365%20user%20%3F%20Note%20that%20for%20the%20moment%2C%20I%20can't%20change%20the%20%40mydomain.onmicrosoft.com%20because%20there%20is%20a%20mailbox%20migration%20running.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnd%20when%20the%20sync%20is%20done%2C%20how%20can%20I%20manage%20online%20mailbox%20%3F%20Do%20I%20have%20to%20install%20a%20local%20hybrid%20Exchange%20%3F%20But%20if%20everything%20is%20already%20created%20online%2C%20how%20my%20Exchange%20will%20know%20existing%20mailboxes%20%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%20for%20you%20help%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-214765%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EExchange%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EHybrid%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-376760%22%20slang%3D%22en-US%22%3ERe%3A%20Enable%20AD%20Connect%20sync%20with%20existing%20Office%20365%20accounts%20and%20mailbox%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-376760%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F65976%22%20target%3D%22_blank%22%3E%40Dominik%20Hoefling%3C%2FA%3E%26nbsp%3BYou%20don't%20need%20a%20full%20install%20of%20Exchange%20to%20manage%20a%20hybrid%20AD%20%2F%20O365%20mail%20environment.%26nbsp%3B%20You%20just%20need%20the%20Azure%20AD%20Connect%20software.%26nbsp%3B%20It%20includes%20the%20PowerShell%20modules%20needed%20for%20AD%20Users%20and%20Computers%20to%20edit%20the%20necessary%20information.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-222280%22%20slang%3D%22en-US%22%3ERe%3A%20Enable%20AD%20Connect%20sync%20with%20existing%20Office%20365%20accounts%20and%20mailbox%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-222280%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Julien%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E1.%20You%20NEED%20Exchange%20on-premises%20for%20recipient%20management.%20It%20is%20not%20supported%20to%20change%20for%20example%20alias%20and%20proxyaddresses%20attribute%20via%20Active%20Directory.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E2.%20Only%20with%20Exchange%202016%20CU10%20you%20can%20create%20shared%20mailboxes%20directly%20in%20Exchange%20Online.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E3.%20Your%20UPN%20should%20match%20your%20primary%20smtp%20address%20as%20best%20practices.%20If%20you%20can%20do%20this%20change%2C%20do%20it.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EBest%2C%3C%2FP%3E%0A%3CP%3EDominik%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-218297%22%20slang%3D%22en-US%22%3ERe%3A%20Enable%20AD%20Connect%20sync%20with%20existing%20Office%20365%20accounts%20and%20mailbox%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-218297%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Julien%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20doesn't%20matter%20what%20the%20UPN%20is%2C%20as%20long%20as%20it%20matches%20the%20user's%20login%20name.%20Or%20are%20you%20saying%20that%20your%20on-premises%20UPN%20is%20not%20an%20email%20address%2C%20i.e.%20username%40domain.local%3F%20If%20so%2C%20when%20configuring%20Azure%20AD%20connect%2C%20just%20select%20to%20use%20mail%26nbsp%3Battribute%20for%20UPN%20and%20you%20should%20be%20fine.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYou%20do%20not%20need%20Exchange%20to%20convert%20users%20to%20shared%20mailboxes%2C%20you%20can%20do%20that%20in%20Office%20365%20too.%20Last%20time%20I%20installed%20an%20Exchange%20server%20from%20scratch%2C%20it%20took%2010%20hours%20or%20so.%20How%20difficult%20it%20is%2C%20depends%20on%20your%20current%20environment%20etc.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-218269%22%20slang%3D%22en-US%22%3ERe%3A%20Enable%20AD%20Connect%20sync%20with%20existing%20Office%20365%20accounts%20and%20mailbox%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-218269%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Nestori%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%20for%20your%20answer.%20the%20problem%20is%20that%20the%20login%20name%20dosen't%20match%20the%20mail%20address.%20In%20this%20case%2C%20do%20I%20have%20to%20set%20the%20UPN%20as%20the%20mail%20domain%20%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20SMTP%20match%20should%20be%20okay%2C%20the%20mail%20attribute%20is%20set%20and%20the%20proxyAddresses%20is%20empty.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20the%20case%2C%20where%20I%20want%20a%20local%20Exchange%20to%20migrate%20user%20mailbox%20to%20shared%2C%20or%20other%20things%2C%20is%20it%20easy%20to%20install%20%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegards%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-215238%22%20slang%3D%22en-US%22%3ERe%3A%20Enable%20AD%20Connect%20sync%20with%20existing%20Office%20365%20accounts%20and%20mailbox%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-215238%22%20slang%3D%22en-US%22%3E%3CP%3EAfter%20the%20migration%20is%20completed%2C%20you%20should%20change%20users'%20UPNs%20to%20match%20those%20in%20on%20prem%20AD.%20I'm%20assuming%20that%20the%20login%20name%20in%20on%20prem%20AD%20is%20same%20than%20email%20address.%20After%20that%2C%20you%20can%20run%20the%20AAD%20Connect%20to%20synchronize%20your%20users%20(and%20connect%20the%20existing%20Office%20365%20users%20to%20AD%20users).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFor%20the%20SMTP%20match%2C%20mail%20attribute%20works%20fine%20unless%20there%20is%20something%20in%20capital%20in%20ProxyAddresses%20attribute%20(such%20as%20SMTP%3Asomething%40else.com).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYou%20do%20not%20need%20Exchange%20in%20your%20scenario%2C%20you%20can%20manage%20users%20(and%20mailboxes)%20in%20on%20prem%20AD.%20However%2C%20to%20add%20aliases%20etc.%2C%20you%20need%20to%20populate%20ProxyAddresses%20attribute.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAfter%20you%20configure%20AAD%20connect%2C%20all%20attributes%20are%20synced%20from%20on%20prem%20to%20AAD.%26nbsp%3BIt%26nbsp%3Bwill%20sync%20back%20to%20AD%20only%20mailbox%20archive%20guids.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-214801%22%20slang%3D%22en-US%22%3ERe%3A%20Enable%20AD%20Connect%20sync%20with%20existing%20Office%20365%20accounts%20and%20mailbox%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-214801%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%20for%20your%20answer.%20Ok%20but%20now%20the%20migration%20is%20already%20started%2C%20and%20I%20must%20wait%20till%20it's%20finished%20to%20perform%20any%20change%20in%20Office%20365.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20I%20can%20prepare%20the%20local%20AD%20accounts%20for%20the%20moment.%20For%20the%20SMTP%20matching%2C%20is%20it%20enough%20to%20fill%20the%20E-mail%20filed%20in%20the%20General%20tab%20of%20a%20user%20properties%20(Attribute%20%3A%20mail)%20%3F%20Or%20do%20I%20have%20to%20set%20the%20%22%3CSPAN%20class%3D%22text-base%22%3EProxyAddresses%22%20attribute%20%3F%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22text-base%22%3EFor%20the%20moment%20there%20is%20no%20Exchange%20server%20present%2C%20all%20e-mails%20was%20on%20an%20external%20Zimbra%20server.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22text-base%22%3ESo%20for%20mailboxes%20management%2C%20it's%20recommended%20to%20have%20an%20hybrid%20Exchange.%20Regarding%20our%20situation%2C%20when%20the%20Exchange%20server%20must%20be%20installed%20and%20when%20the%20hybrid%20configuration%20should%20be%20run%20%3F%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22text-base%22%3EAnd%20how%20mailbox%20attributes%20present%20on%20Exchange%20Online%20will%20be%20be%20imported%20to%20local%20%3F%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22text-base%22%3EThank%20you%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-214776%22%20slang%3D%22en-US%22%3ERe%3A%20Enable%20AD%20Connect%20sync%20with%20existing%20Office%20365%20accounts%20and%20mailbox%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-214776%22%20slang%3D%22en-US%22%3E%3CP%3EYou%20should%20have%20done%20the%20directory%20sync%20before%20you%20started%20the%20mailbox%20migration.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20easiest%20way%20to%20do%20this%20for%2060%20users%20is%20described%20at%20%3CA%20href%3D%22https%3A%2F%2Fsupport.office.com%2Fen-us%2Farticle%2Fuse-minimal-hybrid-to-quickly-migrate-exchange-mailboxes-to-office-365-fdecceed-0702-4af3-85be-f2a0013937ef%3Fui%3Den-US%26amp%3Brs%3Den-US%26amp%3Bad%3DUS%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.office.com%2Fen-us%2Farticle%2Fuse-minimal-hybrid-to-quickly-migrate-exchange-mailboxes-to-office-365-fdecceed-0702-4af3-85be-f2a0013937ef%3Fui%3Den-US%26amp%3Brs%3Den-US%26amp%3Bad%3DUS%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBut%20since%20you%20did%20not%20do%20that%2C%20see%20%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F2641663%2Fhow-to-use-smtp-matching-to-match-on-premises-user-accounts-to-office%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F2641663%2Fhow-to-use-smtp-matching-to-match-on-premises-user-accounts-to-office%3C%2FA%3E%20to%20get%20these%20cloud%20accounts%20connected%20to%20the%20on-premises%20accounts%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1581781%22%20slang%3D%22en-US%22%3ERe%3A%20Enable%20AD%20Connect%20sync%20with%20existing%20Office%20365%20accounts%20and%20mailbox%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1581781%22%20slang%3D%22en-US%22%3E%3CP%3EWhen%20I%20try%20this%2C%20I%20get%20an%26nbsp%3BAttributeValueMustBeUnique%20error%20when%20it%20tries%20to%20syncronize%20for%20the%20new%20user%20since%20the%26nbsp%3BUserPrincipalName%20is%20not%20unique.%20I%20followed%20the%20guide%20on%20this%20page...%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F2641663%2Fuse-smtp-matching-to-match-on-premises-user-accounts-to-office-365%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F2641663%2Fuse-smtp-matching-to-match-on-premises-user-accounts-to-office-365%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDo%20you%20know%20how%20to%20get%20around%20this%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ep.s.%20Sorry%20for%20posting%20on%20an%20old%20thread.%20It%20was%20one%20of%20only%20a%20few%20that%20I%20could%20find%20that%20directly%20discusses%20AD%20Connect%20to%20an%20existing%20365%20company.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22dan_jjjj_0-1597161174661.png%22%20style%3D%22width%3A%20745px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F211798i4C2B0C8D805E7050%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20title%3D%22dan_jjjj_0-1597161174661.png%22%20alt%3D%22dan_jjjj_0-1597161174661.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1582293%22%20slang%3D%22en-US%22%3ERe%3A%20Enable%20AD%20Connect%20sync%20with%20existing%20Office%20365%20accounts%20and%20mailbox%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1582293%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F756077%22%20target%3D%22_blank%22%3E%40dan_jjjj%3C%2FA%3E%2Ccan%20you%20give%20more%20details%20about%20the%20scenario%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1628700%22%20slang%3D%22en-US%22%3ERe%3A%20Enable%20AD%20Connect%20sync%20with%20existing%20Office%20365%20accounts%20and%20mailbox%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1628700%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F89338%22%20target%3D%22_blank%22%3E%40Dean%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20wanted%20to%20followup%20on%20this%20thread.%20We%20are%20in%20the%20process%20of%20a%20similar%20migration.%20My%20question%20is%20since%20the%20Microsoft%20Office%20365%20license%20was%20originally%20issues%20in%20Office%20online%20365%20and%20now%20its%20being%20re-issues%20to%20on-premise%20account%20AD%20%2C%20what%20will%20the%20end%20user%20desktop%20experience%20be%3F%20Will%20they%20be%20prompted%20%2F%20required%20to%20re-logon%20to%20their%20Microsoft%20account%20once%20they%20reopen%20Outlook%3F%20I%20reason%20I%20ask%20is%20because%20we%20have%20152%20users%20who%20will%20be%20in%20this%20same%20scenario%20and%20having%20152%20users%20all%20at%20once%20being%20prompted%20for%20credentials%20is%20very%20time%20consuming%20to%20support.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20thoughts%20to%20this%20will%20be%20welcomed%2C%20thank%20you.%3C%2FP%3E%3CP%3EJerry%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Contributor

Hi,

 

I'm managing an Office 365 tenant with 60 users with E3 subscription. For the moment all users have a username with @mydomain.onmicrosoft.com domain and a mailbox associated.

 

Now, I want to synchronize password of the local AD with Office 365 accounts. So I have to install AD Connect and configure the sync. How to sync a local AD user with an existing Office 365 user ? Note that for the moment, I can't change the @mydomain.onmicrosoft.com because there is a mailbox migration running.

 

And when the sync is done, how can I manage online mailbox ? Do I have to install a local hybrid Exchange ? But if everything is already created online, how my Exchange will know existing mailboxes ?

 

Thank you for you help

10 Replies
Highlighted

You should have done the directory sync before you started the mailbox migration. 

 

The easiest way to do this for 60 users is described at https://support.office.com/en-us/article/use-minimal-hybrid-to-quickly-migrate-exchange-mailboxes-to...

 

But since you did not do that, see https://support.microsoft.com/en-us/help/2641663/how-to-use-smtp-matching-to-match-on-premises-user-... to get these cloud accounts connected to the on-premises accounts

 

Highlighted

Hi,

 

Thank you for your answer. Ok but now the migration is already started, and I must wait till it's finished to perform any change in Office 365.

 

So I can prepare the local AD accounts for the moment. For the SMTP matching, is it enough to fill the E-mail filed in the General tab of a user properties (Attribute : mail) ? Or do I have to set the "ProxyAddresses" attribute ?

 

For the moment there is no Exchange server present, all e-mails was on an external Zimbra server.

So for mailboxes management, it's recommended to have an hybrid Exchange. Regarding our situation, when the Exchange server must be installed and when the hybrid configuration should be run ?

And how mailbox attributes present on Exchange Online will be be imported to local ?

 

Thank you

Highlighted

After the migration is completed, you should change users' UPNs to match those in on prem AD. I'm assuming that the login name in on prem AD is same than email address. After that, you can run the AAD Connect to synchronize your users (and connect the existing Office 365 users to AD users).

 

For the SMTP match, mail attribute works fine unless there is something in capital in ProxyAddresses attribute (such as SMTP:something@else.com).

 

You do not need Exchange in your scenario, you can manage users (and mailboxes) in on prem AD. However, to add aliases etc., you need to populate ProxyAddresses attribute.

 

After you configure AAD connect, all attributes are synced from on prem to AAD. It will sync back to AD only mailbox archive guids. 

Highlighted

Hi Nestori,

 

Thank you for your answer. the problem is that the login name dosen't match the mail address. In this case, do I have to set the UPN as the mail domain ?

 

The SMTP match should be okay, the mail attribute is set and the proxyAddresses is empty.

 

In the case, where I want a local Exchange to migrate user mailbox to shared, or other things, is it easy to install ?

 

Regards

 

Highlighted

Hi Julien,

 

It doesn't matter what the UPN is, as long as it matches the user's login name. Or are you saying that your on-premises UPN is not an email address, i.e. username@domain.local? If so, when configuring Azure AD connect, just select to use mail attribute for UPN and you should be fine.

 

You do not need Exchange to convert users to shared mailboxes, you can do that in Office 365 too. Last time I installed an Exchange server from scratch, it took 10 hours or so. How difficult it is, depends on your current environment etc.

Highlighted

Hi Julien,

 

1. You NEED Exchange on-premises for recipient management. It is not supported to change for example alias and proxyaddresses attribute via Active Directory.

 

2. Only with Exchange 2016 CU10 you can create shared mailboxes directly in Exchange Online.

 

3. Your UPN should match your primary smtp address as best practices. If you can do this change, do it.

 

Best,

Dominik

Highlighted

@Dominik Hoefling You don't need a full install of Exchange to manage a hybrid AD / O365 mail environment.  You just need the Azure AD Connect software.  It includes the PowerShell modules needed for AD Users and Computers to edit the necessary information.

Highlighted

When I try this, I get an AttributeValueMustBeUnique error when it tries to syncronize for the new user since the UserPrincipalName is not unique. I followed the guide on this page...

https://support.microsoft.com/en-us/help/2641663/use-smtp-matching-to-match-on-premises-user-account...

 

Do you know how to get around this?

 

p.s. Sorry for posting on an old thread. It was one of only a few that I could find that directly discusses AD Connect to an existing 365 company. 

 

Thanks

 

dan_jjjj_0-1597161174661.png

 

Highlighted

@dan_jjjj,can you give more details about the scenario?

Highlighted

Hello @Dean

 

I wanted to followup on this thread. We are in the process of a similar migration. My question is since the Microsoft Office 365 license was originally issues in Office online 365 and now its being re-issues to on-premise account AD , what will the end user desktop experience be? Will they be prompted / required to re-logon to their Microsoft account once they reopen Outlook? I reason I ask is because we have 152 users who will be in this same scenario and having 152 users all at once being prompted for credentials is very time consuming to support.

 

Any thoughts to this will be welcomed, thank you.

Jerry