From 30d91588977a9d4ef646ed974d8599cd3e91aa06 Mon Sep 17 00:00:00 2001 From: Chris Davis Date: Thu, 11 Dec 2025 17:24:21 -0800 Subject: [PATCH] Update NEW_CMDLETS.md --- repo_docs/NEW_CMDLETS.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/repo_docs/NEW_CMDLETS.md b/repo_docs/NEW_CMDLETS.md index cfa6e96e8d..baa731cabf 100644 --- a/repo_docs/NEW_CMDLETS.md +++ b/repo_docs/NEW_CMDLETS.md @@ -1,5 +1,5 @@ --- -ms.date: 10/03/2025 +ms.date: 12/11/2025 --- # Create new cmdlet articles @@ -55,8 +55,11 @@ You probably know how to connect, but the available workloads and connection met - Exchange: - Exchange Online PowerShell: [Connect to Exchange Online PowerShell](https://learn.microsoft.com/powershell/exchange/connect-to-exchange-online-powershell) + + > [!TIP] + > These instructions also apply to Exchange Online Protection PowerShell (PowerShell in [the Built-in security add-on for on-premises mailboxes](/exchange/standalone-eop/standalone-eop)). + - Security & Compliance PowerShell: [Connect to Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/connect-to-scc-powershell) - - Exchange Online Protection PowerShell for on-premises email organizations: [Connect to Exchange Online PowerShell](https://learn.microsoft.com/powershell/exchange/connect-to-exchange-online-powershell) - Exchange Server PowerShell: [Connect to Exchange servers using remote PowerShell](https://learn.microsoft.com/powershell/exchange/connect-to-exchange-servers-using-remote-powershell) > [!TIP]