Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

AutodiscoverV2 request returns REST API endpoint not AutoDiscoverV1 endpoint in Exchange Server 2019 and 2016


View products that this article applies to.

Symptoms

Assume that you try to make a GET request to get the AutodiscoverV1 endpoint for a mailbox (for example, user1@contoso.com) that’s hosted on Microsoft Exchange Server 2019 or Exchange Server 2016. The JSON emitted is {"Protocol":"AutoDiscoverV1","Url":"https://mail.contoso.com/api"} instead of {"Protocol":"AutoDiscoverV1","Url":"https://autodiscover.contoso.com/autodiscover/autodiscover.xml"}.

↑ Back to the top


Cause

AutodiscoverV1 isn't in the enumeration of SupportedProtocol. The result is that in the ResourceUrlBuilder.GetResourceUrlSuffixForProtocol method, the wrong enumeration value is computed. When the code uses Enum.TryParse, it doesn't check the return value to see whether the parse is successful. The parse isn’t successful, and the enumeration value ends up being REST. That causes the REST endpoint to be returned.

↑ Back to the top


Resolution

To fix this issue, install one of the following updates:

↑ Back to the top


References

Learn about the terminology that Microsoft uses to describe software updates.

↑ Back to the top


Keywords: autodiscoverv2 request returns rest api endpoint not autodiscoverv1, kb, kbqfe, kbHotfixAuto, CI105536

↑ Back to the top

Article Info
Article ID : 4515274
Revision : 6
Created on : 9/17/2019
Published on : 9/17/2019
Exists online : False
Views : 297