Hello,
First, you should be using the Plain Old XML (POX) Autodiscover endpoint to gather settings to create an Outlook profile. The SOAP Autodiscover endpoint doesn't contain all the information to configure an Outlook profile properly. My guess is that the target mailbox is using the MAPI over HTTP protocol rather than the RPC over HTTP protocol and that's why the information is not available in the SOAP Autodiscover response. Here is a way you can confirm my guess:
Resolve Exchange Free / Busy and Communicator Presence Issues
Specifically, the section labeled Step 3: Check Autodiscover and Exchange Web Services
If the target mailbox is indeed using MAPI / HTTP as the protocol you can either disable it on that client or you can use the Autodiscover response to configure the profile to use MAPI / HTTP.
http://blogs.technet.com/b/exchange/archive/2014/05/09/outlook-connectivity-with-mapi-over-http.aspx
First, you should be using the Plain Old XML (POX) Autodiscover endpoint to gather settings to create an Outlook profile. The SOAP Autodiscover endpoint doesn't contain all the information to configure an Outlook profile properly. My guess is that the target mailbox is using the MAPI over HTTP protocol rather than the RPC over HTTP protocol and that's why the information is not available in the SOAP Autodiscover response. Here is a way you can confirm my guess:
-
Use Outlook's Test E-Mail Autoconfiguration tool to pull back the POX autodiscover response from the server. An article describing how it can be done can be found here:
Resolve Exchange Free / Busy and Communicator Presence Issues
Specifically, the section labeled Step 3: Check Autodiscover and Exchange Web Services
If the target mailbox is indeed using MAPI / HTTP as the protocol you can either disable it on that client or you can use the Autodiscover response to configure the profile to use MAPI / HTTP.
http://blogs.technet.com/b/exchange/archive/2014/05/09/outlook-connectivity-with-mapi-over-http.aspx