Microsoft 365 - Need to add .local domain to accepted domain list - Hybrid Exchange Server

%3CLINGO-SUB%20id%3D%22lingo-sub-2021362%22%20slang%3D%22en-US%22%3EMicrosoft%20365%20-%20Need%20to%20add%20.local%20domain%20to%20accepted%20domain%20list%20-%20Hybrid%20Exchange%20Server%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2021362%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20a%20virtual%20SMTP%20server%20listed%20as%20a%20.local%20address%20that%20sends%20document%20emails%20to%20Microsoft%20exchange%20users%20within%20our%20organization.%20Our%20registered%20domains%20in%20EAC%20end%20with%20.com.%3C%2FP%3E%3CP%3EWe%20currently%20have%20a%20hybrid%20Microsoft%20Exchange%20environment%2C%20but%20as%20of%20last%20week%2C%20the%20domain's%20.local%20FQDN%20ended%20up%20in%20the%20Exchange%20non-accepted%20domain%20list.%3C%2FP%3E%3CP%3EHow%20do%20I%20correct%20this%20and%20get%20our%20local%20SMTP%20server%20domain%20back%20on%20our%20accepted%20domain%20list%3F%3C%2FP%3E%3CP%3EAny%20help%20would%20be%20appreciated.%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EThanks!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2021362%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAdmin%3C%2FLINGO-LABEL%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-2021472%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20365%20-%20Need%20to%20add%20.local%20domain%20to%20accepted%20domain%20list%20-%20Hybrid%20Exchange%20Server%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2021472%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F760367%22%20target%3D%22_blank%22%3E%40TryRestartingIt%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EHi%2C%20what%20version%20of%20Exchange%20on-prem%20are%20you%20running%3F%26nbsp%3B%20Must%20admit%2C%20I've%20never%20heard%20of%20an%20accepted%20domain%20randomly%20being%20removed%20as%20you%20describe.%26nbsp%3B%20Have%20you%20tried%20simply%20adding%20it%20back%20in%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2022741%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20365%20-%20Need%20to%20add%20.local%20domain%20to%20accepted%20domain%20list%20-%20Hybrid%20Exchange%20Server%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2022741%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F616707%22%20target%3D%22_blank%22%3E%40PeterRising%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOur%20on-prem%20has%20Exchange%20Server%202016.%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20.local%20subdomain%20didn't%20have%20to%20be%20added%20in%20the%20past.%20It%20just%20worked.%20I've%20tried%20added%20all%20sorts%20of%20mail%20flow%20exceptions%20and%20whitelisting%2C%20but%20the%20M365%20Admin%20portal%20in%20general%20will%20not%20allow%20a%20.local%20domain.%3C%2FP%3E%3CP%3EAdding%20the%20domain%20to%20our%20physical%20Exchange%20server%20didn't%20seem%20to%20make%20a%20difference.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

We have a virtual SMTP server listed as a .local address that sends document emails to Microsoft exchange users within our organization. Our registered domains in EAC end with .com.

We currently have a hybrid Microsoft Exchange environment, but as of last week, the domain's .local FQDN ended up in the Exchange non-accepted domain list.

How do I correct this and get our local SMTP server domain back on our accepted domain list?

Any help would be appreciated.


Thanks!

 

4 Replies

@TryRestartingIt 

 

Hi, what version of Exchange on-prem are you running?  Must admit, I've never heard of an accepted domain randomly being removed as you describe.  Have you tried simply adding it back in?

@PeterRising 

Our on-prem has Exchange Server 2016. 

The .local subdomain didn't have to be added in the past. It just worked. I've tried added all sorts of mail flow exceptions and whitelisting, but the M365 Admin portal in general will not allow a .local domain.

Adding the domain to our physical Exchange server didn't seem to make a difference. 

@TryRestartingIt 

 

Hmm, sorry not sure then in this instance.  Have you logged a ticket with Microsoft?  I'd suggest this is the next logical step.

@PeterRising 

I got sick of the issue, so I pointed the application's SMTP settings to our hybrid exchange server instead of the local virtual SMTP server. We are all set. I'm thinking Microsoft may be trying to add more email security obstacles.