This article applies to:
Windows Server 2012 R2, Exchange 2016
When you run the ConfigureEnterprisePartnerApplication.ps1 on your Exchange server in order to configure application partnership with another server (typically Skype for Business or SharePoint) you receive the following error message:
Cannot acquire auth metadata document from ‘https://sfbpool.company.com/metadata/json/1’. Error: The remote server returned an error: (503) Server unavailable.
When you attempt to open the mentioned URL via browser, you are able to open it and you receive the configuration data:
The most usual cause for this error is wrong proxy configuration. Exchange server does not take the proxy configuration from the IE browser. This setting can be configured in 2 places: Windows server OS or the Exchange itself.
Windows proxy settings:
Exchange will by default take over this value for proxy (unless proxy is explicitly defined in Exchange itself)
To see current proxy configuration in Windows, open the command prompt and type the following command:
To remove the proxy settings for direct access you can use the following command:
To use the same settings as defined in Internet Explorer web browser:
To set correct proxy and at the same time exclude local domain:
Note: The proxy port number is usually 8080, but can be different in your environment.
Exchange Proxy Settings
Exchange will by default take the proxy value from the Windows OS (as described above). If you want to configure proxy settings for Exchange server application only you can do that via Exchange PowerShell:
In order to see the current proxy configuration on all your Exchange servers, use the following PowerShell command:
To remove the proxy configuration from all your Exchange Servers:
- FAQ 000180 – How to set Microsoft Teams Room Device to use internal NTP server - December 15, 2021
- FAQ 000178 – How to change the sender and reply E-mail address in Microsoft Bookings - January 11, 2021
- FAQ 000175 – How to use Windows performance monitor to troubleshoot inbound SMTP mail flow in Exchange - July 10, 2019
Leave A Comment