If you administrate Office 365 regularly, especially from different locations, you may well have seen this error:
There was no endpoint listening at https://provisioningapi.microsoftonline.com/provisioningwebservice.svc
The number one cause for this error is a proxy servers. The likely cause is that your Internet Explorer browser has a proxy server configured. If this is in the format of a .pac file, you will need to go into IE>Internet Options>Connections>LAN Settings and remove the Proxy entry. Your connection will now be successful.
However if you have a proxy server manually set to a specific server, you need to tell PowerShell to go via the proxy. First though, check your winhttp configuration by running CMD as Administrator and running the following command:
netsh winhttp show proxy
This will probably show the following result:
Now run the following command:
netsh winhttp import proxy ie
This will import your proxy settings into your winhttp configuration and PowerShell should now navigate through the proxy and (hopefully) get to Office 365. Remember to restart PowerShell before attemping this! If this still doesn’t work, try removing the proxy settings in IE completely and retrying. If even this doesn’t do it, then you likely have a web filter blocking your traffic, in which case you will need to make sure the Office 365 IP addresses and/or URLs are allowed through your filter.
A lot of the above information depends on your network configuration and whether you are using transparent proxies or not, so information may not be 100% accurate to your specific setup. If you end up with incorrect winhttp settings and need to reset to defaults, run:
netsh winhttp reset proxy
from an Administrative CMD prompt and you will be back to square one.
Hopefully this helps some of you suffering from issues when trying to connect to Office 365 PowerShell.