Proxy Settings in Outlook Client 2016

Your second screen is irrelevant as it is for EAS accounts which is something completely different from Exchange accounts which use Outlook Anywhere.

Having a properly functioning AutoDiscover service running on your Exchange server is a hard requirement to have a supported Exchange configuration. Outlook 2016 also relies on this AutoDiscover service to obtain all the server settings for various functionality; not just for configuring your account.

When your AutoDiscover service has been configured correctly on the Exchange server, all you have to provide in Outlook would be your name, email address and password and Outlook will configure itself without the need to manually alter something.

Your second screen is irrelevant as it is for EAS accounts which is something completely different from Exchange accounts which use Outlook Anywhere.

Having a properly functioning AutoDiscover service running on your Exchange server is a hard requirement to have a supported Exchange configuration. Outlook 2016 also relies on this AutoDiscover service to obtain all the server settings for various functionality; not just for configuring your account.

When your AutoDiscover service has been configured correctly on the Exchange server, all you have to provide in Outlook would be your name, email address and password and Outlook will configure itself without the need to manually alter something.

This is a hosted Exchange server that I do not control. Is this AutoDiscovery standard with all exchange servers? Is there anyway to manually set this up if you don't have AutoDiscovery on your Exchange server as I am pretty sure mine is not setup or at least setup properly.

-David

This is a hosted Exchange server that I do not control. Is this AutoDiscovery standard with all exchange servers? Is there anyway to manually set this up if you don't have AutoDiscovery on your Exchange server as I am pretty sure mine is not setup or at least setup properly.

Yes, it is a core functionality and a hard requirement for Outlook Anywhere support. I seriously doubt that your hosting provider isn't running it properly on their side.

Are you using this hosted Exchange service with your own domain?
Then make sure that you have a CNAME entry in your DNS configuration for autodiscover.yourdomain.com pointing to the autodiscover domain of your Exchange hosting provider. You Exchange hosting provider should also be able to help you with this.

Due to the complexity of the connection strings for MAPI over HTTP and several other services, manual configuration is no longer an option but as I mentioned; it shouldn't be needed either.

This is a hosted Exchange server that I do not control. Is this AutoDiscovery standard with all exchange servers? Is there anyway to manually set this up if you don't have AutoDiscovery on your Exchange server as I am pretty sure mine is not setup or at least setup properly.

Yes, it is a core functionality and a hard requirement for Outlook Anywhere support. I seriously doubt that your hosting provider isn't running it properly on their side.

Are you using this hosted Exchange service with your own domain?
Then make sure that you have a CNAME entry in your DNS configuration for autodiscover.yourdomain.com pointing to the autodiscover domain of your Exchange hosting provider. You Exchange hosting provider should also be able to help you with this.

Due to the complexity of the connection strings for MAPI over HTTP and several other services, manual configuration is no longer an option but as I mentioned; it shouldn't be needed either.

Let me try to explain a bit more see if I can clear up some of my confusion.

We have a domain which I am not the executor of. Instead of hosting our own exchange server we hired an outside outfit to control our exchange email. So we are using a hosted exchange server with our own domain. But I don't know about "hosted Exchange service" is that different that a hosted exchange server? If there is no difference than the only thing I will need to do is talk to the network administrator and have him add a CNAME entry into our DNS configuration for autodiscovery.mydomain.com and point that to the exchange hosting provider.

Is that correct?

The service exists out of multiple Exchange servers but in this case, it is the same ;-)

Note that it is "autodiscover" and not "autodiscovery" and that it should point to the autodiscover domain of the Exchange environment of your hosting provider.

The service exists out of multiple Exchange servers but in this case, it is the same ;-)

Note that it is "autodiscover" and not "autodiscovery" and that it should point to the autodiscover domain of the Exchange environment of your hosting provider.

Thanks for all your help.. I will work with my network administrator as it seems the issue is on our end.

Thanks,

-David

We use Intermedia for Exchange hosting, apart from any office 365 offering. Our domains have been hosted on Godaddy for the better part of 10 years.  Intermedia notes that unless intermedia is hosting our domains on their DNS servers, Autodiscover will not work.  So what pray tell should i do? terminate a happy relationship because microsoft feels like making less flexible software?  or should i just start shopping for an open source based, standards compliant solution that doesn't pull the rug out from underneath us and the time and money invested?

this is crazy.