SOLVED
Home

Add an Office 365 domain

%3CLINGO-SUB%20id%3D%22lingo-sub-328276%22%20slang%3D%22en-US%22%3EAdd%20an%20Office%20365%20domain%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-328276%22%20slang%3D%22en-US%22%3E%3CP%3EI've%20added%20a%20new%20domain%20to%20a%20Business%20Essentials%20license%20with%20the%20status%20now%20showing%20setup%20complete.%20The%20plan%20is%20to%20move%20to%20the%20new%20domain%20in%20the%20future.%26nbsp%3B%20To%20test%20I've%20also%20added%20an%20alias%20to%20a%20user%20with%20the%20new%20domain%20e.g.%20webmaster%40newdomain.com%20but%20not%20yet%20set%20it%20as%20the%20primary.%26nbsp%3B%20The%20issue%20is%20when%20sending%20an%20email%20to%20webmaster%40newdomain.com%20I%20get%20an%20access%20denied%20error%20i.e.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERecipient%20address%20rejected%3A%20Access%20denied%20%5B%3CA%20href%3D%22http%3A%2F%2Fme1aus01ft004.eop-aus01.prod.protection.outlook.com%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3EME1AUS01FT004.eop-AUS01.prod.protection.outlook.com%3C%2FA%3E%5D%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EEmails%20to%20the%20primary%20address%20are%20still%20being%20received.%26nbsp%3B%20I've%20used%20MX%20Toolbox%20to%20do%20lookups%20on%20the%20required%20DNS%20records%20and%20all%20look%20ok.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20there%20something%20else%20I%20need%20to%20do%20to%20enable%20the%20new%20domain%20email%20address%3F%26nbsp%3B%20Does%20the%20addition%20of%20an%20alias%20take%20effect%20immediately%20or%20is%20there%20a%20delay%20period%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20for%20you%20help%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDavid%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-328276%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAdmin%20center%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-329935%22%20slang%3D%22en-US%22%3ERe%3A%20Add%20an%20Office%20365%20domain%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-329935%22%20slang%3D%22en-US%22%3E%3CP%3EIt%20was%20definitely%20a%20propagation%20delay.%26nbsp%3B%20Emails%20to%20the%20new%20domain%20now%20working.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDavid%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-328399%22%20slang%3D%22en-US%22%3ERe%3A%20Add%20an%20Office%20365%20domain%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-328399%22%20slang%3D%22en-US%22%3E%3CP%3EI've%20confirmed%20the%20user%20has%20a%20Business%20Essentials%20product%20license.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDavid%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-328395%22%20slang%3D%22en-US%22%3ERe%3A%20Add%20an%20Office%20365%20domain%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-328395%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20for%20the%20advice%20Chris.%26nbsp%3B%20Will%20double%20check%20and%20wait%20for%20propagation%20and%20let%20you%20know%20how%20it%20goes%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDavid%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-328366%22%20slang%3D%22en-US%22%3ERe%3A%20Add%20an%20Office%20365%20domain%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-328366%22%20slang%3D%22en-US%22%3ECan%20you%20also%20confirm%20the%20right%20licenses%20are%20assigned%20to%20the%20user%20where%20you%20have%20defined%20the%20alias%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-328301%22%20slang%3D%22en-US%22%3ERe%3A%20Add%20an%20Office%20365%20domain%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-328301%22%20slang%3D%22en-US%22%3EHi%20David%2C%3CBR%20%2F%3E%3CBR%20%2F%3EIf%20you%20have%20recently%20set%20the%20DNS%20records%20and%20added%20the%20mail%20alias%20to%20the%20mailbox%20then%20it%20can%20take%20some%20time%20to%20propagate%20(Global%20DNS%20propagation%20is%2072%20hours).%20I%20would%20leave%20it%20a%20few%20hours%20and%20then%20send%20to%20the%20mail%20alias%20again.%20If%20it%20doesn't%20work%20in%20this%20case%20then%20I%20would%20double%20check%20the%20DNS%20records%2C%20ensure%20that%20the%20domain%20is%20showing%20in%20the%20accepted%20domains%20in%20the%20Exchange%20Admin%20console%2C%20and%20that%20the%20alias%20is%20on%20the%20mailbox%20in%20the%20Exchange%20Admin%20console.%20If%20all%20of%20this%20is%2C%20then%20wait%20one%20day%20and%20try%20again.%20If%20this%20still%20isn't%20working%2C%20let%20us%20know%20and%20we'll%20investigate%3CBR%20%2F%3E%3CBR%20%2F%3EHope%20that%20answers%20your%20question!%3CBR%20%2F%3E%3CBR%20%2F%3EBest%2C%20Chris%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

I've added a new domain to a Business Essentials license with the status now showing setup complete. The plan is to move to the new domain in the future.  To test I've also added an alias to a user with the new domain e.g. webmaster@newdomain.com but not yet set it as the primary.  The issue is when sending an email to webmaster@newdomain.com I get an access denied error i.e.

 

Recipient address rejected: Access denied [ME1AUS01FT004.eop-AUS01.prod.protection.outlook.com]

 

Emails to the primary address are still being received.  I've used MX Toolbox to do lookups on the required DNS records and all look ok.

 

Is there something else I need to do to enable the new domain email address?  Does the addition of an alias take effect immediately or is there a delay period?

 

Thanks for you help,

 

David

 

5 Replies
Highlighted
Solution
Hi David,

If you have recently set the DNS records and added the mail alias to the mailbox then it can take some time to propagate (Global DNS propagation is 72 hours). I would leave it a few hours and then send to the mail alias again. If it doesn't work in this case then I would double check the DNS records, ensure that the domain is showing in the accepted domains in the Exchange Admin console, and that the alias is on the mailbox in the Exchange Admin console. If all of this is, then wait one day and try again. If this still isn't working, let us know and we'll investigate

Hope that answers your question!

Best, Chris
Highlighted
Can you also confirm the right licenses are assigned to the user where you have defined the alias?
Highlighted

Thanks for the advice Chris.  Will double check and wait for propagation and let you know how it goes

 

David

Highlighted

I've confirmed the user has a Business Essentials product license.

 

Thanks,

 

David

Highlighted

It was definitely a propagation delay.  Emails to the new domain now working.

 

Thanks,

 

David