On provisioning mailboxes in Exchange Online when in Hybrid

Published May 20 2020 12:22 PM 42.6K Views

In this blog post we will cover a very common scenario faced by customers who have moved all of their mailboxes from on-premises to the cloud. How do you create mailboxes directly in the cloud? The task might seem simple, but in support we see a fair amount of confusion around it. And there are certainly opportunities to do wrong things here!

You have set up Exchange hybrid configuration with Exchange Online (EXO) and have started or even completed your mailbox migrations.  At some point, you decide that you want to have new mailboxes created as EXO mailboxes instead of creating them on-premises (and then migrating them to Office 365). But you quickly learn that if you create on-premises users, allow them to sync, and then just license them for Exchange Online, you’ll be unable to manage the Exchange attributes because there is no mail-enabled user in the on-premises Exchange organization. 

If you’ve ever been in that position, this is the post for you. The process below will enable you to correctly provision mailboxes in EXO.

Once in hybrid, the Exchange 2013 (or later) Admin Center gives the admin the choice to create a New Office 365 Mailbox instead of a Mailbox.  Using this option will create the AD User AND the Mail-enabled user (MEU) object with the remote routing address (such as jsmith@contoso.mail.onmicrosoft.com).  This will then be synchronized to Azure AD by AAD Connect.  Because we now have a MailUser object on-premises, EXO creates the corresponding Mailbox user.

mbxinhybrid.jpg

This same operation can of course also be accomplished with the new-remotemailbox cmdlet.

Now, whichever way you used, to avoid potential issues if you ever need to offboard this mailbox back to on-premises, we recommend the EXO Exchange GUID be added to the on-premises MEU:

Set-RemoteMailbox “user identity” -ExchangeGuid “value from Exchange Online”

But let’s say you didn’t follow this process, and instead you just created the AD User without the remotemailbox. If this is your scenario then you’ll have to use the PowerShell cmdlet(s) to enable-remotemailbox

The way forward then is to:

  1. Enable-remotemailbox on the AD User (see below)
  2. Validate synchronization to Azure

Here are a few notes regarding the usage of enable-remotemailbox instead of new-remotemailbox. Let’s say you run this command:

Enable-RemoteMailbox jsmith@contoso.com -RemoteRoutingAddress jsmith@contoso.mail.onmicrosoft.com

Since this did not specify a PrimarySMTPAddress then your Exchange Email Address Policy (EAP) will add both the primary via the Email Address Policy (EAP) and secondary proxy address - jsmith@contoso.mail.onmicrosoft.com.  If this is what you wanted, you are good to go!

Sometimes though, we have seen some customers get into trouble when they include the –PrimarySMTPaddress parameter. They want a primary SMTP address that doesn’t match their EAP default. In that case, you’ll need to also add the secondary proxy address jsmith@contoso.mail.onmicrosoft.com in a subsequent PowerShell cmdlet (or use on-premises EAC).

You cannot unfortunately include the secondary proxy address that matches the remote routing address using the Enable-RemoteMailbox cmdlet as it is not a supported parameter. This needs to be done separately using the Set-RemoteMailbox Cmdlet.  The ‘EmailAddresses’ parameter is a multi-valued property and needs to be ‘added’ to the existing values as follows:

Set-RemoteMailbox -Identity jsmith@contoso.com -EmailAddresses @{add= ‘jsmith@contoso.mail.onmicrosoft.com'}

This will add the secondary in the MEU proxy addresses on premises and AAD Connect will synchronize it to the O365 mailbox proxy addresses, enabling delivery via the matching remote routing address.  Again, once the EXO mailbox is created, make sure you add the EXO Exchange GUID to the on-premises MEU.

I wanted to thank Nino Bilic, Ben Winzenz, Mirela Buruiana and Greg Taylor for their review of this post!

Larry Dunnewin

21 Comments
%3CLINGO-SUB%20id%3D%22lingo-sub-1406335%22%20slang%3D%22en-US%22%3EOn%20provisioning%20mailboxes%20in%20Exchange%20Online%20when%20in%20Hybrid%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1406335%22%20slang%3D%22en-US%22%3E%3CP%3EIn%20this%20blog%20post%20we%20will%20cover%20a%20very%20common%20scenario%20faced%20by%20customers%20who%20have%20moved%20all%20of%20their%20mailboxes%20from%20on-premises%20to%20the%20cloud.%20How%20do%20you%20create%20mailboxes%20directly%20in%20the%20cloud%3F%20The%20task%20might%20seem%20simple%2C%20but%20in%20support%20we%20see%20a%20fair%20amount%20of%20confusion%20around%20it.%20And%20there%20are%20certainly%20opportunities%20to%20do%20%3CEM%3Ewrong%3C%2FEM%3E%20things%20here!%3C%2FP%3E%0A%3CP%3EYou%20have%20set%20up%20Exchange%20hybrid%20configuration%20with%20Exchange%20Online%20(EXO)%20and%20have%20started%20or%20even%20completed%20your%20mailbox%20migrations.%26nbsp%3B%20At%20some%20point%2C%20you%20decide%20that%20you%20want%20to%20have%20new%20mailboxes%20created%20as%20EXO%20mailboxes%20instead%20of%20creating%20them%20on-premises%20(and%20then%20migrating%20them%20to%20Office%20365).%20But%20you%20quickly%20learn%20that%20if%20you%20create%20on-premises%20users%2C%20allow%20them%20to%20sync%2C%20and%20then%20just%20license%20them%20for%20Exchange%20Online%2C%20you%E2%80%99ll%20be%20unable%20to%20manage%20the%20Exchange%20attributes%20because%20there%20is%20no%20mail-enabled%20user%20in%20the%20on-premises%20Exchange%20organization.%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIf%20you%E2%80%99ve%20ever%20been%20in%20that%20position%2C%20this%20is%20the%20post%20for%20you.%20The%20process%20below%20will%20enable%20you%20to%20correctly%20provision%20mailboxes%20in%20EXO.%3C%2FP%3E%0A%3CP%3EOnce%20in%20hybrid%2C%20the%20Exchange%202013%20(or%20later)%20Admin%20Center%20gives%20the%20admin%20the%20choice%20to%20create%20a%20New%20Office%20365%20Mailbox%20instead%20of%20a%20Mailbox.%26nbsp%3B%20Using%20this%20option%20will%20create%20the%20AD%20User%20AND%20the%20Mail-enabled%20user%20(MEU)%20object%20with%20the%20remote%20routing%20address%20(such%20as%20jsmith%40contoso.mail.onmicrosoft.com).%26nbsp%3B%20This%20will%20then%20be%20synchronized%20to%20Azure%20AD%20by%20AAD%20Connect.%26nbsp%3B%20Because%20we%20now%20have%20a%20MailUser%20object%20on-premises%2C%20EXO%20creates%20the%20corresponding%20Mailbox%20user.%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20image-alt%3D%22mbxinhybrid.jpg%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F193350i73DAA2CFC16F2412%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%22mbxinhybrid.jpg%22%20alt%3D%22mbxinhybrid.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3EThis%20same%20operation%20can%20of%20course%20also%20be%20accomplished%20with%20the%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fpowershell%2Fmodule%2Fexchange%2Ffederation-and-hybrid%2Fnew-remotemailbox%3Fview%3Dexchange-ps%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Enew-remotemailbox%3C%2FA%3E%20cmdlet.%3C%2FP%3E%0A%3CP%3ENow%2C%20whichever%20way%20you%20used%2C%20to%20avoid%20potential%20issues%20%3CEM%3Eif%20you%3C%2FEM%3E%20%3CEM%3Eever%20need%20to%3C%2FEM%3E%20%3CEM%3Eoffboard%20this%20mailbox%20back%20to%20on-premises%3C%2FEM%3E%2C%20we%20recommend%20the%20EXO%20Exchange%20GUID%20be%20added%20to%20the%20on-premises%20MEU%3A%3C%2FP%3E%0A%3CP%20class%3D%22code%22%3ESet-RemoteMailbox%20%E2%80%9Cuser%20identity%E2%80%9D%20-ExchangeGuid%20%E2%80%9Cvalue%20from%20Exchange%20Online%E2%80%9D%3C%2FP%3E%0A%3CP%3EBut%20let%E2%80%99s%20say%20you%20didn%E2%80%99t%20follow%20this%20process%2C%20and%20instead%20you%20just%20created%20the%20AD%20User%20without%20the%20remotemailbox.%20If%20this%20is%20your%20scenario%20then%20you%E2%80%99ll%20have%20to%20use%20the%20PowerShell%20cmdlet(s)%20to%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fpowershell%2Fmodule%2Fexchange%2Ffederation-and-hybrid%2Fnew-remotemailbox%3Fview%3Dexchange-ps%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Eenable-remotemailbox%3C%2FA%3E.%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20way%20forward%20then%20is%20to%3A%3C%2FP%3E%0A%3COL%3E%0A%3CLI%3EEnable-remotemailbox%20on%20the%20AD%20User%20(see%20below)%3C%2FLI%3E%0A%3CLI%3EValidate%20synchronization%20to%20Azure%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3CP%3EHere%20are%20a%20few%20notes%20regarding%20the%20usage%20of%20enable-remotemailbox%20instead%20of%20new-remotemailbox.%20Let%E2%80%99s%20say%20you%20run%20this%20command%3A%3C%2FP%3E%0A%3CP%20class%3D%22code%22%3EEnable-RemoteMailbox%20jsmith%40contoso.com%20-RemoteRoutingAddress%20jsmith%40contoso.mail.onmicrosoft.com%3C%2FP%3E%0A%3CP%3ESince%20this%20did%20not%20specify%20a%20PrimarySMTPAddress%20then%20your%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fexchange%2Femail-addresses-and-address-books%2Femail-address-policies%2Femail-address-policies%3Fview%3Dexchserver-2019%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EExchange%20Email%20Address%20Policy%20(EAP)%3C%2FA%3E%20will%20add%20both%20the%20primary%20via%20the%20Email%20Address%20Policy%20(EAP)%20and%20secondary%20proxy%20address%20-%20jsmith%40contoso.mail.onmicrosoft.com.%26nbsp%3B%20If%20this%20is%20what%20you%20wanted%2C%20you%20are%20good%20to%20go!%3C%2FP%3E%0A%3CP%3ESometimes%20though%2C%20we%20have%20seen%20some%20customers%20get%20into%20trouble%20when%20they%20include%20the%20%E2%80%93PrimarySMTPaddress%20parameter.%20They%20want%20a%20primary%20SMTP%20address%20that%20doesn%E2%80%99t%20match%20their%20EAP%20default.%20In%20that%20case%2C%20you%E2%80%99ll%20need%20to%20also%20add%20the%20secondary%20proxy%20address%20jsmith%40contoso.mail.onmicrosoft.com%20in%20a%20subsequent%20PowerShell%20cmdlet%20(or%20use%20on-premises%20EAC).%3C%2FP%3E%0A%3CP%3EYou%20cannot%20unfortunately%20include%20the%20secondary%20proxy%20address%20that%20matches%20the%20remote%20routing%20address%20using%20the%20Enable-RemoteMailbox%20cmdlet%20as%20it%20is%20not%20a%20supported%20parameter.%20This%20needs%20to%20be%20done%20separately%20using%20the%20Set-RemoteMailbox%20Cmdlet.%26nbsp%3B%20The%20%E2%80%98EmailAddresses%E2%80%99%20parameter%20is%20a%20multi-valued%20property%20and%20needs%20to%20be%20%E2%80%98added%E2%80%99%20to%20the%20existing%20values%20as%20follows%3A%3C%2FP%3E%0A%3CP%20class%3D%22code%22%3ESet-RemoteMailbox%20-Identity%20jsmith%40contoso.com%20-EmailAddresses%20%40%7Badd%3D%20%E2%80%98jsmith%40contoso.mail.onmicrosoft.com'%7D%3C%2FP%3E%0A%3CP%3EThis%20will%20add%20the%20secondary%20in%20the%20MEU%20proxy%20addresses%20on%20premises%20and%20AAD%20Connect%20will%20synchronize%20it%20to%20the%20O365%20mailbox%20proxy%20addresses%2C%20enabling%20delivery%20via%20the%20matching%20remote%20routing%20address.%20%26nbsp%3BAgain%2C%20once%20the%20EXO%20mailbox%20is%20created%2C%20make%20sure%20you%20add%20the%20EXO%20Exchange%20GUID%20to%20the%20on-premises%20MEU.%3C%2FP%3E%0A%3CP%3EI%20wanted%20to%20thank%20Nino%20Bilic%2C%20Ben%20Winzenz%2C%20Mirela%20Buruiana%20and%20Greg%20Taylor%20for%20their%20review%20of%20this%20post!%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22author%22%3ELarry%20Dunnewin%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-1406335%22%20slang%3D%22en-US%22%3E%3CP%3EIn%20this%20blog%20post%20we%20will%20cover%20a%20very%20common%20scenario%20faced%20by%20customers%20who%20have%20moved%20all%20of%20their%20mailboxes%20from%20on-premises%20to%20the%20cloud.%20How%20do%20you%20create%20mailboxes%20directly%20in%20the%20cloud%3F%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1406335%22%20slang%3D%22en-US%22%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-1410783%22%20slang%3D%22en-US%22%3ERe%3A%20On%20provisioning%20mailboxes%20in%20Exchange%20Online%20when%20in%20Hybrid%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1410783%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Guys%20-%20The%20above%20references%20Exchange%202013%20(or%20later).%3C%2FP%3E%3CP%3EHow%20does%20this%20apply%20when%20your%20on-premise%20environment%20is%20Exchange%202010%3F%3C%2FP%3E%3CP%3EAre%20you%20able%20to%20provide%20guidance%20in%20that%20scenario%20too%3F%3C%2FP%3E%3CP%3EThanks!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1412074%22%20slang%3D%22en-US%22%3ERe%3A%20On%20provisioning%20mailboxes%20in%20Exchange%20Online%20when%20in%20Hybrid%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1412074%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20EAC%20for%20New%20Office%20365%20mailbox%20only%20applies%20to%20Exchange%202013%2B.%26nbsp%3B%20For%20Exchange%202010%20you%20will%20use%20the%20PowerShell%20cmdlets.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1413493%22%20slang%3D%22en-US%22%3ERe%3A%20On%20provisioning%20mailboxes%20in%20Exchange%20Online%20when%20in%20Hybrid%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1413493%22%20slang%3D%22en-US%22%3E%3CP%3EGreat%20post%2C%20I%20was%20actually%20having%20a%20discussion%20with%20my%20team%20about%20this%20very%20subject%20on%20the%20same%20day%20this%20got%20published.%20Spooky!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20do%20have%20one%20question%20regarding%20however.%20In%20a%20Hybrid%20environment%20when%20changing%20a%20users%20UPN%20in%20Active%20Directory%20which%20has%20an%20Exchange%20Online%20Mailbox%20the%20primary%20SMTP%20Address%20does%20not%20get%20updated%20automatically%20on%20either%20end%20to%20reflect%20this.%20Exchange%20on-prem%20and%20EXO%20still%20show%20the%20original%20UPN.%20Even%20after%20forcing%20an%20update%20of%20the%20Email%20Address%20Policy.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETypically%20we%20would%20need%20to%20change%20this%20when%20a%20member%20of%20staff%20changes%20their%20name%2C%20such%20as%20get's%20married%20for%20example.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETo%20resolve%20this%20we%20have%20had%20to%20modify%20primary%20SMTP%20address%20within%20the%20proxyAddresses%20attribute%20under%20the%20users%20account%20within%20Active%20Directory%20then%20force%20a%20sync%20with%20Azure%20AD%20Connect.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20there%20an%20official%20supported%20way%20of%20making%20the%20on-prem%20UPN%20and%20Primary%20SMTP%20address%20match%20between%20the%20two%20environments%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMany%20thanks.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1416153%22%20slang%3D%22en-US%22%3ERe%3A%20On%20provisioning%20mailboxes%20in%20Exchange%20Online%20when%20in%20Hybrid%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1416153%22%20slang%3D%22en-US%22%3E%3CP%3E%3CFONT%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F674814%22%20target%3D%22_blank%22%3E%40Larry_Dunnewin%3C%2FA%3E%2C%20do%20you%20know%20the%20minimum%20CU%20version%20or%20was%20it%20included%20in%20RTM%20for%20Exchange%202013%20%26amp%3B%202016%3F%20My%20gut%20tells%20me%20it%20wasn't%20included%20in%20RTM%20but%20I%20wouldn't%20trust%20that!%20%3A)%3C%2Fimg%3E%20%3C%2FFONT%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1416382%22%20slang%3D%22en-US%22%3ERe%3A%20On%20provisioning%20mailboxes%20in%20Exchange%20Online%20when%20in%20Hybrid%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1416382%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F677690%22%20target%3D%22_blank%22%3E%40GreigMitchell%3C%2FA%3E%26nbsp%3BYou%20can%20enable%20the%20synchronization%20of%20the%20UserPrincipalName%20attribute.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETo%20check%20whether%20this%20feature%20is%20enabled%20run%3C%2FP%3E%3CP%3E%3CSTRONG%3EConnect-MSOLService%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%3CSTRONG%3EGet-MsolDirSyncFeatures%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3Eand%20check%20if%26nbsp%3B%3CEM%3ESynchronizeUpnForManagedUsers%3C%2FEM%3E%20is%20enabled.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3ECaution%3C%2FSTRONG%3E%3A%20Setting%26nbsp%3B%3CEM%3ESynchronizeUpnForManagedUsers%3C%2FEM%3E%20to%20%24true%20is%20a%20one-time%20operation%20and%20cannot%20be%20undone.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20it%20is%20true%20(which%20probably%20is%20not%20the%20case%20in%20your%20environment)%20then%20the%20UPN%20should%20be%20updated%20in%20the%20cloud%20after%20you%20change%20it%20on-premises.%20This%20can%20take%20a%20while.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAn%20automation%20to%20match%20the%20email%20address%20to%20the%20UPN%20does%20not%20exist.%20Best%20you%20can%20do%20is%20having%20an%20active%20EAP%20that%20updates%20the%20email%20address%20based%20on%20the%20alias%20(mailNickname%20in%20Active%20Directory).%20In%20that%20case%2C%20when%20you%20change%20the%20UPN%2C%20you%20must%20change%20the%20alias%2C%20too.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20easiest%20way%20to%20do%20all%20of%20this%20in%20one%20step%20is%20to%20use%20Set-RemoteMailbox%3A%3C%2FP%3E%3CP%20data-unlink%3D%22true%22%3E%3CSTRONG%3ESet-RemoteMailbox%20jon.doe%40example.com%20-UserPrincipalName%20jon.dane%40example.com%26nbsp%3B-Alias%20jon.dane%3C%2FSTRONG%3E%26nbsp%3B%3C%2FP%3E%3CP%20data-unlink%3D%22true%22%3EAnd%20if%20you're%20like%20and%20like%20a%20clean%20user%20object%2C%20you%20can%20change%20the%20RemoteRoutingAddress%20with%20it%20as%20well%3A%3C%2FP%3E%3CP%20data-unlink%3D%22true%22%3E%3CSTRONG%3ESet-RemoteMailbox%20jon.doe%40example.com%20-UserPrincipalName%20jon.dane%40example.com%26nbsp%3B-Alias%20jon.dane%26nbsp%3B%20-RemoteRoutingAddress%20jon.dane%40example.mail.onmicrosoft.com%3C%2FSTRONG%3E%3C%2FP%3E%3CP%20data-unlink%3D%22true%22%3E%26nbsp%3B%3C%2FP%3E%3CP%20data-unlink%3D%22true%22%3EIf%20you%20do%20not%20have%20an%20EAP%2C%20add%20the%20%3CEM%3E-PrimarySmtpAddress%3C%2FEM%3E%20parameter.%3C%2FP%3E%3CP%20data-unlink%3D%22true%22%3E%26nbsp%3B%3C%2FP%3E%3CP%20data-unlink%3D%22true%22%3EThe%20UPN%20change%20at%20Microsoft%20will%20take%20a%20while.%3C%2FP%3E%3CP%20data-unlink%3D%22true%22%3E%26nbsp%3B%3C%2FP%3E%3CP%20data-unlink%3D%22true%22%3EIf%26nbsp%3B%3CEM%3ESynchronizeUpnForManagedUsers%3C%2FEM%3E%20is%20false%2C%20then%20you%20need%20to%20change%20the%20userprincipalname%20manually%20by%20using%20the%26nbsp%3B%3CSTRONG%3ESet-MsolUserPrincipalName%3C%2FSTRONG%3E%20cmdlet.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1417801%22%20slang%3D%22en-US%22%3ERe%3A%20On%20provisioning%20mailboxes%20in%20Exchange%20Online%20when%20in%20Hybrid%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1417801%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F217567%22%20target%3D%22_blank%22%3E%40Joshua%20Bines%3C%2FA%3E%26nbsp%3BI%20do%20not%20know%20for%20sure%20if%20the%20%22new%20office%20365%20mailbox'%20was%20part%20of%20RTM%20for%20Exchange%202013%2C%20however%2C%20I%20am%20on%20the%20side%20of%20it%20was%2C%20rather%20than%20it%20was%20not.%26nbsp%3B%20Regardless%2C%20best%20practice%20for%20Exchange%20Hybrid%20configuration%20is%20to%20have%20your%20on%20premises%20servers%20on%20the%20most%20current%20version.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1418959%22%20slang%3D%22en-US%22%3ERe%3A%20On%20provisioning%20mailboxes%20in%20Exchange%20Online%20when%20in%20Hybrid%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1418959%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F217567%22%20target%3D%22_blank%22%3E%40Joshua%20Bines%3C%2FA%3E%2C%20Remote%20Mailboxes%20were%20introduced%20in%20Exchange%202010%20SP1.%26nbsp%3B%20They%20got%20a%20lot%20easier%20to%20work%20with%20in%20SP2%20when%20the%20HCW%20was%20introduced.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ei.e.%20%3CA%20href%3D%22https%3A%2F%2Flh3.googleusercontent.com%2Fproxy%2F-FxF5xk7hUoc7Wlcc8XKdunjfguHCL2D7TOvVkBKF0Qihw-HhS2uNbKlO-rlcRFfFGgRMulOkJvc087sIyqLq3N1SSqSTjbLRFQ%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Flh3.googleusercontent.com%2Fproxy%2F-FxF5xk7hUoc7Wlcc8XKdunjfguHCL2D7TOvVkBKF0Qihw-HhS2uNbKlO-rlcRFfFGgRMulOkJvc087sIyqLq3N1SSqSTjbLRFQ%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1420337%22%20slang%3D%22en-US%22%3ERe%3A%20On%20provisioning%20mailboxes%20in%20Exchange%20Online%20when%20in%20Hybrid%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1420337%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20can%20comment%20to%20say%20that%20the%20new%20Office%20365%20mailbox%20option%20%3CSTRONG%3Eis%3C%2FSTRONG%3E%20available%20in%20the%20EAC%20for%20Exchange%202016%20when%20in%20Exchange%20Hybrid%20mode%20with%20Office%20365.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20considering%20removing%20the%20Exchange%20Hybrid%20configuration%20and%20did%20so%20in%20our%20test%20environment%20and%20noticed%20that%20the%20option%20to%20create%20an%20Office%20365%20Mailbox%20was%20no%20longer%20in%20the%20EAC%20for%202016.%26nbsp%3B%20We%20are%20hopeful%20that%20we%20can%20find%20a%20Microsoft%20supported%20GUI%20solution%20for%20this%20if%20we%20remove%20Exchange%20Hybrid%20but%2C%20it%20is%20not%20looking%20hopeful%20at%20this%20time.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20going%20to%20continue%20with%20an%20Active%20Directory%20hybrid%20configuration%20and%20would%20like%20to%20know%20if%20you%20have%20any%20account%20management%2Fprovisioning%20best%20practice%20links%20you%20could%20share%20after%20Exchange%20Hybrid%20is%20removed%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%2C%3C%2FP%3E%3CP%3EBentley%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1420669%22%20slang%3D%22en-US%22%3ERe%3A%20On%20provisioning%20mailboxes%20in%20Exchange%20Online%20when%20in%20Hybrid%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1420669%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F512344%22%20target%3D%22_blank%22%3E%40Bentley_at_Work%3C%2FA%3E%26nbsp%3B%20Currently%2C%20when%20users%20are%20synchronized%20with%20AAD%20Connect%2C%20the%20best%20practice%20is%20to%20remain%20in%20a%20hybrid%20configuration%20with%20an%20Exchange%20on%20premises%20server%20for%20management%20of%20Exchange%20Online%20mailbox%20attributes.%26nbsp%3B%3CA%20title%3D%22Why%20you%20may%20not%20want%20to%20remove%20all%20Exchange%20servers%22%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fdecommission-on-premises-exchange%23why-you-may-not-want-to-decommission-exchange-servers-from-on-premises%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3EWhy%20you%20may%20not%20want%20to%20remove%20all%20Exchange%20servers%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1437518%22%20slang%3D%22en-US%22%3ERe%3A%20On%20provisioning%20mailboxes%20in%20Exchange%20Online%20when%20in%20Hybrid%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1437518%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F677690%22%20target%3D%22_blank%22%3E%40GreigMitchell%3C%2FA%3E%20-%20UPN%20change%20due%20to%20Name%20Change%3C%2FP%3E%3CP%3EIn%20the%20old%20Exchange%202010%20we%20would%20just%20modify%20the%20Alias%20and%20it%20would%20update%20the%20email%20address%20since%20our%20policy%20states%20that%20it%20is%20the%20alias%40domain.com.%26nbsp%3B%20But%20in%20Exchange%202016%20Microsoft%20does%20not%20make%20that%20field%20available%2C%20so%20we%20just%20edit%20AD%20to%20change%20their%20mailNickname%20field%20which%20is%20the%20field%20that%20stores%20what%20Exchange%20labels%20%22Alias%22.%26nbsp%3B%20We%20then%20force%20it%20to%20apply%20our%20rule.%26nbsp%3B%20We%20then%20have%20their%20old%20smtp%20address%20in%20there%20and%20their%20new%20SMTP%20address.%26nbsp%3B%20We%20schedule%20and%20let%20them%20continue%20having%20both%20email%20addresses%20for%2060%20days%20to%20clean%20up%20all%20of%20their%20newsletters.%26nbsp%3B%20After%2060%20days%20we%20remove%20their%20old%20email%20address.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1423699%22%20slang%3D%22en-US%22%3ERe%3A%20On%20provisioning%20mailboxes%20in%20Exchange%20Online%20when%20in%20Hybrid%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1423699%22%20slang%3D%22en-US%22%3E%3CP%3EPerhaps%20worth%20mentioning%20that%20you%20can%20create%20rooms%2C%20equipment%20and%20shared-mailboxes%20on-prem%20with%20the%20-room%2F-equipment%2F-shared%20switches%20for%20new-remotemailbox%20(or%20enable-remotemailbox)%20nowadays.%20In%20that%20way%2C%20you%20do%20not%20need%20to%20assign%20a%20license%20at%20the%20creation%20time.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20earlier%20versions%2C%20the%20only%20mailbox%20type%20that%20new-remotemailbox%20could%20create%20was%20a%20user%20mailbox%2C%20so%20you%20had%20to%20do%20that%2C%20wait%20for%20replication%2C%20and%20then%20change%20the%20mailbox%20type%20on%20both%20ends%20to%20match%2C%20and%20could%20revoke%20the%20license%20for%20shared%20mailboxes...which%20was%20a%20pain.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20so%20much%20easier%20now..%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1458474%22%20slang%3D%22en-US%22%3ERe%3A%20On%20provisioning%20mailboxes%20in%20Exchange%20Online%20when%20in%20Hybrid%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1458474%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20also%20very%20curious%20what%20the%20Microsoft%20supported%20way%20is%20for%20changing%20names%20(marriage%2Fdivorce).%3CBR%20%2F%3EWhat%20are%20the%20supported%20issues%20for%20changing%26nbsp%3BmailNickname%2C%20targetAddress%20and%20userPrincipalName.%3C%2FP%3E%3CP%3EIs%20it%20allowed%20to%20change%20them%20in%20AD%20and%20let%20the%20changes%20sync%2C%20or%20does%20it%20have%20to%20be%20done%20with%20Exchange%20PowerShell%20commands%20(or%20GUI)%3F%3C%2FP%3E%3CP%3EAnd%20what%20is%20the%20best%20practice%3F%20Correct%20everything%20or%20leave%20the%20mailNickname%20and%20TargetAddress%20alone%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20really%20would%20like%20an%20official%20answer%20from%20the%20Exchange%20team.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1460524%22%20slang%3D%22en-US%22%3ERe%3A%20On%20provisioning%20mailboxes%20in%20Exchange%20Online%20when%20in%20Hybrid%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1460524%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F185969%22%20target%3D%22_blank%22%3E%40Ron%20Houet%3C%2FA%3E%26nbsp%3B%20There%20is%20an%20official%20answer.%20In%20a%20hybrid%20environment%20with%20Exchange%20you%20must%20use%20Exchange%20to%20manage%20that.%20SO%20either%20through%20the%20ECP%20or%20with%20PowerShell%20(*-RemoteMailbox).%20Everything%20else%20is%20not%20supported.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1460575%22%20slang%3D%22en-US%22%3ERe%3A%20On%20provisioning%20mailboxes%20in%20Exchange%20Online%20when%20in%20Hybrid%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1460575%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F185969%22%20target%3D%22_blank%22%3E%40Ron%20Houet%3C%2FA%3E%26nbsp%3B%20If%20you%20want%20the%20offical%20answer.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EThe%20Exchange%20Management%20Console%2C%20the%20Exchange%20admin%20center%20(EAC)%2C%20and%20the%20Exchange%20Management%20Shell%20are%20the%20only%20supported%20tools%20that%20are%20available%20to%20manage%20Exchange%20recipients%20and%20objects.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fdecommission-on-premises-exchange%23can-third-party-management-tools-be-used%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fdecommission-on-premises-exchange%23can-third-party-management-tools-be-used%3C%2FA%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EThe%20Azure%20AD%20Product%20team%20are%20working%20on%20removing%20this%20requirement%20ATM.%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Ffeedback.azure.com%2Fforums%2F169401-azure-active-directory%2Fsuggestions%2F6412831-remove-requirement-for-onprem-exchange-when-using%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Ffeedback.azure.com%2Fforums%2F169401-azure-active-directory%2Fsuggestions%2F6412831-remove-requirement-for-onprem-exchange-when-using%3C%2FA%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1462662%22%20slang%3D%22en-US%22%3ERe%3A%20On%20provisioning%20mailboxes%20in%20Exchange%20Online%20when%20in%20Hybrid%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1462662%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F217567%22%20target%3D%22_blank%22%3E%40Joshua%20Bines%3C%2FA%3E%26nbsp%3BThank%20you%20for%20your%20answer%20and%20I%20already%20read%20the%20link%20you%20reffered%20to.%20But%20I%20don't%20want%20to%20use%20third%20party%20solutions%20nor%20do%20I%20want%20to%20use%20ADSIEDIT.%20If%20a%20property%20of%20a%20user%20changes%20(like%20the%20UPN)%20you%20can%20change%20that%20in%20Active%20Directory%20Users%20%26amp%3B%20Computers.%20Exchange%20command's%20aren't%20capable%20of%20that.%20If%20you%20do%20that%20the%20other%20properties%20like%26nbsp%3B%3CSPAN%3EmailNickname%20and%20targetAddress%26nbsp%3Bwill%20not%20be%20changed.%20You%20can%20change%20those%20in%20ADUC%20with%20attribute%20editor%20but%20I%20believe%20that's%20not%20a%20supported%20way.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3ESo%20again%2C%20thank%20you%20for%20your%20answer%20but%20I%20really%20would%20like%20an%20answer%20from%20the%20Exchange%20Team%20regarding%20changing%20those%20values.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EAlso%20regarding%20the%20recommended%20way%20whether%20you%20should%20change%20the%26nbsp%3BmailNickname%20and%20targetAddress%26nbsp%3Bor%20if%20you%20should%20leave%20them%20alone.%20(which%20leads%20to%20discrepancies%20in%20the%20attributes)%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1462690%22%20slang%3D%22en-US%22%3ERe%3A%20On%20provisioning%20mailboxes%20in%20Exchange%20Online%20when%20in%20Hybrid%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1462690%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3E%26gt%3B%20If%20a%20property%20of%20a%20user%20changes%20(like%20the%20UPN)%20you%20can%20change%20that%20in%20Active%20Directory%20Users%20%26amp%3B%20Computers.%20Exchange%20command's%20aren't%20capable%20of%20that.%20If%20you%20do%20that%20the%20other%20properties%20like%26nbsp%3B%3C%2FSPAN%3E%3CSPAN%3EmailNickname%20and%20targetAddress%26nbsp%3Bwill%20not%20be%20changed.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F185969%22%20target%3D%22_blank%22%3E%40Ron%20Houet%3C%2FA%3E%26nbsp%3B%20Set-RemoteMailbox%20can%20change%20the%20mailNickname%20(Alias)%2C%20targetAddress%20(RemoteRoutingAddress)%20and%20the%20userPrincippalName.%20Have%20you%20read%20the%20docs%20for%20the%20command%20I%20gave%20you%2C%20because%20it's%20very%20well%20documented%20in%20there.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1462795%22%20slang%3D%22en-US%22%3ERe%3A%20On%20provisioning%20mailboxes%20in%20Exchange%20Online%20when%20in%20Hybrid%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1462795%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Daniel%2C%20my%20apologies%2C%20I%20see%20now%20that%20the%20remote%20mailbox%20commands%20can%20change%20all%20that%20too.%3CBR%20%2F%3EBut%20still%2C%20I%20would%20like%20to%20hear%20the%20best%20practices%20in%20streamlining%20the%20targetAddress%20and%20Alias%20or%20leave%20them%20in%20the%20original%20state%20when%20changing%20a%20username%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1559673%22%20slang%3D%22en-US%22%3ERe%3A%20On%20provisioning%20mailboxes%20in%20Exchange%20Online%20when%20in%20Hybrid%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1559673%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20a%20newbie%20at%20this%2C%20so%20forgive%20me%20if%20it's%20an%20obvious%20%22can't%20do%20it%22.%20I%20have%20to%20modify%20old%20codebase%20that%20creates%20an%20AD%20user%20using%20System.DirectoryServices.%20The%20code%20creates%20an%20AD%20account%2C%20but%20now%20I%20need%20to%20add%20the%20enabling%20of%20the%20remote%20mailbox.%20Is%20there%20a%20way%20to%20do%20the%20same%20as%20new-remotemailbox%20and%20enable-remotemailbox%20in%20DirectoryServices%3F%20Or%20is%20it%20only%20thru%20PowerShell%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%2C%3C%2FP%3E%3CP%3ELauraH%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1599186%22%20slang%3D%22en-US%22%3ERe%3A%20On%20provisioning%20mailboxes%20in%20Exchange%20Online%20when%20in%20Hybrid%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1599186%22%20slang%3D%22en-US%22%3E%3CP%3EUnfortunately%20there%20are%20a%20lot%20of%20features%20missing.%20For%20example%20enabling%20existing%20Users%20in%20the%20GUI.%20This%20is%20possible%20if%20you%20create%20an%20OnPremises%20Mailbox%20but%20not%20when%20creating%20an%20O365%20mailbox%20(why%3F).%20Furthermore%2C%20if%20you%20create%20Room%2FResources%2C%20they%20are%20shown%20in%20the%20%22mailboxes%22%20tab%20and%20not%20in%20the%20%22resources%22%20tab.%20This%20is%20confusing%20to%20delegated%20admins.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EShared%20O365%20mailboxes%20cannot%20be%20created%20in%20the%20GUI%20-%20did%20you%20forget%20the%20entry%20in%20the%20dropdown%20when%20the%20mailbox%20is%20created%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EO365%20resource%2Fshared%20mailboxes%20cannot%20be%20added%20to%20groups%20via%20the%20GUI.%20(this%20is%20btw%20a%20simple%20change%20in%20the%20GroupPicker.as*%20file%20-%20the%20filter%20there%20is%20simply%20missing%20some%20recipient%20types...)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnd%20last%20but%20not%20least%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ffeedback.azure.com%2Fforums%2F169401-azure-active-directory%2Fsuggestions%2F6412831-remove-requirement-for-onprem-exchange-when-using%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Ffeedback.azure.com%2Fforums%2F169401-azure-active-directory%2Fsuggestions%2F6412831-remove-requirement-for-onprem-exchange-when-using%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20solution%20that%20the%20AAD%20Team%20is%20working%20on%2C%20has%20a%20status%20of%20%22Started%22%20for%20exactly%20one%20year%20with%20no%20updates%20how%20it%20is%20proceeding...%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1749253%22%20slang%3D%22en-US%22%3ERe%3A%20On%20provisioning%20mailboxes%20in%20Exchange%20Online%20when%20in%20Hybrid%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1749253%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20planning%20to%20start%20cloud%20mailbox%20provision.%20At%20present%20we%20are%20stuck%20with%20shared%20mailbox%20permission%20issue.%20basically%20you%20can%20take%20advantage%20of%20any%20of%20this%20PS%20command%26nbsp%3B%20New-RemoteMailbox%2C%20Enable-RemoteMailbox%2C%20Set-RemoteMailbox%20to%20create%20Shared%20mailbox%20in%20EXO.%20problem%20is%20after%20that%20how%20can%20we%20grant%20SendAs%20and%20Full%20Access%20permission%20as%20there%20is%20no%20remote%20command%20available%20for%20Add-MailboxPermission.%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3EIssue%20is%20if%20you%20are%20creating%20shared%20mailbox%20using%20script%20you%20will%20have%20to%20silent%20your%20script%20for%2030%20minutes%20or%20go%20in%20loop%20until%20this%20is%20replicated%20on%20Azure-AD.%20You%20can%20not%20run%20Add-MailboxPermission%20until%20mailbox%20is%20provision%20on%20EXO.%3C%2FP%3E%3CP%3EHas%20anyone%20came%20up%20with%20solution%20to%20grant%20mailbox%20permission%20with%20minimum%20admin%20activity%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2001882%22%20slang%3D%22en-US%22%3ERe%3A%20On%20provisioning%20mailboxes%20in%20Exchange%20Online%20when%20in%20Hybrid%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2001882%22%20slang%3D%22en-US%22%3E%3CP%3EI%20did%20not%20see%20an%20answer%20to%20the%20question%20by%20Ron%20above%20that%20I%20am%20also%20looking%20for.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhen%20we%20are%20required%20to%20change%20the%20username%20and%20email%20address%20of%20an%20end%20user%20in%20an%20Hybrid%20O365%20configuration.%26nbsp%3B%26nbsp%3B%3CSPAN%3EWhat%20is%20the%20best%20practice%20for%26nbsp%3B%3C%2FSPAN%3E%3CSPAN%3Ethe%20targetAddress(Remote%20Routing%20Address)%20and%20mailNickName(Alias)%20attributes%3F%3C%2FSPAN%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3ESpecifically%2C%20should%20we%20change%2Fupdate%20them%2C%20adding%20the%20old%20email%20address%20to%20catch%20any%20mail%20that%20may%20still%20be%20sent%20to%20the%20old%20address%2C%20or%20leave%20them%20in%20the%20original%20state%20and%20just%20add%20the%20additional%26nbsp%3Bemail%20address%20needed%20and%20disable%20the%20address%20policy%20so%20the%20new%20address%20can%20be%20set%20as%20the%20Primary%20address%3F%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3ENOTE%3A%20Our%20current%20email%20address%20policy%20makes%20the%20mailnickname%2FAlias%20the%20primary%20address%20and%20sets%20the%20remote%20mail%20address%20to%20the%20mailNickName%40tennant.onmicrosoft.com)%3F%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Version history
Last update:
‎May 20 2020 12:22 PM
Updated by: