SOLVED

Office 365 alias to email

%3CLINGO-SUB%20id%3D%22lingo-sub-1383805%22%20slang%3D%22en-US%22%3EOffice%20365%20alias%20to%20email%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1383805%22%20slang%3D%22en-US%22%3E%3CP%3EI%20want%20to%20change%20an%20existing%20alias%20to%20a%20regular%20email%20account.%26nbsp%3B%20Once%20I%20delete%20the%20Alias%20and%20then%20create%20the%20user%2C%20how%20long%20does%20it%20take%20for%20the%20email%20that%20was%20going%20to%20the%20alias%20to%20go%20to%20the%20newly%20created%20mailbox%3F%26nbsp%3B%20During%20this%20transition%2C%20will%20any%20mail%20be%20lost%20if%20it%20is%20sent%20while%20making%20this%20change%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1383805%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1383872%22%20slang%3D%22en-US%22%3ERe%3A%20Office%20365%20alias%20to%20email%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1383872%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F665221%22%20target%3D%22_blank%22%3E%40johnbentrim%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20you%20are%20synchronising%20AD%20to%20O365%20with%20Azure%20AD%20connect%2C%20then%20you%20will%20need%20to%20remove%20the%20alias%20on-premise%20and%20then%20either%20wait%20for%20AD%20sync%20to%20run%2C%20or%20force%20a%20sync%20manually.%20If%20cloud%20only%2C%20it's%20a%20lot%20quicker%20and%20simpler.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EEven%20taking%20AD%20sync%20into%20account%2C%20the%20process%20can%20be%20done%20very%20quickly.%20%26nbsp%3BAssuming%20you%20have%20directory%20sync%20in%20place%2C%20I'd%20suggest%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E1).%20Remove%20the%20alias%20from%20the%20on-prem%20object%3C%2FP%3E%3CP%3E2).%20Run%20manual%20sync%20of%20AD%20connect%20from%20the%20AADC%20server%20by%20going%20to%20PowerShell%20and%20running%26nbsp%3B%3CSTRONG%3EStart-AdSyncSyncCycle%20-PolicyType%20delta%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E3).%20Check%20that%20the%20alias%20is%20removed%20from%20the%20O365%20account%3C%2FP%3E%3CP%3E4).%20Create%20new%20remote%20mailbox%20on-prem%20and%20then%20re-run%20the%20manual%20sync%20from%20step%202%20again.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYou%20should%20not%20see%20any%20emails%20bouncing%20during%20this%20time%20if%20you%20carry%20out%20these%20steps%20swiftly%20enough.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20you%20are%20cloud%20only%2C%20the%20process%20will%20be%20even%20quicker%20and%20easier%20as%20you%20can%20do%20all%20of%20the%20steps%20from%20the%20Office%20365%20Admin%20Center.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1384096%22%20slang%3D%22en-US%22%3ERe%3A%20Office%20365%20alias%20to%20email%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1384096%22%20slang%3D%22en-US%22%3E%3CP%3ESince%20I'm%20cloud%20only%2C%20I%20don't%20have%20to%20worry%20about%20step%202%3F%26nbsp%3B%20Just%20delete%20the%20alias%2C%20double%20check%20that%20it's%20gone%2C%20then%20create%20the%20user%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1384133%22%20slang%3D%22en-US%22%3ERe%3A%20Office%20365%20alias%20to%20email%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1384133%22%20slang%3D%22en-US%22%3EYes%2C%20nice%20and%20simple.%20You%20are%20good%20to%20go.%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

I want to change an existing alias to a regular email account.  Once I delete the Alias and then create the user, how long does it take for the email that was going to the alias to go to the newly created mailbox?  During this transition, will any mail be lost if it is sent while making this change?

3 Replies
Highlighted

@johnbentrim 

 

If you are synchronising AD to O365 with Azure AD connect, then you will need to remove the alias on-premise and then either wait for AD sync to run, or force a sync manually. If cloud only, it's a lot quicker and simpler.

 

Even taking AD sync into account, the process can be done very quickly.  Assuming you have directory sync in place, I'd suggest;

 

1). Remove the alias from the on-prem object

2). Run manual sync of AD connect from the AADC server by going to PowerShell and running Start-AdSyncSyncCycle -PolicyType delta

3). Check that the alias is removed from the O365 account

4). Create new remote mailbox on-prem and then re-run the manual sync from step 2 again.

 

You should not see any emails bouncing during this time if you carry out these steps swiftly enough.

 

If you are cloud only, the process will be even quicker and easier as you can do all of the steps from the Office 365 Admin Center.

Highlighted

Since I'm cloud only, I don't have to worry about step 2?  Just delete the alias, double check that it's gone, then create the user?

Highlighted
Best Response confirmed by johnbentrim (New Contributor)
Solution
Yes, nice and simple. You are good to go.