From 838484c9b99076393aefda6ce3fccfc5237c8d2f Mon Sep 17 00:00:00 2001 From: johage <37371976+johage@users.noreply.github.com> Date: Fri, 23 Jan 2026 10:58:58 -0600 Subject: [PATCH 1/2] Update note on ConnectionUri encryption method Clarified the note about using HTTP instead of HTTPS for the ConnectionUri, explaining the use of Kerberos for encryption. --- .../connect-to-exchange-servers-using-remote-powershell.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/exchange/docs-conceptual/connect-to-exchange-servers-using-remote-powershell.md b/exchange/docs-conceptual/connect-to-exchange-servers-using-remote-powershell.md index 96fdd45233..afed1247a6 100644 --- a/exchange/docs-conceptual/connect-to-exchange-servers-using-remote-powershell.md +++ b/exchange/docs-conceptual/connect-to-exchange-servers-using-remote-powershell.md @@ -74,7 +74,7 @@ If you don't have the Exchange management tools installed on your local computer $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri http:///PowerShell/ -Authentication Kerberos -Credential $UserCredential ``` - **Note**: The _ConnectionUri_ value is `http`, not `https`. + **Note**: The _ConnectionUri_ value is `http`, not `https`. The reason this doesn't use HTTPS is due to the session being encrypted with Kerberos token in the payload. This removes the need to have the session also to be encrypted again using HTTPS. 3. Run the following command: From 0d557e753e464e2d5fb0e828bd9e39a0cebed8c9 Mon Sep 17 00:00:00 2001 From: Chris Davis Date: Fri, 23 Jan 2026 09:23:45 -0800 Subject: [PATCH 2/2] Revise ConnectionUri note and update date Updated the date and improved the note on ConnectionUri usage. --- .../connect-to-exchange-servers-using-remote-powershell.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/exchange/docs-conceptual/connect-to-exchange-servers-using-remote-powershell.md b/exchange/docs-conceptual/connect-to-exchange-servers-using-remote-powershell.md index afed1247a6..d0c67ef3f1 100644 --- a/exchange/docs-conceptual/connect-to-exchange-servers-using-remote-powershell.md +++ b/exchange/docs-conceptual/connect-to-exchange-servers-using-remote-powershell.md @@ -3,7 +3,7 @@ title: "Connect to Exchange servers using remote PowerShell" ms.author: chrisda author: chrisda manager: orspodek -ms.date: 9/7/2023 +ms.date: 01/23/2026 ms.audience: ITPro audience: ITPro ms.topic: article @@ -74,7 +74,8 @@ If you don't have the Exchange management tools installed on your local computer $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri http:///PowerShell/ -Authentication Kerberos -Credential $UserCredential ``` - **Note**: The _ConnectionUri_ value is `http`, not `https`. The reason this doesn't use HTTPS is due to the session being encrypted with Kerberos token in the payload. This removes the need to have the session also to be encrypted again using HTTPS. + > [!TIP] + > The _ConnectionUri_ value uses `http`, not `https` because the session is encrypted by the Kerberos token in the payload. Kerberos encryption removes the need to encrypt the session again using `https`. 3. Run the following command: