Link to home
Start Free TrialLog in
Avatar of LuiLui77
LuiLui77

asked on

Autodiscovery prompt on Outlook client

Hello All,

I am currently running a hybrid setup between my onpremises Exchange server 2007 and Office 365. I have migrated almost all of our users to the cloud. Our MX is still pointing to our onpremises Exchange.

Our ISP has configured all of DNS entries needed, including the Autodiscover entry which is the following: CNAME  -  autodiscover  autodiscover.outlook.com  1 Hour

Email flow seems to be working properly, but in some of my Outlook clients on computers in my network I am getting the following prompt:

"Allow this website to configure user@domain server settings"
"https://mail.domain.com/autodiscover/autodiscover.xml
Your account was redirected to this website for settings
Allow or Cancel"

Of what I understand this says that the autodiscover is redirecting to my OnPremises Exchange server for settings and not to the autodiscover.oulook.com, which is the office 365 one.

I do not know if I am missing something on my internal DNS.

Can someone enlighten me on what's happening?

Also if someone can explain how autodiscover works on my situation I will appreciate it.
Now I am kind of confused on how autodiscover works.
Avatar of mwiesauer
mwiesauer

seems you do use autodiscover via http redirection. this is one of 4 ways to make it working. autodiscover will check if you do have an A record for autodiscover.domain.com and port 80 listening on that address. the "warning" is usual when using http redirection and you can click it away, so that it does not come up in the future. i recommend to check your autodiscover Settings using remote connectivity analyzer (https://testconnectivity.microsoft.com/)

Martin
Avatar of Jeffrey Kane - TechSoEasy
You probably just want to suppress that warning -- there are two ways to do it.

Either install the Microsoft Sign-on assistant (which is found on your Office365 Software Downloads - Desktop Setup.

Or, follow this KB article to suppress the warnings by GPO:  http://support.microsoft.com/kb/2480582

I suggest that you install the Desktop Setup because it will also make sure Outlook is fully patched, etc.

Jeff
Avatar of LuiLui77

ASKER

I have installed Microsoft Sign-on Assistant already. I think I will suppress the message too, but I am still kind of confused as to why is autodiscover redirecting me to my internal Exchange server and not to the Office 365 CNAME entry: autodiscover.outlook.com
ASKER CERTIFIED SOLUTION
Avatar of Jeffrey Kane - TechSoEasy
Jeffrey Kane - TechSoEasy
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Our Internal domain is .local, but I spotted a couple of autodiscovery entries in my internal DNS, that were most probably created when we first implemented Exchange 2007.
I have a SRV _autodiscover entry pointing to my Exchange 2007 FQDN (mail.domain.com)
and a couple of A Records for autodiscover pointing to my Exchange 2007 IP, so I think that explains it. The Autodiscover request generated by the Outlook client is directed to my Exchange box since my DNS is pointing to it, correct me if I am wrong.

I think until I don't delete all these records, the autodiscover will not be directed to Office 365, It will always be directed to my on-premises exchange box.

So I am thinking to delete these records but not sure what will be the effect. Any ideas?

Can I recreate the records (SRV and A) in case I ran into any overlooked issues?
Definitely remove the SRV records in your internal DNS, that is what is causing the problem.  You don't need to add anything else as long as you don't have a zone in your internal dns configured for your public domain name.

You can always create any type of record you like in your DNS.

Jeff
OK Jeff, Thanks. I will remove the SRV record.

My MX record is still pointing to my on-premises. Do you see any issue caused by the SRV record removal?
Two completely separate things.  Go ahead and remove it.

Jeff