In Exchange 2013 CU11, we introduced a change to the way Remote PowerShell (RPS) functioned. Prior to CU11, Exchange 2013 routed Remote PowerShell requests by finding a random mailbox that is eit...
Updated Jul 01, 2019
Version 2.0
Blog Post
Ross Smith IV not something that I would do usually. However unable to find any good references for this and this is the closest I can find.
In the reference article of yours there is a clear Note: The ConnectionUri value is http, not https.
Connect to Exchange servers using Remote PowerShell.
However the sample Uri that you have on this articles are all https, is that a typo or something more you can help us understand. If its intentional, pointing to any existing documentation would help or maybe a fresh article published.
Moreover, it should become the new default and move away from secure HTTP via Kerberos. It would save some time spent with security teams for port 80 discusssions.