SOLVED

Outlook Profile forced to connect to Windows AD Local Exchange. Need to connect to new M365 tenant

%3CLINGO-SUB%20id%3D%22lingo-sub-2839228%22%20slang%3D%22en-US%22%3EOutlook%20Profile%20forced%20to%20connect%20to%20Windows%20AD%20Local%20Exchange.%20Need%20to%20connect%20to%20new%20M365%20tenant%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2839228%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20a%20customer%20who%20is%20still%20in%20a%20Windows%20AD%20domain.%26nbsp%3B%20They're%20splitting%20from%20the%20parent%20company%2C%20but%20for%20now%20the%20PCs%20still%20have%20to%20be%20in%20the%20domain.%26nbsp%3B%20I've%20migrated%20email%20to%20Microsoft%20365%20from%20their%20in-house%20Exchange.%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20trying%20to%20create%20new%20Outlook%20profiles%20to%20connect%20to%20the%20cloud%2C%20but%20the%20domain%20is%20forcing%20the%20connection%20to%20their%20old%20server.%26nbsp%3B%20How%20can%20I%20force%20or%20override%20this%20and%20connect%20Outlook%20to%20the%20cloud%20directory%20and%20Microsoft%20365%20Exchange%20service%3F%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%2C%3C%2FP%3E%3CP%3EKevin%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2839228%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EExchange%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMigration%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOn-Premises%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
New Contributor

I have a customer who is still in a Windows AD domain.  They're splitting from the parent company, but for now the PCs still have to be in the domain.  I've migrated email to Microsoft 365 from their in-house Exchange. 

I'm trying to create new Outlook profiles to connect to the cloud, but the domain is forcing the connection to their old server.  How can I force or override this and connect Outlook to the cloud directory and Microsoft 365 Exchange service?  

 

Thanks,

Kevin

1 Reply
best response confirmed by Kevin Remde (New Contributor)
Solution
First, you need to identify which method is Outlook hitting. On a domain-joined machine, this is likely the SRV, but just in case go over this article and check by running the Test Email Autoconfiguration wizard: https://support.microsoft.com/en-us/topic/outlook-2016-implementation-of-autodiscover-0d7b2709-958a-...
Once you identify the method, you can use the client-side reg keys to disable it and "instruct" Outlook to proceed to the O365 endpoint.