Error autodiscover metadata in Exchange and Skype for Business Integration RRS feed

  • Question

  • Hi all,

    I integrate Exchange and Skype for Business only in internal

    When I access link https://autodiscover.domain.com/autodiscover/metadata/json/1 --> error Not found

    And type New-CsPartnerApplication, I receive this error

    New-CsPartnerApplication : Cannot bind parameter 'MetadataUrl' to the target. Exception setting "MetadataUrl": "The
    metadata document could not be downloaded from the URL in the MetadataUrl parameter or downloaded data is not a valid
    metadata document, error: The remote server returned an error: (404) Not Found."

    However, I access link https://autodiscover.domain.com:444/autodiscover/metadata/json/1--> Access successfully

    Use Command New-CsPartnerApplication, I still receive other error:

    "The underlying connection was closed: Could not establish trust relationship for secure channel SSL / TLS"

    Can you help me for you know reason??

    Thank you.

    Monday, August 27, 2018 10:56 AM


  • Hi Hale,


    Please use the Exchange Server Management Console run the following Get-ClientAccessServer cmdlet to view the current Autodiscover configuration, just to make sure Autodiscover is well configured.


    And also check if the following DNS records are created that mostly autodiscover-aware clients will query when attempting to locate an Exchange Server.

    CNAME record: autodiscover.domain.com

    SRV record: select “_autodiscover” service, “_tcp” protocol, pointing this record to the CNAME record created in the previous step.

    (Reference: http://blog.schertz.name/2015/09/exchange-and-skype-for-business-integration/)


    Please also try to check the SAN of your certificate on your Exchange server, make sure autodiscover.domain.com is added to the SAN as well.

    Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.

    Best Regards,
    Leon Lu

    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    • Marked as answer by HaLe19295 Tuesday, August 28, 2018 5:17 PM
    Tuesday, August 28, 2018 9:05 AM