From c4feef063667bb367a13278d32c4685fe1267558 Mon Sep 17 00:00:00 2001
From: Saisang Cai <Saisang@users.noreply.github.com>
Date: Fri, 1 Aug 2025 22:25:16 +0800
Subject: [PATCH 001/145] Migrate docs build to use PSMD2Yaml and new page
 template

When MAML2Yaml is not in the path of monikerMapping.json, reference content in the docset will be built by PSMD2Yaml instead of its predecessor MAML2Yaml. For details, see https://dev.azure.com/ceapex/Engineering/_workitems/edit/783982
---
 .openpublishing.publish.config.json           | 32 +++++++++----------
 .../{MAML2Yaml => }/monikerMapping.json       |  0
 .../{MAML2Yaml => }/monikerMapping.json       |  0
 .../{MAML2Yaml => }/monikerMapping.json       |  0
 .../{MAML2Yaml => }/monikerMapping.json       |  0
 .../{MAML2Yaml => }/monikerMapping.json       |  0
 6 files changed, 16 insertions(+), 16 deletions(-)
 rename exchange/mapping/{MAML2Yaml => }/monikerMapping.json (100%)
 rename skype/mapping/{MAML2Yaml => }/monikerMapping.json (100%)
 rename spmt/mapping/{MAML2Yaml => }/monikerMapping.json (100%)
 rename teams/mapping/{MAML2Yaml => }/monikerMapping.json (100%)
 rename whiteboard/mapping/{MAML2Yaml => }/monikerMapping.json (100%)

diff --git a/.openpublishing.publish.config.json b/.openpublishing.publish.config.json
index ae9f54a3f2..6144e7e800 100644
--- a/.openpublishing.publish.config.json
+++ b/.openpublishing.publish.config.json
@@ -37,7 +37,7 @@
             "docset_name": "exchange-ps",
             "locale": "en-us",
             "monikerPath": [
-                "mapping/MAML2Yaml/monikerMapping.json"
+                "mapping/monikerMapping.json"
             ],
             "moniker_ranges": [],
             "monikers": [],
@@ -46,8 +46,8 @@
             "type_mapping": {
                 "Conceptual": "Content",
                 "ManagedReference": "Content",
-                "PowershellCmdlet": "Content",
-                "PowershellModule": "Content",
+                "PowerShellCmdlet1": "Content",
+                "PowerShellModule1": "Content",
                 "RestApi": "Content"
             },
             "version": 0
@@ -86,7 +86,7 @@
             "docset_name": "skype-ps",
             "locale": "en-us",
             "monikerPath": [
-                "mapping/MAML2Yaml/monikerMapping.json"
+                "mapping/monikerMapping.json"
             ],
             "moniker_ranges": [],
             "monikers": [],
@@ -95,8 +95,8 @@
             "type_mapping": {
                 "Conceptual": "Content",
                 "ManagedReference": "Content",
-                "PowershellCmdlet": "Content",
-                "PowershellModule": "Content",
+                "PowerShellCmdlet1": "Content",
+                "PowerShellModule1": "Content",
                 "RestApi": "Content"
             },
             "version": 0
@@ -108,7 +108,7 @@
             "docset_name": "spmt-ps",
             "locale": "en-us",
             "monikerPath": [
-                "mapping/MAML2Yaml/monikerMapping.json"
+                "mapping/monikerMapping.json"
             ],
             "moniker_ranges": [],
             "monikers": [],
@@ -117,8 +117,8 @@
             "type_mapping": {
                 "Conceptual": "Content",
                 "ManagedReference": "Content",
-                "PowershellCmdlet": "Content",
-                "PowershellModule": "Content",
+                "PowerShellCmdlet1": "Content",
+                "PowerShellModule1": "Content",
                 "RestApi": "Content"
             },
             "version": 0
@@ -135,7 +135,7 @@
             "docset_name": "teams-ps",
             "locale": "en-us",
             "monikerPath": [
-                "mapping/MAML2Yaml/monikerMapping.json"
+                "mapping/monikerMapping.json"
             ],
             "moniker_ranges": [],
             "monikers": [],
@@ -144,8 +144,8 @@
             "type_mapping": {
                 "Conceptual": "Content",
                 "ManagedReference": "Content",
-                "PowershellCmdlet": "Content",
-                "PowershellModule": "Content",
+                "PowerShellCmdlet1": "Content",
+                "PowerShellModule1": "Content",
                 "RestApi": "Content"
             },
             "version": 0
@@ -162,7 +162,7 @@
             "docset_name": "whiteboard-ps",
             "locale": "en-us",
             "monikerPath": [
-                "mapping/MAML2Yaml/monikerMapping.json"
+                "mapping/monikerMapping.json"
             ],
             "moniker_ranges": [],
             "monikers": [],
@@ -171,8 +171,8 @@
             "type_mapping": {
                 "Conceptual": "Content",
                 "ManagedReference": "Content",
-                "PowershellCmdlet": "Content",
-                "PowershellModule": "Content",
+                "PowerShellCmdlet1": "Content",
+                "PowerShellModule1": "Content",
                 "RestApi": "Content"
             },
             "version": 0
@@ -199,4 +199,4 @@
             "template_folder": "_themes.pdf"
         }
     }
-}
\ No newline at end of file
+}
diff --git a/exchange/mapping/MAML2Yaml/monikerMapping.json b/exchange/mapping/monikerMapping.json
similarity index 100%
rename from exchange/mapping/MAML2Yaml/monikerMapping.json
rename to exchange/mapping/monikerMapping.json
diff --git a/skype/mapping/MAML2Yaml/monikerMapping.json b/skype/mapping/monikerMapping.json
similarity index 100%
rename from skype/mapping/MAML2Yaml/monikerMapping.json
rename to skype/mapping/monikerMapping.json
diff --git a/spmt/mapping/MAML2Yaml/monikerMapping.json b/spmt/mapping/monikerMapping.json
similarity index 100%
rename from spmt/mapping/MAML2Yaml/monikerMapping.json
rename to spmt/mapping/monikerMapping.json
diff --git a/teams/mapping/MAML2Yaml/monikerMapping.json b/teams/mapping/monikerMapping.json
similarity index 100%
rename from teams/mapping/MAML2Yaml/monikerMapping.json
rename to teams/mapping/monikerMapping.json
diff --git a/whiteboard/mapping/MAML2Yaml/monikerMapping.json b/whiteboard/mapping/monikerMapping.json
similarity index 100%
rename from whiteboard/mapping/MAML2Yaml/monikerMapping.json
rename to whiteboard/mapping/monikerMapping.json

From 9bece9560ce4a4445169f7e79abf95905903e780 Mon Sep 17 00:00:00 2001
From: Jeahenng <jeahenng@outlook.com>
Date: Mon, 4 Aug 2025 13:30:09 +0800
Subject: [PATCH 002/145] Update New-CsTeamsCallingPolicy.md

---
 teams/teams-ps/MicrosoftTeams/New-CsTeamsCallingPolicy.md | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/teams/teams-ps/MicrosoftTeams/New-CsTeamsCallingPolicy.md b/teams/teams-ps/MicrosoftTeams/New-CsTeamsCallingPolicy.md
index eda358df5f..8e454b0d26 100644
--- a/teams/teams-ps/MicrosoftTeams/New-CsTeamsCallingPolicy.md
+++ b/teams/teams-ps/MicrosoftTeams/New-CsTeamsCallingPolicy.md
@@ -684,9 +684,6 @@ Accept wildcard characters: False
 
 > Applicable: Microsoft Teams
 
->[!NOTE]
->This feature has not been released yet and will have no changes if it is enabled or disabled.
-
 Allows users to use real time text during a call, allowing them to communicate by typing their messages in real time.
 
 Possible Values:

From 7bd81e8ef53049e8d7bdb7d2ec0946e76466515d Mon Sep 17 00:00:00 2001
From: Jeahenng <jeahenng@outlook.com>
Date: Mon, 4 Aug 2025 13:31:01 +0800
Subject: [PATCH 003/145] Update New-CsTeamsMeetingPolicy.md

---
 teams/teams-ps/MicrosoftTeams/New-CsTeamsMeetingPolicy.md | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/teams/teams-ps/MicrosoftTeams/New-CsTeamsMeetingPolicy.md b/teams/teams-ps/MicrosoftTeams/New-CsTeamsMeetingPolicy.md
index eeb72afd3f..de4222da63 100644
--- a/teams/teams-ps/MicrosoftTeams/New-CsTeamsMeetingPolicy.md
+++ b/teams/teams-ps/MicrosoftTeams/New-CsTeamsMeetingPolicy.md
@@ -1602,9 +1602,6 @@ Accept wildcard characters: False
 
 > Applicable: Microsoft Teams
 
->[!NOTE]
->This feature has not been released yet and will have no changes if it is enabled or disabled.
-
 Allows users to use real time text during a meeting, allowing them to communicate by typing their messages in real time.
 
 Possible Values:

From 9fa77ec005228c0bc0f8e7671527059aa6b5c07a Mon Sep 17 00:00:00 2001
From: Jeahenng <jeahenng@outlook.com>
Date: Mon, 4 Aug 2025 13:31:33 +0800
Subject: [PATCH 004/145] Update Set-CsTeamsCallingPolicy.md

---
 teams/teams-ps/MicrosoftTeams/Set-CsTeamsCallingPolicy.md | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/teams/teams-ps/MicrosoftTeams/Set-CsTeamsCallingPolicy.md b/teams/teams-ps/MicrosoftTeams/Set-CsTeamsCallingPolicy.md
index 1d0d11adb7..240f14ab0c 100644
--- a/teams/teams-ps/MicrosoftTeams/Set-CsTeamsCallingPolicy.md
+++ b/teams/teams-ps/MicrosoftTeams/Set-CsTeamsCallingPolicy.md
@@ -687,9 +687,6 @@ Accept wildcard characters: False
 
 > Applicable: Microsoft Teams
 
->[!NOTE]
->This feature has not been released yet and will have no changes if it is enabled or disabled.
-
 Allows users to use real time text during a call, allowing them to communicate by typing their messages in real time.
 
 Possible Values:

From 5705ad2919cd12976be2c35b31b59c5ac3dbb21d Mon Sep 17 00:00:00 2001
From: Jeahenng <jeahenng@outlook.com>
Date: Mon, 4 Aug 2025 13:32:03 +0800
Subject: [PATCH 005/145] Update Set-CsTeamsMeetingPolicy.md

---
 teams/teams-ps/MicrosoftTeams/Set-CsTeamsMeetingPolicy.md | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/teams/teams-ps/MicrosoftTeams/Set-CsTeamsMeetingPolicy.md b/teams/teams-ps/MicrosoftTeams/Set-CsTeamsMeetingPolicy.md
index d250f0f641..8ae549b548 100644
--- a/teams/teams-ps/MicrosoftTeams/Set-CsTeamsMeetingPolicy.md
+++ b/teams/teams-ps/MicrosoftTeams/Set-CsTeamsMeetingPolicy.md
@@ -1655,9 +1655,6 @@ Accept wildcard characters: False
 
 > Applicable: Microsoft Teams
 
->[!NOTE]
->This feature has not been released yet and will have no changes if it is enabled or disabled.
-
 Allows users to use real time text during a meeting, allowing them to communicate by typing their messages in real time.
 
 Possible Values:

From c66b876c63531f9b56913645b0eafe39c7aa108b Mon Sep 17 00:00:00 2001
From: Sean Wheeler <sean.wheeler@microsoft.com>
Date: Mon, 4 Aug 2025 08:38:10 -0500
Subject: [PATCH 006/145] Restore deleted file

---
 ...able-CsTeamsShiftsConnectionErrorReport.md | 70 +++++++++++++++++++
 1 file changed, 70 insertions(+)
 create mode 100644 teams/teams-ps/teams/Disable-CsTeamsShiftsConnectionErrorReport.md

diff --git a/teams/teams-ps/teams/Disable-CsTeamsShiftsConnectionErrorReport.md b/teams/teams-ps/teams/Disable-CsTeamsShiftsConnectionErrorReport.md
new file mode 100644
index 0000000000..60edafb900
--- /dev/null
+++ b/teams/teams-ps/teams/Disable-CsTeamsShiftsConnectionErrorReport.md
@@ -0,0 +1,70 @@
+---
+external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml
+Module Name: MicrosoftTeams
+title: Disable-CsTeamsShiftsConnectionErrorReport
+author: gucsun
+ms.author: gucsun
+manager: navinth
+online version: https://learn.microsoft.com/powershell/module/teams/disable-csteamsshiftsconnectionerrorreport
+schema: 2.0.0
+---
+
+# Disable-CsTeamsShiftsConnectionErrorReport
+
+## SYNOPSIS
+
+This cmdlet disables an error report.
+
+## SYNTAX
+
+```
+Disable-CsTeamsShiftsConnectionErrorReport -ErrorReportId <String> [<CommonParameters>]
+```
+
+## DESCRIPTION
+
+**Note:** This cmdlet is currently in public preview.
+
+This cmdlet disables an error report. All available instances can be found by running [Get-CsTeamsShiftsConnectionErrorReport](https://learn.microsoft.com/powershell/module/teams/get-csteamsshiftsconnectionerrorreport).
+
+## EXAMPLES
+
+### Example 1
+```powershell
+PS C:\> Disable-CsTeamsShiftsConnectionErrorReport -ErrorReportId 18b3e490-e6ed-4c2e-9925-47e36609dff3
+```
+
+Disables the error report with ID `18b3e490-e6ed-4c2e-9925-47e36609dff3`.
+
+## PARAMETERS
+
+### -ErrorReportId
+
+> Applicable: Microsoft Teams
+
+The ID of the error report that you want to disable.
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+
+Required: True
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### CommonParameters
+This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).
+
+## INPUTS
+
+## OUTPUTS
+
+## NOTES
+
+## RELATED LINKS
+
+[Get-CsTeamsShiftsConnectionErrorReport](https://learn.microsoft.com/powershell/module/teams/get-csteamsshiftsconnectionerrorreport)

From 78d46dee8f73890acf401cab172085b417942f66 Mon Sep 17 00:00:00 2001
From: Chris Davis <chris.davis@microsoft.com>
Date: Mon, 4 Aug 2025 15:09:27 -0700
Subject: [PATCH 007/145] Cmdlet ref link updates

---
 .../app-only-auth-powershell-v2.md            | 18 ++---
 .../client-advanced-settings.md               |  4 +-
 .../docs-conceptual/cmdlet-property-sets.md   | 16 ++--
 ...connect-exo-powershell-managed-identity.md |  8 +-
 .../connect-to-exchange-online-powershell.md  |  2 +-
 .../connect-to-scc-powershell.md              |  2 +-
 ...e-powershell-access-to-exchange-servers.md |  2 +-
 .../exchange-online-powershell-v2.md          | 78 +++++++++----------
 exchange/docs-conceptual/filter-properties.md | 40 +++++-----
 exchange/docs-conceptual/filters-v2.md        |  6 +-
 exchange/docs-conceptual/recipient-filters.md | 64 +++++++--------
 .../recipientfilter-properties.md             | 18 ++---
 exchange/docs-conceptual/scc-powershell.md    |  4 +-
 ...alues-for-custompropertynames-parameter.md |  2 +-
 14 files changed, 132 insertions(+), 132 deletions(-)

diff --git a/exchange/docs-conceptual/app-only-auth-powershell-v2.md b/exchange/docs-conceptual/app-only-auth-powershell-v2.md
index f23758f7ff..38fa8dc50f 100644
--- a/exchange/docs-conceptual/app-only-auth-powershell-v2.md
+++ b/exchange/docs-conceptual/app-only-auth-powershell-v2.md
@@ -38,17 +38,17 @@ Certificate based authentication (CBA) or app-only authentication as described i
 >   If the procedures in this article don't work for you, verify that you don't have Beta versions of the PackageManagement or PowerShellGet modules installed by running the following command: `Get-InstalledModule PackageManagement -AllVersions; Get-InstalledModule PowerShellGet -AllVersions`.
 >
 > - In Exchange Online PowerShell, you can't use the procedures in this article with the following Microsoft 365 Group cmdlets:
->   - [New-UnifiedGroup](/powershell/module/exchange/new-unifiedgroup)
->   - [Remove-UnifiedGroup](/powershell/module/exchange/remove-unifiedgroup)
->   - [Remove-UnifiedGroupLinks](/powershell/module/exchange/remove-unifiedgrouplinks)
->   - [Add-UnifiedGroupLinks](/powershell/module/exchange/add-unifiedgrouplinks)
+>   - [New-UnifiedGroup](/powershell/module/exchangepowershell/new-unifiedgroup)
+>   - [Remove-UnifiedGroup](/powershell/module/exchangepowershell/remove-unifiedgroup)
+>   - [Remove-UnifiedGroupLinks](/powershell/module/exchangepowershell/remove-unifiedgrouplinks)
+>   - [Add-UnifiedGroupLinks](/powershell/module/exchangepowershell/add-unifiedgrouplinks)
 >
 >   You can use Microsoft Graph to replace most of the functionality from those cmdlets. For more information, see [Working with groups in Microsoft Graph](/graph/api/resources/groups-overview).
 >
 > - In Security & Compliance PowerShell, you can't use the procedures in this article with the following Microsoft 365 Group cmdlets:
->   - [Get-ComplianceSearchAction](/powershell/module/exchange/get-compliancesearchaction)
->   - [New-ComplianceSearch](/powershell/module/exchange/new-compliancesearch)
->   - [Start-ComplianceSearch](/powershell/module/exchange/start-compliancesearch)
+>   - [Get-ComplianceSearchAction](/powershell/module/exchangepowershell/get-compliancesearchaction)
+>   - [New-ComplianceSearch](/powershell/module/exchangepowershell/new-compliancesearch)
+>   - [Start-ComplianceSearch](/powershell/module/exchangepowershell/start-compliancesearch)
 >
 > - Delegated scenarios are supported in Exchange Online. The recommended method for connecting with delegation is using GDAP and App Consent. For more information, see [Use the Exchange Online PowerShell v3 Module with GDAP and App Consent](/powershell/partnercenter/exchange-online-gdap-app). You can also use multi-tenant applications when CSP relationships are not created with the customer. The required steps for using multi-tenant applications are called out within the regular instructions in this article.
 >
@@ -523,7 +523,7 @@ To assign custom role groups to the application using service principals, do the
    $SP = Get-ServicePrincipal -Identity "SP for Azure AD App ExO PowerShell CBA"
    ```
 
-   For detailed syntax and parameter information, see [New-ServicePrincipal](/powershell/module/exchange/new-serviceprincipal).
+   For detailed syntax and parameter information, see [New-ServicePrincipal](/powershell/module/exchangepowershell/new-serviceprincipal).
 
 3. In Exchange Online PowerShell or Security & Compliance PowerShell, run the following command to add the service principal as a member of the custom role group:
 
@@ -537,4 +537,4 @@ To assign custom role groups to the application using service principals, do the
    Add-RoleGroupMember -Identity "Contoso View-Only Recipients" -Member $SP.Identity
    ```
 
-   For detailed syntax and parameter information, see [Add-RoleGroupMember](/powershell/module/exchange/add-rolegroupmember).
+   For detailed syntax and parameter information, see [Add-RoleGroupMember](/powershell/module/exchangepowershell/add-rolegroupmember).
diff --git a/exchange/docs-conceptual/client-advanced-settings.md b/exchange/docs-conceptual/client-advanced-settings.md
index dc5a85dd20..965318b2df 100644
--- a/exchange/docs-conceptual/client-advanced-settings.md
+++ b/exchange/docs-conceptual/client-advanced-settings.md
@@ -21,8 +21,8 @@ description: "Security & Compliance PowerShell advanced settings for Microsoft P
 
 This article contains the [Security & Compliance PowerShell](/powershell/exchange/office-365-scc/office-365-scc-powershell) advanced settings that are supported by [Microsoft Purview Information Protection client](/purview/information-protection-client) when you use the following cmdlets:
 
-- [New-Label](/powershell/module/exchange/new-label) or [Set-Label](/powershell/module/exchange/set-label)
-- [New-LabelPolicy](/powershell/module/exchange/new-labelpolicy) or [Set-LabelPolicy](/powershell/module/exchange/set-labelpolicy)
+- [New-Label](/powershell/module/exchangepowershell/new-label) or [Set-Label](/powershell/module/exchangepowershell/set-label)
+- [New-LabelPolicy](/powershell/module/exchangepowershell/new-labelpolicy) or [Set-LabelPolicy](/powershell/module/exchangepowershell/set-labelpolicy)
 
 The advanced settings that are supported by sensitivity labels built into Microsoft 365 apps and services are included on the cmdlet page itself. You might also find useful [PowerShell tips for specifying the advanced settings](/purview/create-sensitivity-labels#powershell-tips-for-specifying-the-advanced-settings).
 
diff --git a/exchange/docs-conceptual/cmdlet-property-sets.md b/exchange/docs-conceptual/cmdlet-property-sets.md
index bbd2cf89d9..af41ff82fd 100644
--- a/exchange/docs-conceptual/cmdlet-property-sets.md
+++ b/exchange/docs-conceptual/cmdlet-property-sets.md
@@ -49,8 +49,8 @@ The available property sets for the **Get-EXOCasMailbox** cmdlet and the propert
 
 For more information, see:
 
-- [Get-EXOCASMailbox](/powershell/module/exchange/get-exocasmailbox)
-- [Get-CASMailbox](/powershell/module/exchange/get-casmailbox)
+- [Get-EXOCASMailbox](/powershell/module/exchangepowershell/get-exocasmailbox)
+- [Get-CASMailbox](/powershell/module/exchangepowershell/get-casmailbox)
 
 ## Get-EXOMailbox property sets
 
@@ -86,8 +86,8 @@ The available property sets for the **Get-EXOMailbox** cmdlet and the properties
 
 For more information, see:
 
-- [Get-EXOMailbox](/powershell/module/exchange/get-exomailbox)
-- [Get-Mailbox](/powershell/module/exchange/get-mailbox)
+- [Get-EXOMailbox](/powershell/module/exchangepowershell/get-exomailbox)
+- [Get-Mailbox](/powershell/module/exchangepowershell/get-mailbox)
 
 ## Get-EXOMailboxStatistics property sets
 
@@ -100,8 +100,8 @@ The available property sets for the **Get-EXOMailboxStatistics** cmdlet and the
 
 For more information, see:
 
-- [Get-EXOMailboxStatistics](/powershell/module/exchange/get-exomailboxstatistics)
-- [Get-MailboxStatistics](/powershell/module/exchange/get-mailboxstatistics)
+- [Get-EXOMailboxStatistics](/powershell/module/exchangepowershell/get-exomailboxstatistics)
+- [Get-MailboxStatistics](/powershell/module/exchangepowershell/get-mailboxstatistics)
 
 ## Get-EXORecipient property sets
 
@@ -121,5 +121,5 @@ The available property sets for the **Get-EXORecipient** cmdlet and the properti
 
 For more information, see:
 
-- [Get-EXORecipient](/powershell/module/exchange/get-exorecipient)
-- [Get-Recipient](/powershell/module/exchange/get-recipient)
+- [Get-EXORecipient](/powershell/module/exchangepowershell/get-exorecipient)
+- [Get-Recipient](/powershell/module/exchangepowershell/get-recipient)
diff --git a/exchange/docs-conceptual/connect-exo-powershell-managed-identity.md b/exchange/docs-conceptual/connect-exo-powershell-managed-identity.md
index 2f484fd336..5266f57d04 100644
--- a/exchange/docs-conceptual/connect-exo-powershell-managed-identity.md
+++ b/exchange/docs-conceptual/connect-exo-powershell-managed-identity.md
@@ -28,10 +28,10 @@ The rest of this article explains how to connect using managed identity, and the
 > [!NOTE]
 > In Exchange Online PowerShell, you can't use the procedures in this article with the following Microsoft 365 Group cmdlets:
 >
-> - [New-UnifiedGroup](/powershell/module/exchange/new-unifiedgroup)
-> - [Remove-UnifiedGroup](/powershell/module/exchange/remove-unifiedgroup)
-> - [Remove-UnifiedGroupLinks](/powershell/module/exchange/remove-unifiedgrouplinks)
-> - [Add-UnifiedGroupLinks](/powershell/module/exchange/add-unifiedgrouplinks)
+> - [New-UnifiedGroup](/powershell/module/exchangepowershell/new-unifiedgroup)
+> - [Remove-UnifiedGroup](/powershell/module/exchangepowershell/remove-unifiedgroup)
+> - [Remove-UnifiedGroupLinks](/powershell/module/exchangepowershell/remove-unifiedgrouplinks)
+> - [Add-UnifiedGroupLinks](/powershell/module/exchangepowershell/add-unifiedgrouplinks)
 >
 > You can use Microsoft Graph to replace most of the functionality from those cmdlets. For more information, see [Working with groups in Microsoft Graph](/graph/api/resources/groups-overview).
 >
diff --git a/exchange/docs-conceptual/connect-to-exchange-online-powershell.md b/exchange/docs-conceptual/connect-to-exchange-online-powershell.md
index b3409d0e1c..e36b948699 100644
--- a/exchange/docs-conceptual/connect-to-exchange-online-powershell.md
+++ b/exchange/docs-conceptual/connect-to-exchange-online-powershell.md
@@ -61,7 +61,7 @@ The command that you need to run uses the following syntax:
 Connect-ExchangeOnline [-UserPrincipalName <UPN>] [-ExchangeEnvironmentName <Value>] [-ShowBanner:$false] [-LoadCmdletHelp] [-DelegatedOrganization <String>] [-SkipLoadingFormatData] [-DisableWAM]
    ```
 
-For detailed syntax and parameter information, see [Connect-ExchangeOnline](/powershell/module/exchange/connect-exchangeonline).
+For detailed syntax and parameter information, see [Connect-ExchangeOnline](/powershell/module/exchangepowershell/connect-exchangeonline).
 
 - _\<UPN\>_ is your account in user principal name format (for example, `navin@contoso.onmicrosoft.com`).
 
diff --git a/exchange/docs-conceptual/connect-to-scc-powershell.md b/exchange/docs-conceptual/connect-to-scc-powershell.md
index 77365e508f..dfa2726eb2 100644
--- a/exchange/docs-conceptual/connect-to-scc-powershell.md
+++ b/exchange/docs-conceptual/connect-to-scc-powershell.md
@@ -54,7 +54,7 @@ The command that you need to run uses the following syntax:
 Connect-IPPSSession -UserPrincipalName <UPN> [-ConnectionUri <URL>] [-AzureADAuthorizationEndpointUri <URL>] [-DelegatedOrganization <String>] [-PSSessionOption $ProxyOptions]
 ```
 
-For detailed syntax and parameter information, see [Connect-IPPSSession](/powershell/module/exchange/connect-ippssession).
+For detailed syntax and parameter information, see [Connect-IPPSSession](/powershell/module/exchangepowershell/connect-ippssession).
 
 - _\<UPN\>_ is your account in user principal name format (for example, `navin@contoso.onmicrosoft.com`).
 
diff --git a/exchange/docs-conceptual/control-remote-powershell-access-to-exchange-servers.md b/exchange/docs-conceptual/control-remote-powershell-access-to-exchange-servers.md
index e852dcea18..da394b256c 100644
--- a/exchange/docs-conceptual/control-remote-powershell-access-to-exchange-servers.md
+++ b/exchange/docs-conceptual/control-remote-powershell-access-to-exchange-servers.md
@@ -36,7 +36,7 @@ For additional management tasks related to remote PowerShell, see [Connect to Ex
 
 - You need to be assigned permissions before you can perform this procedure or procedures. To see what permissions you need, see the "Remote PowerShell" entry in the [Exchange infrastructure and PowerShell permissions](/Exchange/permissions/feature-permissions/infrastructure-permissions) article.
 
-- If you're using non-Microsoft tools to customize email addresses of users, you need to disable email address policies on the affected users before you do the procedures in this article. If you don't, the **Set-User** commands change the email addresses of the users to match the applicable email address policy. To disable email address policies on users, set the value of the EmailAddressPolicyEnabled parameter to $false on the [Set-Mailbox](/powershell/module/exchange/set-mailbox) cmdlet.
+- If you're using non-Microsoft tools to customize email addresses of users, you need to disable email address policies on the affected users before you do the procedures in this article. If you don't, the **Set-User** commands change the email addresses of the users to match the applicable email address policy. To disable email address policies on users, set the value of the EmailAddressPolicyEnabled parameter to $false on the [Set-Mailbox](/powershell/module/exchangepowershell/set-mailbox) cmdlet.
 
 > [!TIP]
 > Having problems? Ask for help in the [Exchange Server](https://go.microsoft.com/fwlink/p/?linkId=60612) forums.
diff --git a/exchange/docs-conceptual/exchange-online-powershell-v2.md b/exchange/docs-conceptual/exchange-online-powershell-v2.md
index bb1f6d26ca..f149901408 100644
--- a/exchange/docs-conceptual/exchange-online-powershell-v2.md
+++ b/exchange/docs-conceptual/exchange-online-powershell-v2.md
@@ -91,7 +91,7 @@ A few cmdlets in Exchange Online PowerShell are updated with the experimental _U
   - **Set-MailboxRegionalConfiguration**
   - **Set-UserPhoto**
 
-- Use the [Get-ConnectionInformation](/powershell/module/exchange/get-connectioninformation) cmdlet to get information about connections to Exchange Online PowerShell and Security & Compliance PowerShell. This cmdlet is required because the [Get-PSSession](/powershell/module/microsoft.powershell.core/get-pssession) cmdlet in Windows PowerShell doesn't return information for REST API connections.
+- Use the [Get-ConnectionInformation](/powershell/module/exchangepowershell/get-connectioninformation) cmdlet to get information about connections to Exchange Online PowerShell and Security & Compliance PowerShell. This cmdlet is required because the [Get-PSSession](/powershell/module/microsoft.powershell.core/get-pssession) cmdlet in Windows PowerShell doesn't return information for REST API connections.
 
   Scenarios where you can use **Get-ConnectionInformation** are described in the following table:
 
@@ -143,15 +143,15 @@ The EXO module contains nine exclusive **Get-EXO\*** cmdlets that are optimized
 
 |EXO module cmdlet|Older related cmdlet|
 |---|---|
-|[Get-EXOMailbox](/powershell/module/exchange/get-exomailbox)|[Get-Mailbox](/powershell/module/exchange/get-mailbox)|
-|[Get-EXORecipient](/powershell/module/exchange/get-exorecipient)|[Get-Recipient](/powershell/module/exchange/get-recipient)|
-|[Get-EXOCasMailbox](/powershell/module/exchange/get-exocasmailbox)|[Get-CASMailbox](/powershell/module/exchange/get-casmailbox)|
-|[Get-EXOMailboxPermission](/powershell/module/exchange/get-exomailboxPermission)|[Get-MailboxPermission](/powershell/module/exchange/get-mailboxpermission)|
-|[Get-EXORecipientPermission](/powershell/module/exchange/get-exorecipientpermission)|[Get-RecipientPermission](/powershell/module/exchange/get-recipientpermission)|
-|[Get-EXOMailboxStatistics](/powershell/module/exchange/get-exomailboxstatistics)|[Get-MailboxStatistics](/powershell/module/exchange/get-mailboxstatistics)|
-|[Get-EXOMailboxFolderStatistics](/powershell/module/exchange/get-exomailboxfolderstatistics)|[Get-MailboxFolderStatistics](/powershell/module/exchange/get-mailboxfolderstatistics)|
-|[Get-EXOMailboxFolderPermission](/powershell/module/exchange/get-exomailboxfolderpermission)|[Get-MailboxFolderPermission](/powershell/module/exchange/get-mailboxfolderpermission)|
-|[Get-EXOMobileDeviceStatistics](/powershell/module/exchange/get-exomobiledevicestatistics)|[Get-MobileDeviceStatistics](/powershell/module/exchange/get-mobiledevicestatistics)|
+|[Get-EXOMailbox](/powershell/module/exchangepowershell/get-exomailbox)|[Get-Mailbox](/powershell/module/exchangepowershell/get-mailbox)|
+|[Get-EXORecipient](/powershell/module/exchangepowershell/get-exorecipient)|[Get-Recipient](/powershell/module/exchangepowershell/get-recipient)|
+|[Get-EXOCasMailbox](/powershell/module/exchangepowershell/get-exocasmailbox)|[Get-CASMailbox](/powershell/module/exchangepowershell/get-casmailbox)|
+|[Get-EXOMailboxPermission](/powershell/module/exchangepowershell/get-exomailboxPermission)|[Get-MailboxPermission](/powershell/module/exchangepowershell/get-mailboxpermission)|
+|[Get-EXORecipientPermission](/powershell/module/exchangepowershell/get-exorecipientpermission)|[Get-RecipientPermission](/powershell/module/exchangepowershell/get-recipientpermission)|
+|[Get-EXOMailboxStatistics](/powershell/module/exchangepowershell/get-exomailboxstatistics)|[Get-MailboxStatistics](/powershell/module/exchangepowershell/get-mailboxstatistics)|
+|[Get-EXOMailboxFolderStatistics](/powershell/module/exchangepowershell/get-exomailboxfolderstatistics)|[Get-MailboxFolderStatistics](/powershell/module/exchangepowershell/get-mailboxfolderstatistics)|
+|[Get-EXOMailboxFolderPermission](/powershell/module/exchangepowershell/get-exomailboxfolderpermission)|[Get-MailboxFolderPermission](/powershell/module/exchangepowershell/get-mailboxfolderpermission)|
+|[Get-EXOMobileDeviceStatistics](/powershell/module/exchangepowershell/get-exomobiledevicestatistics)|[Get-MobileDeviceStatistics](/powershell/module/exchangepowershell/get-mobiledevicestatistics)|
 
 > [!TIP]
 > If you open multiple connections to Exchange Online PowerShell in the same window, the **Get-EXO\*** cmdlets are always associated with the last (most recent) Exchange Online PowerShell connection. Run the following command to find the REST API session where the **Get-EXO\*** cmdlets are run: `Get-ConnectionInformation | Where-Object {$_.ConnectionUsedForInbuiltCmdlets -eq $true}`.
@@ -160,10 +160,10 @@ The connection-related cmdlets in the module are listed in the following table:
 
 |EXO module cmdlet|Older related cmdlet|Comments|
 |---|---|---|
-|[Connect-ExchangeOnline](/powershell/module/exchange/connect-exchangeonline)|**Connect-EXOPSSession** in V1 of the module <br/> or <br/> [New-PSSession](/powershell/module/microsoft.powershell.core/new-pssession)||
-|[Connect-IPPSSession](/powershell/module/exchange/connect-ippssession)|**Connect-IPPSSession** in V1 of the module||
-|[Disconnect-ExchangeOnline](/powershell/module/exchange/disconnect-exchangeonline)|[Remove-PSSession](/powershell/module/microsoft.powershell.core/remove-pssession)||
-|[Get-ConnectionInformation](/powershell/module/exchange/get-connectioninformation)|[Get-PSSession](/powershell/module/microsoft.powershell.core/get-pssession)|Available in v3.0.0 or later.|
+|[Connect-ExchangeOnline](/powershell/module/exchangepowershell/connect-exchangeonline)|**Connect-EXOPSSession** in V1 of the module <br/> or <br/> [New-PSSession](/powershell/module/microsoft.powershell.core/new-pssession)||
+|[Connect-IPPSSession](/powershell/module/exchangepowershell/connect-ippssession)|**Connect-IPPSSession** in V1 of the module||
+|[Disconnect-ExchangeOnline](/powershell/module/exchangepowershell/disconnect-exchangeonline)|[Remove-PSSession](/powershell/module/microsoft.powershell.core/remove-pssession)||
+|[Get-ConnectionInformation](/powershell/module/exchangepowershell/get-connectioninformation)|[Get-PSSession](/powershell/module/microsoft.powershell.core/get-pssession)|Available in v3.0.0 or later.|
 
 > [!TIP]
 > Frequent use of the **Connect-ExchangeOnline** and **Disconnect-ExchangeOnline** cmdlets in a single PowerShell session or script might lead to a memory leak. The best way to avoid this issue is to use the _CommandName_ parameter on the **Connect-ExchangeOnline** cmdlet to limit the cmdlets that are used in the session.
@@ -172,25 +172,25 @@ Miscellaneous Exchange Online feature cmdlets that happen to be in the module ar
 
 |Cmdlet|Comments|
 |---|---|
-|[Get-DefaultTenantBriefingConfig](/powershell/module/exchange/get-defaulttenantbriefingconfig)|Available in v3.2.0 or later.|
-|[Set-DefaultTenantBriefingConfig](/powershell/module/exchange/set-defaulttenantbriefingconfig)|Available in v3.2.0 or later.|
-|[Get-DefaultTenantMyAnalyticsFeatureConfig](/powershell/module/exchange/get-defaulttenantmyanalyticsfeatureconfig)|Available in v3.2.0 or later.|
-|[Set-DefaultTenantMyAnalyticsFeatureConfig](/powershell/module/exchange/set-defaulttenantmyanalyticsfeatureconfig)|Available in v3.2.0 or later.|
-|[Get-MyAnalyticsFeatureConfig](/powershell/module/exchange/get-myanalyticsfeatureconfig)|Available in v2.0.4 or later.|
-|[Set-MyAnalyticsFeatureConfig](/powershell/module/exchange/set-myanalyticsfeatureconfig)|Available in v2.0.4 or later.|
-|[Get-UserBriefingConfig](/powershell/module/exchange/get-userbriefingconfig)|Replaced by [Get-MyAnalyticsFeatureConfig](/powershell/module/exchange/get-myanalyticsfeatureconfig).|
-|[Set-UserBriefingConfig](/powershell/module/exchange/set-userbriefingconfig)|Replaced by [Set-MyAnalyticsFeatureConfig](/powershell/module/exchange/set-myanalyticsfeatureconfig).|
-|[Get-VivaInsightsSettings](/powershell/module/exchange/get-vivainsightssettings)|Available in v2.0.5 or later.|
-|[Set-VivaInsightsSettings](/powershell/module/exchange/set-vivainsightssettings)|Available in v2.0.5 or later.|
-|[Get-VivaModuleFeature](/powershell/module/exchange/get-vivamodulefeature)|Available in v3.2.0 or later.|
-|[Get-VivaModuleFeatureEnablement](/powershell/module/exchange/get-vivamodulefeatureenablement)|Available in v3.2.0 or later.|
-|[Add-VivaModuleFeaturePolicy](/powershell/module/exchange/add-vivamodulefeaturepolicy)|Available in v3.2.0 or later.|
-|[Get-VivaModuleFeaturePolicy](/powershell/module/exchange/get-vivamodulefeaturepolicy)|Available in v3.2.0 or later.|
-|[Remove-VivaModuleFeaturePolicy](/powershell/module/exchange/remove-vivamodulefeaturepolicy)|Available in v3.2.0 or later.|
-|[Update-VivaModuleFeaturePolicy](/powershell/module/exchange/update-vivamodulefeaturepolicy)|Available in v3.2.0 or later.|
-|[Add-VivaOrgInsightsDelegatedRole](/powershell/module/exchange/add-vivaorginsightsdelegatedrole)|Available in v3.7.0-Preview1 or later.|
-|[Get-VivaOrgInsightsDelegatedRole](/powershell/module/exchange/get-vivaorginsightsdelegatedrole)|Available in v3.7.0-Preview1 or later.|
-|[Remove-VivaOrgInsightsDelegatedRole](/powershell/module/exchange/remove-vivaorginsightsdelegatedrole)|Available in v3.7.0-Preview1 or later.|
+|[Get-DefaultTenantBriefingConfig](/powershell/module/exchangepowershell/get-defaulttenantbriefingconfig)|Available in v3.2.0 or later.|
+|[Set-DefaultTenantBriefingConfig](/powershell/module/exchangepowershell/set-defaulttenantbriefingconfig)|Available in v3.2.0 or later.|
+|[Get-DefaultTenantMyAnalyticsFeatureConfig](/powershell/module/exchangepowershell/get-defaulttenantmyanalyticsfeatureconfig)|Available in v3.2.0 or later.|
+|[Set-DefaultTenantMyAnalyticsFeatureConfig](/powershell/module/exchangepowershell/set-defaulttenantmyanalyticsfeatureconfig)|Available in v3.2.0 or later.|
+|[Get-MyAnalyticsFeatureConfig](/powershell/module/exchangepowershell/get-myanalyticsfeatureconfig)|Available in v2.0.4 or later.|
+|[Set-MyAnalyticsFeatureConfig](/powershell/module/exchangepowershell/set-myanalyticsfeatureconfig)|Available in v2.0.4 or later.|
+|[Get-UserBriefingConfig](/powershell/module/exchangepowershell/get-userbriefingconfig)|Replaced by [Get-MyAnalyticsFeatureConfig](/powershell/module/exchangepowershell/get-myanalyticsfeatureconfig).|
+|[Set-UserBriefingConfig](/powershell/module/exchangepowershell/set-userbriefingconfig)|Replaced by [Set-MyAnalyticsFeatureConfig](/powershell/module/exchangepowershell/set-myanalyticsfeatureconfig).|
+|[Get-VivaInsightsSettings](/powershell/module/exchangepowershell/get-vivainsightssettings)|Available in v2.0.5 or later.|
+|[Set-VivaInsightsSettings](/powershell/module/exchangepowershell/set-vivainsightssettings)|Available in v2.0.5 or later.|
+|[Get-VivaModuleFeature](/powershell/module/exchangepowershell/get-vivamodulefeature)|Available in v3.2.0 or later.|
+|[Get-VivaModuleFeatureEnablement](/powershell/module/exchangepowershell/get-vivamodulefeatureenablement)|Available in v3.2.0 or later.|
+|[Add-VivaModuleFeaturePolicy](/powershell/module/exchangepowershell/add-vivamodulefeaturepolicy)|Available in v3.2.0 or later.|
+|[Get-VivaModuleFeaturePolicy](/powershell/module/exchangepowershell/get-vivamodulefeaturepolicy)|Available in v3.2.0 or later.|
+|[Remove-VivaModuleFeaturePolicy](/powershell/module/exchangepowershell/remove-vivamodulefeaturepolicy)|Available in v3.2.0 or later.|
+|[Update-VivaModuleFeaturePolicy](/powershell/module/exchangepowershell/update-vivamodulefeaturepolicy)|Available in v3.2.0 or later.|
+|[Add-VivaOrgInsightsDelegatedRole](/powershell/module/exchangepowershell/add-vivaorginsightsdelegatedrole)|Available in v3.7.0-Preview1 or later.|
+|[Get-VivaOrgInsightsDelegatedRole](/powershell/module/exchangepowershell/get-vivaorginsightsdelegatedrole)|Available in v3.7.0-Preview1 or later.|
+|[Remove-VivaOrgInsightsDelegatedRole](/powershell/module/exchangepowershell/remove-vivaorginsightsdelegatedrole)|Available in v3.7.0-Preview1 or later.|
 
 ## Install and maintain the Exchange Online PowerShell module
 
@@ -547,10 +547,10 @@ The **Get-EXO\*** cmdlets in the module contain categorized output properties. I
 
 The biggest and most used **Get-EXO\*** cmdlets use property sets:
 
-- [Get-EXOCasMailbox](/powershell/module/exchange/get-exocasmailbox)
-- [Get-EXOMailbox](/powershell/module/exchange/get-exomailbox)
-- [Get-EXOMailboxStatistics](/powershell/module/exchange/get-exomailboxstatistics)
-- [Get-EXORecipient](/powershell/module/exchange/get-exorecipient)
+- [Get-EXOCasMailbox](/powershell/module/exchangepowershell/get-exocasmailbox)
+- [Get-EXOMailbox](/powershell/module/exchangepowershell/get-exomailbox)
+- [Get-EXOMailboxStatistics](/powershell/module/exchangepowershell/get-exomailboxstatistics)
+- [Get-EXORecipient](/powershell/module/exchangepowershell/get-exorecipient)
 
 In those cmdlets, the following parameters control property sets:
 
@@ -668,7 +668,7 @@ Unless otherwise noted, the current release of the Exchange Online PowerShell mo
 
 - Features already described in the [REST API connections in the EXO V3 module](#rest-api-connections-in-the-exo-v3-module) section:
   - [Certificate based authentication](app-only-auth-powershell-v2.md) for Security & Compliance PowerShell (version 2.0.6-Preview5 or later).
-  - The [Get-ConnectionInformation](/powershell/module/exchange/get-connectioninformation) cmdlet for REST-based connections (version 2.0.6-Preview7 or later).
+  - The [Get-ConnectionInformation](/powershell/module/exchangepowershell/get-connectioninformation) cmdlet for REST-based connections (version 2.0.6-Preview7 or later).
   - The _SkipLoadingFormatData_ switch on the **Connect-ExchangeOnline** cmdlet for REST-based connections (version 2.0.6-Preview8 or later).
 - The _DelegatedOrganization_ parameter works in the **Connect-IPPSSession** cmdlet as long as you also use the _AzureADAuthorizationEndpointUri_ parameter in the command.
 - Certain cmdlets that prompted for confirmation in specific scenarios no longer do so. By default, the cmdlet runs to completion.
@@ -703,7 +703,7 @@ Unless otherwise noted, the current release of the Exchange Online PowerShell mo
   - Remote in the Azure Key Value (the _Certificate_) parameter. This option enhances security by fetching the certificate only at runtime.
   - Local in the CurrentUser or LocalMachine certificate store (the _CertificateThumbprint_ parameter).
   - Local in an exported certificate file (the _CertificateFilePath_ and _CertificatePassword_ parameters).
-  For more information, see the parameter descriptions in [Connect-ExchangeOnline](/powershell/module/exchange/connect-exchangeonline) and [App-only authentication for unattended scripts in the Exchange Online PowerShell module](app-only-auth-powershell-v2.md).
+  For more information, see the parameter descriptions in [Connect-ExchangeOnline](/powershell/module/exchangepowershell/connect-exchangeonline) and [App-only authentication for unattended scripts in the Exchange Online PowerShell module](app-only-auth-powershell-v2.md).
 - Connect to Exchange Online PowerShell and Security & Compliance PowerShell simultaneously in a single PowerShell window.
 - The new _CommandName_ parameter allows you to specify and restrict the Exchange Online PowerShell cmdlets that are imported in a session. This option reduces the memory footprint for high usage PowerShell applications.
 - **Get-EXOMailboxFolderPermission** now supports ExternalDirectoryObjectID in the _Identity_ parameter.
diff --git a/exchange/docs-conceptual/filter-properties.md b/exchange/docs-conceptual/filter-properties.md
index acd6c6bdeb..c351b83884 100644
--- a/exchange/docs-conceptual/filter-properties.md
+++ b/exchange/docs-conceptual/filter-properties.md
@@ -17,22 +17,22 @@ description: "Learn about the filterable properties for the Filter parameter in
 
 You use the _Filter_ parameter to create OPATH filters based on the properties of user and group objects in the Exchange Management Shell (Exchange Server PowerShell) and in Exchange Online PowerShell. The _Filter_ parameter is available on these recipient cmdlets:
 
-- [Get-CASMailbox](/powershell/module/exchange/get-casmailbox)
-- [Get-Contact](/powershell/module/exchange/get-contact)
-- [Get-DistributionGroup](/powershell/module/exchange/get-distributiongroup)
-- [Get-DynamicDistributionGroup](/powershell/module/exchange/get-dynamicdistributiongroup)
-- [Get-Group](/powershell/module/exchange/get-group)
-- [Get-LinkedUser](/powershell/module/exchange/get-linkeduser)
-- [Get-Mailbox](/powershell/module/exchange/get-mailbox)
-- [Get-MailContact](/powershell/module/exchange/get-mailcontact)
-- [Get-MailPublicFolder](/powershell/module/exchange/get-mailpublicfolder)
-- [Get-MailUser](/powershell/module/exchange/get-mailuser)
-- [Get-Recipient](/powershell/module/exchange/get-recipient)
-- [Get-RemoteMailbox](/powershell/module/exchange/get-remotemailbox)
-- [Get-SecurityPrincipal](/powershell/module/exchange/get-securityprincipal)
-- [Get-UMMailbox](/powershell/module/exchange/get-ummailbox)
-- [Get-User](/powershell/module/exchange/get-user)
-- [Get-UnifiedGroup](/powershell/module/exchange/get-unifiedgroup)
+- [Get-CASMailbox](/powershell/module/exchangepowershell/get-casmailbox)
+- [Get-Contact](/powershell/module/exchangepowershell/get-contact)
+- [Get-DistributionGroup](/powershell/module/exchangepowershell/get-distributiongroup)
+- [Get-DynamicDistributionGroup](/powershell/module/exchangepowershell/get-dynamicdistributiongroup)
+- [Get-Group](/powershell/module/exchangepowershell/get-group)
+- [Get-LinkedUser](/powershell/module/exchangepowershell/get-linkeduser)
+- [Get-Mailbox](/powershell/module/exchangepowershell/get-mailbox)
+- [Get-MailContact](/powershell/module/exchangepowershell/get-mailcontact)
+- [Get-MailPublicFolder](/powershell/module/exchangepowershell/get-mailpublicfolder)
+- [Get-MailUser](/powershell/module/exchangepowershell/get-mailuser)
+- [Get-Recipient](/powershell/module/exchangepowershell/get-recipient)
+- [Get-RemoteMailbox](/powershell/module/exchangepowershell/get-remotemailbox)
+- [Get-SecurityPrincipal](/powershell/module/exchangepowershell/get-securityprincipal)
+- [Get-UMMailbox](/powershell/module/exchangepowershell/get-ummailbox)
+- [Get-User](/powershell/module/exchangepowershell/get-user)
+- [Get-UnifiedGroup](/powershell/module/exchangepowershell/get-unifiedgroup)
 
 For more information about _recipient_ filters in Exchange PowerShell, see [Recipient filters in Exchange PowerShell commands](recipient-filters.md).
 
@@ -1052,7 +1052,7 @@ You can find the names of migration batches by running the **Get-MigrationBatch*
 
 |LDAP display name|Available on cmdlets|Value|
 |---|---|---|
-|_msExchMailboxMoveFlags_|**Get-Mailbox** <br/> **Get-MailUser** <br/> **Get-Recipient** <br/> **Get-RemoteMailbox**|For valid values, see the description of the _Flags_ parameter in [Get-MoveRequest](/powershell/module/exchange/get-moverequest#-flags).|
+|_msExchMailboxMoveFlags_|**Get-Mailbox** <br/> **Get-MailUser** <br/> **Get-Recipient** <br/> **Get-RemoteMailbox**|For valid values, see the description of the _Flags_ parameter in [Get-MoveRequest](/powershell/module/exchangepowershell/get-moverequest#-flags).|
 
 For example, `Get-Mailbox -Filter "MailboxMoveFlags -ne 'None'"`.
 
@@ -1082,7 +1082,7 @@ You can find the distinguished names of mailbox databases by running this comman
 
 |LDAP display name|Available on cmdlets|Value|
 |---|---|---|
-|_msExchMailboxMoveStatus_|**Get-Mailbox** <br/> **Get-MailUser** <br/> **Get-Recipient** <br/> **Get-RemoteMailbox**|For valid values, see the description of the _MoveStatus_ parameter in [Get-MoveRequest](/powershell/module/exchange/get-moverequest#-movestatus).|
+|_msExchMailboxMoveStatus_|**Get-Mailbox** <br/> **Get-MailUser** <br/> **Get-Recipient** <br/> **Get-RemoteMailbox**|For valid values, see the description of the _MoveStatus_ parameter in [Get-MoveRequest](/powershell/module/exchangepowershell/get-moverequest#-movestatus).|
 
 For example, `Get-Mailbox -Filter "MailboxMoveStatus -eq 'Completed'"`.
 
@@ -1504,7 +1504,7 @@ For example, `Get-User -Filter "PostOfficeBox -like '555*'"`.
 |---|---|---|
 |_msExchPreviousRecipientTypeDetails_|**Get-LinkedUser** <br/> **Get-User**|String or `$null`|
 
-For valid values, see the description of the _RecipientTypeDetails_ parameter in [Get-Recipient](/powershell/module/exchange/get-recipient#-recipienttypedetails).
+For valid values, see the description of the _RecipientTypeDetails_ parameter in [Get-Recipient](/powershell/module/exchangepowershell/get-recipient#-recipienttypedetails).
 
 For example, `Get-User -Filter 'PreviousRecipientTypeDetails -ne $null'`.
 
@@ -1602,7 +1602,7 @@ For example, `Get-Recipient -Filter "RecipientType -eq 'MailContact'"`.
 |---|---|---|
 |n/a|**Get-Contact** <br/> **Get-DistributionGroup** <br/> **Get-DynamicDistributionGroup** <br/> **Get-Group** <br/> **Get-LinkedUser** <br/> **Get-Mailbox** <br/> **Get-MailContact** <br/> **Get-MailPublicFolder** <br/> **Get-MailUser** <br/> **Get-Recipient** <br/> **Get-RemoteMailbox** <br/> **Get-SecurityPrincipal** <br/> **Get-User** <br/> **Get-UnifiedGroup**|String|
 
-For valid values, see the description of the _RecipientTypeDetails_ parameter in [Get-Recipient](/powershell/module/exchange/get-recipient#-recipienttypedetails).
+For valid values, see the description of the _RecipientTypeDetails_ parameter in [Get-Recipient](/powershell/module/exchangepowershell/get-recipient#-recipienttypedetails).
 
 For example, `Get-Recipient -Filter "RecipientTypeDetails -eq 'SharedMailbox'"`.
 
diff --git a/exchange/docs-conceptual/filters-v2.md b/exchange/docs-conceptual/filters-v2.md
index aae21efdc2..85f538fcdc 100644
--- a/exchange/docs-conceptual/filters-v2.md
+++ b/exchange/docs-conceptual/filters-v2.md
@@ -40,9 +40,9 @@ The **Get-EXO\*** cmdlets in the module support the majority of [filterable prop
 
 |Cmdlet|Unsupported filterable property|LDAP Display Name|
 |---|---|---|
-|[Get-EXOCASMailbox](/powershell/module/exchange/get-exocasmailbox)|MemberOfGroup <br><br> ExternalDirectoryObjectId|memberOf <br><br> msExchExternalDirectoryObjectId|
-|[Get-EXOMailbox](/powershell/module/exchange/get-exomailbox)|DeletedItemFlags <br><br> LanguagesRaw <p> MasterAccountSid <p> MemberOfGroup <p> RequireAllSendersAreAuthenticated <p> SCLDeleteThresholdInt <p> SCLJunkThresholdInt <p> SCLQuarantineThresholdInt <p> SCLRejectThresholdInt|deletedItemFlags <br><br> msExchUserCulture <p> msExchMasterAccountSid <p> memberOf <p> msExchRequireAuthToSendTo <p> msExchMessageHygieneSCLDeleteThreshold <p> msExchMessageHygieneSCLJunkThreshold <p> msExchMessageHygieneSCLQuarantineThreshold <p> msExchMessageHygieneSCLRejectThreshold|
-|[Get-EXORecipient](/powershell/module/exchange/get-exorecipient)|CountryCode <br><br> ExternalDirectoryObjectId <p> MasterAccountSid <p> MemberOfGroup <p> Members|countryCode <br><br> msExchExternalDirectoryObjectId <p> msExchMasterAccountSid <p> memberOf <p> member|
+|[Get-EXOCASMailbox](/powershell/module/exchangepowershell/get-exocasmailbox)|MemberOfGroup <br><br> ExternalDirectoryObjectId|memberOf <br><br> msExchExternalDirectoryObjectId|
+|[Get-EXOMailbox](/powershell/module/exchangepowershell/get-exomailbox)|DeletedItemFlags <br><br> LanguagesRaw <p> MasterAccountSid <p> MemberOfGroup <p> RequireAllSendersAreAuthenticated <p> SCLDeleteThresholdInt <p> SCLJunkThresholdInt <p> SCLQuarantineThresholdInt <p> SCLRejectThresholdInt|deletedItemFlags <br><br> msExchUserCulture <p> msExchMasterAccountSid <p> memberOf <p> msExchRequireAuthToSendTo <p> msExchMessageHygieneSCLDeleteThreshold <p> msExchMessageHygieneSCLJunkThreshold <p> msExchMessageHygieneSCLQuarantineThreshold <p> msExchMessageHygieneSCLRejectThreshold|
+|[Get-EXORecipient](/powershell/module/exchangepowershell/get-exorecipient)|CountryCode <br><br> ExternalDirectoryObjectId <p> MasterAccountSid <p> MemberOfGroup <p> Members|countryCode <br><br> msExchExternalDirectoryObjectId <p> msExchMasterAccountSid <p> memberOf <p> member|
 
 ## Supported operators
 
diff --git a/exchange/docs-conceptual/recipient-filters.md b/exchange/docs-conceptual/recipient-filters.md
index dc3ea8bf77..bf995e41b3 100644
--- a/exchange/docs-conceptual/recipient-filters.md
+++ b/exchange/docs-conceptual/recipient-filters.md
@@ -42,17 +42,17 @@ The following parameters are considered precanned filters:
 
 Precanned filters are available on the following cmdlets:
 
-- [New-DynamicDistributionGroup](/powershell/module/exchange/new-dynamicdistributiongroup)
-- [Set-DynamicDistributionGroup](/powershell/module/exchange/set-dynamicdistributiongroup)
+- [New-DynamicDistributionGroup](/powershell/module/exchangepowershell/new-dynamicdistributiongroup)
+- [Set-DynamicDistributionGroup](/powershell/module/exchangepowershell/set-dynamicdistributiongroup)
 
-- [New-EmailAddressPolicy](/powershell/module/exchange/new-emailaddresspolicy)
-- [Set-EmailAddressPolicy](/powershell/module/exchange/set-emailaddresspolicy)
+- [New-EmailAddressPolicy](/powershell/module/exchangepowershell/new-emailaddresspolicy)
+- [Set-EmailAddressPolicy](/powershell/module/exchangepowershell/set-emailaddresspolicy)
 
-- [New-AddressList](/powershell/module/exchange/new-addresslist)
-- [Set-AddressList](/powershell/module/exchange/set-addresslist)
+- [New-AddressList](/powershell/module/exchangepowershell/new-addresslist)
+- [Set-AddressList](/powershell/module/exchangepowershell/set-addresslist)
 
-- [New-GlobalAddressList](/powershell/module/exchange/new-globaladdresslist)
-- [Set-GlobalAddressList](/powershell/module/exchange/set-globaladdresslist)
+- [New-GlobalAddressList](/powershell/module/exchangepowershell/new-globaladdresslist)
+- [Set-GlobalAddressList](/powershell/module/exchangepowershell/set-globaladdresslist)
 
 ### Precanned filter example
 
@@ -88,17 +88,17 @@ Get-DynamicDistributionGroup -Identity "Contoso Finance" | Format-List Recipient
 
 If precanned filters don't meet your needs, you can create custom filters by using the _RecipientFilter_ parameter. This parameter is available on the following cmdlets:
 
-- [New-DynamicDistributionGroup](/powershell/module/exchange/new-dynamicdistributiongroup)
-- [Set-DynamicDistributionGroup](/powershell/module/exchange/set-dynamicdistributiongroup)
+- [New-DynamicDistributionGroup](/powershell/module/exchangepowershell/new-dynamicdistributiongroup)
+- [Set-DynamicDistributionGroup](/powershell/module/exchangepowershell/set-dynamicdistributiongroup)
 
-- [New-EmailAddressPolicy](/powershell/module/exchange/new-emailaddresspolicy)
-- [Set-EmailAddressPolicy](/powershell/module/exchange/set-emailaddresspolicy)
+- [New-EmailAddressPolicy](/powershell/module/exchangepowershell/new-emailaddresspolicy)
+- [Set-EmailAddressPolicy](/powershell/module/exchangepowershell/set-emailaddresspolicy)
 
-- [New-AddressList](/powershell/module/exchange/new-addresslist)
-- [Set-AddressList](/powershell/module/exchange/set-addresslist)
+- [New-AddressList](/powershell/module/exchangepowershell/new-addresslist)
+- [Set-AddressList](/powershell/module/exchangepowershell/set-addresslist)
 
-- [New-GlobalAddressList](/powershell/module/exchange/new-globaladdresslist)
-- [Set-GlobalAddressList](/powershell/module/exchange/set-globaladdresslist)
+- [New-GlobalAddressList](/powershell/module/exchangepowershell/new-globaladdresslist)
+- [Set-GlobalAddressList](/powershell/module/exchangepowershell/set-globaladdresslist)
 
 For more information about the filterable properties you can use with the _RecipientFilter_ parameter, see [Filterable properties for the RecipientFilter parameter](recipientfilter-properties.md).
 
@@ -133,21 +133,21 @@ Get-Mailbox -Identity Ayla | Format-List
 
 The _Filter_ parameter is available for the following recipient cmdlets:
 
-- [Get-CASMailbox](/powershell/module/exchange/get-casmailbox)
-- [Get-Contact](/powershell/module/exchange/get-contact)
-- [Get-DistributionGroup](/powershell/module/exchange/get-distributiongroup)
-- [Get-DynamicDistributionGroup](/powershell/module/exchange/get-dynamicdistributiongroup)
-- [Get-Group](/powershell/module/exchange/get-group)
-- [Get-Mailbox](/powershell/module/exchange/get-mailbox)
-- [Get-MailContact](/powershell/module/exchange/get-mailcontact)
-- [Get-MailPublicFolder](/powershell/module/exchange/get-mailpublicfolder)
-- [Get-MailUser](/powershell/module/exchange/get-mailuser)
-- [Get-Recipient](/powershell/module/exchange/get-recipient)
-- [Get-RemoteMailbox](/powershell/module/exchange/get-remotemailbox)
-- [Get-SecurityPrincipal](/powershell/module/exchange/get-securityprincipal)
-- [Get-UMMailbox](/powershell/module/exchange/get-ummailbox)
-- [Get-User](/powershell/module/exchange/get-user)
-- [Get-UnifiedGroup](/powershell/module/exchange/get-unifiedgroup)
+- [Get-CASMailbox](/powershell/module/exchangepowershell/get-casmailbox)
+- [Get-Contact](/powershell/module/exchangepowershell/get-contact)
+- [Get-DistributionGroup](/powershell/module/exchangepowershell/get-distributiongroup)
+- [Get-DynamicDistributionGroup](/powershell/module/exchangepowershell/get-dynamicdistributiongroup)
+- [Get-Group](/powershell/module/exchangepowershell/get-group)
+- [Get-Mailbox](/powershell/module/exchangepowershell/get-mailbox)
+- [Get-MailContact](/powershell/module/exchangepowershell/get-mailcontact)
+- [Get-MailPublicFolder](/powershell/module/exchangepowershell/get-mailpublicfolder)
+- [Get-MailUser](/powershell/module/exchangepowershell/get-mailuser)
+- [Get-Recipient](/powershell/module/exchangepowershell/get-recipient)
+- [Get-RemoteMailbox](/powershell/module/exchangepowershell/get-remotemailbox)
+- [Get-SecurityPrincipal](/powershell/module/exchangepowershell/get-securityprincipal)
+- [Get-UMMailbox](/powershell/module/exchangepowershell/get-ummailbox)
+- [Get-User](/powershell/module/exchangepowershell/get-user)
+- [Get-UnifiedGroup](/powershell/module/exchangepowershell/get-unifiedgroup)
 
 For more information about the filterable properties you can use with the _Filter_ parameter, see [Filterable properties for the Filter parameter](filter-properties.md).
 
@@ -161,7 +161,7 @@ Get-User -Filter "Title -like 'Manager*'"
 
 ## Custom filters using the ContentFilter parameter
 
-You can use the _ContentFilter_ parameter to select specific message content to export when using the [New-MailboxExportRequest](/powershell/module/exchange/new-mailboxexportrequest) cmdlet. If the command finds a message that contains the match to the content filter, it exports the message to a .pst file.
+You can use the _ContentFilter_ parameter to select specific message content to export when using the [New-MailboxExportRequest](/powershell/module/exchangepowershell/new-mailboxexportrequest) cmdlet. If the command finds a message that contains the match to the content filter, it exports the message to a .pst file.
 
 ### ContentFilter parameter example
 
diff --git a/exchange/docs-conceptual/recipientfilter-properties.md b/exchange/docs-conceptual/recipientfilter-properties.md
index 0c75acd5b6..f94d2a8186 100644
--- a/exchange/docs-conceptual/recipientfilter-properties.md
+++ b/exchange/docs-conceptual/recipientfilter-properties.md
@@ -17,10 +17,10 @@ description: "Learn about the recipient properties that you can use with the Rec
 
 You use the _RecipientFilter_ parameter to create OPATH filters based on the properties of recipient objects in Exchange Server 2016 or later, and Exchange Online. The _RecipientFilter_ parameter is available in the following cmdlets:
 
-- [New-AddressList](/powershell/module/exchange/new-addresslist) and [Set-AddressList](/powershell/module/exchange/set-addresslist)
-- [New-DynamicDistributionGroup](/powershell/module/exchange/new-dynamicdistributiongroup) and [Set-DynamicDistributionGroup](/powershell/module/exchange/set-dynamicdistributiongroup)
-- [New-EmailAddressPolicy](/powershell/module/exchange/new-emailaddresspolicy) and [Set-EmailAddressPolicy](/powershell/module/exchange/set-emailaddresspolicy)
-- [New-GlobalAddressList](/powershell/module/exchange/new-globaladdresslist) and [Set-GlobalAddressList](/powershell/module/exchange/set-globaladdresslist)
+- [New-AddressList](/powershell/module/exchangepowershell/new-addresslist) and [Set-AddressList](/powershell/module/exchangepowershell/set-addresslist)
+- [New-DynamicDistributionGroup](/powershell/module/exchangepowershell/new-dynamicdistributiongroup) and [Set-DynamicDistributionGroup](/powershell/module/exchangepowershell/set-dynamicdistributiongroup)
+- [New-EmailAddressPolicy](/powershell/module/exchangepowershell/new-emailaddresspolicy) and [Set-EmailAddressPolicy](/powershell/module/exchangepowershell/set-emailaddresspolicy)
+- [New-GlobalAddressList](/powershell/module/exchangepowershell/new-globaladdresslist) and [Set-GlobalAddressList](/powershell/module/exchangepowershell/set-globaladdresslist)
 
 ## Filterable recipient properties
 
@@ -167,10 +167,10 @@ The recipient properties that have been *confirmed* to work with the _RecipientF
 |_LitigationHoldOwner_|_msExchLitigationHoldOwner_|String (wildcards accepted).||
 |_LocaleID_|_localeID_|Integer|For valid values, [Microsoft Locale ID Values](/openspecs/office_standards/ms-oe376/6c085406-a698-4e12-9d4d-c3b0ee3dbc4a).|
 |_MailboxMoveBatchName_|_msExchMailboxMoveBatchName_|String (wildcards accepted).||
-|_MailboxMoveFlags_|_msExchMailboxMoveFlags_|For valid values, see the description of the _Flags_ parameter in [Get-MoveRequest](/powershell/module/exchange/get-moverequest).||
+|_MailboxMoveFlags_|_msExchMailboxMoveFlags_|For valid values, see the description of the _Flags_ parameter in [Get-MoveRequest](/powershell/module/exchangepowershell/get-moverequest).||
 |_MailboxMoveRemoteHostName_|_msExchMailboxMoveRemoteHostName_|String (wildcards accepted).||
 |_MailboxMoveSourceMDB_|_msExchMailboxMoveSourceMDBLink_|String (wildcards accepted in dynamic distribution groups).||
-|_MailboxMoveStatus_|_msExchMailboxMoveStatus_|For valid values, see the description of the _MoveStatus_ parameter in [Get-MoveRequest](/powershell/module/exchange/get-moverequest).||
+|_MailboxMoveStatus_|_msExchMailboxMoveStatus_|For valid values, see the description of the _MoveStatus_ parameter in [Get-MoveRequest](/powershell/module/exchangepowershell/get-moverequest).||
 |_MailboxMoveTargetMDB_|_msExchMailboxMoveTargetMDBLink_|String (wildcards accepted in dynamic distribution groups).||
 |_MailboxPlan_|_msExchParentPlanLink_|String (wildcards accepted).|Mailbox plans correspond to Microsoft 365 license types. The availability of a license plans is determined by the selections that you make when you enroll your domain.|
 |_MailboxRelease_|_msExchMailboxRelease_|String (wildcards accepted).||
@@ -221,7 +221,7 @@ The recipient properties that have been *confirmed* to work with the _RecipientF
 |_PopEnabled_|n/a|Boolean (`$true` or `$false`)||
 |_PostalCode_|_postalCode_|String (wildcards accepted).||
 |_PostOfficeBox_|_postOfficeBox_|String (wildcards accepted).||
-|_PreviousRecipientTypeDetails_|_msExchPreviousRecipientTypeDetails_|For valid values, see the description of the _RecipientTypeDetails_ parameter in [Get-Recipient](/powershell/module/exchange/get-recipient).||
+|_PreviousRecipientTypeDetails_|_msExchPreviousRecipientTypeDetails_|For valid values, see the description of the _RecipientTypeDetails_ parameter in [Get-Recipient](/powershell/module/exchangepowershell/get-recipient).||
 |_PrimaryGroupId_|_primaryGroupId_|Integer|For domain users, the value of this property is typically 513, which corresponds to the Domain Users group.|
 |_PrimarySmtpAddress_|n/a|String (wildcards accepted).|Don't use the _PrimarySmtpAddress_ property; use the _EmailAddresses_ property instead. Any filter that uses the _PrimarySmtpAddress_ property will also search values in the _EmailAddresses_ property. For example, if a mailbox has the primary email address dario@contoso.com, and the additional proxy addresses dario2@contoso.com and dario3@contoso.com, all of the following filters will return that mailbox in the result: `"PrimarySmtpAddress -eq 'dario@contoso.com'"`, `"PrimarySmtpAddress -eq 'dario2@contoso.com'"`, or `"PrimarySmtpAddress -eq 'dario3@contoso.com'"`.|
 |_ProhibitSendQuota_|_mDBOverQuotaLimit_|Dynamic distribution groups: A byte quantified size value (for example, `50MB` or `1.5GB`). Unqualified values are treated as bytes. <br> Others: Blank or non-blank.||
@@ -237,8 +237,8 @@ The recipient properties that have been *confirmed* to work with the _RecipientF
 |_RecipientDisplayType_|_msExchRecipientDisplayType_|`MailboxUser` (0), `DistributionGroup` (1), `PublicFolder` (2), `DynamicDistributionGroup` (3), `Organization` (4), `PrivateDistributionList` (5), `RemoteMailUser` (6). `ConferenceRoomMailbox` (7), or `EquipmentMailbox` (8).||
 |_RecipientFilter_|_msExchQueryFilter_|String (wildcards accepted).||
 |_RecipientLimits_|_msExchRecipLimit_|`Unlimited` or an integer.|This property specifies the maximum number of recipients that are allowed in messages sent by the mailbox.|
-|_RecipientType_|n/a|For valid values, see the description of the _RecipientType_ parameter in [Get-Recipient](/powershell/module/exchange/get-recipient).||
-|_RecipientTypeDetails_|n/a|For valid values, see the description of the _RecipientTypeDetails_ parameter in [Get-Recipient](/powershell/module/exchange/get-recipient).||
+|_RecipientType_|n/a|For valid values, see the description of the _RecipientType_ parameter in [Get-Recipient](/powershell/module/exchangepowershell/get-recipient).||
+|_RecipientTypeDetails_|n/a|For valid values, see the description of the _RecipientTypeDetails_ parameter in [Get-Recipient](/powershell/module/exchangepowershell/get-recipient).||
 |_RecoverableItemsQuota_|_msExchDumpsterQuota_|Dynamic distribution groups: A byte quantified size value (for example, `50MB` or `1.5GB`). Unqualified values are treated as bytes. <br> Others: Blank or non-blank.||
 |_RecoverableItemsWarningQuota_|_msExchDumpsterWarningQuota_|Dynamic distribution groups: A byte quantified size value (for example, `50MB` or `1.5GB`). Unqualified values are treated as bytes. <br> Others: Blank or non-blank.||
 |_RejectMessagesFrom_|_unauthOrig_|Dynamic distribution groups: String (wildcards accepted). <br> Others: Blank or non-blank.||
diff --git a/exchange/docs-conceptual/scc-powershell.md b/exchange/docs-conceptual/scc-powershell.md
index bf972d6ad0..057ea44964 100644
--- a/exchange/docs-conceptual/scc-powershell.md
+++ b/exchange/docs-conceptual/scc-powershell.md
@@ -34,8 +34,8 @@ Security & Compliance PowerShell is the administrative interface that enables yo
 Security & Compliance PowerShell contains the following types of cmdlets:
 
 - Cmdlets that correspond to features available only in Purview compliance and the Microsoft Purview compliance portal. Most cmdlets in Security & Compliance PowerShell fall into this category.
-- Basic cmdlets that are also available in Exchange Online PowerShell (for example, [Get-User](/powershell/module/exchange/get-user), and [Get-RoleGroup](/powershell/module/exchange/get-rolegroup)).
-- A few cmdlets that correspond to default protections for cloud mailboxes and protections in Microsoft Defender for Office 365 in the Microsoft Defender portal (for example, [Set-SecOpsOverridePolicy](/powershell/module/exchange/set-secopsoverridepolicy)).
+- Basic cmdlets that are also available in Exchange Online PowerShell (for example, [Get-User](/powershell/module/exchangepowershell/get-user), and [Get-RoleGroup](/powershell/module/exchangepowershell/get-rolegroup)).
+- A few cmdlets that correspond to default protections for cloud mailboxes and protections in Microsoft Defender for Office 365 in the Microsoft Defender portal (for example, [Set-SecOpsOverridePolicy](/powershell/module/exchangepowershell/set-secopsoverridepolicy)).
 
   Cmdlets for most EOP and Defender for Office 365 security features (for example, [anti-spam policies](/defender-office-365/anti-spam-protection-about)) are available only in [Exchange Online PowerShell](exchange-online-powershell.md).
 
diff --git a/exchange/docs-conceptual/values-for-custompropertynames-parameter.md b/exchange/docs-conceptual/values-for-custompropertynames-parameter.md
index ea729cff90..fcb4c97c9d 100644
--- a/exchange/docs-conceptual/values-for-custompropertynames-parameter.md
+++ b/exchange/docs-conceptual/values-for-custompropertynames-parameter.md
@@ -19,7 +19,7 @@ description: "Learn about the valid values for the CustomPropertyNames parameter
 
 # Values for the CustomPropertyNames parameter in Exchange Online PowerShell
 
-The _CustomPropertyNames_ parameter on the [Get-CalendarDiagnosticObjects](/powershell/module/exchange/get-calendardiagnosticobjects) cmdlet returns the specified properties in the results.
+The _CustomPropertyNames_ parameter on the [Get-CalendarDiagnosticObjects](/powershell/module/exchangepowershell/get-calendardiagnosticobjects) cmdlet returns the specified properties in the results.
 
 The article describes the valid values for the _CustomPropertyNames_ parameter.
 

From b8818377630ba2f4ba9c341beb51be83b5606b7a Mon Sep 17 00:00:00 2001
From: Chris Davis <chris.davis@microsoft.com>
Date: Mon, 4 Aug 2025 15:12:16 -0700
Subject: [PATCH 008/145] Exchange cmdlet ref links

---
 teams/teams-ps/MicrosoftTeams/New-Team.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/teams/teams-ps/MicrosoftTeams/New-Team.md b/teams/teams-ps/MicrosoftTeams/New-Team.md
index d9756ee326..d8eff81575 100644
--- a/teams/teams-ps/MicrosoftTeams/New-Team.md
+++ b/teams/teams-ps/MicrosoftTeams/New-Team.md
@@ -44,7 +44,7 @@ Creates a new team with user specified settings, and returns a Group object with
 
 Groups created through teams cmdlets, APIs, or clients will not show up in Outlook by default.
 
-If you want these groups to appear in Outlook clients, you can use the [Set-UnifiedGroup](https://learn.microsoft.com/powershell/module/exchange/set-unifiedgroup) cmdlet in the Exchange Powershell Module to disable the switch parameter `HiddenFromExchangeClientsEnabled` (-HiddenFromExchangeClientsEnabled:$false).
+If you want these groups to appear in Outlook clients, you can use the [Set-UnifiedGroup](https://learn.microsoft.com/powershell/module/exchangepowershell/set-unifiedgroup) cmdlet in the Exchange Powershell Module to disable the switch parameter `HiddenFromExchangeClientsEnabled` (-HiddenFromExchangeClientsEnabled:$false).
 
 Note: The Teams application may need to be open by an Owner for up to two hours before changes are reflected.
 
@@ -381,7 +381,7 @@ Accept wildcard characters: False
 
 ### -GroupId
 Specify a GroupId to convert to a Team.  If specified, you cannot provide the other values that are already specified by the existing group, namely: Visibility, Alias, Description, or DisplayName.
-If, for example, you need to create a Team from an existing Microsoft 365 Group, use the _ExternalDirectoryObjectId_ property value returned by [Get-UnifiedGroup](https://learn.microsoft.com/powershell/module/exchange/get-unifiedgroup?view=exchange-ps).
+If, for example, you need to create a Team from an existing Microsoft 365 Group, use the _ExternalDirectoryObjectId_ property value returned by [Get-UnifiedGroup](https://learn.microsoft.com/powershell/module/exchangepowershell/get-unifiedgroup).
 
 ```yaml
 Type: String
@@ -401,7 +401,7 @@ This value will be used for the mail enabled object and will be used as PrimaryS
 The value of the MailNickName parameter has to be unique across your tenant.
 Note: If Microsoft 365 groups naming policies are enabled in your tenant, this parameter is required and must also comply with the naming policy.
 
-For more details about the naming conventions see here: [New-UnifiedGroup](https://learn.microsoft.com/powershell/module/exchange/new-unifiedgroup#parameters), Parameter: -Alias.
+For more details about the naming conventions see here: [New-UnifiedGroup](https://learn.microsoft.com/powershell/module/exchangepowershell/new-unifiedgroup#parameters), Parameter: -Alias.
 
 ```yaml
 Type: String

From c685047c9f1d108c29a4dae23bc2d3c4d22447cb Mon Sep 17 00:00:00 2001
From: hedwig233 <31384861+hedwig233@users.noreply.github.com>
Date: Tue, 5 Aug 2025 11:01:47 +0800
Subject: [PATCH 009/145] Update New-CsTeamsCallingPolicy.md

---
 .../New-CsTeamsCallingPolicy.md               | 26 +++++++++++++++++++
 1 file changed, 26 insertions(+)

diff --git a/teams/teams-ps/MicrosoftTeams/New-CsTeamsCallingPolicy.md b/teams/teams-ps/MicrosoftTeams/New-CsTeamsCallingPolicy.md
index eda358df5f..fc603913b9 100644
--- a/teams/teams-ps/MicrosoftTeams/New-CsTeamsCallingPolicy.md
+++ b/teams/teams-ps/MicrosoftTeams/New-CsTeamsCallingPolicy.md
@@ -54,6 +54,7 @@ New-CsTeamsCallingPolicy [-Identity] <string>
  [-SpamFilteringEnabledType <string>]
  [-VoiceSimulationInInterpreter <string>]
  [-RealTimeText <string>]
+ [-ExplicitRecordingConsent <string>]
  [-WhatIf]
  [<CommonParameters>]
 ```
@@ -195,6 +196,31 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
+### -ExplicitRecordingConsent
+
+> Applicable: Microsoft Teams
+
+>[!NOTE]
+>This feature has not been released yet and will have no changes if it is enabled or disabled.
+
+Determines whether users need to give explicit consent for recording and transcript in 1:1 calls. Set this to enabled to request users to give explicit consent.
+
+Possible Values:
+- Enabled: Explicit consent, requires participant agreement.
+- Disabled: Implicit consent, does not require participant agreement.
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+
+Required: False
+Position: Named
+Default value: Disabled
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
 ### -AllowDelegation
 
 > Applicable: Microsoft Teams

From 22ab385c0f9089e972e4ae0f30dfdbde63a649f2 Mon Sep 17 00:00:00 2001
From: hedwig233 <31384861+hedwig233@users.noreply.github.com>
Date: Tue, 5 Aug 2025 11:09:50 +0800
Subject: [PATCH 010/145] Update Set-CsTeamsCallingPolicy.md

---
 .../Set-CsTeamsCallingPolicy.md               | 26 +++++++++++++++++++
 1 file changed, 26 insertions(+)

diff --git a/teams/teams-ps/MicrosoftTeams/Set-CsTeamsCallingPolicy.md b/teams/teams-ps/MicrosoftTeams/Set-CsTeamsCallingPolicy.md
index 1d0d11adb7..6a6bcf2c59 100644
--- a/teams/teams-ps/MicrosoftTeams/Set-CsTeamsCallingPolicy.md
+++ b/teams/teams-ps/MicrosoftTeams/Set-CsTeamsCallingPolicy.md
@@ -53,6 +53,7 @@ Set-CsTeamsCallingPolicy [-Identity] <string>
  [-SpamFilteringEnabledType <string>]
  [-VoiceSimulationInInterpreter <string>]
  [-RealTimeText <string>]
+ [-ExplicitRecordingConsent <string>]
  [-WhatIf]
  [<CommonParameters>]
 ```
@@ -203,6 +204,31 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
+### -ExplicitRecordingConsent
+
+> Applicable: Microsoft Teams
+
+>[!NOTE]
+>This feature has not been released yet and will have no changes if it is enabled or disabled.
+
+Determines whether users need to give explicit consent for recording and transcript in 1:1 calls. Set this to enabled to request users to give explicit consent.
+
+Possible Values:
+- Enabled: Explicit consent, requires participant agreement.
+- Disabled: Implicit consent, does not require participant agreement.
+
+```yaml
+Type: Boolean
+Parameter Sets: (All)
+Aliases:
+
+Required: False
+Position: Named
+Default value: Disabled
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
 ### -AllowDelegation
 
 > Applicable: Microsoft Teams

From f4967cc4150479deb6b8133ee4addea63f41790d Mon Sep 17 00:00:00 2001
From: Chris Davis <chris.davis@microsoft.com>
Date: Tue, 5 Aug 2025 08:59:13 -0700
Subject: [PATCH 011/145] Update app-only-auth-powershell-v2.md

21Vianet support
---
 exchange/docs-conceptual/app-only-auth-powershell-v2.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/exchange/docs-conceptual/app-only-auth-powershell-v2.md b/exchange/docs-conceptual/app-only-auth-powershell-v2.md
index 38fa8dc50f..fc8364d818 100644
--- a/exchange/docs-conceptual/app-only-auth-powershell-v2.md
+++ b/exchange/docs-conceptual/app-only-auth-powershell-v2.md
@@ -33,6 +33,8 @@ Certificate based authentication (CBA) or app-only authentication as described i
 >
 >   For instructions on how to install or update the module, see [Install and maintain the Exchange Online PowerShell module](exchange-online-powershell-v2.md#install-and-maintain-the-exchange-online-powershell-module). For instructions on how to use the module in Azure automation, see [Manage modules in Azure Automation](/azure/automation/shared-resources/modules).
 >
+> - CBA or app-only authentication is available in Office 365 operated by 21Vianet in China.
+>
 > - REST API connections in the Exchange Online PowerShell V3 module require the PowerShellGet and PackageManagement modules. For more information, see [PowerShellGet for REST-based connections in Windows](exchange-online-powershell-v2.md#powershellget-for-rest-api-connections-in-windows).
 >
 >   If the procedures in this article don't work for you, verify that you don't have Beta versions of the PackageManagement or PowerShellGet modules installed by running the following command: `Get-InstalledModule PackageManagement -AllVersions; Get-InstalledModule PowerShellGet -AllVersions`.

From 5ea75c2c5aefd8829a641d0f6b270982e637bc3b Mon Sep 17 00:00:00 2001
From: Prashant Bafna <pbafna@microsoft.com>
Date: Wed, 6 Aug 2025 00:13:10 +0530
Subject: [PATCH 012/145] Move back
 Disable-CsTeamsShiftsConnectionErrorReport.md

---
 ...able-CsTeamsShiftsConnectionErrorReport.md | 70 +++++++++++++++++++
 1 file changed, 70 insertions(+)
 create mode 100644 teams/teams-ps/MicrosoftTeams/Disable-CsTeamsShiftsConnectionErrorReport.md

diff --git a/teams/teams-ps/MicrosoftTeams/Disable-CsTeamsShiftsConnectionErrorReport.md b/teams/teams-ps/MicrosoftTeams/Disable-CsTeamsShiftsConnectionErrorReport.md
new file mode 100644
index 0000000000..60edafb900
--- /dev/null
+++ b/teams/teams-ps/MicrosoftTeams/Disable-CsTeamsShiftsConnectionErrorReport.md
@@ -0,0 +1,70 @@
+---
+external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml
+Module Name: MicrosoftTeams
+title: Disable-CsTeamsShiftsConnectionErrorReport
+author: gucsun
+ms.author: gucsun
+manager: navinth
+online version: https://learn.microsoft.com/powershell/module/teams/disable-csteamsshiftsconnectionerrorreport
+schema: 2.0.0
+---
+
+# Disable-CsTeamsShiftsConnectionErrorReport
+
+## SYNOPSIS
+
+This cmdlet disables an error report.
+
+## SYNTAX
+
+```
+Disable-CsTeamsShiftsConnectionErrorReport -ErrorReportId <String> [<CommonParameters>]
+```
+
+## DESCRIPTION
+
+**Note:** This cmdlet is currently in public preview.
+
+This cmdlet disables an error report. All available instances can be found by running [Get-CsTeamsShiftsConnectionErrorReport](https://learn.microsoft.com/powershell/module/teams/get-csteamsshiftsconnectionerrorreport).
+
+## EXAMPLES
+
+### Example 1
+```powershell
+PS C:\> Disable-CsTeamsShiftsConnectionErrorReport -ErrorReportId 18b3e490-e6ed-4c2e-9925-47e36609dff3
+```
+
+Disables the error report with ID `18b3e490-e6ed-4c2e-9925-47e36609dff3`.
+
+## PARAMETERS
+
+### -ErrorReportId
+
+> Applicable: Microsoft Teams
+
+The ID of the error report that you want to disable.
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+
+Required: True
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### CommonParameters
+This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).
+
+## INPUTS
+
+## OUTPUTS
+
+## NOTES
+
+## RELATED LINKS
+
+[Get-CsTeamsShiftsConnectionErrorReport](https://learn.microsoft.com/powershell/module/teams/get-csteamsshiftsconnectionerrorreport)

From 499313e33ab38831c1bd7f25f3bd9fd82673c000 Mon Sep 17 00:00:00 2001
From: Prashant Bafna <pbafna@microsoft.com>
Date: Wed, 6 Aug 2025 00:16:05 +0530
Subject: [PATCH 013/145] Delete
 teams/teams-ps/teams/Disable-CsTeamsShiftsConnectionErrorReport.md

---
 ...able-CsTeamsShiftsConnectionErrorReport.md | 70 -------------------
 1 file changed, 70 deletions(-)
 delete mode 100644 teams/teams-ps/teams/Disable-CsTeamsShiftsConnectionErrorReport.md

diff --git a/teams/teams-ps/teams/Disable-CsTeamsShiftsConnectionErrorReport.md b/teams/teams-ps/teams/Disable-CsTeamsShiftsConnectionErrorReport.md
deleted file mode 100644
index 60edafb900..0000000000
--- a/teams/teams-ps/teams/Disable-CsTeamsShiftsConnectionErrorReport.md
+++ /dev/null
@@ -1,70 +0,0 @@
----
-external help file: Microsoft.TeamsCmdlets.PowerShell.Custom.dll-Help.xml
-Module Name: MicrosoftTeams
-title: Disable-CsTeamsShiftsConnectionErrorReport
-author: gucsun
-ms.author: gucsun
-manager: navinth
-online version: https://learn.microsoft.com/powershell/module/teams/disable-csteamsshiftsconnectionerrorreport
-schema: 2.0.0
----
-
-# Disable-CsTeamsShiftsConnectionErrorReport
-
-## SYNOPSIS
-
-This cmdlet disables an error report.
-
-## SYNTAX
-
-```
-Disable-CsTeamsShiftsConnectionErrorReport -ErrorReportId <String> [<CommonParameters>]
-```
-
-## DESCRIPTION
-
-**Note:** This cmdlet is currently in public preview.
-
-This cmdlet disables an error report. All available instances can be found by running [Get-CsTeamsShiftsConnectionErrorReport](https://learn.microsoft.com/powershell/module/teams/get-csteamsshiftsconnectionerrorreport).
-
-## EXAMPLES
-
-### Example 1
-```powershell
-PS C:\> Disable-CsTeamsShiftsConnectionErrorReport -ErrorReportId 18b3e490-e6ed-4c2e-9925-47e36609dff3
-```
-
-Disables the error report with ID `18b3e490-e6ed-4c2e-9925-47e36609dff3`.
-
-## PARAMETERS
-
-### -ErrorReportId
-
-> Applicable: Microsoft Teams
-
-The ID of the error report that you want to disable.
-
-```yaml
-Type: String
-Parameter Sets: (All)
-Aliases:
-
-Required: True
-Position: Named
-Default value: None
-Accept pipeline input: False
-Accept wildcard characters: False
-```
-
-### CommonParameters
-This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).
-
-## INPUTS
-
-## OUTPUTS
-
-## NOTES
-
-## RELATED LINKS
-
-[Get-CsTeamsShiftsConnectionErrorReport](https://learn.microsoft.com/powershell/module/teams/get-csteamsshiftsconnectionerrorreport)

From c64405ddb8fe175081b003c2b3184093fda79db9 Mon Sep 17 00:00:00 2001
From: Prashant Bafna <pbafna@microsoft.com>
Date: Wed, 6 Aug 2025 00:28:49 +0530
Subject: [PATCH 014/145] Update MicrosoftTeams.md

---
 teams/teams-ps/MicrosoftTeams/MicrosoftTeams.md | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/teams/teams-ps/MicrosoftTeams/MicrosoftTeams.md b/teams/teams-ps/MicrosoftTeams/MicrosoftTeams.md
index 5e7990cbf7..55e8182c05 100644
--- a/teams/teams-ps/MicrosoftTeams/MicrosoftTeams.md
+++ b/teams/teams-ps/MicrosoftTeams/MicrosoftTeams.md
@@ -35,6 +35,9 @@ The Connect-MicrosoftTeams cmdlet connects an authenticated account for use with
 ### [Disable-CsOnlineSipDomain](Disable-CsOnlineSipDomain.md)
 This cmdlet prevents provisioning of users in Skype for Business Online for the specified domain.
 
+### [Disable-CsTeamsShiftsConnectionErrorReport](Disable-CsTeamsShiftsConnectionErrorReport.md)
+This cmdlet disables an error report.
+
 ### [Disconnect-MicrosoftTeams](Disconnect-MicrosoftTeams.md)
 {{Placeholder}}
 

From 81e69f74e5b6e1d6f4a2e40593dc887b1eb180a7 Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Tue, 5 Aug 2025 12:00:21 -0700
Subject: [PATCH 015/145] Update New-CsAutoAttendantCallFlow.md

---
 teams/teams-ps/MicrosoftTeams/New-CsAutoAttendantCallFlow.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/teams/teams-ps/MicrosoftTeams/New-CsAutoAttendantCallFlow.md b/teams/teams-ps/MicrosoftTeams/New-CsAutoAttendantCallFlow.md
index 7e23f4fdaf..3db30d58e5 100644
--- a/teams/teams-ps/MicrosoftTeams/New-CsAutoAttendantCallFlow.md
+++ b/teams/teams-ps/MicrosoftTeams/New-CsAutoAttendantCallFlow.md
@@ -196,3 +196,5 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable
 [New-CsAutoAttendantMenu](https://learn.microsoft.com/powershell/module/microsoftteams/new-csautoattendantmenu)
 
 [New-CsAutoAttendantPrompt](https://learn.microsoft.com/powershell/module/microsoftteams/new-csautoattendantprompt)
+
+[Get-CsMainlineAttendantFlow](https://learn.microsoft.com/powershell/module/microsoftteams/new-csautoattendantprompt)

From 698c99b5ba265d33aedb25b02f44a49179f93806 Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Tue, 5 Aug 2025 12:01:27 -0700
Subject: [PATCH 016/145] Create
 Get-CsMainlineAttendantAppointmentBookingFlow.md

---
 ...MainlineAttendantAppointmentBookingFlow.md | 190 ++++++++++++++++++
 1 file changed, 190 insertions(+)
 create mode 100644 teams/teams-ps/MicrosoftTeams/Get-CsMainlineAttendantAppointmentBookingFlow.md

diff --git a/teams/teams-ps/MicrosoftTeams/Get-CsMainlineAttendantAppointmentBookingFlow.md b/teams/teams-ps/MicrosoftTeams/Get-CsMainlineAttendantAppointmentBookingFlow.md
new file mode 100644
index 0000000000..f5161eb3d9
--- /dev/null
+++ b/teams/teams-ps/MicrosoftTeams/Get-CsMainlineAttendantAppointmentBookingFlow.md
@@ -0,0 +1,190 @@
+---
+external help file: Microsoft.Rtc.Management.dll-Help.xml
+online version: https://learn.microsoft.com/powershell/module/teams/Get-CsMainlineAttendantAppointmentBookingFlow
+applicable: Microsoft Teams
+title: Get-CsMainlineAttendantAppointmentBookingFlow
+schema: 2.0.0
+ms.reviewer:
+manager: bulenteg
+author: tomkau
+ms.author: tomkau
+ms.reviewer: williamlooney
+---
+
+# Get-CsMainlineAttendantAppointmentBookingFlow
+
+## SYNOPSIS
+The Get-CsMainlineAttendantAppointmentBookingFlow cmdlet returns the identified Mainline attendant appointment booking flow.
+
+## SYNTAX
+
+```
+Get-CsMainlineAttendantAppointmentBookingFlow [-Identity <Guid>] [-Tenant <Guid>] [-First <Int32>] [-Skip <Int32>] [-ExcludeContent <Switch>] [-Sort <String>] [-Descending <Switch>] [-NameFilter <String>] [<CommonParameters>]
+```
+
+## DESCRIPTION
+The Get-CsMainlineAttendantAppointmentBookingFlow cmdlet lets you retrieve information about the Mainline attendant appointment booking flows n your organization.
+
+## EXAMPLES
+
+### -------------------------- Example 1 --------------------------
+```
+Get-CsMainlineAttendantAppointmentBookingFlow
+```
+
+This example gets the first 100 Mainline attendant appointment booking flows in the organization.
+
+### -------------------------- Example 2 --------------------------
+```
+Get-CsMainlineAttendantAppointmentBookingFlow -Identity 5e3a575e-1faa-49ff-83c2-5cf1c36c0e01
+```
+
+This example gets the Mainline attendant appointment booking flow with the identity 5e3a575e-1faa-49ff-83c2-5cf1c36c0e01. If no appointment booking flow exists with the identity 5e3a575e-1faa-49ff-83c2-5cf1c36c0e01, then this example generates an error.
+
+## PARAMETERS
+
+### -Identity
+PARAMVALUE: Guid
+
+```yaml
+Type: Guid
+Parameter Sets: (All)
+Aliases:
+applicable: Microsoft Teams
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -Tenant
+PARAMVALUE: Guid
+
+```yaml
+Type: Guid
+Parameter Sets: (All)
+Aliases:
+applicable: Microsoft Teams
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -First
+The First parameter gets the first N appointment flows, up to a maximum of 100 at a time. 
+When not specified, the default behavior is to return the first 100 appointment flows. It is intended to be used in conjunction with the `-Skip` parameter for pagination purposes.
+If a number greater than 100 is supplied, the request will fail.
+
+```yaml
+Type: Int32
+Parameter Sets: (All)
+Aliases:
+applicable: Microsoft Teams
+
+Required: False
+Position: Named
+Default value: 100
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -Skip
+The Skip parameter skips the first N appointment flows. It is intended to be used in conjunction with the `-First` parameter for pagination purposes.
+
+```yaml
+Type: Int32
+Parameter Sets: (All)
+Aliases:
+applicable: Microsoft Teams
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -ExcludeContent
+The ExcludeContent parameter only displays the Name and Id of the appointment flow.
+
+```yaml
+Type: SwitchParameter
+Parameter Sets: (All)
+Aliases:
+applicable: Microsoft Teams
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -Sort
+The Sort parameter specifies the property used to sort.
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+applicable: Microsoft Teams
+
+Required: True
+Position: Named
+Default value: Name
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -Descending
+The Descending parameter sorts appointment booking flows in descending order
+
+```yaml
+Type: SwitchParameter
+Parameter Sets: (All)
+Aliases:
+applicable: Microsoft Teams
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -NameFilter
+The NameFilter parameter returns appointment booking flows where the name contains specified string
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+applicable: Microsoft Teams
+
+Required: True
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### CommonParameters
+This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).
+
+## INPUTS
+
+### Identity
+Represents the unique identifier of an appointment booking flow.
+
+## OUTPUTS
+
+### Microsoft.Rtc.Management.Hosted.CallQueue.Models.CallQueue
+
+## NOTES
+
+## RELATED LINKS

From 73062abb51b030334cc9102ab6551c74cbc0be25 Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Tue, 5 Aug 2025 12:02:25 -0700
Subject: [PATCH 017/145] Create Get-CsMainlineAttendantFlow.md

---
 .../Get-CsMainlineAttendantFlow.md            | 124 ++++++++++++++++++
 1 file changed, 124 insertions(+)
 create mode 100644 teams/teams-ps/MicrosoftTeams/Get-CsMainlineAttendantFlow.md

diff --git a/teams/teams-ps/MicrosoftTeams/Get-CsMainlineAttendantFlow.md b/teams/teams-ps/MicrosoftTeams/Get-CsMainlineAttendantFlow.md
new file mode 100644
index 0000000000..3b01b0dd8f
--- /dev/null
+++ b/teams/teams-ps/MicrosoftTeams/Get-CsMainlineAttendantFlow.md
@@ -0,0 +1,124 @@
+---
+external help file: Microsoft.Rtc.Management.dll-Help.xml
+online version: https://learn.microsoft.com/powershell/module/teams/get-csmainlineattendantflow
+applicable: Microsoft Teams
+title: Get-CsMainlineAttendantFlow
+author: tomkau
+ms.author: tomkau
+manager: bulenteg
+ms.reviewer:
+schema: 2.0.0
+---
+
+# Get-CsMainlineAttendantFlow 
+
+## SYNOPSIS
+Creates new Call Queue in your Skype for Business Online organization.
+
+## SYNTAX
+
+```
+Get-CsMainlineAttendantFlow  [-MaConfigId <String>] [-Type <String>] [-FlowId <String>] [-Tenant <Guid>] [<CommonParameters>]
+```
+
+## DESCRIPTION
+The Get-CsMainlineAttendantFlow cmdlet returns information about the Mainline Attendant flows configured in your organization.
+
+> [!CAUTION]
+> This cmdlet will only work for customers that are participating in the Voice Applications private preview for these features. General Availability for this functionality has not been determined at this time.
+
+## EXAMPLES
+
+### Example 1
+```
+Get-CsMainlineAttendantFlow 
+```
+
+This example will list all the Mainline Attendant flows in the tenant.
+
+### Example 2
+```
+Get-CsMainlineAttendantFlow -MaConfig 0b31bbe5-e2a0-4117-9b6f-956bca6023f8
+```
+
+This example will list all the Mainline Attendant flows associated with the specific configuration id.
+
+### Example 3
+```
+Get-CsMainlineAttendantFlow -Type Type 1 | Type 2
+```
+
+This example will list all the Mainline Attendant flows with the specified type.
+
+### Example 4
+```
+Get-CsMainlineAttendantFlow -FlowId 956bca6-e2a0-4117-9b6f-023f80b31bbe5
+```
+
+This example will list the Mainline Attendant flow with the specified flow id.
+
+## PARAMETERS
+
+### -MaConfigId
+The Mainline Attendant configuration Id
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+applicable: Microsoft Teams
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -Type
+The Mainline Attendant flow type
+
+PARAMVALUE: Appointment | QuestionAndAnswer
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+applicable: Microsoft Teams
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -FlowId
+The Mainline Attendant flow id
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+applicable: Microsoft Teams
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### CommonParameters
+This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).
+
+## INPUTS
+
+## OUTPUTS
+
+### Microsoft.Rtc.Management.Hosted.CallQueue.Models.CallQueue
+
+## NOTES
+
+## RELATED LINKS
+

From 2887f3389df573a56d6996d4f85a97779c4255c3 Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Tue, 5 Aug 2025 12:02:56 -0700
Subject: [PATCH 018/145] Create Get-CsMainlineAttendantQuestionAnswerFlow.md

---
 ...t-CsMainlineAttendantQuestionAnswerFlow.md | 191 ++++++++++++++++++
 1 file changed, 191 insertions(+)
 create mode 100644 teams/teams-ps/MicrosoftTeams/Get-CsMainlineAttendantQuestionAnswerFlow.md

diff --git a/teams/teams-ps/MicrosoftTeams/Get-CsMainlineAttendantQuestionAnswerFlow.md b/teams/teams-ps/MicrosoftTeams/Get-CsMainlineAttendantQuestionAnswerFlow.md
new file mode 100644
index 0000000000..fcaf4470cd
--- /dev/null
+++ b/teams/teams-ps/MicrosoftTeams/Get-CsMainlineAttendantQuestionAnswerFlow.md
@@ -0,0 +1,191 @@
+---
+external help file: Microsoft.Rtc.Management.dll-Help.xml
+online version: https://learn.microsoft.com/powershell/module/teams/Get-CsMainlineAttendantQuestionAnswerFlow
+applicable: Microsoft Teams
+title: Get-CsMainlineAttendantQuestionAnswerFlow
+schema: 2.0.0
+ms.reviewer:
+manager: bulenteg
+author: tomkau
+ms.author: tomkau
+ms.reviewer: williamlooney
+---
+
+# Get-CsMainlineAttendantQuestionAnswerFlow
+
+## SYNOPSIS
+The Get-CsMainlineAttendantQuestionAnswerFlow cmdlet returns the identified Mainline attendant question and answer flow.
+
+## SYNTAX
+
+```
+Get-CsMainlineAttendantQuestionAnswerFlow [-Identity <Guid>] [-Tenant <Guid>] [-First <Int32>] [-Skip <Int32>] [-ExcludeContent <Switch>] [-Sort <String>] [-Descending <Switch>] [-NameFilter <String>] [<CommonParameters>]
+```
+
+## DESCRIPTION
+The Get-CsMainlineAttendantQuestionAnswerFlow cmdlet lets you retrieve information about the Mainline attendant question and answer flows n your organization.
+
+## EXAMPLES
+
+### -------------------------- Example 1 --------------------------
+```
+Get-CsMainlineAttendantQuestionAnswerFlow
+```
+
+This example gets the first 100 Mainline attendant question and answer flows in the organization.
+
+### -------------------------- Example 2 --------------------------
+```
+Get-CsMainlineAttendantQuestionAnswerFlow -Identity 5e3a575e-1faa-49ff-83c2-5cf1c36c0e01
+```
+
+This example gets the Mainline attendant question and answer flow with the identity 5e3a575e-1faa-49ff-83c2-5cf1c36c0e01. If no question and answer flow exists with the identity 5e3a575e-1faa-49ff-83c2-5cf1c36c0e01, then this example generates an error.
+
+## PARAMETERS
+
+### -Identity
+PARAMVALUE: Guid
+
+```yaml
+Type: Guid
+Parameter Sets: (All)
+Aliases:
+applicable: Microsoft Teams
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -Tenant
+PARAMVALUE: Guid
+
+```yaml
+Type: Guid
+Parameter Sets: (All)
+Aliases:
+applicable: Microsoft Teams
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -First
+The First parameter gets the first N appointment flows, up to a maximum of 100 at a time. 
+When not specified, the default behavior is to return the first 100 question and answer flows. It is intended to be used in conjunction with the `-Skip` parameter for pagination purposes.
+If a number greater than 100 is supplied, the request will fail.
+
+```yaml
+Type: Int32
+Parameter Sets: (All)
+Aliases:
+applicable: Microsoft Teams
+
+Required: False
+Position: Named
+Default value: 100
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -Skip
+The Skip parameter skips the first N appointment flows. It is intended to be used in conjunction with the `-First` parameter for pagination purposes.
+
+```yaml
+Type: Int32
+Parameter Sets: (All)
+Aliases:
+applicable: Microsoft Teams
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -ExcludeContent
+The ExcludeContent parameter only displays the Name and Id of the question and answer flow.
+
+```yaml
+Type: SwitchParameter
+Parameter Sets: (All)
+Aliases:
+applicable: Microsoft Teams
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -Sort
+The Sort parameter specifies the property used to sort.
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+applicable: Microsoft Teams
+
+Required: True
+Position: Named
+Default value: Name
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -Descending
+The Descending parameter sorts appointment booking flows in descending order
+
+```yaml
+Type: SwitchParameter
+Parameter Sets: (All)
+Aliases:
+applicable: Microsoft Teams
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -NameFilter
+The NameFilter parameter returns question and answer booking flows where the name contains specified string
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+applicable: Microsoft Teams
+
+Required: True
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### CommonParameters
+This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).
+
+## INPUTS
+
+### Identity
+Represents the unique identifier of a question and answer booking flow.
+
+## OUTPUTS
+
+### Microsoft.Rtc.Management.Hosted.CallQueue.Models.CallQueue
+
+## NOTES
+
+## RELATED LINKS
+

From bd04c2224101620588fbcbbdadcf1ad366a45fb8 Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Tue, 5 Aug 2025 12:03:37 -0700
Subject: [PATCH 019/145] Create
 New-CsMainlineAttendantAppointmentBookingFlow.md

---
 ...MainlineAttendantAppointmentBookingFlow.md | 135 ++++++++++++++++++
 1 file changed, 135 insertions(+)
 create mode 100644 teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantAppointmentBookingFlow.md

diff --git a/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantAppointmentBookingFlow.md b/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantAppointmentBookingFlow.md
new file mode 100644
index 0000000000..f55a7ea3db
--- /dev/null
+++ b/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantAppointmentBookingFlow.md
@@ -0,0 +1,135 @@
+---
+external help file: Microsoft.Rtc.Management.dll-Help.xml
+online version: https://learn.microsoft.com/powershell/module/teams/new-csmainlineattendantappointmentbookingflow
+applicable: Microsoft Teams
+title: New-CsMainlineAttendantAppointmentBookingFlow
+author: tomkau
+ms.author: tomkau
+manager: bulenteg
+ms.reviewer:
+schema: 2.0.0
+---
+
+# New-CsMainlineAttendantAppointmentBookingFlow
+
+## SYNOPSIS
+Creates new Mainline Attendant appointment booking flow
+
+## SYNTAX
+
+```
+New-CsMainlineAttendantAppointmentBookingFlow -Name <String> -Description <String>  -CallerAuthenticationMethod <sms | email | verification_link | voiceprint | user_details> -ApiAuthenticationType <basic | api_key | bearer_token_static | bearer_token_dynamic> -ApiDefinitions <String> [-Tenant <Guid>] [<CommonParameters>]
+```
+
+## DESCRIPTION
+The New-CsMainlineAttendantAppointmentBookingFlow cmdlet creates a new appointment booking connection that can be used with Mainline Attendant
+
+> [!CAUTION]
+> This cmdlet will only work for customers that are participating in the Voice Applications private preview for these features. General Availability for this functionality has not been determined at this time.
+
+## EXAMPLES
+
+
+## PARAMETERS
+
+### -Name
+The name of the appointment booking flow
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+applicable: Microsoft Teams
+
+Required: True
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -Description
+The description for the appointment booking flow
+
+Limit: 500 characters. 
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+applicable: Microsoft Teams
+
+Required: True
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+###  -CallerAuthenticationMethod
+The method by which the caller is authenticated
+
+PARAVALUES: sms | email | verification_link | voiceprint | user_details
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+applicable: Microsoft Teams
+
+Required: True
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+###  -ApiAuthenticationType
+The method of authentication used by the API
+
+PARAVALUES: basic | api_key | bearer_token_static | bearer_token_dynamic
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+applicable: Microsoft Teams
+
+Required: True
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+###  -ApiDefinitions
+The parameters used by the API
+
+For an example, see [New-CsMainlineAttendantAppointBookingFlow -ApiDefinitions](./New-CsMainlineAttendantAppointmentBookingFlowApiDefinitionsJSON.md)
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+applicable: Microsoft Teams
+
+Required: True
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### CommonParameters
+This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).
+
+## INPUTS
+
+## OUTPUTS
+
+### Microsoft.Rtc.Management.Hosted.CallQueue.Models.CallQueue
+
+## NOTES
+
+## RELATED LINKS
+

From ee048facf57d8f5acc513c212b9879c975d88469 Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Tue, 5 Aug 2025 12:04:26 -0700
Subject: [PATCH 020/145] Create
 New-CsMainlineAttendantAppointmentBookingFlowApiDefinitionsJSON.md

---
 ...ppointmentBookingFlowApiDefinitionsJSON.md | 298 ++++++++++++++++++
 1 file changed, 298 insertions(+)
 create mode 100644 teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantAppointmentBookingFlowApiDefinitionsJSON.md

diff --git a/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantAppointmentBookingFlowApiDefinitionsJSON.md b/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantAppointmentBookingFlowApiDefinitionsJSON.md
new file mode 100644
index 0000000000..6403f8f04b
--- /dev/null
+++ b/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantAppointmentBookingFlowApiDefinitionsJSON.md
@@ -0,0 +1,298 @@
+---
+external help file: Microsoft.Rtc.Management.dll-Help.xml
+online version: https://learn.microsoft.com/powershell/module/teams/new-csmainlineattendantappointmentbookingflowapidefinitionsJSON
+applicable: Microsoft Teams
+title: New-CsMainLineAttendantAppointmentBookingFlowApiDefinitionsJSON
+author: tomkau
+ms.author: tomkau
+manager: bulenteg
+ms.reviewer:
+schema: 2.0.0
+---
+
+# New-CsMainlineAttendantAppointmentBookingFlow -ApiDefinition JSON Example
+
+## SYNOPSIS
+The [New-CsMainlineAttendantAppointmentBookingFlow](./New-CsMainlineAttendantAppointmentBookingFlow.md) -ApiDefinitions requires a JSON formatted response.
+
+## SYNTAX
+
+```
+{ 
+	"generateAuthToken" : { // Must be specified for "bearer_token_dynamic" 
+		"endpoint" : "<endpoint>", // For example, https://www.contoso.com/home?parameter1=<parameter1>&parameter2=<parameter2> 
+		"method_type": "GET" or "PUT" or "POST", 
+		"description" : "<description>", 
+
+		"query_strings" : { // Description of the query string parameters in the endpoint 
+			"parameter1" : "<parameter1>", 
+			"parameter2" : "<parameter2>" 
+			}, 
+
+		"headers" : { 
+			"Authorization" : "Basic <constant>" or "api-key <constant>" or "Bearer <constant>", // replace <constant> with an expected value 
+			"X-API-Key" : "API-Key" // Only applicable for "api_key" auth type. 
+			}, 
+
+		"response" : { // Response to 200 range of codes 
+			"token" : "<token>" // this token will be used for APIs with "bearer_token_dynamic" auth type 
+			} 
+	}, 
+
+	"getCallerDetails" : [ // Can specify multiple endpoints below to get caller details by phone number, ID, email, etc. 
+	{ 
+		"endpoint" : "<endpoint1>", // For example, https://www.contoso.com/home?parameter1=<parameter1>&parameter2=<parameter2> 
+		"method_type": "GET" or "PUT" or "POST", 
+		"description" : "<description>", 
+		
+		"query_strings" : { // Definition of the query string parameters in the endpoint 
+			"parameter1" : "<parameter1>", 
+			"parameter2" : "<parameter2>" 
+			}, 
+
+		"headers" : { 
+			"Authorization" : "Basic <constant>" or "api-key <constant>" or "Bearer <constant>" or "Bearer <token>", // replace <constant> with an expected value. <token> will be replaced by the response to generateAuthToken()  
+			"X-API-Key" : "API-Key" // Only applicable for "api_key" auth type. 
+			}, 
+
+		"body" : { // Sent as JSON payload 
+			"in_parameter1" : "<in_parameter1>", 
+			"in_parameter2" : "<in_parameter2>" 
+			}, 
+
+		"response" : { // Response to 200 range of codes 
+			"out_parameter1" : "<out_parameter1>", 
+			"out_parameter2" : "<out_parameter2>", 
+			"out_parameter3" : "<out_parameter3>" 
+			} 
+	}, 
+
+	{ 
+		"endpoint" : "<endpoint2>", 
+		"method_type": "GET" or "PUT" or "POST", 
+		"description" : "<description>", 
+		"query_strings" : { 
+			"parameter1" : "<parameter1>", 
+			"parameter2" : "<parameter2>" 
+			}, 
+
+		"headers" : { 
+			"Authorization" : "Basic <constant>" or "api-key <constant>" or "Bearer <constant>" or "Bearer <token>", 
+			"X-API-Key" : "API-Key" 
+			}, 
+
+		"body" : { 
+			"in_parameter1" : "<in_parameter1>", 
+			"in_parameter2" : "<in_parameter2>" 
+			}, 
+
+		"response" : { 
+			"out_parameter1" : "<out_parameter1>", 
+			"out_parameter2" : "<out_parameter2>", 
+			"out_parameter3" : "<out_parameter3>" 
+		} 
+	}
+	], 
+
+	"initiateCallerAuthentication" : [ // for SMS/email code, verification link 
+	{ 
+		"endpoint" : "<endpoint>", 
+		"method_type": "GET" or "PUT" or "POST", 
+		"description" : "<description>", 
+
+		"query_strings" : { 
+			"parameter1" : "<parameter1>", 
+			"parameter2" : "<parameter2>" 
+			}, 
+
+		"headers" : { 
+			"Authorization" : "Basic <constant>" or "api-key <constant>" or "Bearer <constant>" or "Bearer <token>", 
+			"X-API-Key" : "API-Key" // Only applicable for "api_key" auth type. 
+			}, 
+
+		"body" : { 
+			"in_parameter1" : "<in_parameter1>", // phone number, user ID, etc 
+			"in_parameter2" : "<in_parameter2>"  // session ID 
+			}, 
+
+		"response" : { 
+			"out_parameter1" : "<out_parameter1>",  // success/failure 
+		} 
+    } 
+	], 
+
+	"authenticateCaller" : [ // for SMS/email code, voiceprint, verification link, caller details 
+	{ 
+		"endpoint" : "<endpoint>", 
+		"method_type": "GET" or "PUT" or "POST", 
+		"description" : "<description>", 
+
+		"query_strings" : { 
+			"parameter1" : "<parameter1>", 
+			"parameter2" : "<parameter2>" 
+			}, 
+
+	"headers" : { 
+		"Authorization" : "Basic <constant>" or "api-key <constant>" or "Bearer <constant>" or "Bearer <token>", 
+		"X-API-Key" : "API-Key" // Only applicable for "api_key" auth type. 
+		}, 
+
+	"body" : { 
+		"in_parameter1" : "<in_parameter1>", // phone number, user ID, etc 
+		"in_parameter2" : "<in_parameter2>", // session ID 
+		"in_parameter3" : "<in_parameter3>", // VoicePrint payload or code 
+		}, 
+
+	"response" : { 
+		"out_parameter1" : "<out_parameter1>",  // success/failure 
+		} 
+	} 
+	], 
+
+	"getAvailableAppointmentTimeslots" : [ 
+	{ 
+		"endpoint" : "<endpoint>", 
+		"method_type": "GET" or "PUT" or "POST", 
+		"description" : "<description>", 
+
+		"query_strings" : { 
+			"parameter1" : "<parameter1>", 
+			"parameter2" : "<parameter2>" 
+			}, 
+
+		"headers" : { 
+			"Authorization" : "Basic <constant>" or "api-key <constant>" or "Bearer <constant>" or "Bearer <token>", 
+			"X-API-Key" : "API-Key" 
+			}, 
+
+		"body" : { 
+			"start_time" : "YYYY-MM-DDTHH:mm:ss.sssZ" // Timezone as configured on the AA config in ISO 8601 standard  
+			"end_time" : "YYYY-MM-DDTHH:mm:ss.sssZ" // Timezone as configured on the AA config in ISO 8601 standard 
+			"in_parameter3" : "<in_parameter3>", // optional parameters like appointment type, doctor name, etc 
+			"in_parameter4" : "<in_parameter4>", // number of results 
+			}, 
+
+		"response" : { 
+			"time_slots" : [
+			{ 
+				"start_time" : "YYYY-MM-DDTHH:mm:ss.sssZ" // Timezone as configured on the AA config in ISO 8601 standard 
+				"end_time" : "YYYY-MM-DDTHH:mm:ss.sssZ" // Timezone as configured on the AA config in ISO 8601 standard 
+				"opt_parameter1" : "<opt_parameter1>", // optional parameters like appointment type, doctor name, etc 
+			}, 
+
+			{ 
+				"start_time" : "YYYY-MM-DDTHH:mm:ss.sssZ" // Timezone as configured on the AA config in ISO 8601 standard 
+				"end_time" : "YYYY-MM-DDTHH:mm:ss.sssZ" // Timezone as configured on the AA config in ISO 8601 standard 
+				"opt_parameter1" : "<opt_parameter1>", // optional parameters like appointment type, doctor name, etc 
+			} 
+			], 
+
+			"out_parameter3" : "<out_parameter3>", 
+			"out_parameter4" : "<out_parameter4>", 
+			} 
+	} 
+	], 
+
+	"bookAppointment" : [ 
+	{ 
+		"endpoint" : "<endpoint>", 
+		"method_type": "GET" or "PUT" or "POST", 
+		"description" : "<description>", 
+
+		"query_strings" : { 
+			"parameter1" : "<parameter1>", 
+			"parameter2" : "<parameter2>" 
+			}, 
+
+		"headers" : { 
+			"Authorization" : "Basic <constant>" or "api-key <constant>" or "Bearer <constant>" or "Bearer <token>", 
+			"X-API-Key" : "API-Key" 
+			}, 
+
+		"body" : { 
+			"start_time" : "YYYY-MM-DDTHH:mm:ss.sssZ" // Timezone as configured on the AA config in ISO 8601 standard 
+			"end_time" : "YYYY-MM-DDTHH:mm:ss.sssZ" // Timezone as configured on the AA config in ISO 8601 standard 
+			"in_parameter3" : "<in_parameter3>", // optional parameters like appointment type, doctor name, etc 
+			"in_parameter4" : "<in_parameter4>", // patient id 
+			}, 
+
+		"response" : { 
+			"out_parameter1" : "<out_parameter1>", // success/failure 
+			"out_parameter2" : "<out_parameter2>", 
+			} 
+	} 
+	], 
+
+	"getUpcomingAppointments" : [ 
+	{ 
+		"endpoint" : "<endpoint>", 
+		"method_type": "GET" or "PUT" or "POST", 
+		"description" : "<description>", 
+
+		"query_strings" : { 
+			"parameter1" : "<parameter1>", 
+			"parameter2" : "<parameter2>" 
+			}, 
+
+		"headers : { 
+			"Authorization" : "Basic <constant>" or "api-key <constant>" or "Bearer <constant>" or "Bearer <token>", 
+			"X-API-Key" : "API-Key" 
+			}, 
+
+		"body" : { 
+			"in_parameter1" : "<in_parameter1>", // phone number, user ID, etc 
+			"in_parameter2" : "<in_parameter2>" 
+			}, 
+
+		"response" : { 
+			"time_slots" : [ 
+			{ 
+				"start_time" : "YYYY-MM-DDTHH:mm:ss.sssZ" // Timezone as configured on the AA config in ISO 8601 standard 
+				"end_time" : "YYYY-MM-DDTHH:mm:ss.sssZ" // Timezone as configured on the AA config in ISO 8601 standard 
+				"opt_parameter1" : "<opt_parameter1>" // optional parameters like appointment type, doctor name, etc 
+			}, 
+
+			{ 
+				"start_time" : "YYYY-MM-DDTHH:mm:ss.sssZ" // Timezone as configured on the AA config in ISO 8601 standard 
+				"end_time" : "YYYY-MM-DDTHH:mm:ss.sssZ" // Timezone as configured on the AA config in ISO 8601 standard 
+				"opt_parameter1" : "<opt_parameter1>" // optional parameters like appointment type, doctor name, etc 
+			} 
+			], 
+
+			"out_parameter3" : "<out_parameter3>", 
+			"out_parameter4" : "<out_parameter4>" 
+			} 
+	} 
+	] 
+} 
+```
+
+## PARAMETERS
+
+###  -ApiDefinitions
+The parameters used by the API - see the JSON example above.
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+
+Required: Yes
+Position: 0
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+## INPUTS
+
+## OUTPUTS
+
+### Microsoft.Rtc.Management.Hosted.CallQueue.Models.CallQueue
+
+## NOTES
+
+## RELATED LINKS
+
+
+

From 51bc5605e13bfa839db5b92122d4ee243051778b Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Tue, 5 Aug 2025 12:05:04 -0700
Subject: [PATCH 021/145] Create New-CsMainlineAttendantQuestionAnswerFlow.md

---
 ...w-CsMainlineAttendantQuestionAnswerFlow.md | 117 ++++++++++++++++++
 1 file changed, 117 insertions(+)
 create mode 100644 teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantQuestionAnswerFlow.md

diff --git a/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantQuestionAnswerFlow.md b/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantQuestionAnswerFlow.md
new file mode 100644
index 0000000000..6b178a7e40
--- /dev/null
+++ b/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantQuestionAnswerFlow.md
@@ -0,0 +1,117 @@
+---
+external help file: Microsoft.Rtc.Management.dll-Help.xml
+online version: https://learn.microsoft.com/powershell/module/teams/New-CsMainlineAttendantQuestionAnswerFlow 
+applicable: Microsoft Teams
+title: New-CsMainlineAttendantQuestionAnswerFlow
+author: tomkau
+ms.author: tomkau
+manager: bulenteg
+ms.reviewer:
+schema: 2.0.0
+---
+
+# New-CsMainlineAttendantQuestionAnswerFlow
+
+## SYNOPSIS
+Creates new Mainline Attendant question and answer (FAQ) flow
+
+## SYNTAX
+
+```
+New-CsMainlineAttendantQuestionAnswerFlow -Name <String> -Description <String>  -ApiAuthenticationType <basic | api_key | bearer_token_static | bearer_token_dynamic> -KnowledgeBase <String> [-Tenant <Guid>] [<CommonParameters>]
+```
+
+## DESCRIPTION
+The New-CsMainlineAttendantQuestionAnswerFlow cmdlet creates a question and answer connection that can be used with Mainline Attendant
+
+> [!CAUTION]
+> This cmdlet will only work for customers that are participating in the Voice Applications private preview for these features. General Availability for this functionality has not been determined at this time.
+
+## EXAMPLES
+
+
+## PARAMETERS
+
+### -Name
+The name of the question and answer flow
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+applicable: Microsoft Teams
+
+Required: True
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -Description
+The description for the question and answer flow
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+applicable: Microsoft Teams
+
+Required: True
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+###  -ApiAuthenticationType
+The method of authentication used by the API
+
+PARAVALUES: basic | api_key | bearer_token_static | bearer_token_dynamic
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+applicable: Microsoft Teams
+
+Required: True
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+###  -KnowledgeBase
+The knowledge base definition
+
+The parameters used by the API
+
+For an example, see [New-CsMainlineAttendantQuestionAnswerFlow -KnowledgeBase](./New-CsMainlineAttendantQuestionAnswerFlowKnowledgeBaseJSON.md)
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+applicable: Microsoft Teams
+
+Required: True
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### CommonParameters
+This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).
+
+## INPUTS
+
+## OUTPUTS
+
+### Microsoft.Rtc.Management.Hosted.CallQueue.Models.CallQueue
+
+## NOTES
+
+## RELATED LINKS
+

From fe9d202ca212fa9883049ca3a09ba24102b08117 Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Tue, 5 Aug 2025 12:05:43 -0700
Subject: [PATCH 022/145] Create
 New-CsMainlineAttendantQuestionAnswerFlowKnowledgeBaseJSON.md

---
 ...dantQuestionAnswerFlowKnowledgeBaseJSON.md | 131 ++++++++++++++++++
 1 file changed, 131 insertions(+)
 create mode 100644 teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantQuestionAnswerFlowKnowledgeBaseJSON.md

diff --git a/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantQuestionAnswerFlowKnowledgeBaseJSON.md b/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantQuestionAnswerFlowKnowledgeBaseJSON.md
new file mode 100644
index 0000000000..94939608d0
--- /dev/null
+++ b/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantQuestionAnswerFlowKnowledgeBaseJSON.md
@@ -0,0 +1,131 @@
+---
+external help file: Microsoft.Rtc.Management.dll-Help.xml
+online version: https://learn.microsoft.com/powershell/module/teams/new-csmainlineattendantquestionanswerflowknowledgebaseJSON
+applicable: Microsoft Teams
+title: New-CsMainlineAttendantQuestionAnswerFlowKnowledgeBaseJSON
+author: tomkau
+ms.author: tomkau
+manager: bulenteg
+ms.reviewer:
+schema: 2.0.0
+---
+
+# New-CsMainlineAttendantQuestionAnswerFlow -KnowledgeBase JSON Example
+
+## SYNOPSIS
+The [New-CsMainlineAttendantQuestionAnswerFlow](./New-CsMainlineAttendantQuestionAnswerFlow.md) -Knowledge requires a path to a JSON formatted response.
+
+## SYNTAX
+
+```
+[
+	{
+		"address_type" : "local_file",
+		"document_address" : "<local_address>", // provide full path to the local address
+		"description" : "<description>"
+		
+	},
+	{
+		"address_type" : "webpage",
+		"document_address" : "<web_address>", // provide full path to the webpage
+		"description" : "<description>"
+		
+	},
+	{
+		"address_type" : "api_endpoint",
+		"description" : "<description>",
+		"api_specification" : {
+			"generateAuthToken" : { // Must be specified for "bearer_token_dynamic"
+				"endpoint" : "<endpoint>", // For example, https://www.contoso.com/home?parameter1=<parameter1>&parameter2=<parameter2>
+				"method_type": "GET" or "PUT" or "POST",
+				"description" : "<description>",
+				"query_strings" : { // Description of the query string parameters in the endpoint
+					"parameter1" : "<parameter1>",
+					"parameter2" : "<parameter2>"
+				},
+				"headers" : {
+					"Authorization" : "Basic <constant>" or "api-key <constant>" or "Bearer <constant>", // replace <constant> with an expected value
+					"X-API-Key" : "API-Key" // Only applicable for "api_key" auth type.
+				},
+				"response" : { // Response to 200 range of codes
+					"token" : "<token>" // this token will be used for APIs with "bearer_token_dynamic" auth type
+				}
+			},
+			"getResults1" : {
+				"endpoint" : "<endpoint>", // For example, https://www.contoso.com/home?parameter1=<parameter1>&parameter2=<parameter2>
+				"method_type": "GET" or "PUT" or "POST",
+				"description" : "<description>",
+				"query_strings" : { // Definition of the query string parameters in the endpoint
+					"parameter1" : "<parameter1>",
+					"parameter2" : "<parameter2>"
+				},
+				"headers" : {
+					"Authorization" : "Basic <constant>" or "api-key <constant>" or "Bearer <constant>" or "Bearer <token>", // replace <constant> with an expected value. <token> will be replaced by the response to generateAuthToken() 
+					"X-API-Key" : "API-Key" // Only applicable for "api_key" auth type.
+				},
+				"body" : { // Sent as JSON payload
+					"in_parameter1" : "<in_parameter1>",
+					"in_parameter2" : "<in_parameter2>"
+				},
+				"response" : { // Response to 200 range of codes
+					"out_parameter1" : "<out_parameter1>",
+					"out_parameter2" : "<out_parameter2>",
+					"out_parameter3" : "<out_parameter3>"
+				}
+			},
+			"getResults2" : {
+				"endpoint" : "<endpoint>", // For example, https://www.contoso.com/home?parameter1=<parameter1>&parameter2=<parameter2>
+				"method_type": "GET" or "PUT" or "POST"
+				"description" : "<description>",
+				"query_strings" : { // Definition of the query string parameters in the endpoint
+					"parameter1" : "<parameter1>",
+					"parameter2" : "<parameter2>"
+				},
+				"headers" : {
+					"Authorization" : "Basic <constant>" or "api-key <constant>" or "Bearer <constant>" or "Bearer <token>", // replace <constant> with an expected value. <token> will be replaced by the response to generateAuthToken() 
+					"X-API-Key" : "API-Key" // Only applicable for "api_key" auth type.
+				},
+				"body" : { // Sent as JSON payload
+					"in_parameter1" : "<in_parameter1>",
+					"in_parameter2" : "<in_parameter2>"
+				},
+				"response" : { // Response to 200 range of codes
+					"out_parameter1" : "<out_parameter1>",
+					"out_parameter2" : "<out_parameter2>",
+					"out_parameter3" : "<out_parameter3>"
+				}
+			}
+		}
+	}
+]
+```
+
+## PARAMETERS
+
+###  -Knowledgebase
+The parameters used by the Knowledgebase - see the JSON example above.
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+
+Required: Yes
+Position: 0
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+## INPUTS
+
+## OUTPUTS
+
+### Microsoft.Rtc.Management.Hosted.CallQueue.Models.CallQueue
+
+## NOTES
+
+## RELATED LINKS
+
+
+

From d00f112c3917d32c1dc7a644ca94fcd9609dc2f8 Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Tue, 5 Aug 2025 12:06:30 -0700
Subject: [PATCH 023/145] Create
 Remove-CsMainlineAttendantAppointmentBookingFlow.md

---
 ...MainlineAttendantAppointmentBookingFlow.md | 86 +++++++++++++++++++
 1 file changed, 86 insertions(+)
 create mode 100644 teams/teams-ps/MicrosoftTeams/Remove-CsMainlineAttendantAppointmentBookingFlow.md

diff --git a/teams/teams-ps/MicrosoftTeams/Remove-CsMainlineAttendantAppointmentBookingFlow.md b/teams/teams-ps/MicrosoftTeams/Remove-CsMainlineAttendantAppointmentBookingFlow.md
new file mode 100644
index 0000000000..e38af8fd7a
--- /dev/null
+++ b/teams/teams-ps/MicrosoftTeams/Remove-CsMainlineAttendantAppointmentBookingFlow.md
@@ -0,0 +1,86 @@
+---
+external help file: Microsoft.Rtc.Management.dll-Help.xml
+online version: https://learn.microsoft.com/powershell/module/teams/Remove-CsMainlineAttendantAppointmentBookingFlow
+applicable: Microsoft Teams
+title: Remove-CsMainlineAttendantAppointmentBookingFlow
+schema: 2.0.0
+ms.reviewer:
+manager: bulenteg
+author: tomkau
+ms.author: tomkau
+ms.reviewer: williamlooney
+---
+
+# Remove-CsMainlineAttendantAppointmentBookingFlow
+
+## SYNOPSIS
+The Remove-CsMainlineAttendantAppointmentBookingFlow cmdlet deletes an existing Mainline attendant appointment booking flow.
+
+## SYNTAX
+
+```
+Remove-CsMainlineAttendantAppointmentBookingFlow -Identity <Guid> [-Tenant <Guid>] [<CommonParameters>]
+```
+
+## DESCRIPTION
+The Remove-CsMainlineAttendantAppointmentBookingFlow cmdlet deletes an existing Mainline attendant appointment booking flow.
+
+## EXAMPLES
+
+### -------------------------- Example 1 --------------------------
+```
+Remove-CsMainlineAttendantAppointmentBookingFlow -Identity 5e3a575e-1faa-49ff-83c2-5cf1c36c0e01
+```
+
+This example removes the Mainline attendant appointment booking flow with the identity 5e3a575e-1faa-49ff-83c2-5cf1c36c0e01. If no appointment booking flow exists with the identity 5e3a575e-1faa-49ff-83c2-5cf1c36c0e01, then this example generates an error.
+
+## PARAMETERS
+
+### -Identity
+PARAMVALUE: Guid
+
+```yaml
+Type: Guid
+Parameter Sets: (All)
+Aliases:
+applicable: Microsoft Teams
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -Tenant
+PARAMVALUE: Guid
+
+```yaml
+Type: Guid
+Parameter Sets: (All)
+Aliases:
+applicable: Microsoft Teams
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### CommonParameters
+This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).
+
+## INPUTS
+
+### Identity
+Represents the unique identifier of a Mainline attendant appointment booking flow.
+
+## OUTPUTS
+
+### Microsoft.Rtc.Management.Hosted.CallQueue.Models.CallQueue
+
+## NOTES
+
+## RELATED LINKS
+

From 6449460c994c6003e16ae60f2ef5e954d75619df Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Tue, 5 Aug 2025 12:07:15 -0700
Subject: [PATCH 024/145] Create
 Remove-CsMainlineAttendantQuestionAnswerFlow.md

---
 ...e-CsMainlineAttendantQuestionAnswerFlow.md | 86 +++++++++++++++++++
 1 file changed, 86 insertions(+)
 create mode 100644 teams/teams-ps/MicrosoftTeams/Remove-CsMainlineAttendantQuestionAnswerFlow.md

diff --git a/teams/teams-ps/MicrosoftTeams/Remove-CsMainlineAttendantQuestionAnswerFlow.md b/teams/teams-ps/MicrosoftTeams/Remove-CsMainlineAttendantQuestionAnswerFlow.md
new file mode 100644
index 0000000000..d57095be09
--- /dev/null
+++ b/teams/teams-ps/MicrosoftTeams/Remove-CsMainlineAttendantQuestionAnswerFlow.md
@@ -0,0 +1,86 @@
+---
+external help file: Microsoft.Rtc.Management.dll-Help.xml
+online version: https://learn.microsoft.com/powershell/module/teams/Remove-CsMainlineAttendantQuestionAnswerFlow
+applicable: Microsoft Teams
+title: Remove-CsMainlineAttendantQuestionAnswerFlow
+schema: 2.0.0
+ms.reviewer:
+manager: bulenteg
+author: tomkau
+ms.author: tomkau
+ms.reviewer: williamlooney
+---
+
+# Remove-CsMainlineAttendantQuestionAnswerFlow
+
+## SYNOPSIS
+The Remove-CsMainlineAttendantQuestionAnswerFlow cmdlet deletes an existing Mainline attendant question and answer flow.
+
+## SYNTAX
+
+```
+Remove-CsMainlineAttendantQuestionAnswerFlow -Identity <Guid> [-Tenant <Guid>] [<CommonParameters>]
+```
+
+## DESCRIPTION
+The Remove-CsMainlineAttendantQuestionAnswerFlow cmdlet deletes an existing Mainline attendant question and answer flow.
+
+## EXAMPLES
+
+### -------------------------- Example 1 --------------------------
+```
+Remove-CsMainlineAttendantQuestionAnswerFlow -Identity 5e3a575e-1faa-49ff-83c2-5cf1c36c0e01
+```
+
+This example removes the Mainline attendant question and answer flow with the identity 5e3a575e-1faa-49ff-83c2-5cf1c36c0e01. If no question and answer flow exists with the identity 5e3a575e-1faa-49ff-83c2-5cf1c36c0e01, then this example generates an error.
+
+## PARAMETERS
+
+### -Identity
+PARAMVALUE: Guid
+
+```yaml
+Type: Guid
+Parameter Sets: (All)
+Aliases:
+applicable: Microsoft Teams
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -Tenant
+PARAMVALUE: Guid
+
+```yaml
+Type: Guid
+Parameter Sets: (All)
+Aliases:
+applicable: Microsoft Teams
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### CommonParameters
+This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).
+
+## INPUTS
+
+### Identity
+Represents the unique identifier of a Mainline attendant question and answer flow.
+
+## OUTPUTS
+
+### Microsoft.Rtc.Management.Hosted.CallQueue.Models.CallQueue
+
+## NOTES
+
+## RELATED LINKS
+

From df61aa5afcdeb26556d33b1e005d3b0f73d0b522 Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Tue, 5 Aug 2025 12:07:47 -0700
Subject: [PATCH 025/145] Create
 Set-CsMainlineAttendantAppointmentBookingFlow.md

---
 ...MainlineAttendantAppointmentBookingFlow.md | 152 ++++++++++++++++++
 1 file changed, 152 insertions(+)
 create mode 100644 teams/teams-ps/MicrosoftTeams/Set-CsMainlineAttendantAppointmentBookingFlow.md

diff --git a/teams/teams-ps/MicrosoftTeams/Set-CsMainlineAttendantAppointmentBookingFlow.md b/teams/teams-ps/MicrosoftTeams/Set-CsMainlineAttendantAppointmentBookingFlow.md
new file mode 100644
index 0000000000..bef2833cb8
--- /dev/null
+++ b/teams/teams-ps/MicrosoftTeams/Set-CsMainlineAttendantAppointmentBookingFlow.md
@@ -0,0 +1,152 @@
+---
+external help file: Microsoft.Rtc.Management.dll-Help.xml
+online version: https://learn.microsoft.com/powershell/module/teams/Set-CsMainlineAttendantAppointmentBookingFlow
+applicable: Microsoft Teams
+title: Set-CsMainlineAttendantAppointmentBookingFlow
+author: tomkau
+ms.author: tomkau
+manager: bulenteg
+ms.reviewer:
+schema: 2.0.0
+---
+
+# Set-CsMainlineAttendantAppointmentBookingFlow
+
+## SYNOPSIS
+Changes an existing Mainline Attendant appointment booking flow
+
+## SYNTAX
+
+```
+Set-CsMainlineAttendantAppointmentBookingFlow -Identity <String> [-Name <String>] [-Description <String>] [-CallerAuthenticationMethod <sms | email | verification_link | voiceprint | user_details>] [-ApiAuthenticationType <basic | api_key | bearer_token_static | bearer_token_dynamic>] [-ApiDefinitions <String>] [-Tenant <Guid>] [<CommonParameters>]
+```
+
+## DESCRIPTION
+The Set-CsMainlineAttendantAppointmentBookingFlow cmdlet changes an existing appointment booking flow that is used with Mainline Attendant
+
+> [!CAUTION]
+> This cmdlet will only work for customers that are participating in the Voice Applications private preview for these features. General Availability for this functionality has not been determined at this time.
+
+## EXAMPLES
+
+
+## PARAMETERS
+
+### -Identity
+The unique Id of the appointment booking flow to change
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+applicable: Microsoft Teams
+
+Required: True
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -Name
+The name of the appointment booking flow
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+applicable: Microsoft Teams
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -Description
+The description for the appointment booking flow
+
+Limit: 500 characters. 
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+applicable: Microsoft Teams
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+###  -CallerAuthenticationMethod
+The method by which the caller is authenticated
+
+PARAVALUES: sms | email | verification_link | voiceprint | user_details
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+applicable: Microsoft Teams
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+###  -ApiAuthenticationType
+The method of authentication used by the API
+
+PARAVALUES: basic | api_key | bearer_token_static | bearer_token_dynamic
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+applicable: Microsoft Teams
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+###  -ApiDefinitions
+The parameters used by the API
+
+For an example, see [New-CsMainlineAttendantAppointBookingFlow -ApiDefinitions](./New-CsMainlineAttendantAppointmentBookingFlowApiDefinitionsJSON.md)
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+applicable: Microsoft Teams
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### CommonParameters
+This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).
+
+## INPUTS
+
+## OUTPUTS
+
+### Microsoft.Rtc.Management.Hosted.CallQueue.Models.CallQueue
+
+## NOTES
+
+## RELATED LINKS
+
+

From 8b4ae154944343983f5c4dbd57de962b70ab6774 Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Tue, 5 Aug 2025 12:08:22 -0700
Subject: [PATCH 026/145] Create Set-CsMainlineAttendantQuestionAnswerFlow.md

---
 ...t-CsMainlineAttendantQuestionAnswerFlow.md | 134 ++++++++++++++++++
 1 file changed, 134 insertions(+)
 create mode 100644 teams/teams-ps/MicrosoftTeams/Set-CsMainlineAttendantQuestionAnswerFlow.md

diff --git a/teams/teams-ps/MicrosoftTeams/Set-CsMainlineAttendantQuestionAnswerFlow.md b/teams/teams-ps/MicrosoftTeams/Set-CsMainlineAttendantQuestionAnswerFlow.md
new file mode 100644
index 0000000000..68cb82c876
--- /dev/null
+++ b/teams/teams-ps/MicrosoftTeams/Set-CsMainlineAttendantQuestionAnswerFlow.md
@@ -0,0 +1,134 @@
+---
+external help file: Microsoft.Rtc.Management.dll-Help.xml
+online version: https://learn.microsoft.com/powershell/module/teams/Set-CsMainlineAttendantQuestionAnswerFlow 
+applicable: Microsoft Teams
+title: Set-CsMainlineAttendantQuestionAnswerFlow
+author: tomkau
+ms.author: tomkau
+manager: bulenteg
+ms.reviewer:
+schema: 2.0.0
+---
+
+# Set-CsMainlineAttendantQuestionAnswerFlow
+
+## SYNOPSIS
+Changes an existing Mainline Attendant question and answer (FAQ) flow
+
+## SYNTAX
+
+```
+Set-CsMainlineAttendantQuestionAnswerFlow -Identity <String> [-Name <String>] [-Description <String>] [-ApiAuthenticationType <basic | api_key | bearer_token_static | bearer_token_dynamic>] [-KnowledgeBase <String>] [-Tenant <Guid>] [<CommonParameters>]
+```
+
+## DESCRIPTION
+The Set-CsMainlineAttendantQuestionAnswerFlow cmdlet changes an existing question and answer connection that can be used with Mainline Attendant
+
+> [!CAUTION]
+> This cmdlet will only work for customers that are participating in the Voice Applications private preview for these features. General Availability for this functionality has not been determined at this time.
+
+## EXAMPLES
+
+
+## PARAMETERS
+
+### -Identity
+The unique identifier for the question and answer flow.
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+applicable: Microsoft Teams
+
+Required: True
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -Name
+The name of the question and answer flow
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+applicable: Microsoft Teams
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -Description
+The description for the question and answer flow
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+applicable: Microsoft Teams
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+###  -ApiAuthenticationType
+The method of authentication used by the API
+
+PARAVALUES: basic | api_key | bearer_token_static | bearer_token_dynamic
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+applicable: Microsoft Teams
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+###  -KnowledgeBase
+The knowledge base definition
+
+The parameters used by the API
+
+For an example, see [New-CsMainlineAttendantQuestionAnswerFlow -KnowledgeBase](./New-CsMainlineAttendantQuestionAnswerFlowKnowledgeBaseJSON.md)
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+applicable: Microsoft Teams
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### CommonParameters
+This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).
+
+## INPUTS
+
+## OUTPUTS
+
+### Microsoft.Rtc.Management.Hosted.CallQueue.Models.CallQueue
+
+## NOTES
+
+## RELATED LINKS
+
+

From 8b43f42b8d0b766fd5819d4835a36d6e0e995e1b Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Tue, 5 Aug 2025 12:45:36 -0700
Subject: [PATCH 027/145] Update
 Get-CsMainlineAttendantAppointmentBookingFlow.md

---
 ...MainlineAttendantAppointmentBookingFlow.md | 22 ++++++-------------
 1 file changed, 7 insertions(+), 15 deletions(-)

diff --git a/teams/teams-ps/MicrosoftTeams/Get-CsMainlineAttendantAppointmentBookingFlow.md b/teams/teams-ps/MicrosoftTeams/Get-CsMainlineAttendantAppointmentBookingFlow.md
index f5161eb3d9..5bf3819350 100644
--- a/teams/teams-ps/MicrosoftTeams/Get-CsMainlineAttendantAppointmentBookingFlow.md
+++ b/teams/teams-ps/MicrosoftTeams/Get-CsMainlineAttendantAppointmentBookingFlow.md
@@ -1,14 +1,14 @@
 ---
-external help file: Microsoft.Rtc.Management.dll-Help.xml
-online version: https://learn.microsoft.com/powershell/module/teams/Get-CsMainlineAttendantAppointmentBookingFlow
 applicable: Microsoft Teams
-title: Get-CsMainlineAttendantAppointmentBookingFlow
-schema: 2.0.0
-ms.reviewer:
-manager: bulenteg
 author: tomkau
+external help file: Microsoft.Rtc.Management.dll-Help.xml
+Locale: en-US
+manager: bulenteg
+Module Name: MicrosoftTeams
 ms.author: tomkau
-ms.reviewer: williamlooney
+online version: https://learn.microsoft.com/powershell/module/teams/Get-CsMainlineAttendantAppointmentBookingFlow
+schema: 2.0.0
+title: Get-CsMainlineAttendantAppointmentBookingFlow
 ---
 
 # Get-CsMainlineAttendantAppointmentBookingFlow
@@ -50,7 +50,6 @@ PARAMVALUE: Guid
 Type: Guid
 Parameter Sets: (All)
 Aliases:
-applicable: Microsoft Teams
 
 Required: False
 Position: Named
@@ -66,7 +65,6 @@ PARAMVALUE: Guid
 Type: Guid
 Parameter Sets: (All)
 Aliases:
-applicable: Microsoft Teams
 
 Required: False
 Position: Named
@@ -84,7 +82,6 @@ If a number greater than 100 is supplied, the request will fail.
 Type: Int32
 Parameter Sets: (All)
 Aliases:
-applicable: Microsoft Teams
 
 Required: False
 Position: Named
@@ -100,7 +97,6 @@ The Skip parameter skips the first N appointment flows. It is intended to be use
 Type: Int32
 Parameter Sets: (All)
 Aliases:
-applicable: Microsoft Teams
 
 Required: False
 Position: Named
@@ -116,7 +112,6 @@ The ExcludeContent parameter only displays the Name and Id of the appointment fl
 Type: SwitchParameter
 Parameter Sets: (All)
 Aliases:
-applicable: Microsoft Teams
 
 Required: False
 Position: Named
@@ -132,7 +127,6 @@ The Sort parameter specifies the property used to sort.
 Type: String
 Parameter Sets: (All)
 Aliases:
-applicable: Microsoft Teams
 
 Required: True
 Position: Named
@@ -148,7 +142,6 @@ The Descending parameter sorts appointment booking flows in descending order
 Type: SwitchParameter
 Parameter Sets: (All)
 Aliases:
-applicable: Microsoft Teams
 
 Required: False
 Position: Named
@@ -164,7 +157,6 @@ The NameFilter parameter returns appointment booking flows where the name contai
 Type: String
 Parameter Sets: (All)
 Aliases:
-applicable: Microsoft Teams
 
 Required: True
 Position: Named

From 49bf03d20f2b82a9011e31047c093691b05583d4 Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Tue, 5 Aug 2025 12:47:38 -0700
Subject: [PATCH 028/145] Update Get-CsMainlineAttendantFlow.md

---
 .../MicrosoftTeams/Get-CsMainlineAttendantFlow.md | 15 ++++++---------
 1 file changed, 6 insertions(+), 9 deletions(-)

diff --git a/teams/teams-ps/MicrosoftTeams/Get-CsMainlineAttendantFlow.md b/teams/teams-ps/MicrosoftTeams/Get-CsMainlineAttendantFlow.md
index 3b01b0dd8f..8f3fe8f1cc 100644
--- a/teams/teams-ps/MicrosoftTeams/Get-CsMainlineAttendantFlow.md
+++ b/teams/teams-ps/MicrosoftTeams/Get-CsMainlineAttendantFlow.md
@@ -1,13 +1,13 @@
----
-external help file: Microsoft.Rtc.Management.dll-Help.xml
-online version: https://learn.microsoft.com/powershell/module/teams/get-csmainlineattendantflow
 applicable: Microsoft Teams
-title: Get-CsMainlineAttendantFlow
 author: tomkau
-ms.author: tomkau
+external help file: Microsoft.Rtc.Management.dll-Help.xml
+Locale: en-US
 manager: bulenteg
-ms.reviewer:
+Module Name: MicrosoftTeams
+ms.author: tomkau
+online version: https://learn.microsoft.com/powershell/module/microsoftteams/Get-CsMainlineAttendantFlow
 schema: 2.0.0
+title: Get-CsMainlineAttendantFlow
 ---
 
 # Get-CsMainlineAttendantFlow 
@@ -66,7 +66,6 @@ The Mainline Attendant configuration Id
 Type: String
 Parameter Sets: (All)
 Aliases:
-applicable: Microsoft Teams
 
 Required: False
 Position: Named
@@ -84,7 +83,6 @@ PARAMVALUE: Appointment | QuestionAndAnswer
 Type: String
 Parameter Sets: (All)
 Aliases:
-applicable: Microsoft Teams
 
 Required: False
 Position: Named
@@ -100,7 +98,6 @@ The Mainline Attendant flow id
 Type: String
 Parameter Sets: (All)
 Aliases:
-applicable: Microsoft Teams
 
 Required: False
 Position: Named

From a6da2ba6299762e2164fc2895e2a5421ffcdc27c Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Tue, 5 Aug 2025 12:48:00 -0700
Subject: [PATCH 029/145] Update
 Get-CsMainlineAttendantAppointmentBookingFlow.md

---
 .../Get-CsMainlineAttendantAppointmentBookingFlow.md            | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/teams/teams-ps/MicrosoftTeams/Get-CsMainlineAttendantAppointmentBookingFlow.md b/teams/teams-ps/MicrosoftTeams/Get-CsMainlineAttendantAppointmentBookingFlow.md
index 5bf3819350..956ca2bcef 100644
--- a/teams/teams-ps/MicrosoftTeams/Get-CsMainlineAttendantAppointmentBookingFlow.md
+++ b/teams/teams-ps/MicrosoftTeams/Get-CsMainlineAttendantAppointmentBookingFlow.md
@@ -6,7 +6,7 @@ Locale: en-US
 manager: bulenteg
 Module Name: MicrosoftTeams
 ms.author: tomkau
-online version: https://learn.microsoft.com/powershell/module/teams/Get-CsMainlineAttendantAppointmentBookingFlow
+online version: https://learn.microsoft.com/powershell/module/microsoftteams/Get-CsMainlineAttendantAppointmentBookingFlow
 schema: 2.0.0
 title: Get-CsMainlineAttendantAppointmentBookingFlow
 ---

From edca08e623f6b6f9d7ee13b34c422fce88bfc72c Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Tue, 5 Aug 2025 12:50:46 -0700
Subject: [PATCH 030/145] Update Get-CsMainlineAttendantQuestionAnswerFlow.md

---
 ...t-CsMainlineAttendantQuestionAnswerFlow.md | 22 ++++++-------------
 1 file changed, 7 insertions(+), 15 deletions(-)

diff --git a/teams/teams-ps/MicrosoftTeams/Get-CsMainlineAttendantQuestionAnswerFlow.md b/teams/teams-ps/MicrosoftTeams/Get-CsMainlineAttendantQuestionAnswerFlow.md
index fcaf4470cd..2537deac74 100644
--- a/teams/teams-ps/MicrosoftTeams/Get-CsMainlineAttendantQuestionAnswerFlow.md
+++ b/teams/teams-ps/MicrosoftTeams/Get-CsMainlineAttendantQuestionAnswerFlow.md
@@ -1,14 +1,14 @@
 ---
-external help file: Microsoft.Rtc.Management.dll-Help.xml
-online version: https://learn.microsoft.com/powershell/module/teams/Get-CsMainlineAttendantQuestionAnswerFlow
 applicable: Microsoft Teams
-title: Get-CsMainlineAttendantQuestionAnswerFlow
-schema: 2.0.0
-ms.reviewer:
-manager: bulenteg
 author: tomkau
+external help file: Microsoft.Rtc.Management.dll-Help.xml
+Locale: en-US
+manager: bulenteg
+Module Name: MicrosoftTeams
 ms.author: tomkau
-ms.reviewer: williamlooney
+online version: https://learn.microsoft.com/powershell/module/microsoftteams/Get-CsMainlineAttendantQuestionAnswerFlow
+schema: 2.0.0
+title: Get-CsMainlineAttendantQuestionAnswerFlow
 ---
 
 # Get-CsMainlineAttendantQuestionAnswerFlow
@@ -50,7 +50,6 @@ PARAMVALUE: Guid
 Type: Guid
 Parameter Sets: (All)
 Aliases:
-applicable: Microsoft Teams
 
 Required: False
 Position: Named
@@ -66,7 +65,6 @@ PARAMVALUE: Guid
 Type: Guid
 Parameter Sets: (All)
 Aliases:
-applicable: Microsoft Teams
 
 Required: False
 Position: Named
@@ -84,7 +82,6 @@ If a number greater than 100 is supplied, the request will fail.
 Type: Int32
 Parameter Sets: (All)
 Aliases:
-applicable: Microsoft Teams
 
 Required: False
 Position: Named
@@ -100,7 +97,6 @@ The Skip parameter skips the first N appointment flows. It is intended to be use
 Type: Int32
 Parameter Sets: (All)
 Aliases:
-applicable: Microsoft Teams
 
 Required: False
 Position: Named
@@ -116,7 +112,6 @@ The ExcludeContent parameter only displays the Name and Id of the question and a
 Type: SwitchParameter
 Parameter Sets: (All)
 Aliases:
-applicable: Microsoft Teams
 
 Required: False
 Position: Named
@@ -132,7 +127,6 @@ The Sort parameter specifies the property used to sort.
 Type: String
 Parameter Sets: (All)
 Aliases:
-applicable: Microsoft Teams
 
 Required: True
 Position: Named
@@ -148,7 +142,6 @@ The Descending parameter sorts appointment booking flows in descending order
 Type: SwitchParameter
 Parameter Sets: (All)
 Aliases:
-applicable: Microsoft Teams
 
 Required: False
 Position: Named
@@ -164,7 +157,6 @@ The NameFilter parameter returns question and answer booking flows where the nam
 Type: String
 Parameter Sets: (All)
 Aliases:
-applicable: Microsoft Teams
 
 Required: True
 Position: Named

From dfaa78439317050e12f82920719ed6856a773612 Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Tue, 5 Aug 2025 12:52:46 -0700
Subject: [PATCH 031/145] Update
 New-CsMainlineAttendantAppointmentBookingFlow.md

---
 ...-CsMainlineAttendantAppointmentBookingFlow.md | 16 ++++++----------
 1 file changed, 6 insertions(+), 10 deletions(-)

diff --git a/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantAppointmentBookingFlow.md b/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantAppointmentBookingFlow.md
index f55a7ea3db..b91b31e886 100644
--- a/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantAppointmentBookingFlow.md
+++ b/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantAppointmentBookingFlow.md
@@ -1,13 +1,14 @@
 ---
-external help file: Microsoft.Rtc.Management.dll-Help.xml
-online version: https://learn.microsoft.com/powershell/module/teams/new-csmainlineattendantappointmentbookingflow
 applicable: Microsoft Teams
-title: New-CsMainlineAttendantAppointmentBookingFlow
 author: tomkau
-ms.author: tomkau
+external help file: Microsoft.Rtc.Management.dll-Help.xml
+Locale: en-US
 manager: bulenteg
-ms.reviewer:
+Module Name: MicrosoftTeams
+ms.author: tomkau
+online version: https://learn.microsoft.com/powershell/module/microsoftteams/New-CsMainlineAttendantAppointmentBookingFlow
 schema: 2.0.0
+title: New-CsMainlineAttendantAppointmentBookingFlow
 ---
 
 # New-CsMainlineAttendantAppointmentBookingFlow
@@ -39,7 +40,6 @@ The name of the appointment booking flow
 Type: String
 Parameter Sets: (All)
 Aliases:
-applicable: Microsoft Teams
 
 Required: True
 Position: Named
@@ -57,7 +57,6 @@ Limit: 500 characters.
 Type: String
 Parameter Sets: (All)
 Aliases:
-applicable: Microsoft Teams
 
 Required: True
 Position: Named
@@ -75,7 +74,6 @@ PARAVALUES: sms | email | verification_link | voiceprint | user_details
 Type: String
 Parameter Sets: (All)
 Aliases:
-applicable: Microsoft Teams
 
 Required: True
 Position: Named
@@ -93,7 +91,6 @@ PARAVALUES: basic | api_key | bearer_token_static | bearer_token_dynamic
 Type: String
 Parameter Sets: (All)
 Aliases:
-applicable: Microsoft Teams
 
 Required: True
 Position: Named
@@ -111,7 +108,6 @@ For an example, see [New-CsMainlineAttendantAppointBookingFlow -ApiDefinitions](
 Type: String
 Parameter Sets: (All)
 Aliases:
-applicable: Microsoft Teams
 
 Required: True
 Position: Named

From df30be9f7b43448e0504360201c8dbf343d5e06f Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Tue, 5 Aug 2025 12:54:14 -0700
Subject: [PATCH 032/145] Update
 New-CsMainlineAttendantAppointmentBookingFlowApiDefinitionsJSON.md

---
 ...tendantAppointmentBookingFlowApiDefinitionsJSON.md | 11 ++++++-----
 1 file changed, 6 insertions(+), 5 deletions(-)

diff --git a/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantAppointmentBookingFlowApiDefinitionsJSON.md b/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantAppointmentBookingFlowApiDefinitionsJSON.md
index 6403f8f04b..22713b4957 100644
--- a/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantAppointmentBookingFlowApiDefinitionsJSON.md
+++ b/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantAppointmentBookingFlowApiDefinitionsJSON.md
@@ -1,13 +1,14 @@
 ---
-external help file: Microsoft.Rtc.Management.dll-Help.xml
-online version: https://learn.microsoft.com/powershell/module/teams/new-csmainlineattendantappointmentbookingflowapidefinitionsJSON
 applicable: Microsoft Teams
-title: New-CsMainLineAttendantAppointmentBookingFlowApiDefinitionsJSON
 author: tomkau
-ms.author: tomkau
+external help file: Microsoft.Rtc.Management.dll-Help.xml
+Locale: en-US
 manager: bulenteg
-ms.reviewer:
+Module Name: MicrosoftTeams
+ms.author: tomkau
+online version: https://learn.microsoft.com/powershell/module/microsoftteams/New-CsMainLineAttendantAppointmentBookingFlowApiDefinitionsJSON
 schema: 2.0.0
+title: New-CsMainLineAttendantAppointmentBookingFlowApiDefinitionsJSON
 ---
 
 # New-CsMainlineAttendantAppointmentBookingFlow -ApiDefinition JSON Example

From 7a548962407264edb560c9fe66a0501ff3d6701d Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Tue, 5 Aug 2025 12:55:14 -0700
Subject: [PATCH 033/145] Update New-CsMainlineAttendantQuestionAnswerFlow.md

---
 .../New-CsMainlineAttendantQuestionAnswerFlow.md  | 15 ++++++---------
 1 file changed, 6 insertions(+), 9 deletions(-)

diff --git a/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantQuestionAnswerFlow.md b/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantQuestionAnswerFlow.md
index 6b178a7e40..c61c14037e 100644
--- a/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantQuestionAnswerFlow.md
+++ b/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantQuestionAnswerFlow.md
@@ -1,13 +1,14 @@
 ---
-external help file: Microsoft.Rtc.Management.dll-Help.xml
-online version: https://learn.microsoft.com/powershell/module/teams/New-CsMainlineAttendantQuestionAnswerFlow 
 applicable: Microsoft Teams
-title: New-CsMainlineAttendantQuestionAnswerFlow
 author: tomkau
-ms.author: tomkau
+external help file: Microsoft.Rtc.Management.dll-Help.xml
+Locale: en-US
 manager: bulenteg
-ms.reviewer:
+Module Name: MicrosoftTeams
+ms.author: tomkau
+online version: https://learn.microsoft.com/powershell/module/microsoftteams/New-CsMainlineAttendantQuestionAnswerFlow
 schema: 2.0.0
+title: New-CsMainlineAttendantQuestionAnswerFlow
 ---
 
 # New-CsMainlineAttendantQuestionAnswerFlow
@@ -39,7 +40,6 @@ The name of the question and answer flow
 Type: String
 Parameter Sets: (All)
 Aliases:
-applicable: Microsoft Teams
 
 Required: True
 Position: Named
@@ -55,7 +55,6 @@ The description for the question and answer flow
 Type: String
 Parameter Sets: (All)
 Aliases:
-applicable: Microsoft Teams
 
 Required: True
 Position: Named
@@ -73,7 +72,6 @@ PARAVALUES: basic | api_key | bearer_token_static | bearer_token_dynamic
 Type: String
 Parameter Sets: (All)
 Aliases:
-applicable: Microsoft Teams
 
 Required: True
 Position: Named
@@ -93,7 +91,6 @@ For an example, see [New-CsMainlineAttendantQuestionAnswerFlow -KnowledgeBase](.
 Type: String
 Parameter Sets: (All)
 Aliases:
-applicable: Microsoft Teams
 
 Required: True
 Position: Named

From 6a4c5682335b666c53dad1593d05d0da35842c78 Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Tue, 5 Aug 2025 12:56:07 -0700
Subject: [PATCH 034/145] Update
 New-CsMainlineAttendantQuestionAnswerFlowKnowledgeBaseJSON.md

---
 ...ineAttendantQuestionAnswerFlowKnowledgeBaseJSON.md | 11 ++++++-----
 1 file changed, 6 insertions(+), 5 deletions(-)

diff --git a/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantQuestionAnswerFlowKnowledgeBaseJSON.md b/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantQuestionAnswerFlowKnowledgeBaseJSON.md
index 94939608d0..67eb6cb581 100644
--- a/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantQuestionAnswerFlowKnowledgeBaseJSON.md
+++ b/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantQuestionAnswerFlowKnowledgeBaseJSON.md
@@ -1,13 +1,14 @@
 ---
-external help file: Microsoft.Rtc.Management.dll-Help.xml
-online version: https://learn.microsoft.com/powershell/module/teams/new-csmainlineattendantquestionanswerflowknowledgebaseJSON
 applicable: Microsoft Teams
-title: New-CsMainlineAttendantQuestionAnswerFlowKnowledgeBaseJSON
 author: tomkau
-ms.author: tomkau
+external help file: Microsoft.Rtc.Management.dll-Help.xml
+Locale: en-US
 manager: bulenteg
-ms.reviewer:
+Module Name: MicrosoftTeams
+ms.author: tomkau
+online version: https://learn.microsoft.com/powershell/module/microsoftteamsNew-CsMainlineAttendantQuestionAnswerFlowKnowledgeBaseJSON
 schema: 2.0.0
+title: New-CsMainlineAttendantQuestionAnswerFlowKnowledgeBaseJSON
 ---
 
 # New-CsMainlineAttendantQuestionAnswerFlow -KnowledgeBase JSON Example

From 1f374bbcb860a8937243bf09e869cc78975c1b99 Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Tue, 5 Aug 2025 12:57:06 -0700
Subject: [PATCH 035/145] Update
 Remove-CsMainlineAttendantAppointmentBookingFlow.md

---
 ...-CsMainlineAttendantAppointmentBookingFlow.md | 16 +++++++---------
 1 file changed, 7 insertions(+), 9 deletions(-)

diff --git a/teams/teams-ps/MicrosoftTeams/Remove-CsMainlineAttendantAppointmentBookingFlow.md b/teams/teams-ps/MicrosoftTeams/Remove-CsMainlineAttendantAppointmentBookingFlow.md
index e38af8fd7a..2102aaa943 100644
--- a/teams/teams-ps/MicrosoftTeams/Remove-CsMainlineAttendantAppointmentBookingFlow.md
+++ b/teams/teams-ps/MicrosoftTeams/Remove-CsMainlineAttendantAppointmentBookingFlow.md
@@ -1,14 +1,14 @@
 ---
-external help file: Microsoft.Rtc.Management.dll-Help.xml
-online version: https://learn.microsoft.com/powershell/module/teams/Remove-CsMainlineAttendantAppointmentBookingFlow
 applicable: Microsoft Teams
-title: Remove-CsMainlineAttendantAppointmentBookingFlow
-schema: 2.0.0
-ms.reviewer:
-manager: bulenteg
 author: tomkau
+external help file: Microsoft.Rtc.Management.dll-Help.xml
+Locale: en-US
+manager: bulenteg
+Module Name: MicrosoftTeams
 ms.author: tomkau
-ms.reviewer: williamlooney
+online version: https://learn.microsoft.com/powershell/module/microsoftteams/Remove-CsMainlineAttendantAppointmentBookingFlow
+schema: 2.0.0
+title: Remove-CsMainlineAttendantAppointmentBookingFlow
 ---
 
 # Remove-CsMainlineAttendantAppointmentBookingFlow
@@ -43,7 +43,6 @@ PARAMVALUE: Guid
 Type: Guid
 Parameter Sets: (All)
 Aliases:
-applicable: Microsoft Teams
 
 Required: False
 Position: Named
@@ -59,7 +58,6 @@ PARAMVALUE: Guid
 Type: Guid
 Parameter Sets: (All)
 Aliases:
-applicable: Microsoft Teams
 
 Required: False
 Position: Named

From 8b0497c0357b20cd51c9ad19f5adbee5da397fba Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Tue, 5 Aug 2025 12:57:32 -0700
Subject: [PATCH 036/145] Update
 New-CsMainlineAttendantQuestionAnswerFlowKnowledgeBaseJSON.md

---
 ...ew-CsMainlineAttendantQuestionAnswerFlowKnowledgeBaseJSON.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantQuestionAnswerFlowKnowledgeBaseJSON.md b/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantQuestionAnswerFlowKnowledgeBaseJSON.md
index 67eb6cb581..1615c53b9b 100644
--- a/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantQuestionAnswerFlowKnowledgeBaseJSON.md
+++ b/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantQuestionAnswerFlowKnowledgeBaseJSON.md
@@ -6,7 +6,7 @@ Locale: en-US
 manager: bulenteg
 Module Name: MicrosoftTeams
 ms.author: tomkau
-online version: https://learn.microsoft.com/powershell/module/microsoftteamsNew-CsMainlineAttendantQuestionAnswerFlowKnowledgeBaseJSON
+online version: https://learn.microsoft.com/powershell/module/microsoftteams/New-CsMainlineAttendantQuestionAnswerFlowKnowledgeBaseJSON
 schema: 2.0.0
 title: New-CsMainlineAttendantQuestionAnswerFlowKnowledgeBaseJSON
 ---

From a1376ae3c9c54149ed4804f66cd80fca4d311047 Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Tue, 5 Aug 2025 12:58:25 -0700
Subject: [PATCH 037/145] Update
 Remove-CsMainlineAttendantQuestionAnswerFlow.md

---
 ...move-CsMainlineAttendantQuestionAnswerFlow.md | 16 +++++++---------
 1 file changed, 7 insertions(+), 9 deletions(-)

diff --git a/teams/teams-ps/MicrosoftTeams/Remove-CsMainlineAttendantQuestionAnswerFlow.md b/teams/teams-ps/MicrosoftTeams/Remove-CsMainlineAttendantQuestionAnswerFlow.md
index d57095be09..dd01af6353 100644
--- a/teams/teams-ps/MicrosoftTeams/Remove-CsMainlineAttendantQuestionAnswerFlow.md
+++ b/teams/teams-ps/MicrosoftTeams/Remove-CsMainlineAttendantQuestionAnswerFlow.md
@@ -1,14 +1,14 @@
 ---
-external help file: Microsoft.Rtc.Management.dll-Help.xml
-online version: https://learn.microsoft.com/powershell/module/teams/Remove-CsMainlineAttendantQuestionAnswerFlow
 applicable: Microsoft Teams
-title: Remove-CsMainlineAttendantQuestionAnswerFlow
-schema: 2.0.0
-ms.reviewer:
-manager: bulenteg
 author: tomkau
+external help file: Microsoft.Rtc.Management.dll-Help.xml
+Locale: en-US
+manager: bulenteg
+Module Name: MicrosoftTeams
 ms.author: tomkau
-ms.reviewer: williamlooney
+online version: https://learn.microsoft.com/powershell/module/microsoftteams/Remove-CsMainlineAttendantQuestionAnswerFlow
+schema: 2.0.0
+title: Remove-CsMainlineAttendantQuestionAnswerFlow
 ---
 
 # Remove-CsMainlineAttendantQuestionAnswerFlow
@@ -43,7 +43,6 @@ PARAMVALUE: Guid
 Type: Guid
 Parameter Sets: (All)
 Aliases:
-applicable: Microsoft Teams
 
 Required: False
 Position: Named
@@ -59,7 +58,6 @@ PARAMVALUE: Guid
 Type: Guid
 Parameter Sets: (All)
 Aliases:
-applicable: Microsoft Teams
 
 Required: False
 Position: Named

From d1dec0425ea313b26a73e15b861b65fe8cf66a51 Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Tue, 5 Aug 2025 12:59:34 -0700
Subject: [PATCH 038/145] Update
 Set-CsMainlineAttendantAppointmentBookingFlow.md

---
 ...CsMainlineAttendantAppointmentBookingFlow.md | 17 ++++++-----------
 1 file changed, 6 insertions(+), 11 deletions(-)

diff --git a/teams/teams-ps/MicrosoftTeams/Set-CsMainlineAttendantAppointmentBookingFlow.md b/teams/teams-ps/MicrosoftTeams/Set-CsMainlineAttendantAppointmentBookingFlow.md
index bef2833cb8..74a33a75ec 100644
--- a/teams/teams-ps/MicrosoftTeams/Set-CsMainlineAttendantAppointmentBookingFlow.md
+++ b/teams/teams-ps/MicrosoftTeams/Set-CsMainlineAttendantAppointmentBookingFlow.md
@@ -1,13 +1,14 @@
 ---
-external help file: Microsoft.Rtc.Management.dll-Help.xml
-online version: https://learn.microsoft.com/powershell/module/teams/Set-CsMainlineAttendantAppointmentBookingFlow
 applicable: Microsoft Teams
-title: Set-CsMainlineAttendantAppointmentBookingFlow
 author: tomkau
-ms.author: tomkau
+external help file: Microsoft.Rtc.Management.dll-Help.xml
+Locale: en-US
 manager: bulenteg
-ms.reviewer:
+Module Name: MicrosoftTeams
+ms.author: tomkau
+online version: https://learn.microsoft.com/powershell/module/microsoftteams/Set-CsMainlineAttendantAppointmentBookingFlow
 schema: 2.0.0
+title: Set-CsMainlineAttendantAppointmentBookingFlow
 ---
 
 # Set-CsMainlineAttendantAppointmentBookingFlow
@@ -39,7 +40,6 @@ The unique Id of the appointment booking flow to change
 Type: String
 Parameter Sets: (All)
 Aliases:
-applicable: Microsoft Teams
 
 Required: True
 Position: Named
@@ -55,7 +55,6 @@ The name of the appointment booking flow
 Type: String
 Parameter Sets: (All)
 Aliases:
-applicable: Microsoft Teams
 
 Required: False
 Position: Named
@@ -73,7 +72,6 @@ Limit: 500 characters.
 Type: String
 Parameter Sets: (All)
 Aliases:
-applicable: Microsoft Teams
 
 Required: False
 Position: Named
@@ -91,7 +89,6 @@ PARAVALUES: sms | email | verification_link | voiceprint | user_details
 Type: String
 Parameter Sets: (All)
 Aliases:
-applicable: Microsoft Teams
 
 Required: False
 Position: Named
@@ -109,7 +106,6 @@ PARAVALUES: basic | api_key | bearer_token_static | bearer_token_dynamic
 Type: String
 Parameter Sets: (All)
 Aliases:
-applicable: Microsoft Teams
 
 Required: False
 Position: Named
@@ -127,7 +123,6 @@ For an example, see [New-CsMainlineAttendantAppointBookingFlow -ApiDefinitions](
 Type: String
 Parameter Sets: (All)
 Aliases:
-applicable: Microsoft Teams
 
 Required: False
 Position: Named

From b0b0a312a1c6698472a92b8a9b470e9b328a2807 Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Tue, 5 Aug 2025 13:00:35 -0700
Subject: [PATCH 039/145] Update Set-CsMainlineAttendantQuestionAnswerFlow.md

---
 .../Set-CsMainlineAttendantQuestionAnswerFlow.md | 16 ++++++----------
 1 file changed, 6 insertions(+), 10 deletions(-)

diff --git a/teams/teams-ps/MicrosoftTeams/Set-CsMainlineAttendantQuestionAnswerFlow.md b/teams/teams-ps/MicrosoftTeams/Set-CsMainlineAttendantQuestionAnswerFlow.md
index 68cb82c876..ea98ad87eb 100644
--- a/teams/teams-ps/MicrosoftTeams/Set-CsMainlineAttendantQuestionAnswerFlow.md
+++ b/teams/teams-ps/MicrosoftTeams/Set-CsMainlineAttendantQuestionAnswerFlow.md
@@ -1,13 +1,14 @@
 ---
-external help file: Microsoft.Rtc.Management.dll-Help.xml
-online version: https://learn.microsoft.com/powershell/module/teams/Set-CsMainlineAttendantQuestionAnswerFlow 
 applicable: Microsoft Teams
-title: Set-CsMainlineAttendantQuestionAnswerFlow
 author: tomkau
-ms.author: tomkau
+external help file: Microsoft.Rtc.Management.dll-Help.xml
+Locale: en-US
 manager: bulenteg
-ms.reviewer:
+Module Name: MicrosoftTeams
+ms.author: tomkau
+online version: https://learn.microsoft.com/powershell/module/microsoftteams/Set-CsMainlineAttendantQuestionAnswerFlow
 schema: 2.0.0
+title: Set-CsMainlineAttendantQuestionAnswerFlow
 ---
 
 # Set-CsMainlineAttendantQuestionAnswerFlow
@@ -39,7 +40,6 @@ The unique identifier for the question and answer flow.
 Type: String
 Parameter Sets: (All)
 Aliases:
-applicable: Microsoft Teams
 
 Required: True
 Position: Named
@@ -55,7 +55,6 @@ The name of the question and answer flow
 Type: String
 Parameter Sets: (All)
 Aliases:
-applicable: Microsoft Teams
 
 Required: False
 Position: Named
@@ -71,7 +70,6 @@ The description for the question and answer flow
 Type: String
 Parameter Sets: (All)
 Aliases:
-applicable: Microsoft Teams
 
 Required: False
 Position: Named
@@ -89,7 +87,6 @@ PARAVALUES: basic | api_key | bearer_token_static | bearer_token_dynamic
 Type: String
 Parameter Sets: (All)
 Aliases:
-applicable: Microsoft Teams
 
 Required: False
 Position: Named
@@ -109,7 +106,6 @@ For an example, see [New-CsMainlineAttendantQuestionAnswerFlow -KnowledgeBase](.
 Type: String
 Parameter Sets: (All)
 Aliases:
-applicable: Microsoft Teams
 
 Required: False
 Position: Named

From db89089111ac228cd9f1fb09c8c361e886b11856 Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Tue, 5 Aug 2025 13:17:19 -0700
Subject: [PATCH 040/145] Update
 Get-CsMainlineAttendantAppointmentBookingFlow.md

---
 ...MainlineAttendantAppointmentBookingFlow.md | 24 +++++++++++++++++++
 1 file changed, 24 insertions(+)

diff --git a/teams/teams-ps/MicrosoftTeams/Get-CsMainlineAttendantAppointmentBookingFlow.md b/teams/teams-ps/MicrosoftTeams/Get-CsMainlineAttendantAppointmentBookingFlow.md
index 956ca2bcef..e7e2a5c43a 100644
--- a/teams/teams-ps/MicrosoftTeams/Get-CsMainlineAttendantAppointmentBookingFlow.md
+++ b/teams/teams-ps/MicrosoftTeams/Get-CsMainlineAttendantAppointmentBookingFlow.md
@@ -44,6 +44,9 @@ This example gets the Mainline attendant appointment booking flow with the ident
 ## PARAMETERS
 
 ### -Identity
+
+> Applicable: Microsoft Teams
+
 PARAMVALUE: Guid
 
 ```yaml
@@ -59,6 +62,9 @@ Accept wildcard characters: False
 ```
 
 ### -Tenant
+
+> Applicable: Microsoft Teams
+
 PARAMVALUE: Guid
 
 ```yaml
@@ -74,6 +80,9 @@ Accept wildcard characters: False
 ```
 
 ### -First
+
+> Applicable: Microsoft Teams
+
 The First parameter gets the first N appointment flows, up to a maximum of 100 at a time. 
 When not specified, the default behavior is to return the first 100 appointment flows. It is intended to be used in conjunction with the `-Skip` parameter for pagination purposes.
 If a number greater than 100 is supplied, the request will fail.
@@ -91,6 +100,9 @@ Accept wildcard characters: False
 ```
 
 ### -Skip
+
+> Applicable: Microsoft Teams
+
 The Skip parameter skips the first N appointment flows. It is intended to be used in conjunction with the `-First` parameter for pagination purposes.
 
 ```yaml
@@ -106,6 +118,9 @@ Accept wildcard characters: False
 ```
 
 ### -ExcludeContent
+
+> Applicable: Microsoft Teams
+
 The ExcludeContent parameter only displays the Name and Id of the appointment flow.
 
 ```yaml
@@ -121,6 +136,9 @@ Accept wildcard characters: False
 ```
 
 ### -Sort
+
+> Applicable: Microsoft Teams
+
 The Sort parameter specifies the property used to sort.
 
 ```yaml
@@ -136,6 +154,9 @@ Accept wildcard characters: False
 ```
 
 ### -Descending
+
+> Applicable: Microsoft Teams
+
 The Descending parameter sorts appointment booking flows in descending order
 
 ```yaml
@@ -151,6 +172,9 @@ Accept wildcard characters: False
 ```
 
 ### -NameFilter
+
+> Applicable: Microsoft Teams
+
 The NameFilter parameter returns appointment booking flows where the name contains specified string
 
 ```yaml

From 0cd228a9db29be67e7281b40563424504bb56bce Mon Sep 17 00:00:00 2001
From: pavellatif <142821210+pavellatif@users.noreply.github.com>
Date: Tue, 5 Aug 2025 17:21:12 -0400
Subject: [PATCH 041/145] Updating syntax and examples for email notifcation
 during telephone number assignment and unassignment

---
 .../Get-CsPhoneNumberAssignment.md            |  2 +-
 .../Remove-CsPhoneNumberAssignment.md         | 22 ++++++++++++++----
 .../Set-CsPhoneNumberAssignment.md            | 23 +++++++++++++++++--
 3 files changed, 40 insertions(+), 7 deletions(-)

diff --git a/teams/teams-ps/MicrosoftTeams/Get-CsPhoneNumberAssignment.md b/teams/teams-ps/MicrosoftTeams/Get-CsPhoneNumberAssignment.md
index 12b29693df..4499f33849 100644
--- a/teams/teams-ps/MicrosoftTeams/Get-CsPhoneNumberAssignment.md
+++ b/teams/teams-ps/MicrosoftTeams/Get-CsPhoneNumberAssignment.md
@@ -473,7 +473,7 @@ Accept wildcard characters: False
 
 > Applicable: Microsoft Teams
 
-This parameter is reserved for internal Microsoft use.
+ID of a network site. A network site represents a location where your organization has a physical venue, such as offices, a set of buildings, or a campus.
 
 ```yaml
 Type: System.String
diff --git a/teams/teams-ps/MicrosoftTeams/Remove-CsPhoneNumberAssignment.md b/teams/teams-ps/MicrosoftTeams/Remove-CsPhoneNumberAssignment.md
index b599742e58..dfe4dbf05a 100644
--- a/teams/teams-ps/MicrosoftTeams/Remove-CsPhoneNumberAssignment.md
+++ b/teams/teams-ps/MicrosoftTeams/Remove-CsPhoneNumberAssignment.md
@@ -20,13 +20,13 @@ This cmdlet will remove/unassign a phone number from a user or a resource accoun
 ### RemoveSome (Default)
 ```
 Remove-CsPhoneNumberAssignment -Identity <String> -PhoneNumber <String> -PhoneNumberType <String>
- [-HttpPipelinePrepend <SendAsyncStep[]>] [<CommonParameters>]
+ [-HttpPipelinePrepend <SendAsyncStep[]>] [-Notify] [<CommonParameters>]
 ```
 
 ### RemoveAll
 ```
 Remove-CsPhoneNumberAssignment -Identity <String> [-HttpPipelinePrepend <SendAsyncStep[]>] [-RemoveAll]
- [<CommonParameters>]
+ [-Notify] [<CommonParameters>]
 ```
 
 ## DESCRIPTION
@@ -58,13 +58,13 @@ This example removes/unassigns all the telephone number from user2@contoso.com.
 
 ### Example 3
 ```powershell
-Remove-CsPhoneNumberAssignment -Identity user1@contoso.com -PhoneNumber +12065551234 -PhoneNumberType CallingPlan
+Remove-CsPhoneNumberAssignment -Identity user1@contoso.com -PhoneNumber +12065551234 -PhoneNumberType CallingPlan -Notify
 ```
 This example removes/unassigns the Microsoft Calling Plan phone number +1 (206) 555-1234 from the user user1@contoso.com and also sends an email notification to the user about the removal of telephone number.
 
 ### Example 4
 ```powershell
-Remove-CsPhoneNumberAssignment -Identity user2@contoso.com -RemoveAll
+Remove-CsPhoneNumberAssignment -Identity user2@contoso.com -RemoveAll -Notify
 ```
 This example removes/unassigns all the telephone number from user2@contoso.com and also sends an email notification to the user about the change.
 
@@ -146,6 +146,20 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
+### -Notify
+Sends a best-effort email notification when a phone number is removed. Failures to send email are not reported.
+
+```yaml
+Type: Switch
+Parameter Sets: (RemoveSome, RemoveAll)
+Aliases:
+
+Required: False
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
 ### CommonParameters
 This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](http://go.microsoft.com/fwlink/?LinkID=113216).
 
diff --git a/teams/teams-ps/MicrosoftTeams/Set-CsPhoneNumberAssignment.md b/teams/teams-ps/MicrosoftTeams/Set-CsPhoneNumberAssignment.md
index bc75b516d8..904ee00f52 100644
--- a/teams/teams-ps/MicrosoftTeams/Set-CsPhoneNumberAssignment.md
+++ b/teams/teams-ps/MicrosoftTeams/Set-CsPhoneNumberAssignment.md
@@ -39,7 +39,7 @@ Set-CsPhoneNumberAssignment -PhoneNumber <String> [-HttpPipelinePrepend <SendAsy
 ```
 Set-CsPhoneNumberAssignment -PhoneNumber <String> [-LocationId <String>]
  [-HttpPipelinePrepend <SendAsyncStep[]>] -Identity <String> -PhoneNumberType <String>
- [-NetworkSiteId <String>] [-AssignmentCategory <String>] [-ReverseNumberLookup <String>] [<CommonParameters>]
+ [-NetworkSiteId <String>] [-AssignmentCategory <String>] [-ReverseNumberLookup <String>] [-Notify] [<CommonParameters>]
 ```
 
 ### Attribute
@@ -48,8 +48,13 @@ Set-CsPhoneNumberAssignment [-HttpPipelinePrepend <SendAsyncStep[]>] -Identity <
  -EnterpriseVoiceEnabled <Boolean> [<CommonParameters>]
 ```
 
+### Notify
+```
+Set-CsPhoneNumberAssignment -Identity <string> -PhoneNumber <string> -PhoneNumberType <String> -Notify [<CommonParameters>]
+```
+
 ## DESCRIPTION
-This cmdlet assigns a phone number to a user or resource account. When you assign a phone number the EnterpriseVoiceEnabled flag is automatically set to True.
+This cmdlet assigns a telephone number to a user or resource account. When you assign a phone number the EnterpriseVoiceEnabled flag is automatically set to True.
 
 You can also assign a location to a phone number.
 
@@ -284,6 +289,20 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
+### -Notify
+Sends an email to Teams phone user about new telephone number assignment.
+
+```yaml
+Type: Switch
+Parameter Sets: (Notify)
+Aliases:
+
+Required: False
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
 ### -PhoneNumber
 The phone number to assign to the user or resource account. Supports E.164 format like +12065551234 and non-E.164 format like 12065551234. The phone number can't have "tel:" prefixed.
 

From 406cac5147840e896215c87f6c701c932024f646 Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Tue, 5 Aug 2025 14:27:57 -0700
Subject: [PATCH 042/145] Update
 Get-CsMainlineAttendantAppointmentBookingFlow.md

---
 .../Get-CsMainlineAttendantAppointmentBookingFlow.md            | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/teams/teams-ps/MicrosoftTeams/Get-CsMainlineAttendantAppointmentBookingFlow.md b/teams/teams-ps/MicrosoftTeams/Get-CsMainlineAttendantAppointmentBookingFlow.md
index e7e2a5c43a..42f0e9d432 100644
--- a/teams/teams-ps/MicrosoftTeams/Get-CsMainlineAttendantAppointmentBookingFlow.md
+++ b/teams/teams-ps/MicrosoftTeams/Get-CsMainlineAttendantAppointmentBookingFlow.md
@@ -6,7 +6,7 @@ Locale: en-US
 manager: bulenteg
 Module Name: MicrosoftTeams
 ms.author: tomkau
-online version: https://learn.microsoft.com/powershell/module/microsoftteams/Get-CsMainlineAttendantAppointmentBookingFlow
+online version: https://learn.microsoft.com/powershell/module/microsoftteams/get-csmainlineattendantappointmentbookingflow
 schema: 2.0.0
 title: Get-CsMainlineAttendantAppointmentBookingFlow
 ---

From 1ad028b3d7db8373ef922cbedf2f7918b0a5bac0 Mon Sep 17 00:00:00 2001
From: pavellatif <142821210+pavellatif@users.noreply.github.com>
Date: Tue, 5 Aug 2025 17:29:51 -0400
Subject: [PATCH 043/145] Update Set-CsPhoneNumberAssignment.md

---
 .../teams-ps/MicrosoftTeams/Set-CsPhoneNumberAssignment.md | 7 +------
 1 file changed, 1 insertion(+), 6 deletions(-)

diff --git a/teams/teams-ps/MicrosoftTeams/Set-CsPhoneNumberAssignment.md b/teams/teams-ps/MicrosoftTeams/Set-CsPhoneNumberAssignment.md
index 904ee00f52..cd2f63a6fa 100644
--- a/teams/teams-ps/MicrosoftTeams/Set-CsPhoneNumberAssignment.md
+++ b/teams/teams-ps/MicrosoftTeams/Set-CsPhoneNumberAssignment.md
@@ -48,11 +48,6 @@ Set-CsPhoneNumberAssignment [-HttpPipelinePrepend <SendAsyncStep[]>] -Identity <
  -EnterpriseVoiceEnabled <Boolean> [<CommonParameters>]
 ```
 
-### Notify
-```
-Set-CsPhoneNumberAssignment -Identity <string> -PhoneNumber <string> -PhoneNumberType <String> -Notify [<CommonParameters>]
-```
-
 ## DESCRIPTION
 This cmdlet assigns a telephone number to a user or resource account. When you assign a phone number the EnterpriseVoiceEnabled flag is automatically set to True.
 
@@ -294,7 +289,7 @@ Sends an email to Teams phone user about new telephone number assignment.
 
 ```yaml
 Type: Switch
-Parameter Sets: (Notify)
+Parameter Sets: Assignment
 Aliases:
 
 Required: False

From f5761574ad2a7161f45e1adf2b0e7f0b4898f374 Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Tue, 5 Aug 2025 14:30:49 -0700
Subject: [PATCH 044/145] Update Get-CsMainlineAttendantFlow.md

---
 teams/teams-ps/MicrosoftTeams/Get-CsMainlineAttendantFlow.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/teams/teams-ps/MicrosoftTeams/Get-CsMainlineAttendantFlow.md b/teams/teams-ps/MicrosoftTeams/Get-CsMainlineAttendantFlow.md
index 8f3fe8f1cc..2ae0210a45 100644
--- a/teams/teams-ps/MicrosoftTeams/Get-CsMainlineAttendantFlow.md
+++ b/teams/teams-ps/MicrosoftTeams/Get-CsMainlineAttendantFlow.md
@@ -5,7 +5,7 @@ Locale: en-US
 manager: bulenteg
 Module Name: MicrosoftTeams
 ms.author: tomkau
-online version: https://learn.microsoft.com/powershell/module/microsoftteams/Get-CsMainlineAttendantFlow
+online version: https://learn.microsoft.com/powershell/module/microsoftteams/get-csmainlineattendantflow
 schema: 2.0.0
 title: Get-CsMainlineAttendantFlow
 ---

From 5d58ab18932843619269d73e56f34ca449c48af9 Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Tue, 5 Aug 2025 14:31:19 -0700
Subject: [PATCH 045/145] Update Get-CsMainlineAttendantQuestionAnswerFlow.md

---
 .../MicrosoftTeams/Get-CsMainlineAttendantQuestionAnswerFlow.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/teams/teams-ps/MicrosoftTeams/Get-CsMainlineAttendantQuestionAnswerFlow.md b/teams/teams-ps/MicrosoftTeams/Get-CsMainlineAttendantQuestionAnswerFlow.md
index 2537deac74..89ed9d9101 100644
--- a/teams/teams-ps/MicrosoftTeams/Get-CsMainlineAttendantQuestionAnswerFlow.md
+++ b/teams/teams-ps/MicrosoftTeams/Get-CsMainlineAttendantQuestionAnswerFlow.md
@@ -6,7 +6,7 @@ Locale: en-US
 manager: bulenteg
 Module Name: MicrosoftTeams
 ms.author: tomkau
-online version: https://learn.microsoft.com/powershell/module/microsoftteams/Get-CsMainlineAttendantQuestionAnswerFlow
+online version: https://learn.microsoft.com/powershell/module/microsoftteams/get-csmainlineattendantquestionanswerflow
 schema: 2.0.0
 title: Get-CsMainlineAttendantQuestionAnswerFlow
 ---

From aa88253e135e0a48a43481ac51e9d1176b992ef8 Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Tue, 5 Aug 2025 14:31:56 -0700
Subject: [PATCH 046/145] Update
 New-CsMainlineAttendantAppointmentBookingFlow.md

---
 .../New-CsMainlineAttendantAppointmentBookingFlow.md            | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantAppointmentBookingFlow.md b/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantAppointmentBookingFlow.md
index b91b31e886..b7e76968a6 100644
--- a/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantAppointmentBookingFlow.md
+++ b/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantAppointmentBookingFlow.md
@@ -6,7 +6,7 @@ Locale: en-US
 manager: bulenteg
 Module Name: MicrosoftTeams
 ms.author: tomkau
-online version: https://learn.microsoft.com/powershell/module/microsoftteams/New-CsMainlineAttendantAppointmentBookingFlow
+online version: https://learn.microsoft.com/powershell/module/microsoftteams/new-csmainlineattendantappointmentbookingflow
 schema: 2.0.0
 title: New-CsMainlineAttendantAppointmentBookingFlow
 ---

From 7d9be018f1d044b1550fdac10c121fcf89993ee1 Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Tue, 5 Aug 2025 14:32:39 -0700
Subject: [PATCH 047/145] Update
 New-CsMainlineAttendantAppointmentBookingFlowApiDefinitionsJSON.md

---
 ...MainlineAttendantAppointmentBookingFlowApiDefinitionsJSON.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantAppointmentBookingFlowApiDefinitionsJSON.md b/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantAppointmentBookingFlowApiDefinitionsJSON.md
index 22713b4957..5fb62f2964 100644
--- a/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantAppointmentBookingFlowApiDefinitionsJSON.md
+++ b/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantAppointmentBookingFlowApiDefinitionsJSON.md
@@ -6,7 +6,7 @@ Locale: en-US
 manager: bulenteg
 Module Name: MicrosoftTeams
 ms.author: tomkau
-online version: https://learn.microsoft.com/powershell/module/microsoftteams/New-CsMainLineAttendantAppointmentBookingFlowApiDefinitionsJSON
+online version: https://learn.microsoft.com/powershell/module/microsoftteams/new-csmainlineattendantappointmentbookingflowapidefinitionsJSON
 schema: 2.0.0
 title: New-CsMainLineAttendantAppointmentBookingFlowApiDefinitionsJSON
 ---

From 45092b0be2a5aa01e0a18fa9a6b861137bece872 Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Tue, 5 Aug 2025 14:33:12 -0700
Subject: [PATCH 048/145] Update New-CsMainlineAttendantQuestionAnswerFlow.md

---
 .../MicrosoftTeams/New-CsMainlineAttendantQuestionAnswerFlow.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantQuestionAnswerFlow.md b/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantQuestionAnswerFlow.md
index c61c14037e..3a38f4aada 100644
--- a/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantQuestionAnswerFlow.md
+++ b/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantQuestionAnswerFlow.md
@@ -6,7 +6,7 @@ Locale: en-US
 manager: bulenteg
 Module Name: MicrosoftTeams
 ms.author: tomkau
-online version: https://learn.microsoft.com/powershell/module/microsoftteams/New-CsMainlineAttendantQuestionAnswerFlow
+online version: https://learn.microsoft.com/powershell/module/microsoftteams/new-csmainlineattendantquestionanswerflow
 schema: 2.0.0
 title: New-CsMainlineAttendantQuestionAnswerFlow
 ---

From 1a89288069dd3fbf9b3a6a4377db88d18cb17841 Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Tue, 5 Aug 2025 14:33:57 -0700
Subject: [PATCH 049/145] Update
 New-CsMainlineAttendantQuestionAnswerFlowKnowledgeBaseJSON.md

---
 ...ew-CsMainlineAttendantQuestionAnswerFlowKnowledgeBaseJSON.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantQuestionAnswerFlowKnowledgeBaseJSON.md b/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantQuestionAnswerFlowKnowledgeBaseJSON.md
index 1615c53b9b..442ae3f811 100644
--- a/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantQuestionAnswerFlowKnowledgeBaseJSON.md
+++ b/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantQuestionAnswerFlowKnowledgeBaseJSON.md
@@ -6,7 +6,7 @@ Locale: en-US
 manager: bulenteg
 Module Name: MicrosoftTeams
 ms.author: tomkau
-online version: https://learn.microsoft.com/powershell/module/microsoftteams/New-CsMainlineAttendantQuestionAnswerFlowKnowledgeBaseJSON
+online version: https://learn.microsoft.com/powershell/module/microsoftteams/new-csmainlineattendantquestionanswerflowknowledgebasejson
 schema: 2.0.0
 title: New-CsMainlineAttendantQuestionAnswerFlowKnowledgeBaseJSON
 ---

From 624cd8d93c1f98b73bcb6c9f1a479a50cd7c0ad2 Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Tue, 5 Aug 2025 14:34:34 -0700
Subject: [PATCH 050/145] Update
 Remove-CsMainlineAttendantAppointmentBookingFlow.md

---
 .../Remove-CsMainlineAttendantAppointmentBookingFlow.md         | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/teams/teams-ps/MicrosoftTeams/Remove-CsMainlineAttendantAppointmentBookingFlow.md b/teams/teams-ps/MicrosoftTeams/Remove-CsMainlineAttendantAppointmentBookingFlow.md
index 2102aaa943..22c8bc1dbf 100644
--- a/teams/teams-ps/MicrosoftTeams/Remove-CsMainlineAttendantAppointmentBookingFlow.md
+++ b/teams/teams-ps/MicrosoftTeams/Remove-CsMainlineAttendantAppointmentBookingFlow.md
@@ -6,7 +6,7 @@ Locale: en-US
 manager: bulenteg
 Module Name: MicrosoftTeams
 ms.author: tomkau
-online version: https://learn.microsoft.com/powershell/module/microsoftteams/Remove-CsMainlineAttendantAppointmentBookingFlow
+online version: https://learn.microsoft.com/powershell/module/microsoftteams/remove-csmainlineattendantappointmentbookingflow
 schema: 2.0.0
 title: Remove-CsMainlineAttendantAppointmentBookingFlow
 ---

From dabbd61202a32b4363d1bfded42b3db6f4996705 Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Tue, 5 Aug 2025 14:35:04 -0700
Subject: [PATCH 051/145] Update
 Remove-CsMainlineAttendantQuestionAnswerFlow.md

---
 .../Remove-CsMainlineAttendantQuestionAnswerFlow.md             | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/teams/teams-ps/MicrosoftTeams/Remove-CsMainlineAttendantQuestionAnswerFlow.md b/teams/teams-ps/MicrosoftTeams/Remove-CsMainlineAttendantQuestionAnswerFlow.md
index dd01af6353..023b3d2ee9 100644
--- a/teams/teams-ps/MicrosoftTeams/Remove-CsMainlineAttendantQuestionAnswerFlow.md
+++ b/teams/teams-ps/MicrosoftTeams/Remove-CsMainlineAttendantQuestionAnswerFlow.md
@@ -6,7 +6,7 @@ Locale: en-US
 manager: bulenteg
 Module Name: MicrosoftTeams
 ms.author: tomkau
-online version: https://learn.microsoft.com/powershell/module/microsoftteams/Remove-CsMainlineAttendantQuestionAnswerFlow
+online version: https://learn.microsoft.com/powershell/module/microsoftteams/remove-csmainlineattendantquestionanswerflow
 schema: 2.0.0
 title: Remove-CsMainlineAttendantQuestionAnswerFlow
 ---

From ea43b7ee0b718277b6d64cb1e2fd1d3ffd812412 Mon Sep 17 00:00:00 2001
From: pavellatif <142821210+pavellatif@users.noreply.github.com>
Date: Tue, 5 Aug 2025 17:35:11 -0400
Subject: [PATCH 052/145] fixing parameter set and type for -Notify parameter

---
 .../teams-ps/MicrosoftTeams/Remove-CsPhoneNumberAssignment.md | 4 ++--
 teams/teams-ps/MicrosoftTeams/Set-CsPhoneNumberAssignment.md  | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/teams/teams-ps/MicrosoftTeams/Remove-CsPhoneNumberAssignment.md b/teams/teams-ps/MicrosoftTeams/Remove-CsPhoneNumberAssignment.md
index dfe4dbf05a..ae124234b8 100644
--- a/teams/teams-ps/MicrosoftTeams/Remove-CsPhoneNumberAssignment.md
+++ b/teams/teams-ps/MicrosoftTeams/Remove-CsPhoneNumberAssignment.md
@@ -150,8 +150,8 @@ Accept wildcard characters: False
 Sends a best-effort email notification when a phone number is removed. Failures to send email are not reported.
 
 ```yaml
-Type: Switch
-Parameter Sets: (RemoveSome, RemoveAll)
+Type: System.Management.Automation.SwitchParameter
+Parameter Sets: RemoveSome, RemoveAll
 Aliases:
 
 Required: False
diff --git a/teams/teams-ps/MicrosoftTeams/Set-CsPhoneNumberAssignment.md b/teams/teams-ps/MicrosoftTeams/Set-CsPhoneNumberAssignment.md
index cd2f63a6fa..56e7b85ea6 100644
--- a/teams/teams-ps/MicrosoftTeams/Set-CsPhoneNumberAssignment.md
+++ b/teams/teams-ps/MicrosoftTeams/Set-CsPhoneNumberAssignment.md
@@ -288,7 +288,7 @@ Accept wildcard characters: False
 Sends an email to Teams phone user about new telephone number assignment.
 
 ```yaml
-Type: Switch
+Type: System.Management.Automation.SwitchParameter
 Parameter Sets: Assignment
 Aliases:
 

From 3a02655a2c195a8f09b150f5ce8bbb4498453a39 Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Tue, 5 Aug 2025 14:35:35 -0700
Subject: [PATCH 053/145] Update
 Set-CsMainlineAttendantAppointmentBookingFlow.md

---
 .../Set-CsMainlineAttendantAppointmentBookingFlow.md            | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/teams/teams-ps/MicrosoftTeams/Set-CsMainlineAttendantAppointmentBookingFlow.md b/teams/teams-ps/MicrosoftTeams/Set-CsMainlineAttendantAppointmentBookingFlow.md
index 74a33a75ec..faf6c8f740 100644
--- a/teams/teams-ps/MicrosoftTeams/Set-CsMainlineAttendantAppointmentBookingFlow.md
+++ b/teams/teams-ps/MicrosoftTeams/Set-CsMainlineAttendantAppointmentBookingFlow.md
@@ -6,7 +6,7 @@ Locale: en-US
 manager: bulenteg
 Module Name: MicrosoftTeams
 ms.author: tomkau
-online version: https://learn.microsoft.com/powershell/module/microsoftteams/Set-CsMainlineAttendantAppointmentBookingFlow
+online version: https://learn.microsoft.com/powershell/module/microsoftteams/set-csmainlineattendantappointmentbookingflow
 schema: 2.0.0
 title: Set-CsMainlineAttendantAppointmentBookingFlow
 ---

From 15e8e028b89b83bf9a5256e5aa0979a28a0c2a15 Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Tue, 5 Aug 2025 14:36:06 -0700
Subject: [PATCH 054/145] Update Set-CsMainlineAttendantQuestionAnswerFlow.md

---
 .../MicrosoftTeams/Set-CsMainlineAttendantQuestionAnswerFlow.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/teams/teams-ps/MicrosoftTeams/Set-CsMainlineAttendantQuestionAnswerFlow.md b/teams/teams-ps/MicrosoftTeams/Set-CsMainlineAttendantQuestionAnswerFlow.md
index ea98ad87eb..1dcc93e9a7 100644
--- a/teams/teams-ps/MicrosoftTeams/Set-CsMainlineAttendantQuestionAnswerFlow.md
+++ b/teams/teams-ps/MicrosoftTeams/Set-CsMainlineAttendantQuestionAnswerFlow.md
@@ -6,7 +6,7 @@ Locale: en-US
 manager: bulenteg
 Module Name: MicrosoftTeams
 ms.author: tomkau
-online version: https://learn.microsoft.com/powershell/module/microsoftteams/Set-CsMainlineAttendantQuestionAnswerFlow
+online version: https://learn.microsoft.com/powershell/module/microsoftteams/set-csmainlineattendantquestionanswerflow
 schema: 2.0.0
 title: Set-CsMainlineAttendantQuestionAnswerFlow
 ---

From 8625998b94acb5799b29b1794efcd7f5738bd60f Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Tue, 5 Aug 2025 14:40:29 -0700
Subject: [PATCH 055/145] Update Get-CsMainlineAttendantFlow.md

---
 teams/teams-ps/MicrosoftTeams/Get-CsMainlineAttendantFlow.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/teams/teams-ps/MicrosoftTeams/Get-CsMainlineAttendantFlow.md b/teams/teams-ps/MicrosoftTeams/Get-CsMainlineAttendantFlow.md
index 2ae0210a45..b56b723e67 100644
--- a/teams/teams-ps/MicrosoftTeams/Get-CsMainlineAttendantFlow.md
+++ b/teams/teams-ps/MicrosoftTeams/Get-CsMainlineAttendantFlow.md
@@ -1,3 +1,4 @@
+---
 applicable: Microsoft Teams
 author: tomkau
 external help file: Microsoft.Rtc.Management.dll-Help.xml

From 377142e04a0e1e149e1334d5bb7d1190e43d753c Mon Sep 17 00:00:00 2001
From: pavellatif <142821210+pavellatif@users.noreply.github.com>
Date: Tue, 5 Aug 2025 17:43:44 -0400
Subject: [PATCH 056/145] Fixing validation error for Notify parameter set

---
 .../teams-ps/MicrosoftTeams/Remove-CsPhoneNumberAssignment.md  | 3 ++-
 teams/teams-ps/MicrosoftTeams/Set-CsPhoneNumberAssignment.md   | 1 +
 2 files changed, 3 insertions(+), 1 deletion(-)

diff --git a/teams/teams-ps/MicrosoftTeams/Remove-CsPhoneNumberAssignment.md b/teams/teams-ps/MicrosoftTeams/Remove-CsPhoneNumberAssignment.md
index ae124234b8..35819f80d0 100644
--- a/teams/teams-ps/MicrosoftTeams/Remove-CsPhoneNumberAssignment.md
+++ b/teams/teams-ps/MicrosoftTeams/Remove-CsPhoneNumberAssignment.md
@@ -151,10 +151,11 @@ Sends a best-effort email notification when a phone number is removed. Failures
 
 ```yaml
 Type: System.Management.Automation.SwitchParameter
-Parameter Sets: RemoveSome, RemoveAll
+Parameter Sets: (All)
 Aliases:
 
 Required: False
+Position: Named
 Default value: None
 Accept pipeline input: False
 Accept wildcard characters: False
diff --git a/teams/teams-ps/MicrosoftTeams/Set-CsPhoneNumberAssignment.md b/teams/teams-ps/MicrosoftTeams/Set-CsPhoneNumberAssignment.md
index 56e7b85ea6..1923a2bfd4 100644
--- a/teams/teams-ps/MicrosoftTeams/Set-CsPhoneNumberAssignment.md
+++ b/teams/teams-ps/MicrosoftTeams/Set-CsPhoneNumberAssignment.md
@@ -293,6 +293,7 @@ Parameter Sets: Assignment
 Aliases:
 
 Required: False
+Position: Named
 Default value: None
 Accept pipeline input: False
 Accept wildcard characters: False

From 25d902dcf03d0ec04120bfeab9794cec7a1e3057 Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Tue, 5 Aug 2025 14:45:28 -0700
Subject: [PATCH 057/145] Update
 New-CsMainlineAttendantAppointmentBookingFlowApiDefinitionsJSON.md

---
 ...MainlineAttendantAppointmentBookingFlowApiDefinitionsJSON.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantAppointmentBookingFlowApiDefinitionsJSON.md b/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantAppointmentBookingFlowApiDefinitionsJSON.md
index 5fb62f2964..fb30b7dda9 100644
--- a/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantAppointmentBookingFlowApiDefinitionsJSON.md
+++ b/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantAppointmentBookingFlowApiDefinitionsJSON.md
@@ -6,7 +6,7 @@ Locale: en-US
 manager: bulenteg
 Module Name: MicrosoftTeams
 ms.author: tomkau
-online version: https://learn.microsoft.com/powershell/module/microsoftteams/new-csmainlineattendantappointmentbookingflowapidefinitionsJSON
+online version: https://learn.microsoft.com/powershell/module/microsoftteams/new-csmainlineattendantappointmentbookingflowapidefinitionsjson
 schema: 2.0.0
 title: New-CsMainLineAttendantAppointmentBookingFlowApiDefinitionsJSON
 ---

From d30fd610422fe26689fe8fb6d6b74a501e865740 Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Tue, 5 Aug 2025 14:51:55 -0700
Subject: [PATCH 058/145] Update
 New-CsMainlineAttendantAppointmentBookingFlow.md

---
 .../New-CsMainlineAttendantAppointmentBookingFlow.md            | 2 --
 1 file changed, 2 deletions(-)

diff --git a/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantAppointmentBookingFlow.md b/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantAppointmentBookingFlow.md
index b7e76968a6..f07207651e 100644
--- a/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantAppointmentBookingFlow.md
+++ b/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantAppointmentBookingFlow.md
@@ -102,8 +102,6 @@ Accept wildcard characters: False
 ###  -ApiDefinitions
 The parameters used by the API
 
-For an example, see [New-CsMainlineAttendantAppointBookingFlow -ApiDefinitions](./New-CsMainlineAttendantAppointmentBookingFlowApiDefinitionsJSON.md)
-
 ```yaml
 Type: String
 Parameter Sets: (All)

From a4505e3563d31221c216cb5399e7fea8dbe14273 Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Tue, 5 Aug 2025 14:52:41 -0700
Subject: [PATCH 059/145] Update New-CsMainlineAttendantQuestionAnswerFlow.md

---
 .../MicrosoftTeams/New-CsMainlineAttendantQuestionAnswerFlow.md | 2 --
 1 file changed, 2 deletions(-)

diff --git a/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantQuestionAnswerFlow.md b/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantQuestionAnswerFlow.md
index 3a38f4aada..e8ae2d797b 100644
--- a/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantQuestionAnswerFlow.md
+++ b/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantQuestionAnswerFlow.md
@@ -85,8 +85,6 @@ The knowledge base definition
 
 The parameters used by the API
 
-For an example, see [New-CsMainlineAttendantQuestionAnswerFlow -KnowledgeBase](./New-CsMainlineAttendantQuestionAnswerFlowKnowledgeBaseJSON.md)
-
 ```yaml
 Type: String
 Parameter Sets: (All)

From 45d108b6f69d0c753749e892f36baff8b9909661 Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Tue, 5 Aug 2025 14:53:14 -0700
Subject: [PATCH 060/145] Update
 Set-CsMainlineAttendantAppointmentBookingFlow.md

---
 .../Set-CsMainlineAttendantAppointmentBookingFlow.md            | 2 --
 1 file changed, 2 deletions(-)

diff --git a/teams/teams-ps/MicrosoftTeams/Set-CsMainlineAttendantAppointmentBookingFlow.md b/teams/teams-ps/MicrosoftTeams/Set-CsMainlineAttendantAppointmentBookingFlow.md
index faf6c8f740..61e17500cc 100644
--- a/teams/teams-ps/MicrosoftTeams/Set-CsMainlineAttendantAppointmentBookingFlow.md
+++ b/teams/teams-ps/MicrosoftTeams/Set-CsMainlineAttendantAppointmentBookingFlow.md
@@ -117,8 +117,6 @@ Accept wildcard characters: False
 ###  -ApiDefinitions
 The parameters used by the API
 
-For an example, see [New-CsMainlineAttendantAppointBookingFlow -ApiDefinitions](./New-CsMainlineAttendantAppointmentBookingFlowApiDefinitionsJSON.md)
-
 ```yaml
 Type: String
 Parameter Sets: (All)

From fdcdd004dfe18094a61af945f135978b1e16546c Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Tue, 5 Aug 2025 14:53:50 -0700
Subject: [PATCH 061/145] Update Set-CsMainlineAttendantQuestionAnswerFlow.md

---
 .../MicrosoftTeams/Set-CsMainlineAttendantQuestionAnswerFlow.md | 2 --
 1 file changed, 2 deletions(-)

diff --git a/teams/teams-ps/MicrosoftTeams/Set-CsMainlineAttendantQuestionAnswerFlow.md b/teams/teams-ps/MicrosoftTeams/Set-CsMainlineAttendantQuestionAnswerFlow.md
index 1dcc93e9a7..5335328561 100644
--- a/teams/teams-ps/MicrosoftTeams/Set-CsMainlineAttendantQuestionAnswerFlow.md
+++ b/teams/teams-ps/MicrosoftTeams/Set-CsMainlineAttendantQuestionAnswerFlow.md
@@ -100,8 +100,6 @@ The knowledge base definition
 
 The parameters used by the API
 
-For an example, see [New-CsMainlineAttendantQuestionAnswerFlow -KnowledgeBase](./New-CsMainlineAttendantQuestionAnswerFlowKnowledgeBaseJSON.md)
-
 ```yaml
 Type: String
 Parameter Sets: (All)

From 3834360e6ad62dcbc3fbfee2bce6b7bb625e2a69 Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Tue, 5 Aug 2025 14:59:14 -0700
Subject: [PATCH 062/145] Update
 New-CsMainlineAttendantAppointmentBookingFlowApiDefinitionsJSON.md

---
 ...MainlineAttendantAppointmentBookingFlowApiDefinitionsJSON.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantAppointmentBookingFlowApiDefinitionsJSON.md b/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantAppointmentBookingFlowApiDefinitionsJSON.md
index fb30b7dda9..4cf35b073c 100644
--- a/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantAppointmentBookingFlowApiDefinitionsJSON.md
+++ b/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantAppointmentBookingFlowApiDefinitionsJSON.md
@@ -14,7 +14,7 @@ title: New-CsMainLineAttendantAppointmentBookingFlowApiDefinitionsJSON
 # New-CsMainlineAttendantAppointmentBookingFlow -ApiDefinition JSON Example
 
 ## SYNOPSIS
-The [New-CsMainlineAttendantAppointmentBookingFlow](./New-CsMainlineAttendantAppointmentBookingFlow.md) -ApiDefinitions requires a JSON formatted response.
+The New-CsMainlineAttendantAppointmentBookingFlow -ApiDefinitions requires a JSON formatted response.
 
 ## SYNTAX
 

From 6ef373dd0c8b9e5a2e76957e07d04f539ce2ac75 Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Tue, 5 Aug 2025 15:04:38 -0700
Subject: [PATCH 063/145] Update
 New-CsMainlineAttendantAppointmentBookingFlowApiDefinitionsJSON.md

---
 ...inlineAttendantAppointmentBookingFlowApiDefinitionsJSON.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantAppointmentBookingFlowApiDefinitionsJSON.md b/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantAppointmentBookingFlowApiDefinitionsJSON.md
index 4cf35b073c..f93ae778b5 100644
--- a/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantAppointmentBookingFlowApiDefinitionsJSON.md
+++ b/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantAppointmentBookingFlowApiDefinitionsJSON.md
@@ -268,6 +268,10 @@ The New-CsMainlineAttendantAppointmentBookingFlow -ApiDefinitions requires a JSO
 } 
 ```
 
+## Description
+
+Some words here.
+
 ## PARAMETERS
 
 ###  -ApiDefinitions

From 517427ce46fc22f5f9b2bf5ba4b5e4e83975574d Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Tue, 5 Aug 2025 15:11:44 -0700
Subject: [PATCH 064/145] Delete
 teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantAppointmentBookingFlowApiDefinitionsJSON.md

---
 ...ppointmentBookingFlowApiDefinitionsJSON.md | 303 ------------------
 1 file changed, 303 deletions(-)
 delete mode 100644 teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantAppointmentBookingFlowApiDefinitionsJSON.md

diff --git a/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantAppointmentBookingFlowApiDefinitionsJSON.md b/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantAppointmentBookingFlowApiDefinitionsJSON.md
deleted file mode 100644
index f93ae778b5..0000000000
--- a/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantAppointmentBookingFlowApiDefinitionsJSON.md
+++ /dev/null
@@ -1,303 +0,0 @@
----
-applicable: Microsoft Teams
-author: tomkau
-external help file: Microsoft.Rtc.Management.dll-Help.xml
-Locale: en-US
-manager: bulenteg
-Module Name: MicrosoftTeams
-ms.author: tomkau
-online version: https://learn.microsoft.com/powershell/module/microsoftteams/new-csmainlineattendantappointmentbookingflowapidefinitionsjson
-schema: 2.0.0
-title: New-CsMainLineAttendantAppointmentBookingFlowApiDefinitionsJSON
----
-
-# New-CsMainlineAttendantAppointmentBookingFlow -ApiDefinition JSON Example
-
-## SYNOPSIS
-The New-CsMainlineAttendantAppointmentBookingFlow -ApiDefinitions requires a JSON formatted response.
-
-## SYNTAX
-
-```
-{ 
-	"generateAuthToken" : { // Must be specified for "bearer_token_dynamic" 
-		"endpoint" : "<endpoint>", // For example, https://www.contoso.com/home?parameter1=<parameter1>&parameter2=<parameter2> 
-		"method_type": "GET" or "PUT" or "POST", 
-		"description" : "<description>", 
-
-		"query_strings" : { // Description of the query string parameters in the endpoint 
-			"parameter1" : "<parameter1>", 
-			"parameter2" : "<parameter2>" 
-			}, 
-
-		"headers" : { 
-			"Authorization" : "Basic <constant>" or "api-key <constant>" or "Bearer <constant>", // replace <constant> with an expected value 
-			"X-API-Key" : "API-Key" // Only applicable for "api_key" auth type. 
-			}, 
-
-		"response" : { // Response to 200 range of codes 
-			"token" : "<token>" // this token will be used for APIs with "bearer_token_dynamic" auth type 
-			} 
-	}, 
-
-	"getCallerDetails" : [ // Can specify multiple endpoints below to get caller details by phone number, ID, email, etc. 
-	{ 
-		"endpoint" : "<endpoint1>", // For example, https://www.contoso.com/home?parameter1=<parameter1>&parameter2=<parameter2> 
-		"method_type": "GET" or "PUT" or "POST", 
-		"description" : "<description>", 
-		
-		"query_strings" : { // Definition of the query string parameters in the endpoint 
-			"parameter1" : "<parameter1>", 
-			"parameter2" : "<parameter2>" 
-			}, 
-
-		"headers" : { 
-			"Authorization" : "Basic <constant>" or "api-key <constant>" or "Bearer <constant>" or "Bearer <token>", // replace <constant> with an expected value. <token> will be replaced by the response to generateAuthToken()  
-			"X-API-Key" : "API-Key" // Only applicable for "api_key" auth type. 
-			}, 
-
-		"body" : { // Sent as JSON payload 
-			"in_parameter1" : "<in_parameter1>", 
-			"in_parameter2" : "<in_parameter2>" 
-			}, 
-
-		"response" : { // Response to 200 range of codes 
-			"out_parameter1" : "<out_parameter1>", 
-			"out_parameter2" : "<out_parameter2>", 
-			"out_parameter3" : "<out_parameter3>" 
-			} 
-	}, 
-
-	{ 
-		"endpoint" : "<endpoint2>", 
-		"method_type": "GET" or "PUT" or "POST", 
-		"description" : "<description>", 
-		"query_strings" : { 
-			"parameter1" : "<parameter1>", 
-			"parameter2" : "<parameter2>" 
-			}, 
-
-		"headers" : { 
-			"Authorization" : "Basic <constant>" or "api-key <constant>" or "Bearer <constant>" or "Bearer <token>", 
-			"X-API-Key" : "API-Key" 
-			}, 
-
-		"body" : { 
-			"in_parameter1" : "<in_parameter1>", 
-			"in_parameter2" : "<in_parameter2>" 
-			}, 
-
-		"response" : { 
-			"out_parameter1" : "<out_parameter1>", 
-			"out_parameter2" : "<out_parameter2>", 
-			"out_parameter3" : "<out_parameter3>" 
-		} 
-	}
-	], 
-
-	"initiateCallerAuthentication" : [ // for SMS/email code, verification link 
-	{ 
-		"endpoint" : "<endpoint>", 
-		"method_type": "GET" or "PUT" or "POST", 
-		"description" : "<description>", 
-
-		"query_strings" : { 
-			"parameter1" : "<parameter1>", 
-			"parameter2" : "<parameter2>" 
-			}, 
-
-		"headers" : { 
-			"Authorization" : "Basic <constant>" or "api-key <constant>" or "Bearer <constant>" or "Bearer <token>", 
-			"X-API-Key" : "API-Key" // Only applicable for "api_key" auth type. 
-			}, 
-
-		"body" : { 
-			"in_parameter1" : "<in_parameter1>", // phone number, user ID, etc 
-			"in_parameter2" : "<in_parameter2>"  // session ID 
-			}, 
-
-		"response" : { 
-			"out_parameter1" : "<out_parameter1>",  // success/failure 
-		} 
-    } 
-	], 
-
-	"authenticateCaller" : [ // for SMS/email code, voiceprint, verification link, caller details 
-	{ 
-		"endpoint" : "<endpoint>", 
-		"method_type": "GET" or "PUT" or "POST", 
-		"description" : "<description>", 
-
-		"query_strings" : { 
-			"parameter1" : "<parameter1>", 
-			"parameter2" : "<parameter2>" 
-			}, 
-
-	"headers" : { 
-		"Authorization" : "Basic <constant>" or "api-key <constant>" or "Bearer <constant>" or "Bearer <token>", 
-		"X-API-Key" : "API-Key" // Only applicable for "api_key" auth type. 
-		}, 
-
-	"body" : { 
-		"in_parameter1" : "<in_parameter1>", // phone number, user ID, etc 
-		"in_parameter2" : "<in_parameter2>", // session ID 
-		"in_parameter3" : "<in_parameter3>", // VoicePrint payload or code 
-		}, 
-
-	"response" : { 
-		"out_parameter1" : "<out_parameter1>",  // success/failure 
-		} 
-	} 
-	], 
-
-	"getAvailableAppointmentTimeslots" : [ 
-	{ 
-		"endpoint" : "<endpoint>", 
-		"method_type": "GET" or "PUT" or "POST", 
-		"description" : "<description>", 
-
-		"query_strings" : { 
-			"parameter1" : "<parameter1>", 
-			"parameter2" : "<parameter2>" 
-			}, 
-
-		"headers" : { 
-			"Authorization" : "Basic <constant>" or "api-key <constant>" or "Bearer <constant>" or "Bearer <token>", 
-			"X-API-Key" : "API-Key" 
-			}, 
-
-		"body" : { 
-			"start_time" : "YYYY-MM-DDTHH:mm:ss.sssZ" // Timezone as configured on the AA config in ISO 8601 standard  
-			"end_time" : "YYYY-MM-DDTHH:mm:ss.sssZ" // Timezone as configured on the AA config in ISO 8601 standard 
-			"in_parameter3" : "<in_parameter3>", // optional parameters like appointment type, doctor name, etc 
-			"in_parameter4" : "<in_parameter4>", // number of results 
-			}, 
-
-		"response" : { 
-			"time_slots" : [
-			{ 
-				"start_time" : "YYYY-MM-DDTHH:mm:ss.sssZ" // Timezone as configured on the AA config in ISO 8601 standard 
-				"end_time" : "YYYY-MM-DDTHH:mm:ss.sssZ" // Timezone as configured on the AA config in ISO 8601 standard 
-				"opt_parameter1" : "<opt_parameter1>", // optional parameters like appointment type, doctor name, etc 
-			}, 
-
-			{ 
-				"start_time" : "YYYY-MM-DDTHH:mm:ss.sssZ" // Timezone as configured on the AA config in ISO 8601 standard 
-				"end_time" : "YYYY-MM-DDTHH:mm:ss.sssZ" // Timezone as configured on the AA config in ISO 8601 standard 
-				"opt_parameter1" : "<opt_parameter1>", // optional parameters like appointment type, doctor name, etc 
-			} 
-			], 
-
-			"out_parameter3" : "<out_parameter3>", 
-			"out_parameter4" : "<out_parameter4>", 
-			} 
-	} 
-	], 
-
-	"bookAppointment" : [ 
-	{ 
-		"endpoint" : "<endpoint>", 
-		"method_type": "GET" or "PUT" or "POST", 
-		"description" : "<description>", 
-
-		"query_strings" : { 
-			"parameter1" : "<parameter1>", 
-			"parameter2" : "<parameter2>" 
-			}, 
-
-		"headers" : { 
-			"Authorization" : "Basic <constant>" or "api-key <constant>" or "Bearer <constant>" or "Bearer <token>", 
-			"X-API-Key" : "API-Key" 
-			}, 
-
-		"body" : { 
-			"start_time" : "YYYY-MM-DDTHH:mm:ss.sssZ" // Timezone as configured on the AA config in ISO 8601 standard 
-			"end_time" : "YYYY-MM-DDTHH:mm:ss.sssZ" // Timezone as configured on the AA config in ISO 8601 standard 
-			"in_parameter3" : "<in_parameter3>", // optional parameters like appointment type, doctor name, etc 
-			"in_parameter4" : "<in_parameter4>", // patient id 
-			}, 
-
-		"response" : { 
-			"out_parameter1" : "<out_parameter1>", // success/failure 
-			"out_parameter2" : "<out_parameter2>", 
-			} 
-	} 
-	], 
-
-	"getUpcomingAppointments" : [ 
-	{ 
-		"endpoint" : "<endpoint>", 
-		"method_type": "GET" or "PUT" or "POST", 
-		"description" : "<description>", 
-
-		"query_strings" : { 
-			"parameter1" : "<parameter1>", 
-			"parameter2" : "<parameter2>" 
-			}, 
-
-		"headers : { 
-			"Authorization" : "Basic <constant>" or "api-key <constant>" or "Bearer <constant>" or "Bearer <token>", 
-			"X-API-Key" : "API-Key" 
-			}, 
-
-		"body" : { 
-			"in_parameter1" : "<in_parameter1>", // phone number, user ID, etc 
-			"in_parameter2" : "<in_parameter2>" 
-			}, 
-
-		"response" : { 
-			"time_slots" : [ 
-			{ 
-				"start_time" : "YYYY-MM-DDTHH:mm:ss.sssZ" // Timezone as configured on the AA config in ISO 8601 standard 
-				"end_time" : "YYYY-MM-DDTHH:mm:ss.sssZ" // Timezone as configured on the AA config in ISO 8601 standard 
-				"opt_parameter1" : "<opt_parameter1>" // optional parameters like appointment type, doctor name, etc 
-			}, 
-
-			{ 
-				"start_time" : "YYYY-MM-DDTHH:mm:ss.sssZ" // Timezone as configured on the AA config in ISO 8601 standard 
-				"end_time" : "YYYY-MM-DDTHH:mm:ss.sssZ" // Timezone as configured on the AA config in ISO 8601 standard 
-				"opt_parameter1" : "<opt_parameter1>" // optional parameters like appointment type, doctor name, etc 
-			} 
-			], 
-
-			"out_parameter3" : "<out_parameter3>", 
-			"out_parameter4" : "<out_parameter4>" 
-			} 
-	} 
-	] 
-} 
-```
-
-## Description
-
-Some words here.
-
-## PARAMETERS
-
-###  -ApiDefinitions
-The parameters used by the API - see the JSON example above.
-
-```yaml
-Type: String
-Parameter Sets: (All)
-Aliases:
-
-Required: Yes
-Position: 0
-Default value: None
-Accept pipeline input: False
-Accept wildcard characters: False
-```
-
-## INPUTS
-
-## OUTPUTS
-
-### Microsoft.Rtc.Management.Hosted.CallQueue.Models.CallQueue
-
-## NOTES
-
-## RELATED LINKS
-
-
-

From 752e992116b8fe85b9ecc4f91cb5e73f8515d0eb Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Tue, 5 Aug 2025 15:12:11 -0700
Subject: [PATCH 065/145] Delete
 teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantQuestionAnswerFlowKnowledgeBaseJSON.md

---
 ...dantQuestionAnswerFlowKnowledgeBaseJSON.md | 132 ------------------
 1 file changed, 132 deletions(-)
 delete mode 100644 teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantQuestionAnswerFlowKnowledgeBaseJSON.md

diff --git a/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantQuestionAnswerFlowKnowledgeBaseJSON.md b/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantQuestionAnswerFlowKnowledgeBaseJSON.md
deleted file mode 100644
index 442ae3f811..0000000000
--- a/teams/teams-ps/MicrosoftTeams/New-CsMainlineAttendantQuestionAnswerFlowKnowledgeBaseJSON.md
+++ /dev/null
@@ -1,132 +0,0 @@
----
-applicable: Microsoft Teams
-author: tomkau
-external help file: Microsoft.Rtc.Management.dll-Help.xml
-Locale: en-US
-manager: bulenteg
-Module Name: MicrosoftTeams
-ms.author: tomkau
-online version: https://learn.microsoft.com/powershell/module/microsoftteams/new-csmainlineattendantquestionanswerflowknowledgebasejson
-schema: 2.0.0
-title: New-CsMainlineAttendantQuestionAnswerFlowKnowledgeBaseJSON
----
-
-# New-CsMainlineAttendantQuestionAnswerFlow -KnowledgeBase JSON Example
-
-## SYNOPSIS
-The [New-CsMainlineAttendantQuestionAnswerFlow](./New-CsMainlineAttendantQuestionAnswerFlow.md) -Knowledge requires a path to a JSON formatted response.
-
-## SYNTAX
-
-```
-[
-	{
-		"address_type" : "local_file",
-		"document_address" : "<local_address>", // provide full path to the local address
-		"description" : "<description>"
-		
-	},
-	{
-		"address_type" : "webpage",
-		"document_address" : "<web_address>", // provide full path to the webpage
-		"description" : "<description>"
-		
-	},
-	{
-		"address_type" : "api_endpoint",
-		"description" : "<description>",
-		"api_specification" : {
-			"generateAuthToken" : { // Must be specified for "bearer_token_dynamic"
-				"endpoint" : "<endpoint>", // For example, https://www.contoso.com/home?parameter1=<parameter1>&parameter2=<parameter2>
-				"method_type": "GET" or "PUT" or "POST",
-				"description" : "<description>",
-				"query_strings" : { // Description of the query string parameters in the endpoint
-					"parameter1" : "<parameter1>",
-					"parameter2" : "<parameter2>"
-				},
-				"headers" : {
-					"Authorization" : "Basic <constant>" or "api-key <constant>" or "Bearer <constant>", // replace <constant> with an expected value
-					"X-API-Key" : "API-Key" // Only applicable for "api_key" auth type.
-				},
-				"response" : { // Response to 200 range of codes
-					"token" : "<token>" // this token will be used for APIs with "bearer_token_dynamic" auth type
-				}
-			},
-			"getResults1" : {
-				"endpoint" : "<endpoint>", // For example, https://www.contoso.com/home?parameter1=<parameter1>&parameter2=<parameter2>
-				"method_type": "GET" or "PUT" or "POST",
-				"description" : "<description>",
-				"query_strings" : { // Definition of the query string parameters in the endpoint
-					"parameter1" : "<parameter1>",
-					"parameter2" : "<parameter2>"
-				},
-				"headers" : {
-					"Authorization" : "Basic <constant>" or "api-key <constant>" or "Bearer <constant>" or "Bearer <token>", // replace <constant> with an expected value. <token> will be replaced by the response to generateAuthToken() 
-					"X-API-Key" : "API-Key" // Only applicable for "api_key" auth type.
-				},
-				"body" : { // Sent as JSON payload
-					"in_parameter1" : "<in_parameter1>",
-					"in_parameter2" : "<in_parameter2>"
-				},
-				"response" : { // Response to 200 range of codes
-					"out_parameter1" : "<out_parameter1>",
-					"out_parameter2" : "<out_parameter2>",
-					"out_parameter3" : "<out_parameter3>"
-				}
-			},
-			"getResults2" : {
-				"endpoint" : "<endpoint>", // For example, https://www.contoso.com/home?parameter1=<parameter1>&parameter2=<parameter2>
-				"method_type": "GET" or "PUT" or "POST"
-				"description" : "<description>",
-				"query_strings" : { // Definition of the query string parameters in the endpoint
-					"parameter1" : "<parameter1>",
-					"parameter2" : "<parameter2>"
-				},
-				"headers" : {
-					"Authorization" : "Basic <constant>" or "api-key <constant>" or "Bearer <constant>" or "Bearer <token>", // replace <constant> with an expected value. <token> will be replaced by the response to generateAuthToken() 
-					"X-API-Key" : "API-Key" // Only applicable for "api_key" auth type.
-				},
-				"body" : { // Sent as JSON payload
-					"in_parameter1" : "<in_parameter1>",
-					"in_parameter2" : "<in_parameter2>"
-				},
-				"response" : { // Response to 200 range of codes
-					"out_parameter1" : "<out_parameter1>",
-					"out_parameter2" : "<out_parameter2>",
-					"out_parameter3" : "<out_parameter3>"
-				}
-			}
-		}
-	}
-]
-```
-
-## PARAMETERS
-
-###  -Knowledgebase
-The parameters used by the Knowledgebase - see the JSON example above.
-
-```yaml
-Type: String
-Parameter Sets: (All)
-Aliases:
-
-Required: Yes
-Position: 0
-Default value: None
-Accept pipeline input: False
-Accept wildcard characters: False
-```
-
-## INPUTS
-
-## OUTPUTS
-
-### Microsoft.Rtc.Management.Hosted.CallQueue.Models.CallQueue
-
-## NOTES
-
-## RELATED LINKS
-
-
-

From 65c7a904cfc0efb60d153f7d152b2f45a48ac03e Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Tue, 5 Aug 2025 15:14:26 -0700
Subject: [PATCH 066/145] Update New-CsAutoAttendantCallFlow.md

---
 teams/teams-ps/MicrosoftTeams/New-CsAutoAttendantCallFlow.md | 2 --
 1 file changed, 2 deletions(-)

diff --git a/teams/teams-ps/MicrosoftTeams/New-CsAutoAttendantCallFlow.md b/teams/teams-ps/MicrosoftTeams/New-CsAutoAttendantCallFlow.md
index 3db30d58e5..5edb50aea2 100644
--- a/teams/teams-ps/MicrosoftTeams/New-CsAutoAttendantCallFlow.md
+++ b/teams/teams-ps/MicrosoftTeams/New-CsAutoAttendantCallFlow.md
@@ -195,6 +195,4 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable
 
 [New-CsAutoAttendantMenu](https://learn.microsoft.com/powershell/module/microsoftteams/new-csautoattendantmenu)
 
-[New-CsAutoAttendantPrompt](https://learn.microsoft.com/powershell/module/microsoftteams/new-csautoattendantprompt)
-
 [Get-CsMainlineAttendantFlow](https://learn.microsoft.com/powershell/module/microsoftteams/new-csautoattendantprompt)

From 0e7d63be5cb544a537c7a9ae9696f49b3f6764d9 Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Tue, 5 Aug 2025 15:20:20 -0700
Subject: [PATCH 067/145] Update MicrosoftTeams.md

---
 teams/teams-ps/MicrosoftTeams/MicrosoftTeams.md | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/teams/teams-ps/MicrosoftTeams/MicrosoftTeams.md b/teams/teams-ps/MicrosoftTeams/MicrosoftTeams.md
index 5e7990cbf7..41f3696b81 100644
--- a/teams/teams-ps/MicrosoftTeams/MicrosoftTeams.md
+++ b/teams/teams-ps/MicrosoftTeams/MicrosoftTeams.md
@@ -125,6 +125,9 @@ Returns a list of all blocked number patterns added to the tenant list.
 ### [Get-CsInboundExemptNumberPattern](Get-CsInboundExemptNumberPattern.md)
 Returns a specific or the full list of all number patterns exempt from call blocking.
 
+### [Get-CsMainlineAttendantAppointmentBookingFlow](Get-CsMainlineAttendantAppointmentBookingFlow.md)
+Returns the identified Mainline attendant appointment booking flow.
+
 ### [Get-CsMeetingMigrationStatus](Get-CsMeetingMigrationStatus.md)
 You use the `Get-CsMeetingMigrationStatus` cmdlet to check the status of meeting migrations.
 

From de4f4a0b1adfd35f84c1797c94dc4c447f5cb019 Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Tue, 5 Aug 2025 15:27:09 -0700
Subject: [PATCH 068/145] Update Get-CsMainlineAttendantFlow.md

---
 teams/teams-ps/MicrosoftTeams/Get-CsMainlineAttendantFlow.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/teams/teams-ps/MicrosoftTeams/Get-CsMainlineAttendantFlow.md b/teams/teams-ps/MicrosoftTeams/Get-CsMainlineAttendantFlow.md
index b56b723e67..1360745f2e 100644
--- a/teams/teams-ps/MicrosoftTeams/Get-CsMainlineAttendantFlow.md
+++ b/teams/teams-ps/MicrosoftTeams/Get-CsMainlineAttendantFlow.md
@@ -14,7 +14,7 @@ title: Get-CsMainlineAttendantFlow
 # Get-CsMainlineAttendantFlow 
 
 ## SYNOPSIS
-Creates new Call Queue in your Skype for Business Online organization.
+The Get-CsMainlineAttendantFlow cmdlet returns information about the Mainline Attendant flows configured in your organization
 
 ## SYNTAX
 

From 28ac0eafe57fcb4ef5d30730faa6b7348d3b1354 Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Tue, 5 Aug 2025 15:29:02 -0700
Subject: [PATCH 069/145] Update MicrosoftTeams.md

---
 teams/teams-ps/MicrosoftTeams/MicrosoftTeams.md | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/teams/teams-ps/MicrosoftTeams/MicrosoftTeams.md b/teams/teams-ps/MicrosoftTeams/MicrosoftTeams.md
index 41f3696b81..2b5c24ee15 100644
--- a/teams/teams-ps/MicrosoftTeams/MicrosoftTeams.md
+++ b/teams/teams-ps/MicrosoftTeams/MicrosoftTeams.md
@@ -128,6 +128,12 @@ Returns a specific or the full list of all number patterns exempt from call bloc
 ### [Get-CsMainlineAttendantAppointmentBookingFlow](Get-CsMainlineAttendantAppointmentBookingFlow.md)
 Returns the identified Mainline attendant appointment booking flow.
 
+### [Get-CsMainlineAttendantFlow](Get-CsMainlineAttendantFlow.md)
+Returns information about the Mainline Attendant flows configured in your organization.
+
+### [Get-CsMainlineAttendantQuestionAnswerFlow](Get-CsMainlineAttendantQuestionAnswerFlow.md)
+Returns the identified Mainline attendant question and answer flow.
+
 ### [Get-CsMeetingMigrationStatus](Get-CsMeetingMigrationStatus.md)
 You use the `Get-CsMeetingMigrationStatus` cmdlet to check the status of meeting migrations.
 

From c504d81e0edf01de5f0dbe1a3ee3231fa0d7ac79 Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Tue, 5 Aug 2025 15:35:50 -0700
Subject: [PATCH 070/145] Update MicrosoftTeams.md

---
 .../teams-ps/MicrosoftTeams/MicrosoftTeams.md  | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)

diff --git a/teams/teams-ps/MicrosoftTeams/MicrosoftTeams.md b/teams/teams-ps/MicrosoftTeams/MicrosoftTeams.md
index 2b5c24ee15..1a498ef064 100644
--- a/teams/teams-ps/MicrosoftTeams/MicrosoftTeams.md
+++ b/teams/teams-ps/MicrosoftTeams/MicrosoftTeams.md
@@ -800,6 +800,12 @@ Adds a blocked number pattern to the tenant list.
 ### [New-CsInboundExemptNumberPattern](New-CsInboundExemptNumberPattern.md)
 This cmdlet lets you configure a new number pattern that is exempt from tenant call blocking.
 
+### [New-CsMainlineAttendantAppointmentBookingFlow](New-CsMainlineAttendantAppointmentBookingFlow.md)
+Creates new Mainline Attendant appointment booking flows.
+
+### [New-CsMainlineAttendantQuestionAnswerFlow](New-CsMainlineAttendantQuestionAnswerFlow.md)
+Creates new Mainline Attendant question and answer (FAQ) flows.
+
 ### [New-CsOnlineApplicationInstance](New-CsOnlineApplicationInstance.md)
 Creates an application instance in Microsoft Entra ID.
 
@@ -1073,6 +1079,12 @@ Removes a blocked number pattern from the tenant list.
 ### [Remove-CsInboundExemptNumberPattern](Remove-CsInboundExemptNumberPattern.md)
 Removes a number pattern exempt from call blocking.
 
+### [Remove-CsMainlineAttendantAppointmentBookingFlow](Remove-CsMainlineAttendantAppointmentBookingFlow.md)
+Removes an existing Mainline attendant appointment booking flow.
+
+### [Remove-CsMainlineAttendantQuestionAnswerFlow](Remove-CsMainlineAttendantQuestionAnswerFlow.md)
+Removes an existing Mainline attendant question and answer flow.
+
 ### [Remove-CsOnlineApplicationInstanceAssociation](Remove-CsOnlineApplicationInstanceAssociation.md)
 Use the Remove-CsOnlineApplicationInstanceAssociation cmdlet to remove the association between an application instance and the associated application configuration.
 
@@ -1349,6 +1361,12 @@ Modifies one or more parameters of a blocked number pattern in the tenant list.
 ### [Set-CsInboundExemptNumberPattern](Set-CsInboundExemptNumberPattern.md)
 Modifies one or more parameters of an exempt number pattern in the tenant list.
 
+### [Set-CsMainlineAttendantAppointmentBookingFlow](Set-CsMainlineAttendantAppointmentBookingFlow.md)
+Modifies an existing Mainline Attendant appointment booking flow.
+
+### [Set-CsMainlineAttendantQuestionAnswerFlow](Set-CsMainlineAttendantQuestionAnswerFlow.md)
+Modifies an existing Mainline Attendant question and answer (FAQ) flow.
+
 ### [Set-CsOnlineApplicationInstance](Set-CsOnlineApplicationInstance.md)
 Updates an application instance in Microsoft Entra ID.
 

From f01d83d180b5cd91795a0194b02c3c9814baa63f Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Tue, 5 Aug 2025 15:44:47 -0700
Subject: [PATCH 071/145] Update
 New-CsComplianceRecordingForCallQueueTemplate.md

---
 .../New-CsComplianceRecordingForCallQueueTemplate.md          | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/teams/teams-ps/MicrosoftTeams/New-CsComplianceRecordingForCallQueueTemplate.md b/teams/teams-ps/MicrosoftTeams/New-CsComplianceRecordingForCallQueueTemplate.md
index 2cc3f34801..e83c5e6371 100644
--- a/teams/teams-ps/MicrosoftTeams/New-CsComplianceRecordingForCallQueueTemplate.md
+++ b/teams/teams-ps/MicrosoftTeams/New-CsComplianceRecordingForCallQueueTemplate.md
@@ -43,9 +43,7 @@ This example creates a new Compliance Recording for Call Queue template.
 
 ### -BotId
 
-> Applicable: Microsoft Teams
-
-The Id of the compliance recording for call queue bot to invite.
+The Application Instance Id of the compliance recording bot to invite.
 
 ```yaml
 Type: System.String

From 0f1fcc0976111f335c7ba97614a8156b982fa100 Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Tue, 5 Aug 2025 15:45:14 -0700
Subject: [PATCH 072/145] Update
 New-CsComplianceRecordingForCallQueueTemplate.md

---
 .../New-CsComplianceRecordingForCallQueueTemplate.md            | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/teams/teams-ps/MicrosoftTeams/New-CsComplianceRecordingForCallQueueTemplate.md b/teams/teams-ps/MicrosoftTeams/New-CsComplianceRecordingForCallQueueTemplate.md
index e83c5e6371..676809efba 100644
--- a/teams/teams-ps/MicrosoftTeams/New-CsComplianceRecordingForCallQueueTemplate.md
+++ b/teams/teams-ps/MicrosoftTeams/New-CsComplianceRecordingForCallQueueTemplate.md
@@ -43,6 +43,8 @@ This example creates a new Compliance Recording for Call Queue template.
 
 ### -BotId
 
+> Applicable: Microsoft Teams
+
 The Application Instance Id of the compliance recording bot to invite.
 
 ```yaml

From 7be6deb8f461a32a4dcae010c7ef0f3f066f9691 Mon Sep 17 00:00:00 2001
From: Chris Davis <chris.davis@microsoft.com>
Date: Tue, 5 Aug 2025 17:08:27 -0700
Subject: [PATCH 073/145] Acrolinx 1

---
 .../docs-conceptual/client-advanced-settings.md  | 14 +++++++-------
 .../connect-exo-powershell-managed-identity.md   |  6 +++---
 .../connect-to-exo-powershell-c-sharp.md         |  2 +-
 .../exchange-online-powershell-v2.md             |  2 +-
 exchange/docs-conceptual/filter-properties.md    | 16 ++++++++--------
 .../recipientfilter-properties.md                |  4 ++--
 .../ExchangePowerShell/Add-ADPermission.md       |  4 ++--
 .../Add-AvailabilityAddressSpace.md              |  4 ++--
 .../Add-ContentFilterPhrase.md                   |  6 +++---
 .../Add-DatabaseAvailabilityGroupServer.md       |  2 +-
 .../Add-DistributionGroupMember.md               |  6 +++---
 .../ExchangePowerShell/Add-FederatedDomain.md    |  2 +-
 .../Add-GlobalMonitoringOverride.md              |  8 ++++----
 .../ExchangePowerShell/Add-IPAllowListEntry.md   |  2 +-
 .../ExchangePowerShell/Add-IPBlockListEntry.md   |  2 +-
 .../Add-MailboxDatabaseCopy.md                   | 12 ++++++------
 .../Add-MailboxFolderPermission.md               | 12 ++++++------
 .../ExchangePowerShell/Add-MailboxPermission.md  | 12 ++++++------
 .../Add-ManagementRoleEntry.md                   |  8 ++++----
 .../Add-PublicFolderAdministrativePermission.md  |  2 +-
 .../Add-PublicFolderClientPermission.md          |  4 ++--
 .../Add-RecipientPermission.md                   |  2 +-
 .../ExchangePowerShell/Add-ResubmitRequest.md    |  4 ++--
 .../ExchangePowerShell/Add-RoleGroupMember.md    | 10 +++++-----
 .../Add-ServerMonitoringOverride.md              |  6 +++---
 .../ExchangePowerShell/Add-UnifiedGroupLinks.md  |  4 ++--
 .../ExchangePowerShell/Clean-MailboxDatabase.md  |  4 ++--
 .../ExchangePowerShell/Clear-ActiveSyncDevice.md |  4 ++--
 .../ExchangePowerShell/Clear-MobileDevice.md     |  4 ++--
 .../Clear-TextMessagingAccount.md                |  4 ++--
 .../Compare-TextMessagingVerificationCode.md     |  4 ++--
 .../Complete-MigrationBatch.md                   |  6 +++---
 .../ExchangePowerShell/Connect-ExchangeOnline.md | 12 ++++++------
 .../ExchangePowerShell/Connect-Mailbox.md        |  6 +++---
 .../Delete-QuarantineMessage.md                  |  2 +-
 .../Disable-ATPProtectionPolicyRule.md           |  2 +-
 .../Disable-AddressListPaging.md                 |  2 +-
 .../ExchangePowerShell/Disable-AntiPhishRule.md  |  2 +-
 .../ExchangePowerShell/Disable-App.md            |  6 +++---
 .../Disable-CmdletExtensionAgent.md              |  2 +-
 .../Disable-DistributionGroup.md                 |  2 +-
 .../Disable-DnssecForVerifiedDomain.md           |  2 +-
 .../Disable-EOPProtectionPolicyRule.md           |  2 +-
 .../Disable-HostedContentFilterRule.md           |  2 +-
 .../Disable-HostedOutboundSpamFilterRule.md      |  2 +-
 .../Disable-IPv6ForAcceptedDomain.md             |  2 +-
 .../ExchangePowerShell/Disable-InboxRule.md      |  6 +++---
 .../Disable-JournalArchiving.md                  |  2 +-
 .../ExchangePowerShell/Disable-JournalRule.md    |  4 ++--
 .../ExchangePowerShell/Disable-MailContact.md    |  2 +-
 .../Disable-MailPublicFolder.md                  |  4 ++--
 .../ExchangePowerShell/Disable-MailUser.md       |  2 +-
 .../ExchangePowerShell/Disable-Mailbox.md        |  8 ++++----
 .../Disable-MailboxQuarantine.md                 |  4 ++--
 .../Disable-MalwareFilterRule.md                 |  4 ++--
 .../Disable-MetaCacheDatabase.md                 |  2 +-
 .../Disable-OutlookAnywhere.md                   |  4 ++--
 .../Disable-OutlookProtectionRule.md             |  4 ++--
 .../Disable-PushNotificationProxy.md             |  2 +-
 .../ExchangePowerShell/Disable-RemoteMailbox.md  | 10 +++++-----
 .../Disable-ReportSubmissionRule.md              |  2 +-
 .../Disable-SafeAttachmentRule.md                |  2 +-
 .../ExchangePowerShell/Disable-SafeLinksRule.md  |  2 +-
 .../Disable-ServiceEmailChannel.md               |  2 +-
 .../Disable-SmtpDaneInbound.md                   |  2 +-
 .../ExchangePowerShell/Disable-SweepRule.md      |  4 ++--
 .../ExchangePowerShell/Disable-TransportAgent.md |  2 +-
 .../ExchangePowerShell/Disable-TransportRule.md  |  4 ++--
 .../Disable-UMAutoAttendant.md                   |  4 ++--
 .../Disable-UMCallAnsweringRule.md               |  4 ++--
 .../ExchangePowerShell/Disable-UMIPGateway.md    |  2 +-
 .../ExchangePowerShell/Disable-UMMailbox.md      |  4 ++--
 .../ExchangePowerShell/Disable-UMServer.md       |  4 ++--
 .../ExchangePowerShell/Disable-UMService.md      |  4 ++--
 .../ExchangePowerShell/Dismount-Database.md      |  2 +-
 .../ExchangePowerShell/Dump-ProvisioningCache.md |  6 +++---
 .../Enable-ATPProtectionPolicyRule.md            |  2 +-
 .../Enable-AddressListPaging.md                  |  2 +-
 .../ExchangePowerShell/Enable-AntiPhishRule.md   |  2 +-
 .../exchange-ps/ExchangePowerShell/Enable-App.md |  6 +++---
 .../Enable-CmdletExtensionAgent.md               |  6 +++---
 .../Enable-ComplianceTagStorage.md               |  2 +-
 .../Enable-DistributionGroup.md                  |  4 ++--
 .../Enable-DnssecForVerifiedDomain.md            |  2 +-
 .../Enable-EOPProtectionPolicyRule.md            |  2 +-
 .../Enable-ExchangeCertificate.md                |  4 ++--
 .../Enable-HostedContentFilterRule.md            |  2 +-
 .../Enable-HostedOutboundSpamFilterRule.md       |  2 +-
 .../Enable-IPv6ForAcceptedDomain.md              |  2 +-
 .../ExchangePowerShell/Enable-InboxRule.md       |  6 +++---
 .../ExchangePowerShell/Enable-JournalRule.md     |  4 ++--
 .../ExchangePowerShell/Enable-MailContact.md     | 10 +++++-----
 .../Enable-MailPublicFolder.md                   |  4 ++--
 .../ExchangePowerShell/Enable-MailUser.md        | 10 +++++-----
 .../ExchangePowerShell/Enable-Mailbox.md         |  6 +++---
 .../Enable-MailboxQuarantine.md                  |  2 +-
 96 files changed, 208 insertions(+), 208 deletions(-)

diff --git a/exchange/docs-conceptual/client-advanced-settings.md b/exchange/docs-conceptual/client-advanced-settings.md
index 965318b2df..4ef196f94f 100644
--- a/exchange/docs-conceptual/client-advanced-settings.md
+++ b/exchange/docs-conceptual/client-advanced-settings.md
@@ -317,11 +317,11 @@ Use this advanced setting in conjunction with *ScannerMinCPU* to limit CPU consu
 
 - Value: \<number>**
 
-The value is set to **100** by default, which means there is no limit of maximum CPU consumption. In this case, the scanner process will try to use all available CPU time to maximize your scan rates.
+The value is set to **100** by default, which means there is no limit of maximum CPU consumption. In this case, the scanner process tries to use all available CPU time to maximize your scan rates.
 
-If you set **ScannerMaxCPU** to less than 100, the scanner will monitor the CPU consumption over the last 30 minutes. If the average CPU crossed the limit you set, it will start to reduce the number of threads allocated for new files.
+If you set **ScannerMaxCPU** to less than 100, the scanner monitors the CPU consumption over the last 30 minutes. If the average CPU crossed the limit you set, it starts to reduce the number of threads allocated for new files.
 
-The limit on the number of threads will continue as long as CPU consumption is higher than the limit set for **ScannerMaxCPU**.
+The limit on the number of threads continues as long as CPU consumption is higher than the limit set for **ScannerMaxCPU**.
 
 ## ScannerMinCPU
 
@@ -334,7 +334,7 @@ Used only if *ScannerMaxCPU* is not equal to 100, and cannot be set to a number
 
 We recommend keeping **ScannerMinCPU** set at least 15 points lower than the value of *ScannerMaxCPU*.
 
-The value is set to **50** by default, which means that if CPU consumption in the last 30 minutes when lower than this value, the scanner will start adding new threads to scan more files in parallel, until the CPU consumption reaches the level you have set for *ScannerMaxCPU*-15.
+The value is set to **50** by default, which means that if CPU consumption in the last 30 minutes when lower than this value, the scanner starts adding new threads to scan more files in parallel, until the CPU consumption reaches the level you have set for *ScannerMaxCPU*-15.
 
 ## ScannerConcurrencyLevel
 
@@ -361,17 +361,17 @@ Set-LabelPolicy -Identity Scanner -AdvancedSettings @{ScannerConcurrencyLevel="8
 
 By default, the information protection scanner scans all relevant files. However, you might want to define specific files to be skipped, such as for archived files or files that have been moved.
 
-Enable the scanner to skip specific files based on their file attributes by using the **ScannerFSAttributesToSkip** advanced setting. In the setting value, list the file attributes that will enable the file to be skipped when they are all set to **true**. This list of file attributes uses the AND logic.
+Enable the scanner to skip specific files based on their file attributes by using the **ScannerFSAttributesToSkip** advanced setting. In the setting value, list the file attributes that enable the file to be skipped when they are all set to **true**. This list of file attributes uses the AND logic.
 
 Example PowerShell commands, where your label policy is named "Global".
 
-**Skip files that are both read-only and archived**
+**Skip files that are both read-only and archived**:
 
 ```PowerShell
 Set-LabelPolicy -Identity Global -AdvancedSettings @{ ScannerFSAttributesToSkip =" FILE_ATTRIBUTE_READONLY, FILE_ATTRIBUTE_ARCHIVE"}
 ```
 
-**Skip files that are either read-only or archived**
+**Skip files that are either read-only or archived**:
 
 To use an OR logic, run the same property multiple times. For example:
 
diff --git a/exchange/docs-conceptual/connect-exo-powershell-managed-identity.md b/exchange/docs-conceptual/connect-exo-powershell-managed-identity.md
index 5266f57d04..8baf75ef9f 100644
--- a/exchange/docs-conceptual/connect-exo-powershell-managed-identity.md
+++ b/exchange/docs-conceptual/connect-exo-powershell-managed-identity.md
@@ -68,7 +68,7 @@ The first command in the PowerShell runbook must be the `Connect-ExchangeOnline.
 Connect-ExchangeOnline -ManagedIdentity -Organization contoso.onmicrosoft.com
 ```
 
-After that, as a test, you can start with as simple, low-impact command in the runbook before moving on to more complex commands or scripts. For example:
+After that, as a test, you can start with as simple, low risk command in the runbook before moving on to more complex commands or scripts. For example:
 
 ```powershell
 Get-AcceptedDomain | Format-Table Name
@@ -118,7 +118,7 @@ Connect-ExchangeOnline -ManagedIdentity -Organization contoso.onmicrosoft.com -M
 
 You get the ManagedIdentityAccount value from [Step 3: Store the user-assigned managed identity in a variable](#step-3-store-the-user-assigned-managed-identity-in-a-variable).
 
-After that, as a test, you can start with as simple, low-impact command in the runbook before moving on to more complex commands or scripts. For example:
+After that, as a test, you can start with as simple, low risk command in the runbook before moving on to more complex commands or scripts. For example:
 
 ```powershell
 Get-AcceptedDomain | Format-Table Name
@@ -285,7 +285,7 @@ To verify that the module imported successfully, run the following command:
 Get-AzAutomationModule -ResourceGroupName ContosoRG -AutomationAccountName ContosoAzAuto1 -Name ExchangeOnlineManagement
 ```
 
-During the import, the ProvisioningState property will have the value Creating. When the module import is complete, the value will change to Succeeded.
+During the import, the ProvisioningState property has the value Creating. When the module import is complete, the value changes to Succeeded.
 
 For detailed syntax and parameter information, see [New-AzAutomationModule](/powershell/module/az.automation/new-azautomationmodule).
 
diff --git a/exchange/docs-conceptual/connect-to-exo-powershell-c-sharp.md b/exchange/docs-conceptual/connect-to-exo-powershell-c-sharp.md
index f34a86b8d1..f372350e60 100644
--- a/exchange/docs-conceptual/connect-to-exo-powershell-c-sharp.md
+++ b/exchange/docs-conceptual/connect-to-exo-powershell-c-sharp.md
@@ -207,7 +207,7 @@ void ParallelConnectionsToExchangeOnline()
 
         // Set the ThreadOptions to reuse the same threads for the runspaces so that
 
-        // the Exchange Online cmdlets will be available after running Connect-ExchangeOnline in each runspace.
+        // the Exchange Online cmdlets are available after running Connect-ExchangeOnline in each runspace.
 
         pool.ThreadOptions = PSThreadOptions.ReuseThread;
 
diff --git a/exchange/docs-conceptual/exchange-online-powershell-v2.md b/exchange/docs-conceptual/exchange-online-powershell-v2.md
index f149901408..0f362ffe35 100644
--- a/exchange/docs-conceptual/exchange-online-powershell-v2.md
+++ b/exchange/docs-conceptual/exchange-online-powershell-v2.md
@@ -591,7 +591,7 @@ Unless otherwise noted, the current release of the Exchange Online PowerShell mo
 - **Get-VivaModuleFeature** now returns information about ParentFeature, ChildFeature, and PolicyModes. These values represent parent and child features of a Viva app feature along with available enablement modes for future policies.  
 - New parameters _IsUserOptedInByDefault_ on the **Add-VivaModuleFeaturePolicy** and **Update-VivaModuleFeaturePolicy** cmdlets and the corresponding property value in all **\*-VivaModuleFeaturePolicy** cmdlets. The value indicates if users are opted in or out by the policy, as long as the user doesn't set a preference.
 
-  You can use this parameter to keep the feature enabled in your organization while opting out the impacted users by default, effectively soft disabling the feature for those users.
+  You can use this parameter to keep the feature enabled in your organization while opting out the affected users by default, effectively soft disabling the feature for those users.
 
 - Deprecated the **Get-VivaFeatureCategory** cmdlet, all category-related parameters, and return values (_CategoryId_, _IsCategoryEnabled_).
 
diff --git a/exchange/docs-conceptual/filter-properties.md b/exchange/docs-conceptual/filter-properties.md
index c351b83884..12f17e81b9 100644
--- a/exchange/docs-conceptual/filter-properties.md
+++ b/exchange/docs-conceptual/filter-properties.md
@@ -532,7 +532,7 @@ For example, `Get-CASMailbox -Filter 'EcpEnabled -eq $false'`.
 
 For example, `Get-Recipient -Filter "EmailAddresses -like 'marketing*'"`.
 
-When you use a complete email address, you don't need to account for the `smtp:` prefix. If you use wildcards, you do. For example, if `"EmailAddresses -eq 'lila@fabrikam.com'"` returns a match, `"EmailAddresses -like 'lila*'"` won't return a match, but or `"EmailAddresses -like 'smtp:lila*'"` will return a match.
+When you use a complete email address, you don't need to account for the `smtp:` prefix. If you use wildcards, you do. For example, if `"EmailAddresses -eq 'lila@fabrikam.com'"` returns a match, `"EmailAddresses -like 'lila*'"` won't return a match, but `"EmailAddresses -like 'smtp:lila*'"` returns a match.
 
 Although this property is multi-valued, the filter returns a match if the property _contains_ the specified value.
 
@@ -640,7 +640,7 @@ For example, `Get-Recipient -Filter 'ExternalDirectoryObjectId -ne $null'`.
 
 For example, `Get-Recipient -Filter "ExternalEmailAddress -like '@fabrikam.com*'"`.
 
-When you use a complete email address, you don't need to account for the `smtp:` prefix. If you use wildcards, you do. For example, if `"ExternalEmailAddress -eq 'lila@fabrikam.com'"` returns a match, `"ExternalEmailAddress -like 'lila*'"` won't return a match, but `"ExternalEmailAddress -like 'smtp:lila*'"` will return a match.
+When you use a complete email address, you don't need to account for the `smtp:` prefix. If you use wildcards, you do. For example, if `"ExternalEmailAddress -eq 'lila@fabrikam.com'"` returns a match, `"ExternalEmailAddress -like 'lila*'"` won't return a match, but `"ExternalEmailAddress -like 'smtp:lila*'"` returns a match.
 
 ## ExternalOofOptions
 
@@ -684,7 +684,7 @@ To find the distinguished name of a forwarding recipient, replace _\<RecipientId
 
 For example, `Get-Mailbox -Filter "ForwardingSmtpAddress -like '@fabrikam.com*'"`.
 
-When you use a complete email address, you don't need to account for the `smtp:` prefix. If you use wildcards, you do. For example, if `"ForwardingSmtpAddress -eq 'lila@fabrikam.com'"` returns a match, `"ForwardingSmtpAddress -like 'lila*'"` won't return a match, but `"ForwardingSmtpAddress -like 'smtp:lila*'"` will return a match.
+When you use a complete email address, you don't need to account for the `smtp:` prefix. If you use wildcards, you do. For example, if `"ForwardingSmtpAddress -eq 'lila@fabrikam.com'"` returns a match, `"ForwardingSmtpAddress -like 'lila*'"` doesn't return a match, but `"ForwardingSmtpAddress -like 'smtp:lila*'"` returns a match.
 
 ## GeneratedOfflineAddressBooks
 
@@ -734,7 +734,7 @@ For example, `Get-UnifiedGroup -Filter "GroupExternalMemberCount -gt 0"`.
 
 Distribution groups have the value `Universal`, and mail-enabled security groups have the value `Universal, SecurityEnabled`. You can specify multiple values separated by commas, and the order doesn't matter. For example, `Get-DistributionGroup -Filter "GroupType -eq 'Universal,SecurityEnabled'"` returns the same results as `Get-DistributionGroup -Filter "GroupType -eq 'SecurityEnabled,Universal'"`.
 
-This multivalued property will only return a match if the property _equals_ the specified value.
+This multivalued property returns a match only if the property _equals_ the specified value.
 
 ## Guid
 
@@ -978,7 +978,7 @@ This property is named **Languages** in the properties of a mailbox, and it cont
 
 You can specify multiple values separated by commas, but the order matters. For example, `Get-Mailbox -Filter "LanguagesRaw -eq 'en-US,es-MX'"` returns different results than `Get-Mailbox -Filter "LanguagesRaw -eq 'es-MX,en-US'"`.
 
-For single values, this multivalued property will return a match if the property _contains_ the specified value.
+For single values, this multivalued property returns a match only if the property _contains_ the specified value.
 
 ## LastExchangeChangedTime
 
@@ -1058,7 +1058,7 @@ For example, `Get-Mailbox -Filter "MailboxMoveFlags -ne 'None'"`.
 
 You can specify multiple values separated by commas, and the order doesn't matter. For example, `Get-Recipient -Filter "MailboxMoveFlags -eq 'IntraOrg,Pull'"` returns the same results as `Get-Recipient -Filter "MailboxMoveFlags -eq 'Pull,IntraOrg'"`.
 
-This multivalued property will only return a match if the property _equals_ the specified value.
+This multivalued property returns a match only if the property _equals_ the specified value.
 
 ## MailboxMoveRemoteHostName
 
@@ -1514,7 +1514,7 @@ For example, `Get-User -Filter 'PreviousRecipientTypeDetails -ne $null'`.
 |---|---|---|
 |n/a|**Get-CASMailbox** <br/> **Get-DistributionGroup** <br/> **Get-DynamicDistributionGroup** <br/> **Get-Mailbox** <br/> **Get-MailContact** <br/> **Get-MailPublicFolder** <br/> **Get-MailUser** <br/> **Get-Recipient** <br/> **Get-RemoteMailbox** <br/> **Get-UMMailbox** <br/> **Get-UnifiedGroup**|String (wildcards accepted)|
 
-Don't use the _PrimarySmtpAddress_ property; use the _EmailAddresses_ property instead. Any filter that uses the _PrimarySmtpAddress_ property will also search values in the _EmailAddresses_ property. For example, if a mailbox has the primary email address dario@contoso.com, and the additional proxy addresses dario2@contoso.com and dario3@contoso.com, all of the following filters will return that mailbox in the result: `"PrimarySmtpAddress -eq 'dario@contoso.com'"`, `"PrimarySmtpAddress -eq 'dario2@contoso.com'"`, or `"PrimarySmtpAddress -eq 'dario3@contoso.com'"`.
+Don't use the _PrimarySmtpAddress_ property; use the _EmailAddresses_ property instead. Any filter that uses the _PrimarySmtpAddress_ property also searchs values in the _EmailAddresses_ property. For example, if a mailbox has the primary email address dario@contoso.com, and the additional proxy addresses dario2@contoso.com and dario3@contoso.com, all of the following filters return that mailbox in the result: `"PrimarySmtpAddress -eq 'dario@contoso.com'"`, `"PrimarySmtpAddress -eq 'dario2@contoso.com'"`, or `"PrimarySmtpAddress -eq 'dario3@contoso.com'"`.
 
 ## ProhibitSendQuota
 
@@ -2085,7 +2085,7 @@ For example, `Get-User -Filter "UserAccountControl -eq 'NormalAccount'"`.
 
 You can specify multiple values separated by commas, but the order matters. For example, `Get-User -Filter "UserAccountControl -eq 'AccountDisabled,NormalAccount'"` returns different results than `Get-User -Filter "UserAccountControl -eq 'NormalAccount,AccountDisabled'"`.
 
-This multivalued property will only return a match if the property _equals_ the specified value.
+This multivalued property returns a match only if the property _equals_ the specified value.
 
 ## UserPrincipalName
 
diff --git a/exchange/docs-conceptual/recipientfilter-properties.md b/exchange/docs-conceptual/recipientfilter-properties.md
index f94d2a8186..6e2a411bad 100644
--- a/exchange/docs-conceptual/recipientfilter-properties.md
+++ b/exchange/docs-conceptual/recipientfilter-properties.md
@@ -117,7 +117,7 @@ The recipient properties that have been *confirmed* to work with the _RecipientF
 |_EwsApplicationAccessPolicy_|_msExchEwsApplicationAccessPolicy_|`EnforceAllowList` or `EnforceBlockList`.||
 |_EwsEnabled_|_msExchEwsEnabled_|Integer||
 |_ExchangeGuid_|_msExchMailboxGuid_|String (wildcards accepted).||
-|_ExchangeUserAccountControl_|_msExchUserAccountControl_|For valid values, see [ADS_USER_FLAG_ENUM enumeration](/windows/win32/api/iads/ne-iads-ads_user_flag_enum). The integer values will work as described. Most of the text values won't work as described (even if you remove `ADS_UF` and all underscores).||
+|_ExchangeUserAccountControl_|_msExchUserAccountControl_|For valid values, see [ADS_USER_FLAG_ENUM enumeration](/windows/win32/api/iads/ne-iads-ads_user_flag_enum). The integer values work as described. Most of the text values don't work as described (even if you remove `ADS_UF` and all underscores).||
 |_ExchangeVersion_|_msExchVersion_|Dynamic distribution groups: String (wildcards accepted). <br> Others: `ExchangeObjectVersion` values.||
 |_ExpansionServer_|_msExchExpansionServerName_|String (wildcards accepted).||
 |_ExtensionCustomAttribute1_ to _ExtensionCustomAttribute5_|_msExchExtensionCustomAttribute1_ to _msExchExtensionCustomAttribute5_|String (wildcards accepted).|Currently, these attributes aren't useable as filters in Exchange Online. For more information, see [Microsoft Entra Connect Sync: Attributes synchronized to Microsoft Entra ID](/entra/identity/hybrid/connect/reference-connect-sync-attributes-synchronized).|
@@ -223,7 +223,7 @@ The recipient properties that have been *confirmed* to work with the _RecipientF
 |_PostOfficeBox_|_postOfficeBox_|String (wildcards accepted).||
 |_PreviousRecipientTypeDetails_|_msExchPreviousRecipientTypeDetails_|For valid values, see the description of the _RecipientTypeDetails_ parameter in [Get-Recipient](/powershell/module/exchangepowershell/get-recipient).||
 |_PrimaryGroupId_|_primaryGroupId_|Integer|For domain users, the value of this property is typically 513, which corresponds to the Domain Users group.|
-|_PrimarySmtpAddress_|n/a|String (wildcards accepted).|Don't use the _PrimarySmtpAddress_ property; use the _EmailAddresses_ property instead. Any filter that uses the _PrimarySmtpAddress_ property will also search values in the _EmailAddresses_ property. For example, if a mailbox has the primary email address dario@contoso.com, and the additional proxy addresses dario2@contoso.com and dario3@contoso.com, all of the following filters will return that mailbox in the result: `"PrimarySmtpAddress -eq 'dario@contoso.com'"`, `"PrimarySmtpAddress -eq 'dario2@contoso.com'"`, or `"PrimarySmtpAddress -eq 'dario3@contoso.com'"`.|
+|_PrimarySmtpAddress_|n/a|String (wildcards accepted).|Don't use the _PrimarySmtpAddress_ property; use the _EmailAddresses_ property instead. Any filter that uses the _PrimarySmtpAddress_ property also searches values in the _EmailAddresses_ property. For example, if a mailbox has the primary email address `dario@contoso.com`, and the additional proxy addresses `dario2@contoso.com` and `dario3@contoso.com`, all of the following filters return that mailbox in the result: `"PrimarySmtpAddress -eq 'dario@contoso.com'"`, `"PrimarySmtpAddress -eq 'dario2@contoso.com'"`, or `"PrimarySmtpAddress -eq 'dario3@contoso.com'"`.|
 |_ProhibitSendQuota_|_mDBOverQuotaLimit_|Dynamic distribution groups: A byte quantified size value (for example, `50MB` or `1.5GB`). Unqualified values are treated as bytes. <br> Others: Blank or non-blank.||
 |_ProhibitSendReceiveQuota_|_mDBOverHardQuotaLimit_|Dynamic distribution groups: A byte quantified size value (for example, `50MB` or `1.5GB`). Unqualified values are treated as bytes. <br> Others: Blank or non-blank.||
 |_ProtocolSettings_|_protocolSettings_|String (wildcards accepted).||
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-ADPermission.md b/exchange/exchange-ps/ExchangePowerShell/Add-ADPermission.md
index 0f883fb2c0..14512499ab 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-ADPermission.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Add-ADPermission.md
@@ -64,9 +64,9 @@ Add-ADPermission [[-Identity] <ADRawEntryIdParameter>] -Instance <ADAcePresentat
 ```
 
 ## DESCRIPTION
-The ADPermission cmdlets can be used to directly modify Active Directory access control lists (ACLs). Although some Microsoft Exchange features may continue to use the ADPermission cmdlets to manage permissions (for example Send and Receive connectors), Exchange 2013 and later versions no longer use customized ACLs to manage administrative permissions. If you want to grant or deny administrative permissions in Exchange 2013 or later, you need to use Role Based Access Control (RBAC). For more information about RBAC, see [Permissions in Exchange Server](https://learn.microsoft.com/Exchange/permissions/permissions).
+The ADPermission cmdlets can be used to directly modify Active Directory access control lists (ACLs). Although some Microsoft Exchange features might continue to use the ADPermission cmdlets to manage permissions (for example Send and Receive connectors), Exchange 2013 and later versions no longer use customized ACLs to manage administrative permissions. If you want to grant or deny administrative permissions in Exchange 2013 or later, you need to use Role Based Access Control (RBAC). For more information about RBAC, see [Permissions in Exchange Server](https://learn.microsoft.com/Exchange/permissions/permissions).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-AvailabilityAddressSpace.md b/exchange/exchange-ps/ExchangePowerShell/Add-AvailabilityAddressSpace.md
index dae8361398..6260a607b7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-AvailabilityAddressSpace.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Add-AvailabilityAddressSpace.md
@@ -13,7 +13,7 @@ title: Add-AvailabilityAddressSpace
 # Add-AvailabilityAddressSpace
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Add-AvailabilityAddressSpace cmdlet to create availability address space objects that are used to share free/busy data across Exchange organizations.
 
@@ -40,7 +40,7 @@ Add-AvailabilityAddressSpace -AccessMethod <AvailabilityAccessMethod> -ForestNam
 ## DESCRIPTION
 In Exchange Online, you need to run the New-AvailabilityConfig cmdlet before you run the Add-AvailabilityAddressSpace cmdlet.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-ContentFilterPhrase.md b/exchange/exchange-ps/ExchangePowerShell/Add-ContentFilterPhrase.md
index 6065a9815c..ccaca37c2f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-ContentFilterPhrase.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Add-ContentFilterPhrase.md
@@ -32,7 +32,7 @@ Add-ContentFilterPhrase [-Phrase] <String> -Influence <Influence>
 ## DESCRIPTION
 The Add-ContentFilterPhrase cmdlet adds phrases to the Allow or Block phrases list.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -41,7 +41,7 @@ You need to be assigned permissions before you can run this cmdlet. Although thi
 Add-ContentFilterPhrase -Phrase "Free credit report" -Influence BadWord
 ```
 
-This example adds the phrase Free credit report to the Block phrase list. Any messages that contain this phrase will be marked as spam by the Content Filtering agent.
+This example adds the phrase Free credit report to the Block phrase list. Any messages that contain this phrase are marked as spam by the Content Filtering agent.
 
 ## PARAMETERS
 
@@ -67,7 +67,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-The Influence parameter specifies whether the phrase being added will cause the messages that contain the phrase to be allowed or blocked. Valid values are GoodWord and BadWord.
+The Influence parameter specifies whether the phrase being added cause messages that contain the phrase to be allowed or blocked. Valid values are GoodWord and BadWord.
 
 A message that contains a custom word or phrase that has an Influence value of GoodWord is automatically assigned a spam confidence level (SCL) rating of 0 and therefore bypasses downstream spam processing. A message that contains a custom word or phrase that has an Influence value of BadWord is automatically assigned an SCL rating of 9 and therefore is treated as spam.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-DatabaseAvailabilityGroupServer.md b/exchange/exchange-ps/ExchangePowerShell/Add-DatabaseAvailabilityGroupServer.md
index 897bf7a61f..270c31ad74 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-DatabaseAvailabilityGroupServer.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Add-DatabaseAvailabilityGroupServer.md
@@ -37,7 +37,7 @@ To add a Mailbox server to a DAG, the Mailbox server must be running the Windows
 
 To add the first server to a DAG and create a computer object for the DAG, the Exchange Windows Permissions security group must have the appropriate rights to add computer accounts to the domain. Alternatively, a computer account can be created and disabled prior to adding the server. Adding the first server to the DAG enables the computer account for the DAG. Thus, the account used for the task doesn't need permissions to add a computer account to the domain. If you're pre-creating the computer account, the name of the account must match the name for the DAG. For example, if the DAG is named DAG1, the computer account must be named DAG1.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-DistributionGroupMember.md b/exchange/exchange-ps/ExchangePowerShell/Add-DistributionGroupMember.md
index b87a4f59b9..b9bf4d3aa9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-DistributionGroupMember.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Add-DistributionGroupMember.md
@@ -13,7 +13,7 @@ title: Add-DistributionGroupMember
 # Add-DistributionGroupMember
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Add-DistributionGroupMember cmdlet to add a single recipient to distribution groups and mail-enabled security groups. To replace all members, use the Update-DistributionGroupMember cmdlet.
 
@@ -32,7 +32,7 @@ Add-DistributionGroupMember [-Identity] <DistributionGroupIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -147,7 +147,7 @@ The Member parameter specifies the recipient that you want to add to the group.
 - Email address
 - GUID
 
-Although it isn't required, it's a good idea to add only security principals (for example, mailboxes and mail users with user accounts or other mail-enabled security groups) to mail-enabled security groups. If you assign permissions to a mail-enabled security group, any members that aren't security principals (for example, mail contacts or distribution groups) won't have the permissions assigned.
+Although it isn't required, it's a good idea to add only security principals (for example, mailboxes and mail users with user accounts or other mail-enabled security groups) to mail-enabled security groups. If you assign permissions to a mail-enabled security group, any members that aren't security principals (for example, mail contacts or distribution groups) don't have the permissions assigned.
 
 ```yaml
 Type: RecipientWithAdUserGroupIdParameter
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-FederatedDomain.md b/exchange/exchange-ps/ExchangePowerShell/Add-FederatedDomain.md
index 25568ab2fa..99df25b20e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-FederatedDomain.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Add-FederatedDomain.md
@@ -36,7 +36,7 @@ You can add any registered Internet domain to the federated organization identif
 
 For more details, see [Federation](https://learn.microsoft.com/exchange/federation-exchange-2013-help).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-GlobalMonitoringOverride.md b/exchange/exchange-ps/ExchangePowerShell/Add-GlobalMonitoringOverride.md
index 7cdc6eb202..c8cbb2af7c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-GlobalMonitoringOverride.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Add-GlobalMonitoringOverride.md
@@ -44,7 +44,7 @@ Add-GlobalMonitoringOverride [-Identity] <String> -ItemType <MonitoringItemTypeE
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -53,14 +53,14 @@ You need to be assigned permissions before you can run this cmdlet. Although thi
 Add-GlobalMonitoringOverride -Identity "FrontendTransport\OnPremisesInboundProxy" -PropertyName Enabled -PropertyValue 0 -Duration 30.00:00:00 -ItemType Probe
 ```
 
-This example adds a global monitoring override that disables the OnPremisesInboundProxy probe for 30 days. Note that the value of Identity is case-sensitive.
+This example adds a global monitoring override that disables the OnPremisesInboundProxy probe for 30 days. The value of Identity is case-sensitive.
 
 ### Example 2
 ```powershell
 Add-GlobalMonitoringOverride -Identity "MailboxSpace\StorageLogicalDriveSpaceEscalate" -PropertyName Enabled -PropertyValue 0 -ItemType Responder -ApplyVersion "15.01.0225.0422"
 ```
 
-This example adds a global monitoring override that disables the StorageLogicalDriveSpaceEscalate responder for all Exchange 2016 servers running version 15.01.0225.0422. Note that the value of Identity is case-sensitive.
+This example adds a global monitoring override that disables the StorageLogicalDriveSpaceEscalate responder for all Exchange 2016 servers running version 15.01.0225.0422. The value of Identity is case-sensitive.
 
 ## PARAMETERS
 
@@ -68,7 +68,7 @@ This example adds a global monitoring override that disables the StorageLogicalD
 
 > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-The Identity parameter specifies the identity of the probe, monitor, or responder. This parameter uses the syntax `HealthSetName\MonitoringItemName[\TargetResource]`. Note that the values are case sensitive. For example, use `AD\ActiveDirectoryConnectivityServerReboot`, not `ad\activedirectoryconnectivityserverreboot`.
+The Identity parameter specifies the identity of the probe, monitor, or responder. This parameter uses the syntax `HealthSetName\MonitoringItemName[\TargetResource]`. The values are case sensitive. For example, use `AD\ActiveDirectoryConnectivityServerReboot`, not `ad\activedirectoryconnectivityserverreboot`.
 
 ```yaml
 Type: String
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-IPAllowListEntry.md b/exchange/exchange-ps/ExchangePowerShell/Add-IPAllowListEntry.md
index 8aeb4bef69..a084014efb 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-IPAllowListEntry.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Add-IPAllowListEntry.md
@@ -147,7 +147,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-The ExpirationTime parameter specifies a day and time when the IP Allow list entry that you're creating will expire. If you specify a time only and you don't specify a date, the current day is assumed.
+The ExpirationTime parameter specifies a day and time when the IP Allow list entry expires. If you specify a time only and you don't specify a date, the current day is assumed.
 
 Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-IPBlockListEntry.md b/exchange/exchange-ps/ExchangePowerShell/Add-IPBlockListEntry.md
index c121c4bd15..5507b123be 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-IPBlockListEntry.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Add-IPBlockListEntry.md
@@ -146,7 +146,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-The ExpirationTime parameter specifies a day and time when the IP Block list entry that you're creating will expire. If you specify a time only and you don't specify a date, the current day is assumed.
+The ExpirationTime parameter specifies a day and time when the IP Block list entry expires. If you specify a time only and you don't specify a date, the current day is assumed.
 
 Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-MailboxDatabaseCopy.md b/exchange/exchange-ps/ExchangePowerShell/Add-MailboxDatabaseCopy.md
index e255aaa90a..b5d228a706 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-MailboxDatabaseCopy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Add-MailboxDatabaseCopy.md
@@ -41,11 +41,11 @@ To use the Add-MailboxDatabaseCopy cmdlet to add a mailbox database copy, the fo
 - The specified Mailbox server must be in the same database availability group (DAG), and the DAG must have quorum and be healthy.
 - The specified Mailbox server must not already host a copy of the specified mailbox database.
 - The database path used by the specified database must also be available on the specified Mailbox server, because all copies of a database must use the same path.
-- If you're adding the second copy of a database (for example, adding the first passive copy of the database), circular logging must not be enabled for the specified mailbox database. If circular logging is enabled, you must first disable it. After the mailbox database copy has been added, circular logging can be enabled. After enabling circular logging for a replicated mailbox database, continuous replication circular logging (CRCL) is used instead of JET circular logging. If you're adding the third or subsequent copy of a database, CRCL can remain enabled.
+- If you're adding the second copy of a database (for example, adding the first passive copy of the database), circular logging must not be enabled for the specified mailbox database. If circular logging is enabled, you must first disable it. After the mailbox database copy is added, circular logging can be enabled. After enabling circular logging for a replicated mailbox database, continuous replication circular logging (CRCL) is used instead of JET circular logging. If you're adding the third or subsequent copy of a database, CRCL can remain enabled.
 
 After running the Add-MailboxDatabaseCopy cmdlet, the new copy remains in a Suspended state if the SeedingPostponed parameter is specified. When the database copy status is set to Suspended, the SuspendMessage is set to "Replication is suspended for database copy '{0}' because database needs to be seeded."
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -98,7 +98,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-The MailboxServer parameter specifies the name of the server that will host the database copy. This server must be a member of the same DAG and must not already host a copy of the database.
+The MailboxServer parameter specifies the name of the server that hosts the database copy. This server must be a member of the same DAG and must not already host a copy of the database.
 
 ```yaml
 Type: MailboxServerIdParameter
@@ -136,7 +136,7 @@ Accept wildcard characters: False
 
 The ConfigurationOnly switch allows database copies to be added without invoking automatic seeding. You don't need to specify a value with this switch.
 
-The source database does not need to be online or present when using this parameter. It will create a new database in Active Directory without contacting the target server. This parameter may be useful in situations where the target server is down for maintenance and the new database copy does not yet exist on the target server.
+The source database does not need to be online or present when using this parameter. It creates a new database in Active Directory without contacting the target server. This parameter might be useful in situations where the target server is down for maintenance and the new database copy does not yet exist on the target server.
 
 ```yaml
 Type: SwitchParameter
@@ -199,7 +199,7 @@ To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = h
 
 The default value is 24:00:00 (24 hours). To disable deferred lagged copy play down, specify the value 00:00:00.
 
-Note that when the disk is running out of space, the value of this parameter is ignored and lagged copy play down occurs without delay.
+When the disk is running out of space, the value of this parameter is ignored and lagged copy play down occurs without delay.
 
 ```yaml
 Type: EnhancedTimeSpan
@@ -257,7 +257,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-The TruncationLagTime parameter specifies the amount of time that the Microsoft Exchange Replication service waits before truncating log files that have replayed into a copy of the database. The time period begins after the log has been successfully replayed into the copy of the database.
+The TruncationLagTime parameter specifies the amount of time that the Microsoft Exchange Replication service waits before truncating log files that have replayed into a copy of the database. The time period begins after the log is successfully replayed into the copy of the database.
 
 To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes and ss = seconds.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-MailboxFolderPermission.md b/exchange/exchange-ps/ExchangePowerShell/Add-MailboxFolderPermission.md
index 721fa3fe78..1b2f8ebb8e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-MailboxFolderPermission.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Add-MailboxFolderPermission.md
@@ -13,7 +13,7 @@ title: Add-MailboxFolderPermission
 # Add-MailboxFolderPermission
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Add-MailboxFolderPermission cmdlet to add folder-level permissions for users in mailboxes.
 
@@ -34,7 +34,7 @@ Add-MailboxFolderPermission [-Identity] <MailboxFolderIdParameter> -AccessRights
 ## DESCRIPTION
 To modify the permissions that are assigned to the user on a mailbox folder, use the Set-MailboxFolderPermission cmdlet. To remove all permissions that are assigned to a user on a mailbox folder, use the Remove-MailboxFolderPermission cmdlet.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -229,10 +229,10 @@ Accept wildcard characters: False
 
 This parameter is available only in the cloud-based service.
 
-The SendNotificationToUser parameter specifies whether to send a sharing invitation to the user when you add calendar permissions for them. The message will be a normal calendar sharing invitation that can be accepted by the recipient. Valid values are:
+The SendNotificationToUser parameter specifies whether to send a sharing invitation to the user when you add calendar permissions for them. The message is a normal calendar sharing invitation that can be accepted by the recipient. Valid values are:
 
 - $true: A sharing invitation is sent.
-- $false: No sharing invitation is sent. This is the default value.
+- $false: No sharing invitation is sent. This value is the default.
 
 This parameter only applies to calendar folders and can only be used with the following AccessRights parameter values:
 
@@ -261,8 +261,8 @@ This parameter is available only in the cloud-based service.
 
 The SharingPermissionFlags parameter assigns calendar delegate permissions. This parameter only applies to calendar folders and can only be used when the AccessRights parameter value is Editor. Valid values are:
 
-- None: Has no effect. This is the default value.
-- Delegate: The user is made a calendar delegate, which includes receiving meeting invites and responses. If there are no other delegates, this value will create the meeting message rule. If there are existing delegates, the user is added to the meeting message rule without changing how delegate messages are sent.
+- None: Has no effect. This value is the default.
+- Delegate: The user is made a calendar delegate, which includes receiving meeting invites and responses. If there are no other delegates, this value creates the meeting message rule. If there are existing delegates, the user is added to the meeting message rule without changing how delegate messages are sent.
 - CanViewPrivateItems: The user can access private items on the calendar. You must use this value with the Delegate value.
 
 You can specify multiple values separated by commas.
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-MailboxPermission.md b/exchange/exchange-ps/ExchangePowerShell/Add-MailboxPermission.md
index accc016d50..893d646309 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-MailboxPermission.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Add-MailboxPermission.md
@@ -13,7 +13,7 @@ title: Add-MailboxPermission
 # Add-MailboxPermission
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Add-MailboxPermission cmdlet to add permissions to a mailbox or to an Exchange Server 2016, Exchange Server 2019, or Exchange Online mail user.
 
@@ -67,7 +67,7 @@ Add-MailboxPermission [[-Identity] <MailboxIdParameter>] -Instance <MailboxAcePr
 > [!NOTE]
 > You can use this cmdlet to add a maximum of 500 permission entries (ACEs) to a mailbox. To grant permissions to more than 500 users, use security groups instead of individual users for the User parameter. Security groups contain many members, but only count as one entry.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -165,7 +165,7 @@ Accept wildcard characters: False
 
 This parameter is available only in on-premises Exchange.
 
-This parameter has been deprecated and is no longer used.
+This parameter is deprecated and no longer used.
 
 ```yaml
 Type: MailboxAcePresentationObject
@@ -228,7 +228,7 @@ The User parameter specifies who gets the permissions on the mailbox. You can sp
 - Mail users
 - Mail-enabled security groups (non-mail-enabled security groups are selectable, but they don't work)
 
-**Note**: When a mail-enabled security group is used to specify Full Access permissions, the auto-mapping feature won't automatically add the mailbox in Outlook for the group member. For more information, see [Mailboxes to which your account has full access aren't automapped to Outlook profile](https://learn.microsoft.com/outlook/troubleshoot/profiles-and-accounts/full-access-mailbox-not-automapped-outlook-profile).
+**Note**: When a mail-enabled security group is used to specify Full Access permissions, the auto-mapping feature doesn't automatically add the mailbox in Outlook for the group member. For more information, see [Mailboxes to which your account has full access aren't automapped to Outlook profile](https://learn.microsoft.com/outlook/troubleshoot/profiles-and-accounts/full-access-mailbox-not-automapped-outlook-profile).
 
 For the best results, we recommend using the following values:
 
@@ -266,9 +266,9 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
 
-The AutoMapping parameter includes or excludes the mailbox from the auto-mapping feature in Microsoft Outlook. Auto-mapping uses Autodiscover to automatically add mailboxes to a user's Outlook profile if the user has Full Access permission to the mailbox. However, Autodiscover won't enumerate security groups that are given Full Access permission to the mailbox. Valid values are:
+The AutoMapping parameter includes or excludes the mailbox from the auto-mapping feature in Microsoft Outlook. Auto-mapping uses Autodiscover to automatically add mailboxes to a user's Outlook profile if the user has Full Access permission to the mailbox. However, Autodiscover doesn't enumerate security groups that have Full Access permission to the mailbox. Valid values are:
 
-- $true: The mailbox is automatically added to the user's Outlook profile if the user has Full Access permission. This is the default value.
+- $true: The mailbox is automatically added to the user's Outlook profile if the user has Full Access permission. This value is the default.
 - $false: The mailbox is not automatically added to the user's Outlook profile if the user has Full Access permission.
 
 **Note**: To disable auto-mapping for a mailbox where the user was already assigned Full Access permission, you need to remove the user's Full Access permission by using the Remove-MailboxPermission cmdlet, and then reassign the user Full Access permission on the mailbox using the AutoMapping parameter with the value $false.
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-ManagementRoleEntry.md b/exchange/exchange-ps/ExchangePowerShell/Add-ManagementRoleEntry.md
index c356ae0e7b..29a7f33b0f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-ManagementRoleEntry.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Add-ManagementRoleEntry.md
@@ -13,7 +13,7 @@ title: Add-ManagementRoleEntry
 # Add-ManagementRoleEntry
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Add-ManagementRoleEntry cmdlet to add management role entries to an existing management role.
 
@@ -50,11 +50,11 @@ Add-ManagementRoleEntry [-ParentRoleEntry] <RoleEntryIdParameter> -Role <RoleIdP
 ## DESCRIPTION
 The cmdlet and its parameters that you add to a role entry must exist in the parent role. You can't add role entries to built-in roles.
 
-You can only add a role entry to a management role if the role entry exists in the role's parent role. For example, if you try to add the Search-Mailbox role entry to a role that's a child of the Mail Recipients role, you'll receive an error. This error occurs because the Search-Mailbox role entry doesn't exist in the Mail Recipients role. To add the Search-Mailbox role entry to a role, you need to create a role that's a child of the Mailbox Import Export role, which contains the Search-Mailbox role entry. Then you can use the Add-ManagementRoleEntry cmdlet to add the Search-Mailbox role entry to the new child role.
+You can only add a role entry to a management role if the role entry exists in the role's parent role. For example, if you try to add the Search-Mailbox role entry to a role that's a child of the Mail Recipients role, you get an error. This error occurs because the Search-Mailbox role entry doesn't exist in the Mail Recipients role. To add the Search-Mailbox role entry to a role, you need to create a role that's a child of the Mailbox Import Export role, which contains the Search-Mailbox role entry. Then you can use the Add-ManagementRoleEntry cmdlet to add the Search-Mailbox role entry to the new child role.
 
 For more information about management role entries, see [Understanding management roles](https://learn.microsoft.com/exchange/understanding-management-roles-exchange-2013-help).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -84,7 +84,7 @@ This example uses the Get-ManagementRoleEntry cmdlet to retrieve a list of all t
 Add-ManagementRoleEntry "IT Scripts\MailboxAudit" -Parameters "Department","Location" -UnScopedTopLevel
 ```
 
-In on-premises Exchange, this example adds the MailboxAudit script with the Department and Location parameters to the IT Scripts unscoped top-level role. Note that the UnScopedTopLevel switch requires the UnScoped Role Management role, which isn't assigned to any role groups by default.
+In on-premises Exchange, this example adds the MailboxAudit script with the Department and Location parameters to the IT Scripts unscoped top-level role. The UnScopedTopLevel switch requires the UnScoped Role Management role, which isn't assigned to any role groups by default.
 
 ## PARAMETERS
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-PublicFolderAdministrativePermission.md b/exchange/exchange-ps/ExchangePowerShell/Add-PublicFolderAdministrativePermission.md
index 7049b48a5c..58bb304fa4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-PublicFolderAdministrativePermission.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Add-PublicFolderAdministrativePermission.md
@@ -58,7 +58,7 @@ Add-PublicFolderAdministrativePermission [-Identity] <PublicFolderIdParameter> -
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-PublicFolderClientPermission.md b/exchange/exchange-ps/ExchangePowerShell/Add-PublicFolderClientPermission.md
index e65cd078af..67c5796bd3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-PublicFolderClientPermission.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Add-PublicFolderClientPermission.md
@@ -13,7 +13,7 @@ title: Add-PublicFolderClientPermission
 # Add-PublicFolderClientPermission
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Add-PublicFolderClientPermission cmdlet to add permissions to public folders.
 
@@ -31,7 +31,7 @@ Add-PublicFolderClientPermission [-Identity] <PublicFolderIdParameter> -AccessRi
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-RecipientPermission.md b/exchange/exchange-ps/ExchangePowerShell/Add-RecipientPermission.md
index 2a629a5a0d..e6aa528fc3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-RecipientPermission.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Add-RecipientPermission.md
@@ -31,7 +31,7 @@ Add-RecipientPermission [-Identity] <RecipientIdParameter> -AccessRights <MultiV
 ## DESCRIPTION
 SendAs permission allows a user or group members to send messages that appear to come from the specified mailbox, mail contact, mail user, or group.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-ResubmitRequest.md b/exchange/exchange-ps/ExchangePowerShell/Add-ResubmitRequest.md
index 05205b5d59..fd3ed1aef1 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-ResubmitRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Add-ResubmitRequest.md
@@ -51,7 +51,7 @@ Add-ResubmitRequest -EndTime <DateTime> -StartTime <DateTime>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -171,7 +171,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2016, Exchange Server 2019
 
-The MessageId parameter filters the results by the Message-ID header field of the message. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which may include angle brackets) and enclose the value in quotation marks (for example, "<d9683b4c-127b-413a-ae2e-fa7dfb32c69d@contoso.com>").
+The MessageId parameter filters the results by the Message-ID header field of the message. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which might include angle brackets) and enclose the value in quotation marks (for example, "<d9683b4c-127b-413a-ae2e-fa7dfb32c69d@contoso.com>").
 
 ```yaml
 Type: String
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-RoleGroupMember.md b/exchange/exchange-ps/ExchangePowerShell/Add-RoleGroupMember.md
index 4b06eb4397..51471eb69b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-RoleGroupMember.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Add-RoleGroupMember.md
@@ -13,7 +13,7 @@ title: Add-RoleGroupMember
 # Add-RoleGroupMember
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Add-RoleGroupMember cmdlet to add members to a management role group.
 
@@ -33,13 +33,13 @@ Add-RoleGroupMember [-Identity] <RoleGroupIdParameter> -Member <SecurityPrincipa
 ## DESCRIPTION
 When you add a member to a role group, the member is given the effective permissions provided by the management roles assigned to the role group.
 
-If the ManagedBy property has been populated with role group managers, the user adding a role group member must be a role group manager. Alternately, if the user is a member of the Organization Management role group or is directly or indirectly assigned the Role Management role, the BypassSecurityGroupManagerCheck switch can be used to override the security group management check.
+If the ManagedBy property is populated with role group managers, the user adding a role group member must be a role group manager. Alternately, if the user is a member of the Organization Management role group or is directly or indirectly assigned the Role Management role, the BypassSecurityGroupManagerCheck switch can be used to override the security group management check.
 
 In on-premises Exchange, if the role group is a linked role group, you can't use the Add-RoleGroupMember cmdlet to add members to the role group. Instead, you need to add members to the foreign universal security group (USG) that's linked to the linked role group. To find the foreign USG that's linked to a role group, use the Get-RoleGroup cmdlet.
 
 For more information about role groups, see [Understanding management role groups](https://learn.microsoft.com/exchange/understanding-management-role-groups-exchange-2013-help).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -55,9 +55,9 @@ This example adds the user David to the role group Recipient Management.
 Get-User -Filter "Department -eq 'Sales' -and RecipientType -eq 'UserMailbox'" | Get-Mailbox | Add-RoleGroupMember "Sales and Marketing Group" -WhatIf
 ```
 
-This example finds all the mailboxes that are part of the Sales department and adds them to the Sales and Marketing Group role group. Because we're using the WhatIf switch, the changes aren't written to the role group, so you can verify that the correct members will be added.
+This example finds all the mailboxes that are part of the Sales department and adds them to the Sales and Marketing Group role group. Because we're using the WhatIf switch, the changes aren't written to the role group, so you can verify that the correct members are added.
 
-After you've verified that the correct members will be added to the role group, remove the WhatIf switch and run the command again.
+After you verify the correct members are added to the role group, remove the WhatIf switch and run the command again.
 
 For more information about pipelining and the WhatIf parameter, see the following topics:
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-ServerMonitoringOverride.md b/exchange/exchange-ps/ExchangePowerShell/Add-ServerMonitoringOverride.md
index 09faae554b..868e0d75a3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-ServerMonitoringOverride.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Add-ServerMonitoringOverride.md
@@ -39,7 +39,7 @@ Add-ServerMonitoringOverride [-Identity] <String> -ItemType <MonitoringItemTypeE
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -48,7 +48,7 @@ You need to be assigned permissions before you can run this cmdlet. Although thi
 Add-ServerMonitoringOverride -Identity "AD\ActiveDirectoryConnectivityConfigDCServerReboot" -Server EXCH03 -ItemType Responder -PropertyName Enabled -PropertyValue 0 -Duration 20.00:00:00
 ```
 
-This example adds a server monitoring override that disables the responder ActiveDirectoryConnectivityConfigDCServerReboot on the server named EXCH03 for 20 days. Note that the value of Identity is case-sensitive.
+This example adds a server monitoring override that disables the responder ActiveDirectoryConnectivityConfigDCServerReboot on the server named EXCH03 for 20 days. The value of Identity is case-sensitive.
 
 ## PARAMETERS
 
@@ -56,7 +56,7 @@ This example adds a server monitoring override that disables the responder Activ
 
 > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-The Identity parameter specifies the identity of the monitoring item that you want to override. This parameter uses the syntax `HealthSet\MonitoringItemName[\TargetResource]`. Note that the values are case sensitive. For example, use `AD\ActiveDirectoryConnectivityConfigDCServerReboot`, not `ad\activedirectoryconnectivityconfigdcserverreboot`.
+The Identity parameter specifies the identity of the monitoring item that you want to override. This parameter uses the syntax `HealthSet\MonitoringItemName[\TargetResource]`. The values are case sensitive. For example, use `AD\ActiveDirectoryConnectivityConfigDCServerReboot`, not `ad\activedirectoryconnectivityconfigdcserverreboot`.
 
 You can use Get-ServerHealth to find the correct object for the monitoring item you want to override.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-UnifiedGroupLinks.md b/exchange/exchange-ps/ExchangePowerShell/Add-UnifiedGroupLinks.md
index a4786f7f64..dd5eb3475f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-UnifiedGroupLinks.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Add-UnifiedGroupLinks.md
@@ -36,9 +36,9 @@ Add-UnifiedGroupLinks [-Identity] <UnifiedGroupIdParameter> -Links <RecipientIdP
 ## DESCRIPTION
 Microsoft 365 Groups are group objects that are available across Microsoft 365 services.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
-**Note**: Only members can be owners of a group, so you must first add a user as member before adding it as an owner. Guest users cannot be an owner of groups, even if the users are members of the groups.
+**Note**: Only members can be owners of a group, so you must first add a user as member before adding it as an owner. Guest users can't be an owner of groups, even if the users are members of the groups.
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Clean-MailboxDatabase.md b/exchange/exchange-ps/ExchangePowerShell/Clean-MailboxDatabase.md
index feca97fac4..c43e7bb860 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Clean-MailboxDatabase.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Clean-MailboxDatabase.md
@@ -34,9 +34,9 @@ A connected mailbox has two parts: the mailbox object in the Exchange store and
 
 If you want to reconnect a disconnected mailbox to an Active Directory user account, use the Connect-Mailbox cmdlet.
 
-Under normal circumstances, it isn't necessary to run the Clean-MailboxDatabase cmdlet because a mailbox is marked as disconnected immediately after the Disable-Mailbox or Remove-Mailbox command completes. If you used the Disable-Mailbox cmdlet or the Remove-Mailbox cmdlet while the Microsoft Exchange Information Store service was stopped, or if a mailbox was disabled by an external means other than the Disable-Mailbox cmdlet or Remove-Mailbox cmdlet, you may want to use the Clean-MailboxDatabase cmdlet to scan for disconnected mailboxes.
+Under normal circumstances, it isn't necessary to run the Clean-MailboxDatabase cmdlet because a mailbox is marked as disconnected immediately after the Disable-Mailbox or Remove-Mailbox command completes. If you used the Disable-Mailbox cmdlet or the Remove-Mailbox cmdlet while the Microsoft Exchange Information Store service was stopped, or if a mailbox was disabled by an external means other than the Disable-Mailbox cmdlet or Remove-Mailbox cmdlet, you might want to use the Clean-MailboxDatabase cmdlet to scan for disconnected mailboxes.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Clear-ActiveSyncDevice.md b/exchange/exchange-ps/ExchangePowerShell/Clear-ActiveSyncDevice.md
index bf8643a66b..e4b6f04148 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Clear-ActiveSyncDevice.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Clear-ActiveSyncDevice.md
@@ -13,7 +13,7 @@ title: Clear-ActiveSyncDevice
 # Clear-ActiveSyncDevice
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Clear-ActiveSyncDevice cmdlet to delete all data from a mobile device.
 
@@ -38,7 +38,7 @@ The Clear-ActiveSyncDevice cmdlet deletes all user data from a mobile device the
 
 After you run this cmdlet, you receive a warning that states: "This command will force all the data on the device to be permanently deleted. Do you want to continue?" You must respond to the warning for the cmdlet to run on the mobile phone.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Clear-MobileDevice.md b/exchange/exchange-ps/ExchangePowerShell/Clear-MobileDevice.md
index 0c9f6522b3..5e979a1257 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Clear-MobileDevice.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Clear-MobileDevice.md
@@ -13,7 +13,7 @@ title: Clear-MobileDevice
 # Clear-MobileDevice
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Clear-MobileDevice cmdlet to delete all data from a mobile phone. This action is often called a remote device wipe.
 
@@ -37,7 +37,7 @@ The Clear-MobileDevice cmdlet deletes all user data from a mobile device the nex
 
 After you run this cmdlet, you receive a warning that states: "This command will force all the data on the device to be permanently deleted. Do you want to continue?" You must respond to the warning for the cmdlet to run on the mobile phone.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Clear-TextMessagingAccount.md b/exchange/exchange-ps/ExchangePowerShell/Clear-TextMessagingAccount.md
index 8a3a2a9579..9e32e22536 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Clear-TextMessagingAccount.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Clear-TextMessagingAccount.md
@@ -13,7 +13,7 @@ title: Clear-TextMessagingAccount
 # Clear-TextMessagingAccount
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 The Clear-TextMessagingAccount cmdlet allows a user to remove the text messaging settings from their own mailbox. An administrator can't use this cmdlet to remove the text messaging settings from another user's mailbox.
 
@@ -33,7 +33,7 @@ Clear-TextMessagingAccount [-Identity] <MailboxIdParameter>
 ## DESCRIPTION
 The Clear-TextMessagingAccount cmdlet clears all of a user's text messaging settings, including communication and notification settings.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Compare-TextMessagingVerificationCode.md b/exchange/exchange-ps/ExchangePowerShell/Compare-TextMessagingVerificationCode.md
index 1eb6f7ca40..2c69601d73 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Compare-TextMessagingVerificationCode.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Compare-TextMessagingVerificationCode.md
@@ -13,7 +13,7 @@ title: Compare-TextMessagingVerificationCode
 # Compare-TextMessagingVerificationCode
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Compare-TextMessagingVerificationCode cmdlet to verify the text messaging verification code that the user specified as part of configuring text message notifications on the mailbox.
 
@@ -34,7 +34,7 @@ The Compare-TextMessagingVerificationCode cmdlet returns the value true if the c
 
 When text messaging notifications are enabled on a mailbox, you can configure calendar notifications, voice mail notifications, and email notifications using an inbox rule.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Complete-MigrationBatch.md b/exchange/exchange-ps/ExchangePowerShell/Complete-MigrationBatch.md
index a47891ea77..47da89c99b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Complete-MigrationBatch.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Complete-MigrationBatch.md
@@ -13,7 +13,7 @@ title: Complete-MigrationBatch
 # Complete-MigrationBatch
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Complete-MigrationBatch cmdlet to finalize a migration batch for a local move, cross-forest move, or remote move migration that has successfully finished initial synchronization.
 
@@ -40,13 +40,13 @@ After a migration batch for a local or cross-forest move has successfully run an
 - Configures the user's Microsoft Outlook profile to point to the new target domain.
 - Converts the source mailbox to a mail-enabled user in the source domain.
 
-In the cloud-based service, this cmdlet sets the value of CompleteAfter to the current time. It is important to remember that any CompleteAfter setting that has been applied to the individual users within the batch will override the setting on the batch, so the completion for some users may be delayed until their configured time.
+In the cloud-based service, this cmdlet sets the value of CompleteAfter to the current time. It is important to remember that any CompleteAfter setting applied to the individual users within the batch overrides the setting on the batch, so the completion for some users might be delayed until their configured time.
 
 When the finalization process is complete, you can remove the batch by using the Remove-MigrationBatch cmdlet.
 
 If a migration batch has a status of Completed with Errors, you can re-attempt to finalize the failed users. In Exchange Online, use the Start-MigrationBatch cmdlet to retry migration for failed users. In Exchange 2013 or Exchange 2016, use the Complete-MigrationBatch to retry these failed users.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Connect-ExchangeOnline.md b/exchange/exchange-ps/ExchangePowerShell/Connect-ExchangeOnline.md
index 04e48a420d..b424b12ca1 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Connect-ExchangeOnline.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Connect-ExchangeOnline.md
@@ -740,7 +740,7 @@ Accept wildcard characters: False
 
 The ShowProgress parameter specifies whether to show or hide the progress bar of imported cmdlets when you connect. Valid values are:
 
-- $true: The progress bar is displayed. This is the default value.
+- $true: The progress bar is displayed. This value is the default.
 - $false: Currently, this value has no effect.
 
 ```yaml
@@ -785,7 +785,7 @@ Accept wildcard characters: False
 
 **Note**: This parameter is available in version 3.3.0 or later of the module.
 
-In version 3.7.0-Preview1 or later, this parameter is replaced by the LoadCmdletHelp parameter. The SkipLoadingCmdletHelp parameter is no longer required and no longer does anything, because cmdlet help files are no longer downloaded by default. Eventually, this parameter will be retired, so remove it from any scripts.
+In version 3.7.0-Preview1 or later, this parameter is replaced by the LoadCmdletHelp parameter. The SkipLoadingCmdletHelp parameter is no longer required and no longer does anything, because cmdlet help files are no longer downloaded by default.
 
 The SkipLoadingCmdletHelp switch prevents downloading the cmdlet help files for the Get-Help cmdlet in REST API connections. You don't need to specify a value with this switch.
 
@@ -811,7 +811,7 @@ Accept wildcard characters: False
 
 The SkipLoadingFormatData switch prevents downloading the format data for REST API connections. You don't need to specify a value with this switch.
 
-When you use this switch, the output of any Exchange cmdlet will be unformatted.
+When you use this switch, the output of any Exchange cmdlet is unformatted.
 
 Use this switch to avoid errors when connecting to Exchange Online PowerShell from within a Windows service or the Windows PowerShell SDK.
 
@@ -836,7 +836,7 @@ Accept wildcard characters: False
 The TrackPerformance parameter measures additional events (for example, CPU load and memory consumed). Valid values are:
 
 - $true: Performance tracking is enabled.
-- $false: Performance tracking is disabled. This is the default value.
+- $false: Performance tracking is disabled. This value is the default.
 
 This parameter works only when logging is enabled.
 
@@ -858,8 +858,8 @@ Accept wildcard characters: False
 
 The UseMultithreading parameter specifies whether to disable or enable multi-threading in the Exchange Online PowerShell module. Valid values are:
 
-- $true: Enable multi-threading. This is the default value.
-- $false: Disable multi-threading. This value will degrade the performance of the nine exclusive **Get-EXO\*** cmdlets in the module.
+- $true: Enable multi-threading. This value is the default.
+- $false: Disable multi-threading. This value degrades the performance of the nine exclusive **Get-EXO\*** cmdlets in the module.
 
 ```yaml
 Type: Boolean
diff --git a/exchange/exchange-ps/ExchangePowerShell/Connect-Mailbox.md b/exchange/exchange-ps/ExchangePowerShell/Connect-Mailbox.md
index cb4c8cfa49..cdf4d75bf3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Connect-Mailbox.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Connect-Mailbox.md
@@ -116,7 +116,7 @@ Connect-Mailbox [-Identity] <StoreMailboxIdParameter> [-Database] <DatabaseIdPar
 ## DESCRIPTION
 If you link a mailbox to an existing user account, that user account has full access to the mailbox and all mail in the mailbox.
 
-If you use the User parameter to specify the user account, make sure you specify the correct account. If you don't use the User parameter, we recommend that you use the ValidateOnly switch to verify which user account the mailbox will try to connect to.
+If you use the User parameter to specify the user account, make sure you specify the correct account. If you don't use the User parameter, we recommend the ValidateOnly switch to verify which user account the mailbox tries to connect to.
 
 There is no Disconnect-Mailbox cmdlet. You can use the Disable-Mailbox or Remove-Mailbox cmdlets to effectively disconnect mailboxes from user accounts.
 
@@ -132,7 +132,7 @@ Use the Remove-Mailbox cmdlet to:
 - Keep the mailbox in the disabled state before it's permanently deleted, subject to the deleted mailbox retention period (except if you use the Permanent or StoreMailboxIdentity parameters, which immediately deletes the mailbox from the database).
 - Remove the user account.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -323,7 +323,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-The ValidateOnly switch tells the cmdlet to evaluate the conditions and requirements necessary to perform the operation and then reports whether the operation will succeed or fail. You don't need to specify a value with this switch.
+The ValidateOnly switch specifies whether to evaluate the potential success or failure of the command without making changes. You don't need to specify a value with this switch.
 
 No changes are made when you use this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Delete-QuarantineMessage.md b/exchange/exchange-ps/ExchangePowerShell/Delete-QuarantineMessage.md
index 4fb377a2a5..c071bd6c30 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Delete-QuarantineMessage.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Delete-QuarantineMessage.md
@@ -45,7 +45,7 @@ Delete-QuarantineMessage -Identity <QuarantineMessageIdentity>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-ATPProtectionPolicyRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-ATPProtectionPolicyRule.md
index 8352e7a409..cec4891367 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-ATPProtectionPolicyRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-ATPProtectionPolicyRule.md
@@ -33,7 +33,7 @@ The State property in rules that are associated with preset security policies in
 
 For more information about preset security policies in PowerShell, see [Preset security policies in Exchange Online PowerShell](https://learn.microsoft.com/defender-office-365/preset-security-policies#preset-security-policies-in-exchange-online-powershell).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-AddressListPaging.md b/exchange/exchange-ps/ExchangePowerShell/Disable-AddressListPaging.md
index eaf4c603a6..1de3a4b7fd 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-AddressListPaging.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-AddressListPaging.md
@@ -29,7 +29,7 @@ Disable-AddressListPaging [-Confirm]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-AntiPhishRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-AntiPhishRule.md
index e736bcd2b3..7660a78413 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-AntiPhishRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-AntiPhishRule.md
@@ -29,7 +29,7 @@ Disable-AntiPhishRule [-Identity] <RuleIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-App.md b/exchange/exchange-ps/ExchangePowerShell/Disable-App.md
index b2ff60ea45..ce690bd262 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-App.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-App.md
@@ -13,7 +13,7 @@ title: Disable-App
 # Disable-App
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Disable-App cmdlet to disable (turn off) a specific app for a specific user.
 
@@ -31,11 +31,11 @@ Disable-App [-Identity] <AppIdParameter>
 ```
 
 ## DESCRIPTION
-The Disable-App cmdlet requires that the specified app has already been installed (for example, that the app has been installed with the New-App cmdlet, or that it's a default app for Microsoft Outlook).
+The Disable-App cmdlet requires that the specified app has already been installed (for example, that the app is installed with the New-App cmdlet, or that it's a default app for Microsoft Outlook).
 
 For more information, see [Manage user access to add-ins for Outlook in Exchange Server](https://learn.microsoft.com/Exchange/manage-user-access-to-add-ins-exchange-2013-help) and [Manage deployment of add-ins in the Microsoft 365 admin center](https://learn.microsoft.com/office365/admin/manage/manage-deployment-of-add-ins).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-CmdletExtensionAgent.md b/exchange/exchange-ps/ExchangePowerShell/Disable-CmdletExtensionAgent.md
index 950d45cb73..a61981d05a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-CmdletExtensionAgent.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-CmdletExtensionAgent.md
@@ -34,7 +34,7 @@ Cmdlet extension agents are used by Exchange cmdlets in Exchange Server 2010 and
 
 When you disable a cmdlet extension agent, the agent is disabled for the entire organization. When an agent is disabled, it's not made available to cmdlets. Cmdlets can no longer use the agent to perform additional operations.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-DistributionGroup.md b/exchange/exchange-ps/ExchangePowerShell/Disable-DistributionGroup.md
index 1bf77a6557..99d3dee368 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-DistributionGroup.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-DistributionGroup.md
@@ -33,7 +33,7 @@ Disable-DistributionGroup [-Identity] <DistributionGroupIdParameter>
 ## DESCRIPTION
 The Disable-DistributionGroup cmdlet mail-disables existing mail-enabled security groups and distribution groups by removing the email attributes that are required by Exchange. Mail-disabled groups are invisible to the \*-DistributionGroup cmdlets (with the exception of Enable-DistributionGroup). All groups (mail-enabled or not) are visible to the Get-Group and Set-Group cmdlets.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-DnssecForVerifiedDomain.md b/exchange/exchange-ps/ExchangePowerShell/Disable-DnssecForVerifiedDomain.md
index d6bba5f7e1..920747bf5b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-DnssecForVerifiedDomain.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-DnssecForVerifiedDomain.md
@@ -31,7 +31,7 @@ Disable-DnssecForVerifiedDomain [-DomainName] <String>
 ## DESCRIPTION
 For more information about debugging, enabling, and disabling SMTP DANE with DNSSEC, see [How SMTP DANE works](https://learn.microsoft.com/purview/how-smtp-dane-works).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-EOPProtectionPolicyRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-EOPProtectionPolicyRule.md
index df608cff7f..2dd8ae99b5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-EOPProtectionPolicyRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-EOPProtectionPolicyRule.md
@@ -33,7 +33,7 @@ The State property in rules that are associated with preset security policies in
 
 For more information about preset security policies in PowerShell, see [Preset security policies in Exchange Online PowerShell](https://learn.microsoft.com/defender-office-365/preset-security-policies#preset-security-policies-in-exchange-online-powershell).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-HostedContentFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-HostedContentFilterRule.md
index 7630a48749..78dae763c9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-HostedContentFilterRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-HostedContentFilterRule.md
@@ -29,7 +29,7 @@ Disable-HostedContentFilterRule [-Identity] <RuleIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-HostedOutboundSpamFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-HostedOutboundSpamFilterRule.md
index 9a3ea41209..4ebd303216 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-HostedOutboundSpamFilterRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-HostedOutboundSpamFilterRule.md
@@ -29,7 +29,7 @@ Disable-HostedOutboundSpamFilterRule [-Identity] <RuleIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-IPv6ForAcceptedDomain.md b/exchange/exchange-ps/ExchangePowerShell/Disable-IPv6ForAcceptedDomain.md
index 3e0dadb098..bb1c87a9ed 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-IPv6ForAcceptedDomain.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-IPv6ForAcceptedDomain.md
@@ -32,7 +32,7 @@ Use the Get-AcceptedDomain cmdlet to return accepted domains in the Exchange Onl
 
 If IPv6 is enabled for an accepted domain in Exchange Online, IPv4 and IPv6 addresses are returned in DNS queries for mail flow records of the domain. If IPv6 is disabled, only IPv4 addresses are returned in DNS queries for mail flow records of the domain.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-InboxRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-InboxRule.md
index 63aca8800c..fc46a1d3e0 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-InboxRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-InboxRule.md
@@ -13,7 +13,7 @@ title: Disable-InboxRule
 # Disable-InboxRule
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Disable-InboxRule cmdlet to disable existing Inbox rules in mailboxes.
 
@@ -35,7 +35,7 @@ Disable-InboxRule [-Identity] <InboxRuleIdParameter>
 ## DESCRIPTION
 When you create, modify, remove, enable, or disable an Inbox rule in Exchange PowerShell, any client-side rules created by Microsoft Outlook are removed.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -140,7 +140,7 @@ The Force switch hides warning or confirmation messages. You don't need to speci
 
 You can use this switch to run tasks programmatically where prompting for administrative input is inappropriate.
 
-A confirmation prompt warns you if the mailbox contains rules that were created by Outlook, because any client-side rules will be removed by the actions of this cmdlet.
+A confirmation prompt warns you if the mailbox contains rules that were created by Outlook, because any client-side rules are removed by the actions of this cmdlet.
 
 ```yaml
 Type: SwitchParameter
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-JournalArchiving.md b/exchange/exchange-ps/ExchangePowerShell/Disable-JournalArchiving.md
index cc3806b3c5..6fed3d1538 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-JournalArchiving.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-JournalArchiving.md
@@ -36,7 +36,7 @@ The Disable-JournalArchiving cmdlet removes the mail user and converts the journ
 
 In hybrid organizations that use DirSync, this cmdlet doesn't remove the mail user. Removal of the mail user is handled by DirSync.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-JournalRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-JournalRule.md
index d3a8397ba1..b15185faa4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-JournalRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-JournalRule.md
@@ -13,7 +13,7 @@ title: Disable-JournalRule
 # Disable-JournalRule
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Disable-JournalRule cmdlet to disable a journal rule on a Mailbox server.
 
@@ -32,7 +32,7 @@ Disable-JournalRule -Identity <RuleIdParameter>
 ## DESCRIPTION
 You can enable or disable specific journal rules in your organization at any time using the Disable-JournalRule and Enable-JournalRule cmdlets.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-MailContact.md b/exchange/exchange-ps/ExchangePowerShell/Disable-MailContact.md
index 3f7988f388..451238f746 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-MailContact.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-MailContact.md
@@ -33,7 +33,7 @@ Disable-MailContact [-Identity] <MailContactIdParameter>
 ## DESCRIPTION
 The Disable-MailContact cmdlet mail-disables existing mail contacts by removing the email attributes that are required by Exchange. Mail-disabled contacts are invisible to the \*-MailContact cmdlets (with the exception of Enable-MailContact). All contacts (mail-enabled or not) are visible to the Get-Contact and Set-Contact cmdlets.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-MailPublicFolder.md b/exchange/exchange-ps/ExchangePowerShell/Disable-MailPublicFolder.md
index e3f87cb3ae..fe5bfbe28b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-MailPublicFolder.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-MailPublicFolder.md
@@ -13,7 +13,7 @@ title: Disable-MailPublicFolder
 # Disable-MailPublicFolder
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Disable-MailPublicFolder cmdlet to mail-disable a public folder.
 
@@ -31,7 +31,7 @@ Disable-MailPublicFolder [-Identity] <PublicFolderIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-MailUser.md b/exchange/exchange-ps/ExchangePowerShell/Disable-MailUser.md
index c2a47e5857..7b7effd7ff 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-MailUser.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-MailUser.md
@@ -34,7 +34,7 @@ Disable-MailUser [-Identity] <MailUserIdParameter>
 ## DESCRIPTION
 The Disable-MailUser cmdlet mail-disables existing mail users by removing the email attributes that are required by Exchange. Mail-disabled users are invisible to the \*-MailUser cmdlets (with the exception of Enable-MailUser). All users (mail-enabled or not) are visible to the Get-User and Set-User cmdlets.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-Mailbox.md b/exchange/exchange-ps/ExchangePowerShell/Disable-Mailbox.md
index 57ce870b95..4edb38bb6f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-Mailbox.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-Mailbox.md
@@ -13,7 +13,7 @@ title: Disable-Mailbox
 # Disable-Mailbox
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Disable-Mailbox cmdlet to disable the mailbox of existing users who already have mailboxes. For this cmdlet, a user could also be a public folder mailbox or an InetOrgPerson object. The user account that's associated with the mailbox remains, but it's no longer associated with a mailbox.
 
@@ -77,9 +77,9 @@ The Disable-Mailbox cmdlet removes the mailbox's Exchange attributes from Active
 
 The Disable-Mailbox cmdlet also performs the clean-up task on the individual mailbox, so the mailbox is disconnected immediately after this task completes.
 
-Under normal circumstances, a mailbox is marked as disconnected immediately after the Disable-Mailbox or Remove-Mailbox command completes. However, if the mailbox was disabled or removed while the Exchange Information Store service was stopped, or if it was disabled or removed by an external means other than Exchange management interfaces, the status of the mailbox object in the Exchange mailbox database won't be marked as disconnected.
+Under normal circumstances, a mailbox is marked as disconnected immediately after the Disable-Mailbox or Remove-Mailbox command completes. However, if the mailbox was disabled or removed while the Exchange Information Store service was stopped, or if it was disabled or removed by an external means other than Exchange management interfaces, the status of the mailbox object in the Exchange mailbox database isn't marked as disconnected.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -313,7 +313,7 @@ The PermanentlyDisable switch specifies whether to permanently disable the mailb
 **Notes**:
 
 - You can only use this switch on user mailboxes that aren't licensed and aren't on hold.
-- When the Exchange Online license is removed from a mailbox without following other deprovisioning steps, this may leave the mailbox in a hard-deleted state. In this case, this parameter is not useful. You can use it, for example, in hybrid Exchange environments.
+- When the Exchange Online license is removed from a mailbox without following other deprovisioning steps, this might leave the mailbox in a hard-deleted state. In this case, this parameter is not useful. You can use it, for example, in hybrid Exchange environments.
 
 ```yaml
 Type: SwitchParameter
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-MailboxQuarantine.md b/exchange/exchange-ps/ExchangePowerShell/Disable-MailboxQuarantine.md
index 1bb4f37eb4..7082e77db1 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-MailboxQuarantine.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-MailboxQuarantine.md
@@ -68,9 +68,9 @@ Disable-MailboxQuarantine -Server <ServerIdParameter>
 ```
 
 ## DESCRIPTION
-Mailboxes are quarantined when they affect the availability of the mailbox database. Typically a software fix from Microsoft is required before releasing a mailbox from quarantine. If a fix isn't deployed before releasing the mailbox, the quarantine on the mailbox will be re-enabled if the condition recurs. The default quarantine duration is 24 hours.
+Mailboxes are quarantined when they affect the availability of the mailbox database. Typically a software fix from Microsoft is required before releasing a mailbox from quarantine. If a fix isn't deployed before releasing the mailbox, the quarantine on the mailbox is re-enabled if the condition recurs. The default quarantine duration is 24 hours.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-MalwareFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-MalwareFilterRule.md
index 44824fbe35..8127d10f40 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-MalwareFilterRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-MalwareFilterRule.md
@@ -13,7 +13,7 @@ title: Disable-MalwareFilterRule
 # Disable-MalwareFilterRule
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Disable-MalwareFilterRule cmdlet to disable malware filter rules in your organization.
 
@@ -30,7 +30,7 @@ Disable-MalwareFilterRule [-Identity] <RuleIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-MetaCacheDatabase.md b/exchange/exchange-ps/ExchangePowerShell/Disable-MetaCacheDatabase.md
index 3d4485454e..f6ff4cfdb9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-MetaCacheDatabase.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-MetaCacheDatabase.md
@@ -29,7 +29,7 @@ Disable-MetaCacheDatabase -Server <String[]>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-OutlookAnywhere.md b/exchange/exchange-ps/ExchangePowerShell/Disable-OutlookAnywhere.md
index 8cfbf56343..f34bfa0d4a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-OutlookAnywhere.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-OutlookAnywhere.md
@@ -44,9 +44,9 @@ Enabling Outlook Anywhere on the Client Access server prevents the server from a
 
 When you run this cmdlet, it can take as long as an hour for the settings to become effective, depending on how long it takes for Active Directory to replicate.
 
-After the Client Access server is disabled for Outlook Anywhere, you may want to remove the RPC over HTTP proxy Windows networking component.
+After the Client Access server is disabled for Outlook Anywhere, you might want to remove the RPC over HTTP proxy Windows networking component.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-OutlookProtectionRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-OutlookProtectionRule.md
index 17ffbc57db..1b77ff5b57 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-OutlookProtectionRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-OutlookProtectionRule.md
@@ -15,7 +15,7 @@ title: Disable-OutlookProtectionRule
 ## SYNOPSIS
 **Note**: This cmdlet is no longer supported in the cloud-based service.
 
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Disable-OutlookProtectionRule cmdlet to disable an existing Microsoft Outlook protection rule.
 
@@ -36,7 +36,7 @@ Outlook protection rules are administrator-created rules applied before a user s
 
 For more information, see [Outlook protection rules](https://learn.microsoft.com/exchange/outlook-protection-rules-exchange-2013-help).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-PushNotificationProxy.md b/exchange/exchange-ps/ExchangePowerShell/Disable-PushNotificationProxy.md
index 069b955360..355b7fb189 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-PushNotificationProxy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-PushNotificationProxy.md
@@ -30,7 +30,7 @@ Disable-PushNotificationProxy [-Confirm]
 ## DESCRIPTION
 The push notification proxy relays event notifications (for example, new email or calendar updates) for on-premises mailboxes through Microsoft 365 to Outlook on the web for devices on the user's device.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-RemoteMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Disable-RemoteMailbox.md
index 3549b91ef4..b6ec895fe5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-RemoteMailbox.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-RemoteMailbox.md
@@ -35,7 +35,7 @@ Disable-RemoteMailbox [-Identity] <RemoteMailboxIdParameter>
 ## DESCRIPTION
 Use the Disable-RemoteMailbox cmdlet to perform the following actions:
 
-- Remove a cloud-based mailbox but keep the associated on-premises user account. To do this, you first need to remove the Exchange Online license for the mailbox. Otherwise, the mailbox won't be removed. The on-premises mail user is automatically converted to a regular user object. You can mail-enable the on-premises user object using the Enable-MailUser cmdlet.
+- Remove a cloud-based mailbox but keep the associated on-premises user account. To do this, you first need to remove the Exchange Online license for the mailbox. Otherwise, the mailbox isn't removed. The on-premises mail user is automatically converted to a regular user object. You can mail-enable the on-premises user object using the Enable-MailUser cmdlet.
 - Disconnect a cloud-based archive mailbox from a cloud-based mailbox. The cloud-based mailbox and the associated on-premises mail user are preserved.
 
 If you want to remove both the cloud-based mailbox and the associated on-premises mail user, use the Remove-RemoteMailbox cmdlet.
@@ -44,10 +44,10 @@ Directory synchronization must be configured correctly for a mailbox to be remov
 
 **Notes**:
 
-- If you are deprovisioning a cloud mailbox and its associated online archive, you must first disable the online archive with the command `Disable-RemoteMailbox <User> -Archive` and then perform a directory synchronization prior to disabling the remote mailbox. Attempting to disable both the online archive and cloud mailbox without a sync between them may result in an ArchiveGuid mismatch and validation error.
+- If you are deprovisioning a cloud mailbox and its associated online archive, you must first disable the online archive with the command `Disable-RemoteMailbox <User> -Archive` and then perform a directory synchronization prior to disabling the remote mailbox. Attempting to disable both the online archive and cloud mailbox without a sync between them might result in an ArchiveGuid mismatch and validation error.
 - Due to the current service architecture, you need to convert shared mailboxes to user mailboxes prior to running the Disable-RemoteMailbox cmdlet.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -56,14 +56,14 @@ You need to be assigned permissions before you can run this cmdlet. Although thi
 Disable-RemoteMailbox "Kim Akers"
 ```
 
-This example removes the cloud-based mailbox that's associated with the on-premises mail user named Kim Akers. The mail user is automatically converted to a regular user. This example assumes that you've already removed the Exchange Online license for the mailbox, and that directory synchronization has been configured.
+This example removes the cloud-based mailbox that's associated with the on-premises mail user named Kim Akers. The mail user is automatically converted to a regular user. This example assumes that you've already removed the Exchange Online license for the mailbox, and that directory synchronization is configured.
 
 ### Example 2
 ```powershell
 Disable-RemoteMailbox "David Strome" -Archive
 ```
 
-This example removes the cloud-based archive mailbox but keeps the cloud-based mailbox that's associated with the on-premises mail user named David Strome. This example assumes directory synchronization has been configured.
+This example removes the cloud-based archive mailbox but keeps the cloud-based mailbox that's associated with the on-premises mail user named David Strome. This example assumes directory synchronization is configured.
 
 ## PARAMETERS
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-ReportSubmissionRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-ReportSubmissionRule.md
index 1fbb643e5a..a55a45da61 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-ReportSubmissionRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-ReportSubmissionRule.md
@@ -29,7 +29,7 @@ Disable-ReportSubmissionRule [-Identity] <RuleIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-SafeAttachmentRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-SafeAttachmentRule.md
index 953b770117..10fba35caf 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-SafeAttachmentRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-SafeAttachmentRule.md
@@ -31,7 +31,7 @@ Disable-SafeAttachmentRule [-Identity] <RuleIdParameter>
 ## DESCRIPTION
 Safe Attachments is a feature in Microsoft Defender for Office 365 that opens email attachments in a special hypervisor environment to detect malicious activity. For more information, see [Safe Attachments in Defender for Office 365](https://learn.microsoft.com/defender-office-365/safe-attachments-about).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-SafeLinksRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-SafeLinksRule.md
index 3327a72700..e9ce882e5f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-SafeLinksRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-SafeLinksRule.md
@@ -31,7 +31,7 @@ Disable-SafeLinksRule [-Identity] <RuleIdParameter>
 ## DESCRIPTION
 Safe Links is a feature in Microsoft Defender for Office 365 that checks links in email messages to see if they lead to malicious web sites. When a user clicks a link in a message, the URL is temporarily rewritten and checked against a list of known, malicious web sites. Safe Links includes the URL trace reporting feature to help determine who has clicked through to a malicious web site.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-ServiceEmailChannel.md b/exchange/exchange-ps/ExchangePowerShell/Disable-ServiceEmailChannel.md
index 4e82617c25..3b3cacc2ab 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-ServiceEmailChannel.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-ServiceEmailChannel.md
@@ -32,7 +32,7 @@ Disable-ServiceEmailChannel [-Identity] <MailboxIdParameter>
 ## DESCRIPTION
 The Disable-ServiceEmailChannel cmdlet deletes the receive folder in the user's mailbox under the root folder.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-SmtpDaneInbound.md b/exchange/exchange-ps/ExchangePowerShell/Disable-SmtpDaneInbound.md
index 658111797e..3ee2297558 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-SmtpDaneInbound.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-SmtpDaneInbound.md
@@ -31,7 +31,7 @@ Disable-SmtpDaneInbound [-DomainName] <String>
 ## DESCRIPTION
 For more information about debugging, enabling, and disabling SMTP DANE with DNSSEC, see [How SMTP DANE works](https://learn.microsoft.com/purview/how-smtp-dane-works).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-SweepRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-SweepRule.md
index 95de0ed658..ba335e644f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-SweepRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-SweepRule.md
@@ -13,7 +13,7 @@ title: Disable-SweepRule
 # Disable-SweepRule
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Disable-SweepRule cmdlet to disable Sweep rules in mailboxes.
 
@@ -31,7 +31,7 @@ Disable-SweepRule [-Identity] <SweepRuleIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-TransportAgent.md b/exchange/exchange-ps/ExchangePowerShell/Disable-TransportAgent.md
index dde2c3a4c3..a70c5a9d46 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-TransportAgent.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-TransportAgent.md
@@ -31,7 +31,7 @@ Disable-TransportAgent [-Identity] <TransportAgentObjectId>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-TransportRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-TransportRule.md
index 1921db70e4..2486bc58e6 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-TransportRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-TransportRule.md
@@ -13,7 +13,7 @@ title: Disable-TransportRule
 # Disable-TransportRule
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Disable-TransportRule cmdlet to disable transport rules (mail flow rules) in your organization.
 
@@ -32,7 +32,7 @@ Disable-TransportRule [-Identity] <RuleIdParameter>
 ## DESCRIPTION
 To enable rules that are disabled, use the Enable-TransportRule cmdlet.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-UMAutoAttendant.md b/exchange/exchange-ps/ExchangePowerShell/Disable-UMAutoAttendant.md
index 1ef66ad50b..6d848275c1 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-UMAutoAttendant.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-UMAutoAttendant.md
@@ -32,9 +32,9 @@ Disable-UMAutoAttendant [-Identity] <UMAutoAttendantIdParameter>
 ## DESCRIPTION
 The Disable-UMAutoAttendant cmdlet disables an existing UM auto attendant that's currently enabled. The Disable-UMAutoAttendant cmdlet disables the UM auto attendant by modifying its status variable. The Disable-UMAutoAttendant cmdlet can't disable the UM auto attendant if it's linked or associated to the UM hunt group associated with the default UM dial plan.
 
-After this task is completed, the UM auto attendant is disabled and won't accept incoming calls.
+After this task is completed, the UM auto attendant is disabled and doesn't accept incoming calls.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-UMCallAnsweringRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-UMCallAnsweringRule.md
index 28f9e0bd91..0d7ed908bd 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-UMCallAnsweringRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-UMCallAnsweringRule.md
@@ -15,7 +15,7 @@ title: Disable-UMCallAnsweringRule
 ## SYNOPSIS
 This cmdlet is available only in on-premises Exchange.
 
-Use the Disable-UMCallAnsweringRule cmdlet to disable a call answering rule that has been created within a UM-enabled mailbox.
+Use the Disable-UMCallAnsweringRule cmdlet to disable a call answering rule that is created within a UM-enabled mailbox.
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
@@ -35,7 +35,7 @@ The Disable-UMCallAnsweringRule cmdlet disables the call answering rule by modif
 
 When the call answering rule is created, you should disable the call answering rule when you're setting up conditions and actions. This prevents the call answering rule from being processed when an incoming call is received until you've correctly configured the call answering rule. After this task is completed, the cmdlet sets the parameters and the values specified.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-UMIPGateway.md b/exchange/exchange-ps/ExchangePowerShell/Disable-UMIPGateway.md
index a715ac322d..db54c5c88d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-UMIPGateway.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-UMIPGateway.md
@@ -33,7 +33,7 @@ Disable-UMIPGateway [-Identity] <UMIPGatewayIdParameter>
 ## DESCRIPTION
 The status variable for a UM IP gateway can be used to enable or disable call answering destined for the IP gateway. The Disable-UMIPGateway cmdlet disables a UM IP gateway in Active Directory by modifying its status variable. After this task is completed, the UM IP gateway no longer answers incoming calls or makes outgoing calls.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-UMMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Disable-UMMailbox.md
index ea3727bee6..ae4ee00bda 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-UMMailbox.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-UMMailbox.md
@@ -34,7 +34,7 @@ Disable-UMMailbox [-Identity] <MailboxIdParameter>
 ## DESCRIPTION
 After the mailbox is disabled for Unified Messaging, the user can no longer use the UM features that are included in Microsoft Exchange and the Microsoft Exchange Unified Messaging service no longer handle calls for the associated extension number. The mailbox continues to function normally for all other operations that are unrelated to Unified Messaging.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -144,7 +144,7 @@ Accept wildcard characters: False
 
 The KeepProperties parameter specifies whether to keep or remove the UM properties for the mailbox. Valid values are:
 
-- $true: The UM properties are retained on the mailbox. This is the default value.
+- $true: The UM properties are retained on the mailbox. This value is the default.
 - $false: The UM properties are removed from the mailbox.
 
 ```yaml
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-UMServer.md b/exchange/exchange-ps/ExchangePowerShell/Disable-UMServer.md
index a4713a795f..4136f0b40f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-UMServer.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-UMServer.md
@@ -31,7 +31,7 @@ Disable-UMServer [-Identity] <UMServerIdParameter>
 ```
 
 ## DESCRIPTION
-The Disable-UMServer cmdlet sets the status of a Unified Messaging server. A UM server has a logical status variable controlled using the enable and disable cmdlets. A UM server won't process any new calls unless it's in the enabled state. With this status variable, you can start or stop call processing on a UM server so the UM server can be brought online or taken offline in a controlled way.
+The Disable-UMServer cmdlet sets the status of a Unified Messaging server. A UM server has a logical status variable controlled using the enable and disable cmdlets. A UM server doesn't process any new calls unless it's in the enabled state. With this status variable, you can start or stop call processing on a UM server so the UM server can be brought online or taken offline in a controlled way.
 
 After this task is completed, the UM server can no longer:
 
@@ -40,7 +40,7 @@ After this task is completed, the UM server can no longer:
 - Be used to manage UM-enabled mailboxes
 - Be queried when a diagnostic task is used
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-UMService.md b/exchange/exchange-ps/ExchangePowerShell/Disable-UMService.md
index f712294833..1dff826b33 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-UMService.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-UMService.md
@@ -33,7 +33,7 @@ Disable-UMService [-Identity] <UMServerIdParameter>
 ```
 
 ## DESCRIPTION
-The Disable-UMService cmdlet sets the status of a UM server. A UM server has a logical status variable controlled using the enable and disable cmdlets. A UM server won't process any new calls unless it's in the enabled state. With this status variable, you can start or stop call processing on a UM server so the UM server can be brought online or taken offline in a controlled way.
+The Disable-UMService cmdlet sets the status of a UM server. A UM server has a logical status variable controlled using the enable and disable cmdlets. A UM server doesn't process any new calls unless it's in the enabled state. With this status variable, you can start or stop call processing on a UM server so the UM server can be brought online or taken offline in a controlled way.
 
 After this task is completed, the UM server can no longer:
 
@@ -42,7 +42,7 @@ After this task is completed, the UM server can no longer:
 - Be used to manage UM-enabled mailboxes.
 - Be queried when a diagnostic task is used.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Dismount-Database.md b/exchange/exchange-ps/ExchangePowerShell/Dismount-Database.md
index f71b315592..2ad03daf97 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Dismount-Database.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Dismount-Database.md
@@ -30,7 +30,7 @@ Dismount-Database [-Identity] <DatabaseIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Dump-ProvisioningCache.md b/exchange/exchange-ps/ExchangePowerShell/Dump-ProvisioningCache.md
index caf85044ed..f417804b7e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Dump-ProvisioningCache.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Dump-ProvisioningCache.md
@@ -43,11 +43,11 @@ Dump-ProvisioningCache [-Server] <Fqdn> -Application <String>
 ```
 
 ## DESCRIPTION
-The Dump-ProvisioningCache cmdlet is for diagnostic purposes only and is rarely used. Exchange administrators or Microsoft support personnel may need to run this cmdlet to troubleshoot problems resulting from incorrect links or properties stamped on newly provisioned recipients, which can be caused by stale data in the provisioning cache.
+The Dump-ProvisioningCache cmdlet is for diagnostic purposes only and is rarely used. Exchange administrators or Microsoft support personnel might need to run this cmdlet to troubleshoot problems resulting from incorrect links or properties stamped on newly provisioned recipients, which can be caused by stale data in the provisioning cache.
 
 The Dump-ProvisioningCache cmdlet displays a list of the Windows PowerShell provisioning cache keys. Use the value of these cache keys with the Reset-ProvisioningCache cmdlet to reset provisioning cache data.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -184,7 +184,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-The Organizations parameter specifies the organizations that the provisioning cache will be reset. This parameter is used in multi-tenant deployments.
+The Organizations parameter specifies the organizations where the provisioning cache is reset. This parameter is used in multi-tenant deployments.
 
 ```yaml
 Type: MultiValuedProperty
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-ATPProtectionPolicyRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-ATPProtectionPolicyRule.md
index c62fb63b78..543c960817 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-ATPProtectionPolicyRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-ATPProtectionPolicyRule.md
@@ -33,7 +33,7 @@ The State property in rules that are associated with preset security policies in
 
 For more information about preset security policies in PowerShell, see [Preset security policies in Exchange Online PowerShell](https://learn.microsoft.com/defender-office-365/preset-security-policies#preset-security-policies-in-exchange-online-powershell).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-AddressListPaging.md b/exchange/exchange-ps/ExchangePowerShell/Enable-AddressListPaging.md
index 7cf35a1dd4..78747343ca 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-AddressListPaging.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-AddressListPaging.md
@@ -31,7 +31,7 @@ Enable-AddressListPaging [-Confirm]
 ## DESCRIPTION
 The Enable-AddressListPaging cmdlet creates the Address List container in Active Directory. Recipient cmdlets, such as Get-Recipient, use the information written to the container to quickly retrieve recipient data.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-AntiPhishRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-AntiPhishRule.md
index 418b53848b..3bb397ee11 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-AntiPhishRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-AntiPhishRule.md
@@ -29,7 +29,7 @@ Enable-AntiPhishRule [-Identity] <RuleIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-App.md b/exchange/exchange-ps/ExchangePowerShell/Enable-App.md
index fe719c307f..6e033b80c9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-App.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-App.md
@@ -13,7 +13,7 @@ title: Enable-App
 # Enable-App
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Enable-App cmdlet to enable (turn on) a specific app for a specific user.
 
@@ -31,11 +31,11 @@ Enable-App [-Identity] <AppIdParameter>
 ```
 
 ## DESCRIPTION
-The Enable-App cmdlet requires that the specified app has already been installed (for example, that it has been installed with the New-App cmdlet, or that it's a default app for Microsoft Outlook).
+The Enable-App cmdlet requires that the specified app has already been installed (for example, that it is installed with the New-App cmdlet, or that it's a default app for Microsoft Outlook).
 
 For more information, see [Manage user access to add-ins for Outlook in Exchange Server](https://learn.microsoft.com/Exchange/manage-user-access-to-add-ins-exchange-2013-help) and [Manage deployment of add-ins in the Microsoft 365 admin center](https://learn.microsoft.com/office365/admin/manage/manage-deployment-of-add-ins).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-CmdletExtensionAgent.md b/exchange/exchange-ps/ExchangePowerShell/Enable-CmdletExtensionAgent.md
index b954efdd4a..bd2048d7e4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-CmdletExtensionAgent.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-CmdletExtensionAgent.md
@@ -34,9 +34,9 @@ Cmdlet extension agents are used by Exchange cmdlets in Exchange Server 2010 and
 
 When you enable a cmdlet extension agent, the agent is run on every Exchange server in the organization. When an agent is enabled, it's made available to cmdlets that can then use the agent to perform additional operations.
 
-Before you enable agents, be sure that you're aware of how the agent works and what impact the agent will have on your organization.
+Before you enable agents, be sure that you're aware of how the agent works and what effect the agent can have on your organization.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -45,7 +45,7 @@ You need to be assigned permissions before you can run this cmdlet. Although thi
 Enable-CmdletExtensionAgent "Scripting Agent"
 ```
 
-This example enables the cmdlet extension agent named Scripting Agent. Before you enable the Scripting Agent, you need to configure the %ExchangeInstallPath%Bin\\CmdletExtensionAgents\\ScriptingAgentConfig.xml.sample file and rename it to ScriptingAgentConfig.xml on all the Exchange servers in your organization. If you don't, all non-Get cmdlets will fail.
+This example enables the cmdlet extension agent named Scripting Agent. Before you enable the Scripting Agent, you need to configure the `%ExchangeInstallPath%Bin\CmdletExtensionAgents\ScriptingAgentConfig.xml.sample` file and rename it to `ScriptingAgentConfig.xml` on all the Exchange servers in your organization. If you don't configure the file, all non-Get cmdlets will fail.
 
 ## PARAMETERS
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-ComplianceTagStorage.md b/exchange/exchange-ps/ExchangePowerShell/Enable-ComplianceTagStorage.md
index a28f12032f..7eaaed4768 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-ComplianceTagStorage.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-ComplianceTagStorage.md
@@ -30,7 +30,7 @@ Enable-ComplianceTagStorage
 ```
 
 ## DESCRIPTION
-You can check the status by running the following command: `Get-ComplianceTagStorage | Format-List Enabled,DistributionStatus`. The value True for the Enabled property and the value Success for the DistributionStatus property indicates the Enable-ComplianceTagStorage cmdlet has already been run in the organization, and you don't need to run it again. If you run the cmdlet unnecessarily, you'll get a warning, and the DistributionStatus property changes to the value Pending for a few minutes before returning to the value Success.
+You can check the status by running the following command: `Get-ComplianceTagStorage | Format-List Enabled,DistributionStatus`. The value True for the Enabled property and the value Success for the DistributionStatus property indicates the Enable-ComplianceTagStorage cmdlet has already been run in the organization, and you don't need to run it again. If you run the cmdlet unnecessarily, you get a warning, and the DistributionStatus property changes to the value Pending for a few minutes before returning to the value Success.
 
 To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions).
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-DistributionGroup.md b/exchange/exchange-ps/ExchangePowerShell/Enable-DistributionGroup.md
index 2b0bca1bab..8ef9efc43b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-DistributionGroup.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-DistributionGroup.md
@@ -35,7 +35,7 @@ Enable-DistributionGroup [-Identity] <GroupIdParameter>
 ## DESCRIPTION
 The Enable-DistributionGroup cmdlet mail-enables existing universal security groups and universal distribution groups by adding the email attributes that are required by Exchange. Mail-enabled security groups and distribution groups are visible to the other \*-DistributionGroup cmdlets and to the \*-DistributionGroupMember cmdlets.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 In Exchange Server, the [CommonParameters](https://go.microsoft.com/fwlink/p/?LinkID=113216) InformationVariable and InformationAction don't work.
 
@@ -172,7 +172,7 @@ Accept wildcard characters: False
 
 The PrimarySmtpAddress parameter specifies the primary return email address that's used for the recipient.
 
-By default, the primary SMTP address is generated based on the default email address policy and the value of the Alias parameter or the Name property. If you use the PrimarySmtpAddress parameter to specify the primary email address, the EmailAddressPolicyEnabled property is set to the value False, which means the email addresses of the group won't be automatically updated by email address policies.
+By default, the primary SMTP address is generated based on the default email address policy and the value of the Alias parameter or the Name property. If you use the PrimarySmtpAddress parameter to specify the primary email address, the EmailAddressPolicyEnabled property is set to the value False, which means the email addresses of the group aren't automatically updated by email address policies.
 
 ```yaml
 Type: SmtpAddress
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-DnssecForVerifiedDomain.md b/exchange/exchange-ps/ExchangePowerShell/Enable-DnssecForVerifiedDomain.md
index ba66a7d906..e081e366bc 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-DnssecForVerifiedDomain.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-DnssecForVerifiedDomain.md
@@ -33,7 +33,7 @@ The output of this cmdlet is an MX record value that you need to add to DNS for
 
 For more information about debugging, enabling, and disabling SMTP DANE with DNSSEC, see [How SMTP DANE works](https://learn.microsoft.com/purview/how-smtp-dane-works).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-EOPProtectionPolicyRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-EOPProtectionPolicyRule.md
index 55ab46f3c3..501ef067ae 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-EOPProtectionPolicyRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-EOPProtectionPolicyRule.md
@@ -33,7 +33,7 @@ The State property in rules that are associated with preset security policies in
 
 For more information about preset security policies in PowerShell, see [Preset security policies in Exchange Online PowerShell](https://learn.microsoft.com/defender-office-365/preset-security-policies#preset-security-policies-in-exchange-online-powershell).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-ExchangeCertificate.md b/exchange/exchange-ps/ExchangePowerShell/Enable-ExchangeCertificate.md
index 8ac543b37b..903cb865ed 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-ExchangeCertificate.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-ExchangeCertificate.md
@@ -57,7 +57,7 @@ There are many factors to consider when you configure certificates for Transport
 
 Secure Sockets Layer (SSL) is being replaced by Transport Layer Security (TLS) as the protocol that's used to encrypt data sent between computer systems. They're so closely related that the terms "SSL" and "TLS" (without versions) are often used interchangeably. Because of this similarity, references to "SSL" in Exchange topics, the Exchange admin center, and the Exchange Management Shell have often been used to encompass both the SSL and TLS protocols. Typically, "SSL" refers to the actual SSL protocol only when a version is also provided (for example, SSL 3.0). For more information, see [Exchange Server TLS configuration best practices](https://learn.microsoft.com/Exchange/exchange-tls-configuration).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -135,7 +135,7 @@ You can specify multiple values separated by commas.
 
 The values that you specify with this parameter are additive. When you enable a certificate for one or more services, any existing services remain in the Services property and you can't remove the existing services. Instead, configure another certificate for the services and then remove the certificate that you don't want to use.
 
-Different services have different certificate requirements. For example, some services may require a server name in the certificate's Subject Name or Subject Alternative Name fields, but other services may require an FQDN. Verify that the certificate supports the services that you want to configure.
+Different services have different certificate requirements. For example, some services might require a server name in the certificate's Subject Name or Subject Alternative Name fields, but other services might require an FQDN. Verify that the certificate supports the services that you want to configure.
 
 ```yaml
 Type: AllowedServices
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-HostedContentFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-HostedContentFilterRule.md
index 2e2746777a..981b7014dd 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-HostedContentFilterRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-HostedContentFilterRule.md
@@ -29,7 +29,7 @@ Enable-HostedContentFilterRule [-Identity] <RuleIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-HostedOutboundSpamFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-HostedOutboundSpamFilterRule.md
index ea9fd1312b..57e3320dfa 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-HostedOutboundSpamFilterRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-HostedOutboundSpamFilterRule.md
@@ -29,7 +29,7 @@ Enable-HostedOutboundSpamFilterRule [-Identity] <RuleIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-IPv6ForAcceptedDomain.md b/exchange/exchange-ps/ExchangePowerShell/Enable-IPv6ForAcceptedDomain.md
index 742bc1c935..3a69a851a2 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-IPv6ForAcceptedDomain.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-IPv6ForAcceptedDomain.md
@@ -32,7 +32,7 @@ Use the Get-AcceptedDomain cmdlet to return accepted domains in the Exchange Onl
 
 If IPv6 is enabled for an accepted domain in Exchange Online, IPv4 and IPv6 addresses are returned in DNS queries for mail flow records of the domain. If IPv6 is disabled, only IPv4 addresses are returned in DNS queries for mail flow records of the domain.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-InboxRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-InboxRule.md
index d1680d3778..59286152ae 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-InboxRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-InboxRule.md
@@ -13,7 +13,7 @@ title: Enable-InboxRule
 # Enable-InboxRule
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Enable-InboxRule cmdlet to enable an Inbox rule. Inbox rules are used to process messages in the Inbox based on conditions specified and take actions such as moving a message to a specified folder or deleting a message.
 
@@ -35,7 +35,7 @@ Enable-InboxRule [-Identity] <InboxRuleIdParameter>
 ## DESCRIPTION
 When you create, modify, remove, enable, or disable an Inbox rule in Exchange PowerShell, any client-side rules created by Microsoft Outlook are removed.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -138,7 +138,7 @@ The Force switch hides warning or confirmation messages. You don't need to speci
 
 You can use this switch to run tasks programmatically where prompting for administrative input is inappropriate.
 
-A confirmation prompt warns you if the mailbox contains rules that were created by Outlook, because any client-side rules will be removed by the actions of this cmdlet.
+A confirmation prompt warns you if the mailbox contains rules that were created by Outlook, because any client-side rules are removed by the actions of this cmdlet.
 
 ```yaml
 Type: SwitchParameter
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-JournalRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-JournalRule.md
index 9cfd07daa1..9f5e90cc65 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-JournalRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-JournalRule.md
@@ -13,7 +13,7 @@ title: Enable-JournalRule
 # Enable-JournalRule
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Enable-JournalRule cmdlet to enable an existing journal rule on a Mailbox server.
 
@@ -32,7 +32,7 @@ Enable-JournalRule [-Identity] <RuleIdParameter>
 ## DESCRIPTION
 You can enable or disable specific journal rules in your organization at any time using the Enable-JournalRule and Disable-JournalRule cmdlets. For more information, see [Journaling in Exchange Server](https://learn.microsoft.com/Exchange/policy-and-compliance/journaling/journaling).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-MailContact.md b/exchange/exchange-ps/ExchangePowerShell/Enable-MailContact.md
index 14a850f520..685fc2057a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-MailContact.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-MailContact.md
@@ -39,7 +39,7 @@ Enable-MailContact [-Identity] <ContactIdParameter> -ExternalEmailAddress <Proxy
 ## DESCRIPTION
 The Enable-MailContact cmdlet mail-enables existing contacts by adding the email attributes that are required by Exchange. Mail contacts are visible to the other \*-MailContact cmdlets.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -194,7 +194,7 @@ Accept wildcard characters: False
 
 The MacAttachmentFormat parameter specifies the Apple Macintosh operating system attachment format to use for messages sent to the mail contact or mail user. Valid values are:
 
-- BinHex (This is the default value)
+- BinHex (default value)
 - UuEncode
 - AppleSingle
 - AppleDouble
@@ -224,7 +224,7 @@ The MessageBodyFormat parameter specifies the message body format for messages s
 
 - Text
 - Html
-- TextAndHtml (This is the default value)
+- TextAndHtml (default value)
 
 The MessageFormat and MessageBodyFormat parameters are interdependent:
 
@@ -250,7 +250,7 @@ Accept wildcard characters: False
 The MessageFormat parameter specifies the message format for messages sent to the mail contact or mail user. Valid values are:
 
 - Text
-- Mime (This is the default value)
+- Mime (default value)
 
 The MessageFormat and MessageBodyFormat parameters are interdependent:
 
@@ -300,7 +300,7 @@ Accept wildcard characters: False
 The UsePreferMessageFormat specifies whether the message format settings configured for the mail user or mail contact override the global settings configured for the remote domain or configured by the message sender. Valid value are:
 
 - $true: Messages sent to the mail user or mail contact use the message format that's configured for the mail user or mail contact.
-- $false: Messages sent to the mail user or mail contact use the message format that's configured for the remote domain (the default remote domain or a specific remote domain) or configured by the message sender. This is the default value.
+- $false: Messages sent to the mail user or mail contact use the message format that's configured for the remote domain (the default remote domain or a specific remote domain) or configured by the message sender. This value is the default.
 
 ```yaml
 Type: Boolean
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-MailPublicFolder.md b/exchange/exchange-ps/ExchangePowerShell/Enable-MailPublicFolder.md
index 1c467a88f0..c1f8773382 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-MailPublicFolder.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-MailPublicFolder.md
@@ -13,7 +13,7 @@ title: Enable-MailPublicFolder
 # Enable-MailPublicFolder
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Enable-MailPublicFolder cmdlet to mail-enable public folders.
 
@@ -33,7 +33,7 @@ Enable-MailPublicFolder [-Identity] <PublicFolderIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-MailUser.md b/exchange/exchange-ps/ExchangePowerShell/Enable-MailUser.md
index 431b7b0427..d102ab1df9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-MailUser.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-MailUser.md
@@ -55,7 +55,7 @@ The Enable-MailUser cmdlet mail-enables existing users by adding the email attri
 
 Mail users have email addresses and accounts in the Exchange organization, but they don't have Exchange mailboxes. Email messages sent to mail users are delivered to the specified external email address.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -208,7 +208,7 @@ Accept wildcard characters: False
 
 The MacAttachmentFormat parameter specifies the Apple Macintosh operating system attachment format to use for messages sent to the mail contact or mail user. Valid values are:
 
-- BinHex (This is the default value)
+- BinHex (default value)
 - UuEncode
 - AppleSingle
 - AppleDouble
@@ -238,7 +238,7 @@ The MessageBodyFormat parameter specifies the message body format for messages s
 
 - Text
 - Html
-- TextAndHtml (This is the default value)
+- TextAndHtml (default value)
 
 The MessageFormat and MessageBodyFormat parameters are interdependent:
 
@@ -264,7 +264,7 @@ Accept wildcard characters: False
 The MessageFormat parameter specifies the message format for messages sent to the mail contact or mail user. Valid values are:
 
 - Text
-- Mime (This is the default value)
+- Mime (default value)
 
 The MessageFormat and MessageBodyFormat parameters are interdependent:
 
@@ -314,7 +314,7 @@ Accept wildcard characters: False
 The UsePreferMessageFormat specifies whether the message format settings configured for the mail user or mail contact override the global settings configured for the remote domain or configured by the message sender. Valid value are:
 
 - $true: Messages sent to the mail user or mail contact use the message format that's configured for the mail user or mail contact.
-- $false: Messages sent to the mail user or mail contact use the message format that's configured for the remote domain (the default remote domain or a specific remote domain) or configured by the message sender. This is the default value.
+- $false: Messages sent to the mail user or mail contact use the message format that's configured for the remote domain (the default remote domain or a specific remote domain) or configured by the message sender. This value is the default.
 
 ```yaml
 Type: Boolean
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-Mailbox.md b/exchange/exchange-ps/ExchangePowerShell/Enable-Mailbox.md
index dc154ed3be..25c3826181 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-Mailbox.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-Mailbox.md
@@ -13,7 +13,7 @@ title: Enable-Mailbox
 # Enable-Mailbox
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Enable-Mailbox cmdlet to create mailboxes for existing users who don't already have mailboxes. You can also use this cmdlet to create In-Place archives for existing mailboxes.
 
@@ -273,7 +273,7 @@ The Enable-Mailbox cmdlet mailbox-enables existing users, public folders, or Ine
 
 When mailbox-enabling an existing user, beware of non-supported characters in the user account or Name property. If you don't specify an Alias value when you mailbox-enable the user, Exchange converts all non-supported characters to question marks (?). To avoid question marks in the Alias, verify that the user account and Name properties have only supported ASCII or Unicode characters or specify an Alias value when you mailbox-enable the user.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 In Exchange Server, the [CommonParameters](https://go.microsoft.com/fwlink/p/?LinkID=113216) InformationVariable and InformationAction don't work.
 
@@ -894,7 +894,7 @@ The HoldForMigration switch specifies whether to prevent any client or user, exc
 
 You need to use this switch when you create the first public folder, which is called the hierarchy mailbox, in your organization.
 
-Use this switch only if you plan to migrate legacy Exchange 2010 public folders to Exchange 2016. If you use this switch but don't have legacy public folders to migrate, you won't be able to create any public folders.
+Use this switch only if you plan to migrate legacy Exchange 2010 public folders to Exchange 2016. If you use this switch but don't have legacy public folders to migrate, you can't create any public folders.
 
 ```yaml
 Type: SwitchParameter
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-MailboxQuarantine.md b/exchange/exchange-ps/ExchangePowerShell/Enable-MailboxQuarantine.md
index cf97201621..867711e84f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-MailboxQuarantine.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-MailboxQuarantine.md
@@ -54,7 +54,7 @@ Enable-MailboxQuarantine -Database <DatabaseIdParameter> -StoreMailboxIdentity <
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 

From 8b2ead4efaa1e87650461f8dba6aaac2d3d75ce3 Mon Sep 17 00:00:00 2001
From: Chris Davis <chris.davis@microsoft.com>
Date: Tue, 5 Aug 2025 17:18:27 -0700
Subject: [PATCH 074/145] Acrolinx 2

---
 .../Enable-MalwareFilterRule.md               |  4 ++--
 .../Enable-MetaCacheDatabase.md               |  2 +-
 .../Enable-OrganizationCustomization.md       | 10 ++++----
 .../Enable-OutlookAnywhere.md                 | 23 ++++++++-----------
 .../Enable-OutlookProtectionRule.md           |  4 ++--
 .../Enable-PushNotificationProxy.md           |  2 +-
 .../Enable-RemoteMailbox.md                   |  2 +-
 .../Enable-ReportSubmissionRule.md            |  2 +-
 .../Enable-SafeAttachmentRule.md              |  2 +-
 .../Enable-SafeLinksRule.md                   |  2 +-
 .../Enable-ServiceEmailChannel.md             |  2 +-
 .../Enable-SmtpDaneInbound.md                 |  2 +-
 .../ExchangePowerShell/Enable-SweepRule.md    |  4 ++--
 .../Enable-TransportAgent.md                  |  2 +-
 .../Enable-TransportRule.md                   |  8 +++----
 .../Enable-UMAutoAttendant.md                 |  2 +-
 .../Enable-UMCallAnsweringRule.md             |  4 ++--
 .../ExchangePowerShell/Enable-UMIPGateway.md  |  2 +-
 .../ExchangePowerShell/Enable-UMMailbox.md    |  8 +++----
 .../ExchangePowerShell/Enable-UMServer.md     |  4 ++--
 .../ExchangePowerShell/Enable-UMService.md    |  4 ++--
 .../Execute-AzureADLabelSync.md               |  2 +-
 .../Expedite-Delicensing.md                   |  2 +-
 .../Export-ActiveSyncLog.md                   |  2 +-
 .../Export-ActivityExplorerData.md            |  4 ++--
 .../Export-AutoDiscoverConfig.md              |  8 +++----
 .../Export-DlpPolicyCollection.md             |  4 ++--
 .../Export-ExchangeCertificate.md             |  4 ++--
 .../Export-JournalRuleCollection.md           |  2 +-
 .../Export-MailboxDiagnosticLogs.md           |  4 ++--
 .../ExchangePowerShell/Export-Message.md      |  2 +-
 .../Export-MigrationReport.md                 |  4 ++--
 .../Export-QuarantineMessage.md               |  2 +-
 .../Export-RecipientDataProperty.md           |  2 +-
 .../Export-TransportRuleCollection.md         |  4 ++--
 .../Export-UMCallDataRecord.md                |  2 +-
 .../ExchangePowerShell/Export-UMPrompt.md     |  2 +-
 .../ExchangePowerShell/Get-ADPermission.md    |  4 ++--
 .../Get-ADServerSettings.md                   |  2 +-
 .../ExchangePowerShell/Get-ADSite.md          |  2 +-
 .../ExchangePowerShell/Get-ADSiteLink.md      |  2 +-
 .../Get-ATPBuiltInProtectionRule.md           |  2 +-
 .../Get-ATPProtectionPolicyRule.md            |  2 +-
 .../Get-ATPTotalTrafficReport.md              |  2 +-
 .../ExchangePowerShell/Get-AcceptedDomain.md  |  4 ++--
 .../Get-AccessToCustomerDataRequest.md        |  2 +-
 .../Get-ActiveSyncDevice.md                   |  4 ++--
 .../Get-ActiveSyncDeviceAccessRule.md         |  4 ++--
 .../Get-ActiveSyncDeviceAutoblockThreshold.md |  2 +-
 .../Get-ActiveSyncDeviceClass.md              |  4 ++--
 .../Get-ActiveSyncDeviceStatistics.md         |  4 ++--
 .../Get-ActiveSyncMailboxPolicy.md            |  4 ++--
 .../Get-ActiveSyncOrganizationSettings.md     |  4 ++--
 .../Get-ActiveSyncVirtualDirectory.md         |  2 +-
 .../Get-AddressBookPolicy.md                  |  4 ++--
 .../ExchangePowerShell/Get-AddressList.md     |  4 ++--
 .../Get-AdminAuditLogConfig.md                |  4 ++--
 .../Get-AdministrativeUnit.md                 |  2 +-
 .../ExchangePowerShell/Get-AgentLog.md        |  2 +-
 .../Get-AggregateZapReport.md                 |  2 +-
 .../ExchangePowerShell/Get-AntiPhishPolicy.md |  2 +-
 .../ExchangePowerShell/Get-AntiPhishRule.md   |  2 +-
 .../exchange-ps/ExchangePowerShell/Get-App.md |  4 ++--
 .../Get-AppRetentionCompliancePolicy.md       |  2 +-
 .../Get-ApplicationAccessPolicy.md            |  2 +-
 .../ExchangePowerShell/Get-ArcConfig.md       |  2 +-
 .../Get-AtpPolicyForO365.md                   |  2 +-
 .../ExchangePowerShell/Get-AuditLogSearch.md  |  6 ++---
 .../ExchangePowerShell/Get-AuthConfig.md      |  2 +-
 .../ExchangePowerShell/Get-AuthRedirect.md    |  2 +-
 .../ExchangePowerShell/Get-AuthServer.md      |  4 ++--
 .../Get-AuthenticationPolicy.md               |  4 ++--
 .../Get-AutoSensitivityLabelPolicy.md         |  2 +-
 .../Get-AutoSensitivityLabelRule.md           |  4 ++--
 .../Get-AutodiscoverVirtualDirectory.md       |  2 +-
 .../Get-AvailabilityAddressSpace.md           |  4 ++--
 .../Get-AvailabilityConfig.md                 |  4 ++--
 .../Get-AvailabilityReportOutage.md           |  2 +-
 .../Get-BlockedConnector.md                   |  2 +-
 .../Get-BlockedSenderAddress.md               |  4 ++--
 .../ExchangePowerShell/Get-CASMailbox.md      |  4 ++--
 .../ExchangePowerShell/Get-CASMailboxPlan.md  |  2 +-
 .../Get-CalendarDiagnosticAnalysis.md         |  6 ++---
 .../Get-CalendarDiagnosticLog.md              |  8 +++----
 .../Get-CalendarDiagnosticObjects.md          | 12 +++++-----
 .../Get-CalendarNotification.md               |  4 ++--
 .../Get-CalendarProcessing.md                 |  6 ++---
 .../ExchangePowerShell/Get-CaseHoldPolicy.md  |  2 +-
 .../Get-ClassificationRuleCollection.md       |  4 ++--
 .../Get-ClientAccessArray.md                  |  2 +-
 .../Get-ClientAccessRule.md                   |  4 ++--
 .../Get-ClientAccessServer.md                 |  2 +-
 .../Get-ClientAccessService.md                |  2 +-
 .../ExchangePowerShell/Get-Clutter.md         |  2 +-
 .../Get-CmdletExtensionAgent.md               |  2 +-
 95 files changed, 165 insertions(+), 168 deletions(-)

diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-MalwareFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-MalwareFilterRule.md
index b323fd1b21..af974853e5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-MalwareFilterRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-MalwareFilterRule.md
@@ -13,7 +13,7 @@ title: Enable-MalwareFilterRule
 # Enable-MalwareFilterRule
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Enable-MalwareFilterRule cmdlet to enable malware filter rules in your organization.
 
@@ -30,7 +30,7 @@ Enable-MalwareFilterRule [-Identity] <RuleIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-MetaCacheDatabase.md b/exchange/exchange-ps/ExchangePowerShell/Enable-MetaCacheDatabase.md
index e498da9e61..dfaa1c8861 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-MetaCacheDatabase.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-MetaCacheDatabase.md
@@ -29,7 +29,7 @@ Enable-MetaCacheDatabase -Server <String[]>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-OrganizationCustomization.md b/exchange/exchange-ps/ExchangePowerShell/Enable-OrganizationCustomization.md
index 0737dacb31..bd23fa403a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-OrganizationCustomization.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-OrganizationCustomization.md
@@ -15,7 +15,7 @@ title: Enable-OrganizationCustomization
 ## SYNOPSIS
 This cmdlet is available only in the cloud-based service.
 
-You may be prompted to run the EnableOrganizationCustomization cmdlet before you create or modify objects in your Exchange Online organization.
+You might be prompted to run the EnableOrganizationCustomization cmdlet before you create or modify objects in your Exchange Online organization.
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
@@ -28,7 +28,7 @@ Enable-OrganizationCustomization [-Confirm]
 ```
 
 ## DESCRIPTION
-In the Microsoft datacenters, certain objects are consolidated to save space. When you use Exchange Online PowerShell or the Exchange admin center to modify one of these objects for the first time, you may encounter an error message that tells you to run the Enable-OrganizationCustomization cmdlet.
+In the Microsoft datacenters, certain objects are consolidated to save space. When you use Exchange Online PowerShell or the Exchange admin center to modify one of these objects for the first time, you might encounter an error message that tells you to run the Enable-OrganizationCustomization cmdlet.
 
 Here are some examples of when you might see this:
 
@@ -39,11 +39,11 @@ Here are some examples of when you might see this:
 - Creating a new retention policy or modifying a built-in retention policy.
 - Enabling preset security policies in the Microsoft Defender portal.
 
-Note that you are only required to run the Enable-OrganizationCustomization cmdlet once in your Exchange Online organization. If you attempt to run the cmdlet again, you'll get an error.
+You are only required to run the Enable-OrganizationCustomization cmdlet once in your Exchange Online organization. If you attempt to run the cmdlet again, you get an error.
 
-Whether or not this command has been previously run in an organization is available in the IsDehydrated property of the Get-OrganizationConfig cmdlet: False ($false) = the command has already been run; True ($true) = the command has never been run.
+Whether or not this command is previously run in an organization is available in the IsDehydrated property of the Get-OrganizationConfig cmdlet: False ($false) = the command has already been run; True ($true) = the command has never been run.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-OutlookAnywhere.md b/exchange/exchange-ps/ExchangePowerShell/Enable-OutlookAnywhere.md
index f3108d903a..2297a39956 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-OutlookAnywhere.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-OutlookAnywhere.md
@@ -57,7 +57,7 @@ When you run this cmdlet, it can take as long as an hour for the settings to bec
 
 For more information about the different authentication methods that you can see in this article, see [Understanding HTTP Authentication](https://learn.microsoft.com/dotnet/framework/wcf/feature-details/understanding-http-authentication).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -95,7 +95,7 @@ The ClientAuthenticationMethod parameter specifies the authentication method tha
 
 This parameter must be specified if you don't use the DefaultAuthenticationMethod parameter. When you use this parameter without specifying the IISAuthenticationMethods parameter, IISAuthenticationMethods parameter is set to both NTLM and Basic.
 
-Although this parameter only allows setting one authentication method, the command won't return an error if you include multiple values.
+Although this parameter only allows setting one authentication method, the command doesn't return an error if you include multiple values.
 
 ```yaml
 Type: AuthenticationMethod
@@ -217,9 +217,9 @@ The ExtendedProtectionFlags parameter is used to customize the options you use i
 
 - None: Default setting.
 - Proxy: Specifies that a proxy is terminating the SSL channel. A Service Principal Name (SPN) must be registered in the ExtendedProtectionSPNList parameter if proxy mode is configured.
-- ProxyCoHosting: Specifies that both HTTP and HTTPS traffic may be accessing the Client Access server and that a proxy is located between at least some of the clients and the Client Access server.
+- ProxyCoHosting: Specifies that both HTTP and HTTPS traffic might be accessing the Client Access server and that a proxy is located between at least some of the clients and the Client Access server.
 - AllowDotlessSPN: Specifies whether you want to support valid SPNs that aren't in the fully qualified domain name (FQDN) format, for example ContosoMail. You specify valid SPNs with the ExtendedProtectionSPNList parameter. This option makes extended protection less secure because dotless certificates aren't unique, so it isn't possible to ensure that the client-to-proxy connection was established over a secure channel.
-- NoServiceNameCheck: Specifies that the SPN list won't be checked to validate a channel binding token. This option makes Extended Protection for Authentication less secure. We generally don't recommend this setting.
+- NoServiceNameCheck: Specifies that the SPN list isn't checked to validate a channel binding token. This option makes Extended Protection for Authentication less secure. We generally don't recommend this setting.
 
 ```yaml
 Type: MultiValuedProperty
@@ -241,7 +241,7 @@ The ExtendedProtectionSPNList parameter specifies a list of valid Service Princi
 
 The possible values are:
 
-- Null This is the default value.
+- Null This value is the default.
 - Single SPN or comma delimited list of valid SPNs By default, you must specify the fully qualified domain name (FQDN) (for example mail.contoso.com) for each SPN. If you want to add an SPN that's not an FQDN (for example, ContosoMail), you must also use the ExtendedProtectionTokenChecking parameter with the AllowDotlessSPN value. You specify the domain in SPN format. The SPN format is `Protocol\FQDN` (for example, `HTTP/mail.contoso.com`).
 
 ```yaml
@@ -262,14 +262,11 @@ Accept wildcard characters: False
 
 The ExtendedProtectionTokenChecking parameter defines how you want to use Extended Protection for Authentication on the specified Exchange virtual directory. Extended Protection for Authentication isn't enabled by default. The available settings are:
 
-- None Extended Protection for Authentication won't be used. Connections between the client and Exchange won't use Extended Protection for Authentication on this virtual directory. This is the default setting.
-- Allow Extended Protection for Authentication will be used for connections between the client and Exchange on this virtual directory if both the client and server support Extended Protection for Authentication. Connections that don't support Extended Protection for Authentication on the client and server will work, but may not be as secure as a connection using Extended Protection for Authentication.
+- None Extended Protection for Authentication isn't used. Connections between the client and Exchange don't use Extended Protection for Authentication on this virtual directory. This is the default setting.
+- Allow Extended Protection for Authentication is used for connections between the client and Exchange on this virtual directory if both the client and server support Extended Protection for Authentication. Connections that don't support Extended Protection for Authentication on the client and server work, but might not be as secure as a connection using Extended Protection for Authentication.
+- Require Extended Protection for Authentication is used for all connections between clients and Exchange servers for this virtual directory. If either the client or server doesn't support Extended Protection for Authentication, the connection between the client and server will fail. If you set this option, you must also set a value for the ExtendedProtectionSPNList parameter.
 
-If you have a proxy server between the client and the Client Access server that's configured to terminate the client-to-proxy SSL channel, you must also configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter.
-
-- Require Extended Protection for Authentication will be used for all connections between clients and Exchange servers for this virtual directory. If either the client or server doesn't support Extended Protection for Authentication, the connection between the client and server will fail. If you set this option, you must also set a value for the ExtendedProtectionSPNList parameter.
-
-If you have a proxy server between the client and the Client Access server that's configured to terminate the client-to-proxy SSL channel, you must also configure one or more SPNs using the parameter ExtendedProtectionSPNList.
+**Note**: If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter.
 
 To learn more about Extended Protection for Authentication, see [Understanding Extended Protection for Authentication](https://learn.microsoft.com/previous-versions/office/exchange-server-2010/ff459225(v=exchg.141)).
 
@@ -291,7 +288,7 @@ Accept wildcard characters: False
 
 The IISAuthenticationMethods parameter specifies the authentication method that's enabled on the /rpc virtual directory in IIS. You can set the virtual directory to allow Basic authentication or NTLM authentication. Alternatively, you can also set the virtual directory to allow both Basic and NTLM authentication. All other authentication methods are disabled.
 
-You may want to enable both Basic and NTLM authentication if you're using the IIS virtual directory with multiple applications that require different authentication methods.
+You might want to enable both Basic and NTLM authentication if you're using the IIS virtual directory with multiple applications that require different authentication methods.
 
 When you configure this setting using the IIS interface, you can enable as many authentication methods as you want.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-OutlookProtectionRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-OutlookProtectionRule.md
index 1224f593ff..c9d18eab91 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-OutlookProtectionRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-OutlookProtectionRule.md
@@ -15,7 +15,7 @@ title: Enable-OutlookProtectionRule
 ## SYNOPSIS
 **Note**: This cmdlet is no longer supported in the cloud-based service.
 
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Enable-OutlookProtectionRule cmdlet to enable an existing Outlook protection rule.
 
@@ -34,7 +34,7 @@ Enable-OutlookProtectionRule [-Identity] <RuleIdParameter>
 ## DESCRIPTION
 Outlook protection rules are used to automatically Information Rights Management (IRM)-protect messages using a Rights Management Services (RMS) template before the message is sent. However, Outlook protection rules don't inspect message content. To rights-protect messages based on message content, use transport protection rules. For more information, see [Outlook protection rules](https://learn.microsoft.com/exchange/outlook-protection-rules-exchange-2013-help).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-PushNotificationProxy.md b/exchange/exchange-ps/ExchangePowerShell/Enable-PushNotificationProxy.md
index 468851c7ae..6cf4a5c65c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-PushNotificationProxy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-PushNotificationProxy.md
@@ -34,7 +34,7 @@ Enable-PushNotificationProxy [-Confirm]
 ## DESCRIPTION
 The push notification proxy relays event notifications (for example, new email or calendar updates) for on-premises mailboxes through Microsoft 365 to Outlook on the web for devices on the user's device.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-RemoteMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Enable-RemoteMailbox.md
index a6256027c7..1f12234ec2 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-RemoteMailbox.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-RemoteMailbox.md
@@ -102,7 +102,7 @@ Directory synchronization must be configured correctly for a mailbox to be creat
 
 The policies that you apply to recipients in the on-premises Exchange organization, such as Unified Messaging or compliance policies, aren't applied to mailboxes in the service. You must configure policies in the service if you want policies to be applied to recipients in the service.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-ReportSubmissionRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-ReportSubmissionRule.md
index 56e3f4dd50..29852d3479 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-ReportSubmissionRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-ReportSubmissionRule.md
@@ -29,7 +29,7 @@ Enable-ReportSubmissionRule [-Identity] <RuleIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-SafeAttachmentRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-SafeAttachmentRule.md
index f90229ee73..0cd9ec3748 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-SafeAttachmentRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-SafeAttachmentRule.md
@@ -31,7 +31,7 @@ Enable-SafeAttachmentRule [-Identity] <RuleIdParameter>
 ## DESCRIPTION
 Safe Attachments is a feature in Microsoft Defender for Office 365 that opens email attachments in a special hypervisor environment to detect malicious activity. For more information, see [Safe Attachments in Defender for Office 365](https://learn.microsoft.com/defender-office-365/safe-attachments-about).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-SafeLinksRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-SafeLinksRule.md
index c328540126..ef7fe14799 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-SafeLinksRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-SafeLinksRule.md
@@ -31,7 +31,7 @@ Enable-SafeLinksRule [-Identity] <RuleIdParameter>
 ## DESCRIPTION
 Safe Links is a feature in Microsoft Defender for Office 365 that checks links in email messages to see if they lead to malicious web sites. When a user clicks a link in a message, the URL is temporarily rewritten and checked against a list of known, malicious web sites. Safe Links includes the URL trace reporting feature to help determine who has clicked through to a malicious web site.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-ServiceEmailChannel.md b/exchange/exchange-ps/ExchangePowerShell/Enable-ServiceEmailChannel.md
index 2e4d132aa7..4a98df3b35 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-ServiceEmailChannel.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-ServiceEmailChannel.md
@@ -32,7 +32,7 @@ Enable-ServiceEmailChannel [-Identity] <MailboxIdParameter>
 ## DESCRIPTION
 The .NET service channel enables Microsoft Exchange to store information that it later forwards to applications or devices that aren't permanently connected to the server running Exchange. This cmdlet creates a receive folder in the user's mailbox under the root folder named Service E-mail.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-SmtpDaneInbound.md b/exchange/exchange-ps/ExchangePowerShell/Enable-SmtpDaneInbound.md
index 98ea3d22e8..3f8909bb29 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-SmtpDaneInbound.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-SmtpDaneInbound.md
@@ -31,7 +31,7 @@ Enable-SmtpDaneInbound [-DomainName] <String>
 ## DESCRIPTION
 For more information about debugging, enabling, and disabling SMTP DANE with DNSSEC, see [How SMTP DANE works](https://learn.microsoft.com/purview/how-smtp-dane-works).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-SweepRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-SweepRule.md
index db15150448..52efc9fe3c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-SweepRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-SweepRule.md
@@ -13,7 +13,7 @@ title: Enable-SweepRule
 # Enable-SweepRule
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Enable-SweepRule cmdlet to enable Sweep rules in mailboxes.
 
@@ -31,7 +31,7 @@ Enable-SweepRule [-Identity] <SweepRuleIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-TransportAgent.md b/exchange/exchange-ps/ExchangePowerShell/Enable-TransportAgent.md
index 1c9fd5b5c9..48365cd90b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-TransportAgent.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-TransportAgent.md
@@ -31,7 +31,7 @@ Enable-TransportAgent [-Identity] <TransportAgentObjectId>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-TransportRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-TransportRule.md
index fad19405e6..88ee1e141b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-TransportRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-TransportRule.md
@@ -13,7 +13,7 @@ title: Enable-TransportRule
 # Enable-TransportRule
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Enable-TransportRule cmdlet to enable transport rules (mail flow rules) in your organization.
 
@@ -33,7 +33,7 @@ Enable-TransportRule [-Identity] <RuleIdParameter>
 ## DESCRIPTION
 To disable rules that are enabled, use the Disable-TransportRule cmdlet.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -124,11 +124,11 @@ Accept wildcard characters: False
 
 The Mode parameter specifies how the rule operates after it's enabled. Valid values are:
 
-- Audit: The actions that the rule would have taken are written to the message tracking log, but no any action is taken on the message that would impact delivery.
+- Audit: The actions that the rule would have taken are written to the message tracking log, but no any action is taken on the message that would affect delivery.
 - AuditAndNotify: The rule operates the same as in Audit mode, but notifications are also enabled.
 - Enforce: All actions specified in the rule are taken.
 
-The value that has already been set in the rule will be persevered, unless -Mode parameter is specified.
+If you don't use this parameter, the value already set in the rule is persevered.
 
 ```yaml
 Type: RuleMode
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-UMAutoAttendant.md b/exchange/exchange-ps/ExchangePowerShell/Enable-UMAutoAttendant.md
index fdf6d70163..a990173558 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-UMAutoAttendant.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-UMAutoAttendant.md
@@ -32,7 +32,7 @@ Enable-UMAutoAttendant [-Identity] <UMAutoAttendantIdParameter>
 ## DESCRIPTION
 The Enable-UMAutoAttendant cmdlet enables the UM auto attendant by modifying its status variable. When you create a UM auto attendant, it isn't enabled by default. For the auto attendant to answer incoming calls, you must first enable it. After this task is completed, the UM auto attendant answers incoming calls.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-UMCallAnsweringRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-UMCallAnsweringRule.md
index 1d442c6278..85f18e53c9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-UMCallAnsweringRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-UMCallAnsweringRule.md
@@ -15,7 +15,7 @@ title: Enable-UMCallAnsweringRule
 ## SYNOPSIS
 This cmdlet is available only in on-premises Exchange.
 
-Use the Enable-UMCallAnsweringRule cmdlet to enable a call answering rule that has been created within a UM-enabled mailbox.
+Use the Enable-UMCallAnsweringRule cmdlet to enable a call answering rule that is created within a UM-enabled mailbox.
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
@@ -35,7 +35,7 @@ The Enable-UMCallAnsweringRule cmdlet enables the call answering rule by modifyi
 
 After this task is completed, the cmdlet sets the parameters and values specified. When you enable a call answering rule, the call answering rule is processed when an incoming call is received.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-UMIPGateway.md b/exchange/exchange-ps/ExchangePowerShell/Enable-UMIPGateway.md
index a26ffb5377..3bac3cc380 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-UMIPGateway.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-UMIPGateway.md
@@ -34,7 +34,7 @@ The status variable for a UM IP gateway can be used to enable or disable call an
 
 After this task is completed, the UM IP gateway answers incoming calls and makes outgoing calls through the IP gateway or IP Private Branch eXchange (PBX).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-UMMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Enable-UMMailbox.md
index 67cdd97fb3..63b1283604 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-UMMailbox.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-UMMailbox.md
@@ -63,7 +63,7 @@ Enable-UMMailbox [-Identity] <MailboxIdParameter>
 ## DESCRIPTION
 When the mailbox is enabled for Unified Messaging, the settings from a UM mailbox policy are applied to the mailbox. After the mailbox is enabled for Unified Messaging, the user can use the UM features that are included in Microsoft Exchange.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -140,7 +140,7 @@ Accept wildcard characters: False
 
 The AutomaticSpeechRecognitionEnabled parameter specifies whether to enable Automatic Speech Recognition (ASR) for the UM mailbox. Valid values are:
 
-- $true: ASR is enabled for the mailbox. This is the default value. ASR is available only if the user's specified preferred language is installed.
+- $true: ASR is enabled for the mailbox. This value is the default. ASR is available only if the user's specified preferred language is installed.
 - $false: ASR is disabled for the mailbox.
 
 ```yaml
@@ -336,7 +336,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2016
 
-The SendWelcomeMail parameter specifies whether you want to send a welcome message after the mailbox has been enabled for UM. Valid values are:
+The SendWelcomeMail parameter specifies whether you want to send a welcome message after the mailbox is enabled for UM. Valid values are:
 
 - $true: Send the welcome to UM message.
 - $false: Don't send the welcome to UM message.
@@ -375,7 +375,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
 
-The ValidateOnly switch tells the cmdlet to evaluate the conditions and requirements necessary to perform the operation and then reports whether the operation will succeed or fail. You don't need to specify a value with this switch.
+The ValidateOnly switch specifies whether to evaluate the potential success or failure of the command without making changes. You don't need to specify a value with this switch.
 
 No changes are made when the ValidateOnly switch is used.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-UMServer.md b/exchange/exchange-ps/ExchangePowerShell/Enable-UMServer.md
index 8ee6d80f46..6f5b17049c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-UMServer.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-UMServer.md
@@ -30,11 +30,11 @@ Enable-UMServer [-Identity] <UMServerIdParameter>
 ```
 
 ## DESCRIPTION
-The Enable-UMServer cmdlet sets the status of a Unified Messaging server. A UM server has a logical status variable controlled using the enable and disable cmdlets. A UM server won't process any new calls unless it's in the enabled state. With the status variable, you can start or stop call processing on a UM server so the UM server can be brought online or taken offline in a controlled way.
+The Enable-UMServer cmdlet sets the status of a Unified Messaging server. A UM server has a logical status variable controlled using the enable and disable cmdlets. A UM server doesn't process any new calls unless it's in the enabled state. With the status variable, you can start or stop call processing on a UM server so the UM server can be brought online or taken offline in a controlled way.
 
 After this task is completed, the Unified Messaging server is available to answer incoming calls.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-UMService.md b/exchange/exchange-ps/ExchangePowerShell/Enable-UMService.md
index 3207726463..e54a0c4d8f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-UMService.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-UMService.md
@@ -32,11 +32,11 @@ Enable-UMService [-Identity] <UMServerIdParameter>
 ```
 
 ## DESCRIPTION
-The Enable-UMService cmdlet sets the status of an Exchange server running the Unified Messaging server role. A UM server has a logical status variable controlled using the enable and disable cmdlets. A UM server won't process any new calls unless it's in the enabled state. With the status variable, you can start or stop call processing on a UM server so the UM server can be brought online or taken offline in a controlled way.
+The Enable-UMService cmdlet sets the status of an Exchange server running the Unified Messaging server role. A UM server has a logical status variable controlled using the enable and disable cmdlets. A UM server doesn't process any new calls unless it's in the enabled state. With the status variable, you can start or stop call processing on a UM server so the UM server can be brought online or taken offline in a controlled way.
 
 After this task is completed, the UM server is available to answer incoming calls.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Execute-AzureADLabelSync.md b/exchange/exchange-ps/ExchangePowerShell/Execute-AzureADLabelSync.md
index 3868bcd8ea..2290b1aed6 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Execute-AzureADLabelSync.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Execute-AzureADLabelSync.md
@@ -35,7 +35,7 @@ To use this cmdlet in Security & Compliance PowerShell, you need to be assigned
 Execute-AzureADLabelSync
 ```
 
-This example will initialize the synchronization of sensitivity labels into Microsoft Entra ID.
+This example initializes the synchronization of sensitivity labels into Microsoft Entra ID.
 
 ## PARAMETERS
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Expedite-Delicensing.md b/exchange/exchange-ps/ExchangePowerShell/Expedite-Delicensing.md
index f490e9a900..b7b89bd6a4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Expedite-Delicensing.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Expedite-Delicensing.md
@@ -27,7 +27,7 @@ Expedite-Delicensing [-Identity] <RecipientIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Export-ActiveSyncLog.md b/exchange/exchange-ps/ExchangePowerShell/Export-ActiveSyncLog.md
index 044fde6d46..e264cc2be0 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Export-ActiveSyncLog.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Export-ActiveSyncLog.md
@@ -37,7 +37,7 @@ Export-ActiveSyncLog -Filename <String>
 ## DESCRIPTION
 The Export-ActiveSyncLog cmdlet parses the IIS log files and returns information about Exchange ActiveSync usage. This cmdlet can export the output to a file or display it in the Exchange Management Shell.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Export-ActivityExplorerData.md b/exchange/exchange-ps/ExchangePowerShell/Export-ActivityExplorerData.md
index 9da4987e32..83eee07bc7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Export-ActivityExplorerData.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Export-ActivityExplorerData.md
@@ -179,7 +179,7 @@ This example exports a maximum of 5000 records for the specified date range in J
 Export-ActivityExplorerData -StartTime "07/08/2022 07:15 AM" -EndTime "07/08/2022 11:08 AM" -OutputFormat Json
 ```
 
-This example exports up to 100 records for the specified date range in Json format. If more than 100 records are available, the value of the LastPage property in the command output will be False. Use the value of the Watermark property as the value of the PageCookie parameter in a new query to get the next set of records.
+This example exports up to 100 records for the specified date range in Json format. If more than 100 records are available, the value of the LastPage property in the command output is False. Use the value of the Watermark property as the value of the PageCookie parameter in a new query to get the next set of records.
 
 ### Example 3
 ```powershell
@@ -431,7 +431,7 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable
 ## NOTES
 The date-time field exported via this cmdlet is in Coordinated Universal Time (UTC).
 
-The cmdlet exports following data columns. However, not all columns will be present for each activity. For details on exported column for different activities, we recommend checking the activities in [Activity Explorer](https://learn.microsoft.com/purview/data-classification-activity-explorer).
+The cmdlet exports following data columns. However, not all columns are present for each activity. For details on exported column for different activities, we recommend checking the activities in [Activity Explorer](https://learn.microsoft.com/purview/data-classification-activity-explorer).
 
 - Activity
 - Application
diff --git a/exchange/exchange-ps/ExchangePowerShell/Export-AutoDiscoverConfig.md b/exchange/exchange-ps/ExchangePowerShell/Export-AutoDiscoverConfig.md
index b0ec8af14a..815599dd21 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Export-AutoDiscoverConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Export-AutoDiscoverConfig.md
@@ -34,9 +34,9 @@ Export-AutoDiscoverConfig -TargetForestDomainController <String>
 ```
 
 ## DESCRIPTION
-The Autodiscover Service Connection Point pointer resides Active Directory in the user account forest and includes the LDAP URL of the resource forest that the client will use to locate the Autodiscover service in the resource forest.
+The Autodiscover Service Connection Point pointer resides Active Directory in the user account forest. The pointer includes the LDAP URL of the resource forest that the client uses to locate the Autodiscover service in the resource forest.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -62,7 +62,7 @@ This example specifies that Exchange is deployed in more than one Active Directo
 
 The TargetForestDomainController parameter specifies the forest or domain controller that you want to export the Autodiscover configuration to.
 
-If the target domain controller requires signing, you'll get the error: "A more secure authentication method is required for this server". Domain controllers that require signing aren't supported.
+If the target domain controller requires signing, you get the error: "A more secure authentication method is required for this server". Domain controllers that require signing aren't supported.
 
 ```yaml
 Type: String
@@ -140,7 +140,7 @@ Accept wildcard characters: False
 The MultipleExchangeDeployments parameter specifies whether multiple Exchange deployments exist. Valid values are:
 
 - $true: Exchange is deployed in more than one Active Directory forest, and the forests are connected. The list of authoritative accepted domains for the source forest is written to the Autodiscover service connection point object. Outlook clients use this object to select the most appropriate forest to search for the Autodiscover service.
-- $False: Multiple Exchange deployments aren't used. This is the default value.
+- $False: Multiple Exchange deployments aren't used. This value is the default.
 
 ```yaml
 Type: Boolean
diff --git a/exchange/exchange-ps/ExchangePowerShell/Export-DlpPolicyCollection.md b/exchange/exchange-ps/ExchangePowerShell/Export-DlpPolicyCollection.md
index fd15f00128..1c0e5668b1 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Export-DlpPolicyCollection.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Export-DlpPolicyCollection.md
@@ -13,7 +13,7 @@ title: Export-DlpPolicyCollection
 # Export-DlpPolicyCollection
 
 ## SYNOPSIS
-**Note**: This cmdlet has been retired from the cloud-based service. For more information, see [this blog post](https://techcommunity.microsoft.com/t5/exchange-team-blog/exchange-online-etrs-to-stop-supporting-dlp-policies/ba-p/3886713).
+**Note**: This cmdlet is retired from the cloud-based service. For more information, see [this blog post](https://techcommunity.microsoft.com/t5/exchange-team-blog/exchange-online-etrs-to-stop-supporting-dlp-policies/ba-p/3886713).
 
 This cmdlet is functional only in on-premises Exchange.
 
@@ -34,7 +34,7 @@ Export-DlpPolicyCollection [[-Identity] <DlpPolicyIdParameter>]
 ## DESCRIPTION
 The Export-DlpPolicyCollection cmdlet exports the settings of the DLP policies and the associated transport rules. You use the Import-DlpPolicyCollection to import the DLP policy collection into your organization.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Export-ExchangeCertificate.md b/exchange/exchange-ps/ExchangePowerShell/Export-ExchangeCertificate.md
index 0d42ee0899..92abab4583 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Export-ExchangeCertificate.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Export-ExchangeCertificate.md
@@ -57,7 +57,7 @@ The Export-ExchangeCertificate cmdlet creates the following types of files:
 
   Typically, you export a certificate request file if you need to resubmit the certificate request to the certification authority. You can't import an exported certificate request on another server.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -161,7 +161,7 @@ Accept wildcard characters: False
 
 The BinaryEncoded switch encodes the exported certificate or certificate request file by using Distinguished Encoding Rules (DER). You don't need to specify a value with this switch.
 
-Typically, you use this switch when you export a certificate, because you can store the certificate and its private key or chain of trust in a single binary file when you also use the Password parameter. If you don't use this switch, the exported certificate file is Base64 encoded, and you'll need to export any intermediate or root certificates in the chain of trust separately.
+Typically, you use this switch when you export a certificate, because you can store the certificate and its private key or chain of trust in a single binary file when you also use the Password parameter. If you don't use this switch, the exported certificate file is Base64 encoded, and you need to export any intermediate or root certificates in the chain of trust separately.
 
 ```yaml
 Type: SwitchParameter
diff --git a/exchange/exchange-ps/ExchangePowerShell/Export-JournalRuleCollection.md b/exchange/exchange-ps/ExchangePowerShell/Export-JournalRuleCollection.md
index 88844ce4ba..ba292844af 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Export-JournalRuleCollection.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Export-JournalRuleCollection.md
@@ -33,7 +33,7 @@ Export-JournalRuleCollection [[-Identity] <RuleIdParameter>]
 ## DESCRIPTION
 You can use the Export-JournalRuleCollection cmdlet to export journal rules in your organization to create a backup copy of your rules.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Export-MailboxDiagnosticLogs.md b/exchange/exchange-ps/ExchangePowerShell/Export-MailboxDiagnosticLogs.md
index fac4b1dd30..6fd1c0489b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Export-MailboxDiagnosticLogs.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Export-MailboxDiagnosticLogs.md
@@ -13,7 +13,7 @@ title: Export-MailboxDiagnosticLogs
 # Export-MailboxDiagnosticLogs
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Export-MailboxDiagnosticLogs cmdlet to export diagnostic data from user and system mailboxes in your organization.
 
@@ -51,7 +51,7 @@ Export-MailboxDiagnosticLogs [-Identity] <GeneralMailboxIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Export-Message.md b/exchange/exchange-ps/ExchangePowerShell/Export-Message.md
index 4046ba538f..e4a8c0a1c4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Export-Message.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Export-Message.md
@@ -31,7 +31,7 @@ Export-Message [-Identity] <MessageIdentity>
 ## DESCRIPTION
 The Export-Message cmdlet copies messages from the Delivery queue, the Unreachable queue, or the poison message queue on Mailbox server or an Edge Transport server to a specified file path. Before you export a message, you must first suspend the message. Messages in the poison message queue are already suspended. You can use the Export-Message cmdlet to copy messages to the Replay directory of another Mailbox server for delivery.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Export-MigrationReport.md b/exchange/exchange-ps/ExchangePowerShell/Export-MigrationReport.md
index 98abe6ceae..616210274f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Export-MigrationReport.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Export-MigrationReport.md
@@ -13,7 +13,7 @@ title: Export-MigrationReport
 # Export-MigrationReport
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 The Export-MigrationReport is used by the Exchange migration process to enable an administrator to download a CSV file that contains migration errors for a selected migration batch. This cmdlet isn't run by an administrator in Windows PowerShell.
 
@@ -42,7 +42,7 @@ Export-MigrationReport [-Identity] <MigrationReportIdParameter> -RowCount <Int32
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Export-QuarantineMessage.md b/exchange/exchange-ps/ExchangePowerShell/Export-QuarantineMessage.md
index e18eff76d6..4b11731d00 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Export-QuarantineMessage.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Export-QuarantineMessage.md
@@ -50,7 +50,7 @@ Export-QuarantineMessage -Identity <QuarantineMessageIdentity>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Export-RecipientDataProperty.md b/exchange/exchange-ps/ExchangePowerShell/Export-RecipientDataProperty.md
index be24b3e0be..45daf7cf05 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Export-RecipientDataProperty.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Export-RecipientDataProperty.md
@@ -42,7 +42,7 @@ Export-RecipientDataProperty [-Identity] <MailboxUserContactIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Export-TransportRuleCollection.md b/exchange/exchange-ps/ExchangePowerShell/Export-TransportRuleCollection.md
index 18d538f220..5369d2b033 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Export-TransportRuleCollection.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Export-TransportRuleCollection.md
@@ -13,7 +13,7 @@ title: Export-TransportRuleCollection
 # Export-TransportRuleCollection
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Export-TransportRuleCollection cmdlet to export the transport rules in your organization.
 
@@ -36,7 +36,7 @@ The Export-TransportRuleCollection cmdlet can be used to export the transport ru
 
 Exporting the rules collection is a two-step process. You first export the rules collection to a variable, and then use the Set-Content cmdlet to write the data to an XML file. For more information, see [Set-Content](https://learn.microsoft.com/powershell/module/microsoft.powershell.management/set-content).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Export-UMCallDataRecord.md b/exchange/exchange-ps/ExchangePowerShell/Export-UMCallDataRecord.md
index 0b1bb2fb95..32025032ee 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Export-UMCallDataRecord.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Export-UMCallDataRecord.md
@@ -36,7 +36,7 @@ The Export-UMCallDataRecord cmdlet exports Unified Messaging call data records f
 
 After this task is completed, a report is generated that contains Unified Messaging call data records.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Export-UMPrompt.md b/exchange/exchange-ps/ExchangePowerShell/Export-UMPrompt.md
index 99782c9c33..21b1a865bf 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Export-UMPrompt.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Export-UMPrompt.md
@@ -44,7 +44,7 @@ The Export-UMPrompt cmdlet exports prompts that belong to existing UM dial plan
 
 After this task is completed, the UM prompts are displayed or saved.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ADPermission.md b/exchange/exchange-ps/ExchangePowerShell/Get-ADPermission.md
index d946553a7a..59fe583201 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ADPermission.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ADPermission.md
@@ -38,9 +38,9 @@ Get-ADPermission [-Identity] <ADRawEntryIdParameter>
 ```
 
 ## DESCRIPTION
-The ADPermission cmdlets can be used to directly modify Active Directory access control lists (ACLs). Although some Microsoft Exchange features may continue to use the ADPermission cmdlets to manage permissions (for example Send and Receive connectors), Exchange 2013 and later versions no longer use customized ACLs to manage administrative permissions. If you want to grant or deny administrative permissions in Exchange 2013 or later, you need to use Role Based Access Control (RBAC). For more information about RBAC, see [Permissions in Exchange Server](https://learn.microsoft.com/Exchange/permissions/permissions).
+The ADPermission cmdlets can be used to directly modify Active Directory access control lists (ACLs). Although some Microsoft Exchange features might continue to use the ADPermission cmdlets to manage permissions (for example Send and Receive connectors), Exchange 2013 and later versions no longer use customized ACLs to manage administrative permissions. If you want to grant or deny administrative permissions in Exchange 2013 or later, you need to use Role Based Access Control (RBAC). For more information about RBAC, see [Permissions in Exchange Server](https://learn.microsoft.com/Exchange/permissions/permissions).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ADServerSettings.md b/exchange/exchange-ps/ExchangePowerShell/Get-ADServerSettings.md
index 60f17efd20..6e48794ca8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ADServerSettings.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ADServerSettings.md
@@ -26,7 +26,7 @@ Get-ADServerSettings [<CommonParameters>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ADSite.md b/exchange/exchange-ps/ExchangePowerShell/Get-ADSite.md
index fd05d2e031..158acf47bb 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ADSite.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ADSite.md
@@ -30,7 +30,7 @@ Get-ADSite [[-Identity] <AdSiteIdParameter>]
 ## DESCRIPTION
 Exchange uses Active Directory sites and the costs assigned to the Active Directory site links to make message routing decisions.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ADSiteLink.md b/exchange/exchange-ps/ExchangePowerShell/Get-ADSiteLink.md
index ed22b0467f..b0596c3e42 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ADSiteLink.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ADSiteLink.md
@@ -28,7 +28,7 @@ Get-ADSiteLink [[-Identity] <AdSiteLinkIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ATPBuiltInProtectionRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-ATPBuiltInProtectionRule.md
index 1ff7c3140b..5f7cf3cb3b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ATPBuiltInProtectionRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ATPBuiltInProtectionRule.md
@@ -28,7 +28,7 @@ Get-ATPBuiltInProtectionRule [[-Identity] <DehydrateableRuleIdParameter>] [-Stat
 ## DESCRIPTION
 For more information about preset security policies, see [Preset security policies in EOP and Microsoft Defender for Office 365](https://learn.microsoft.com/defender-office-365/preset-security-policies).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ATPProtectionPolicyRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-ATPProtectionPolicyRule.md
index 1463a2e760..3b58d62111 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ATPProtectionPolicyRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ATPProtectionPolicyRule.md
@@ -30,7 +30,7 @@ Get-ATPProtectionPolicyRule [[-Identity] <RuleIdParameter>]
 ## DESCRIPTION
 For more information about preset security policies in PowerShell, see [Preset security policies in Exchange Online PowerShell](https://learn.microsoft.com/defender-office-365/preset-security-policies#preset-security-policies-in-exchange-online-powershell).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ATPTotalTrafficReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-ATPTotalTrafficReport.md
index 75b267a41d..e3439c0023 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ATPTotalTrafficReport.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ATPTotalTrafficReport.md
@@ -56,7 +56,7 @@ If the tenant had Safe Attachments or Safe Links policies, the messages would ha
 
 By default, the command returns data for the last 14 days. Data for the last 90 days is available.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AcceptedDomain.md b/exchange/exchange-ps/ExchangePowerShell/Get-AcceptedDomain.md
index 9ba5ea4926..7e97bc3970 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AcceptedDomain.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-AcceptedDomain.md
@@ -13,7 +13,7 @@ title: Get-AcceptedDomain
 # Get-AcceptedDomain
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-AcceptedDomain cmdlet to view the configuration information for the accepted domains in your organization.
 
@@ -29,7 +29,7 @@ Get-AcceptedDomain [[-Identity] <AcceptedDomainIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AccessToCustomerDataRequest.md b/exchange/exchange-ps/ExchangePowerShell/Get-AccessToCustomerDataRequest.md
index b2043007fa..b30d05b9dc 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AccessToCustomerDataRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-AccessToCustomerDataRequest.md
@@ -31,7 +31,7 @@ Get-AccessToCustomerDataRequest [-ApprovalStatus <String>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDevice.md b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDevice.md
index ddefef7cd4..3a287a1293 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDevice.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDevice.md
@@ -13,7 +13,7 @@ title: Get-ActiveSyncDevice
 # Get-ActiveSyncDevice
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-ActiveSyncDevice cmdlet to retrieve the list of devices in your organization that have active Exchange ActiveSync partnerships.
 
@@ -50,7 +50,7 @@ Get-ActiveSyncDevice [[-Identity] <ActiveSyncDeviceIdParameter>]
 ## DESCRIPTION
 The Get-ActiveSyncDevice cmdlet returns identification, configuration and status information for each device.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceAccessRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceAccessRule.md
index d5102b012a..04f6699372 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceAccessRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceAccessRule.md
@@ -13,7 +13,7 @@ title: Get-ActiveSyncDeviceAccessRule
 # Get-ActiveSyncDeviceAccessRule
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-ActiveSyncDeviceAccessRule cmdlet to retrieve an access group of Exchange mobile devices along with their access level.
 
@@ -30,7 +30,7 @@ Get-ActiveSyncDeviceAccessRule [[-Identity] <ActiveSyncDeviceAccessRuleIdParamet
 ## DESCRIPTION
 You can create multiple groups of devices: allowed devices, blocked devices, and quarantined devices with the New-ActiveSyncDeviceAccessRule cmdlet. The Get-ActiveSyncDeviceAccessRule cmdlet retrieves the settings for any existing group.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceAutoblockThreshold.md b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceAutoblockThreshold.md
index bee07e3451..804549c94e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceAutoblockThreshold.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceAutoblockThreshold.md
@@ -30,7 +30,7 @@ Get-ActiveSyncDeviceAutoblockThreshold [[-Identity] <ActiveSyncDeviceAutoblockTh
 ## DESCRIPTION
 Microsoft Exchange and Exchange ActiveSync have the capability to block Exchange ActiveSync mobile devices if these devices display any of a defined list of behaviors that have the capability to cause issues with the server. The Get-ActiveSyncDeviceAutoblockThreshold cmdlet returns the settings for the requested threshold rule.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceClass.md b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceClass.md
index 6a373b8d58..dc34912d32 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceClass.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceClass.md
@@ -13,7 +13,7 @@ title: Get-ActiveSyncDeviceClass
 # Get-ActiveSyncDeviceClass
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-ActiveSyncDeviceClass cmdlet to retrieve a list of ActiveSync devices that have connected to your organization. The cmdlet returns the mobile device type and model information.
 
@@ -32,7 +32,7 @@ Get-ActiveSyncDeviceClass [[-Identity] <ActiveSyncDeviceClassIdParameter>]
 ## DESCRIPTION
 You can use this cmdlet to view a list of mobile phones or devices by type. For example, you can return a list of all Android mobile digital devices in the organization or all Windows Phone devices in the organization.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceStatistics.md
index c79c8576e2..6413242a39 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceStatistics.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceStatistics.md
@@ -13,7 +13,7 @@ title: Get-ActiveSyncDeviceStatistics
 # Get-ActiveSyncDeviceStatistics
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-ActiveSyncDeviceStatistics cmdlet to retrieve the list of mobile devices configured to synchronize with a specified user's mailbox and return a list of statistics about the mobile devices.
 
@@ -46,7 +46,7 @@ Get-ActiveSyncDeviceStatistics -Mailbox <MailboxIdParameter>
 ## DESCRIPTION
 The Get-ActiveSyncDeviceStatistics cmdlet returns a list of statistics about each mobile device. Additionally, it allows you to retrieve logs and send those logs to a recipient for troubleshooting purposes.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncMailboxPolicy.md
index 13cdaabfc9..72c2d259e4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncMailboxPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncMailboxPolicy.md
@@ -13,7 +13,7 @@ title: Get-ActiveSyncMailboxPolicy
 # Get-ActiveSyncMailboxPolicy
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-ActiveSyncMailboxPolicy cmdlet to retrieve the Mobile Device mailbox policy settings for a specific Mobile Device mailbox policy.
 
@@ -32,7 +32,7 @@ Get-ActiveSyncMailboxPolicy [[-Identity] <MailboxPolicyIdParameter>]
 ## DESCRIPTION
 A Mobile Device mailbox policy is a group of settings that specifies how mobile devices enabled for Microsoft Exchange ActiveSync connect to the computer running Exchange. Exchange supports multiple Mobile Device mailbox policies. The Get-ActiveSyncMailboxPolicy cmdlet displays all the policy settings for the specified policy. These settings include password settings, file access settings and attachment settings.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncOrganizationSettings.md b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncOrganizationSettings.md
index c6cd6f96fa..7560cac114 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncOrganizationSettings.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncOrganizationSettings.md
@@ -13,7 +13,7 @@ title: Get-ActiveSyncOrganizationSettings
 # Get-ActiveSyncOrganizationSettings
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-ActiveSyncOrganizationSettings cmdlet to view the Microsoft Exchange ActiveSync settings for your organization.
 
@@ -28,7 +28,7 @@ Get-ActiveSyncOrganizationSettings [[-Identity] <ActiveSyncOrganizationSettingsI
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncVirtualDirectory.md
index e86d0275ad..ca9c796dcb 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncVirtualDirectory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncVirtualDirectory.md
@@ -42,7 +42,7 @@ Get-ActiveSyncVirtualDirectory [[-Identity] <VirtualDirectoryIdParameter>]
 ## DESCRIPTION
 Microsoft Exchange servers have a default virtual directory that Exchange ActiveSync mobile devices use to synchronize with the server. You can create multiple virtual directories and assign different devices to different directories.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AddressBookPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-AddressBookPolicy.md
index 48627a19bd..178bc818bb 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AddressBookPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-AddressBookPolicy.md
@@ -13,7 +13,7 @@ title: Get-AddressBookPolicy
 # Get-AddressBookPolicy
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-AddressBookPolicy cmdlet to return address book policies that match the specified conditions.
 
@@ -30,7 +30,7 @@ Get-AddressBookPolicy [[-Identity] <MailboxPolicyIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AddressList.md b/exchange/exchange-ps/ExchangePowerShell/Get-AddressList.md
index 7eacd33705..26b167606c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AddressList.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-AddressList.md
@@ -13,7 +13,7 @@ title: Get-AddressList
 # Get-AddressList
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-AddressList cmdlet to view address lists.
 
@@ -47,7 +47,7 @@ Get-AddressList [-SearchText <String>]
 ## DESCRIPTION
 You can pipe the output from the Get-AddressList cmdlet to the Remove-AddressList, Set-AddressList, Update-AddressList and Move-AddressList cmdlets instead of using the Identity parameter with each of those cmdlets.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AdminAuditLogConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-AdminAuditLogConfig.md
index 98e1a44545..946b4e03d9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AdminAuditLogConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-AdminAuditLogConfig.md
@@ -13,7 +13,7 @@ title: Get-AdminAuditLogConfig
 # Get-AdminAuditLogConfig
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-AdminAuditLogConfig cmdlet to view the administrator audit logging configuration settings.
 
@@ -29,7 +29,7 @@ Get-AdminAuditLogConfig [-DomainController <Fqdn>]
 ## DESCRIPTION
 To check the UnifiedAuditLogIngestionEnabled value in the output of this cmdlet, run the command in Exchange Online PowerShell. The value in Security & Compliance PowerShell is always False and the Set-AdminAuditLogConfig cmdlet (and the UnifiedAuditLogIngestionEnabled parameter) is not available to change it.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AdministrativeUnit.md b/exchange/exchange-ps/ExchangePowerShell/Get-AdministrativeUnit.md
index d1db51fb3f..ebc5e1b4d0 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AdministrativeUnit.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-AdministrativeUnit.md
@@ -32,7 +32,7 @@ Get-AdministrativeUnit [[-Identity] <AdministrativeUnitIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AgentLog.md b/exchange/exchange-ps/ExchangePowerShell/Get-AgentLog.md
index 7cc4bd9fa0..2875806cc5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AgentLog.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-AgentLog.md
@@ -30,7 +30,7 @@ Get-AgentLog [-EndDate <DateTime>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AggregateZapReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-AggregateZapReport.md
index fe08151188..255b5435c1 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AggregateZapReport.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-AggregateZapReport.md
@@ -37,7 +37,7 @@ For the reporting period you specify, the cmdlet returns the following informati
 - EventType
 - ZapActionCount
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AntiPhishPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-AntiPhishPolicy.md
index 86ea27c33c..cdf89a913d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AntiPhishPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-AntiPhishPolicy.md
@@ -30,7 +30,7 @@ Get-AntiPhishPolicy [-Identity <AntiPhishPolicyIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AntiPhishRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-AntiPhishRule.md
index d21b4063d9..cc2853c02c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AntiPhishRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-AntiPhishRule.md
@@ -28,7 +28,7 @@ Get-AntiPhishRule [[-Identity] <RuleIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-App.md b/exchange/exchange-ps/ExchangePowerShell/Get-App.md
index a1ade6001f..2b7fa376d0 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-App.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-App.md
@@ -13,7 +13,7 @@ title: Get-App
 # Get-App
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-App cmdlet to view installed apps.
 
@@ -33,7 +33,7 @@ Get-App [[-Identity] <AppIdParameter>]
 ## DESCRIPTION
 The Get-App cmdlet returns information about all installed apps or the details of a specific installed app.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AppRetentionCompliancePolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-AppRetentionCompliancePolicy.md
index a945fa35af..bf1ee91fe5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AppRetentionCompliancePolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-AppRetentionCompliancePolicy.md
@@ -30,7 +30,7 @@ Get-AppRetentionCompliancePolicy [[-Identity] <PolicyIdParameter>]
 ```
 
 ## DESCRIPTION
-\*-AppRetentionCompliance\* cmdlets are used for policies with adaptive policy scopes and all static policies that cover Teams private channels, Viva Engage chats, and Viva Engage community messages. Eventually, you'll use these cmdlets for most retention locations and policy types. The \*-RetentionCompliance\* cmdlets will continue to support Exchange and SharePoint locations primarily. For policies created with the \*-AppRetentionCompliance\* cmdlets, you can only set the list of included or excluded scopes for all included workloads, which means you'll likely need to create one policy per workload.
+\*-AppRetentionCompliance\* cmdlets are used for policies with adaptive policy scopes and all static policies that cover Teams private channels, Viva Engage chats, and Viva Engage community messages. Eventually, you'll use these cmdlets for most retention locations and policy types. The \*-RetentionCompliance\* cmdlets will continue to support Exchange and SharePoint locations primarily. For policies created with the \*-AppRetentionCompliance\* cmdlets, you can only set the list of included or excluded scopes for all included workloads, which means you likely need to create one policy per workload.
 
 To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions).
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ApplicationAccessPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-ApplicationAccessPolicy.md
index 83a5b541f3..4e781959c5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ApplicationAccessPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ApplicationAccessPolicy.md
@@ -29,7 +29,7 @@ Get-ApplicationAccessPolicy [[-Identity] <ApplicationAccessPolicyIdParameter>]
 ## DESCRIPTION
 This feature applies only to apps connecting to the Microsoft Graph API for Outlook resources.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ArcConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-ArcConfig.md
index 49101ba1b4..3b6f57fbd4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ArcConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ArcConfig.md
@@ -28,7 +28,7 @@ Get-ArcConfig [<CommonParameters>]
 ## DESCRIPTION
 Services that modify message content in transit before delivery can invalidate DKIM email signatures and affect the authentication of the message. These services can use ARC to provide details of the original authentication before the modifications occurred. Your organization can then trust these details to help authenticate the message.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AtpPolicyForO365.md b/exchange/exchange-ps/ExchangePowerShell/Get-AtpPolicyForO365.md
index 6af619e308..6bc86ea8c5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AtpPolicyForO365.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-AtpPolicyForO365.md
@@ -37,7 +37,7 @@ Safe Documents scans documents and files that are opened in Protected View. For
 
 Safe Attachments for SharePoint, OneDrive, and Microsoft Teams prevents users from opening and downloading files that are identified as malicious. For more information, see [Safe Attachments for SharePoint, OneDrive, and Microsoft Teams](https://learn.microsoft.com/defender-office-365/safe-attachments-for-spo-odfb-teams-about).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AuditLogSearch.md b/exchange/exchange-ps/ExchangePowerShell/Get-AuditLogSearch.md
index eb76ab1d68..36c6b25396 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AuditLogSearch.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-AuditLogSearch.md
@@ -13,7 +13,7 @@ title: Get-AuditLogSearch
 # Get-AuditLogSearch
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-AuditLogSearch cmdlet to return a list of current audit log searches that were created with the New-AdminAuditLogSearch or New-MailboxAuditLogSearch cmdlets. The Get-AuditLogSearch cmdlet also returns audit log searches that are initiated whenever an administrator uses the Exchange admin center (EAC) to export audit logs.
 
@@ -31,9 +31,9 @@ Get-AuditLogSearch [[-Identity] <AuditLogSearchIdParameter>]
 ```
 
 ## DESCRIPTION
-Run the Get-AuditLogSearch cmdlet to return a list of pending audit log searches. If an audit log search has been completed, it won't be displayed in the list of audit log searches.
+Run the Get-AuditLogSearch cmdlet to return a list of pending audit log searches. If an audit log search has completed, it isn't displayed in the list of audit log searches.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AuthConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-AuthConfig.md
index 0274db23b5..2ee2b66f48 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AuthConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-AuthConfig.md
@@ -27,7 +27,7 @@ Get-AuthConfig [-DomainController <Fqdn>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AuthRedirect.md b/exchange/exchange-ps/ExchangePowerShell/Get-AuthRedirect.md
index 51703adc07..392e1c2bf0 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AuthRedirect.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-AuthRedirect.md
@@ -30,7 +30,7 @@ Get-AuthRedirect [[-Identity] <AuthRedirectIdParameter>]
 ## DESCRIPTION
 Exchange 2010 Client Access servers don't support OAuth authentication requests. OAuth redirection objects redirect OAuth authentication requests to Exchange servers that are running later versions of Exchange. This cmdlet is only useful if your organization has Exchange 2010 Client Access servers.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AuthServer.md b/exchange/exchange-ps/ExchangePowerShell/Get-AuthServer.md
index 169457a4a0..1c90a96a4d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AuthServer.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-AuthServer.md
@@ -13,7 +13,7 @@ title: Get-AuthServer
 # Get-AuthServer
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-AuthServer cmdlet to view the settings of authorization servers in the Exchange organization.
 
@@ -30,7 +30,7 @@ Get-AuthServer [[-Identity] <AuthServerIdParameter>]
 ## DESCRIPTION
 An authorization server is a server or service that issues tokens trusted by Microsoft Exchange for access by partner applications.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AuthenticationPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-AuthenticationPolicy.md
index 5c142396b0..a2c52203b4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AuthenticationPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-AuthenticationPolicy.md
@@ -13,7 +13,7 @@ title: Get-AuthenticationPolicy
 # Get-AuthenticationPolicy
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-AuthenticationPolicy cmdlet to view authentication policies in your organization.
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
@@ -28,7 +28,7 @@ Get-AuthenticationPolicy [[-Identity] <AuthPolicyIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AutoSensitivityLabelPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-AutoSensitivityLabelPolicy.md
index 5f3b883571..11abe41196 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AutoSensitivityLabelPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-AutoSensitivityLabelPolicy.md
@@ -91,7 +91,7 @@ Accept wildcard characters: False
 The ForceValidate parameter specifies whether to include details related to the AdminUnits of users, groups, or sites in the policy. Valid values are:
 
 - $true: Various properties in the policy include details of the AdminUnits that are associated with current set of selected users, groups, or sites.
-- $false: The output doesn't contain the information. This is the default value.
+- $false: The output doesn't contain the information. This value is the default.
 
 ```yaml
 Type: Boolean
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AutoSensitivityLabelRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-AutoSensitivityLabelRule.md
index 1c816823d5..4db72e7ae3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AutoSensitivityLabelRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-AutoSensitivityLabelRule.md
@@ -111,7 +111,7 @@ Accept wildcard characters: False
 The IncludeExecutionRuleGuids parameter specifies whether to include the execution rule GUID in the rule details. Valid values are:
 
 - $true: Include the execution rule GUID in the rule details.
-- $false: Don't include the execution rule GUID in the rule details. This is the default value.
+- $false: Don't include the execution rule GUID in the rule details. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -132,7 +132,7 @@ Accept wildcard characters: False
 The IncludeExecutionRuleInformation parameter specifies whether to include the execution rule information in the rule details. Valid values are:
 
 - $true: Include the execution rule information in the rule details.
-- $false: Don't include the execution rule information in the rule details. This is the default value.
+- $false: Don't include the execution rule information in the rule details. This value is the default.
 
 ```yaml
 Type: Boolean
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AutodiscoverVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Get-AutodiscoverVirtualDirectory.md
index e37a13db48..0f05438f81 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AutodiscoverVirtualDirectory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-AutodiscoverVirtualDirectory.md
@@ -40,7 +40,7 @@ Get-AutodiscoverVirtualDirectory [[-Identity] <VirtualDirectoryIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AvailabilityAddressSpace.md b/exchange/exchange-ps/ExchangePowerShell/Get-AvailabilityAddressSpace.md
index ee7c097c2e..7e14d7db02 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AvailabilityAddressSpace.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-AvailabilityAddressSpace.md
@@ -13,7 +13,7 @@ title: Get-AvailabilityAddressSpace
 # Get-AvailabilityAddressSpace
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-AvailabilityAddressSpace cmdlet to view existing availability address space objects that are used to share free/busy data across Exchange organizations.
 
@@ -30,7 +30,7 @@ Get-AvailabilityAddressSpace [[-Identity] <AvailabilityAddressSpaceIdParameter>]
 ## DESCRIPTION
 In on-premises Exchange organizations, you run the Remove-AvailabilityAddressSpace cmdlet on Exchange servers that have the Client Access server role installed.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AvailabilityConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-AvailabilityConfig.md
index 92f1bd5067..30ebc3e5ed 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AvailabilityConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-AvailabilityConfig.md
@@ -13,7 +13,7 @@ title: Get-AvailabilityConfig
 # Get-AvailabilityConfig
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-AvailabilityConfig cmdlet to view information about the sharing of free/busy information between organizations:
 
@@ -31,7 +31,7 @@ Get-AvailabilityConfig [[-Identity] <OrganizationIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AvailabilityReportOutage.md b/exchange/exchange-ps/ExchangePowerShell/Get-AvailabilityReportOutage.md
index 3bcdbbc750..ad2b43f866 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AvailabilityReportOutage.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-AvailabilityReportOutage.md
@@ -30,7 +30,7 @@ Get-AvailabilityReportOutage [[-Identity] <AvailabilityReportOutageIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-BlockedConnector.md b/exchange/exchange-ps/ExchangePowerShell/Get-BlockedConnector.md
index 9004e6d029..11a3f14b28 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-BlockedConnector.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-BlockedConnector.md
@@ -26,7 +26,7 @@ Get-BlockedConnector [-ConnectorId <Guid>] [<CommonParameters>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-BlockedSenderAddress.md b/exchange/exchange-ps/ExchangePowerShell/Get-BlockedSenderAddress.md
index 92c889fdec..3516ff3e4f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-BlockedSenderAddress.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-BlockedSenderAddress.md
@@ -15,7 +15,7 @@ title: Get-BlockedSenderAddress
 ## SYNOPSIS
 This cmdlet is available only in the cloud-based service.
 
-Use the Get-BlockedSenderAddress cmdlet to view users in your Microsoft 365 organization that are impacted by the protection system. These users sent multiple messages that were classified as spam, so they're blocked from sending messages.
+Use the Get-BlockedSenderAddress cmdlet to view users in your Microsoft 365 organization that are affected by the protection system. These users sent multiple messages that were classified as spam, so they're blocked from sending messages.
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
@@ -27,7 +27,7 @@ Get-BlockedSenderAddress [-SenderAddress <SmtpAddress>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-CASMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Get-CASMailbox.md
index a742383485..ed3b0f3a22 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-CASMailbox.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-CASMailbox.md
@@ -13,7 +13,7 @@ title: Get-CASMailbox
 # Get-CASMailbox
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-CASMailbox cmdlet to view the Client Access settings that are configured on mailboxes.
 
@@ -66,7 +66,7 @@ Get-CASMailbox [[-Identity] <MailboxIdParameter>]
 ## DESCRIPTION
 This cmdlet returns a variety of client access settings for one or more mailboxes. These settings include options for Outlook on the web, Exchange ActiveSync, POP3, and IMAP4.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-CASMailboxPlan.md b/exchange/exchange-ps/ExchangePowerShell/Get-CASMailboxPlan.md
index 6f9a965d48..c59d301409 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-CASMailboxPlan.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-CASMailboxPlan.md
@@ -35,7 +35,7 @@ Get-CASMailboxPlan [[-Identity] <MailboxPlanIdParameter>]
 ## DESCRIPTION
 A CAS mailbox plan is tied to the corresponding mailbox plan that has the same name (and display name). Like mailbox plans, CAS mailbox plans correspond to license types, and are applied to a mailbox when you license the user. The availability of a CAS mailbox plan is determined by your selections when you enroll in the service and the age of your organization.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-CalendarDiagnosticAnalysis.md b/exchange/exchange-ps/ExchangePowerShell/Get-CalendarDiagnosticAnalysis.md
index ed3b0dc62d..0c08a5c78b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-CalendarDiagnosticAnalysis.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-CalendarDiagnosticAnalysis.md
@@ -60,7 +60,7 @@ The following properties of the calendar item are returned in the default output
 - SenderEmailAddress
 - SentRepresentingDisplayName
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -155,7 +155,7 @@ Accept wildcard characters: False
 
 The DetailLevel parameter specifies the level of detail you want to see in the analysis output. Valid values are:
 
-- Basic: This is the default value. The calendar item properties that are returned are listed in the Detailed Description.
+- Basic: This value is the default. The calendar item properties that are returned are listed in the Detailed Description.
 - Advanced: 37 additional calendar item properties are returned. You should use this value only for detailed debugging information.
 
 ```yaml
@@ -196,7 +196,7 @@ Accept wildcard characters: False
 
 The OutputAs parameter specifies the output format of the command. Valid values are:
 
-- CSV (This is the default value)
+- CSV (default value)
 - HTML
 - XML
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-CalendarDiagnosticLog.md b/exchange/exchange-ps/ExchangePowerShell/Get-CalendarDiagnosticLog.md
index 5de9699698..5e3f48c881 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-CalendarDiagnosticLog.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-CalendarDiagnosticLog.md
@@ -65,7 +65,7 @@ Get-CalendarDiagnosticLog [-Identity] <MailboxIdParameter> -LogLocation <String>
 ## DESCRIPTION
 The output of this cmdlet contains the following information:
 
-- IsFileLink: Indicates whether the calendar item has been exported to a .msg file by using the LogLocation parameter. Values are True or False.
+- IsFileLink: Indicates whether the calendar item is exported to a .msg file by using the LogLocation parameter. Values are True or False.
 - Identity: Identifies the mailbox that holds the calendar item. An example value is: excallog://laura@contoso.com/?id=RgAAAACF/h/dHTTkQbdPrk7z+G4SBwCoatc7EmnEQq1iF35p17stAAAAAAFEAACoatc7EmnEQq1iF35p17stAAAAABEIAAAP.
 - LogDate: The date-time that the calendar item was logged.
 - NormalizedSubject: The Subject field of the calendar item.
@@ -73,7 +73,7 @@ The output of this cmdlet contains the following information:
 
 After you run the Get-CalendarDiagnosticLog cmdlet, you can analyze the calendar data using the Get-CalendarDiagnosticAnalysis cmdlet. For more information, see [Get-CalendarDiagnosticAnalysis](https://learn.microsoft.com/powershell/module/exchangepowershell/get-calendardiagnosticanalysis).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -299,9 +299,9 @@ Accept wildcard characters: False
 The ExactMatch parameter specifies whether to use an exact match or a partial match for text values that you specify for the Subject parameter. Valid values are:
 
 - $true: The subject search uses an exact match and searches all calendar items in the mailbox. For example, if you search for "budget", the search looks for items that have "budget" anywhere in the subject, but not "budgeting".
-- $false: The subject search uses a partial match and searches a maximum of 1000 calendar items in the mailbox. For example, if you search for "budget", the search looks for items that have "budget" and "budgeting" anywhere in the subject. This is the default value.
+- $false: The subject search uses a partial match and searches a maximum of 1000 calendar items in the mailbox. For example, if you search for "budget", the search looks for items that have "budget" and "budgeting" anywhere in the subject. This value is the default.
 
-A partial subject match search may not return all of the relevant calendar items. Try using an exact subject match search for more accurate results.
+A partial subject match search might not return all of the relevant calendar items. Try using an exact subject match search for more accurate results.
 
 You only use this parameter with the Subject parameter.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-CalendarDiagnosticObjects.md b/exchange/exchange-ps/ExchangePowerShell/Get-CalendarDiagnosticObjects.md
index 27ba38654a..c9e9fb38fb 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-CalendarDiagnosticObjects.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-CalendarDiagnosticObjects.md
@@ -49,7 +49,7 @@ Get-CalendarDiagnosticObjects [-Identity] <UnifiedGroupOrUserMailboxIdParameter>
 ## DESCRIPTION
 Some of the more interesting properties that are returned in the results are:
 
-- AppointmentState: 1 = The appointment is a meeting, 2 = The appointment has been received, 4 = The appointment has been cancelled, and 8 = the appointment is a forwarded appointment.
+- AppointmentState: 1 = The appointment is a meeting, 2 = The appointment is received, 4 = The appointment is cancelled, and 8 = the appointment is a forwarded appointment.
 - CalendarLogTriggerAction: The action that's taken on the item (for example, Create or Update).
 - ClientInfoString: The entity that made the change (for example, `Client=OWA;<AdditionalDetails>`, `Client=WebServices;<AdditionalDetails>`;, or `Client=TBA;Service=MSExchangeMailboxAssistants;Action=ELCAssistant;`).
 - MeetingRequestType: 1 = The meeting message is a meeting request, 65536 = The meeting message is a full update to an existing meeting, 131072 = The meeting message is an informational update to an existing meeting, 262144 = The meeting message is a silent update, 524288 = The update is outdated, or 1048576 = The meeting message is forwarded to a delegate, and the copy is marked as informational.
@@ -57,7 +57,7 @@ Some of the more interesting properties that are returned in the results are:
 - ResponseType: 0 = The organizer hasn't received a response, 1 = The organizer's copy of the meeting, 2 = Tentative, 3 = Accept, 4 = Decline, or 5 = The attendee hasn't responded.
 - ResponsibleUserName: The LegacyExchangeDN value of the user who made the change (for example, `/o=ExchangeLabs/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=BN6PR11MB1587/cn=Microsoft System Attendant` or `/o=ExchangeLabs/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=696eea97d3c449eab648920d03385efb-admin`).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -259,9 +259,9 @@ Accept wildcard characters: False
 The ExactMatch parameter specifies whether to use an exact match or a partial match for text values that you specify for the Subject parameter. Valid values are:
 
 - $true: The subject search uses an exact match and searches all calendar items in the mailbox. For example, if you search for "budget", the search looks for items that have "budget" anywhere in the subject, but not "budgeting".
-- $false: The subject search uses a partial match and searches a maximum of 1000 calendar items in the mailbox. For example, if you search for "budget", the search looks for items that have "budget" and "budgeting" anywhere in the subject. This is the default value.
+- $false: The subject search uses a partial match and searches a maximum of 1000 calendar items in the mailbox. For example, if you search for "budget", the search looks for items that have "budget" and "budgeting" anywhere in the subject. This value is the default.
 
-A partial subject match search may not return all of the relevant calendar items. Try using an exact subject match search for more accurate results.
+A partial subject match search might not return all of the relevant calendar items. Try using an exact subject match search for more accurate results.
 
 You only use this parameter with the Subject parameter.
 
@@ -394,7 +394,7 @@ Accept wildcard characters: False
 The ShouldBindToItem parameter specifies whether to truncate large streamable property values (for example, AppointmentRecurrenceBlob). Valid values are:
 
 - $true: The values of large streamable properties aren't truncated, so the full value is returned.
-- $false: The values of large streamable properties are truncated. This is the default value.
+- $false: The values of large streamable properties are truncated. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -451,7 +451,7 @@ Accept wildcard characters: False
 The ShouldFetchRecurrenceExceptions parameter specifies whether to include exceptions to recurring meetings. Valid values are:
 
 - $true: Include exceptions to recurring meetings. When you use this value, you also need to use the ItemIds parameter.
-- $false: Don't Include exceptions to recurring meetings. This is the default value.
+- $false: Don't Include exceptions to recurring meetings. This value is the default.
 
 ```yaml
 Type: Boolean
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-CalendarNotification.md b/exchange/exchange-ps/ExchangePowerShell/Get-CalendarNotification.md
index 1f56a01412..03e6c54481 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-CalendarNotification.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-CalendarNotification.md
@@ -17,7 +17,7 @@ This cmdlet is available only in on-premises Exchange.
 
 Use the Get-CalendarNotification cmdlet to view calendar text message notification settings for a mailbox.
 
-**Note**: This cmdlet has been deprecated in Exchange Online PowerShell. The text message notification service has been discontinued in Microsoft 365.
+**Note**: This cmdlet is deprecated in Exchange Online PowerShell. The text message notification service is discontinued in Microsoft 365.
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
@@ -35,7 +35,7 @@ Get-CalendarNotification [-Identity] <MailboxIdParameter>
 ## DESCRIPTION
 The Get-CalendarNotification cmdlet retrieves and displays the rules that trigger the calendar agenda notification, reminder notification, or update notification text messages.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-CalendarProcessing.md b/exchange/exchange-ps/ExchangePowerShell/Get-CalendarProcessing.md
index 87199882e2..232212d73f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-CalendarProcessing.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-CalendarProcessing.md
@@ -13,9 +13,9 @@ title: Get-CalendarProcessing
 # Get-CalendarProcessing
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
-Use the Get-CalendarProcessing cmdlet to view the calendar processing options for resource mailboxes, which include the Calendar Attendant, resource booking assistant and calendar configuration. Note that the settings returned by this cmdlet are editable only on resource mailboxes.
+Use the Get-CalendarProcessing cmdlet to view the calendar processing options for resource mailboxes, which include the Calendar Attendant, resource booking assistant and calendar configuration. The settings returned by this cmdlet are editable only on resource mailboxes.
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
@@ -32,7 +32,7 @@ Get-CalendarProcessing [-Identity] <MailboxIdParameter>
 ## DESCRIPTION
 For details about the properties that are returned in the output of this cmdlet, see [Set-CalendarProcessing](https://learn.microsoft.com/powershell/module/exchangepowershell/set-calendarprocessing).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-CaseHoldPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-CaseHoldPolicy.md
index 6f2f8b1488..e1c850af72 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-CaseHoldPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-CaseHoldPolicy.md
@@ -102,7 +102,7 @@ Accept wildcard characters: False
 
 The DistributionDetail switch returns detailed policy distribution information on the case hold policy. You don't need to specify a value with this switch.
 
-If you don't use this switch, the command won't return information about the current deployment status, and the DistributionStatus property will only show as "Pending".
+If you don't use this switch, the command doesn't return information about the current deployment status, and the DistributionStatus property shows as "Pending".
 
 The following properties are affected by this switch:
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ClassificationRuleCollection.md b/exchange/exchange-ps/ExchangePowerShell/Get-ClassificationRuleCollection.md
index eb41942aba..63acdf54d9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ClassificationRuleCollection.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ClassificationRuleCollection.md
@@ -13,7 +13,7 @@ title: Get-ClassificationRuleCollection
 # Get-ClassificationRuleCollection
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-ClassificationRuleCollection cmdlet to view the classification rule collections in your organization.
 
@@ -30,7 +30,7 @@ Get-ClassificationRuleCollection [[-Identity] <ClassificationRuleCollectionIdPar
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessArray.md b/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessArray.md
index 61d0861444..3b220ee5f6 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessArray.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessArray.md
@@ -36,7 +36,7 @@ Changes in the Exchange server architecture that were introduced in Exchange Ser
 - Outlook clients can't use RPC over TCP to access mailboxes on Exchange Server 2013 or later versions and RPC Client Access arrays only work with RPC over TCP.
 - Because the Client Access server role is now a stateless proxy, you use different and less complex methods to configure load balancing and high availability for internal and external client connections. For more information, see [Load balancing in Exchange Server](https://learn.microsoft.com/Exchange/architecture/client-access/load-balancing).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessRule.md
index ce2deaa5e2..57eb9b41ff 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessRule.md
@@ -16,7 +16,7 @@ title: Get-ClientAccessRule
 > [!NOTE]
 > Beginning in October 2022, client access rules were deprecated for all Exchange Online organizations that weren't using them. Client access rules will be deprecated for all remaining organizations on September 1, 2025. If you choose to turn off client access rules before the deadline, the feature will be disabled in your organization. For more information, see [Update on Client Access Rules Deprecation in Exchange Online](https://techcommunity.microsoft.com/blog/exchange/update-on-client-access-rules-deprecation-in-exchange-online/4354809).
 
-This cmdlet is functional only in Exchange Server 2019 and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is functional only in Exchange Server 2019 and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-ClientAccessRule cmdlet to view client access rules. Client access rules help you control access to your cloud-based organization based on the properties of the connection.
 
@@ -35,7 +35,7 @@ Get-ClientAccessRule [[-Identity] <ClientAccessRuleIdParameter>]
 ## DESCRIPTION
 Client access rules are like mail flow rules (also known as transport rules) for client connections to your organization. You use conditions and exceptions to identify the connections based on their properties, and actions that allow or block the connections.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessServer.md b/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessServer.md
index ae619fa9f7..3fff1f85e2 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessServer.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessServer.md
@@ -32,7 +32,7 @@ Get-ClientAccessServer [[-Identity] <ClientAccessServerIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessService.md b/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessService.md
index 75380355de..fa35e4a5fc 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessService.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessService.md
@@ -30,7 +30,7 @@ Get-ClientAccessService [[-Identity] <ClientAccessServerIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-Clutter.md b/exchange/exchange-ps/ExchangePowerShell/Get-Clutter.md
index 7ecfb68037..ef6f60312c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-Clutter.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-Clutter.md
@@ -28,7 +28,7 @@ Get-Clutter -Identity <MailboxIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-CmdletExtensionAgent.md b/exchange/exchange-ps/ExchangePowerShell/Get-CmdletExtensionAgent.md
index bf76f861a0..ee03554a60 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-CmdletExtensionAgent.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-CmdletExtensionAgent.md
@@ -39,7 +39,7 @@ Get-CmdletExtensionAgent [[-Identity] <CmdletExtensionAgentIdParameter>]
 ## DESCRIPTION
 Cmdlet extension agents are used by Exchange cmdlets in Exchange Server 2010 and later. Cmdlets provided by other Microsoft or non-Microsoft products can't use cmdlet extension agents.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 

From c88b802425e0d51022c33afecd043456a8fd24fc Mon Sep 17 00:00:00 2001
From: Chris Davis <chris.davis@microsoft.com>
Date: Tue, 5 Aug 2025 17:47:48 -0700
Subject: [PATCH 075/145] Acrolinx 2

---
 .../exchange-ps/ExchangePowerShell/Get-ComplianceCase.md  | 2 +-
 .../Get-ComplianceRetentionEventType.md                   | 4 ++--
 .../ExchangePowerShell/Get-ComplianceSearch.md            | 4 ++--
 .../ExchangePowerShell/Get-ComplianceSearchAction.md      | 4 ++--
 .../Get-CompromisedUserAggregateReport.md                 | 2 +-
 .../ExchangePowerShell/Get-CompromisedUserDetailReport.md | 2 +-
 .../Get-ConfigAnalyzerPolicyRecommendation.md             | 6 +++---
 exchange/exchange-ps/ExchangePowerShell/Get-Contact.md    | 4 ++--
 .../ExchangePowerShell/Get-ContentFilterConfig.md         | 2 +-
 .../ExchangePowerShell/Get-ContentFilterPhrase.md         | 2 +-
 .../Get-ContentMalwareMdoAggregateReport.md               | 2 +-
 .../Get-ContentMalwareMdoDetailReport.md                  | 2 +-
 .../ExchangePowerShell/Get-DataClassification.md          | 4 ++--
 .../ExchangePowerShell/Get-DataClassificationConfig.md    | 2 +-
 .../ExchangePowerShell/Get-DataEncryptionPolicy.md        | 2 +-
 .../ExchangePowerShell/Get-DatabaseAvailabilityGroup.md   | 2 +-
 .../Get-DatabaseAvailabilityGroupNetwork.md               | 2 +-
 .../ExchangePowerShell/Get-DeliveryAgentConnector.md      | 2 +-
 .../exchange-ps/ExchangePowerShell/Get-DetailZapReport.md | 2 +-
 .../exchange-ps/ExchangePowerShell/Get-DetailsTemplate.md | 2 +-
 .../ExchangePowerShell/Get-DistributionGroup.md           | 4 ++--
 .../ExchangePowerShell/Get-DistributionGroupMember.md     | 6 +++---
 .../ExchangePowerShell/Get-DkimSigningConfig.md           | 2 +-
 .../exchange-ps/ExchangePowerShell/Get-DlpDetailReport.md | 4 ++--
 .../ExchangePowerShell/Get-DlpDetectionsReport.md         | 2 +-
 .../ExchangePowerShell/Get-DlpIncidentDetailReport.md     | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Get-DlpPolicy.md  | 4 ++--
 .../ExchangePowerShell/Get-DlpPolicyTemplate.md           | 4 ++--
 .../Get-DnssecStatusForVerifiedDomain.md                  | 2 +-
 .../ExchangePowerShell/Get-DomainController.md            | 2 +-
 .../ExchangePowerShell/Get-DynamicDistributionGroup.md    | 4 ++--
 .../Get-DynamicDistributionGroupMember.md                 | 2 +-
 .../ExchangePowerShell/Get-EOPProtectionPolicyRule.md     | 2 +-
 .../ExchangePowerShell/Get-EXOMailboxFolderPermission.md  | 4 ++--
 .../ExchangePowerShell/Get-EXOMailboxPermission.md        | 2 +-
 .../exchange-ps/ExchangePowerShell/Get-EXORecipient.md    | 2 +-
 .../ExchangePowerShell/Get-EXORecipientPermission.md      | 2 +-
 .../ExchangePowerShell/Get-EcpVirtualDirectory.md         | 2 +-
 .../ExchangePowerShell/Get-EdgeSubscription.md            | 2 +-
 .../ExchangePowerShell/Get-EdgeSyncServiceConfig.md       | 2 +-
 .../Get-EligibleDistributionGroupForMigration.md          | 2 +-
 .../ExchangePowerShell/Get-EmailAddressPolicy.md          | 4 ++--
 .../ExchangePowerShell/Get-EmailTenantSettings.md         | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Get-EtrLimits.md  | 2 +-
 .../exchange-ps/ExchangePowerShell/Get-EventLogLevel.md   | 2 +-
 .../Get-EventsFromEmailConfiguration.md                   | 2 +-
 .../ExchangePowerShell/Get-ExchangeAssistanceConfig.md    | 2 +-
 .../ExchangePowerShell/Get-ExchangeCertificate.md         | 8 ++++----
 .../ExchangePowerShell/Get-ExchangeDiagnosticInfo.md      | 2 +-
 .../exchange-ps/ExchangePowerShell/Get-ExchangeFeature.md | 2 +-
 .../exchange-ps/ExchangePowerShell/Get-ExchangeServer.md  | 2 +-
 .../ExchangePowerShell/Get-ExchangeServerAccessLicense.md | 2 +-
 .../Get-ExchangeServerAccessLicenseUser.md                | 2 +-
 .../ExchangePowerShell/Get-ExchangeSettings.md            | 2 +-
 .../ExchangePowerShell/Get-ExoInformationBarrierPolicy.md | 2 +-
 .../Get-ExoInformationBarrierRelationship.md              | 2 +-
 .../Get-ExoInformationBarrierSegment.md                   | 2 +-
 .../ExchangePowerShell/Get-ExoPhishSimOverrideRule.md     | 2 +-
 .../ExchangePowerShell/Get-ExoSecOpsOverrideRule.md       | 2 +-
 .../ExchangePowerShell/Get-ExternalInOutlook.md           | 2 +-
 .../ExchangePowerShell/Get-FailedContentIndexDocuments.md | 2 +-
 .../ExchangePowerShell/Get-FederatedDomainProof.md        | 2 +-
 .../Get-FederatedOrganizationIdentifier.md                | 4 ++--
 .../ExchangePowerShell/Get-FederationInformation.md       | 4 ++--
 .../exchange-ps/ExchangePowerShell/Get-FederationTrust.md | 4 ++--
 .../exchange-ps/ExchangePowerShell/Get-FocusedInbox.md    | 2 +-
 .../ExchangePowerShell/Get-ForeignConnector.md            | 2 +-
 .../ExchangePowerShell/Get-FrontendTransportService.md    | 2 +-
 .../ExchangePowerShell/Get-GlobalAddressList.md           | 4 ++--
 .../ExchangePowerShell/Get-GlobalMonitoringOverride.md    | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Get-Group.md      | 4 ++--
 .../exchange-ps/ExchangePowerShell/Get-HealthReport.md    | 2 +-
 .../ExchangePowerShell/Get-HistoricalSearch.md            | 2 +-
 .../ExchangePowerShell/Get-HoldCompliancePolicy.md        | 2 +-
 .../ExchangePowerShell/Get-HoldComplianceRule.md          | 2 +-
 .../Get-HostedConnectionFilterPolicy.md                   | 2 +-
 .../ExchangePowerShell/Get-HostedContentFilterPolicy.md   | 2 +-
 .../ExchangePowerShell/Get-HostedContentFilterRule.md     | 2 +-
 .../Get-HostedOutboundSpamFilterPolicy.md                 | 2 +-
 .../Get-HostedOutboundSpamFilterRule.md                   | 2 +-
 .../ExchangePowerShell/Get-HybridConfiguration.md         | 2 +-
 .../ExchangePowerShell/Get-HybridMailflowDatacenterIPs.md | 6 +++---
 .../ExchangePowerShell/Get-IPv6StatusForAcceptedDomain.md | 2 +-
 .../ExchangePowerShell/Get-IRMConfiguration.md            | 4 ++--
 .../exchange-ps/ExchangePowerShell/Get-ImapSettings.md    | 2 +-
 .../ExchangePowerShell/Get-InboundConnector.md            | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Get-InboxRule.md  | 4 ++--
 .../Get-IntraOrganizationConfiguration.md                 | 6 +++---
 .../ExchangePowerShell/Get-IntraOrganizationConnector.md  | 4 ++--
 .../exchange-ps/ExchangePowerShell/Get-JournalRule.md     | 4 ++--
 exchange/exchange-ps/ExchangePowerShell/Get-LinkedUser.md | 2 +-
 .../exchange-ps/ExchangePowerShell/Get-LogonStatistics.md | 6 +++---
 .../Get-M365DataAtRestEncryptionPolicy.md                 | 2 +-
 .../Get-M365DataAtRestEncryptionPolicyAssignment.md       | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Get-Mailbox.md    | 6 +++---
 95 files changed, 131 insertions(+), 131 deletions(-)

diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceCase.md b/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceCase.md
index d0e22b0d1d..b28065f954 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceCase.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceCase.md
@@ -97,7 +97,7 @@ The CaseType parameter specifies the type of compliance case that you want to vi
 - ComplianceWorkspace: This value is reserved for internal Microsoft use.
 - DataInvestigation: Data investigation cases are used to investigate data spillage incidents. In the Microsoft Purview compliance portal, Data investigation cases are displayed on the **Data investigations** page.
 - DSR: Data Subject Request (DSR) cases are used to manage General Data Protection Regulation (GDPR) DSR investigations. In the Microsoft Purview compliance portal, DSR cases are displayed under **Data privacy** \> **Data subject requests**.
-- eDiscovery: eDiscovery (also called eDiscovery Standard) cases are used to manage legal or other types of investigations. In the Microsoft Purview compliance portal, eDiscovery Standard cases are displayed under **eDiscovery** \> **Standard**. This is the default value.
+- eDiscovery: eDiscovery (also called eDiscovery Standard) cases are used to manage legal or other types of investigations. In the Microsoft Purview compliance portal, eDiscovery Standard cases are displayed under **eDiscovery** \> **Standard**. This value is the default.
 - InsiderRisk: Insider risk cases are used to manage insider risk management cases. In the Microsoft Purview compliance portal, insider risk cases are displayed under **Insider risk management** \> **Cases**. Typically, insider risk management cases are manually created in the Microsoft Purview compliance portal to further investigate activity based on a risk alert.
 - InternalInvestigation: This value is reserved for internal Microsoft use.
 - SupervisionPolicy: This type of case corresponds to communication compliance policy. In the Microsoft Purview compliance portal, communication compliance policies are displayed under **Communication compliance** \> **Policies**.
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceRetentionEventType.md b/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceRetentionEventType.md
index eaa1c7f19c..29c6be59fc 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceRetentionEventType.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceRetentionEventType.md
@@ -28,7 +28,7 @@ Get-ComplianceRetentionEventType [-Identity <ComplianceRuleIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -76,7 +76,7 @@ Accept wildcard characters: False
 
 The LoadTag switch specifies whether to show the compliance tags that are associated with the retention event types. You don't need to specify a value with this switch.
 
-If you don't use this switch, the ComplianceTag property will always appear empty in the results.
+If you don't use this switch, the ComplianceTag property always appears empty in the results.
 
 ```yaml
 Type: SwitchParameter
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceSearch.md b/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceSearch.md
index 92d5c4ff7f..877553b037 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceSearch.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceSearch.md
@@ -13,7 +13,7 @@ title: Get-ComplianceSearch
 # Get-ComplianceSearch
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-ComplianceSearch cmdlet to view estimate compliance searches in Exchange Server 2016 or later and in the Microsoft Purview compliance portal. After you use the New-ComplianceSearchAction cmdlet to define a preview action for the compliance search, use the Get-ComplianceSearchAction cmdlet to view the results of the compliance search.
 
@@ -30,7 +30,7 @@ Get-ComplianceSearch [[-Identity] <ComplianceSearchIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 In on-premises Exchange, this cmdlet is available in the Mailbox Search role. By default, this role is assigned only to the Discovery Management role group.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceSearchAction.md b/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceSearchAction.md
index bb1a32696a..ada10e2ac6 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceSearchAction.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceSearchAction.md
@@ -13,7 +13,7 @@ title: Get-ComplianceSearchAction
 # Get-ComplianceSearchAction
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-ComplianceSearchAction cmdlet to view information about compliance search actions.
 
@@ -72,7 +72,7 @@ Get-ComplianceSearchAction [-Export]
 ## DESCRIPTION
 After you create and run a compliance search using the New-ComplianceSearch cmdlet, and start the search using the Start-ComplianceSearch cmdlet, you assign a search action using the New-ComplianceSearchAction cmdlet. You use the Get-ComplianceSearchAction cmdlet to track the progress of the compliance search action.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 In on-premises Exchange, this cmdlet is available in the Mailbox Search role. By default, this role is assigned only to the Discovery Management role group.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-CompromisedUserAggregateReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-CompromisedUserAggregateReport.md
index 5f7e8ed48b..e45a462bc6 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-CompromisedUserAggregateReport.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-CompromisedUserAggregateReport.md
@@ -38,7 +38,7 @@ This cmdlet returns the following information:
 - UserCount
 - Action
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-CompromisedUserDetailReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-CompromisedUserDetailReport.md
index 5b8fba0918..fb13f0365e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-CompromisedUserDetailReport.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-CompromisedUserDetailReport.md
@@ -38,7 +38,7 @@ This cmdlet returns the following information:
 - UserCount
 - Action
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ConfigAnalyzerPolicyRecommendation.md b/exchange/exchange-ps/ExchangePowerShell/Get-ConfigAnalyzerPolicyRecommendation.md
index 3d946278f6..4b369acf50 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ConfigAnalyzerPolicyRecommendation.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ConfigAnalyzerPolicyRecommendation.md
@@ -35,11 +35,11 @@ The output of this cmdlet only returns settings that fall below the value that y
 
 The output contains the following information for each setting:
 
-- PolicyGroup: The type of policy. The value will be Anti-Spam, Anti-Phishing, Anti-Malware, ATP Safe Links, or ATP Safe Attachments
+- PolicyGroup: The type of policy. The value is Anti-Spam, Anti-Phishing, Anti-Malware, ATP Safe Links, or ATP Safe Attachments
 - SettingName: The name of the setting in the policy.
 - SettingNameDescription: A description of the setting.
 - Policy: The name of the policy.
-- AppliedTo: The number of users or domains that the policy applies to. If the policy isn't applied to anyone (for example, it's disabled), this value will be blank.
+- AppliedTo: The number of users or domains that the policy applies to. If the policy isn't applied to anyone (for example, it's disabled), this value is blank.
 - CurrentConfiguration: The current value of the setting.
 - LastModified: When the policy was last modified.
 - Recommendation: The recommended Standard or Strict value for the setting.
@@ -49,7 +49,7 @@ If a setting is configured at or better than the Standard or Strict protection p
 
 This cmdlet returns the following output for each setting in each policy that falls below the recommended value.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-Contact.md b/exchange/exchange-ps/ExchangePowerShell/Get-Contact.md
index 1fc5354a8a..5a6584b210 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-Contact.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-Contact.md
@@ -13,7 +13,7 @@ title: Get-Contact
 # Get-Contact
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-Contact cmdlet to view existing contact objects in your organization. This cmdlet returns contacts and mail contacts.
 
@@ -52,7 +52,7 @@ Get-Contact [[-Identity] <ContactIdParameter>]
 ## DESCRIPTION
 The Get-Contact cmdlet returns no mail-related properties for mail contacts. Use the Get-MailContact to view mail-related properties for mail contacts.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ContentFilterConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-ContentFilterConfig.md
index 6a8e1dbce8..12081057e7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ContentFilterConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ContentFilterConfig.md
@@ -27,7 +27,7 @@ Get-ContentFilterConfig [-DomainController <Fqdn>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ContentFilterPhrase.md b/exchange/exchange-ps/ExchangePowerShell/Get-ContentFilterPhrase.md
index 9b20ec8f22..8c0a7405f0 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ContentFilterPhrase.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ContentFilterPhrase.md
@@ -36,7 +36,7 @@ Get-ContentFilterPhrase [-Phrase <ContentFilterPhraseIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ContentMalwareMdoAggregateReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-ContentMalwareMdoAggregateReport.md
index 0769430b82..79a807688f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ContentMalwareMdoAggregateReport.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ContentMalwareMdoAggregateReport.md
@@ -42,7 +42,7 @@ For the specified reporting period, the cmdlet returns the following information
 
 By default, the command returns data for the last 14 days. Data for the last 90 days is available.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ContentMalwareMdoDetailReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-ContentMalwareMdoDetailReport.md
index ce69c30ab3..8e7f403dd9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ContentMalwareMdoDetailReport.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ContentMalwareMdoDetailReport.md
@@ -44,7 +44,7 @@ For the specified reporting period, the cmdlet returns the following information
 
 By default, the command returns data for the last 14 days. Data for the last 30 days is available.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DataClassification.md b/exchange/exchange-ps/ExchangePowerShell/Get-DataClassification.md
index 271b48a173..c1e5e1cbaf 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DataClassification.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-DataClassification.md
@@ -15,7 +15,7 @@ title: Get-DataClassification
 ## SYNOPSIS
 This cmdlet is functional only in on-premises Exchange.
 
-In Exchange Online, this cmdlet has been replaced by the [Get-DlpSensitiveInformationType](https://learn.microsoft.com/powershell/module/exchangepowershell/get-dlpsensitiveinformationtype) cmdlet in Security & Compliance PowerShell.
+In Exchange Online, this cmdlet is replaced by the [Get-DlpSensitiveInformationType](https://learn.microsoft.com/powershell/module/exchangepowershell/get-dlpsensitiveinformationtype) cmdlet in Security & Compliance PowerShell.
 
 Use the Get-DataClassification cmdlet to view the data classification rules in your organization. This cmdlet shows built-in data classification rules and rules that you created that use document fingerprints.
 
@@ -40,7 +40,7 @@ Get-DataClassification [[-Identity] <DataClassificationIdParameter>]
 ## DESCRIPTION
 Classification rule packages are used by data loss prevention (DLP) to detect sensitive content in messages.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DataClassificationConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-DataClassificationConfig.md
index 39e8fca684..7d40e138f2 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DataClassificationConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-DataClassificationConfig.md
@@ -26,7 +26,7 @@ Get-DataClassificationConfig [<CommonParameters>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DataEncryptionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-DataEncryptionPolicy.md
index e21fd13b90..a1d0a13841 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DataEncryptionPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-DataEncryptionPolicy.md
@@ -34,7 +34,7 @@ Data encryption policy cmdlets are the Exchange Online part of Customer Key. For
 
 You can assign a data encryption policy to a mailbox by using the DataEncryptionPolicy parameter on the Set-Mailbox cmdlet in Exchange Online PowerShell.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DatabaseAvailabilityGroup.md b/exchange/exchange-ps/ExchangePowerShell/Get-DatabaseAvailabilityGroup.md
index 4077072041..b26d54636a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DatabaseAvailabilityGroup.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-DatabaseAvailabilityGroup.md
@@ -39,7 +39,7 @@ In addition to obtaining a list of DAG members, the Get-DatabaseAvailabilityGrou
 
 Use the Status parameter with the command to include the values for these listed properties. Without the Status parameter, the values returned for these properties are blank.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DatabaseAvailabilityGroupNetwork.md b/exchange/exchange-ps/ExchangePowerShell/Get-DatabaseAvailabilityGroupNetwork.md
index 20964115f3..659b7a2920 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DatabaseAvailabilityGroupNetwork.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-DatabaseAvailabilityGroupNetwork.md
@@ -48,7 +48,7 @@ Valid states for network interfaces
 - Unavailable: The network interface isn't enabled for replication or use by the DAG, or the DAG member associated with this network interface is inactive or unavailable.The network interface isn't enabled for replication or use by the DAG, or the DAG member associated with this network interface is inactive or unavailable.
 - Unknown: The system was unable to determine the state of the network interface.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DeliveryAgentConnector.md b/exchange/exchange-ps/ExchangePowerShell/Get-DeliveryAgentConnector.md
index 5fe36fb545..158918e113 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DeliveryAgentConnector.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-DeliveryAgentConnector.md
@@ -30,7 +30,7 @@ Get-DeliveryAgentConnector [[-Identity] <DeliveryAgentConnectorIdParameter>]
 ## DESCRIPTION
 Delivery agent connectors are used to route messages addressed to foreign systems that don't use the SMTP protocol. When a message is routed to a delivery agent connector, the associated delivery agent performs the content conversion and message delivery. Delivery agent connectors allow queue management of foreign connectors, thereby eliminating the need for storing messages on the file system in Drop and Pickup directories. For more information, see [Delivery agents and Delivery Agent connectors](https://learn.microsoft.com/exchange/delivery-agents-and-delivery-agent-connectors-exchange-2013-help).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DetailZapReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-DetailZapReport.md
index 0c93ed0d8a..259eb9844a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DetailZapReport.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-DetailZapReport.md
@@ -48,7 +48,7 @@ If you append the command with ` | Format-List`, the following additional inform
 - Delivery Status
 - Detection Technology
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DetailsTemplate.md b/exchange/exchange-ps/ExchangePowerShell/Get-DetailsTemplate.md
index f04bcdd675..ba5338a4a8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DetailsTemplate.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-DetailsTemplate.md
@@ -32,7 +32,7 @@ Get-DetailsTemplate [[-Identity] <DetailsTemplateIdParameter>]
 ## DESCRIPTION
 The Get-DetailsTemplate cmdlet retrieves the attributes for one or more details templates. Wildcard characters can be used when specifying the type and language of the details templates.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DistributionGroup.md b/exchange/exchange-ps/ExchangePowerShell/Get-DistributionGroup.md
index 5603596725..19775f1e8f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DistributionGroup.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-DistributionGroup.md
@@ -13,7 +13,7 @@ title: Get-DistributionGroup
 # Get-DistributionGroup
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-DistributionGroup cmdlet to view existing distribution groups or mail-enabled security groups. To view the members of a group, use the Get-DistributionGroupMember cmdlet.
 
@@ -85,7 +85,7 @@ Get-DistributionGroup [-Credential <PSCredential>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DistributionGroupMember.md b/exchange/exchange-ps/ExchangePowerShell/Get-DistributionGroupMember.md
index 1d9b8bb4fd..9bd3ff56a4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DistributionGroupMember.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-DistributionGroupMember.md
@@ -13,7 +13,7 @@ title: Get-DistributionGroupMember
 # Get-DistributionGroupMember
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-DistributionGroupMember cmdlet to view the members of distribution groups and mail-enabled security groups.
 
@@ -33,9 +33,9 @@ Get-DistributionGroupMember [-Identity] <DistributionGroupMemberIdParameter>
 ```
 
 ## DESCRIPTION
-If your organization has multiple Active Directory domains, you may need to run the Set-ADServerSettings cmdlet with the ViewEntireForest parameter set to $true before running the Get-DistributionGroupMember cmdlet to view the entire forest. For more information, see Example 2.
+If your organization has multiple Active Directory domains, you might need to run the Set-ADServerSettings cmdlet with the ViewEntireForest parameter set to $true before running the Get-DistributionGroupMember cmdlet to view the entire forest. For more information, see Example 2.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DkimSigningConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-DkimSigningConfig.md
index f26a3f5385..89e4889084 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DkimSigningConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-DkimSigningConfig.md
@@ -29,7 +29,7 @@ Get-DkimSigningConfig [[-Identity] <DkimSigningConfigIdParameter>]
 ## DESCRIPTION
 DKIM in Microsoft 365 is an email authentication method that uses a public key infrastructure (PKI), message headers and CNAME records in DNS to authenticate the message sender, which is stamped in the DKIM-Signature header field. DKIM helps prevent forged sender email addresses (also known as spoofing) by verifying that the domain in the From address matches the domain in the DKIM-Signature header field.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DlpDetailReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-DlpDetailReport.md
index 9b5a04d968..1aad6efd02 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DlpDetailReport.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-DlpDetailReport.md
@@ -13,7 +13,7 @@ title: Get-DlpDetailReport
 # Get-DlpDetailReport
 
 ## SYNOPSIS
-**Note**: This cmdlet has been retired. Use the [Export-ActivityExplorerData](https://learn.microsoft.com/powershell/module/exchangepowershell/export-activityexplorerdata) cmdlet to view DLP information. Data from Export-ActivityExplorerData is the same as the retired Get-DlpIncidentDetailReport cmdlet.
+**Note**: This cmdlet is retired. Use the [Export-ActivityExplorerData](https://learn.microsoft.com/powershell/module/exchangepowershell/export-activityexplorerdata) cmdlet to view DLP information. Data from Export-ActivityExplorerData is the same as the retired Get-DlpIncidentDetailReport cmdlet.
 
 This cmdlet is available only in the cloud-based service.
 
@@ -61,7 +61,7 @@ The Get-DlpDetailReport cmdlet returns detailed information about specific DLP r
 
 To see DLP detection data that's aggregated per day, use the [Get-DlpDetectionsReport](https://learn.microsoft.com/powershell/module/exchangepowershell/get-dlpdetectionsreport) cmdlet.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DlpDetectionsReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-DlpDetectionsReport.md
index 2668fc6b73..5d9632faf6 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DlpDetectionsReport.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-DlpDetectionsReport.md
@@ -53,7 +53,7 @@ To see all of these columns (width issues), write the output to a file. For exam
 
 To see detailed information about each DLP rule match, use the Get-DlpDetailReport cmdlet.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DlpIncidentDetailReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-DlpIncidentDetailReport.md
index b5aa6eac36..6b5f5fb3b1 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DlpIncidentDetailReport.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-DlpIncidentDetailReport.md
@@ -66,7 +66,7 @@ The output of the Get-DlpIncidentDetailReport cmdlet includes the following prop
 - SensitiveInformationCountList
 - SensitiveInformationConfidenceList
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DlpPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-DlpPolicy.md
index d8452dfc15..65c660582f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DlpPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-DlpPolicy.md
@@ -13,7 +13,7 @@ title: Get-DlpPolicy
 # Get-DlpPolicy
 
 ## SYNOPSIS
-**Note**: This cmdlet has been retired from the cloud-based service. For more information, see [this blog post](https://techcommunity.microsoft.com/t5/exchange-team-blog/exchange-online-etrs-to-stop-supporting-dlp-policies/ba-p/3886713). Use the Get-DlpCompliancePolicy and Get-DlpComplianceRule cmdlets instead.
+**Note**: This cmdlet is retired from the cloud-based service. For more information, see [this blog post](https://techcommunity.microsoft.com/t5/exchange-team-blog/exchange-online-etrs-to-stop-supporting-dlp-policies/ba-p/3886713). Use the Get-DlpCompliancePolicy and Get-DlpComplianceRule cmdlets instead.
 
 This cmdlet is functional only in on-premises Exchange.
 
@@ -30,7 +30,7 @@ Get-DlpPolicy [[-Identity] <DlpPolicyIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DlpPolicyTemplate.md b/exchange/exchange-ps/ExchangePowerShell/Get-DlpPolicyTemplate.md
index c43bb97aac..b3260543ef 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DlpPolicyTemplate.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-DlpPolicyTemplate.md
@@ -13,7 +13,7 @@ title: Get-DlpPolicyTemplate
 # Get-DlpPolicyTemplate
 
 ## SYNOPSIS
-**Note**: This cmdlet has been retired from the cloud-based service. For more information, see [this blog post](https://techcommunity.microsoft.com/t5/exchange-team-blog/exchange-online-etrs-to-stop-supporting-dlp-policies/ba-p/3886713).
+**Note**: This cmdlet is retired from the cloud-based service. For more information, see [this blog post](https://techcommunity.microsoft.com/t5/exchange-team-blog/exchange-online-etrs-to-stop-supporting-dlp-policies/ba-p/3886713).
 
 This cmdlet is functional only in on-premises Exchange.
 
@@ -30,7 +30,7 @@ Get-DlpPolicyTemplate [[-Identity] <DlpPolicyIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DnssecStatusForVerifiedDomain.md b/exchange/exchange-ps/ExchangePowerShell/Get-DnssecStatusForVerifiedDomain.md
index 36ca1bd7a8..282963d2eb 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DnssecStatusForVerifiedDomain.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-DnssecStatusForVerifiedDomain.md
@@ -34,7 +34,7 @@ Get-DnssecStatusForVerifiedDomain [-DomainName] <String>
 ## DESCRIPTION
 For more information about debugging, enabling, and disabling SMTP DANE with DNSSEC, see [How SMTP DANE works](https://learn.microsoft.com/purview/how-smtp-dane-works).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DomainController.md b/exchange/exchange-ps/ExchangePowerShell/Get-DomainController.md
index 7a52528003..5ef1c821e9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DomainController.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-DomainController.md
@@ -40,7 +40,7 @@ Get-DomainController [-DomainName <Fqdn>]
 
 The Get-DomainController cmdlet is used by the Exchange admin center to populate fields that display domain controller information.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DynamicDistributionGroup.md b/exchange/exchange-ps/ExchangePowerShell/Get-DynamicDistributionGroup.md
index 87c60a02f3..85d20b7657 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DynamicDistributionGroup.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-DynamicDistributionGroup.md
@@ -13,7 +13,7 @@ title: Get-DynamicDistributionGroup
 # Get-DynamicDistributionGroup
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-DynamicDistributionGroup cmdlet to view existing dynamic distribution groups.
 
@@ -90,7 +90,7 @@ Get-DynamicDistributionGroup [-ManagedBy <GeneralRecipientIdParameter>]
 ## DESCRIPTION
 A dynamic distribution group queries mail-enabled objects and builds the group membership based on the results. The group membership is recalculated whenever an email message is sent to the group.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DynamicDistributionGroupMember.md b/exchange/exchange-ps/ExchangePowerShell/Get-DynamicDistributionGroupMember.md
index 0f7bc5f3fe..73b6f4ac35 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DynamicDistributionGroupMember.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-DynamicDistributionGroupMember.md
@@ -32,7 +32,7 @@ Get-DynamicDistributionGroupMember [-Identity] <DynamicDistributionGroupMemberId
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-EOPProtectionPolicyRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-EOPProtectionPolicyRule.md
index ca0f1e8085..4367780130 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-EOPProtectionPolicyRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-EOPProtectionPolicyRule.md
@@ -30,7 +30,7 @@ Get-EOPProtectionPolicyRule [[-Identity] <RuleIdParameter>]
 ## DESCRIPTION
 For more information about preset security policies in PowerShell, see [Preset security policies in Exchange Online PowerShell](https://learn.microsoft.com/defender-office-365/preset-security-policies#preset-security-policies-in-exchange-online-powershell).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-EXOMailboxFolderPermission.md b/exchange/exchange-ps/ExchangePowerShell/Get-EXOMailboxFolderPermission.md
index 5cbf8ec31b..f4ab5fa2a7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-EXOMailboxFolderPermission.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-EXOMailboxFolderPermission.md
@@ -152,7 +152,7 @@ The User parameter filters the results by the specified mailbox, mail user, or m
 - Email address
 - GUID
 
-**Note**: If you specify a user that doesn't have permission to access the mailbox folder, the command will throw an exception.
+**Note**: If you specify a user that doesn't have permission to access the mailbox folder, the command returns an error.
 
 ```yaml
 Type: String
@@ -170,7 +170,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online
 
-The UserPrincipalName parameter identifies the mailbox that you want to view by UPN (for example, navin@contoso.onmicrosoft.com).
+The UserPrincipalName parameter identifies the mailbox that you want to view by UPN (for example, `navin@contoso.onmicrosoft.com`).
 
 You can't use this parameter with the ExternalDirectoryObjectId, Identity, or PrimarySmtpAddress parameters.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-EXOMailboxPermission.md b/exchange/exchange-ps/ExchangePowerShell/Get-EXOMailboxPermission.md
index d52f055125..65358472d3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-EXOMailboxPermission.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-EXOMailboxPermission.md
@@ -54,7 +54,7 @@ By default, the following permissions are assigned to user mailboxes:
 
 - FullAccess and ReadPermission are directly assigned to NT AUTHORITY\SELF. This entry gives a user permission to their own mailbox.
 - FullAccess is denied to Administrator, Domain Admins, Enterprise Admins and Organization Management. These inherited permissions prevent these users and group members from opening other users' mailboxes.
-- ChangeOwner, ChangePermission, DeleteItem, and ReadPermission are allowed for Administrator, Domain Admins, Enterprise Admins and Organization Management. Note that these inherited permission entries also appear to allow FullAccess. However, these users and groups do not have FullAccess to the mailbox because the inherited Deny permission entries override the inherited Allow permission entries.
+- ChangeOwner, ChangePermission, DeleteItem, and ReadPermission are allowed for Administrator, Domain Admins, Enterprise Admins and Organization Management. These inherited permission entries also appear to allow FullAccess. However, these users and groups do not have FullAccess to the mailbox because the inherited Deny permission entries override the inherited Allow permission entries.
 - FullAccess is inherited by NT AUTHORITY\SYSTEM and ReadPermission is inherited by NT AUTHORITY\NETWORK.
 - FullAccess and ReadPermission are inherited by Exchange Servers, ChangeOwner, ChangePermission, DeleteItem, and ReadPermission are inherited by Exchange Trusted Subsystem and ReadPermission is inherited by Managed Availability Servers.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-EXORecipient.md b/exchange/exchange-ps/ExchangePowerShell/Get-EXORecipient.md
index eac17545ab..b4f3f62b24 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-EXORecipient.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-EXORecipient.md
@@ -374,7 +374,7 @@ The RecipientTypeDetails parameter filters the results by the specified recipien
 
 You can specify multiple values separated by commas.
 
-The value of the RecipientType parameter affects the values that you can use for this parameter. For example, if you use the RecipientType value MailContact, you can't use the value UserMailbox for this parameter. You'll receive the error: None of the specified RecipientTypeDetails are included in any specified recipient type.
+The value of the RecipientType parameter affects the values that you can use for this parameter. For example, if you use the RecipientType value MailContact, you can't use the value UserMailbox for this parameter. You get the error: None of the specified RecipientTypeDetails are included in any specified recipient type.
 
 ```yaml
 Type: String[]
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-EXORecipientPermission.md b/exchange/exchange-ps/ExchangePowerShell/Get-EXORecipientPermission.md
index 41c27a1675..ec3795b475 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-EXORecipientPermission.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-EXORecipientPermission.md
@@ -43,7 +43,7 @@ Get-EXORecipientPermission [[-Identity] <String>]
 ```
 
 ## DESCRIPTION
-This cmdlet is used to view/manage information about SendAs permissions that are configured for users in a cloud-based organization. Send As permission allows delegates to use the mailbox to send messages. After this permission is assigned to a delegate, any message that the delegate sends from the mailbox will appear to have been sent by the mailbox owner. However, this permission doesn't allow a delegate to sign in to the user's mailbox. It only allows users to open the mailbox. If this permission is assigned to a group, a message sent by the delegate will appear to have been sent by the group.
+This cmdlet is used to view/manage information about SendAs permissions that are configured for users in a cloud-based organization. Send As permission allows delegates to use the mailbox to send messages. After this permission is assigned to a delegate, any message that the delegate sends from the mailbox appears to be sent by the mailbox owner. However, this permission doesn't allow a delegate to sign in to the user's mailbox. It only allows users to open the mailbox. If this permission is assigned to a group, a message sent by the delegate appears to be sent by the group.
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-EcpVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Get-EcpVirtualDirectory.md
index 250dab85ba..a892d29bdf 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-EcpVirtualDirectory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-EcpVirtualDirectory.md
@@ -42,7 +42,7 @@ Get-EcpVirtualDirectory [[-Identity] <VirtualDirectoryIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-EdgeSubscription.md b/exchange/exchange-ps/ExchangePowerShell/Get-EdgeSubscription.md
index 75362938ad..0bcc05c3a9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-EdgeSubscription.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-EdgeSubscription.md
@@ -30,7 +30,7 @@ Get-EdgeSubscription [[-Identity] <TransportServerIdParameter>]
 ## DESCRIPTION
 Run the Get-EdgeSubscription cmdlet on an Exchange server in your organization. This cmdlet retrieves the list of Edge Subscriptions. Each Edge Transport server that's subscribed to the Exchange organization has a separate Edge Subscription. You can use this cmdlet to view the Edge Subscription information for a specific Edge Transport server. You can also use this cmdlet to view the Edge Subscription information for all Edge Transport servers subscribed to Active Directory sites.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-EdgeSyncServiceConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-EdgeSyncServiceConfig.md
index 0f9ce42282..d10d31d535 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-EdgeSyncServiceConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-EdgeSyncServiceConfig.md
@@ -29,7 +29,7 @@ Get-EdgeSyncServiceConfig [[-Identity] <EdgeSyncServiceConfigIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-EligibleDistributionGroupForMigration.md b/exchange/exchange-ps/ExchangePowerShell/Get-EligibleDistributionGroupForMigration.md
index dabfa9610d..85571cd4b0 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-EligibleDistributionGroupForMigration.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-EligibleDistributionGroupForMigration.md
@@ -38,7 +38,7 @@ Get-EligibleDistributionGroupForMigration [-ManagedBy <GeneralRecipientIdParamet
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-EmailAddressPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-EmailAddressPolicy.md
index ccc466c3b6..7a18f54fe9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-EmailAddressPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-EmailAddressPolicy.md
@@ -13,7 +13,7 @@ title: Get-EmailAddressPolicy
 # Get-EmailAddressPolicy
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-EmailAddressPolicy cmdlet to view email address policies. In Exchange Online, email address policies are available only for Microsoft 365 Groups.
 
@@ -29,7 +29,7 @@ Get-EmailAddressPolicy [[-Identity] <EmailAddressPolicyIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-EmailTenantSettings.md b/exchange/exchange-ps/ExchangePowerShell/Get-EmailTenantSettings.md
index 8fa56a3fe5..48232a093d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-EmailTenantSettings.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-EmailTenantSettings.md
@@ -26,7 +26,7 @@ Get-EmailTenantSettings [[-Identity] <EmailTenantSettingsIdParameter>] [<CommonP
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-EtrLimits.md b/exchange/exchange-ps/ExchangePowerShell/Get-EtrLimits.md
index ddcf5e44e4..0d338fcdc2 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-EtrLimits.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-EtrLimits.md
@@ -26,7 +26,7 @@ Get-EtrLimits [<CommonParameters>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-EventLogLevel.md b/exchange/exchange-ps/ExchangePowerShell/Get-EventLogLevel.md
index e44116bb97..0e6199f755 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-EventLogLevel.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-EventLogLevel.md
@@ -36,7 +36,7 @@ Get-EventLogLevel [[-Identity] <ECIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-EventsFromEmailConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Get-EventsFromEmailConfiguration.md
index 739c0aca33..25832eb908 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-EventsFromEmailConfiguration.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-EventsFromEmailConfiguration.md
@@ -29,7 +29,7 @@ Get-EventsFromEmailConfiguration [-Identity] <RecipientIdParameter>
 ## DESCRIPTION
 **Note**: The following output properties have been deprecated: EventReservationProcessingLevel, FoodEstablishmentReservationProcessingLevel, InvoiceProcessingLevel, and ServiceReservationProcessingLevel.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeAssistanceConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeAssistanceConfig.md
index 6935ba187f..ab03c82edf 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeAssistanceConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeAssistanceConfig.md
@@ -28,7 +28,7 @@ Get-ExchangeAssistanceConfig [[-Identity] <OrganizationIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeCertificate.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeCertificate.md
index fea0c58a77..0931257c1a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeCertificate.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeCertificate.md
@@ -51,7 +51,7 @@ Get-ExchangeCertificate [[-Thumbprint] <String>]
 By default, this cmdlet returns the following certificate properties in the summary list view:
 
 - Thumbprint: The unique digest of the certificate data. An example thumbprint value is 78E1BE82F683EE6D8CB9B9266FC1185AE0890C41.
-- Services: The Exchange services that the certificate is assigned to by using the Enable-ExchangeCertificate cmdlet. Values are None, Federation, IIS, IMAP, POP, SMTP, UM, and UMCallRouter. You'll see the value None in certificates that aren't used with Exchange (for example, the `WMSvc-<ServerName>` certificate that's used for the IIS Web Management Service).
+- Services: The Exchange services that the certificate is assigned to by using the Enable-ExchangeCertificate cmdlet. Values are None, Federation, IIS, IMAP, POP, SMTP, UM, and UMCallRouter. You see the value None in certificates that aren't used with Exchange (for example, the `WMSvc-<ServerName>` certificate that's used for the IIS Web Management Service).
 - Subject: Contains the X.500 value in the certificate's Subject Name field. The important part is the CN= value.
 
 If you append ` | Format-List` to the command, the cmdlet returns these additional certificate properties:
@@ -92,7 +92,7 @@ If you append ` | Format-List *` to the command, the cmdlet returns these additi
 - SubjectName: Typically, this value is System.Security.Cryptography.X509Certificates.X500DistinguishedName.
 - Version: Typically, this value is 3.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -122,7 +122,7 @@ This example returns all available information for the specified certificate.
 Get-ExchangeCertificate -DomainName mail.contoso.com
 ```
 
-This example shows which certificate Exchange will select for the domain name mail.contoso.com. A Send connector or Receive connector selects the certificate to use based on the fully qualified domain name (FQDN) of the connector. If you have multiple certificates with the same FQDN, you can see which certificate Exchange will select by using the DomainName parameter to specify the FQDN. The first certificate returned is the certificate that Exchange will select.
+This example shows which certificate Exchange selects for the domain name mail.contoso.com. A Send connector or Receive connector selects the certificate to use based on the fully qualified domain name (FQDN) of the connector. If you have multiple certificates with the same FQDN, you can see which certificate Exchange selects by using the DomainName parameter to specify the FQDN. The first certificate returned is the certificate that Exchange selects.
 
 ## PARAMETERS
 
@@ -213,7 +213,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-This parameter has been deprecated and is no longer used.
+This parameter is deprecated and no longer used.
 
 ```yaml
 Type: X509Certificate2
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeDiagnosticInfo.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeDiagnosticInfo.md
index 26ef51e172..f0d225dc85 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeDiagnosticInfo.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeDiagnosticInfo.md
@@ -31,7 +31,7 @@ Get-ExchangeDiagnosticInfo [-Argument <String>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeFeature.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeFeature.md
index 124cbe2406..66aa3b8ac0 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeFeature.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeFeature.md
@@ -31,7 +31,7 @@ Get-ExchangeFeature [-Identity <ServerIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServer.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServer.md
index 5bbf2d4944..0765cedd81 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServer.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServer.md
@@ -42,7 +42,7 @@ Get-ExchangeServer [[-Identity] <ServerIdParameter>]
 ## DESCRIPTION
 The ExchangeVersion attribute returned is the minimum version of Microsoft Exchange that you can use to manage the returned object. This attribute isn't the same as the version of Exchange displayed in the Exchange admin center when you select Server Configuration.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServerAccessLicense.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServerAccessLicense.md
index 1663316338..3bb1ee430a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServerAccessLicense.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServerAccessLicense.md
@@ -33,7 +33,7 @@ The Get-ExchangeServerAccessLicense cmdlet returns a collection of these license
 - Exchange Server Standard Edition
 - Exchange Server Enterprise Edition
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServerAccessLicenseUser.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServerAccessLicenseUser.md
index 4c452c27b0..eb7f39eb5d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServerAccessLicenseUser.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServerAccessLicenseUser.md
@@ -29,7 +29,7 @@ Get-ExchangeServerAccessLicenseUser -LicenseName <String>
 ## DESCRIPTION
 The Get-ExchangeServerAccessLicenseUser cmdlet returns a collection of unique users for the specified license name. The list of unique users represents an estimate of your licenses when you run this cmdlet. Each object contains the FQDN or primary SMTP address of the mailbox and the license name to which it's associated.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeSettings.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeSettings.md
index 23cefad71d..d1d449f8f3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeSettings.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeSettings.md
@@ -40,7 +40,7 @@ Get-ExchangeSettings [[-Identity] <ExchangeSettingsIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ExoInformationBarrierPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExoInformationBarrierPolicy.md
index 593507275d..c7bf951bbb 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ExoInformationBarrierPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExoInformationBarrierPolicy.md
@@ -26,7 +26,7 @@ Get-ExoInformationBarrierPolicy [[-Identity] <MailboxPolicyIdParameter>] [-ShowF
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ExoInformationBarrierRelationship.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExoInformationBarrierRelationship.md
index a21fb872a1..77602601cd 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ExoInformationBarrierRelationship.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExoInformationBarrierRelationship.md
@@ -27,7 +27,7 @@ Get-ExoInformationBarrierRelationship -RecipientId1 <RecipientIdParameter> -Reci
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ExoInformationBarrierSegment.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExoInformationBarrierSegment.md
index 2133d84497..b66215c355 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ExoInformationBarrierSegment.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExoInformationBarrierSegment.md
@@ -26,7 +26,7 @@ Get-ExoInformationBarrierSegment [[-Identity] <InformationBarrierSegmentIdParame
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ExoPhishSimOverrideRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExoPhishSimOverrideRule.md
index 3b747b043e..17a8d7192e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ExoPhishSimOverrideRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExoPhishSimOverrideRule.md
@@ -31,7 +31,7 @@ Get-ExoPhishSimOverrideRule [[-Identity] <ComplianceRuleIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ExoSecOpsOverrideRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExoSecOpsOverrideRule.md
index 6a7a7b3409..3d42a3cbcf 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ExoSecOpsOverrideRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExoSecOpsOverrideRule.md
@@ -31,7 +31,7 @@ Get-ExoSecOpsOverrideRule [[-Identity] <ComplianceRuleIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ExternalInOutlook.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExternalInOutlook.md
index 8da1e93597..b33e844ca7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ExternalInOutlook.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExternalInOutlook.md
@@ -31,7 +31,7 @@ The important properties that are returned in the output of this cmdlet are:
 - Enabled: True means the feature is enabled; False means the feature is disabled.
 - AllowList: The list of exceptions. Messages received from the specified senders or senders in the specified domains don't receive the External icon in the area of subject line.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-FailedContentIndexDocuments.md b/exchange/exchange-ps/ExchangePowerShell/Get-FailedContentIndexDocuments.md
index 509c2fe2d2..e86dea6e67 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-FailedContentIndexDocuments.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-FailedContentIndexDocuments.md
@@ -71,7 +71,7 @@ After a new filter is installed, only new messages with attachments of the type
 
 The cmdlet output provides details about items in a mailbox that couldn't be indexed, including an error code and the reason for failure.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-FederatedDomainProof.md b/exchange/exchange-ps/ExchangePowerShell/Get-FederatedDomainProof.md
index 6e8cafa070..4fe0da6daa 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-FederatedDomainProof.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-FederatedDomainProof.md
@@ -31,7 +31,7 @@ Get-FederatedDomainProof -DomainName <SmtpDomain>
 ## DESCRIPTION
 The Get-FederatedDomainProof cmdlet generates a cryptographically secure string for the domain used for federated sharing. The resulting string is used to manually configure a text (TXT) record in the Domain Name System (DNS) zone for the domain used by the administrator when running the cmdlet. A TXT record needs to be added to DNS for all accepted domains used for federated sharing. If the thumbprint of a certificate isn't provided, the task generates strings for all the certificates currently configured for the federation trust. Upon initial configuration of federated sharing, the proof string generated for the current certificate needs to be put into the TXT record for the federated domain in DNS. We recommend you update the TXT records whenever a new certificate is configured for the federation trust.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-FederatedOrganizationIdentifier.md b/exchange/exchange-ps/ExchangePowerShell/Get-FederatedOrganizationIdentifier.md
index 9e34d46c14..47e2fce1d9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-FederatedOrganizationIdentifier.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-FederatedOrganizationIdentifier.md
@@ -13,7 +13,7 @@ title: Get-FederatedOrganizationIdentifier
 # Get-FederatedOrganizationIdentifier
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-FederatedOrganizationIdentifier cmdlet to retrieve the Exchange organization's federated organization identifier and related details, such as federated domains, organization contact and status.
 
@@ -31,7 +31,7 @@ Get-FederatedOrganizationIdentifier [[-Identity] <OrganizationIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-FederationInformation.md b/exchange/exchange-ps/ExchangePowerShell/Get-FederationInformation.md
index 3d86985c9a..c270d36671 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-FederationInformation.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-FederationInformation.md
@@ -13,7 +13,7 @@ title: Get-FederationInformation
 # Get-FederationInformation
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-FederationInformation cmdlet to get federation information from an external Exchange organization.
 
@@ -35,7 +35,7 @@ Get-FederationInformation -DomainName <SmtpDomain>
 ## DESCRIPTION
 The Get-FederationInformation cmdlet retrieves federation information from the specified domain, which should have federation enabled.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-FederationTrust.md b/exchange/exchange-ps/ExchangePowerShell/Get-FederationTrust.md
index e4bb95f38d..56f0ba4831 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-FederationTrust.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-FederationTrust.md
@@ -13,7 +13,7 @@ title: Get-FederationTrust
 # Get-FederationTrust
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-FederationTrust cmdlet to view the federation trust configured for the Exchange organization.
 
@@ -28,7 +28,7 @@ Get-FederationTrust [[-Identity] <FederationTrustIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-FocusedInbox.md b/exchange/exchange-ps/ExchangePowerShell/Get-FocusedInbox.md
index 5ffb9ea050..b1f7e2b8ea 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-FocusedInbox.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-FocusedInbox.md
@@ -30,7 +30,7 @@ Get-FocusedInbox -Identity <MailboxIdParameter>
 ## DESCRIPTION
 Focused Inbox is a replacement for Clutter that separates the Inbox into the Focused and Other tabs in Outlook on the web and newer versions of Outlook. Important emails are on the Focused tab while the rest are on the Other tab.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ForeignConnector.md b/exchange/exchange-ps/ExchangePowerShell/Get-ForeignConnector.md
index 7abc2d7b28..6aa7779b61 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ForeignConnector.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ForeignConnector.md
@@ -28,7 +28,7 @@ Get-ForeignConnector [[-Identity] <ForeignConnectorIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-FrontendTransportService.md b/exchange/exchange-ps/ExchangePowerShell/Get-FrontendTransportService.md
index 2c21f00765..0e1874937a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-FrontendTransportService.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-FrontendTransportService.md
@@ -30,7 +30,7 @@ Get-FrontendTransportService [[-Identity] <FrontendTransportServerIdParameter>]
 ## DESCRIPTION
 The Front End Transport service acts as a stateless proxy for all inbound and outbound external SMTP traffic for the Exchange organization.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-GlobalAddressList.md b/exchange/exchange-ps/ExchangePowerShell/Get-GlobalAddressList.md
index 6725543d75..71b37b5867 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-GlobalAddressList.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-GlobalAddressList.md
@@ -13,7 +13,7 @@ title: Get-GlobalAddressList
 # Get-GlobalAddressList
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-GlobalAddressList cmdlet to view a global address list (GAL) or a set of GALs.
 
@@ -40,7 +40,7 @@ Get-GlobalAddressList [[-Identity] <GlobalAddressListIdParameter>]
 ## DESCRIPTION
 The Get-GlobalAddressList cmdlet is mainly used to populate the GAL property pages in the Exchange admin center. This command doesn't provide a filtering capability. If filtering is required, you should use a WHERE clause with the command.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-GlobalMonitoringOverride.md b/exchange/exchange-ps/ExchangePowerShell/Get-GlobalMonitoringOverride.md
index 83d6144720..5b523b365d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-GlobalMonitoringOverride.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-GlobalMonitoringOverride.md
@@ -27,7 +27,7 @@ Get-GlobalMonitoringOverride [-DomainController <Fqdn>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-Group.md b/exchange/exchange-ps/ExchangePowerShell/Get-Group.md
index dbaaa4b176..7a8fd3d370 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-Group.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-Group.md
@@ -13,7 +13,7 @@ title: Get-Group
 # Get-Group
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-Group cmdlet to view existing group objects in your organization. In all environments, this cmdlet returns mail-enabled security groups, distribution groups, role groups, and room lists. For details about other supported group types in on-premises Exchange environments, see the RecipientTypeDetails parameter description.
 
@@ -54,7 +54,7 @@ Get-Group [[-Identity] <GroupIdParameter>]
 ## DESCRIPTION
 The Get-Group cmdlet returns no mail-related properties for distribution groups or mail-enabled security groups, and no role group-related properties for role groups. To view the object-specific properties for a group, you need to use the corresponding cmdlet based on the object type (for example, Get-DistributionGroup or Get-RoleGroup).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-HealthReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-HealthReport.md
index e95ba742ac..b729e36b53 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-HealthReport.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-HealthReport.md
@@ -41,7 +41,7 @@ The following list contains the health values that are returned:
 - Functional
 - Unavailable
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-HistoricalSearch.md b/exchange/exchange-ps/ExchangePowerShell/Get-HistoricalSearch.md
index 27051147bd..97064d9895 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-HistoricalSearch.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-HistoricalSearch.md
@@ -29,7 +29,7 @@ Get-HistoricalSearch [-JobId <Guid>]
 ## DESCRIPTION
 A historical search provides message trace and report details in a comma-separated value (CSV) file for messages that are less than 90 days old.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-HoldCompliancePolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-HoldCompliancePolicy.md
index 78c781ef0f..13535a450a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-HoldCompliancePolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-HoldCompliancePolicy.md
@@ -17,7 +17,7 @@ This cmdlet is available only in Security & Compliance PowerShell. For more info
 
 Use the Get-HoldCompliancePolicy to view existing preservation policies in the Microsoft Purview compliance portal.
 
-**Note**: The Get-HoldCompliancePolicy cmdlet has been replaced by the Get-RetentionCompliancePolicy cmdlet. If you have scripts that use Get-HoldCompliancePolicy, update them to use Get-RetentionCompliancePolicy.
+**Note**: The Get-HoldCompliancePolicy cmdlet is replaced by the Get-RetentionCompliancePolicy cmdlet. If you have scripts that use Get-HoldCompliancePolicy, update them to use Get-RetentionCompliancePolicy.
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-HoldComplianceRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-HoldComplianceRule.md
index 6f68eb4b30..7885973ffc 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-HoldComplianceRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-HoldComplianceRule.md
@@ -17,7 +17,7 @@ This cmdlet is available only in Security & Compliance PowerShell. For more info
 
 Use the Get-HoldComplianceRule to view preservation rules in the Microsoft Purview compliance portal.
 
-**Note**: The Get-HoldComplianceRule cmdlet has been replaced by the Get-RetentionComplianceRule cmdlet. If you have scripts that use Get-HoldComplianceRule, update them to use Get-RetentionComplianceRule.
+**Note**: The Get-HoldComplianceRule cmdlet is replaced by the Get-RetentionComplianceRule cmdlet. If you have scripts that use Get-HoldComplianceRule, update them to use Get-RetentionComplianceRule.
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-HostedConnectionFilterPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-HostedConnectionFilterPolicy.md
index 3b9e5bdaac..9207a2a0e7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-HostedConnectionFilterPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-HostedConnectionFilterPolicy.md
@@ -27,7 +27,7 @@ Get-HostedConnectionFilterPolicy [[-Identity] <HostedConnectionFilterPolicyIdPar
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-HostedContentFilterPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-HostedContentFilterPolicy.md
index 3fd2f2b42b..bf029648b2 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-HostedContentFilterPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-HostedContentFilterPolicy.md
@@ -27,7 +27,7 @@ Get-HostedContentFilterPolicy [[-Identity] <HostedContentFilterPolicyIdParameter
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-HostedContentFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-HostedContentFilterRule.md
index 1f67787900..23b47a8a79 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-HostedContentFilterRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-HostedContentFilterRule.md
@@ -29,7 +29,7 @@ Get-HostedContentFilterRule [[-Identity] <RuleIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-HostedOutboundSpamFilterPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-HostedOutboundSpamFilterPolicy.md
index 20ca00576b..3259b337b8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-HostedOutboundSpamFilterPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-HostedOutboundSpamFilterPolicy.md
@@ -27,7 +27,7 @@ Get-HostedOutboundSpamFilterPolicy [-Identity] <HostedOutboundSpamFilterPolicyId
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-HostedOutboundSpamFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-HostedOutboundSpamFilterRule.md
index 2a1d5d73a1..0e251e98d8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-HostedOutboundSpamFilterRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-HostedOutboundSpamFilterRule.md
@@ -28,7 +28,7 @@ Get-HostedOutboundSpamFilterRule [[-Identity] <RuleIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-HybridConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Get-HybridConfiguration.md
index fd1ebea9b8..f1c086874f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-HybridConfiguration.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-HybridConfiguration.md
@@ -27,7 +27,7 @@ Get-HybridConfiguration [-DomainController <Fqdn>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-HybridMailflowDatacenterIPs.md b/exchange/exchange-ps/ExchangePowerShell/Get-HybridMailflowDatacenterIPs.md
index b9e16d25d2..47d56b16c7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-HybridMailflowDatacenterIPs.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-HybridMailflowDatacenterIPs.md
@@ -15,7 +15,7 @@ title: Get-HybridMailflowDatacenterIPs
 ## SYNOPSIS
 This cmdlet is available only in the cloud-based service.
 
-This cmdlet has been deprecated and is no longer used.
+This cmdlet is deprecated and is no longer used.
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
@@ -26,7 +26,7 @@ Get-HybridMailflowDatacenterIPs [<CommonParameters>]
 ```
 
 ## DESCRIPTION
-This cmdlet has been deprecated and is no longer used.
+This cmdlet is deprecated and is no longer used.
 
 ## EXAMPLES
 
@@ -35,7 +35,7 @@ This cmdlet has been deprecated and is no longer used.
 Get-HybridMailflowDatacenterIPs
 ```
 
-This cmdlet has been deprecated and is no longer used.
+This cmdlet is deprecated and is no longer used.
 
 ## PARAMETERS
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-IPv6StatusForAcceptedDomain.md b/exchange/exchange-ps/ExchangePowerShell/Get-IPv6StatusForAcceptedDomain.md
index 95b42a54fc..341dfde6a7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-IPv6StatusForAcceptedDomain.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-IPv6StatusForAcceptedDomain.md
@@ -32,7 +32,7 @@ Use the Get-AcceptedDomain cmdlet to return accepted domains in the Exchange Onl
 
 If IPv6 is enabled for an accepted domain in Exchange Online, IPv4 and IPv6 addresses are returned in DNS queries for mail flow records of the domain. If IPv6 is disabled, only IPv4 addresses are returned in DNS queries for mail flow records of the domain.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 > [!NOTE]
 >
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-IRMConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Get-IRMConfiguration.md
index dc6a295bf7..4e66c8198d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-IRMConfiguration.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-IRMConfiguration.md
@@ -13,7 +13,7 @@ title: Get-IRMConfiguration
 # Get-IRMConfiguration
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-IRMConfiguration cmdlet to view the Information Rights Management (IRM) configuration in your organization.
 
@@ -29,7 +29,7 @@ Get-IRMConfiguration [-DomainController <Fqdn>]
 ## DESCRIPTION
 The Get-IRMConfiguration cmdlet provides details about the current IRM configuration, including whether individual IRM features are enabled or disabled and provides the URLs used for ServiceLocation, PublishingLocation and LicensingLocation.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ImapSettings.md b/exchange/exchange-ps/ExchangePowerShell/Get-ImapSettings.md
index 09f01eed05..3e3bc98b54 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ImapSettings.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ImapSettings.md
@@ -28,7 +28,7 @@ Get-ImapSettings [-DomainController <Fqdn>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-InboundConnector.md b/exchange/exchange-ps/ExchangePowerShell/Get-InboundConnector.md
index 4b8f165f3a..0dc6a2864e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-InboundConnector.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-InboundConnector.md
@@ -30,7 +30,7 @@ Get-InboundConnector [[-Identity] <InboundConnectorIdParameter>]
 ## DESCRIPTION
 Inbound connectors accept email messages from remote domains that require specific configuration options.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-InboxRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-InboxRule.md
index 59c768d5f7..13da496b00 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-InboxRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-InboxRule.md
@@ -13,7 +13,7 @@ title: Get-InboxRule
 # Get-InboxRule
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-InboxRule cmdlet to view Inbox rule properties. Inbox rules are used to process messages in the Inbox based on conditions specified and take actions such as moving a message to a specified folder or deleting a message.
 
@@ -37,7 +37,7 @@ Get-InboxRule [[-Identity] <InboxRuleIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 **Note**: This cmdlet doesn't work for members of View-Only Organization Management role group in Exchange Online or the Global Reader role in Microsoft Entra ID.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-IntraOrganizationConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Get-IntraOrganizationConfiguration.md
index a0fff4f00b..3c8a1400ef 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-IntraOrganizationConfiguration.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-IntraOrganizationConfiguration.md
@@ -13,7 +13,7 @@ title: Get-IntraOrganizationConfiguration
 # Get-IntraOrganizationConfiguration
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-IntraOrganizationConfiguration cmdlet to view the component settings of a hybrid Exchange deployment.
 
@@ -31,7 +31,7 @@ A hybrid Exchange deployment results in one logical organization made up of a nu
 
 Hybrid environments are enabled by Intra-Organization connectors. The connectors can be created and managed by cmdlets like New-IntraOrganizationConnector, but we strongly recommend that you use the Hybrid Configuration wizard when configuring a hybrid deployment with an Exchange Online organization.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -50,7 +50,7 @@ This example returns the settings of the intra-organization configuration.
 
 This parameter is available only in the cloud-based service.
 
-The OrganizationGuid parameter specifies the on-premises organization in a hybrid deployment that has multiple on-premises organizations defined. If you don't use the OrganizationGuid parameter for these types of hybrid deployments, the Get-IntraOrganizationConfiguration cmdlet will generate errors. To view the on-premises organization GUID values that are required for this parameter, use the Get-OnPremisesOrganization cmdlet.
+The OrganizationGuid parameter specifies the on-premises organization in a hybrid deployment that has multiple on-premises organizations defined. If you don't use the OrganizationGuid parameter for these types of hybrid deployments, the Get-IntraOrganizationConfiguration cmdlet returns errors. To view the on-premises organization GUID values that are required for this parameter, use the Get-OnPremisesOrganization cmdlet.
 
 ```yaml
 Type: OnPremisesOrganizationIdParameter
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-IntraOrganizationConnector.md b/exchange/exchange-ps/ExchangePowerShell/Get-IntraOrganizationConnector.md
index 9b1bb44334..f8c1970bfe 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-IntraOrganizationConnector.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-IntraOrganizationConnector.md
@@ -13,7 +13,7 @@ title: Get-IntraOrganizationConnector
 # Get-IntraOrganizationConnector
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-IntraOrganizationConnector cmdlet to view the settings of Intra-Organization connectors.
 
@@ -30,7 +30,7 @@ Get-IntraOrganizationConnector [[-Identity] <IntraOrganizationConnectorIdParamet
 ## DESCRIPTION
 Intra-Organizational connectors enable features and services between divisions in your Exchange organization. It allows for the expansion of organizational boundaries for features and services across different hosts and network boundaries, such as between Active Directory forests, between on-premises and cloud-based organizations, or between tenants hosted in the same or different datacenters.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-JournalRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-JournalRule.md
index c1bc9f9203..815d630a83 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-JournalRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-JournalRule.md
@@ -13,7 +13,7 @@ title: Get-JournalRule
 # Get-JournalRule
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-JournalRule cmdlet to view the journal rules in your organization.
 
@@ -30,7 +30,7 @@ Get-JournalRule [[-Identity] <RuleIdParameter>]
 ## DESCRIPTION
 The Get-JournalRule cmdlet displays journal rules configured in your organization.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-LinkedUser.md b/exchange/exchange-ps/ExchangePowerShell/Get-LinkedUser.md
index a4e3fe0a73..b75371ad04 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-LinkedUser.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-LinkedUser.md
@@ -42,7 +42,7 @@ Get-LinkedUser [[-Identity] <UserIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-LogonStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-LogonStatistics.md
index dc9385ddb7..b688ec17cc 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-LogonStatistics.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-LogonStatistics.md
@@ -15,7 +15,7 @@ title: Get-LogonStatistics
 ## SYNOPSIS
 This cmdlet is functional only in Exchange Server 2010.
 
-The Get-LogonStatistics cmdlet has been deprecated and is no longer used.
+The Get-LogonStatistics cmdlet is deprecated and is no longer used.
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
@@ -45,9 +45,9 @@ Get-LogonStatistics -Server <ServerIdParameter>
 ## DESCRIPTION
 The Get-LogonStatistics cmdlet retrieves logon information about currently active sessions. On Mailbox servers only, you can use the Get-LogonStatistics cmdlet without parameters. In this case, the cmdlet returns the logon statistics for all mailboxes on all databases on the local server.
 
-Users who log on to their mailboxes using Microsoft Office Outlook Web App aren't continually connected to the Mailbox server. An Outlook Web App client connects to the server, performs tasks, and then disconnects from the server. Therefore, you may see few or no logon statistics for Outlook Web App, even if users are logged on with this client.
+Users who log on to their mailboxes using Microsoft Office Outlook Web App aren't continually connected to the Mailbox server. An Outlook Web App client connects to the server, performs tasks, and then disconnects from the server. Therefore, you might see few or no logon statistics for Outlook Web App, even if users are logged on with this client.
 
-You need to be assigned permissions before you can run this cmdlet. Although all parameters for this cmdlet are listed in this topic, you may not have access to some parameters if they're not included in the permissions assigned to you. To see what permissions you need, see the "Recipient Provisioning Permissions" section in the Mailbox Permissions topic.
+You need to be assigned permissions before you can run this cmdlet. Although all parameters for this cmdlet are listed in this topic, you might not have access to some parameters if they're not included in the permissions assigned to you. To see what permissions you need, see the "Recipient Provisioning Permissions" section in the Mailbox Permissions topic.
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-M365DataAtRestEncryptionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-M365DataAtRestEncryptionPolicy.md
index fa455671a6..5fd747c8bd 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-M365DataAtRestEncryptionPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-M365DataAtRestEncryptionPolicy.md
@@ -34,7 +34,7 @@ M365 data-at-rest encryption policy cmdlets are accessible to compliance adminis
 
 You can create and assign a Microsoft 365 data-at-rest encryption policy at the tenant level by using the appropriate M365DataAtRestEncryptionPolicy cmdlets in Exchange Online PowerShell.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-M365DataAtRestEncryptionPolicyAssignment.md b/exchange/exchange-ps/ExchangePowerShell/Get-M365DataAtRestEncryptionPolicyAssignment.md
index b096ce31ee..a27e3b6d3f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-M365DataAtRestEncryptionPolicyAssignment.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-M365DataAtRestEncryptionPolicyAssignment.md
@@ -28,7 +28,7 @@ Get-M365DataAtRestEncryptionPolicyAssignment [<CommonParameters>]
 ## DESCRIPTION
 This cmdlet lists the Microsoft 365 data-at-rest encryption policy that's currently assigned to the tenant.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-Mailbox.md b/exchange/exchange-ps/ExchangePowerShell/Get-Mailbox.md
index 1d1068f22f..8025e351a4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-Mailbox.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-Mailbox.md
@@ -13,7 +13,7 @@ title: Get-Mailbox
 # Get-Mailbox
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-Mailbox cmdlet to view mailbox objects and attributes, populate property pages, or supply mailbox information to other tasks.
 
@@ -168,7 +168,7 @@ Get-Mailbox [-MailboxPlan <MailboxPlanIdParameter>]
 ## DESCRIPTION
 When you use the Get-Mailbox cmdlet in on-premises Exchange environments to view the quota settings for a mailbox, you first need to check the value of the UseDatabaseQuotaDefaults property. The value True means per-mailbox quota settings are ignored, and you need to use the Get-MailboxDatabase cmdlet to see the actual values. If the UseDatabaseQuotaDefaults property is False, the per-mailbox quota settings are used, so what you see with the Get-Mailbox cmdlet are the actual quota values for the mailbox.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -886,7 +886,7 @@ You can use any value that uniquely identifies the server. For example:
 
 You can't use this parameter with the Anr, Database, or Identity parameters.
 
-The ServerName and ServerLegacyDN properties for a mailbox may not be updated immediately after a mailbox move within a database availability group (DAG). To get the most up-to-date values for these mailbox properties, run the command `Get-Mailbox <Identity> | Get-MailboxStatistics | Format-List Name,ServerName,ServerLegacyDN`.
+The ServerName and ServerLegacyDN properties for a mailbox might not be updated immediately after a mailbox move within a database availability group (DAG). To get the most up-to-date values for these mailbox properties, run the command `Get-Mailbox <Identity> | Get-MailboxStatistics | Format-List Name,ServerName,ServerLegacyDN`.
 
 **Note**: The result from this parameter could be a legacy value before migration. For better results, use the Database parameter instead.
 

From bf956f8e65306bd834d1c7faafaf76f49fda1ad4 Mon Sep 17 00:00:00 2001
From: Chris Davis <chris.davis@microsoft.com>
Date: Tue, 5 Aug 2025 18:11:27 -0700
Subject: [PATCH 076/145] Acrolinx 4

---
 exchange/exchange-ps/ExchangePowerShell/Add-ADPermission.md     | 2 +-
 .../ExchangePowerShell/Add-AvailabilityAddressSpace.md          | 2 +-
 .../exchange-ps/ExchangePowerShell/Add-ContentFilterPhrase.md   | 2 +-
 .../ExchangePowerShell/Add-DatabaseAvailabilityGroupServer.md   | 2 +-
 .../ExchangePowerShell/Add-DistributionGroupMember.md           | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Add-FederatedDomain.md  | 2 +-
 .../ExchangePowerShell/Add-GlobalMonitoringOverride.md          | 2 +-
 .../exchange-ps/ExchangePowerShell/Add-MailboxDatabaseCopy.md   | 2 +-
 .../ExchangePowerShell/Add-MailboxFolderPermission.md           | 2 +-
 .../exchange-ps/ExchangePowerShell/Add-MailboxPermission.md     | 2 +-
 .../exchange-ps/ExchangePowerShell/Add-ManagementRoleEntry.md   | 2 +-
 .../Add-PublicFolderAdministrativePermission.md                 | 2 +-
 .../ExchangePowerShell/Add-PublicFolderClientPermission.md      | 2 +-
 .../exchange-ps/ExchangePowerShell/Add-RecipientPermission.md   | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Add-ResubmitRequest.md  | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Add-RoleGroupMember.md  | 2 +-
 .../ExchangePowerShell/Add-ServerMonitoringOverride.md          | 2 +-
 .../exchange-ps/ExchangePowerShell/Add-UnifiedGroupLinks.md     | 2 +-
 .../exchange-ps/ExchangePowerShell/Clean-MailboxDatabase.md     | 2 +-
 .../exchange-ps/ExchangePowerShell/Clear-ActiveSyncDevice.md    | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Clear-MobileDevice.md   | 2 +-
 .../ExchangePowerShell/Clear-TextMessagingAccount.md            | 2 +-
 .../ExchangePowerShell/Compare-TextMessagingVerificationCode.md | 2 +-
 .../exchange-ps/ExchangePowerShell/Complete-MigrationBatch.md   | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Connect-Mailbox.md      | 2 +-
 .../exchange-ps/ExchangePowerShell/Delete-QuarantineMessage.md  | 2 +-
 .../ExchangePowerShell/Disable-ATPProtectionPolicyRule.md       | 2 +-
 .../exchange-ps/ExchangePowerShell/Disable-AddressListPaging.md | 2 +-
 .../exchange-ps/ExchangePowerShell/Disable-AntiPhishRule.md     | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Disable-App.md          | 2 +-
 .../ExchangePowerShell/Disable-CmdletExtensionAgent.md          | 2 +-
 .../exchange-ps/ExchangePowerShell/Disable-DistributionGroup.md | 2 +-
 .../ExchangePowerShell/Disable-DnssecForVerifiedDomain.md       | 2 +-
 .../ExchangePowerShell/Disable-EOPProtectionPolicyRule.md       | 2 +-
 .../ExchangePowerShell/Disable-HostedContentFilterRule.md       | 2 +-
 .../ExchangePowerShell/Disable-HostedOutboundSpamFilterRule.md  | 2 +-
 .../ExchangePowerShell/Disable-IPv6ForAcceptedDomain.md         | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Disable-InboxRule.md    | 2 +-
 .../exchange-ps/ExchangePowerShell/Disable-JournalArchiving.md  | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Disable-JournalRule.md  | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Disable-MailContact.md  | 2 +-
 .../exchange-ps/ExchangePowerShell/Disable-MailPublicFolder.md  | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Disable-MailUser.md     | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Disable-Mailbox.md      | 2 +-
 .../exchange-ps/ExchangePowerShell/Disable-MailboxQuarantine.md | 2 +-
 .../exchange-ps/ExchangePowerShell/Disable-MalwareFilterRule.md | 2 +-
 .../exchange-ps/ExchangePowerShell/Disable-MetaCacheDatabase.md | 2 +-
 .../exchange-ps/ExchangePowerShell/Disable-OutlookAnywhere.md   | 2 +-
 .../ExchangePowerShell/Disable-OutlookProtectionRule.md         | 2 +-
 .../ExchangePowerShell/Disable-PushNotificationProxy.md         | 2 +-
 .../exchange-ps/ExchangePowerShell/Disable-RemoteMailbox.md     | 2 +-
 .../ExchangePowerShell/Disable-ReportSubmissionRule.md          | 2 +-
 .../ExchangePowerShell/Disable-SafeAttachmentRule.md            | 2 +-
 .../exchange-ps/ExchangePowerShell/Disable-SafeLinksRule.md     | 2 +-
 .../ExchangePowerShell/Disable-ServiceEmailChannel.md           | 2 +-
 .../exchange-ps/ExchangePowerShell/Disable-SmtpDaneInbound.md   | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Disable-SweepRule.md    | 2 +-
 .../exchange-ps/ExchangePowerShell/Disable-TransportAgent.md    | 2 +-
 .../exchange-ps/ExchangePowerShell/Disable-TransportRule.md     | 2 +-
 .../exchange-ps/ExchangePowerShell/Disable-UMAutoAttendant.md   | 2 +-
 .../ExchangePowerShell/Disable-UMCallAnsweringRule.md           | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Disable-UMIPGateway.md  | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Disable-UMMailbox.md    | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Disable-UMServer.md     | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Disable-UMService.md    | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Dismount-Database.md    | 2 +-
 .../exchange-ps/ExchangePowerShell/Dump-ProvisioningCache.md    | 2 +-
 .../ExchangePowerShell/Enable-ATPProtectionPolicyRule.md        | 2 +-
 .../exchange-ps/ExchangePowerShell/Enable-AddressListPaging.md  | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Enable-AntiPhishRule.md | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Enable-App.md           | 2 +-
 .../ExchangePowerShell/Enable-CmdletExtensionAgent.md           | 2 +-
 .../exchange-ps/ExchangePowerShell/Enable-DistributionGroup.md  | 2 +-
 .../ExchangePowerShell/Enable-DnssecForVerifiedDomain.md        | 2 +-
 .../ExchangePowerShell/Enable-EOPProtectionPolicyRule.md        | 2 +-
 .../ExchangePowerShell/Enable-ExchangeCertificate.md            | 2 +-
 .../ExchangePowerShell/Enable-HostedContentFilterRule.md        | 2 +-
 .../ExchangePowerShell/Enable-HostedOutboundSpamFilterRule.md   | 2 +-
 .../ExchangePowerShell/Enable-IPv6ForAcceptedDomain.md          | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Enable-InboxRule.md     | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Enable-JournalRule.md   | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Enable-MailContact.md   | 2 +-
 .../exchange-ps/ExchangePowerShell/Enable-MailPublicFolder.md   | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Enable-MailUser.md      | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Enable-Mailbox.md       | 2 +-
 .../exchange-ps/ExchangePowerShell/Enable-MailboxQuarantine.md  | 2 +-
 .../exchange-ps/ExchangePowerShell/Enable-MalwareFilterRule.md  | 2 +-
 .../exchange-ps/ExchangePowerShell/Enable-MetaCacheDatabase.md  | 2 +-
 .../ExchangePowerShell/Enable-OrganizationCustomization.md      | 2 +-
 .../exchange-ps/ExchangePowerShell/Enable-OutlookAnywhere.md    | 2 +-
 .../ExchangePowerShell/Enable-OutlookProtectionRule.md          | 2 +-
 .../ExchangePowerShell/Enable-PushNotificationProxy.md          | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Enable-RemoteMailbox.md | 2 +-
 .../ExchangePowerShell/Enable-ReportSubmissionRule.md           | 2 +-
 .../exchange-ps/ExchangePowerShell/Enable-SafeAttachmentRule.md | 2 +-
 95 files changed, 95 insertions(+), 95 deletions(-)

diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-ADPermission.md b/exchange/exchange-ps/ExchangePowerShell/Add-ADPermission.md
index 14512499ab..9b7f139ea5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-ADPermission.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Add-ADPermission.md
@@ -66,7 +66,7 @@ Add-ADPermission [[-Identity] <ADRawEntryIdParameter>] -Instance <ADAcePresentat
 ## DESCRIPTION
 The ADPermission cmdlets can be used to directly modify Active Directory access control lists (ACLs). Although some Microsoft Exchange features might continue to use the ADPermission cmdlets to manage permissions (for example Send and Receive connectors), Exchange 2013 and later versions no longer use customized ACLs to manage administrative permissions. If you want to grant or deny administrative permissions in Exchange 2013 or later, you need to use Role Based Access Control (RBAC). For more information about RBAC, see [Permissions in Exchange Server](https://learn.microsoft.com/Exchange/permissions/permissions).
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-AvailabilityAddressSpace.md b/exchange/exchange-ps/ExchangePowerShell/Add-AvailabilityAddressSpace.md
index 6260a607b7..b07f62ef9e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-AvailabilityAddressSpace.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Add-AvailabilityAddressSpace.md
@@ -40,7 +40,7 @@ Add-AvailabilityAddressSpace -AccessMethod <AvailabilityAccessMethod> -ForestNam
 ## DESCRIPTION
 In Exchange Online, you need to run the New-AvailabilityConfig cmdlet before you run the Add-AvailabilityAddressSpace cmdlet.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-ContentFilterPhrase.md b/exchange/exchange-ps/ExchangePowerShell/Add-ContentFilterPhrase.md
index ccaca37c2f..7e7cef98c9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-ContentFilterPhrase.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Add-ContentFilterPhrase.md
@@ -32,7 +32,7 @@ Add-ContentFilterPhrase [-Phrase] <String> -Influence <Influence>
 ## DESCRIPTION
 The Add-ContentFilterPhrase cmdlet adds phrases to the Allow or Block phrases list.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-DatabaseAvailabilityGroupServer.md b/exchange/exchange-ps/ExchangePowerShell/Add-DatabaseAvailabilityGroupServer.md
index 270c31ad74..8773c97f8a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-DatabaseAvailabilityGroupServer.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Add-DatabaseAvailabilityGroupServer.md
@@ -37,7 +37,7 @@ To add a Mailbox server to a DAG, the Mailbox server must be running the Windows
 
 To add the first server to a DAG and create a computer object for the DAG, the Exchange Windows Permissions security group must have the appropriate rights to add computer accounts to the domain. Alternatively, a computer account can be created and disabled prior to adding the server. Adding the first server to the DAG enables the computer account for the DAG. Thus, the account used for the task doesn't need permissions to add a computer account to the domain. If you're pre-creating the computer account, the name of the account must match the name for the DAG. For example, if the DAG is named DAG1, the computer account must be named DAG1.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-DistributionGroupMember.md b/exchange/exchange-ps/ExchangePowerShell/Add-DistributionGroupMember.md
index b9bf4d3aa9..7b4aa8a16e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-DistributionGroupMember.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Add-DistributionGroupMember.md
@@ -32,7 +32,7 @@ Add-DistributionGroupMember [-Identity] <DistributionGroupIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-FederatedDomain.md b/exchange/exchange-ps/ExchangePowerShell/Add-FederatedDomain.md
index 99df25b20e..a955e3dbaa 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-FederatedDomain.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Add-FederatedDomain.md
@@ -36,7 +36,7 @@ You can add any registered Internet domain to the federated organization identif
 
 For more details, see [Federation](https://learn.microsoft.com/exchange/federation-exchange-2013-help).
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-GlobalMonitoringOverride.md b/exchange/exchange-ps/ExchangePowerShell/Add-GlobalMonitoringOverride.md
index c8cbb2af7c..8a81090517 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-GlobalMonitoringOverride.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Add-GlobalMonitoringOverride.md
@@ -44,7 +44,7 @@ Add-GlobalMonitoringOverride [-Identity] <String> -ItemType <MonitoringItemTypeE
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-MailboxDatabaseCopy.md b/exchange/exchange-ps/ExchangePowerShell/Add-MailboxDatabaseCopy.md
index b5d228a706..c76c4e5760 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-MailboxDatabaseCopy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Add-MailboxDatabaseCopy.md
@@ -45,7 +45,7 @@ To use the Add-MailboxDatabaseCopy cmdlet to add a mailbox database copy, the fo
 
 After running the Add-MailboxDatabaseCopy cmdlet, the new copy remains in a Suspended state if the SeedingPostponed parameter is specified. When the database copy status is set to Suspended, the SuspendMessage is set to "Replication is suspended for database copy '{0}' because database needs to be seeded."
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-MailboxFolderPermission.md b/exchange/exchange-ps/ExchangePowerShell/Add-MailboxFolderPermission.md
index 1b2f8ebb8e..93f7798c11 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-MailboxFolderPermission.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Add-MailboxFolderPermission.md
@@ -34,7 +34,7 @@ Add-MailboxFolderPermission [-Identity] <MailboxFolderIdParameter> -AccessRights
 ## DESCRIPTION
 To modify the permissions that are assigned to the user on a mailbox folder, use the Set-MailboxFolderPermission cmdlet. To remove all permissions that are assigned to a user on a mailbox folder, use the Remove-MailboxFolderPermission cmdlet.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-MailboxPermission.md b/exchange/exchange-ps/ExchangePowerShell/Add-MailboxPermission.md
index 893d646309..e3d74dcb35 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-MailboxPermission.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Add-MailboxPermission.md
@@ -67,7 +67,7 @@ Add-MailboxPermission [[-Identity] <MailboxIdParameter>] -Instance <MailboxAcePr
 > [!NOTE]
 > You can use this cmdlet to add a maximum of 500 permission entries (ACEs) to a mailbox. To grant permissions to more than 500 users, use security groups instead of individual users for the User parameter. Security groups contain many members, but only count as one entry.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-ManagementRoleEntry.md b/exchange/exchange-ps/ExchangePowerShell/Add-ManagementRoleEntry.md
index 29a7f33b0f..ae6c6b0762 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-ManagementRoleEntry.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Add-ManagementRoleEntry.md
@@ -54,7 +54,7 @@ You can only add a role entry to a management role if the role entry exists in t
 
 For more information about management role entries, see [Understanding management roles](https://learn.microsoft.com/exchange/understanding-management-roles-exchange-2013-help).
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-PublicFolderAdministrativePermission.md b/exchange/exchange-ps/ExchangePowerShell/Add-PublicFolderAdministrativePermission.md
index 58bb304fa4..7cc7bfea5a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-PublicFolderAdministrativePermission.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Add-PublicFolderAdministrativePermission.md
@@ -58,7 +58,7 @@ Add-PublicFolderAdministrativePermission [-Identity] <PublicFolderIdParameter> -
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-PublicFolderClientPermission.md b/exchange/exchange-ps/ExchangePowerShell/Add-PublicFolderClientPermission.md
index 67c5796bd3..8bfbcd9ac9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-PublicFolderClientPermission.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Add-PublicFolderClientPermission.md
@@ -31,7 +31,7 @@ Add-PublicFolderClientPermission [-Identity] <PublicFolderIdParameter> -AccessRi
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-RecipientPermission.md b/exchange/exchange-ps/ExchangePowerShell/Add-RecipientPermission.md
index e6aa528fc3..e1708d0560 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-RecipientPermission.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Add-RecipientPermission.md
@@ -31,7 +31,7 @@ Add-RecipientPermission [-Identity] <RecipientIdParameter> -AccessRights <MultiV
 ## DESCRIPTION
 SendAs permission allows a user or group members to send messages that appear to come from the specified mailbox, mail contact, mail user, or group.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-ResubmitRequest.md b/exchange/exchange-ps/ExchangePowerShell/Add-ResubmitRequest.md
index fd3ed1aef1..74bb47fd4f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-ResubmitRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Add-ResubmitRequest.md
@@ -51,7 +51,7 @@ Add-ResubmitRequest -EndTime <DateTime> -StartTime <DateTime>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-RoleGroupMember.md b/exchange/exchange-ps/ExchangePowerShell/Add-RoleGroupMember.md
index 51471eb69b..a700deba46 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-RoleGroupMember.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Add-RoleGroupMember.md
@@ -39,7 +39,7 @@ In on-premises Exchange, if the role group is a linked role group, you can't use
 
 For more information about role groups, see [Understanding management role groups](https://learn.microsoft.com/exchange/understanding-management-role-groups-exchange-2013-help).
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-ServerMonitoringOverride.md b/exchange/exchange-ps/ExchangePowerShell/Add-ServerMonitoringOverride.md
index 868e0d75a3..d0ca5ec943 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-ServerMonitoringOverride.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Add-ServerMonitoringOverride.md
@@ -39,7 +39,7 @@ Add-ServerMonitoringOverride [-Identity] <String> -ItemType <MonitoringItemTypeE
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-UnifiedGroupLinks.md b/exchange/exchange-ps/ExchangePowerShell/Add-UnifiedGroupLinks.md
index dd5eb3475f..4e1ade63bf 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-UnifiedGroupLinks.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Add-UnifiedGroupLinks.md
@@ -36,7 +36,7 @@ Add-UnifiedGroupLinks [-Identity] <UnifiedGroupIdParameter> -Links <RecipientIdP
 ## DESCRIPTION
 Microsoft 365 Groups are group objects that are available across Microsoft 365 services.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 **Note**: Only members can be owners of a group, so you must first add a user as member before adding it as an owner. Guest users can't be an owner of groups, even if the users are members of the groups.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Clean-MailboxDatabase.md b/exchange/exchange-ps/ExchangePowerShell/Clean-MailboxDatabase.md
index c43e7bb860..7908ebabdd 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Clean-MailboxDatabase.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Clean-MailboxDatabase.md
@@ -36,7 +36,7 @@ If you want to reconnect a disconnected mailbox to an Active Directory user acco
 
 Under normal circumstances, it isn't necessary to run the Clean-MailboxDatabase cmdlet because a mailbox is marked as disconnected immediately after the Disable-Mailbox or Remove-Mailbox command completes. If you used the Disable-Mailbox cmdlet or the Remove-Mailbox cmdlet while the Microsoft Exchange Information Store service was stopped, or if a mailbox was disabled by an external means other than the Disable-Mailbox cmdlet or Remove-Mailbox cmdlet, you might want to use the Clean-MailboxDatabase cmdlet to scan for disconnected mailboxes.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Clear-ActiveSyncDevice.md b/exchange/exchange-ps/ExchangePowerShell/Clear-ActiveSyncDevice.md
index e4b6f04148..2a911c759e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Clear-ActiveSyncDevice.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Clear-ActiveSyncDevice.md
@@ -38,7 +38,7 @@ The Clear-ActiveSyncDevice cmdlet deletes all user data from a mobile device the
 
 After you run this cmdlet, you receive a warning that states: "This command will force all the data on the device to be permanently deleted. Do you want to continue?" You must respond to the warning for the cmdlet to run on the mobile phone.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Clear-MobileDevice.md b/exchange/exchange-ps/ExchangePowerShell/Clear-MobileDevice.md
index 5e979a1257..c202f39495 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Clear-MobileDevice.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Clear-MobileDevice.md
@@ -37,7 +37,7 @@ The Clear-MobileDevice cmdlet deletes all user data from a mobile device the nex
 
 After you run this cmdlet, you receive a warning that states: "This command will force all the data on the device to be permanently deleted. Do you want to continue?" You must respond to the warning for the cmdlet to run on the mobile phone.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Clear-TextMessagingAccount.md b/exchange/exchange-ps/ExchangePowerShell/Clear-TextMessagingAccount.md
index 9e32e22536..e68025ff05 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Clear-TextMessagingAccount.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Clear-TextMessagingAccount.md
@@ -33,7 +33,7 @@ Clear-TextMessagingAccount [-Identity] <MailboxIdParameter>
 ## DESCRIPTION
 The Clear-TextMessagingAccount cmdlet clears all of a user's text messaging settings, including communication and notification settings.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Compare-TextMessagingVerificationCode.md b/exchange/exchange-ps/ExchangePowerShell/Compare-TextMessagingVerificationCode.md
index 2c69601d73..83845e82d0 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Compare-TextMessagingVerificationCode.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Compare-TextMessagingVerificationCode.md
@@ -34,7 +34,7 @@ The Compare-TextMessagingVerificationCode cmdlet returns the value true if the c
 
 When text messaging notifications are enabled on a mailbox, you can configure calendar notifications, voice mail notifications, and email notifications using an inbox rule.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Complete-MigrationBatch.md b/exchange/exchange-ps/ExchangePowerShell/Complete-MigrationBatch.md
index 47da89c99b..a8ed9f625e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Complete-MigrationBatch.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Complete-MigrationBatch.md
@@ -46,7 +46,7 @@ When the finalization process is complete, you can remove the batch by using the
 
 If a migration batch has a status of Completed with Errors, you can re-attempt to finalize the failed users. In Exchange Online, use the Start-MigrationBatch cmdlet to retry migration for failed users. In Exchange 2013 or Exchange 2016, use the Complete-MigrationBatch to retry these failed users.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Connect-Mailbox.md b/exchange/exchange-ps/ExchangePowerShell/Connect-Mailbox.md
index cdf4d75bf3..8d4f60535b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Connect-Mailbox.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Connect-Mailbox.md
@@ -132,7 +132,7 @@ Use the Remove-Mailbox cmdlet to:
 - Keep the mailbox in the disabled state before it's permanently deleted, subject to the deleted mailbox retention period (except if you use the Permanent or StoreMailboxIdentity parameters, which immediately deletes the mailbox from the database).
 - Remove the user account.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Delete-QuarantineMessage.md b/exchange/exchange-ps/ExchangePowerShell/Delete-QuarantineMessage.md
index c071bd6c30..eaa566a1f2 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Delete-QuarantineMessage.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Delete-QuarantineMessage.md
@@ -45,7 +45,7 @@ Delete-QuarantineMessage -Identity <QuarantineMessageIdentity>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-ATPProtectionPolicyRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-ATPProtectionPolicyRule.md
index cec4891367..55e5a4c0fd 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-ATPProtectionPolicyRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-ATPProtectionPolicyRule.md
@@ -33,7 +33,7 @@ The State property in rules that are associated with preset security policies in
 
 For more information about preset security policies in PowerShell, see [Preset security policies in Exchange Online PowerShell](https://learn.microsoft.com/defender-office-365/preset-security-policies#preset-security-policies-in-exchange-online-powershell).
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-AddressListPaging.md b/exchange/exchange-ps/ExchangePowerShell/Disable-AddressListPaging.md
index 1de3a4b7fd..c525408a82 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-AddressListPaging.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-AddressListPaging.md
@@ -29,7 +29,7 @@ Disable-AddressListPaging [-Confirm]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-AntiPhishRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-AntiPhishRule.md
index 7660a78413..3773a17e34 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-AntiPhishRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-AntiPhishRule.md
@@ -29,7 +29,7 @@ Disable-AntiPhishRule [-Identity] <RuleIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-App.md b/exchange/exchange-ps/ExchangePowerShell/Disable-App.md
index ce690bd262..c176a7102c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-App.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-App.md
@@ -35,7 +35,7 @@ The Disable-App cmdlet requires that the specified app has already been installe
 
 For more information, see [Manage user access to add-ins for Outlook in Exchange Server](https://learn.microsoft.com/Exchange/manage-user-access-to-add-ins-exchange-2013-help) and [Manage deployment of add-ins in the Microsoft 365 admin center](https://learn.microsoft.com/office365/admin/manage/manage-deployment-of-add-ins).
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-CmdletExtensionAgent.md b/exchange/exchange-ps/ExchangePowerShell/Disable-CmdletExtensionAgent.md
index a61981d05a..1ba7f512d3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-CmdletExtensionAgent.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-CmdletExtensionAgent.md
@@ -34,7 +34,7 @@ Cmdlet extension agents are used by Exchange cmdlets in Exchange Server 2010 and
 
 When you disable a cmdlet extension agent, the agent is disabled for the entire organization. When an agent is disabled, it's not made available to cmdlets. Cmdlets can no longer use the agent to perform additional operations.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-DistributionGroup.md b/exchange/exchange-ps/ExchangePowerShell/Disable-DistributionGroup.md
index 99d3dee368..81854c040f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-DistributionGroup.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-DistributionGroup.md
@@ -33,7 +33,7 @@ Disable-DistributionGroup [-Identity] <DistributionGroupIdParameter>
 ## DESCRIPTION
 The Disable-DistributionGroup cmdlet mail-disables existing mail-enabled security groups and distribution groups by removing the email attributes that are required by Exchange. Mail-disabled groups are invisible to the \*-DistributionGroup cmdlets (with the exception of Enable-DistributionGroup). All groups (mail-enabled or not) are visible to the Get-Group and Set-Group cmdlets.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-DnssecForVerifiedDomain.md b/exchange/exchange-ps/ExchangePowerShell/Disable-DnssecForVerifiedDomain.md
index 920747bf5b..41c64fcc70 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-DnssecForVerifiedDomain.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-DnssecForVerifiedDomain.md
@@ -31,7 +31,7 @@ Disable-DnssecForVerifiedDomain [-DomainName] <String>
 ## DESCRIPTION
 For more information about debugging, enabling, and disabling SMTP DANE with DNSSEC, see [How SMTP DANE works](https://learn.microsoft.com/purview/how-smtp-dane-works).
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-EOPProtectionPolicyRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-EOPProtectionPolicyRule.md
index 2dd8ae99b5..0a8a006a20 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-EOPProtectionPolicyRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-EOPProtectionPolicyRule.md
@@ -33,7 +33,7 @@ The State property in rules that are associated with preset security policies in
 
 For more information about preset security policies in PowerShell, see [Preset security policies in Exchange Online PowerShell](https://learn.microsoft.com/defender-office-365/preset-security-policies#preset-security-policies-in-exchange-online-powershell).
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-HostedContentFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-HostedContentFilterRule.md
index 78dae763c9..bc31eef052 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-HostedContentFilterRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-HostedContentFilterRule.md
@@ -29,7 +29,7 @@ Disable-HostedContentFilterRule [-Identity] <RuleIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-HostedOutboundSpamFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-HostedOutboundSpamFilterRule.md
index 4ebd303216..4b73d2012f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-HostedOutboundSpamFilterRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-HostedOutboundSpamFilterRule.md
@@ -29,7 +29,7 @@ Disable-HostedOutboundSpamFilterRule [-Identity] <RuleIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-IPv6ForAcceptedDomain.md b/exchange/exchange-ps/ExchangePowerShell/Disable-IPv6ForAcceptedDomain.md
index bb1c87a9ed..799ceca694 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-IPv6ForAcceptedDomain.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-IPv6ForAcceptedDomain.md
@@ -32,7 +32,7 @@ Use the Get-AcceptedDomain cmdlet to return accepted domains in the Exchange Onl
 
 If IPv6 is enabled for an accepted domain in Exchange Online, IPv4 and IPv6 addresses are returned in DNS queries for mail flow records of the domain. If IPv6 is disabled, only IPv4 addresses are returned in DNS queries for mail flow records of the domain.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-InboxRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-InboxRule.md
index fc46a1d3e0..dde3d20511 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-InboxRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-InboxRule.md
@@ -35,7 +35,7 @@ Disable-InboxRule [-Identity] <InboxRuleIdParameter>
 ## DESCRIPTION
 When you create, modify, remove, enable, or disable an Inbox rule in Exchange PowerShell, any client-side rules created by Microsoft Outlook are removed.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-JournalArchiving.md b/exchange/exchange-ps/ExchangePowerShell/Disable-JournalArchiving.md
index 6fed3d1538..e8dfd114a9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-JournalArchiving.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-JournalArchiving.md
@@ -36,7 +36,7 @@ The Disable-JournalArchiving cmdlet removes the mail user and converts the journ
 
 In hybrid organizations that use DirSync, this cmdlet doesn't remove the mail user. Removal of the mail user is handled by DirSync.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-JournalRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-JournalRule.md
index b15185faa4..c2e684786c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-JournalRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-JournalRule.md
@@ -32,7 +32,7 @@ Disable-JournalRule -Identity <RuleIdParameter>
 ## DESCRIPTION
 You can enable or disable specific journal rules in your organization at any time using the Disable-JournalRule and Enable-JournalRule cmdlets.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-MailContact.md b/exchange/exchange-ps/ExchangePowerShell/Disable-MailContact.md
index 451238f746..66d3cc5e91 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-MailContact.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-MailContact.md
@@ -33,7 +33,7 @@ Disable-MailContact [-Identity] <MailContactIdParameter>
 ## DESCRIPTION
 The Disable-MailContact cmdlet mail-disables existing mail contacts by removing the email attributes that are required by Exchange. Mail-disabled contacts are invisible to the \*-MailContact cmdlets (with the exception of Enable-MailContact). All contacts (mail-enabled or not) are visible to the Get-Contact and Set-Contact cmdlets.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-MailPublicFolder.md b/exchange/exchange-ps/ExchangePowerShell/Disable-MailPublicFolder.md
index fe5bfbe28b..19e6f06e0d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-MailPublicFolder.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-MailPublicFolder.md
@@ -31,7 +31,7 @@ Disable-MailPublicFolder [-Identity] <PublicFolderIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-MailUser.md b/exchange/exchange-ps/ExchangePowerShell/Disable-MailUser.md
index 7b7effd7ff..3bc30aea90 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-MailUser.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-MailUser.md
@@ -34,7 +34,7 @@ Disable-MailUser [-Identity] <MailUserIdParameter>
 ## DESCRIPTION
 The Disable-MailUser cmdlet mail-disables existing mail users by removing the email attributes that are required by Exchange. Mail-disabled users are invisible to the \*-MailUser cmdlets (with the exception of Enable-MailUser). All users (mail-enabled or not) are visible to the Get-User and Set-User cmdlets.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-Mailbox.md b/exchange/exchange-ps/ExchangePowerShell/Disable-Mailbox.md
index 4edb38bb6f..ffd3bd0dd9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-Mailbox.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-Mailbox.md
@@ -79,7 +79,7 @@ The Disable-Mailbox cmdlet also performs the clean-up task on the individual mai
 
 Under normal circumstances, a mailbox is marked as disconnected immediately after the Disable-Mailbox or Remove-Mailbox command completes. However, if the mailbox was disabled or removed while the Exchange Information Store service was stopped, or if it was disabled or removed by an external means other than Exchange management interfaces, the status of the mailbox object in the Exchange mailbox database isn't marked as disconnected.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-MailboxQuarantine.md b/exchange/exchange-ps/ExchangePowerShell/Disable-MailboxQuarantine.md
index 7082e77db1..69bd293167 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-MailboxQuarantine.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-MailboxQuarantine.md
@@ -70,7 +70,7 @@ Disable-MailboxQuarantine -Server <ServerIdParameter>
 ## DESCRIPTION
 Mailboxes are quarantined when they affect the availability of the mailbox database. Typically a software fix from Microsoft is required before releasing a mailbox from quarantine. If a fix isn't deployed before releasing the mailbox, the quarantine on the mailbox is re-enabled if the condition recurs. The default quarantine duration is 24 hours.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-MalwareFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-MalwareFilterRule.md
index 8127d10f40..3135c19f76 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-MalwareFilterRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-MalwareFilterRule.md
@@ -30,7 +30,7 @@ Disable-MalwareFilterRule [-Identity] <RuleIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-MetaCacheDatabase.md b/exchange/exchange-ps/ExchangePowerShell/Disable-MetaCacheDatabase.md
index f6ff4cfdb9..cff0f8762f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-MetaCacheDatabase.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-MetaCacheDatabase.md
@@ -29,7 +29,7 @@ Disable-MetaCacheDatabase -Server <String[]>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-OutlookAnywhere.md b/exchange/exchange-ps/ExchangePowerShell/Disable-OutlookAnywhere.md
index f34bfa0d4a..2be4362dad 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-OutlookAnywhere.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-OutlookAnywhere.md
@@ -46,7 +46,7 @@ When you run this cmdlet, it can take as long as an hour for the settings to bec
 
 After the Client Access server is disabled for Outlook Anywhere, you might want to remove the RPC over HTTP proxy Windows networking component.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-OutlookProtectionRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-OutlookProtectionRule.md
index 1b77ff5b57..f294454b97 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-OutlookProtectionRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-OutlookProtectionRule.md
@@ -36,7 +36,7 @@ Outlook protection rules are administrator-created rules applied before a user s
 
 For more information, see [Outlook protection rules](https://learn.microsoft.com/exchange/outlook-protection-rules-exchange-2013-help).
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-PushNotificationProxy.md b/exchange/exchange-ps/ExchangePowerShell/Disable-PushNotificationProxy.md
index 355b7fb189..45364575b0 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-PushNotificationProxy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-PushNotificationProxy.md
@@ -30,7 +30,7 @@ Disable-PushNotificationProxy [-Confirm]
 ## DESCRIPTION
 The push notification proxy relays event notifications (for example, new email or calendar updates) for on-premises mailboxes through Microsoft 365 to Outlook on the web for devices on the user's device.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-RemoteMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Disable-RemoteMailbox.md
index b6ec895fe5..ce5291ee76 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-RemoteMailbox.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-RemoteMailbox.md
@@ -47,7 +47,7 @@ Directory synchronization must be configured correctly for a mailbox to be remov
 - If you are deprovisioning a cloud mailbox and its associated online archive, you must first disable the online archive with the command `Disable-RemoteMailbox <User> -Archive` and then perform a directory synchronization prior to disabling the remote mailbox. Attempting to disable both the online archive and cloud mailbox without a sync between them might result in an ArchiveGuid mismatch and validation error.
 - Due to the current service architecture, you need to convert shared mailboxes to user mailboxes prior to running the Disable-RemoteMailbox cmdlet.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-ReportSubmissionRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-ReportSubmissionRule.md
index a55a45da61..95727eff23 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-ReportSubmissionRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-ReportSubmissionRule.md
@@ -29,7 +29,7 @@ Disable-ReportSubmissionRule [-Identity] <RuleIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-SafeAttachmentRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-SafeAttachmentRule.md
index 10fba35caf..ee21f6286e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-SafeAttachmentRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-SafeAttachmentRule.md
@@ -31,7 +31,7 @@ Disable-SafeAttachmentRule [-Identity] <RuleIdParameter>
 ## DESCRIPTION
 Safe Attachments is a feature in Microsoft Defender for Office 365 that opens email attachments in a special hypervisor environment to detect malicious activity. For more information, see [Safe Attachments in Defender for Office 365](https://learn.microsoft.com/defender-office-365/safe-attachments-about).
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-SafeLinksRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-SafeLinksRule.md
index e9ce882e5f..24f062ac31 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-SafeLinksRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-SafeLinksRule.md
@@ -31,7 +31,7 @@ Disable-SafeLinksRule [-Identity] <RuleIdParameter>
 ## DESCRIPTION
 Safe Links is a feature in Microsoft Defender for Office 365 that checks links in email messages to see if they lead to malicious web sites. When a user clicks a link in a message, the URL is temporarily rewritten and checked against a list of known, malicious web sites. Safe Links includes the URL trace reporting feature to help determine who has clicked through to a malicious web site.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-ServiceEmailChannel.md b/exchange/exchange-ps/ExchangePowerShell/Disable-ServiceEmailChannel.md
index 3b3cacc2ab..66799f5106 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-ServiceEmailChannel.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-ServiceEmailChannel.md
@@ -32,7 +32,7 @@ Disable-ServiceEmailChannel [-Identity] <MailboxIdParameter>
 ## DESCRIPTION
 The Disable-ServiceEmailChannel cmdlet deletes the receive folder in the user's mailbox under the root folder.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-SmtpDaneInbound.md b/exchange/exchange-ps/ExchangePowerShell/Disable-SmtpDaneInbound.md
index 3ee2297558..9c28890fee 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-SmtpDaneInbound.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-SmtpDaneInbound.md
@@ -31,7 +31,7 @@ Disable-SmtpDaneInbound [-DomainName] <String>
 ## DESCRIPTION
 For more information about debugging, enabling, and disabling SMTP DANE with DNSSEC, see [How SMTP DANE works](https://learn.microsoft.com/purview/how-smtp-dane-works).
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-SweepRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-SweepRule.md
index ba335e644f..5049dce174 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-SweepRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-SweepRule.md
@@ -31,7 +31,7 @@ Disable-SweepRule [-Identity] <SweepRuleIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-TransportAgent.md b/exchange/exchange-ps/ExchangePowerShell/Disable-TransportAgent.md
index a70c5a9d46..675098e0b9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-TransportAgent.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-TransportAgent.md
@@ -31,7 +31,7 @@ Disable-TransportAgent [-Identity] <TransportAgentObjectId>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-TransportRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-TransportRule.md
index 2486bc58e6..72a6cd1f6e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-TransportRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-TransportRule.md
@@ -32,7 +32,7 @@ Disable-TransportRule [-Identity] <RuleIdParameter>
 ## DESCRIPTION
 To enable rules that are disabled, use the Enable-TransportRule cmdlet.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-UMAutoAttendant.md b/exchange/exchange-ps/ExchangePowerShell/Disable-UMAutoAttendant.md
index 6d848275c1..55d93cb30b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-UMAutoAttendant.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-UMAutoAttendant.md
@@ -34,7 +34,7 @@ The Disable-UMAutoAttendant cmdlet disables an existing UM auto attendant that's
 
 After this task is completed, the UM auto attendant is disabled and doesn't accept incoming calls.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-UMCallAnsweringRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-UMCallAnsweringRule.md
index 0d7ed908bd..83930d80a6 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-UMCallAnsweringRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-UMCallAnsweringRule.md
@@ -35,7 +35,7 @@ The Disable-UMCallAnsweringRule cmdlet disables the call answering rule by modif
 
 When the call answering rule is created, you should disable the call answering rule when you're setting up conditions and actions. This prevents the call answering rule from being processed when an incoming call is received until you've correctly configured the call answering rule. After this task is completed, the cmdlet sets the parameters and the values specified.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-UMIPGateway.md b/exchange/exchange-ps/ExchangePowerShell/Disable-UMIPGateway.md
index db54c5c88d..99d701cbe6 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-UMIPGateway.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-UMIPGateway.md
@@ -33,7 +33,7 @@ Disable-UMIPGateway [-Identity] <UMIPGatewayIdParameter>
 ## DESCRIPTION
 The status variable for a UM IP gateway can be used to enable or disable call answering destined for the IP gateway. The Disable-UMIPGateway cmdlet disables a UM IP gateway in Active Directory by modifying its status variable. After this task is completed, the UM IP gateway no longer answers incoming calls or makes outgoing calls.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-UMMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Disable-UMMailbox.md
index ae4ee00bda..de6a75d801 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-UMMailbox.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-UMMailbox.md
@@ -34,7 +34,7 @@ Disable-UMMailbox [-Identity] <MailboxIdParameter>
 ## DESCRIPTION
 After the mailbox is disabled for Unified Messaging, the user can no longer use the UM features that are included in Microsoft Exchange and the Microsoft Exchange Unified Messaging service no longer handle calls for the associated extension number. The mailbox continues to function normally for all other operations that are unrelated to Unified Messaging.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-UMServer.md b/exchange/exchange-ps/ExchangePowerShell/Disable-UMServer.md
index 4136f0b40f..090daef048 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-UMServer.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-UMServer.md
@@ -40,7 +40,7 @@ After this task is completed, the UM server can no longer:
 - Be used to manage UM-enabled mailboxes
 - Be queried when a diagnostic task is used
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-UMService.md b/exchange/exchange-ps/ExchangePowerShell/Disable-UMService.md
index 1dff826b33..f3f2b6c64a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-UMService.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-UMService.md
@@ -42,7 +42,7 @@ After this task is completed, the UM server can no longer:
 - Be used to manage UM-enabled mailboxes.
 - Be queried when a diagnostic task is used.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Dismount-Database.md b/exchange/exchange-ps/ExchangePowerShell/Dismount-Database.md
index 2ad03daf97..27e96b01a7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Dismount-Database.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Dismount-Database.md
@@ -30,7 +30,7 @@ Dismount-Database [-Identity] <DatabaseIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Dump-ProvisioningCache.md b/exchange/exchange-ps/ExchangePowerShell/Dump-ProvisioningCache.md
index f417804b7e..0ec91c54ca 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Dump-ProvisioningCache.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Dump-ProvisioningCache.md
@@ -47,7 +47,7 @@ The Dump-ProvisioningCache cmdlet is for diagnostic purposes only and is rarely
 
 The Dump-ProvisioningCache cmdlet displays a list of the Windows PowerShell provisioning cache keys. Use the value of these cache keys with the Reset-ProvisioningCache cmdlet to reset provisioning cache data.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-ATPProtectionPolicyRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-ATPProtectionPolicyRule.md
index 543c960817..58eda1bbbf 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-ATPProtectionPolicyRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-ATPProtectionPolicyRule.md
@@ -33,7 +33,7 @@ The State property in rules that are associated with preset security policies in
 
 For more information about preset security policies in PowerShell, see [Preset security policies in Exchange Online PowerShell](https://learn.microsoft.com/defender-office-365/preset-security-policies#preset-security-policies-in-exchange-online-powershell).
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-AddressListPaging.md b/exchange/exchange-ps/ExchangePowerShell/Enable-AddressListPaging.md
index 78747343ca..bb39c286cd 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-AddressListPaging.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-AddressListPaging.md
@@ -31,7 +31,7 @@ Enable-AddressListPaging [-Confirm]
 ## DESCRIPTION
 The Enable-AddressListPaging cmdlet creates the Address List container in Active Directory. Recipient cmdlets, such as Get-Recipient, use the information written to the container to quickly retrieve recipient data.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-AntiPhishRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-AntiPhishRule.md
index 3bb397ee11..9cd62cc3f6 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-AntiPhishRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-AntiPhishRule.md
@@ -29,7 +29,7 @@ Enable-AntiPhishRule [-Identity] <RuleIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-App.md b/exchange/exchange-ps/ExchangePowerShell/Enable-App.md
index 6e033b80c9..5379a54dbe 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-App.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-App.md
@@ -35,7 +35,7 @@ The Enable-App cmdlet requires that the specified app has already been installed
 
 For more information, see [Manage user access to add-ins for Outlook in Exchange Server](https://learn.microsoft.com/Exchange/manage-user-access-to-add-ins-exchange-2013-help) and [Manage deployment of add-ins in the Microsoft 365 admin center](https://learn.microsoft.com/office365/admin/manage/manage-deployment-of-add-ins).
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-CmdletExtensionAgent.md b/exchange/exchange-ps/ExchangePowerShell/Enable-CmdletExtensionAgent.md
index bd2048d7e4..fa6ec7a67a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-CmdletExtensionAgent.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-CmdletExtensionAgent.md
@@ -36,7 +36,7 @@ When you enable a cmdlet extension agent, the agent is run on every Exchange ser
 
 Before you enable agents, be sure that you're aware of how the agent works and what effect the agent can have on your organization.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-DistributionGroup.md b/exchange/exchange-ps/ExchangePowerShell/Enable-DistributionGroup.md
index 8ef9efc43b..3c3963ce8a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-DistributionGroup.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-DistributionGroup.md
@@ -35,7 +35,7 @@ Enable-DistributionGroup [-Identity] <GroupIdParameter>
 ## DESCRIPTION
 The Enable-DistributionGroup cmdlet mail-enables existing universal security groups and universal distribution groups by adding the email attributes that are required by Exchange. Mail-enabled security groups and distribution groups are visible to the other \*-DistributionGroup cmdlets and to the \*-DistributionGroupMember cmdlets.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 In Exchange Server, the [CommonParameters](https://go.microsoft.com/fwlink/p/?LinkID=113216) InformationVariable and InformationAction don't work.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-DnssecForVerifiedDomain.md b/exchange/exchange-ps/ExchangePowerShell/Enable-DnssecForVerifiedDomain.md
index e081e366bc..d538718ea9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-DnssecForVerifiedDomain.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-DnssecForVerifiedDomain.md
@@ -33,7 +33,7 @@ The output of this cmdlet is an MX record value that you need to add to DNS for
 
 For more information about debugging, enabling, and disabling SMTP DANE with DNSSEC, see [How SMTP DANE works](https://learn.microsoft.com/purview/how-smtp-dane-works).
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-EOPProtectionPolicyRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-EOPProtectionPolicyRule.md
index 501ef067ae..a71a9634b9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-EOPProtectionPolicyRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-EOPProtectionPolicyRule.md
@@ -33,7 +33,7 @@ The State property in rules that are associated with preset security policies in
 
 For more information about preset security policies in PowerShell, see [Preset security policies in Exchange Online PowerShell](https://learn.microsoft.com/defender-office-365/preset-security-policies#preset-security-policies-in-exchange-online-powershell).
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-ExchangeCertificate.md b/exchange/exchange-ps/ExchangePowerShell/Enable-ExchangeCertificate.md
index 903cb865ed..1d42298bb7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-ExchangeCertificate.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-ExchangeCertificate.md
@@ -57,7 +57,7 @@ There are many factors to consider when you configure certificates for Transport
 
 Secure Sockets Layer (SSL) is being replaced by Transport Layer Security (TLS) as the protocol that's used to encrypt data sent between computer systems. They're so closely related that the terms "SSL" and "TLS" (without versions) are often used interchangeably. Because of this similarity, references to "SSL" in Exchange topics, the Exchange admin center, and the Exchange Management Shell have often been used to encompass both the SSL and TLS protocols. Typically, "SSL" refers to the actual SSL protocol only when a version is also provided (for example, SSL 3.0). For more information, see [Exchange Server TLS configuration best practices](https://learn.microsoft.com/Exchange/exchange-tls-configuration).
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-HostedContentFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-HostedContentFilterRule.md
index 981b7014dd..3bed2ac086 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-HostedContentFilterRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-HostedContentFilterRule.md
@@ -29,7 +29,7 @@ Enable-HostedContentFilterRule [-Identity] <RuleIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-HostedOutboundSpamFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-HostedOutboundSpamFilterRule.md
index 57e3320dfa..4db53e86eb 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-HostedOutboundSpamFilterRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-HostedOutboundSpamFilterRule.md
@@ -29,7 +29,7 @@ Enable-HostedOutboundSpamFilterRule [-Identity] <RuleIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-IPv6ForAcceptedDomain.md b/exchange/exchange-ps/ExchangePowerShell/Enable-IPv6ForAcceptedDomain.md
index 3a69a851a2..faceb49a5d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-IPv6ForAcceptedDomain.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-IPv6ForAcceptedDomain.md
@@ -32,7 +32,7 @@ Use the Get-AcceptedDomain cmdlet to return accepted domains in the Exchange Onl
 
 If IPv6 is enabled for an accepted domain in Exchange Online, IPv4 and IPv6 addresses are returned in DNS queries for mail flow records of the domain. If IPv6 is disabled, only IPv4 addresses are returned in DNS queries for mail flow records of the domain.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-InboxRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-InboxRule.md
index 59286152ae..6c3673325b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-InboxRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-InboxRule.md
@@ -35,7 +35,7 @@ Enable-InboxRule [-Identity] <InboxRuleIdParameter>
 ## DESCRIPTION
 When you create, modify, remove, enable, or disable an Inbox rule in Exchange PowerShell, any client-side rules created by Microsoft Outlook are removed.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-JournalRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-JournalRule.md
index 9f5e90cc65..244d0391ce 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-JournalRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-JournalRule.md
@@ -32,7 +32,7 @@ Enable-JournalRule [-Identity] <RuleIdParameter>
 ## DESCRIPTION
 You can enable or disable specific journal rules in your organization at any time using the Enable-JournalRule and Disable-JournalRule cmdlets. For more information, see [Journaling in Exchange Server](https://learn.microsoft.com/Exchange/policy-and-compliance/journaling/journaling).
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-MailContact.md b/exchange/exchange-ps/ExchangePowerShell/Enable-MailContact.md
index 685fc2057a..2b9a9f8fda 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-MailContact.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-MailContact.md
@@ -39,7 +39,7 @@ Enable-MailContact [-Identity] <ContactIdParameter> -ExternalEmailAddress <Proxy
 ## DESCRIPTION
 The Enable-MailContact cmdlet mail-enables existing contacts by adding the email attributes that are required by Exchange. Mail contacts are visible to the other \*-MailContact cmdlets.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-MailPublicFolder.md b/exchange/exchange-ps/ExchangePowerShell/Enable-MailPublicFolder.md
index c1f8773382..34c3553ec7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-MailPublicFolder.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-MailPublicFolder.md
@@ -33,7 +33,7 @@ Enable-MailPublicFolder [-Identity] <PublicFolderIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-MailUser.md b/exchange/exchange-ps/ExchangePowerShell/Enable-MailUser.md
index d102ab1df9..ceb3f644e4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-MailUser.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-MailUser.md
@@ -55,7 +55,7 @@ The Enable-MailUser cmdlet mail-enables existing users by adding the email attri
 
 Mail users have email addresses and accounts in the Exchange organization, but they don't have Exchange mailboxes. Email messages sent to mail users are delivered to the specified external email address.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-Mailbox.md b/exchange/exchange-ps/ExchangePowerShell/Enable-Mailbox.md
index 25c3826181..4ca227e302 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-Mailbox.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-Mailbox.md
@@ -273,7 +273,7 @@ The Enable-Mailbox cmdlet mailbox-enables existing users, public folders, or Ine
 
 When mailbox-enabling an existing user, beware of non-supported characters in the user account or Name property. If you don't specify an Alias value when you mailbox-enable the user, Exchange converts all non-supported characters to question marks (?). To avoid question marks in the Alias, verify that the user account and Name properties have only supported ASCII or Unicode characters or specify an Alias value when you mailbox-enable the user.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 In Exchange Server, the [CommonParameters](https://go.microsoft.com/fwlink/p/?LinkID=113216) InformationVariable and InformationAction don't work.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-MailboxQuarantine.md b/exchange/exchange-ps/ExchangePowerShell/Enable-MailboxQuarantine.md
index 867711e84f..d539c0c031 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-MailboxQuarantine.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-MailboxQuarantine.md
@@ -54,7 +54,7 @@ Enable-MailboxQuarantine -Database <DatabaseIdParameter> -StoreMailboxIdentity <
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-MalwareFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-MalwareFilterRule.md
index af974853e5..c8d9f1432e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-MalwareFilterRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-MalwareFilterRule.md
@@ -30,7 +30,7 @@ Enable-MalwareFilterRule [-Identity] <RuleIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-MetaCacheDatabase.md b/exchange/exchange-ps/ExchangePowerShell/Enable-MetaCacheDatabase.md
index dfaa1c8861..860be7f17a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-MetaCacheDatabase.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-MetaCacheDatabase.md
@@ -29,7 +29,7 @@ Enable-MetaCacheDatabase -Server <String[]>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-OrganizationCustomization.md b/exchange/exchange-ps/ExchangePowerShell/Enable-OrganizationCustomization.md
index bd23fa403a..92019b3cd6 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-OrganizationCustomization.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-OrganizationCustomization.md
@@ -43,7 +43,7 @@ You are only required to run the Enable-OrganizationCustomization cmdlet once in
 
 Whether or not this command is previously run in an organization is available in the IsDehydrated property of the Get-OrganizationConfig cmdlet: False ($false) = the command has already been run; True ($true) = the command has never been run.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-OutlookAnywhere.md b/exchange/exchange-ps/ExchangePowerShell/Enable-OutlookAnywhere.md
index 2297a39956..300964c824 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-OutlookAnywhere.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-OutlookAnywhere.md
@@ -57,7 +57,7 @@ When you run this cmdlet, it can take as long as an hour for the settings to bec
 
 For more information about the different authentication methods that you can see in this article, see [Understanding HTTP Authentication](https://learn.microsoft.com/dotnet/framework/wcf/feature-details/understanding-http-authentication).
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-OutlookProtectionRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-OutlookProtectionRule.md
index c9d18eab91..46b914e2ec 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-OutlookProtectionRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-OutlookProtectionRule.md
@@ -34,7 +34,7 @@ Enable-OutlookProtectionRule [-Identity] <RuleIdParameter>
 ## DESCRIPTION
 Outlook protection rules are used to automatically Information Rights Management (IRM)-protect messages using a Rights Management Services (RMS) template before the message is sent. However, Outlook protection rules don't inspect message content. To rights-protect messages based on message content, use transport protection rules. For more information, see [Outlook protection rules](https://learn.microsoft.com/exchange/outlook-protection-rules-exchange-2013-help).
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-PushNotificationProxy.md b/exchange/exchange-ps/ExchangePowerShell/Enable-PushNotificationProxy.md
index 6cf4a5c65c..79a0e49acc 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-PushNotificationProxy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-PushNotificationProxy.md
@@ -34,7 +34,7 @@ Enable-PushNotificationProxy [-Confirm]
 ## DESCRIPTION
 The push notification proxy relays event notifications (for example, new email or calendar updates) for on-premises mailboxes through Microsoft 365 to Outlook on the web for devices on the user's device.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-RemoteMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Enable-RemoteMailbox.md
index 1f12234ec2..26f49783c0 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-RemoteMailbox.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-RemoteMailbox.md
@@ -102,7 +102,7 @@ Directory synchronization must be configured correctly for a mailbox to be creat
 
 The policies that you apply to recipients in the on-premises Exchange organization, such as Unified Messaging or compliance policies, aren't applied to mailboxes in the service. You must configure policies in the service if you want policies to be applied to recipients in the service.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-ReportSubmissionRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-ReportSubmissionRule.md
index 29852d3479..8cb09e07a1 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-ReportSubmissionRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-ReportSubmissionRule.md
@@ -29,7 +29,7 @@ Enable-ReportSubmissionRule [-Identity] <RuleIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-SafeAttachmentRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-SafeAttachmentRule.md
index 0cd9ec3748..352b045c45 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-SafeAttachmentRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-SafeAttachmentRule.md
@@ -31,7 +31,7 @@ Enable-SafeAttachmentRule [-Identity] <RuleIdParameter>
 ## DESCRIPTION
 Safe Attachments is a feature in Microsoft Defender for Office 365 that opens email attachments in a special hypervisor environment to detect malicious activity. For more information, see [Safe Attachments in Defender for Office 365](https://learn.microsoft.com/defender-office-365/safe-attachments-about).
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 

From cf4c476f1953182ee3bc9b9a661d257a86888ce6 Mon Sep 17 00:00:00 2001
From: Chris Davis <chris.davis@microsoft.com>
Date: Tue, 5 Aug 2025 21:23:19 -0700
Subject: [PATCH 077/145] Acrolinx 5

---
 exchange/exchange-ps/ExchangePowerShell/Enable-SafeLinksRule.md | 2 +-
 .../ExchangePowerShell/Enable-ServiceEmailChannel.md            | 2 +-
 .../exchange-ps/ExchangePowerShell/Enable-SmtpDaneInbound.md    | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Enable-SweepRule.md     | 2 +-
 .../exchange-ps/ExchangePowerShell/Enable-TransportAgent.md     | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Enable-TransportRule.md | 2 +-
 .../exchange-ps/ExchangePowerShell/Enable-UMAutoAttendant.md    | 2 +-
 .../ExchangePowerShell/Enable-UMCallAnsweringRule.md            | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Enable-UMIPGateway.md   | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Enable-UMMailbox.md     | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Enable-UMServer.md      | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Enable-UMService.md     | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Expedite-Delicensing.md | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Export-ActiveSyncLog.md | 2 +-
 .../exchange-ps/ExchangePowerShell/Export-AutoDiscoverConfig.md | 2 +-
 .../ExchangePowerShell/Export-DlpPolicyCollection.md            | 2 +-
 .../ExchangePowerShell/Export-ExchangeCertificate.md            | 2 +-
 .../ExchangePowerShell/Export-JournalRuleCollection.md          | 2 +-
 .../ExchangePowerShell/Export-MailboxDiagnosticLogs.md          | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Export-Message.md       | 2 +-
 .../exchange-ps/ExchangePowerShell/Export-MigrationReport.md    | 2 +-
 .../exchange-ps/ExchangePowerShell/Export-QuarantineMessage.md  | 2 +-
 .../ExchangePowerShell/Export-RecipientDataProperty.md          | 2 +-
 .../ExchangePowerShell/Export-TransportRuleCollection.md        | 2 +-
 .../exchange-ps/ExchangePowerShell/Export-UMCallDataRecord.md   | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Export-UMPrompt.md      | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Get-ADPermission.md     | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Get-ADServerSettings.md | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Get-ADSite.md           | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Get-ADSiteLink.md       | 2 +-
 .../ExchangePowerShell/Get-ATPBuiltInProtectionRule.md          | 2 +-
 .../ExchangePowerShell/Get-ATPProtectionPolicyRule.md           | 2 +-
 .../exchange-ps/ExchangePowerShell/Get-ATPTotalTrafficReport.md | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Get-AcceptedDomain.md   | 2 +-
 .../ExchangePowerShell/Get-AccessToCustomerDataRequest.md       | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDevice.md | 2 +-
 .../ExchangePowerShell/Get-ActiveSyncDeviceAccessRule.md        | 2 +-
 .../Get-ActiveSyncDeviceAutoblockThreshold.md                   | 2 +-
 .../exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceClass.md | 2 +-
 .../ExchangePowerShell/Get-ActiveSyncDeviceStatistics.md        | 2 +-
 .../ExchangePowerShell/Get-ActiveSyncMailboxPolicy.md           | 2 +-
 .../ExchangePowerShell/Get-ActiveSyncOrganizationSettings.md    | 2 +-
 .../ExchangePowerShell/Get-ActiveSyncVirtualDirectory.md        | 2 +-
 .../exchange-ps/ExchangePowerShell/Get-AddressBookPolicy.md     | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Get-AddressList.md      | 2 +-
 .../exchange-ps/ExchangePowerShell/Get-AdminAuditLogConfig.md   | 2 +-
 .../exchange-ps/ExchangePowerShell/Get-AdministrativeUnit.md    | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Get-AgentLog.md         | 2 +-
 .../exchange-ps/ExchangePowerShell/Get-AggregateZapReport.md    | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Get-AntiPhishPolicy.md  | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Get-AntiPhishRule.md    | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Get-App.md              | 2 +-
 .../ExchangePowerShell/Get-ApplicationAccessPolicy.md           | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Get-ArcConfig.md        | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Get-AtpPolicyForO365.md | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Get-AuditLogSearch.md   | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Get-AuthConfig.md       | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Get-AuthRedirect.md     | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Get-AuthServer.md       | 2 +-
 .../exchange-ps/ExchangePowerShell/Get-AuthenticationPolicy.md  | 2 +-
 .../ExchangePowerShell/Get-AutodiscoverVirtualDirectory.md      | 2 +-
 .../ExchangePowerShell/Get-AvailabilityAddressSpace.md          | 2 +-
 .../exchange-ps/ExchangePowerShell/Get-AvailabilityConfig.md    | 2 +-
 .../ExchangePowerShell/Get-AvailabilityReportOutage.md          | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Get-BlockedConnector.md | 2 +-
 .../exchange-ps/ExchangePowerShell/Get-BlockedSenderAddress.md  | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Get-CASMailbox.md       | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Get-CASMailboxPlan.md   | 2 +-
 .../ExchangePowerShell/Get-CalendarDiagnosticAnalysis.md        | 2 +-
 .../exchange-ps/ExchangePowerShell/Get-CalendarDiagnosticLog.md | 2 +-
 .../ExchangePowerShell/Get-CalendarDiagnosticObjects.md         | 2 +-
 .../exchange-ps/ExchangePowerShell/Get-CalendarNotification.md  | 2 +-
 .../exchange-ps/ExchangePowerShell/Get-CalendarProcessing.md    | 2 +-
 .../ExchangePowerShell/Get-ClassificationRuleCollection.md      | 2 +-
 .../exchange-ps/ExchangePowerShell/Get-ClientAccessArray.md     | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessRule.md | 2 +-
 .../exchange-ps/ExchangePowerShell/Get-ClientAccessServer.md    | 2 +-
 .../exchange-ps/ExchangePowerShell/Get-ClientAccessService.md   | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Get-Clutter.md          | 2 +-
 .../exchange-ps/ExchangePowerShell/Get-CmdletExtensionAgent.md  | 2 +-
 .../ExchangePowerShell/Get-ComplianceRetentionEventType.md      | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Get-ComplianceSearch.md | 2 +-
 .../ExchangePowerShell/Get-ComplianceSearchAction.md            | 2 +-
 .../ExchangePowerShell/Get-CompromisedUserAggregateReport.md    | 2 +-
 .../ExchangePowerShell/Get-CompromisedUserDetailReport.md       | 2 +-
 .../Get-ConfigAnalyzerPolicyRecommendation.md                   | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Get-Contact.md          | 2 +-
 .../exchange-ps/ExchangePowerShell/Get-ContentFilterConfig.md   | 2 +-
 .../exchange-ps/ExchangePowerShell/Get-ContentFilterPhrase.md   | 2 +-
 .../ExchangePowerShell/Get-ContentMalwareMdoAggregateReport.md  | 2 +-
 .../ExchangePowerShell/Get-ContentMalwareMdoDetailReport.md     | 2 +-
 .../exchange-ps/ExchangePowerShell/Get-DataClassification.md    | 2 +-
 .../ExchangePowerShell/Get-DataClassificationConfig.md          | 2 +-
 .../ExchangePowerShell/Get-DatabaseAvailabilityGroup.md         | 2 +-
 .../ExchangePowerShell/Get-DatabaseAvailabilityGroupNetwork.md  | 2 +-
 95 files changed, 95 insertions(+), 95 deletions(-)

diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-SafeLinksRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-SafeLinksRule.md
index ef7fe14799..a488f199df 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-SafeLinksRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-SafeLinksRule.md
@@ -31,7 +31,7 @@ Enable-SafeLinksRule [-Identity] <RuleIdParameter>
 ## DESCRIPTION
 Safe Links is a feature in Microsoft Defender for Office 365 that checks links in email messages to see if they lead to malicious web sites. When a user clicks a link in a message, the URL is temporarily rewritten and checked against a list of known, malicious web sites. Safe Links includes the URL trace reporting feature to help determine who has clicked through to a malicious web site.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-ServiceEmailChannel.md b/exchange/exchange-ps/ExchangePowerShell/Enable-ServiceEmailChannel.md
index 4a98df3b35..d4a9119467 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-ServiceEmailChannel.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-ServiceEmailChannel.md
@@ -32,7 +32,7 @@ Enable-ServiceEmailChannel [-Identity] <MailboxIdParameter>
 ## DESCRIPTION
 The .NET service channel enables Microsoft Exchange to store information that it later forwards to applications or devices that aren't permanently connected to the server running Exchange. This cmdlet creates a receive folder in the user's mailbox under the root folder named Service E-mail.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-SmtpDaneInbound.md b/exchange/exchange-ps/ExchangePowerShell/Enable-SmtpDaneInbound.md
index 3f8909bb29..0198844e56 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-SmtpDaneInbound.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-SmtpDaneInbound.md
@@ -31,7 +31,7 @@ Enable-SmtpDaneInbound [-DomainName] <String>
 ## DESCRIPTION
 For more information about debugging, enabling, and disabling SMTP DANE with DNSSEC, see [How SMTP DANE works](https://learn.microsoft.com/purview/how-smtp-dane-works).
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-SweepRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-SweepRule.md
index 52efc9fe3c..da7cacb624 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-SweepRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-SweepRule.md
@@ -31,7 +31,7 @@ Enable-SweepRule [-Identity] <SweepRuleIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-TransportAgent.md b/exchange/exchange-ps/ExchangePowerShell/Enable-TransportAgent.md
index 48365cd90b..3b13e5f06b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-TransportAgent.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-TransportAgent.md
@@ -31,7 +31,7 @@ Enable-TransportAgent [-Identity] <TransportAgentObjectId>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-TransportRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-TransportRule.md
index 88ee1e141b..a5df89ce00 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-TransportRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-TransportRule.md
@@ -33,7 +33,7 @@ Enable-TransportRule [-Identity] <RuleIdParameter>
 ## DESCRIPTION
 To disable rules that are enabled, use the Disable-TransportRule cmdlet.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-UMAutoAttendant.md b/exchange/exchange-ps/ExchangePowerShell/Enable-UMAutoAttendant.md
index a990173558..6738fa8dca 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-UMAutoAttendant.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-UMAutoAttendant.md
@@ -32,7 +32,7 @@ Enable-UMAutoAttendant [-Identity] <UMAutoAttendantIdParameter>
 ## DESCRIPTION
 The Enable-UMAutoAttendant cmdlet enables the UM auto attendant by modifying its status variable. When you create a UM auto attendant, it isn't enabled by default. For the auto attendant to answer incoming calls, you must first enable it. After this task is completed, the UM auto attendant answers incoming calls.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-UMCallAnsweringRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-UMCallAnsweringRule.md
index 85f18e53c9..d5f4e06300 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-UMCallAnsweringRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-UMCallAnsweringRule.md
@@ -35,7 +35,7 @@ The Enable-UMCallAnsweringRule cmdlet enables the call answering rule by modifyi
 
 After this task is completed, the cmdlet sets the parameters and values specified. When you enable a call answering rule, the call answering rule is processed when an incoming call is received.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-UMIPGateway.md b/exchange/exchange-ps/ExchangePowerShell/Enable-UMIPGateway.md
index 3bac3cc380..257616fe21 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-UMIPGateway.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-UMIPGateway.md
@@ -34,7 +34,7 @@ The status variable for a UM IP gateway can be used to enable or disable call an
 
 After this task is completed, the UM IP gateway answers incoming calls and makes outgoing calls through the IP gateway or IP Private Branch eXchange (PBX).
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-UMMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Enable-UMMailbox.md
index 63b1283604..702bc96be8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-UMMailbox.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-UMMailbox.md
@@ -63,7 +63,7 @@ Enable-UMMailbox [-Identity] <MailboxIdParameter>
 ## DESCRIPTION
 When the mailbox is enabled for Unified Messaging, the settings from a UM mailbox policy are applied to the mailbox. After the mailbox is enabled for Unified Messaging, the user can use the UM features that are included in Microsoft Exchange.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-UMServer.md b/exchange/exchange-ps/ExchangePowerShell/Enable-UMServer.md
index 6f5b17049c..44f9f235b6 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-UMServer.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-UMServer.md
@@ -34,7 +34,7 @@ The Enable-UMServer cmdlet sets the status of a Unified Messaging server. A UM s
 
 After this task is completed, the Unified Messaging server is available to answer incoming calls.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-UMService.md b/exchange/exchange-ps/ExchangePowerShell/Enable-UMService.md
index e54a0c4d8f..9804245e88 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-UMService.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-UMService.md
@@ -36,7 +36,7 @@ The Enable-UMService cmdlet sets the status of an Exchange server running the Un
 
 After this task is completed, the UM server is available to answer incoming calls.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Expedite-Delicensing.md b/exchange/exchange-ps/ExchangePowerShell/Expedite-Delicensing.md
index b7b89bd6a4..349d748c48 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Expedite-Delicensing.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Expedite-Delicensing.md
@@ -27,7 +27,7 @@ Expedite-Delicensing [-Identity] <RecipientIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Export-ActiveSyncLog.md b/exchange/exchange-ps/ExchangePowerShell/Export-ActiveSyncLog.md
index e264cc2be0..cce74c131a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Export-ActiveSyncLog.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Export-ActiveSyncLog.md
@@ -37,7 +37,7 @@ Export-ActiveSyncLog -Filename <String>
 ## DESCRIPTION
 The Export-ActiveSyncLog cmdlet parses the IIS log files and returns information about Exchange ActiveSync usage. This cmdlet can export the output to a file or display it in the Exchange Management Shell.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Export-AutoDiscoverConfig.md b/exchange/exchange-ps/ExchangePowerShell/Export-AutoDiscoverConfig.md
index 815599dd21..c347036561 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Export-AutoDiscoverConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Export-AutoDiscoverConfig.md
@@ -36,7 +36,7 @@ Export-AutoDiscoverConfig -TargetForestDomainController <String>
 ## DESCRIPTION
 The Autodiscover Service Connection Point pointer resides Active Directory in the user account forest. The pointer includes the LDAP URL of the resource forest that the client uses to locate the Autodiscover service in the resource forest.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Export-DlpPolicyCollection.md b/exchange/exchange-ps/ExchangePowerShell/Export-DlpPolicyCollection.md
index 1c0e5668b1..63d707a6a2 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Export-DlpPolicyCollection.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Export-DlpPolicyCollection.md
@@ -34,7 +34,7 @@ Export-DlpPolicyCollection [[-Identity] <DlpPolicyIdParameter>]
 ## DESCRIPTION
 The Export-DlpPolicyCollection cmdlet exports the settings of the DLP policies and the associated transport rules. You use the Import-DlpPolicyCollection to import the DLP policy collection into your organization.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Export-ExchangeCertificate.md b/exchange/exchange-ps/ExchangePowerShell/Export-ExchangeCertificate.md
index 92abab4583..46aae8392f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Export-ExchangeCertificate.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Export-ExchangeCertificate.md
@@ -57,7 +57,7 @@ The Export-ExchangeCertificate cmdlet creates the following types of files:
 
   Typically, you export a certificate request file if you need to resubmit the certificate request to the certification authority. You can't import an exported certificate request on another server.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Export-JournalRuleCollection.md b/exchange/exchange-ps/ExchangePowerShell/Export-JournalRuleCollection.md
index ba292844af..556b223c09 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Export-JournalRuleCollection.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Export-JournalRuleCollection.md
@@ -33,7 +33,7 @@ Export-JournalRuleCollection [[-Identity] <RuleIdParameter>]
 ## DESCRIPTION
 You can use the Export-JournalRuleCollection cmdlet to export journal rules in your organization to create a backup copy of your rules.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Export-MailboxDiagnosticLogs.md b/exchange/exchange-ps/ExchangePowerShell/Export-MailboxDiagnosticLogs.md
index 6fd1c0489b..98b784d811 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Export-MailboxDiagnosticLogs.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Export-MailboxDiagnosticLogs.md
@@ -51,7 +51,7 @@ Export-MailboxDiagnosticLogs [-Identity] <GeneralMailboxIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Export-Message.md b/exchange/exchange-ps/ExchangePowerShell/Export-Message.md
index e4a8c0a1c4..c550e5f436 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Export-Message.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Export-Message.md
@@ -31,7 +31,7 @@ Export-Message [-Identity] <MessageIdentity>
 ## DESCRIPTION
 The Export-Message cmdlet copies messages from the Delivery queue, the Unreachable queue, or the poison message queue on Mailbox server or an Edge Transport server to a specified file path. Before you export a message, you must first suspend the message. Messages in the poison message queue are already suspended. You can use the Export-Message cmdlet to copy messages to the Replay directory of another Mailbox server for delivery.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Export-MigrationReport.md b/exchange/exchange-ps/ExchangePowerShell/Export-MigrationReport.md
index 616210274f..f01bf9c014 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Export-MigrationReport.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Export-MigrationReport.md
@@ -42,7 +42,7 @@ Export-MigrationReport [-Identity] <MigrationReportIdParameter> -RowCount <Int32
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Export-QuarantineMessage.md b/exchange/exchange-ps/ExchangePowerShell/Export-QuarantineMessage.md
index 4b11731d00..28299d4927 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Export-QuarantineMessage.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Export-QuarantineMessage.md
@@ -50,7 +50,7 @@ Export-QuarantineMessage -Identity <QuarantineMessageIdentity>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Export-RecipientDataProperty.md b/exchange/exchange-ps/ExchangePowerShell/Export-RecipientDataProperty.md
index 45daf7cf05..f7ded90650 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Export-RecipientDataProperty.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Export-RecipientDataProperty.md
@@ -42,7 +42,7 @@ Export-RecipientDataProperty [-Identity] <MailboxUserContactIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Export-TransportRuleCollection.md b/exchange/exchange-ps/ExchangePowerShell/Export-TransportRuleCollection.md
index 5369d2b033..733a9c53f1 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Export-TransportRuleCollection.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Export-TransportRuleCollection.md
@@ -36,7 +36,7 @@ The Export-TransportRuleCollection cmdlet can be used to export the transport ru
 
 Exporting the rules collection is a two-step process. You first export the rules collection to a variable, and then use the Set-Content cmdlet to write the data to an XML file. For more information, see [Set-Content](https://learn.microsoft.com/powershell/module/microsoft.powershell.management/set-content).
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Export-UMCallDataRecord.md b/exchange/exchange-ps/ExchangePowerShell/Export-UMCallDataRecord.md
index 32025032ee..2cae15c5ab 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Export-UMCallDataRecord.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Export-UMCallDataRecord.md
@@ -36,7 +36,7 @@ The Export-UMCallDataRecord cmdlet exports Unified Messaging call data records f
 
 After this task is completed, a report is generated that contains Unified Messaging call data records.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Export-UMPrompt.md b/exchange/exchange-ps/ExchangePowerShell/Export-UMPrompt.md
index 21b1a865bf..3e7bdb2f80 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Export-UMPrompt.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Export-UMPrompt.md
@@ -44,7 +44,7 @@ The Export-UMPrompt cmdlet exports prompts that belong to existing UM dial plan
 
 After this task is completed, the UM prompts are displayed or saved.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ADPermission.md b/exchange/exchange-ps/ExchangePowerShell/Get-ADPermission.md
index 59fe583201..bb70e13cd8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ADPermission.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ADPermission.md
@@ -40,7 +40,7 @@ Get-ADPermission [-Identity] <ADRawEntryIdParameter>
 ## DESCRIPTION
 The ADPermission cmdlets can be used to directly modify Active Directory access control lists (ACLs). Although some Microsoft Exchange features might continue to use the ADPermission cmdlets to manage permissions (for example Send and Receive connectors), Exchange 2013 and later versions no longer use customized ACLs to manage administrative permissions. If you want to grant or deny administrative permissions in Exchange 2013 or later, you need to use Role Based Access Control (RBAC). For more information about RBAC, see [Permissions in Exchange Server](https://learn.microsoft.com/Exchange/permissions/permissions).
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ADServerSettings.md b/exchange/exchange-ps/ExchangePowerShell/Get-ADServerSettings.md
index 6e48794ca8..d34e36afaa 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ADServerSettings.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ADServerSettings.md
@@ -26,7 +26,7 @@ Get-ADServerSettings [<CommonParameters>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ADSite.md b/exchange/exchange-ps/ExchangePowerShell/Get-ADSite.md
index 158acf47bb..6849e8bdc0 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ADSite.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ADSite.md
@@ -30,7 +30,7 @@ Get-ADSite [[-Identity] <AdSiteIdParameter>]
 ## DESCRIPTION
 Exchange uses Active Directory sites and the costs assigned to the Active Directory site links to make message routing decisions.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ADSiteLink.md b/exchange/exchange-ps/ExchangePowerShell/Get-ADSiteLink.md
index b0596c3e42..cc1b89a208 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ADSiteLink.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ADSiteLink.md
@@ -28,7 +28,7 @@ Get-ADSiteLink [[-Identity] <AdSiteLinkIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ATPBuiltInProtectionRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-ATPBuiltInProtectionRule.md
index 5f7cf3cb3b..2cb22176b0 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ATPBuiltInProtectionRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ATPBuiltInProtectionRule.md
@@ -28,7 +28,7 @@ Get-ATPBuiltInProtectionRule [[-Identity] <DehydrateableRuleIdParameter>] [-Stat
 ## DESCRIPTION
 For more information about preset security policies, see [Preset security policies in EOP and Microsoft Defender for Office 365](https://learn.microsoft.com/defender-office-365/preset-security-policies).
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ATPProtectionPolicyRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-ATPProtectionPolicyRule.md
index 3b58d62111..963826fe7e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ATPProtectionPolicyRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ATPProtectionPolicyRule.md
@@ -30,7 +30,7 @@ Get-ATPProtectionPolicyRule [[-Identity] <RuleIdParameter>]
 ## DESCRIPTION
 For more information about preset security policies in PowerShell, see [Preset security policies in Exchange Online PowerShell](https://learn.microsoft.com/defender-office-365/preset-security-policies#preset-security-policies-in-exchange-online-powershell).
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ATPTotalTrafficReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-ATPTotalTrafficReport.md
index e3439c0023..75dddf8e56 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ATPTotalTrafficReport.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ATPTotalTrafficReport.md
@@ -56,7 +56,7 @@ If the tenant had Safe Attachments or Safe Links policies, the messages would ha
 
 By default, the command returns data for the last 14 days. Data for the last 90 days is available.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AcceptedDomain.md b/exchange/exchange-ps/ExchangePowerShell/Get-AcceptedDomain.md
index 7e97bc3970..7748fcd4fb 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AcceptedDomain.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-AcceptedDomain.md
@@ -29,7 +29,7 @@ Get-AcceptedDomain [[-Identity] <AcceptedDomainIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AccessToCustomerDataRequest.md b/exchange/exchange-ps/ExchangePowerShell/Get-AccessToCustomerDataRequest.md
index b30d05b9dc..995c951c19 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AccessToCustomerDataRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-AccessToCustomerDataRequest.md
@@ -31,7 +31,7 @@ Get-AccessToCustomerDataRequest [-ApprovalStatus <String>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDevice.md b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDevice.md
index 3a287a1293..38fa08786f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDevice.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDevice.md
@@ -50,7 +50,7 @@ Get-ActiveSyncDevice [[-Identity] <ActiveSyncDeviceIdParameter>]
 ## DESCRIPTION
 The Get-ActiveSyncDevice cmdlet returns identification, configuration and status information for each device.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceAccessRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceAccessRule.md
index 04f6699372..969dff3485 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceAccessRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceAccessRule.md
@@ -30,7 +30,7 @@ Get-ActiveSyncDeviceAccessRule [[-Identity] <ActiveSyncDeviceAccessRuleIdParamet
 ## DESCRIPTION
 You can create multiple groups of devices: allowed devices, blocked devices, and quarantined devices with the New-ActiveSyncDeviceAccessRule cmdlet. The Get-ActiveSyncDeviceAccessRule cmdlet retrieves the settings for any existing group.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceAutoblockThreshold.md b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceAutoblockThreshold.md
index 804549c94e..3eae2e954e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceAutoblockThreshold.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceAutoblockThreshold.md
@@ -30,7 +30,7 @@ Get-ActiveSyncDeviceAutoblockThreshold [[-Identity] <ActiveSyncDeviceAutoblockTh
 ## DESCRIPTION
 Microsoft Exchange and Exchange ActiveSync have the capability to block Exchange ActiveSync mobile devices if these devices display any of a defined list of behaviors that have the capability to cause issues with the server. The Get-ActiveSyncDeviceAutoblockThreshold cmdlet returns the settings for the requested threshold rule.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceClass.md b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceClass.md
index dc34912d32..136f9d646d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceClass.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceClass.md
@@ -32,7 +32,7 @@ Get-ActiveSyncDeviceClass [[-Identity] <ActiveSyncDeviceClassIdParameter>]
 ## DESCRIPTION
 You can use this cmdlet to view a list of mobile phones or devices by type. For example, you can return a list of all Android mobile digital devices in the organization or all Windows Phone devices in the organization.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceStatistics.md
index 6413242a39..08446a5d56 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceStatistics.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceStatistics.md
@@ -46,7 +46,7 @@ Get-ActiveSyncDeviceStatistics -Mailbox <MailboxIdParameter>
 ## DESCRIPTION
 The Get-ActiveSyncDeviceStatistics cmdlet returns a list of statistics about each mobile device. Additionally, it allows you to retrieve logs and send those logs to a recipient for troubleshooting purposes.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncMailboxPolicy.md
index 72c2d259e4..daa6a942b5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncMailboxPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncMailboxPolicy.md
@@ -32,7 +32,7 @@ Get-ActiveSyncMailboxPolicy [[-Identity] <MailboxPolicyIdParameter>]
 ## DESCRIPTION
 A Mobile Device mailbox policy is a group of settings that specifies how mobile devices enabled for Microsoft Exchange ActiveSync connect to the computer running Exchange. Exchange supports multiple Mobile Device mailbox policies. The Get-ActiveSyncMailboxPolicy cmdlet displays all the policy settings for the specified policy. These settings include password settings, file access settings and attachment settings.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncOrganizationSettings.md b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncOrganizationSettings.md
index 7560cac114..a8b91cba75 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncOrganizationSettings.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncOrganizationSettings.md
@@ -28,7 +28,7 @@ Get-ActiveSyncOrganizationSettings [[-Identity] <ActiveSyncOrganizationSettingsI
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncVirtualDirectory.md
index ca9c796dcb..a5ff61bfa0 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncVirtualDirectory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncVirtualDirectory.md
@@ -42,7 +42,7 @@ Get-ActiveSyncVirtualDirectory [[-Identity] <VirtualDirectoryIdParameter>]
 ## DESCRIPTION
 Microsoft Exchange servers have a default virtual directory that Exchange ActiveSync mobile devices use to synchronize with the server. You can create multiple virtual directories and assign different devices to different directories.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AddressBookPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-AddressBookPolicy.md
index 178bc818bb..14bcfbf882 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AddressBookPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-AddressBookPolicy.md
@@ -30,7 +30,7 @@ Get-AddressBookPolicy [[-Identity] <MailboxPolicyIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AddressList.md b/exchange/exchange-ps/ExchangePowerShell/Get-AddressList.md
index 26b167606c..16fd763848 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AddressList.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-AddressList.md
@@ -47,7 +47,7 @@ Get-AddressList [-SearchText <String>]
 ## DESCRIPTION
 You can pipe the output from the Get-AddressList cmdlet to the Remove-AddressList, Set-AddressList, Update-AddressList and Move-AddressList cmdlets instead of using the Identity parameter with each of those cmdlets.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AdminAuditLogConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-AdminAuditLogConfig.md
index 946b4e03d9..975a94075f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AdminAuditLogConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-AdminAuditLogConfig.md
@@ -29,7 +29,7 @@ Get-AdminAuditLogConfig [-DomainController <Fqdn>]
 ## DESCRIPTION
 To check the UnifiedAuditLogIngestionEnabled value in the output of this cmdlet, run the command in Exchange Online PowerShell. The value in Security & Compliance PowerShell is always False and the Set-AdminAuditLogConfig cmdlet (and the UnifiedAuditLogIngestionEnabled parameter) is not available to change it.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AdministrativeUnit.md b/exchange/exchange-ps/ExchangePowerShell/Get-AdministrativeUnit.md
index ebc5e1b4d0..9a605c829e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AdministrativeUnit.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-AdministrativeUnit.md
@@ -32,7 +32,7 @@ Get-AdministrativeUnit [[-Identity] <AdministrativeUnitIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AgentLog.md b/exchange/exchange-ps/ExchangePowerShell/Get-AgentLog.md
index 2875806cc5..5c34512eea 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AgentLog.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-AgentLog.md
@@ -30,7 +30,7 @@ Get-AgentLog [-EndDate <DateTime>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AggregateZapReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-AggregateZapReport.md
index 255b5435c1..1a7944c6c3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AggregateZapReport.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-AggregateZapReport.md
@@ -37,7 +37,7 @@ For the reporting period you specify, the cmdlet returns the following informati
 - EventType
 - ZapActionCount
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AntiPhishPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-AntiPhishPolicy.md
index cdf89a913d..819eba076b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AntiPhishPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-AntiPhishPolicy.md
@@ -30,7 +30,7 @@ Get-AntiPhishPolicy [-Identity <AntiPhishPolicyIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AntiPhishRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-AntiPhishRule.md
index cc2853c02c..729fd881f2 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AntiPhishRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-AntiPhishRule.md
@@ -28,7 +28,7 @@ Get-AntiPhishRule [[-Identity] <RuleIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-App.md b/exchange/exchange-ps/ExchangePowerShell/Get-App.md
index 2b7fa376d0..4dfc80bbfd 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-App.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-App.md
@@ -33,7 +33,7 @@ Get-App [[-Identity] <AppIdParameter>]
 ## DESCRIPTION
 The Get-App cmdlet returns information about all installed apps or the details of a specific installed app.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ApplicationAccessPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-ApplicationAccessPolicy.md
index 4e781959c5..e2c7f08d47 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ApplicationAccessPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ApplicationAccessPolicy.md
@@ -29,7 +29,7 @@ Get-ApplicationAccessPolicy [[-Identity] <ApplicationAccessPolicyIdParameter>]
 ## DESCRIPTION
 This feature applies only to apps connecting to the Microsoft Graph API for Outlook resources.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ArcConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-ArcConfig.md
index 3b6f57fbd4..b85c65bf0f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ArcConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ArcConfig.md
@@ -28,7 +28,7 @@ Get-ArcConfig [<CommonParameters>]
 ## DESCRIPTION
 Services that modify message content in transit before delivery can invalidate DKIM email signatures and affect the authentication of the message. These services can use ARC to provide details of the original authentication before the modifications occurred. Your organization can then trust these details to help authenticate the message.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AtpPolicyForO365.md b/exchange/exchange-ps/ExchangePowerShell/Get-AtpPolicyForO365.md
index 6bc86ea8c5..4ab8b7aacd 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AtpPolicyForO365.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-AtpPolicyForO365.md
@@ -37,7 +37,7 @@ Safe Documents scans documents and files that are opened in Protected View. For
 
 Safe Attachments for SharePoint, OneDrive, and Microsoft Teams prevents users from opening and downloading files that are identified as malicious. For more information, see [Safe Attachments for SharePoint, OneDrive, and Microsoft Teams](https://learn.microsoft.com/defender-office-365/safe-attachments-for-spo-odfb-teams-about).
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AuditLogSearch.md b/exchange/exchange-ps/ExchangePowerShell/Get-AuditLogSearch.md
index 36c6b25396..1074a5cee0 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AuditLogSearch.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-AuditLogSearch.md
@@ -33,7 +33,7 @@ Get-AuditLogSearch [[-Identity] <AuditLogSearchIdParameter>]
 ## DESCRIPTION
 Run the Get-AuditLogSearch cmdlet to return a list of pending audit log searches. If an audit log search has completed, it isn't displayed in the list of audit log searches.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AuthConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-AuthConfig.md
index 2ee2b66f48..9f1e7d1fa9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AuthConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-AuthConfig.md
@@ -27,7 +27,7 @@ Get-AuthConfig [-DomainController <Fqdn>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AuthRedirect.md b/exchange/exchange-ps/ExchangePowerShell/Get-AuthRedirect.md
index 392e1c2bf0..2fd82357b2 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AuthRedirect.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-AuthRedirect.md
@@ -30,7 +30,7 @@ Get-AuthRedirect [[-Identity] <AuthRedirectIdParameter>]
 ## DESCRIPTION
 Exchange 2010 Client Access servers don't support OAuth authentication requests. OAuth redirection objects redirect OAuth authentication requests to Exchange servers that are running later versions of Exchange. This cmdlet is only useful if your organization has Exchange 2010 Client Access servers.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AuthServer.md b/exchange/exchange-ps/ExchangePowerShell/Get-AuthServer.md
index 1c90a96a4d..18a995e5e5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AuthServer.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-AuthServer.md
@@ -30,7 +30,7 @@ Get-AuthServer [[-Identity] <AuthServerIdParameter>]
 ## DESCRIPTION
 An authorization server is a server or service that issues tokens trusted by Microsoft Exchange for access by partner applications.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AuthenticationPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-AuthenticationPolicy.md
index a2c52203b4..0cc8f2ce52 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AuthenticationPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-AuthenticationPolicy.md
@@ -28,7 +28,7 @@ Get-AuthenticationPolicy [[-Identity] <AuthPolicyIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AutodiscoverVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Get-AutodiscoverVirtualDirectory.md
index 0f05438f81..9427b28c13 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AutodiscoverVirtualDirectory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-AutodiscoverVirtualDirectory.md
@@ -40,7 +40,7 @@ Get-AutodiscoverVirtualDirectory [[-Identity] <VirtualDirectoryIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AvailabilityAddressSpace.md b/exchange/exchange-ps/ExchangePowerShell/Get-AvailabilityAddressSpace.md
index 7e14d7db02..dd98d48602 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AvailabilityAddressSpace.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-AvailabilityAddressSpace.md
@@ -30,7 +30,7 @@ Get-AvailabilityAddressSpace [[-Identity] <AvailabilityAddressSpaceIdParameter>]
 ## DESCRIPTION
 In on-premises Exchange organizations, you run the Remove-AvailabilityAddressSpace cmdlet on Exchange servers that have the Client Access server role installed.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AvailabilityConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-AvailabilityConfig.md
index 30ebc3e5ed..41769cda65 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AvailabilityConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-AvailabilityConfig.md
@@ -31,7 +31,7 @@ Get-AvailabilityConfig [[-Identity] <OrganizationIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AvailabilityReportOutage.md b/exchange/exchange-ps/ExchangePowerShell/Get-AvailabilityReportOutage.md
index ad2b43f866..34915d7e93 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AvailabilityReportOutage.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-AvailabilityReportOutage.md
@@ -30,7 +30,7 @@ Get-AvailabilityReportOutage [[-Identity] <AvailabilityReportOutageIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-BlockedConnector.md b/exchange/exchange-ps/ExchangePowerShell/Get-BlockedConnector.md
index 11a3f14b28..e32648d522 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-BlockedConnector.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-BlockedConnector.md
@@ -26,7 +26,7 @@ Get-BlockedConnector [-ConnectorId <Guid>] [<CommonParameters>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-BlockedSenderAddress.md b/exchange/exchange-ps/ExchangePowerShell/Get-BlockedSenderAddress.md
index 3516ff3e4f..8a230bbf7a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-BlockedSenderAddress.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-BlockedSenderAddress.md
@@ -27,7 +27,7 @@ Get-BlockedSenderAddress [-SenderAddress <SmtpAddress>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-CASMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Get-CASMailbox.md
index ed3b0f3a22..01bae9325f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-CASMailbox.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-CASMailbox.md
@@ -66,7 +66,7 @@ Get-CASMailbox [[-Identity] <MailboxIdParameter>]
 ## DESCRIPTION
 This cmdlet returns a variety of client access settings for one or more mailboxes. These settings include options for Outlook on the web, Exchange ActiveSync, POP3, and IMAP4.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-CASMailboxPlan.md b/exchange/exchange-ps/ExchangePowerShell/Get-CASMailboxPlan.md
index c59d301409..b18ba0fbd9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-CASMailboxPlan.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-CASMailboxPlan.md
@@ -35,7 +35,7 @@ Get-CASMailboxPlan [[-Identity] <MailboxPlanIdParameter>]
 ## DESCRIPTION
 A CAS mailbox plan is tied to the corresponding mailbox plan that has the same name (and display name). Like mailbox plans, CAS mailbox plans correspond to license types, and are applied to a mailbox when you license the user. The availability of a CAS mailbox plan is determined by your selections when you enroll in the service and the age of your organization.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-CalendarDiagnosticAnalysis.md b/exchange/exchange-ps/ExchangePowerShell/Get-CalendarDiagnosticAnalysis.md
index 0c08a5c78b..254a8bc41d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-CalendarDiagnosticAnalysis.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-CalendarDiagnosticAnalysis.md
@@ -60,7 +60,7 @@ The following properties of the calendar item are returned in the default output
 - SenderEmailAddress
 - SentRepresentingDisplayName
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-CalendarDiagnosticLog.md b/exchange/exchange-ps/ExchangePowerShell/Get-CalendarDiagnosticLog.md
index 5e3f48c881..381a1fe665 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-CalendarDiagnosticLog.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-CalendarDiagnosticLog.md
@@ -73,7 +73,7 @@ The output of this cmdlet contains the following information:
 
 After you run the Get-CalendarDiagnosticLog cmdlet, you can analyze the calendar data using the Get-CalendarDiagnosticAnalysis cmdlet. For more information, see [Get-CalendarDiagnosticAnalysis](https://learn.microsoft.com/powershell/module/exchangepowershell/get-calendardiagnosticanalysis).
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-CalendarDiagnosticObjects.md b/exchange/exchange-ps/ExchangePowerShell/Get-CalendarDiagnosticObjects.md
index c9e9fb38fb..8971b36801 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-CalendarDiagnosticObjects.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-CalendarDiagnosticObjects.md
@@ -57,7 +57,7 @@ Some of the more interesting properties that are returned in the results are:
 - ResponseType: 0 = The organizer hasn't received a response, 1 = The organizer's copy of the meeting, 2 = Tentative, 3 = Accept, 4 = Decline, or 5 = The attendee hasn't responded.
 - ResponsibleUserName: The LegacyExchangeDN value of the user who made the change (for example, `/o=ExchangeLabs/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=BN6PR11MB1587/cn=Microsoft System Attendant` or `/o=ExchangeLabs/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=696eea97d3c449eab648920d03385efb-admin`).
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-CalendarNotification.md b/exchange/exchange-ps/ExchangePowerShell/Get-CalendarNotification.md
index 03e6c54481..8805d48276 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-CalendarNotification.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-CalendarNotification.md
@@ -35,7 +35,7 @@ Get-CalendarNotification [-Identity] <MailboxIdParameter>
 ## DESCRIPTION
 The Get-CalendarNotification cmdlet retrieves and displays the rules that trigger the calendar agenda notification, reminder notification, or update notification text messages.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-CalendarProcessing.md b/exchange/exchange-ps/ExchangePowerShell/Get-CalendarProcessing.md
index 232212d73f..7e0d1c3a47 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-CalendarProcessing.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-CalendarProcessing.md
@@ -32,7 +32,7 @@ Get-CalendarProcessing [-Identity] <MailboxIdParameter>
 ## DESCRIPTION
 For details about the properties that are returned in the output of this cmdlet, see [Set-CalendarProcessing](https://learn.microsoft.com/powershell/module/exchangepowershell/set-calendarprocessing).
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ClassificationRuleCollection.md b/exchange/exchange-ps/ExchangePowerShell/Get-ClassificationRuleCollection.md
index 63acdf54d9..d193a9e80d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ClassificationRuleCollection.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ClassificationRuleCollection.md
@@ -30,7 +30,7 @@ Get-ClassificationRuleCollection [[-Identity] <ClassificationRuleCollectionIdPar
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessArray.md b/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessArray.md
index 3b220ee5f6..8bc2e48ab3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessArray.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessArray.md
@@ -36,7 +36,7 @@ Changes in the Exchange server architecture that were introduced in Exchange Ser
 - Outlook clients can't use RPC over TCP to access mailboxes on Exchange Server 2013 or later versions and RPC Client Access arrays only work with RPC over TCP.
 - Because the Client Access server role is now a stateless proxy, you use different and less complex methods to configure load balancing and high availability for internal and external client connections. For more information, see [Load balancing in Exchange Server](https://learn.microsoft.com/Exchange/architecture/client-access/load-balancing).
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessRule.md
index 57eb9b41ff..256fd14a48 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessRule.md
@@ -35,7 +35,7 @@ Get-ClientAccessRule [[-Identity] <ClientAccessRuleIdParameter>]
 ## DESCRIPTION
 Client access rules are like mail flow rules (also known as transport rules) for client connections to your organization. You use conditions and exceptions to identify the connections based on their properties, and actions that allow or block the connections.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessServer.md b/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessServer.md
index 3fff1f85e2..09650e1a71 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessServer.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessServer.md
@@ -32,7 +32,7 @@ Get-ClientAccessServer [[-Identity] <ClientAccessServerIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessService.md b/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessService.md
index fa35e4a5fc..0bc4dd10e3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessService.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessService.md
@@ -30,7 +30,7 @@ Get-ClientAccessService [[-Identity] <ClientAccessServerIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-Clutter.md b/exchange/exchange-ps/ExchangePowerShell/Get-Clutter.md
index ef6f60312c..726b83b98e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-Clutter.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-Clutter.md
@@ -28,7 +28,7 @@ Get-Clutter -Identity <MailboxIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-CmdletExtensionAgent.md b/exchange/exchange-ps/ExchangePowerShell/Get-CmdletExtensionAgent.md
index ee03554a60..2de9f2d0a0 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-CmdletExtensionAgent.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-CmdletExtensionAgent.md
@@ -39,7 +39,7 @@ Get-CmdletExtensionAgent [[-Identity] <CmdletExtensionAgentIdParameter>]
 ## DESCRIPTION
 Cmdlet extension agents are used by Exchange cmdlets in Exchange Server 2010 and later. Cmdlets provided by other Microsoft or non-Microsoft products can't use cmdlet extension agents.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceRetentionEventType.md b/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceRetentionEventType.md
index 29c6be59fc..a20b6d4bff 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceRetentionEventType.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceRetentionEventType.md
@@ -28,7 +28,7 @@ Get-ComplianceRetentionEventType [-Identity <ComplianceRuleIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceSearch.md b/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceSearch.md
index 877553b037..9ae15ddfbb 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceSearch.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceSearch.md
@@ -30,7 +30,7 @@ Get-ComplianceSearch [[-Identity] <ComplianceSearchIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 In on-premises Exchange, this cmdlet is available in the Mailbox Search role. By default, this role is assigned only to the Discovery Management role group.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceSearchAction.md b/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceSearchAction.md
index ada10e2ac6..b21f4a1973 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceSearchAction.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceSearchAction.md
@@ -72,7 +72,7 @@ Get-ComplianceSearchAction [-Export]
 ## DESCRIPTION
 After you create and run a compliance search using the New-ComplianceSearch cmdlet, and start the search using the Start-ComplianceSearch cmdlet, you assign a search action using the New-ComplianceSearchAction cmdlet. You use the Get-ComplianceSearchAction cmdlet to track the progress of the compliance search action.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 In on-premises Exchange, this cmdlet is available in the Mailbox Search role. By default, this role is assigned only to the Discovery Management role group.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-CompromisedUserAggregateReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-CompromisedUserAggregateReport.md
index e45a462bc6..265f55aab4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-CompromisedUserAggregateReport.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-CompromisedUserAggregateReport.md
@@ -38,7 +38,7 @@ This cmdlet returns the following information:
 - UserCount
 - Action
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-CompromisedUserDetailReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-CompromisedUserDetailReport.md
index fb13f0365e..762a182473 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-CompromisedUserDetailReport.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-CompromisedUserDetailReport.md
@@ -38,7 +38,7 @@ This cmdlet returns the following information:
 - UserCount
 - Action
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ConfigAnalyzerPolicyRecommendation.md b/exchange/exchange-ps/ExchangePowerShell/Get-ConfigAnalyzerPolicyRecommendation.md
index 4b369acf50..4b2485cfbf 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ConfigAnalyzerPolicyRecommendation.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ConfigAnalyzerPolicyRecommendation.md
@@ -49,7 +49,7 @@ If a setting is configured at or better than the Standard or Strict protection p
 
 This cmdlet returns the following output for each setting in each policy that falls below the recommended value.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-Contact.md b/exchange/exchange-ps/ExchangePowerShell/Get-Contact.md
index 5a6584b210..2869b21596 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-Contact.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-Contact.md
@@ -52,7 +52,7 @@ Get-Contact [[-Identity] <ContactIdParameter>]
 ## DESCRIPTION
 The Get-Contact cmdlet returns no mail-related properties for mail contacts. Use the Get-MailContact to view mail-related properties for mail contacts.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ContentFilterConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-ContentFilterConfig.md
index 12081057e7..fc479a47c6 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ContentFilterConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ContentFilterConfig.md
@@ -27,7 +27,7 @@ Get-ContentFilterConfig [-DomainController <Fqdn>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ContentFilterPhrase.md b/exchange/exchange-ps/ExchangePowerShell/Get-ContentFilterPhrase.md
index 8c0a7405f0..2e50b904e8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ContentFilterPhrase.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ContentFilterPhrase.md
@@ -36,7 +36,7 @@ Get-ContentFilterPhrase [-Phrase <ContentFilterPhraseIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ContentMalwareMdoAggregateReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-ContentMalwareMdoAggregateReport.md
index 79a807688f..58abe6daed 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ContentMalwareMdoAggregateReport.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ContentMalwareMdoAggregateReport.md
@@ -42,7 +42,7 @@ For the specified reporting period, the cmdlet returns the following information
 
 By default, the command returns data for the last 14 days. Data for the last 90 days is available.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ContentMalwareMdoDetailReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-ContentMalwareMdoDetailReport.md
index 8e7f403dd9..e50714762a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ContentMalwareMdoDetailReport.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ContentMalwareMdoDetailReport.md
@@ -44,7 +44,7 @@ For the specified reporting period, the cmdlet returns the following information
 
 By default, the command returns data for the last 14 days. Data for the last 30 days is available.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DataClassification.md b/exchange/exchange-ps/ExchangePowerShell/Get-DataClassification.md
index c1e5e1cbaf..00d4186107 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DataClassification.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-DataClassification.md
@@ -40,7 +40,7 @@ Get-DataClassification [[-Identity] <DataClassificationIdParameter>]
 ## DESCRIPTION
 Classification rule packages are used by data loss prevention (DLP) to detect sensitive content in messages.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DataClassificationConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-DataClassificationConfig.md
index 7d40e138f2..582c99fd75 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DataClassificationConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-DataClassificationConfig.md
@@ -26,7 +26,7 @@ Get-DataClassificationConfig [<CommonParameters>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DatabaseAvailabilityGroup.md b/exchange/exchange-ps/ExchangePowerShell/Get-DatabaseAvailabilityGroup.md
index b26d54636a..4b2ad570fd 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DatabaseAvailabilityGroup.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-DatabaseAvailabilityGroup.md
@@ -39,7 +39,7 @@ In addition to obtaining a list of DAG members, the Get-DatabaseAvailabilityGrou
 
 Use the Status parameter with the command to include the values for these listed properties. Without the Status parameter, the values returned for these properties are blank.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DatabaseAvailabilityGroupNetwork.md b/exchange/exchange-ps/ExchangePowerShell/Get-DatabaseAvailabilityGroupNetwork.md
index 659b7a2920..06b82d75b5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DatabaseAvailabilityGroupNetwork.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-DatabaseAvailabilityGroupNetwork.md
@@ -48,7 +48,7 @@ Valid states for network interfaces
 - Unavailable: The network interface isn't enabled for replication or use by the DAG, or the DAG member associated with this network interface is inactive or unavailable.The network interface isn't enabled for replication or use by the DAG, or the DAG member associated with this network interface is inactive or unavailable.
 - Unknown: The system was unable to determine the state of the network interface.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 

From c2bdae96f480ba8562097333fa4e6803d74c9033 Mon Sep 17 00:00:00 2001
From: William Blocker <118470885+saleens7@users.noreply.github.com>
Date: Wed, 6 Aug 2025 01:28:22 -0700
Subject: [PATCH 078/145] Update Set-CsTeamsEventsPolicy.md

---
 .../MicrosoftTeams/Set-CsTeamsEventsPolicy.md | 43 +++++++++++++++++--
 1 file changed, 40 insertions(+), 3 deletions(-)

diff --git a/teams/teams-ps/MicrosoftTeams/Set-CsTeamsEventsPolicy.md b/teams/teams-ps/MicrosoftTeams/Set-CsTeamsEventsPolicy.md
index 2d6de4e0a5..ec716bcce9 100644
--- a/teams/teams-ps/MicrosoftTeams/Set-CsTeamsEventsPolicy.md
+++ b/teams/teams-ps/MicrosoftTeams/Set-CsTeamsEventsPolicy.md
@@ -20,9 +20,8 @@ Set-CsTeamsEventsPolicy [-AllowWebinars <String>] [-EventAccessType <String>] [-
  [-TownhallEventAttendeeAccess <String>] [-AllowEmailEditing <String>] [-AllowedQuestionTypesInRegistrationForm <String>]
  [-AllowEventIntegrations <Boolean>] [-AllowedWebinarTypesForRecordingPublish <String>]
  [-AllowedTownhallTypesForRecordingPublish <String>] [-TownhallChatExperience <String>] [-Description <String>]
- [-RecordingForTownhall <String>] [-RecordingForWebinar <String>]
- [-TranscriptionForTownhall <String>] [-TranscriptionForWebinar <String>]
- [-UseMicrosoftECDN <Boolean>] [-BroadcastPremiumApps <String>]
+ [-RecordingForTownhall <String>] [-RecordingForWebinar <String>] [-TranscriptionForTownhall <String>] [-TranscriptionForWebinar <String>]
+ [-UseMicrosoftECDN <Boolean>] [-BroadcastPremiumApps <String>] [-MaxResolutionForTownhall <String>] [-HighBitrateForTownhall <String>]
 ```
 
 ## DESCRIPTION
@@ -439,6 +438,44 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
+### -MaxResolutionForTownhall
+This policy sets the maximum video resolution supported in Town hall events.
+
+Possible values are:
+- **Max720p**: Town halls support video resolution up to 720p.
+- **Max1080p**: Town halls support video resolution up to 1080p.
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+
+Required: False
+Position: Named
+Default value: Max1080p
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -HighBitrateForTownhall
+This policy controls whether high-bitrate streaming is enabled for Town hall events.
+
+Possible values are:
+- **Enabled**: Enables high bitrate for Town hall events.
+- **Disabled**: Disables high bitrate for Town hall events.
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+
+Required: False
+Position: Named
+Default value: Disabled
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
 ### -WhatIf
 The WhatIf switch does not work with this cmdlet.
 The cmdlet is not run.

From 565d6d5c526b579a7498bd648abfe7cb56da0c4f Mon Sep 17 00:00:00 2001
From: William Blocker <118470885+saleens7@users.noreply.github.com>
Date: Wed, 6 Aug 2025 01:30:02 -0700
Subject: [PATCH 079/145] Update New-CsTeamsEventsPolicy.md

---
 .../MicrosoftTeams/New-CsTeamsEventsPolicy.md | 41 ++++++++++++++++++-
 1 file changed, 40 insertions(+), 1 deletion(-)

diff --git a/teams/teams-ps/MicrosoftTeams/New-CsTeamsEventsPolicy.md b/teams/teams-ps/MicrosoftTeams/New-CsTeamsEventsPolicy.md
index 11ed7d8a64..bda9f1143f 100644
--- a/teams/teams-ps/MicrosoftTeams/New-CsTeamsEventsPolicy.md
+++ b/teams/teams-ps/MicrosoftTeams/New-CsTeamsEventsPolicy.md
@@ -19,7 +19,7 @@ This cmdlet allows you to create a new TeamsEventsPolicy instance and set its pr
 New-CsTeamsEventsPolicy [-Identity] <String> [-AllowWebinars <String>] [-AllowTownhalls <String>] [-ImmersiveEvents <String>] [-AllowEmailEditing <String>] [-Description <String>]
 [-TownhallEventAttendeeAccess <String>] [-RecordingForTownhall <String>] [-RecordingForWebinar <String>]
 [-TranscriptionForTownhall <String>] [-TranscriptionForWebinar <String>] [-AllowEventIntegrations <Boolean>] [-TownhallChatExperience <String>]
-[-UseMicrosoftECDN <String>] [-EventAccessType <String>] [-BroadcastPremiumApps <String>] [-WhatIf] [-Confirm] [<CommonParameters>]
+[-UseMicrosoftECDN <String>] [-EventAccessType <String>] [-BroadcastPremiumApps <String>]  [-MaxResolutionForTownhall <String>] [-HighBitrateForTownhall <String>] [-WhatIf] [-Confirm] [<CommonParameters>]
 ```
 
 ## DESCRIPTION
@@ -377,6 +377,45 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
+### -MaxResolutionForTownhall
+This policy sets the maximum video resolution supported in Town hall events.
+
+Possible values are:
+- **Max720p**: Town halls support video resolution up to 720p.
+- **Max1080p**: Town halls support video resolution up to 1080p.
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+
+Required: False
+Position: Named
+Default value: Max1080p
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -HighBitrateForTownhall
+This policy controls whether high-bitrate streaming is enabled for Town hall events.
+
+Possible values are:
+- **Enabled**: Enables high bitrate for Town hall events.
+- **Disabled**: Disables high bitrate for Town hall events.
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+
+Required: False
+Position: Named
+Default value: Disabled
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+
 ### -WhatIf
 The WhatIf switch does not work with this cmdlet.
 The cmdlet is not run.

From c048a3ebf5e2d15d05068dd5d4fe4682fcd0194b Mon Sep 17 00:00:00 2001
From: William Blocker <118470885+saleens7@users.noreply.github.com>
Date: Wed, 6 Aug 2025 01:35:39 -0700
Subject: [PATCH 080/145] Update New-CsTeamsCallingPolicy.md

---
 .../New-CsTeamsCallingPolicy.md               | 22 +++++++++++++++++++
 1 file changed, 22 insertions(+)

diff --git a/teams/teams-ps/MicrosoftTeams/New-CsTeamsCallingPolicy.md b/teams/teams-ps/MicrosoftTeams/New-CsTeamsCallingPolicy.md
index eda358df5f..a1983e55fb 100644
--- a/teams/teams-ps/MicrosoftTeams/New-CsTeamsCallingPolicy.md
+++ b/teams/teams-ps/MicrosoftTeams/New-CsTeamsCallingPolicy.md
@@ -54,6 +54,7 @@ New-CsTeamsCallingPolicy [-Identity] <string>
  [-SpamFilteringEnabledType <string>]
  [-VoiceSimulationInInterpreter <string>]
  [-RealTimeText <string>]
+ [-ExplicitRecordingConsent <string>]
  [-WhatIf]
  [<CommonParameters>]
 ```
@@ -755,6 +756,27 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
+### -ExplicitRecordingConsent
+
+This setting controls whether users must provide or obtain explicit consent before recording a 1:1 PSTN or Teams call. When enabled, both parties will receive a notification, and consent must be given before recording starts.
+
+Possible values:
+
+- **Enabled**: Requires users to give and obtain explicit consent before starting a call recording.
+- **Disabled**: Users are not required to obtain explicit consent before recording starts.
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+
+Required: False
+Position: Named
+Default value: Disabled
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
 ### -WhatIf
 
 > Applicable: Microsoft Teams

From b5b6783bfa056adb51a57b81146edd08a3fb12a1 Mon Sep 17 00:00:00 2001
From: William Blocker <118470885+saleens7@users.noreply.github.com>
Date: Wed, 6 Aug 2025 01:36:43 -0700
Subject: [PATCH 081/145] Update Set-CsTeamsCallingPolicy.md

---
 .../Set-CsTeamsCallingPolicy.md               | 22 +++++++++++++++++++
 1 file changed, 22 insertions(+)

diff --git a/teams/teams-ps/MicrosoftTeams/Set-CsTeamsCallingPolicy.md b/teams/teams-ps/MicrosoftTeams/Set-CsTeamsCallingPolicy.md
index 1d0d11adb7..33e9c661d9 100644
--- a/teams/teams-ps/MicrosoftTeams/Set-CsTeamsCallingPolicy.md
+++ b/teams/teams-ps/MicrosoftTeams/Set-CsTeamsCallingPolicy.md
@@ -53,6 +53,7 @@ Set-CsTeamsCallingPolicy [-Identity] <string>
  [-SpamFilteringEnabledType <string>]
  [-VoiceSimulationInInterpreter <string>]
  [-RealTimeText <string>]
+ [-ExplicitRecordingConsent <string>]
  [-WhatIf]
  [<CommonParameters>]
 ```
@@ -757,6 +758,27 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
+### -ExplicitRecordingConsent
+
+This setting controls whether users must provide or obtain explicit consent before recording a 1:1 PSTN or Teams call. When enabled, both parties will receive a notification, and consent must be given before recording starts.
+
+Possible values:
+
+- **Enabled**: Requires users to give and obtain explicit consent before starting a call recording.
+- **Disabled**: Users are not required to obtain explicit consent before recording starts.
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+
+Required: False
+Position: Named
+Default value: Disabled
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
 ### -WhatIf
 
 > Applicable: Microsoft Teams

From 5f7101d37e992124a8473fb9c5fa2d1783f7a973 Mon Sep 17 00:00:00 2001
From: William Blocker <118470885+saleens7@users.noreply.github.com>
Date: Wed, 6 Aug 2025 01:41:27 -0700
Subject: [PATCH 082/145] Update Set-CsTeamsEducationConfiguration.md

---
 .../Set-CsTeamsEducationConfiguration.md      | 36 ++++++++++++++++++-
 1 file changed, 35 insertions(+), 1 deletion(-)

diff --git a/teams/teams-ps/MicrosoftTeams/Set-CsTeamsEducationConfiguration.md b/teams/teams-ps/MicrosoftTeams/Set-CsTeamsEducationConfiguration.md
index 1307bdd7dd..812ee9c67d 100644
--- a/teams/teams-ps/MicrosoftTeams/Set-CsTeamsEducationConfiguration.md
+++ b/teams/teams-ps/MicrosoftTeams/Set-CsTeamsEducationConfiguration.md
@@ -19,7 +19,8 @@ This cmdlet is used to manage the organization-wide education configuration for
 
 ```powershell
 Set-CsTeamsEducationConfiguration [-ParentGuardianPreferredContactMethod <String>]
- [-UpdateParentInformation <String>] [-WhatIf] [-Confirm] [<CommonParameters>]
+ [-UpdateParentInformation <String>]  [-EduGenerativeAIEnhancements <String>] [-Identity <String>]
+ [-WhatIf] [-Confirm] [<CommonParameters>]
 ```
 
 ## DESCRIPTION
@@ -90,6 +91,39 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
+### -EduGenerativeAIEnhancements
+
+Controls whether generative AI enhancements are enabled in the education environment.
+
+Possible values:
+
+- `Enabled`: Generative AI features are available to educators and students.
+- `Disabled`: Generative AI features are disabled across the tenant.
+
+```yaml
+Type: System.String
+Parameter Sets: (All)
+Required: False
+Position: Named
+Default value: Enabled
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -Identity
+
+Specifies the identity of the education configuration to set.
+
+```yaml
+Type: System.String
+Parameter Sets: (All)
+Required: False
+Position: Named
+Default value: Global
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
 ### CommonParameters
 This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).
 

From a5a5491f1936af939c14639a199b3565cb22f18a Mon Sep 17 00:00:00 2001
From: William Blocker <118470885+saleens7@users.noreply.github.com>
Date: Wed, 6 Aug 2025 01:44:59 -0700
Subject: [PATCH 083/145] Update Set-CsTeamsMessagingPolicy.md

---
 .../Set-CsTeamsMessagingPolicy.md             | 40 +++++++++++++++++++
 1 file changed, 40 insertions(+)

diff --git a/teams/teams-ps/MicrosoftTeams/Set-CsTeamsMessagingPolicy.md b/teams/teams-ps/MicrosoftTeams/Set-CsTeamsMessagingPolicy.md
index a4472ecb06..0ed1f1cef2 100644
--- a/teams/teams-ps/MicrosoftTeams/Set-CsTeamsMessagingPolicy.md
+++ b/teams/teams-ps/MicrosoftTeams/Set-CsTeamsMessagingPolicy.md
@@ -58,6 +58,8 @@ Set-CsTeamsMessagingPolicy [[-Identity] <XdsIdentity>]
  [-ReadReceiptsEnabledType <String>]
  [-Tenant <Guid>]
  [-UsersCanDeleteBotMessages <Boolean>]
+ [-AutoShareFilesInExternalChats <String>]
+ [-UseB2BInvitesToAddExternalUsers <String>]
  [-WhatIf]
  [<CommonParameters>]
 ```
@@ -788,6 +790,44 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
+### -UseB2BInvitesToAddExternalUsers
+
+Indicates whether B2B invites should be used to add external users when necessary.
+
+Possible values:
+
+- `Enabled`: External users will be added using B2B invites.
+- `Disabled`: External users will not be added using B2B invites.
+
+```yaml
+Type: System.String
+Parameter Sets: (All)
+Required: False
+Position: Named
+Default value: Disabled
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -AutoShareFilesInExternalChats
+
+Determines whether files are automatically shared in external chats.
+
+Possible values:
+
+- `Enabled`: Files are automatically shared in external chats.
+- `Disabled`: Files are not automatically shared in external chats.
+
+```yaml
+Type: System.String
+Parameter Sets: (All)
+Required: False
+Position: Named
+Default value: Disabled
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
 ### -WhatIf
 Shows what would happen if the cmdlet runs.
 The cmdlet is not run.

From 8b53c5b1d52844ed790f342b8a737a65687568ff Mon Sep 17 00:00:00 2001
From: William Blocker <118470885+saleens7@users.noreply.github.com>
Date: Wed, 6 Aug 2025 01:45:18 -0700
Subject: [PATCH 084/145] Update Set-CsTeamsMessagingPolicy.md

---
 teams/teams-ps/MicrosoftTeams/Set-CsTeamsMessagingPolicy.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/teams/teams-ps/MicrosoftTeams/Set-CsTeamsMessagingPolicy.md b/teams/teams-ps/MicrosoftTeams/Set-CsTeamsMessagingPolicy.md
index 0ed1f1cef2..5d867c419e 100644
--- a/teams/teams-ps/MicrosoftTeams/Set-CsTeamsMessagingPolicy.md
+++ b/teams/teams-ps/MicrosoftTeams/Set-CsTeamsMessagingPolicy.md
@@ -106,6 +106,8 @@ Set-CsTeamsMessagingPolicy [-Instance <PSObject>]
  [-ReadReceiptsEnabledType <String>]
  [-Tenant <Guid>]
  [-UsersCanDeleteBotMessages <Boolean>]
+ [-AutoShareFilesInExternalChats <String>]
+ [-UseB2BInvitesToAddExternalUsers <String>]
  [-WhatIf]
  [<CommonParameters>]
 ```

From 1203e76de6dadb88cca968bb49f9dbd58c4956c1 Mon Sep 17 00:00:00 2001
From: William Blocker <118470885+saleens7@users.noreply.github.com>
Date: Wed, 6 Aug 2025 01:45:49 -0700
Subject: [PATCH 085/145] Update New-CsTeamsMessagingPolicy.md

---
 teams/teams-ps/MicrosoftTeams/New-CsTeamsMessagingPolicy.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/teams/teams-ps/MicrosoftTeams/New-CsTeamsMessagingPolicy.md b/teams/teams-ps/MicrosoftTeams/New-CsTeamsMessagingPolicy.md
index f421e0536e..cc2472c71b 100644
--- a/teams/teams-ps/MicrosoftTeams/New-CsTeamsMessagingPolicy.md
+++ b/teams/teams-ps/MicrosoftTeams/New-CsTeamsMessagingPolicy.md
@@ -58,6 +58,8 @@ New-CsTeamsMessagingPolicy [[-Identity] <XdsIdentity>]
  [-ReadReceiptsEnabledType <String>]
  [-Tenant <Guid>]
  [-UsersCanDeleteBotMessages <Boolean>]
+ [-AutoShareFilesInExternalChats <String>]
+ [-UseB2BInvitesToAddExternalUsers <String>]
  [<CommonParameters>]
  [-WhatIf]
  ```

From b83e24b94a3b406339a4970a6cc2e9eac1d4236b Mon Sep 17 00:00:00 2001
From: William Blocker <118470885+saleens7@users.noreply.github.com>
Date: Wed, 6 Aug 2025 01:46:30 -0700
Subject: [PATCH 086/145] Update New-CsTeamsMessagingPolicy.md

---
 .../New-CsTeamsMessagingPolicy.md             | 38 +++++++++++++++++++
 1 file changed, 38 insertions(+)

diff --git a/teams/teams-ps/MicrosoftTeams/New-CsTeamsMessagingPolicy.md b/teams/teams-ps/MicrosoftTeams/New-CsTeamsMessagingPolicy.md
index cc2472c71b..3efbfe0e8b 100644
--- a/teams/teams-ps/MicrosoftTeams/New-CsTeamsMessagingPolicy.md
+++ b/teams/teams-ps/MicrosoftTeams/New-CsTeamsMessagingPolicy.md
@@ -736,6 +736,44 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
+### -UseB2BInvitesToAddExternalUsers
+
+Indicates whether B2B invites should be used to add external users when necessary.
+
+Possible values:
+
+- `Enabled`: External users will be added using B2B invites.
+- `Disabled`: External users will not be added using B2B invites.
+
+```yaml
+Type: System.String
+Parameter Sets: (All)
+Required: False
+Position: Named
+Default value: Disabled
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -AutoShareFilesInExternalChats
+
+Determines whether files are automatically shared in external chats.
+
+Possible values:
+
+- `Enabled`: Files are automatically shared in external chats.
+- `Disabled`: Files are not automatically shared in external chats.
+
+```yaml
+Type: System.String
+Parameter Sets: (All)
+Required: False
+Position: Named
+Default value: Disabled
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
 ### -WhatIf
 Shows what would happen if the cmdlet runs.
 The cmdlet is not run.

From 6bc7f2a27d5a925897496c7be9f6bf05a56ab452 Mon Sep 17 00:00:00 2001
From: alexcotsalas <116087923+alexcotsalas@users.noreply.github.com>
Date: Wed, 6 Aug 2025 06:32:26 -0700
Subject: [PATCH 087/145] Update New-OrganizationRelationship.md

Adds guidance for max group size in FreeBusyAccessScope.
---
 .../ExchangePowerShell/New-OrganizationRelationship.md          | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/exchange/exchange-ps/ExchangePowerShell/New-OrganizationRelationship.md b/exchange/exchange-ps/ExchangePowerShell/New-OrganizationRelationship.md
index 770257916d..bdaaea5dc3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-OrganizationRelationship.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-OrganizationRelationship.md
@@ -284,7 +284,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
 
-The FreeBusyAccessScope parameter specifies a mail-enabled security group in the internal organization that contains users whose free/busy information is accessible by an external organization. You can use any value that uniquely identifies the group. For example:
+The FreeBusyAccessScope parameter specifies a mail-enabled security group in the internal organization that contains users whose free/busy information is accessible by an external organization. For best performance, groups should be smaller than 10,000 members. You can use any value that uniquely identifies the group. For example:
 
 - Name
 - Distinguished name (DN)

From 59c2a0db703889c168926ef23140c51715a02552 Mon Sep 17 00:00:00 2001
From: alexcotsalas <116087923+alexcotsalas@users.noreply.github.com>
Date: Wed, 6 Aug 2025 07:12:13 -0700
Subject: [PATCH 088/145] Update Add-AvailabilityAddressSpace to clarify
 configurations needed for Free/busy sharing between online tenants

Removes -AccessMethod OrgWideFBBasic which was deprecated some time ago when basic auth was deprecated in Exchange Online.

Clarifies that -AccessMethod OrgWideFB is deprecated for accessing target forests in Exchange Online.

Adds -AccessMethod OrgWideFBToken which is now the only way to establish AvailabilityAddressSpace for Freebusy sharing across two tenants in Exchange Online.

Clarifies that -AccessMethod OrgWideFBToken also requires TargetTenantId and TargetServiceEpr for a successful configuration.
---
 .../ExchangePowerShell/Add-AvailabilityAddressSpace.md    | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-AvailabilityAddressSpace.md b/exchange/exchange-ps/ExchangePowerShell/Add-AvailabilityAddressSpace.md
index b07f62ef9e..0e4585433d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-AvailabilityAddressSpace.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Add-AvailabilityAddressSpace.md
@@ -81,8 +81,8 @@ In Exchange Online, this example sets up the sharing of free/busy information wi
 The AccessMethod parameter specifies how the free/busy data is accessed. Valid values are:
 
 - PerUserFB: Per-user free/busy information can be requested. The free/busy data is accessed in the defined per-user free/busy proxy account or group, or in the All Exchange Servers group. This value requires a trust between the two forests, and requires you to use either the UseServiceAccount parameter or Credentials parameter.
-- OrgWideFB: Only default free/busy for each user can be requested. The free/busy data is accessed in the per-user free/busy proxy account or group in the target forest. This value requires you to use either the UseServiceAccount parameter or Credentials parameter.
-- OrgWideFBBasic: Free/busy sharing between tenants that are all in Exchange Online.
+- OrgWideFB: Only the default free/busy for each user can be requested. The free/busy data is accessed in the per-user free/busy proxy account or group in the target forest. This value requires you to use either the UseServiceAccount parameter or Credentials parameter. This is deprecated for accessing target forests in Exchange Online.
+- OrgWideFBToken: Used for free/busy sharing between two tenants in Exchange Online. Only the default free/busy for each user can be requested. This option also requires you to set both TargetTenantId and TargetServiceEpr.
 - InternalProxy: The request is proxied to an Exchange server in the site that's running a later version of Exchange.
 - PublicFolder: This value was used to access free/busy data on Exchange Server 2003 servers.
 
@@ -221,7 +221,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online, Exchange Online Protection
 
-This parameter is available only in the cloud-based service.
+This parameter is available only in the cloud-based service and is only used when AccessMethod is OrgWideFBToken.
 
 The TargetServiceEpr parameter specifies the Exchange Online Calendar Service URL of the external Microsoft 365 organization that you're trying to read free/busy information from. Valid values are:
 
@@ -245,7 +245,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online, Exchange Online Protection
 
-This parameter is available only in the cloud-based service.
+This parameter is available only in the cloud-based service and is only used when AccessMethod is OrgWideFBToken.
 
 The TargetTenantID parameter specifies the tenant ID of the external Microsoft 365 organization that you're trying to read free/busy information from.
 

From c25f93fc5fd235174a108b64b3b88b0721e7423d Mon Sep 17 00:00:00 2001
From: Chris Davis <chris.davis@microsoft.com>
Date: Wed, 6 Aug 2025 08:24:06 -0700
Subject: [PATCH 089/145] Acrolinx 6

---
 .../ExchangePowerShell/Get-DataEncryptionPolicy.md        | 2 +-
 .../ExchangePowerShell/Get-DeliveryAgentConnector.md      | 2 +-
 .../exchange-ps/ExchangePowerShell/Get-DetailZapReport.md | 2 +-
 .../exchange-ps/ExchangePowerShell/Get-DetailsTemplate.md | 2 +-
 .../ExchangePowerShell/Get-DistributionGroup.md           | 2 +-
 .../ExchangePowerShell/Get-DistributionGroupMember.md     | 2 +-
 .../ExchangePowerShell/Get-DkimSigningConfig.md           | 2 +-
 .../exchange-ps/ExchangePowerShell/Get-DlpDetailReport.md | 2 +-
 .../ExchangePowerShell/Get-DlpDetectionsReport.md         | 2 +-
 .../ExchangePowerShell/Get-DlpIncidentDetailReport.md     | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Get-DlpPolicy.md  | 2 +-
 .../ExchangePowerShell/Get-DlpPolicyTemplate.md           | 2 +-
 .../Get-DnssecStatusForVerifiedDomain.md                  | 2 +-
 .../ExchangePowerShell/Get-DomainController.md            | 2 +-
 .../ExchangePowerShell/Get-DynamicDistributionGroup.md    | 2 +-
 .../Get-DynamicDistributionGroupMember.md                 | 2 +-
 .../ExchangePowerShell/Get-EOPProtectionPolicyRule.md     | 2 +-
 .../ExchangePowerShell/Get-EcpVirtualDirectory.md         | 2 +-
 .../ExchangePowerShell/Get-EdgeSubscription.md            | 2 +-
 .../ExchangePowerShell/Get-EdgeSyncServiceConfig.md       | 2 +-
 .../Get-EligibleDistributionGroupForMigration.md          | 2 +-
 .../ExchangePowerShell/Get-EmailAddressPolicy.md          | 2 +-
 .../ExchangePowerShell/Get-EmailTenantSettings.md         | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Get-EtrLimits.md  | 2 +-
 .../exchange-ps/ExchangePowerShell/Get-EventLogLevel.md   | 2 +-
 .../Get-EventsFromEmailConfiguration.md                   | 2 +-
 .../ExchangePowerShell/Get-ExchangeAssistanceConfig.md    | 2 +-
 .../ExchangePowerShell/Get-ExchangeCertificate.md         | 2 +-
 .../ExchangePowerShell/Get-ExchangeDiagnosticInfo.md      | 2 +-
 .../exchange-ps/ExchangePowerShell/Get-ExchangeFeature.md | 2 +-
 .../exchange-ps/ExchangePowerShell/Get-ExchangeServer.md  | 2 +-
 .../ExchangePowerShell/Get-ExchangeServerAccessLicense.md | 2 +-
 .../Get-ExchangeServerAccessLicenseUser.md                | 2 +-
 .../ExchangePowerShell/Get-ExchangeSettings.md            | 2 +-
 .../ExchangePowerShell/Get-ExoInformationBarrierPolicy.md | 2 +-
 .../Get-ExoInformationBarrierRelationship.md              | 2 +-
 .../Get-ExoInformationBarrierSegment.md                   | 2 +-
 .../ExchangePowerShell/Get-ExoPhishSimOverrideRule.md     | 2 +-
 .../ExchangePowerShell/Get-ExoSecOpsOverrideRule.md       | 2 +-
 .../ExchangePowerShell/Get-ExternalInOutlook.md           | 2 +-
 .../ExchangePowerShell/Get-FailedContentIndexDocuments.md | 2 +-
 .../ExchangePowerShell/Get-FederatedDomainProof.md        | 2 +-
 .../Get-FederatedOrganizationIdentifier.md                | 2 +-
 .../ExchangePowerShell/Get-FederationInformation.md       | 2 +-
 .../exchange-ps/ExchangePowerShell/Get-FederationTrust.md | 2 +-
 .../exchange-ps/ExchangePowerShell/Get-FocusedInbox.md    | 2 +-
 .../ExchangePowerShell/Get-ForeignConnector.md            | 2 +-
 .../ExchangePowerShell/Get-FrontendTransportService.md    | 2 +-
 .../ExchangePowerShell/Get-GlobalAddressList.md           | 2 +-
 .../ExchangePowerShell/Get-GlobalMonitoringOverride.md    | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Get-Group.md      | 2 +-
 .../exchange-ps/ExchangePowerShell/Get-HealthReport.md    | 2 +-
 .../ExchangePowerShell/Get-HistoricalSearch.md            | 2 +-
 .../Get-HostedConnectionFilterPolicy.md                   | 2 +-
 .../ExchangePowerShell/Get-HostedContentFilterPolicy.md   | 2 +-
 .../ExchangePowerShell/Get-HostedContentFilterRule.md     | 2 +-
 .../Get-HostedOutboundSpamFilterPolicy.md                 | 2 +-
 .../Get-HostedOutboundSpamFilterRule.md                   | 2 +-
 .../ExchangePowerShell/Get-HybridConfiguration.md         | 2 +-
 .../ExchangePowerShell/Get-IPv6StatusForAcceptedDomain.md | 2 +-
 .../ExchangePowerShell/Get-IRMConfiguration.md            | 2 +-
 .../exchange-ps/ExchangePowerShell/Get-ImapSettings.md    | 2 +-
 .../ExchangePowerShell/Get-InboundConnector.md            | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Get-InboxRule.md  | 2 +-
 .../Get-IntraOrganizationConfiguration.md                 | 2 +-
 .../ExchangePowerShell/Get-IntraOrganizationConnector.md  | 2 +-
 .../exchange-ps/ExchangePowerShell/Get-JournalRule.md     | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Get-LinkedUser.md | 2 +-
 .../exchange-ps/ExchangePowerShell/Get-LogonStatistics.md | 2 +-
 .../Get-M365DataAtRestEncryptionPolicy.md                 | 2 +-
 .../Get-M365DataAtRestEncryptionPolicyAssignment.md       | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Get-Mailbox.md    | 2 +-
 .../Get-MailboxAuditBypassAssociation.md                  | 4 ++--
 .../Get-MailboxAutoReplyConfiguration.md                  | 6 +++---
 .../Get-MailboxCalendarConfiguration.md                   | 4 ++--
 .../ExchangePowerShell/Get-MailboxCalendarFolder.md       | 4 ++--
 .../exchange-ps/ExchangePowerShell/Get-MailboxDatabase.md | 2 +-
 .../ExchangePowerShell/Get-MailboxDatabaseCopyStatus.md   | 4 ++--
 .../ExchangePowerShell/Get-MailboxExportRequest.md        | 6 +++---
 .../Get-MailboxExportRequestStatistics.md                 | 6 +++---
 .../exchange-ps/ExchangePowerShell/Get-MailboxFolder.md   | 4 ++--
 .../ExchangePowerShell/Get-MailboxFolderPermission.md     | 4 ++--
 .../ExchangePowerShell/Get-MailboxFolderStatistics.md     | 4 ++--
 .../ExchangePowerShell/Get-MailboxIRMAccess.md            | 2 +-
 .../ExchangePowerShell/Get-MailboxImportRequest.md        | 8 ++++----
 .../Get-MailboxImportRequestStatistics.md                 | 4 ++--
 .../Get-MailboxJunkEmailConfiguration.md                  | 4 ++--
 .../exchange-ps/ExchangePowerShell/Get-MailboxLocation.md | 4 ++--
 .../ExchangePowerShell/Get-MailboxMessageConfiguration.md | 4 ++--
 .../ExchangePowerShell/Get-MailboxPermission.md           | 6 +++---
 .../exchange-ps/ExchangePowerShell/Get-MailboxPlan.md     | 2 +-
 .../Get-MailboxRegionalConfiguration.md                   | 4 ++--
 .../ExchangePowerShell/Get-MailboxRepairRequest.md        | 2 +-
 .../ExchangePowerShell/Get-MailboxRestoreRequest.md       | 6 +++---
 .../Get-MailboxRestoreRequestStatistics.md                | 4 ++--
 95 files changed, 121 insertions(+), 121 deletions(-)

diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DataEncryptionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-DataEncryptionPolicy.md
index a1d0a13841..93b66367bd 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DataEncryptionPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-DataEncryptionPolicy.md
@@ -34,7 +34,7 @@ Data encryption policy cmdlets are the Exchange Online part of Customer Key. For
 
 You can assign a data encryption policy to a mailbox by using the DataEncryptionPolicy parameter on the Set-Mailbox cmdlet in Exchange Online PowerShell.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DeliveryAgentConnector.md b/exchange/exchange-ps/ExchangePowerShell/Get-DeliveryAgentConnector.md
index 158918e113..985c0a3e68 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DeliveryAgentConnector.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-DeliveryAgentConnector.md
@@ -30,7 +30,7 @@ Get-DeliveryAgentConnector [[-Identity] <DeliveryAgentConnectorIdParameter>]
 ## DESCRIPTION
 Delivery agent connectors are used to route messages addressed to foreign systems that don't use the SMTP protocol. When a message is routed to a delivery agent connector, the associated delivery agent performs the content conversion and message delivery. Delivery agent connectors allow queue management of foreign connectors, thereby eliminating the need for storing messages on the file system in Drop and Pickup directories. For more information, see [Delivery agents and Delivery Agent connectors](https://learn.microsoft.com/exchange/delivery-agents-and-delivery-agent-connectors-exchange-2013-help).
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DetailZapReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-DetailZapReport.md
index 259eb9844a..71c067b620 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DetailZapReport.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-DetailZapReport.md
@@ -48,7 +48,7 @@ If you append the command with ` | Format-List`, the following additional inform
 - Delivery Status
 - Detection Technology
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DetailsTemplate.md b/exchange/exchange-ps/ExchangePowerShell/Get-DetailsTemplate.md
index ba5338a4a8..db826becce 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DetailsTemplate.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-DetailsTemplate.md
@@ -32,7 +32,7 @@ Get-DetailsTemplate [[-Identity] <DetailsTemplateIdParameter>]
 ## DESCRIPTION
 The Get-DetailsTemplate cmdlet retrieves the attributes for one or more details templates. Wildcard characters can be used when specifying the type and language of the details templates.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DistributionGroup.md b/exchange/exchange-ps/ExchangePowerShell/Get-DistributionGroup.md
index 19775f1e8f..db98febfb6 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DistributionGroup.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-DistributionGroup.md
@@ -85,7 +85,7 @@ Get-DistributionGroup [-Credential <PSCredential>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DistributionGroupMember.md b/exchange/exchange-ps/ExchangePowerShell/Get-DistributionGroupMember.md
index 9bd3ff56a4..fced01ba5f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DistributionGroupMember.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-DistributionGroupMember.md
@@ -35,7 +35,7 @@ Get-DistributionGroupMember [-Identity] <DistributionGroupMemberIdParameter>
 ## DESCRIPTION
 If your organization has multiple Active Directory domains, you might need to run the Set-ADServerSettings cmdlet with the ViewEntireForest parameter set to $true before running the Get-DistributionGroupMember cmdlet to view the entire forest. For more information, see Example 2.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DkimSigningConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-DkimSigningConfig.md
index 89e4889084..edabbe60c2 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DkimSigningConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-DkimSigningConfig.md
@@ -29,7 +29,7 @@ Get-DkimSigningConfig [[-Identity] <DkimSigningConfigIdParameter>]
 ## DESCRIPTION
 DKIM in Microsoft 365 is an email authentication method that uses a public key infrastructure (PKI), message headers and CNAME records in DNS to authenticate the message sender, which is stamped in the DKIM-Signature header field. DKIM helps prevent forged sender email addresses (also known as spoofing) by verifying that the domain in the From address matches the domain in the DKIM-Signature header field.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DlpDetailReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-DlpDetailReport.md
index 1aad6efd02..e210567039 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DlpDetailReport.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-DlpDetailReport.md
@@ -61,7 +61,7 @@ The Get-DlpDetailReport cmdlet returns detailed information about specific DLP r
 
 To see DLP detection data that's aggregated per day, use the [Get-DlpDetectionsReport](https://learn.microsoft.com/powershell/module/exchangepowershell/get-dlpdetectionsreport) cmdlet.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DlpDetectionsReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-DlpDetectionsReport.md
index 5d9632faf6..db6246c871 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DlpDetectionsReport.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-DlpDetectionsReport.md
@@ -53,7 +53,7 @@ To see all of these columns (width issues), write the output to a file. For exam
 
 To see detailed information about each DLP rule match, use the Get-DlpDetailReport cmdlet.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DlpIncidentDetailReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-DlpIncidentDetailReport.md
index 6b5f5fb3b1..e5e31d5ac0 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DlpIncidentDetailReport.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-DlpIncidentDetailReport.md
@@ -66,7 +66,7 @@ The output of the Get-DlpIncidentDetailReport cmdlet includes the following prop
 - SensitiveInformationCountList
 - SensitiveInformationConfidenceList
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DlpPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-DlpPolicy.md
index 65c660582f..e211930a67 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DlpPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-DlpPolicy.md
@@ -30,7 +30,7 @@ Get-DlpPolicy [[-Identity] <DlpPolicyIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DlpPolicyTemplate.md b/exchange/exchange-ps/ExchangePowerShell/Get-DlpPolicyTemplate.md
index b3260543ef..7152f5927d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DlpPolicyTemplate.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-DlpPolicyTemplate.md
@@ -30,7 +30,7 @@ Get-DlpPolicyTemplate [[-Identity] <DlpPolicyIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DnssecStatusForVerifiedDomain.md b/exchange/exchange-ps/ExchangePowerShell/Get-DnssecStatusForVerifiedDomain.md
index 282963d2eb..db6ed9f581 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DnssecStatusForVerifiedDomain.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-DnssecStatusForVerifiedDomain.md
@@ -34,7 +34,7 @@ Get-DnssecStatusForVerifiedDomain [-DomainName] <String>
 ## DESCRIPTION
 For more information about debugging, enabling, and disabling SMTP DANE with DNSSEC, see [How SMTP DANE works](https://learn.microsoft.com/purview/how-smtp-dane-works).
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DomainController.md b/exchange/exchange-ps/ExchangePowerShell/Get-DomainController.md
index 5ef1c821e9..17becbdbe3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DomainController.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-DomainController.md
@@ -40,7 +40,7 @@ Get-DomainController [-DomainName <Fqdn>]
 
 The Get-DomainController cmdlet is used by the Exchange admin center to populate fields that display domain controller information.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DynamicDistributionGroup.md b/exchange/exchange-ps/ExchangePowerShell/Get-DynamicDistributionGroup.md
index 85d20b7657..5b6aa5a8d5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DynamicDistributionGroup.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-DynamicDistributionGroup.md
@@ -90,7 +90,7 @@ Get-DynamicDistributionGroup [-ManagedBy <GeneralRecipientIdParameter>]
 ## DESCRIPTION
 A dynamic distribution group queries mail-enabled objects and builds the group membership based on the results. The group membership is recalculated whenever an email message is sent to the group.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DynamicDistributionGroupMember.md b/exchange/exchange-ps/ExchangePowerShell/Get-DynamicDistributionGroupMember.md
index 73b6f4ac35..52dea07cde 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DynamicDistributionGroupMember.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-DynamicDistributionGroupMember.md
@@ -32,7 +32,7 @@ Get-DynamicDistributionGroupMember [-Identity] <DynamicDistributionGroupMemberId
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-EOPProtectionPolicyRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-EOPProtectionPolicyRule.md
index 4367780130..96a4b4e058 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-EOPProtectionPolicyRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-EOPProtectionPolicyRule.md
@@ -30,7 +30,7 @@ Get-EOPProtectionPolicyRule [[-Identity] <RuleIdParameter>]
 ## DESCRIPTION
 For more information about preset security policies in PowerShell, see [Preset security policies in Exchange Online PowerShell](https://learn.microsoft.com/defender-office-365/preset-security-policies#preset-security-policies-in-exchange-online-powershell).
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-EcpVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Get-EcpVirtualDirectory.md
index a892d29bdf..f16142ba9d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-EcpVirtualDirectory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-EcpVirtualDirectory.md
@@ -42,7 +42,7 @@ Get-EcpVirtualDirectory [[-Identity] <VirtualDirectoryIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-EdgeSubscription.md b/exchange/exchange-ps/ExchangePowerShell/Get-EdgeSubscription.md
index 0bcc05c3a9..848fef4f46 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-EdgeSubscription.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-EdgeSubscription.md
@@ -30,7 +30,7 @@ Get-EdgeSubscription [[-Identity] <TransportServerIdParameter>]
 ## DESCRIPTION
 Run the Get-EdgeSubscription cmdlet on an Exchange server in your organization. This cmdlet retrieves the list of Edge Subscriptions. Each Edge Transport server that's subscribed to the Exchange organization has a separate Edge Subscription. You can use this cmdlet to view the Edge Subscription information for a specific Edge Transport server. You can also use this cmdlet to view the Edge Subscription information for all Edge Transport servers subscribed to Active Directory sites.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-EdgeSyncServiceConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-EdgeSyncServiceConfig.md
index d10d31d535..cf67707480 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-EdgeSyncServiceConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-EdgeSyncServiceConfig.md
@@ -29,7 +29,7 @@ Get-EdgeSyncServiceConfig [[-Identity] <EdgeSyncServiceConfigIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-EligibleDistributionGroupForMigration.md b/exchange/exchange-ps/ExchangePowerShell/Get-EligibleDistributionGroupForMigration.md
index 85571cd4b0..18f1ca9705 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-EligibleDistributionGroupForMigration.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-EligibleDistributionGroupForMigration.md
@@ -38,7 +38,7 @@ Get-EligibleDistributionGroupForMigration [-ManagedBy <GeneralRecipientIdParamet
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-EmailAddressPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-EmailAddressPolicy.md
index 7a18f54fe9..6b73acce8c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-EmailAddressPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-EmailAddressPolicy.md
@@ -29,7 +29,7 @@ Get-EmailAddressPolicy [[-Identity] <EmailAddressPolicyIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-EmailTenantSettings.md b/exchange/exchange-ps/ExchangePowerShell/Get-EmailTenantSettings.md
index 48232a093d..f8e70e2a35 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-EmailTenantSettings.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-EmailTenantSettings.md
@@ -26,7 +26,7 @@ Get-EmailTenantSettings [[-Identity] <EmailTenantSettingsIdParameter>] [<CommonP
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-EtrLimits.md b/exchange/exchange-ps/ExchangePowerShell/Get-EtrLimits.md
index 0d338fcdc2..9e785a6cc9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-EtrLimits.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-EtrLimits.md
@@ -26,7 +26,7 @@ Get-EtrLimits [<CommonParameters>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-EventLogLevel.md b/exchange/exchange-ps/ExchangePowerShell/Get-EventLogLevel.md
index 0e6199f755..28431d01ac 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-EventLogLevel.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-EventLogLevel.md
@@ -36,7 +36,7 @@ Get-EventLogLevel [[-Identity] <ECIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-EventsFromEmailConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Get-EventsFromEmailConfiguration.md
index 25832eb908..52e03a6dbd 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-EventsFromEmailConfiguration.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-EventsFromEmailConfiguration.md
@@ -29,7 +29,7 @@ Get-EventsFromEmailConfiguration [-Identity] <RecipientIdParameter>
 ## DESCRIPTION
 **Note**: The following output properties have been deprecated: EventReservationProcessingLevel, FoodEstablishmentReservationProcessingLevel, InvoiceProcessingLevel, and ServiceReservationProcessingLevel.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeAssistanceConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeAssistanceConfig.md
index ab03c82edf..41ba1e52ca 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeAssistanceConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeAssistanceConfig.md
@@ -28,7 +28,7 @@ Get-ExchangeAssistanceConfig [[-Identity] <OrganizationIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeCertificate.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeCertificate.md
index 0931257c1a..1a7503a3a4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeCertificate.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeCertificate.md
@@ -92,7 +92,7 @@ If you append ` | Format-List *` to the command, the cmdlet returns these additi
 - SubjectName: Typically, this value is System.Security.Cryptography.X509Certificates.X500DistinguishedName.
 - Version: Typically, this value is 3.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeDiagnosticInfo.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeDiagnosticInfo.md
index f0d225dc85..8bf3fbf192 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeDiagnosticInfo.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeDiagnosticInfo.md
@@ -31,7 +31,7 @@ Get-ExchangeDiagnosticInfo [-Argument <String>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeFeature.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeFeature.md
index 66aa3b8ac0..b9e03ef705 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeFeature.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeFeature.md
@@ -31,7 +31,7 @@ Get-ExchangeFeature [-Identity <ServerIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServer.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServer.md
index 0765cedd81..c98652453b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServer.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServer.md
@@ -42,7 +42,7 @@ Get-ExchangeServer [[-Identity] <ServerIdParameter>]
 ## DESCRIPTION
 The ExchangeVersion attribute returned is the minimum version of Microsoft Exchange that you can use to manage the returned object. This attribute isn't the same as the version of Exchange displayed in the Exchange admin center when you select Server Configuration.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServerAccessLicense.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServerAccessLicense.md
index 3bb1ee430a..f9685a6836 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServerAccessLicense.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServerAccessLicense.md
@@ -33,7 +33,7 @@ The Get-ExchangeServerAccessLicense cmdlet returns a collection of these license
 - Exchange Server Standard Edition
 - Exchange Server Enterprise Edition
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServerAccessLicenseUser.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServerAccessLicenseUser.md
index eb7f39eb5d..983741a576 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServerAccessLicenseUser.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServerAccessLicenseUser.md
@@ -29,7 +29,7 @@ Get-ExchangeServerAccessLicenseUser -LicenseName <String>
 ## DESCRIPTION
 The Get-ExchangeServerAccessLicenseUser cmdlet returns a collection of unique users for the specified license name. The list of unique users represents an estimate of your licenses when you run this cmdlet. Each object contains the FQDN or primary SMTP address of the mailbox and the license name to which it's associated.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeSettings.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeSettings.md
index d1d449f8f3..b3c862a120 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeSettings.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeSettings.md
@@ -40,7 +40,7 @@ Get-ExchangeSettings [[-Identity] <ExchangeSettingsIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ExoInformationBarrierPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExoInformationBarrierPolicy.md
index c7bf951bbb..39d0c63f23 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ExoInformationBarrierPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExoInformationBarrierPolicy.md
@@ -26,7 +26,7 @@ Get-ExoInformationBarrierPolicy [[-Identity] <MailboxPolicyIdParameter>] [-ShowF
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ExoInformationBarrierRelationship.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExoInformationBarrierRelationship.md
index 77602601cd..1adfb6db00 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ExoInformationBarrierRelationship.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExoInformationBarrierRelationship.md
@@ -27,7 +27,7 @@ Get-ExoInformationBarrierRelationship -RecipientId1 <RecipientIdParameter> -Reci
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ExoInformationBarrierSegment.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExoInformationBarrierSegment.md
index b66215c355..4abb7a13a8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ExoInformationBarrierSegment.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExoInformationBarrierSegment.md
@@ -26,7 +26,7 @@ Get-ExoInformationBarrierSegment [[-Identity] <InformationBarrierSegmentIdParame
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ExoPhishSimOverrideRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExoPhishSimOverrideRule.md
index 17a8d7192e..bd2639d1b8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ExoPhishSimOverrideRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExoPhishSimOverrideRule.md
@@ -31,7 +31,7 @@ Get-ExoPhishSimOverrideRule [[-Identity] <ComplianceRuleIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ExoSecOpsOverrideRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExoSecOpsOverrideRule.md
index 3d42a3cbcf..958273ae8c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ExoSecOpsOverrideRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExoSecOpsOverrideRule.md
@@ -31,7 +31,7 @@ Get-ExoSecOpsOverrideRule [[-Identity] <ComplianceRuleIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ExternalInOutlook.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExternalInOutlook.md
index b33e844ca7..4a833e7025 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ExternalInOutlook.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExternalInOutlook.md
@@ -31,7 +31,7 @@ The important properties that are returned in the output of this cmdlet are:
 - Enabled: True means the feature is enabled; False means the feature is disabled.
 - AllowList: The list of exceptions. Messages received from the specified senders or senders in the specified domains don't receive the External icon in the area of subject line.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-FailedContentIndexDocuments.md b/exchange/exchange-ps/ExchangePowerShell/Get-FailedContentIndexDocuments.md
index e86dea6e67..5bfda847f8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-FailedContentIndexDocuments.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-FailedContentIndexDocuments.md
@@ -71,7 +71,7 @@ After a new filter is installed, only new messages with attachments of the type
 
 The cmdlet output provides details about items in a mailbox that couldn't be indexed, including an error code and the reason for failure.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-FederatedDomainProof.md b/exchange/exchange-ps/ExchangePowerShell/Get-FederatedDomainProof.md
index 4fe0da6daa..4885ae058c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-FederatedDomainProof.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-FederatedDomainProof.md
@@ -31,7 +31,7 @@ Get-FederatedDomainProof -DomainName <SmtpDomain>
 ## DESCRIPTION
 The Get-FederatedDomainProof cmdlet generates a cryptographically secure string for the domain used for federated sharing. The resulting string is used to manually configure a text (TXT) record in the Domain Name System (DNS) zone for the domain used by the administrator when running the cmdlet. A TXT record needs to be added to DNS for all accepted domains used for federated sharing. If the thumbprint of a certificate isn't provided, the task generates strings for all the certificates currently configured for the federation trust. Upon initial configuration of federated sharing, the proof string generated for the current certificate needs to be put into the TXT record for the federated domain in DNS. We recommend you update the TXT records whenever a new certificate is configured for the federation trust.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-FederatedOrganizationIdentifier.md b/exchange/exchange-ps/ExchangePowerShell/Get-FederatedOrganizationIdentifier.md
index 47e2fce1d9..aedaada0b0 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-FederatedOrganizationIdentifier.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-FederatedOrganizationIdentifier.md
@@ -31,7 +31,7 @@ Get-FederatedOrganizationIdentifier [[-Identity] <OrganizationIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-FederationInformation.md b/exchange/exchange-ps/ExchangePowerShell/Get-FederationInformation.md
index c270d36671..cbc458cea9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-FederationInformation.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-FederationInformation.md
@@ -35,7 +35,7 @@ Get-FederationInformation -DomainName <SmtpDomain>
 ## DESCRIPTION
 The Get-FederationInformation cmdlet retrieves federation information from the specified domain, which should have federation enabled.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-FederationTrust.md b/exchange/exchange-ps/ExchangePowerShell/Get-FederationTrust.md
index 56f0ba4831..a6583ce2f7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-FederationTrust.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-FederationTrust.md
@@ -28,7 +28,7 @@ Get-FederationTrust [[-Identity] <FederationTrustIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-FocusedInbox.md b/exchange/exchange-ps/ExchangePowerShell/Get-FocusedInbox.md
index b1f7e2b8ea..bf5e31049a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-FocusedInbox.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-FocusedInbox.md
@@ -30,7 +30,7 @@ Get-FocusedInbox -Identity <MailboxIdParameter>
 ## DESCRIPTION
 Focused Inbox is a replacement for Clutter that separates the Inbox into the Focused and Other tabs in Outlook on the web and newer versions of Outlook. Important emails are on the Focused tab while the rest are on the Other tab.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ForeignConnector.md b/exchange/exchange-ps/ExchangePowerShell/Get-ForeignConnector.md
index 6aa7779b61..e2055e5041 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ForeignConnector.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ForeignConnector.md
@@ -28,7 +28,7 @@ Get-ForeignConnector [[-Identity] <ForeignConnectorIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-FrontendTransportService.md b/exchange/exchange-ps/ExchangePowerShell/Get-FrontendTransportService.md
index 0e1874937a..ff407fa6e7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-FrontendTransportService.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-FrontendTransportService.md
@@ -30,7 +30,7 @@ Get-FrontendTransportService [[-Identity] <FrontendTransportServerIdParameter>]
 ## DESCRIPTION
 The Front End Transport service acts as a stateless proxy for all inbound and outbound external SMTP traffic for the Exchange organization.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-GlobalAddressList.md b/exchange/exchange-ps/ExchangePowerShell/Get-GlobalAddressList.md
index 71b37b5867..9f93791074 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-GlobalAddressList.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-GlobalAddressList.md
@@ -40,7 +40,7 @@ Get-GlobalAddressList [[-Identity] <GlobalAddressListIdParameter>]
 ## DESCRIPTION
 The Get-GlobalAddressList cmdlet is mainly used to populate the GAL property pages in the Exchange admin center. This command doesn't provide a filtering capability. If filtering is required, you should use a WHERE clause with the command.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-GlobalMonitoringOverride.md b/exchange/exchange-ps/ExchangePowerShell/Get-GlobalMonitoringOverride.md
index 5b523b365d..75a07338cb 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-GlobalMonitoringOverride.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-GlobalMonitoringOverride.md
@@ -27,7 +27,7 @@ Get-GlobalMonitoringOverride [-DomainController <Fqdn>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-Group.md b/exchange/exchange-ps/ExchangePowerShell/Get-Group.md
index 7a8fd3d370..175c1c7ad4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-Group.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-Group.md
@@ -54,7 +54,7 @@ Get-Group [[-Identity] <GroupIdParameter>]
 ## DESCRIPTION
 The Get-Group cmdlet returns no mail-related properties for distribution groups or mail-enabled security groups, and no role group-related properties for role groups. To view the object-specific properties for a group, you need to use the corresponding cmdlet based on the object type (for example, Get-DistributionGroup or Get-RoleGroup).
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-HealthReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-HealthReport.md
index b729e36b53..8629351a23 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-HealthReport.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-HealthReport.md
@@ -41,7 +41,7 @@ The following list contains the health values that are returned:
 - Functional
 - Unavailable
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-HistoricalSearch.md b/exchange/exchange-ps/ExchangePowerShell/Get-HistoricalSearch.md
index 97064d9895..3f1e3f33d2 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-HistoricalSearch.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-HistoricalSearch.md
@@ -29,7 +29,7 @@ Get-HistoricalSearch [-JobId <Guid>]
 ## DESCRIPTION
 A historical search provides message trace and report details in a comma-separated value (CSV) file for messages that are less than 90 days old.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-HostedConnectionFilterPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-HostedConnectionFilterPolicy.md
index 9207a2a0e7..6a277a7fed 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-HostedConnectionFilterPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-HostedConnectionFilterPolicy.md
@@ -27,7 +27,7 @@ Get-HostedConnectionFilterPolicy [[-Identity] <HostedConnectionFilterPolicyIdPar
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-HostedContentFilterPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-HostedContentFilterPolicy.md
index bf029648b2..ad081ea01c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-HostedContentFilterPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-HostedContentFilterPolicy.md
@@ -27,7 +27,7 @@ Get-HostedContentFilterPolicy [[-Identity] <HostedContentFilterPolicyIdParameter
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-HostedContentFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-HostedContentFilterRule.md
index 23b47a8a79..61414d2265 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-HostedContentFilterRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-HostedContentFilterRule.md
@@ -29,7 +29,7 @@ Get-HostedContentFilterRule [[-Identity] <RuleIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-HostedOutboundSpamFilterPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-HostedOutboundSpamFilterPolicy.md
index 3259b337b8..c1b6455966 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-HostedOutboundSpamFilterPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-HostedOutboundSpamFilterPolicy.md
@@ -27,7 +27,7 @@ Get-HostedOutboundSpamFilterPolicy [-Identity] <HostedOutboundSpamFilterPolicyId
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-HostedOutboundSpamFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-HostedOutboundSpamFilterRule.md
index 0e251e98d8..e5e9fb6b86 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-HostedOutboundSpamFilterRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-HostedOutboundSpamFilterRule.md
@@ -28,7 +28,7 @@ Get-HostedOutboundSpamFilterRule [[-Identity] <RuleIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-HybridConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Get-HybridConfiguration.md
index f1c086874f..2d7cd5fc46 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-HybridConfiguration.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-HybridConfiguration.md
@@ -27,7 +27,7 @@ Get-HybridConfiguration [-DomainController <Fqdn>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-IPv6StatusForAcceptedDomain.md b/exchange/exchange-ps/ExchangePowerShell/Get-IPv6StatusForAcceptedDomain.md
index 341dfde6a7..8315774650 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-IPv6StatusForAcceptedDomain.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-IPv6StatusForAcceptedDomain.md
@@ -32,7 +32,7 @@ Use the Get-AcceptedDomain cmdlet to return accepted domains in the Exchange Onl
 
 If IPv6 is enabled for an accepted domain in Exchange Online, IPv4 and IPv6 addresses are returned in DNS queries for mail flow records of the domain. If IPv6 is disabled, only IPv4 addresses are returned in DNS queries for mail flow records of the domain.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 > [!NOTE]
 >
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-IRMConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Get-IRMConfiguration.md
index 4e66c8198d..34e73d32b3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-IRMConfiguration.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-IRMConfiguration.md
@@ -29,7 +29,7 @@ Get-IRMConfiguration [-DomainController <Fqdn>]
 ## DESCRIPTION
 The Get-IRMConfiguration cmdlet provides details about the current IRM configuration, including whether individual IRM features are enabled or disabled and provides the URLs used for ServiceLocation, PublishingLocation and LicensingLocation.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ImapSettings.md b/exchange/exchange-ps/ExchangePowerShell/Get-ImapSettings.md
index 3e3bc98b54..aa7c94f41a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ImapSettings.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ImapSettings.md
@@ -28,7 +28,7 @@ Get-ImapSettings [-DomainController <Fqdn>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-InboundConnector.md b/exchange/exchange-ps/ExchangePowerShell/Get-InboundConnector.md
index 0dc6a2864e..cc7b89664c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-InboundConnector.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-InboundConnector.md
@@ -30,7 +30,7 @@ Get-InboundConnector [[-Identity] <InboundConnectorIdParameter>]
 ## DESCRIPTION
 Inbound connectors accept email messages from remote domains that require specific configuration options.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-InboxRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-InboxRule.md
index 13da496b00..d534f407cd 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-InboxRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-InboxRule.md
@@ -37,7 +37,7 @@ Get-InboxRule [[-Identity] <InboxRuleIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 **Note**: This cmdlet doesn't work for members of View-Only Organization Management role group in Exchange Online or the Global Reader role in Microsoft Entra ID.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-IntraOrganizationConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Get-IntraOrganizationConfiguration.md
index 3c8a1400ef..c604bab845 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-IntraOrganizationConfiguration.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-IntraOrganizationConfiguration.md
@@ -31,7 +31,7 @@ A hybrid Exchange deployment results in one logical organization made up of a nu
 
 Hybrid environments are enabled by Intra-Organization connectors. The connectors can be created and managed by cmdlets like New-IntraOrganizationConnector, but we strongly recommend that you use the Hybrid Configuration wizard when configuring a hybrid deployment with an Exchange Online organization.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-IntraOrganizationConnector.md b/exchange/exchange-ps/ExchangePowerShell/Get-IntraOrganizationConnector.md
index f8c1970bfe..e1f54a76a5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-IntraOrganizationConnector.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-IntraOrganizationConnector.md
@@ -30,7 +30,7 @@ Get-IntraOrganizationConnector [[-Identity] <IntraOrganizationConnectorIdParamet
 ## DESCRIPTION
 Intra-Organizational connectors enable features and services between divisions in your Exchange organization. It allows for the expansion of organizational boundaries for features and services across different hosts and network boundaries, such as between Active Directory forests, between on-premises and cloud-based organizations, or between tenants hosted in the same or different datacenters.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-JournalRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-JournalRule.md
index 815d630a83..a5bf61f338 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-JournalRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-JournalRule.md
@@ -30,7 +30,7 @@ Get-JournalRule [[-Identity] <RuleIdParameter>]
 ## DESCRIPTION
 The Get-JournalRule cmdlet displays journal rules configured in your organization.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-LinkedUser.md b/exchange/exchange-ps/ExchangePowerShell/Get-LinkedUser.md
index b75371ad04..cc39479866 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-LinkedUser.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-LinkedUser.md
@@ -42,7 +42,7 @@ Get-LinkedUser [[-Identity] <UserIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-LogonStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-LogonStatistics.md
index b688ec17cc..d64ba0f423 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-LogonStatistics.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-LogonStatistics.md
@@ -47,7 +47,7 @@ The Get-LogonStatistics cmdlet retrieves logon information about currently activ
 
 Users who log on to their mailboxes using Microsoft Office Outlook Web App aren't continually connected to the Mailbox server. An Outlook Web App client connects to the server, performs tasks, and then disconnects from the server. Therefore, you might see few or no logon statistics for Outlook Web App, even if users are logged on with this client.
 
-You need to be assigned permissions before you can run this cmdlet. Although all parameters for this cmdlet are listed in this topic, you might not have access to some parameters if they're not included in the permissions assigned to you. To see what permissions you need, see the "Recipient Provisioning Permissions" section in the Mailbox Permissions topic.
+You need to be assigned permissions before you can run this cmdlet. Although all parameters for this cmdlet are listed in this topic, you might not have access to some parameters if they aren't included in the permissions assigned to you. To see what permissions you need, see the "Recipient Provisioning Permissions" section in the Mailbox Permissions topic.
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-M365DataAtRestEncryptionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-M365DataAtRestEncryptionPolicy.md
index 5fd747c8bd..1208f2a526 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-M365DataAtRestEncryptionPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-M365DataAtRestEncryptionPolicy.md
@@ -34,7 +34,7 @@ M365 data-at-rest encryption policy cmdlets are accessible to compliance adminis
 
 You can create and assign a Microsoft 365 data-at-rest encryption policy at the tenant level by using the appropriate M365DataAtRestEncryptionPolicy cmdlets in Exchange Online PowerShell.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-M365DataAtRestEncryptionPolicyAssignment.md b/exchange/exchange-ps/ExchangePowerShell/Get-M365DataAtRestEncryptionPolicyAssignment.md
index a27e3b6d3f..a069af8112 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-M365DataAtRestEncryptionPolicyAssignment.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-M365DataAtRestEncryptionPolicyAssignment.md
@@ -28,7 +28,7 @@ Get-M365DataAtRestEncryptionPolicyAssignment [<CommonParameters>]
 ## DESCRIPTION
 This cmdlet lists the Microsoft 365 data-at-rest encryption policy that's currently assigned to the tenant.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-Mailbox.md b/exchange/exchange-ps/ExchangePowerShell/Get-Mailbox.md
index 8025e351a4..b1f77201f7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-Mailbox.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-Mailbox.md
@@ -168,7 +168,7 @@ Get-Mailbox [-MailboxPlan <MailboxPlanIdParameter>]
 ## DESCRIPTION
 When you use the Get-Mailbox cmdlet in on-premises Exchange environments to view the quota settings for a mailbox, you first need to check the value of the UseDatabaseQuotaDefaults property. The value True means per-mailbox quota settings are ignored, and you need to use the Get-MailboxDatabase cmdlet to see the actual values. If the UseDatabaseQuotaDefaults property is False, the per-mailbox quota settings are used, so what you see with the Get-Mailbox cmdlet are the actual quota values for the mailbox.
 
-You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxAuditBypassAssociation.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxAuditBypassAssociation.md
index 6085bdb0ae..909b2e8062 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxAuditBypassAssociation.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxAuditBypassAssociation.md
@@ -13,7 +13,7 @@ title: Get-MailboxAuditBypassAssociation
 # Get-MailboxAuditBypassAssociation
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-MailboxAuditBypassAssociation cmdlet to retrieve information about the AuditBypassEnabled property value for user accounts (on-premises Exchange and the cloud) and computer accounts (on-premises Exchange only). You use the [Set-MailboxAuditBypassAssociation](https://learn.microsoft.com/powershell/module/exchangepowershell/set-mailboxauditbypassassociation) cmdlet to enable this property to bypass mailbox audit logging.
 
@@ -31,7 +31,7 @@ Get-MailboxAuditBypassAssociation [[-Identity] <MailboxAuditBypassAssociationIdP
 ## DESCRIPTION
 When you configure a user or computer account to bypass mailbox audit logging, access or actions taken by the user account or computer account to any mailbox isn't logged. By bypassing trusted user accounts or computer accounts that need to access mailboxes frequently, you can reduce the noise in mailbox audit logs.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxAutoReplyConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxAutoReplyConfiguration.md
index cee567d5c3..35f606e712 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxAutoReplyConfiguration.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxAutoReplyConfiguration.md
@@ -13,7 +13,7 @@ title: Get-MailboxAutoReplyConfiguration
 # Get-MailboxAutoReplyConfiguration
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-MailboxAutoReplyConfiguration cmdlet to retrieve Automatic Replies settings for a specific mailbox.
 
@@ -36,11 +36,11 @@ You can use the Get-MailboxAutoReplyConfiguration cmdlet to retrieve all the mai
 
 - Mailbox identity value
 - Whether Automatic Replies is enabled, scheduled, or disabled for the mailbox
-- Start and end date, time during which Automatic Replies will be sent
+- Start and end date, time during which Automatic Replies are sent
 - Whether external senders receive Automatic Replies (none, known senders, or all)
 - Automatic Replies message to be sent to internal and external senders
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxCalendarConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxCalendarConfiguration.md
index bb084b22b9..4001d80f30 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxCalendarConfiguration.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxCalendarConfiguration.md
@@ -13,7 +13,7 @@ title: Get-MailboxCalendarConfiguration
 # Get-MailboxCalendarConfiguration
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-MailboxCalendarConfiguration cmdlet to show the calendar settings for a specified mailbox.
 
@@ -53,7 +53,7 @@ The Get-MailboxCalendarConfiguration cmdlet returns settings for the calendar of
 
 To see all of the settings returned, pipeline the command to the Format-List command. To view a code sample, see "Example 1."
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxCalendarFolder.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxCalendarFolder.md
index 39190a3f18..c0a830aac8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxCalendarFolder.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxCalendarFolder.md
@@ -13,7 +13,7 @@ title: Get-MailboxCalendarFolder
 # Get-MailboxCalendarFolder
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-MailboxCalendarFolder cmdlet to retrieve the publishing or sharing settings for a specified mailbox calendar folder.
 
@@ -31,7 +31,7 @@ Get-MailboxCalendarFolder [-Identity] <MailboxFolderIdParameter>
 ## DESCRIPTION
 The Get-MailboxCalendarFolder cmdlet retrieves information for the specified calendar folder. This information includes the calendar folder name, whether the folder is currently published or shared, the start and end range of calendar days published, the level of details published for the calendar, whether the published URL of the calendar can be searched on the web and the published URL for the calendar.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxDatabase.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxDatabase.md
index d0c9fca722..91f420193f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxDatabase.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxDatabase.md
@@ -55,7 +55,7 @@ The following list describes the properties that are returned in the results.
 - Recovery: Specifies whether the new database is designated as a recovery database.
 - ReplicationType: Replication type of the database.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxDatabaseCopyStatus.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxDatabaseCopyStatus.md
index 90105c739e..e4b66a20fa 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxDatabaseCopyStatus.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxDatabaseCopyStatus.md
@@ -47,7 +47,7 @@ Get-MailboxDatabaseCopyStatus [[-Identity] <DatabaseCopyIdParameter>]
 ## DESCRIPTION
 If a database is specified by using the Identity parameter with the command, the status of all copies of the database is returned. If a server is specified by using the Server parameter with the command, information about all database copies on the server is returned. If neither parameter is specified with the command, information about all database copies in the organization is returned.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -132,7 +132,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-This parameter has been deprecated and is no longer used.
+This parameter is deprecated and no longer used.
 
 ```yaml
 Type: SwitchParameter
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxExportRequest.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxExportRequest.md
index 15d115b5e7..ea3af86b8e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxExportRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxExportRequest.md
@@ -64,7 +64,7 @@ Get-MailboxExportRequest [-Mailbox <MailboxLocationIdParameter>]
 ## DESCRIPTION
 The search criteria for the Get-MailboxExportRequest cmdlet is a Boolean And statement. If you use multiple parameters, you narrow your search and reduce your search results.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -94,7 +94,7 @@ This example returns the status of export requests in the Attachment\_CompanyRep
 Get-MailboxExportRequest -Name "DB01toPST" -Suspend $true
 ```
 
-This example returns all export requests that have the name DB01toPST where the export has been suspended.
+This example returns all export requests that have the name DB01toPST where the export is suspended.
 
 ## PARAMETERS
 
@@ -308,7 +308,7 @@ The Status parameter filters the results based on status. You can use the follow
 
 You can't use this parameter with the Identity parameter.
 
-CompletionInProgress and AutoSuspended don't apply to export requests and won't return any information.
+CompletionInProgress and AutoSuspended don't apply to export requests and doesn't return any information.
 
 ```yaml
 Type: RequestStatus
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxExportRequestStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxExportRequestStatistics.md
index d5f0ed8fe8..5877037fe2 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxExportRequestStatistics.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxExportRequestStatistics.md
@@ -58,7 +58,7 @@ Get-MailboxExportRequestStatistics -RequestQueue <DatabaseIdParameter>
 ## DESCRIPTION
 You can pipeline the Get-MailboxExportRequestStatistics cmdlet from the Get-MailboxExportRequest cmdlet.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -88,14 +88,14 @@ This example returns additional information about the export request for Tony Sm
 Get-MailboxExportRequestStatistics -MRSInstance CAS01.contoso.com
 ```
 
-In Exchange Server 2010, this example returns default statistics for an export request being processed by the instance of MRS running on the server CAS01. This command only returns information for export requests that are currently being processed by an instance of MRS. If the request is already finished, it won't be returned.
+In Exchange Server 2010, this example returns default statistics for an export request being processed by the instance of MRS running on the server CAS01. This command only returns information for export requests that are currently being processed by an instance of MRS. If the request is already finished, no information is returned.
 
 ### Example 5
 ```powershell
 Get-MailboxExportRequestStatistics -RequestQueue MailboxDatabase01
 ```
 
-This example returns default statistics for an export request being processed by the instance of MRS running on the server CAS01. This command only returns information for export requests currently being processed by an instance of MRS. If the request is already finished, it won't be returned.
+This example returns default statistics for an export request being processed by the instance of MRS running on the server CAS01. This command only returns information for export requests currently being processed by an instance of MRS. If the request is already finished, no information is returned.
 
 ### Example 6
 ```powershell
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxFolder.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxFolder.md
index 4f0450521d..681bdd6120 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxFolder.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxFolder.md
@@ -13,7 +13,7 @@ title: Get-MailboxFolder
 # Get-MailboxFolder
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-MailboxFolder cmdlet to view folders in your own mailbox. Administrators can't use this cmdlet to view folders in other mailboxes (the cmdlet is available only from the MyBaseOptions user role).
 
@@ -44,7 +44,7 @@ Get-MailboxFolder [[-Identity] <MailboxFolderIdParameter>]
 ## DESCRIPTION
 This command checks that the mailbox specified in the Identity parameter is a valid Exchange mailbox before retrieving the requested folders. The cmdlet returns all folders if the MailFolderOnly switch isn't specified.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxFolderPermission.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxFolderPermission.md
index 45768bf0e7..198d611d27 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxFolderPermission.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxFolderPermission.md
@@ -13,7 +13,7 @@ title: Get-MailboxFolderPermission
 # Get-MailboxFolderPermission
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-MailboxFolderPermission cmdlet to view folder-level permissions in mailboxes.
 
@@ -35,7 +35,7 @@ Get-MailboxFolderPermission [-Identity] <MailboxFolderIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxFolderStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxFolderStatistics.md
index 51eb753990..7bd91cd3c4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxFolderStatistics.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxFolderStatistics.md
@@ -13,7 +13,7 @@ title: Get-MailboxFolderStatistics
 # Get-MailboxFolderStatistics
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-MailboxFolderStatistics cmdlet to retrieve information about the folders in a specified mailbox, including the number and size of items in the folder, the folder name and ID, and other information.
 
@@ -68,7 +68,7 @@ Get-MailboxFolderStatistics -Database <DatabaseIdParameter> -StoreMailboxIdentit
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 A mailbox can have hidden items that are never visible to the user and are only used by applications. The Get-MailboxFolderStatistics cmdlet can return hidden items for the following values: FolderSize, FolderAndSubfolderSize, ItemsInFolder and ItemsInFolderAndSubfolders.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxIRMAccess.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxIRMAccess.md
index 5988155a36..a20f74e575 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxIRMAccess.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxIRMAccess.md
@@ -33,7 +33,7 @@ Get-MailboxIRMAccess [[-Identity] <MailboxIdParameter>]
 >
 > Delegates with Full Access permission to the mailbox who don't appear in the results of this cmdlet have access to IRM-protected messages. Only Full Access delegates who are blocked from reading IRM-protected messages in the mailbox appear in the results.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxImportRequest.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxImportRequest.md
index 26a0c1dd9f..0f27c0ce17 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxImportRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxImportRequest.md
@@ -13,7 +13,7 @@ title: Get-MailboxImportRequest
 # Get-MailboxImportRequest
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-MailboxImportRequest cmdlet to view the detailed status of an ongoing import request that was initiated using the New-MailboxImportRequest cmdlet.
 
@@ -66,7 +66,7 @@ Get-MailboxImportRequest
 ## DESCRIPTION
 The search criteria for the Get-MailboxImportRequest cmdlet is a Boolean And statement. If you use multiple parameters, you narrow your search and reduce your search results.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -96,7 +96,7 @@ This example returns the status of import requests in the ImportingDB1PSTs batch
 Get-MailboxImportRequest -Name "Recovered" -Suspend $true
 ```
 
-This example returns all import requests that have the name Recovered where the import has been suspended.
+This example returns all import requests that have the name Recovered where the import is suspended.
 
 ## PARAMETERS
 
@@ -314,7 +314,7 @@ The Status parameter filters the results based on status. You can use the follow
 
 You can't use this parameter with the Identity parameter.
 
-CompletionInProgress and AutoSuspended don't apply to import requests and won't return any information.
+CompletionInProgress and AutoSuspended don't apply to import requests and doesn't return any information.
 
 ```yaml
 Type: RequestStatus
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxImportRequestStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxImportRequestStatistics.md
index f2b4d0172b..9d553d04e1 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxImportRequestStatistics.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxImportRequestStatistics.md
@@ -13,7 +13,7 @@ title: Get-MailboxImportRequestStatistics
 # Get-MailboxImportRequestStatistics
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-MailboxImportRequestStatistics cmdlet to view detailed information about import requests.
 
@@ -67,7 +67,7 @@ Get-MailboxImportRequestStatistics -RequestQueue <DatabaseIdParameter>
 ## DESCRIPTION
 You can pipeline the Get-MailboxImportRequestStatistics cmdlet from the Get-MailboxImportRequest cmdlet.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxJunkEmailConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxJunkEmailConfiguration.md
index 2d93050ad9..4f7d3ec93d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxJunkEmailConfiguration.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxJunkEmailConfiguration.md
@@ -13,7 +13,7 @@ title: Get-MailboxJunkEmailConfiguration
 # Get-MailboxJunkEmailConfiguration
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-MailboxJunkEmailConfiguration cmdlet to view the junk email settings on mailboxes.
 
@@ -43,7 +43,7 @@ The junk email settings on the mailbox are:
 
 Administrators can enable or disable the junk email rule, and configure the safelist collection on a mailbox by using the Set-MailboxJunkEmailConfiguration cmdlet. For more information, see [Configure Exchange antispam settings on mailboxes](https://learn.microsoft.com/Exchange/antispam-and-antimalware/antispam-protection/configure-antispam-settings).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxLocation.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxLocation.md
index 49f45baaaf..13d0a15a7b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxLocation.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxLocation.md
@@ -13,7 +13,7 @@ title: Get-MailboxLocation
 # Get-MailboxLocation
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-MailboxLocation cmdlet to view mailbox location information in Exchange Online.
 
@@ -53,7 +53,7 @@ Get-MailboxLocation -User <UserIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxMessageConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxMessageConfiguration.md
index 973de8d9f7..c198362e18 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxMessageConfiguration.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxMessageConfiguration.md
@@ -13,7 +13,7 @@ title: Get-MailboxMessageConfiguration
 # Get-MailboxMessageConfiguration
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-MailboxMessageConfiguration cmdlet to view the Outlook on the web settings that are applied to specific mailboxes.
 
@@ -38,7 +38,7 @@ The Get-MailboxMessageConfiguration cmdlet shows Outlook on the web settings for
 > [!NOTE]
 > The SignatureHtml and SignatureText parameters don't work if the Outlook roaming signatures feature is enabled in your cloud-based organization. Currently, the only way to make these parameters work again is to open a support ticket and ask to have Outlook roaming signatures disabled in your organization.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxPermission.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxPermission.md
index 46b2722ed2..6a41b26466 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxPermission.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxPermission.md
@@ -13,7 +13,7 @@ title: Get-MailboxPermission
 # Get-MailboxPermission
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-MailboxPermission cmdlet to retrieve permissions on a mailbox.
 
@@ -64,13 +64,13 @@ By default, the following permissions are assigned to user mailboxes:
 
 - FullAccess and ReadPermission are directly assigned to NT AUTHORITY\\SELF. This entry gives a user permission to their own mailbox.
 - FullAccess is denied to Administrator, Domain Admins, Enterprise Admins and Organization Management. These inherited permissions prevent these users and group members from opening other users' mailboxes.
-- ChangeOwner, ChangePermission, DeleteItem, and ReadPermission are allowed for Administrator, Domain Admins, Enterprise Admins and Organization Management. Note that these inherited permission entries also appear to allow FullAccess. However, these users and groups do not have FullAccess to the mailbox because the inherited Deny permission entries override the inherited Allow permission entries.
+- ChangeOwner, ChangePermission, DeleteItem, and ReadPermission are allowed for Administrator, Domain Admins, Enterprise Admins and Organization Management. These inherited permission entries also appear to allow FullAccess. However, these users and groups do not have FullAccess to the mailbox because the inherited Deny permission entries override the inherited Allow permission entries.
 - FullAccess is inherited by NT AUTHORITY\\SYSTEM and ReadPermission is inherited by NT AUTHORITY\\NETWORK.
 - FullAccess and ReadPermission are inherited by Exchange Servers, ChangeOwner, ChangePermission, DeleteItem, and ReadPermission are inherited by Exchange Trusted Subsystem and ReadPermission is inherited by Managed Availability Servers.
 
 By default, other security groups and role groups inherit permissions to mailboxes based on their location (on-premises Exchange or Microsoft 365).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxPlan.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxPlan.md
index 76da58ae59..34dbb6428e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxPlan.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxPlan.md
@@ -35,7 +35,7 @@ Get-MailboxPlan [[-Identity] <MailboxPlanIdParameter>]
 ## DESCRIPTION
 A mailbox plan is a template that automatically configures mailbox properties. Mailbox plans correspond to license types, and are applied when you license the user. The availability of a mailbox plan is determined by your selections when you enroll in the service and the age of your organization.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxRegionalConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxRegionalConfiguration.md
index a44a8b5da5..23813b7c6f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxRegionalConfiguration.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxRegionalConfiguration.md
@@ -13,7 +13,7 @@ title: Get-MailboxRegionalConfiguration
 # Get-MailboxRegionalConfiguration
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-MailboxRegionalConfiguration cmdlet to view the regional settings of a mailbox. You can view the date format, time format, time zone, and language of the mailbox.
 
@@ -45,7 +45,7 @@ Get-MailboxRegionalConfiguration [-MailboxLocation <MailboxLocationIdParameter>]
 ## DESCRIPTION
 To modify the regional settings of a mailbox, use the [Set-MailboxRegionalConfiguration](https://learn.microsoft.com/powershell/module/exchangepowershell/set-mailboxregionalconfiguration) cmdlet.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxRepairRequest.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxRepairRequest.md
index d9224ee757..b7e31ea498 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxRepairRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxRepairRequest.md
@@ -52,7 +52,7 @@ The Get-MailboxRepairRequest cmdlet displays information about mailbox repair re
 - The status of the repair request; values are Queued, Running, Succeeded and Failed.
 - The date and time when the mailbox repair request was created and when it finished.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxRestoreRequest.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxRestoreRequest.md
index 91a54258e6..9f68aae6cd 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxRestoreRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxRestoreRequest.md
@@ -13,7 +13,7 @@ title: Get-MailboxRestoreRequest
 # Get-MailboxRestoreRequest
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-MailboxRestoreRequest cmdlet to view detailed status of an ongoing restore request that was initiated by using the New-MailboxRestoreRequest cmdlet.
 
@@ -46,7 +46,7 @@ Get-MailboxRestoreRequest [-BatchName <String>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -76,7 +76,7 @@ This example returns the status of in-progress and queued restore requests that
 Get-MailboxRestoreRequest -Name "RestoreToMBD01" -Suspend $true
 ```
 
-This example returns all restore requests that have the name RestoreToMBD01 where the restore request has been suspended.
+This example returns all restore requests that have the name RestoreToMBD01 where the restore request is suspended.
 
 ## PARAMETERS
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxRestoreRequestStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxRestoreRequestStatistics.md
index cf05e6387b..9ef9b9e6e7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxRestoreRequestStatistics.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxRestoreRequestStatistics.md
@@ -13,7 +13,7 @@ title: Get-MailboxRestoreRequestStatistics
 # Get-MailboxRestoreRequestStatistics
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-MailboxRestoreRequestStatistics cmdlet to view detailed information about restore requests.
 
@@ -63,7 +63,7 @@ Get-MailboxRestoreRequestStatistics -RequestQueue <DatabaseIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 

From ed44ed699a7d8ff5ba3d6824460842467848295c Mon Sep 17 00:00:00 2001
From: Chris Davis <chris.davis@microsoft.com>
Date: Wed, 6 Aug 2025 08:30:18 -0700
Subject: [PATCH 090/145] Update New-OrganizationRelationship.md

---
 .../ExchangePowerShell/New-OrganizationRelationship.md          | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/exchange/exchange-ps/ExchangePowerShell/New-OrganizationRelationship.md b/exchange/exchange-ps/ExchangePowerShell/New-OrganizationRelationship.md
index bdaaea5dc3..e18434a74d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-OrganizationRelationship.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-OrganizationRelationship.md
@@ -284,7 +284,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
 
-The FreeBusyAccessScope parameter specifies a mail-enabled security group in the internal organization that contains users whose free/busy information is accessible by an external organization. For best performance, groups should be smaller than 10,000 members. You can use any value that uniquely identifies the group. For example:
+The FreeBusyAccessScope parameter specifies an internal mail-enabled security group where member free/busy information is accessible by the external organization. For best performance, the group should have less than 10,000 members. You can use any value that uniquely identifies the group. For example:
 
 - Name
 - Distinguished name (DN)

From 8a58a5fe961ab347153fd68b31014b5f497a584f Mon Sep 17 00:00:00 2001
From: Chris Davis <chris.davis@microsoft.com>
Date: Wed, 6 Aug 2025 08:35:23 -0700
Subject: [PATCH 091/145] Update Add-AvailabilityAddressSpace.md

---
 .../Add-AvailabilityAddressSpace.md                  | 12 ++++++++----
 1 file changed, 8 insertions(+), 4 deletions(-)

diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-AvailabilityAddressSpace.md b/exchange/exchange-ps/ExchangePowerShell/Add-AvailabilityAddressSpace.md
index 0e4585433d..dde9b592f2 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-AvailabilityAddressSpace.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Add-AvailabilityAddressSpace.md
@@ -81,8 +81,8 @@ In Exchange Online, this example sets up the sharing of free/busy information wi
 The AccessMethod parameter specifies how the free/busy data is accessed. Valid values are:
 
 - PerUserFB: Per-user free/busy information can be requested. The free/busy data is accessed in the defined per-user free/busy proxy account or group, or in the All Exchange Servers group. This value requires a trust between the two forests, and requires you to use either the UseServiceAccount parameter or Credentials parameter.
-- OrgWideFB: Only the default free/busy for each user can be requested. The free/busy data is accessed in the per-user free/busy proxy account or group in the target forest. This value requires you to use either the UseServiceAccount parameter or Credentials parameter. This is deprecated for accessing target forests in Exchange Online.
-- OrgWideFBToken: Used for free/busy sharing between two tenants in Exchange Online. Only the default free/busy for each user can be requested. This option also requires you to set both TargetTenantId and TargetServiceEpr.
+- OrgWideFB: Only the default free/busy for each user can be requested. The free/busy data is accessed in the per-user free/busy proxy account or group in the target forest. This value requires you to use either the UseServiceAccount parameter or Credentials parameter. This value is deprecated for accessing target forests in Exchange Online.
+- OrgWideFBToken: Used for free/busy sharing between two tenants in Exchange Online. Only the default free/busy for each user can be requested. This value also requires you to set both the TargetTenantId and TargetServiceEpr parameters.
 - InternalProxy: The request is proxied to an Exchange server in the site that's running a later version of Exchange.
 - PublicFolder: This value was used to access free/busy data on Exchange Server 2003 servers.
 
@@ -221,7 +221,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online, Exchange Online Protection
 
-This parameter is available only in the cloud-based service and is only used when AccessMethod is OrgWideFBToken.
+This parameter is available only in the cloud-based service.
 
 The TargetServiceEpr parameter specifies the Exchange Online Calendar Service URL of the external Microsoft 365 organization that you're trying to read free/busy information from. Valid values are:
 
@@ -229,6 +229,8 @@ The TargetServiceEpr parameter specifies the Exchange Online Calendar Service UR
 - Office 365 operated by 21Vianet: partner.outlook.cn
 - Microsoft 365 GCC High or DoD: outlook.office365.us
 
+You use this parameter only when the AccessMethod parameter value is OrgWideFBToken.
+
 ```yaml
 Type: String
 Parameter Sets: (All)
@@ -245,10 +247,12 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online, Exchange Online Protection
 
-This parameter is available only in the cloud-based service and is only used when AccessMethod is OrgWideFBToken.
+This parameter is available only in the cloud-based service.
 
 The TargetTenantID parameter specifies the tenant ID of the external Microsoft 365 organization that you're trying to read free/busy information from.
 
+You use this parameter only when the AccessMethod parameter value is OrgWideFBToken.
+
 ```yaml
 Type: String
 Parameter Sets: (All)

From d924515a2a886611ee5841d7a2c9d692277dc463 Mon Sep 17 00:00:00 2001
From: Chris Davis <chris.davis@microsoft.com>
Date: Wed, 6 Aug 2025 08:38:04 -0700
Subject: [PATCH 092/145] Acrolinx 7

---
 .../ExchangePowerShell/Get-MailContact.md          |  4 ++--
 .../ExchangePowerShell/Get-MailDetailATPReport.md  |  8 +++++---
 .../Get-MailDetailDlpPolicyReport.md               |  4 ++--
 .../Get-MailDetailEncryptionReport.md              |  4 ++--
 .../Get-MailDetailTransportRuleReport.md           |  4 ++--
 .../ExchangePowerShell/Get-MailFilterListReport.md |  2 +-
 .../ExchangePowerShell/Get-MailFlowStatusReport.md |  2 +-
 .../ExchangePowerShell/Get-MailPublicFolder.md     |  4 ++--
 .../ExchangePowerShell/Get-MailTrafficATPReport.md |  2 +-
 .../Get-MailTrafficEncryptionReport.md             |  2 +-
 .../Get-MailTrafficPolicyReport.md                 |  2 +-
 .../Get-MailTrafficSummaryReport.md                |  2 +-
 .../exchange-ps/ExchangePowerShell/Get-MailUser.md |  4 ++--
 .../ExchangePowerShell/Get-MailboxSearch.md        |  4 ++--
 .../Get-MailboxSentItemsConfiguration.md           |  2 +-
 .../ExchangePowerShell/Get-MailboxServer.md        |  2 +-
 .../Get-MailboxSpellingConfiguration.md            |  4 ++--
 .../ExchangePowerShell/Get-MailboxStatistics.md    |  6 +++---
 .../Get-MailboxTransportService.md                 |  2 +-
 .../Get-MailboxUserConfiguration.md                |  4 ++--
 .../ExchangePowerShell/Get-MalwareFilterPolicy.md  |  4 ++--
 .../ExchangePowerShell/Get-MalwareFilterRule.md    |  4 ++--
 .../Get-MalwareFilteringServer.md                  |  2 +-
 .../Get-ManagedContentSettings.md                  |  2 +-
 .../ExchangePowerShell/Get-ManagedFolder.md        |  2 +-
 .../Get-ManagedFolderMailboxPolicy.md              |  2 +-
 .../ExchangePowerShell/Get-ManagementRole.md       |  4 ++--
 .../Get-ManagementRoleAssignment.md                |  4 ++--
 .../ExchangePowerShell/Get-ManagementRoleEntry.md  |  4 ++--
 .../ExchangePowerShell/Get-ManagementScope.md      |  4 ++--
 .../ExchangePowerShell/Get-MapiVirtualDirectory.md |  2 +-
 .../exchange-ps/ExchangePowerShell/Get-Message.md  |  8 ++++----
 .../ExchangePowerShell/Get-MessageCategory.md      |  4 ++--
 .../Get-MessageClassification.md                   |  4 ++--
 .../ExchangePowerShell/Get-MessageTrace.md         |  8 ++++----
 .../ExchangePowerShell/Get-MessageTraceDetail.md   | 10 +++++-----
 .../ExchangePowerShell/Get-MessageTraceDetailV2.md | 10 +++++-----
 .../ExchangePowerShell/Get-MessageTraceV2.md       |  6 +++---
 .../ExchangePowerShell/Get-MessageTrackingLog.md   |  6 +++---
 .../Get-MessageTrackingReport.md                   |  2 +-
 .../ExchangePowerShell/Get-MigrationBatch.md       |  6 +++---
 .../ExchangePowerShell/Get-MigrationConfig.md      |  4 ++--
 .../ExchangePowerShell/Get-MigrationEndpoint.md    |  4 ++--
 .../ExchangePowerShell/Get-MigrationStatistics.md  |  4 ++--
 .../ExchangePowerShell/Get-MigrationUser.md        |  4 ++--
 .../Get-MigrationUserStatistics.md                 |  4 ++--
 .../ExchangePowerShell/Get-MobileDevice.md         |  4 ++--
 .../Get-MobileDeviceMailboxPolicy.md               |  4 ++--
 .../Get-MobileDeviceStatistics.md                  |  4 ++--
 .../ExchangePowerShell/Get-MonitoringItemHelp.md   |  2 +-
 .../Get-MonitoringItemIdentity.md                  |  2 +-
 .../ExchangePowerShell/Get-MoveRequest.md          |  6 +++---
 .../Get-MoveRequestStatistics.md                   |  6 +++---
 .../ExchangePowerShell/Get-MxRecordReport.md       |  2 +-
 .../Get-NetworkConnectionInfo.md                   |  2 +-
 .../ExchangePowerShell/Get-Notification.md         |  4 ++--
 .../ExchangePowerShell/Get-OMEConfiguration.md     |  2 +-
 .../ExchangePowerShell/Get-OMEMessageStatus.md     |  6 +++---
 .../ExchangePowerShell/Get-OabVirtualDirectory.md  |  2 +-
 .../ExchangePowerShell/Get-OfflineAddressBook.md   |  4 ++--
 .../Get-OnPremisesOrganization.md                  |  6 +++---
 .../Get-OnlineMeetingConfiguration.md              |  2 +-
 .../ExchangePowerShell/Get-OrganizationConfig.md   |  4 ++--
 .../Get-OrganizationRelationship.md                |  6 +++---
 .../ExchangePowerShell/Get-OrganizationalUnit.md   |  4 ++--
 .../ExchangePowerShell/Get-OutboundConnector.md    |  6 +++---
 .../Get-OutboundConnectorReport.md                 |  2 +-
 .../ExchangePowerShell/Get-OutlookAnywhere.md      |  2 +-
 .../Get-OutlookProtectionRule.md                   |  4 ++--
 .../ExchangePowerShell/Get-OutlookProvider.md      |  2 +-
 .../ExchangePowerShell/Get-OwaMailboxPolicy.md     |  4 ++--
 .../ExchangePowerShell/Get-OwaVirtualDirectory.md  |  2 +-
 .../ExchangePowerShell/Get-PartnerApplication.md   |  4 ++--
 .../ExchangePowerShell/Get-PendingDelicenseUser.md |  2 +-
 .../Get-PendingFederatedDomain.md                  |  2 +-
 .../Get-PhishSimOverridePolicy.md                  |  2 +-
 .../exchange-ps/ExchangePowerShell/Get-Place.md    |  2 +-
 .../ExchangePowerShell/Get-PolicyTipConfig.md      |  4 ++--
 .../ExchangePowerShell/Get-PopSettings.md          |  2 +-
 .../Get-PowerShellVirtualDirectory.md              |  2 +-
 .../ExchangePowerShell/Get-PublicFolder.md         |  6 +++---
 .../Get-PublicFolderAdministrativePermission.md    |  2 +-
 .../Get-PublicFolderClientPermission.md            |  4 ++--
 .../ExchangePowerShell/Get-PublicFolderDatabase.md |  2 +-
 .../Get-PublicFolderItemStatistics.md              |  4 ++--
 .../Get-PublicFolderMailboxDiagnostics.md          |  4 ++--
 .../Get-PublicFolderMailboxMigrationRequest.md     |  4 ++--
 ...ublicFolderMailboxMigrationRequestStatistics.md |  4 ++--
 .../Get-PublicFolderMigrationRequest.md            |  4 ++--
 .../Get-PublicFolderMigrationRequestStatistics.md  |  2 +-
 .../Get-PublicFolderMoveRequest.md                 |  6 +++---
 .../Get-PublicFolderMoveRequestStatistics.md       |  4 ++--
 .../Get-PublicFolderStatistics.md                  |  4 ++--
 .../ExchangePowerShell/Get-QuarantineMessage.md    | 14 +++++++-------
 .../Get-QuarantineMessageHeader.md                 |  4 ++--
 95 files changed, 185 insertions(+), 183 deletions(-)

diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailContact.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailContact.md
index ae2917a68a..95a7d4a31c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailContact.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailContact.md
@@ -13,7 +13,7 @@ title: Get-MailContact
 # Get-MailContact
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-MailContact cmdlet to view existing mail contacts.
 
@@ -54,7 +54,7 @@ Get-MailContact [[-Identity] <MailContactIdParameter>]
 ## DESCRIPTION
 The Get-MailContact cmdlet retrieves all attributes of the specified contact. No parameters are required. If the cmdlet is run without a parameter, a complete list of contacts for the Exchange organization is returned.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailDetailATPReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailDetailATPReport.md
index 0cd35bc4ee..39cb412f8d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailDetailATPReport.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailDetailATPReport.md
@@ -65,7 +65,7 @@ For the reporting period you specify, the cmdlet returns the following informati
 
 This cmdlet is limited to 10,000 results. If you reach this limit, you can use the available parameters to filter the output.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -74,7 +74,9 @@ You need to be assigned permissions before you can run this cmdlet. Although thi
 Get-MailDetailATPReport -StartDate 7/22/2018 -EndDate 7/31/2018
 ```
 
-This example returns the actions for the last 10 days in July, 2018. (Note: Customers with Defender for Office 365 subscriptions will be able to get up to 30 days of data.)
+This example returns the actions for the last 10 days in July, 2018.
+
+Customers with Defender for Office 365 subscriptions can get up to 30 days of data.
 
 ## PARAMETERS
 
@@ -233,7 +235,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online, Exchange Online Protection
 
-The MessageId parameter filters the results by the Message-ID header field of the message. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which may include angle brackets) and enclose the value in quotation marks (for example, "<d9683b4c-127b-413a-ae2e-fa7dfb32c69d@DM3NAM06BG401.Eop-nam06.prod.protection.outlook.com>").
+The MessageId parameter filters the results by the Message-ID header field of the message. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which might include angle brackets) and enclose the value in quotation marks (for example, "<d9683b4c-127b-413a-ae2e-fa7dfb32c69d@DM3NAM06BG401.Eop-nam06.prod.protection.outlook.com>").
 
 ```yaml
 Type: MultiValuedProperty
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailDetailDlpPolicyReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailDetailDlpPolicyReport.md
index 2043cdee62..1318943b53 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailDetailDlpPolicyReport.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailDetailDlpPolicyReport.md
@@ -41,7 +41,7 @@ Get-MailDetailDlpPolicyReport [-Action <MultiValuedProperty>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -185,7 +185,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online
 
-The MessageId parameter filters the results by the Message-ID header field of the message. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which may include angle brackets) and enclose the value in quotation marks (for example, "<d9683b4c-127b-413a-ae2e-fa7dfb32c69d@DM3NAM06BG401.Eop-nam06.prod.protection.outlook.com>").
+The MessageId parameter filters the results by the Message-ID header field of the message. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which might include angle brackets) and enclose the value in quotation marks (for example, "<d9683b4c-127b-413a-ae2e-fa7dfb32c69d@DM3NAM06BG401.Eop-nam06.prod.protection.outlook.com>").
 
 ```yaml
 Type: MultiValuedProperty
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailDetailEncryptionReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailDetailEncryptionReport.md
index 3f2175e653..986013442c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailDetailEncryptionReport.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailDetailEncryptionReport.md
@@ -54,7 +54,7 @@ If you append the command with ` | Format-List`, the following additional inform
 - Message Size
 - Subject
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -193,7 +193,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
 
-The MessageId parameter filters the results by the Message-ID header field of the message. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which may include angle brackets) and enclose the value in quotation marks (for example, "<d9683b4c-127b-413a-ae2e-fa7dfb32c69d@DM3NAM06BG401.Eop-nam06.prod.protection.outlook.com>").
+The MessageId parameter filters the results by the Message-ID header field of the message. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which might include angle brackets) and enclose the value in quotation marks (for example, "<d9683b4c-127b-413a-ae2e-fa7dfb32c69d@DM3NAM06BG401.Eop-nam06.prod.protection.outlook.com>").
 
 You can specify multiple values separated by commas.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailDetailTransportRuleReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailDetailTransportRuleReport.md
index 7ca077624a..21c4bddb6f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailDetailTransportRuleReport.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailDetailTransportRuleReport.md
@@ -40,7 +40,7 @@ Get-MailDetailTransportRuleReport [-Action <MultiValuedProperty>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -165,7 +165,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online, Exchange Online Protection
 
-The MessageId parameter filters the results by the Message-ID header field of the message. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which may include angle brackets) and enclose the value in quotation marks (for example, "<d9683b4c-127b-413a-ae2e-fa7dfb32c69d@DM3NAM06BG401.Eop-nam06.prod.protection.outlook.com>").
+The MessageId parameter filters the results by the Message-ID header field of the message. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which might include angle brackets) and enclose the value in quotation marks (for example, "<d9683b4c-127b-413a-ae2e-fa7dfb32c69d@DM3NAM06BG401.Eop-nam06.prod.protection.outlook.com>").
 
 ```yaml
 Type: MultiValuedProperty
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailFilterListReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailFilterListReport.md
index fca22fa5d4..3038284e6e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailFilterListReport.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailFilterListReport.md
@@ -31,7 +31,7 @@ Get-MailFilterListReport
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailFlowStatusReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailFlowStatusReport.md
index c9ca311930..fc641edb9e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailFlowStatusReport.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailFlowStatusReport.md
@@ -42,7 +42,7 @@ This cmdlet returns the following information:
 - Event Type
 - Count
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailPublicFolder.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailPublicFolder.md
index 0ff82748fe..c9c71c1564 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailPublicFolder.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailPublicFolder.md
@@ -13,7 +13,7 @@ title: Get-MailPublicFolder
 # Get-MailPublicFolder
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-MailPublicFolder cmdlet to retrieve mail-related information about mail-enabled public folders. If you want information about the basic (not mail-related) settings of mail-enabled public folders, use the Get-PublicFolder cmdlet instead.
 
@@ -50,7 +50,7 @@ Get-MailPublicFolder [[-Identity] <MailPublicFolderIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailTrafficATPReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailTrafficATPReport.md
index 318fbbbe60..8c4dd7aca1 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailTrafficATPReport.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailTrafficATPReport.md
@@ -53,7 +53,7 @@ For the reporting period you specify, the cmdlet returns the following informati
 - Verdict Source
 - Message Count
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailTrafficEncryptionReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailTrafficEncryptionReport.md
index e864108d17..dc8465437c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailTrafficEncryptionReport.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailTrafficEncryptionReport.md
@@ -47,7 +47,7 @@ For the reporting period you specify, the cmdlet returns the following informati
 - Message Count
 - Recipient Count
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailTrafficPolicyReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailTrafficPolicyReport.md
index 78abc412a0..a85f525837 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailTrafficPolicyReport.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailTrafficPolicyReport.md
@@ -49,7 +49,7 @@ For the reporting period you specify, the cmdlet returns the following informati
 - Direction
 - Message Count
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailTrafficSummaryReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailTrafficSummaryReport.md
index 05ad814da1..652e149273 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailTrafficSummaryReport.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailTrafficSummaryReport.md
@@ -41,7 +41,7 @@ This cmdlet has C1, C2 and C3 as header names and the meaning of them depends on
 - TopSpamRecipient, TopMailSender, TopMailRecipient and TopMalwareRecipient: C1 is the recipient or sender and C2 the quantity of email messages.
 - TopMalware: C1 is the malware name and C2 the quantity of appearances.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailUser.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailUser.md
index 7e8cd7aefb..8198063763 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailUser.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailUser.md
@@ -13,7 +13,7 @@ title: Get-MailUser
 # Get-MailUser
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-MailUser cmdlet to view mail users and also guest users for Microsoft 365 Groups in cloud environments.
 
@@ -79,7 +79,7 @@ Get-MailUser [-HVEAccount]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxSearch.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxSearch.md
index 607711b6f8..1dd6099661 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxSearch.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxSearch.md
@@ -13,7 +13,7 @@ title: Get-MailboxSearch
 # Get-MailboxSearch
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-MailboxSearch cmdlet to view mailbox searches that are in progress, complete or stopped.
 
@@ -52,7 +52,7 @@ Get-MailboxSearch -InPlaceHoldIdentity <String>
 ## DESCRIPTION
 In on-premises Exchange, a mailbox search is used to perform an In-Place eDiscovery or to place users on an In-Place Hold. Use the Get-MailboxSearch cmdlet to retrieve details of either type of mailbox search.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxSentItemsConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxSentItemsConfiguration.md
index 847a41ef34..6ed02a5bdc 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxSentItemsConfiguration.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxSentItemsConfiguration.md
@@ -30,7 +30,7 @@ Get-MailboxSentItemsConfiguration [-DomainController <Fqdn>]
 ## DESCRIPTION
 By default, when you use Send As or Send On Behalf Of to send a message from another mailbox, the message is saved in your Sent Items folder (not in the Sent Items folder of the source mailbox). In Microsoft Exchange Server 2010 Service Pack 3 (SP3), you can save copies messages in the Sent Items folder of the sender and the source mailbox. For example, consider a shared mailbox that receives customer feedback and is monitored by multiple users. When someone responds to a message in the shared mailbox, you can save the message in the Sent Items folder of the shared mailbox and the sender's mailbox.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxServer.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxServer.md
index 6be71ce89d..4c6925717f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxServer.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxServer.md
@@ -31,7 +31,7 @@ Get-MailboxServer [[-Identity] <MailboxServerIdParameter>]
 ## DESCRIPTION
 The ExchangeVersion attribute returned is the minimum version of Microsoft Exchange that you can use to manage the returned object. This attribute isn't the same as the version of Microsoft Exchange that's displayed in the Exchange admin center when you select Server Configuration.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxSpellingConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxSpellingConfiguration.md
index d132b4950f..fc0ca8f8a2 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxSpellingConfiguration.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxSpellingConfiguration.md
@@ -13,7 +13,7 @@ title: Get-MailboxSpellingConfiguration
 # Get-MailboxSpellingConfiguration
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-MailboxSpellingConfiguration cmdlet to retrieve the Outlook on the web spelling checker settings of a specified user. For example, users can set their dictionary language and configure the spelling checker to ignore mixed digits and words in all uppercase.
 
@@ -35,7 +35,7 @@ The Get-MailboxSpellingConfiguration cmdlet is primarily used to populate the sp
 - DictionaryLanguage: This setting specifies the dictionary language used when the spelling checker checks the spelling in messages.
 - IgnoreMixedDigits: This setting specifies whether the spelling checker ignores words that contain numbers.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxStatistics.md
index 53dfbc6753..fa20e834d4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxStatistics.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxStatistics.md
@@ -13,7 +13,7 @@ title: Get-MailboxStatistics
 # Get-MailboxStatistics
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-MailboxStatistics cmdlet to return information about a mailbox, such as the size of the mailbox, the number of messages it contains, and the last time it was accessed. In addition, you can get the move history or a move report of a completed move request.
 
@@ -75,7 +75,7 @@ You can only see move reports and move history for completed move requests.
 
 **Note**: We're deprecating the LastUserActionTime property in Exchange Online PowerShell. Don't use the value of that property as the last active time for a mailbox.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -135,7 +135,7 @@ $temp=Get-MailboxStatistics -Identity AylaKol -IncludeMoveHistory
 $temp.MoveHistory[0]
 ```
 
-This example returns the detailed move history for the completed move request for Ayla Kol's mailbox. This example uses a temporary variable to store the mailbox statistics object. If the mailbox has been moved multiple times, there are multiple move reports. The last move report is always MoveReport[0].
+This example returns the detailed move history for the completed move request for Ayla Kol's mailbox. This example uses a temporary variable to store the mailbox statistics object. If the mailbox is moved multiple times, there are multiple move reports. The last move report is always MoveReport[0].
 
 ### Example 9
 ```powershell
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxTransportService.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxTransportService.md
index 25cb4369a6..d93f8c7443 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxTransportService.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxTransportService.md
@@ -30,7 +30,7 @@ Get-MailboxTransportService [[-Identity] <MailboxTransportServerIdParameter>]
 ## DESCRIPTION
 The Mailbox Transport service runs on all Mailbox servers and is responsible for delivering messages to and accepting messages from local mailbox databases using remote procedure calls (RPC). The Mailbox Transport service also uses SMTP to send messages to and from the Transport service that runs on all Mailbox servers for routing their ultimate destinations.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxUserConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxUserConfiguration.md
index 961975f2db..c5a73d9071 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxUserConfiguration.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxUserConfiguration.md
@@ -13,7 +13,7 @@ title: Get-MailboxUserConfiguration
 # Get-MailboxUserConfiguration
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-MailboxUserConfiguration cmdlet to view user configuration items in mailboxes.
 
@@ -30,7 +30,7 @@ Get-MailboxUserConfiguration [-Identity] <MailboxUserConfigurationIdParameter> -
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MalwareFilterPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-MalwareFilterPolicy.md
index 5d133ef2fb..70fc40e4e3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MalwareFilterPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MalwareFilterPolicy.md
@@ -13,7 +13,7 @@ title: Get-MalwareFilterPolicy
 # Get-MalwareFilterPolicy
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-MalwareFilterPolicy cmdlet to view the malware filter policies in your organization.
 
@@ -30,7 +30,7 @@ Get-MalwareFilterPolicy [[-Identity] <MalwareFilterPolicyIdParameter>]
 ## DESCRIPTION
 Malware filter policies contain the malware settings and a list of domains to which those settings apply. A domain can't belong to more than one malware filter policy.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MalwareFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-MalwareFilterRule.md
index 9dece05188..851fe8bee1 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MalwareFilterRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MalwareFilterRule.md
@@ -13,7 +13,7 @@ title: Get-MalwareFilterRule
 # Get-MalwareFilterRule
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Enable-MalwareFilterRule cmdlet to view malware filter rules in your organization.
 
@@ -29,7 +29,7 @@ Get-MalwareFilterRule [[-Identity] <RuleIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MalwareFilteringServer.md b/exchange/exchange-ps/ExchangePowerShell/Get-MalwareFilteringServer.md
index 7cdc96ccc4..a5aa694930 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MalwareFilteringServer.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MalwareFilteringServer.md
@@ -28,7 +28,7 @@ Get-MalwareFilteringServer [[-Identity] <MalwareFilteringServerIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ManagedContentSettings.md b/exchange/exchange-ps/ExchangePowerShell/Get-ManagedContentSettings.md
index 38de7eef3b..3363cb27c8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ManagedContentSettings.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ManagedContentSettings.md
@@ -40,7 +40,7 @@ The Get-ManagedContentSettings cmdlet retrieves from one to all of the managed c
 
 If only the Identity parameter is present, the folder content settings and all associated attributes are returned. If the Identity parameter isn't present, the command returns all content settings. If the FolderName parameter is present, the command returns all content settings contained in the specified managed folder and all the attributes of each setting.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ManagedFolder.md b/exchange/exchange-ps/ExchangePowerShell/Get-ManagedFolder.md
index a3984883b9..603b909fa6 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ManagedFolder.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ManagedFolder.md
@@ -44,7 +44,7 @@ The Get-ManagedFolder cmdlet retrieves the specified managed folder attributes:
 
 The Get-ManagedFolder cmdlet accepts a ManagedFolder object or an identity string as pipelined input.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ManagedFolderMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-ManagedFolderMailboxPolicy.md
index 012ba3077b..7c810e181a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ManagedFolderMailboxPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ManagedFolderMailboxPolicy.md
@@ -30,7 +30,7 @@ Get-ManagedFolderMailboxPolicy [[-Identity] <MailboxPolicyIdParameter>]
 ## DESCRIPTION
 A managed folder mailbox policy is a logical grouping of one or more managed folders. Policies are applied to mailboxes. The Get-ManagedFolderMailboxPolicy cmdlet lists one or more managed folder mailbox policies created in the Microsoft Exchange Server 2010 organization. All policies can be listed.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ManagementRole.md b/exchange/exchange-ps/ExchangePowerShell/Get-ManagementRole.md
index fc7a39e6d1..67b161bb48 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ManagementRole.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ManagementRole.md
@@ -13,7 +13,7 @@ title: Get-ManagementRole
 # Get-ManagementRole
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-ManagementRole cmdlet to view management roles that have been created in your organization.
 
@@ -64,7 +64,7 @@ You can view management roles in several ways, from listing all the roles in you
 
 For more information about management roles, see [Understanding management roles](https://learn.microsoft.com/exchange/understanding-management-roles-exchange-2013-help).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ManagementRoleAssignment.md b/exchange/exchange-ps/ExchangePowerShell/Get-ManagementRoleAssignment.md
index 31e8e41432..e3ee03a9c7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ManagementRoleAssignment.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ManagementRoleAssignment.md
@@ -13,7 +13,7 @@ title: Get-ManagementRoleAssignment
 # Get-ManagementRoleAssignment
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-ManagementRoleAssignment cmdlet to retrieve management role assignments.
 
@@ -76,7 +76,7 @@ You can retrieve role assignments in a variety of ways including by assignment t
 
 For more information about management role assignments, see [Understanding management role assignments](https://learn.microsoft.com/exchange/understanding-management-role-assignments-exchange-2013-help).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ManagementRoleEntry.md b/exchange/exchange-ps/ExchangePowerShell/Get-ManagementRoleEntry.md
index 7c88254dd8..6069d86005 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ManagementRoleEntry.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ManagementRoleEntry.md
@@ -13,7 +13,7 @@ title: Get-ManagementRoleEntry
 # Get-ManagementRoleEntry
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-ManagementRoleEntry cmdlet to retrieve management role entries that have been configured on management roles.
 
@@ -36,7 +36,7 @@ The Get-ManagementRoleEntry cmdlet retrieves role entries that have been configu
 
 For more information about management role entries, see [Understanding management roles](https://learn.microsoft.com/exchange/understanding-management-roles-exchange-2013-help).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ManagementScope.md b/exchange/exchange-ps/ExchangePowerShell/Get-ManagementScope.md
index cc67cda634..e3d35c1cde 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ManagementScope.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ManagementScope.md
@@ -13,7 +13,7 @@ title: Get-ManagementScope
 # Get-ManagementScope
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-ManagementScope cmdlet to return a list of management scopes.
 
@@ -34,7 +34,7 @@ You can retrieve one scope or many, retrieve only scopes that aren't associated
 
 For more information about regular and exclusive scopes, see [Understanding management role scopes](https://learn.microsoft.com/exchange/understanding-management-role-scopes-exchange-2013-help).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MapiVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Get-MapiVirtualDirectory.md
index 72586d4075..8d63f79498 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MapiVirtualDirectory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MapiVirtualDirectory.md
@@ -40,7 +40,7 @@ Get-MapiVirtualDirectory [[-Identity] <VirtualDirectoryIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-Message.md b/exchange/exchange-ps/ExchangePowerShell/Get-Message.md
index f9c313b9b5..2aa1848340 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-Message.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-Message.md
@@ -70,7 +70,7 @@ Get-Message [-Queue <QueueIdentity>]
 ## DESCRIPTION
 You can display messages by including the server name as part of the Identity parameter or the Queue parameter or by including the Server parameter with a filter query. The Identity parameter, Queue parameter, and Filter parameter settings are mutually exclusive.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -195,7 +195,7 @@ Accept wildcard characters: False
 
 The IncludeComponentLatencyInfo switch specifies whether the information about component latency is included in the message properties. You don't need to specify a value with this switch.
 
-If you include this switch, the message objects returned will include latency measurements for each Transport component that has contributed to the local server latency for each queued message.
+If you include this switch, the message objects returned include latency measurements for each Transport component that has contributed to the local server latency for each queued message.
 
 ```yaml
 Type: SwitchParameter
@@ -220,9 +220,9 @@ If you don't include the IncludeRecipientInfo switch, the Recipients field is bl
 Storing the results of a `Get-Message -IncludeRecipientInfo` command in a variable allows you to display additional properties for the message recipients. The following list describes the available recipient properties:
 
 - Address: The email address of the recipient.
-- Type: The recipient type, which may be External, Mailbox or Distribution Group. Distribution Group is used when the destination is an expansion server.
+- Type: The recipient type, which might be External, Mailbox or Distribution Group. Distribution Group is used when the destination is an expansion server.
 - FinalDestination: The distinguished name (DN) of the object used to route the message.
-- Status: The recipient status may be Complete, Ready or Retry.
+- Status: The recipient status might be Complete, Ready or Retry.
 - LastError: The SMTP response after the last delivery attempt or a localized error message if the message is placed in the unreachable queue.
 
 For example, to store the recipient information of a message in the contoso.com remote delivery queue that has the MessageIdentity value of 1234 to a variable named $x, use the following command: `$x=Get-Message -Identity "contoso.com\\1234" -IncludeRecipientInfo`.
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MessageCategory.md b/exchange/exchange-ps/ExchangePowerShell/Get-MessageCategory.md
index b459f539f4..3eaf7fb54c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MessageCategory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MessageCategory.md
@@ -13,7 +13,7 @@ title: Get-MessageCategory
 # Get-MessageCategory
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-MessageCategory cmdlet to retrieve a message category from the specified mailbox.
 
@@ -31,7 +31,7 @@ Get-MessageCategory [[-Identity] <MessageCategoryIdParameter>]
 ## DESCRIPTION
 The Get-MessageCategory cmdlet is used by the web management interface in Microsoft Exchange to populate fields that display message category information.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MessageClassification.md b/exchange/exchange-ps/ExchangePowerShell/Get-MessageClassification.md
index c2c3594d87..4dc5651fcc 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MessageClassification.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MessageClassification.md
@@ -13,7 +13,7 @@ title: Get-MessageClassification
 # Get-MessageClassification
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-MessageClassification cmdlet to view existing message classifications in your organization.
 
@@ -29,7 +29,7 @@ Get-MessageClassification [[-Identity] <MessageClassificationIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MessageTrace.md b/exchange/exchange-ps/ExchangePowerShell/Get-MessageTrace.md
index a364e80569..a470a56e43 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MessageTrace.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MessageTrace.md
@@ -44,15 +44,15 @@ Get-MessageTrace
 ## DESCRIPTION
 You can use this cmdlet to search message data for the last 10 days. If you run this cmdlet without any parameters, only data from the last 48 hours is returned.
 
-If you enter a start date that is older than 10 days, you will receive an error and the command will return no results.
+If you enter a start date that is older than 10 days, you get an error and the command returns no results.
 
 To search for message data that is greater than 10 days old, use the Start-HistoricalSearch and Get-HistoricalSearch cmdlets.
 
-By default, this cmdlet returns a maximum of 1000 results, and will timeout on very large queries. If your query returns too many results, consider splitting it up using smaller StartDate and EndDate intervals.
+By default, this cmdlet returns a maximum of 1000 results, and times out on very large queries. If your query returns too many results, consider splitting it up using smaller StartDate and EndDate intervals.
 
 The time stamps on the output are in UTC time format. That might be different from the time format that you used for the -StartDate and the -EndDate parameters.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -107,7 +107,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online, Exchange Online Protection
 
-The MessageId parameter filters the results by the Message-ID header field of the message. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which may include angle brackets) and enclose the value in quotation marks (for example, "<d9683b4c-127b-413a-ae2e-fa7dfb32c69d@DM3NAM06BG401.Eop-nam06.prod.protection.outlook.com>").
+The MessageId parameter filters the results by the Message-ID header field of the message. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which might include angle brackets) and enclose the value in quotation marks (for example, "<d9683b4c-127b-413a-ae2e-fa7dfb32c69d@DM3NAM06BG401.Eop-nam06.prod.protection.outlook.com>").
 
 ```yaml
 Type: MultiValuedProperty
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MessageTraceDetail.md b/exchange/exchange-ps/ExchangePowerShell/Get-MessageTraceDetail.md
index 86ce5348b6..fd7c45e868 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MessageTraceDetail.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MessageTraceDetail.md
@@ -18,7 +18,7 @@ This cmdlet is available only in the cloud-based service.
 > [!NOTE]
 > This cmdlet is replaced by the [Get-MessageTraceDetailV2](https://learn.microsoft.com/powershell/module/exchangepowershell/get-messagetracedetailv2) cmdlet and will eventually be deprecated.
 
-Use the Get-MessageTraceDetail cmdlet to view the message trace event details for a specific message. Note that these detailed results are returned less quickly than the Get-MessageTrace results.
+Use the Get-MessageTraceDetail cmdlet to view the message trace event details for a specific message. These detailed results are returned less quickly than the Get-MessageTrace results.
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
@@ -39,11 +39,11 @@ Get-MessageTraceDetail -MessageTraceId <Guid> -RecipientAddress <String>
 ```
 
 ## DESCRIPTION
-You can use this cmdlet to search message data for the last 10 days. If you enter a time period that's older than 10 days, you will receive an error and the command will return no results.
+You can use this cmdlet to search message data for the last 10 days. If you enter a time period that's older than 10 days, you get an error and the command returns no results.
 
 To search for message data that is greater than 10 days old, use the Start-HistoricalSearch and Get-HistoricalSearch cmdlets.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -161,7 +161,7 @@ The Event parameter filters the report by the message event. The following are e
 - DELIVER: The message was delivered to a mailbox.
 - EXPAND: The message was sent to a distribution group that was expanded.
 - TRANSFER: Recipients were moved to a bifurcated message because of content conversion, message recipient limits, or agents.
-- DEFER: The message delivery was postponed and may be re-attempted later.
+- DEFER: The message delivery was postponed and might be re-attempted later.
 
 You can specify multiple values separated by commas.
 
@@ -181,7 +181,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online, Exchange Online Protection
 
-The MessageId parameter filters the results by the Message-ID header field of the message. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which may include angle brackets) and enclose the value in quotation marks (for example, "<d9683b4c-127b-413a-ae2e-fa7dfb32c69d@DM3NAM06BG401.Eop-nam06.prod.protection.outlook.com>").
+The MessageId parameter filters the results by the Message-ID header field of the message. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which might include angle brackets) and enclose the value in quotation marks (for example, "<d9683b4c-127b-413a-ae2e-fa7dfb32c69d@DM3NAM06BG401.Eop-nam06.prod.protection.outlook.com>").
 
 ```yaml
 Type: String
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MessageTraceDetailV2.md b/exchange/exchange-ps/ExchangePowerShell/Get-MessageTraceDetailV2.md
index 0c9ae55a19..2a3f46266f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MessageTraceDetailV2.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MessageTraceDetailV2.md
@@ -28,11 +28,11 @@ Get-MessageTraceDetailV2 [-MessageTraceId] <Guid> [-RecipientAddress] <String>
 ```
 
 ## DESCRIPTION
-You can use this cmdlet to search message data for the last 90 days. You can only query 10 days worth of data per query. If you enter a timeframe that's older than 90 days, you receive an error and the command will return no results.
+You can use this cmdlet to search message data for the last 90 days. You can only query 10 days worth of data per query. If you enter a timeframe that's older than 90 days, you receive an error and the command returns no results.
 
-Throttling limit: A maximum of 100 query requests will be accepted within 5 minutes running window. Throttling is automatically not applied if the request rate is lower than 100 requests in the past 5 minutes
+Throttling limit: A maximum of 100 query requests are accepted within a 5 minute running window. Throttling is automatically not applied if the request rate is lower than 100 requests in the last 5 minutes
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -142,7 +142,7 @@ The Event parameter filters the report by the message event. The following are e
 - DELIVER: The message was delivered to a mailbox.
 - EXPAND: The message was sent to a distribution group that was expanded.
 - TRANSFER: Recipients were moved to a bifurcated message because of content conversion, message recipient limits, or agents.
-- DEFER: The message delivery was postponed and may be re-attempted later.
+- DEFER: The message delivery was postponed and might be re-attempted later.
 
 You can specify multiple values separated by commas.
 
@@ -162,7 +162,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online
 
-The MessageId parameter filters the results by the Message-ID header field of the message. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which may include angle brackets) and enclose the value in quotation marks (for example, "<d9683b4c-127b-413a-ae2e-fa7dfb32c69d@DM3NAM06BG401.Eop-nam06.prod.protection.outlook.com>").
+The MessageId parameter filters the results by the Message-ID header field of the message. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which might include angle brackets) and enclose the value in quotation marks (for example, "<d9683b4c-127b-413a-ae2e-fa7dfb32c69d@DM3NAM06BG401.Eop-nam06.prod.protection.outlook.com>").
 
 ```yaml
 Type: String
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MessageTraceV2.md b/exchange/exchange-ps/ExchangePowerShell/Get-MessageTraceV2.md
index 066f328ae0..0e274fc967 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MessageTraceV2.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MessageTraceV2.md
@@ -46,7 +46,7 @@ By default, this cmdlet returns up to 1000 results, with a maximum of 5000 resul
 
 The time stamps on the output are in UTC time format. That might be different from the time format that you used for the -StartDate and the -EndDate parameters.
 
-Throttling limit: A maximum of 100 query requests will be accepted within 5 minutes running window. Throttling is automatically not applied if the request rate is lower than 100 requests in the past 5 minutes
+Throttling limit: A maximum of 100 query requests are accepted within a 5 minute running window. Throttling is automatically not applied if the request rate is lower than 100 requests in the last 5 minutes
 
 Pagination isn't supported in this cmdlet. To query subsequent data, use the StartingRecipientAddress and EndDate parameters with the values from the **Recipient address** and **Received Time** properties respectively of the previous result in the next query.
 
@@ -56,7 +56,7 @@ Best Practices:
 - Be as precise as possible. Narrow the gap between StartDate and EndDate and use additional parameters (for example, SenderAddress) where possible.
 - Use MessageTraceId where possible (required for messages sent to more than 1000 recipients).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -111,7 +111,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online
 
-The MessageId parameter filters the results by the Message-ID header field of the message. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which may include angle brackets) and enclose the value in quotation marks (for example, "<d9683b4c-127b-413a-ae2e-fa7dfb32c69d@DM3NAM06BG401.Eop-nam06.prod.protection.outlook.com>").
+The MessageId parameter filters the results by the Message-ID header field of the message. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which might include angle brackets) and enclose the value in quotation marks (for example, "<d9683b4c-127b-413a-ae2e-fa7dfb32c69d@DM3NAM06BG401.Eop-nam06.prod.protection.outlook.com>").
 
 ```yaml
 Type: MultiValuedProperty
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MessageTrackingLog.md b/exchange/exchange-ps/ExchangePowerShell/Get-MessageTrackingLog.md
index b31a70814c..d2f4eae656 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MessageTrackingLog.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MessageTrackingLog.md
@@ -54,7 +54,7 @@ For more information about the message tracking log files, see [Message tracking
 
 You can write the results to a file by piping the output to ConvertTo-Html or ConvertTo-Csv and adding ` > <filename>` to the command. For example: `Get-MessageTrackingLog -Start "03/13/2020 09:00:00" -End "03/13/2020 09:10:00" | ConvertTo-Html > "C:\My Documents\message track.html"`.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -156,7 +156,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-The MessageId parameter filters the message tracking log entries by the value of the MessageId field. The value of MessageId corresponds to the value of the Message-Id: header field in the message. If the Message-ID header field is blank or doesn't exist, an arbitrary value is assigned. Be sure to include the full MessageId string (which may include angle brackets) and enclose the value in quotation marks (for example, "<d9683b4c-127b-413a-ae2e-fa7dfb32c69d@contoso.com>").
+The MessageId parameter filters the message tracking log entries by the value of the MessageId field. The value of MessageId corresponds to the value of the Message-Id: header field in the message. If the Message-ID header field is blank or doesn't exist, an arbitrary value is assigned. Be sure to include the full MessageId string (which might include angle brackets) and enclose the value in quotation marks (for example, "<d9683b4c-127b-413a-ae2e-fa7dfb32c69d@contoso.com>").
 
 ```yaml
 Type: String
@@ -309,7 +309,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2016, Exchange Server 2019
 
-The NetworkMessageId parameter filters the message tracking log entries by the value of the NetworkMessageId field. This field contains a unique message ID value that persists across copies of the message that may be created due to bifurcation or distribution group expansion. An example value is 1341ac7b13fb42ab4d4408cf7f55890f.
+The NetworkMessageId parameter filters the message tracking log entries by the value of the NetworkMessageId field. This field contains a unique message ID value that persists across copies of the message that might be created due to bifurcation or distribution group expansion. An example value is 1341ac7b13fb42ab4d4408cf7f55890f.
 
 ```yaml
 Type: String
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MessageTrackingReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-MessageTrackingReport.md
index 6ab8dab4b6..67532cc6d9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MessageTrackingReport.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MessageTrackingReport.md
@@ -41,7 +41,7 @@ Get-MessageTrackingReport [-Identity] <MessageTrackingReportId>
 ## DESCRIPTION
 This cmdlet requires the ID for the message tracking report that you want to view. Therefore, first you need to use the Search-MessageTrackingReport cmdlet to find the message tracking report ID for a specific message, and then pass the results to this cmdlet. For more information, see [Search-MessageTrackingReport](https://learn.microsoft.com/powershell/module/exchangepowershell/search-messagetrackingreport).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MigrationBatch.md b/exchange/exchange-ps/ExchangePowerShell/Get-MigrationBatch.md
index 0739a81f91..fb5ffbccec 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MigrationBatch.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MigrationBatch.md
@@ -13,7 +13,7 @@ title: Get-MigrationBatch
 # Get-MigrationBatch
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-MigrationBatch cmdlet to retrieve status information about the current migration batch.
 
@@ -78,9 +78,9 @@ The Get-MigrationBatch cmdlet displays status information about the current migr
 - Migration errors
 - Date and time when the migration was started and completed.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
-**Note**: In the cloud-based service, if you don't use the TimeZone parameter in the New-MigrationBatch command, the default time zone for the migration batch is UTC. The CompleteAfter and CompleteAfterUTC properties will contain the same value (as will the StartAfter and StartAfterUTC properties). When you create the migration batch in the Exchange admin center (EAC), the time zone that's used is based on your regional configuration.
+**Note**: In the cloud-based service, if you don't use the TimeZone parameter in the New-MigrationBatch command, the default time zone for the migration batch is UTC. The CompleteAfter and CompleteAfterUTC properties contain the same value (and also the StartAfter and StartAfterUTC properties). When you create the migration batch in the Exchange admin center (EAC), the time zone that's used is based on your regional configuration.
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MigrationConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-MigrationConfig.md
index 6129685733..a256dc66ad 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MigrationConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MigrationConfig.md
@@ -13,7 +13,7 @@ title: Get-MigrationConfig
 # Get-MigrationConfig
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-MigrationConfig cmdlet to retrieve migration configuration settings on Exchange servers.
 
@@ -42,7 +42,7 @@ Get-MigrationConfig [-AllPartitions]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MigrationEndpoint.md b/exchange/exchange-ps/ExchangePowerShell/Get-MigrationEndpoint.md
index 44e621ed39..3ea33df985 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MigrationEndpoint.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MigrationEndpoint.md
@@ -13,7 +13,7 @@ title: Get-MigrationEndpoint
 # Get-MigrationEndpoint
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-MigrationEndpoint cmdlet to retrieve migration endpoint settings for source or destination servers for cutover or staged Exchange migrations, IMAP migrations, and remote moves.
 
@@ -67,7 +67,7 @@ For more information about the different move and migration scenarios, see:
 - [Mailbox moves in Exchange Server](https://learn.microsoft.com/Exchange/recipients/mailbox-moves)
 - [Manage on-premises mailbox moves in Exchange Server](https://learn.microsoft.com/Exchange/architecture/mailbox-servers/manage-mailbox-moves)
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MigrationStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-MigrationStatistics.md
index a039591098..05587e4c0a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MigrationStatistics.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MigrationStatistics.md
@@ -13,7 +13,7 @@ title: Get-MigrationStatistics
 # Get-MigrationStatistics
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-MigrationStatistics cmdlet to view detailed information about migration requests.
 
@@ -31,7 +31,7 @@ Get-MigrationStatistics [-Diagnostic]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MigrationUser.md b/exchange/exchange-ps/ExchangePowerShell/Get-MigrationUser.md
index 3539caf558..4f85b2de43 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MigrationUser.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MigrationUser.md
@@ -13,7 +13,7 @@ title: Get-MigrationUser
 # Get-MigrationUser
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-MigrationUser cmdlet to view information about move and migration users.
 
@@ -62,7 +62,7 @@ Get-MigrationUser -EmailAddress <SmtpAddress>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MigrationUserStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-MigrationUserStatistics.md
index 98b51272c1..cc7cf9ad2f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MigrationUserStatistics.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MigrationUserStatistics.md
@@ -13,7 +13,7 @@ title: Get-MigrationUserStatistics
 # Get-MigrationUserStatistics
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-MigrationUserStatistics cmdlet to view detailed information about the migration requested for a specific user.
 
@@ -37,7 +37,7 @@ Get-MigrationUserStatistics [-Identity] <MigrationUserIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MobileDevice.md b/exchange/exchange-ps/ExchangePowerShell/Get-MobileDevice.md
index f0dcc63610..d54fc9963c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MobileDevice.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MobileDevice.md
@@ -13,7 +13,7 @@ title: Get-MobileDevice
 # Get-MobileDevice
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-MobileDevice cmdlet to get the list of devices in your organization that have active partnerships.
 
@@ -56,7 +56,7 @@ Get-MobileDevice [[-Identity] <MobileDeviceIdParameter>]
 ## DESCRIPTION
 The Get-MobileDevice cmdlet returns identification, configuration, and status information for each mobile device.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MobileDeviceMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-MobileDeviceMailboxPolicy.md
index 61bdb004a8..ce8b3ca55f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MobileDeviceMailboxPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MobileDeviceMailboxPolicy.md
@@ -13,7 +13,7 @@ title: Get-MobileDeviceMailboxPolicy
 # Get-MobileDeviceMailboxPolicy
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-MobileDeviceMailboxPolicy cmdlet to retrieve the Mobile Device mailbox policy settings for a specific Mobile Device mailbox policy.
 
@@ -30,7 +30,7 @@ Get-MobileDeviceMailboxPolicy [[-Identity] <MailboxPolicyIdParameter>]
 ## DESCRIPTION
 A Mobile Device mailbox policy is a group of settings that specifies how mobile devices connect Exchange. Exchange supports multiple mobile device mailbox policies. The Get-MobileDeviceMailboxPolicy cmdlet displays all the policy settings for the specified policy. These settings include password settings, file access settings and attachment settings.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MobileDeviceStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-MobileDeviceStatistics.md
index 9e800bcd46..ae8aeb20f0 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MobileDeviceStatistics.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MobileDeviceStatistics.md
@@ -13,7 +13,7 @@ title: Get-MobileDeviceStatistics
 # Get-MobileDeviceStatistics
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-MobileDeviceStatistics cmdlet to retrieve the list of mobile devices configured to synchronize with a specified user's mailbox and return a list of statistics about the mobile devices.
 
@@ -56,7 +56,7 @@ Get-MobileDeviceStatistics -Mailbox <MailboxIdParameter>
 ## DESCRIPTION
 The Get-MobileDeviceStatistics cmdlet returns a list of statistics about each mobile device. Additionally, it allows you to retrieve logs and send those logs to a recipient for troubleshooting purposes.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MonitoringItemHelp.md b/exchange/exchange-ps/ExchangePowerShell/Get-MonitoringItemHelp.md
index d7d517597e..738fa466ce 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MonitoringItemHelp.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MonitoringItemHelp.md
@@ -27,7 +27,7 @@ Get-MonitoringItemHelp [-Identity] <String> -Server <ServerIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MonitoringItemIdentity.md b/exchange/exchange-ps/ExchangePowerShell/Get-MonitoringItemIdentity.md
index ca5cfa71ed..3ac2e98fc2 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MonitoringItemIdentity.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MonitoringItemIdentity.md
@@ -27,7 +27,7 @@ Get-MonitoringItemIdentity [-Identity] <String> -Server <ServerIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MoveRequest.md b/exchange/exchange-ps/ExchangePowerShell/Get-MoveRequest.md
index b38430ed75..34a6e39394 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MoveRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MoveRequest.md
@@ -13,7 +13,7 @@ title: Get-MoveRequest
 # Get-MoveRequest
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-MoveRequest cmdlet to view the detailed status of an ongoing asynchronous mailbox move that was initiated by using the New-MoveRequest cmdlet.
 
@@ -61,7 +61,7 @@ Get-MoveRequest [-BatchName <String>]
 ## DESCRIPTION
 The search criteria for the Get-MoveRequest cmdlet is a Boolean And statement. If you use multiple parameters, it narrows your search and reduces your search results.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -196,7 +196,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
 
-The Flags parameter specifies the move type to retrieve information for. The following values may be used:
+The Flags parameter specifies the move type to retrieve information for. Valid value are:
 
 - CrossOrg
 - HighPriority
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MoveRequestStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-MoveRequestStatistics.md
index 68320eaf70..b3d60fea23 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MoveRequestStatistics.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MoveRequestStatistics.md
@@ -13,7 +13,7 @@ title: Get-MoveRequestStatistics
 # Get-MoveRequestStatistics
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-MoveRequestStatistics cmdlet to view detailed information about move requests.
 
@@ -67,7 +67,7 @@ Get-MoveRequestStatistics -MRSInstance <Fqdn>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -104,7 +104,7 @@ This example returns default statistics for all mailboxes whose move requests ar
 Get-MoveRequestStatistics -MRSInstance CAS01.contoso.com -MailboxGuid b6a6795c-a010-4f67-aaaa-da372d56fcb9
 ```
 
-In Exchange Server 2010, this example returns default statistics for a mailbox that has been moved by the instance of the Microsoft Exchange Mailbox Replication service running on the server CAS01.
+In Exchange Server 2010, this example returns default statistics for a mailbox that is moved by the instance of the Microsoft Exchange Mailbox Replication service running on the server CAS01.
 
 ### Example 6
 ```powershell
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MxRecordReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-MxRecordReport.md
index 381a4bd6ca..13fa49ad9d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MxRecordReport.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MxRecordReport.md
@@ -28,7 +28,7 @@ Get-MxRecordReport [-Domain <Fqdn>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-NetworkConnectionInfo.md b/exchange/exchange-ps/ExchangePowerShell/Get-NetworkConnectionInfo.md
index f7b4de2bb8..65e665e779 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-NetworkConnectionInfo.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-NetworkConnectionInfo.md
@@ -36,7 +36,7 @@ This cmdlet retrieves the following configuration information for each network a
 - AdapterGuid: This field displays the GUID assigned to the network adapter by Windows.
 - MacAddress: This field displays the media access control (MAC) address of the network adapter.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-Notification.md b/exchange/exchange-ps/ExchangePowerShell/Get-Notification.md
index 56c6a50bb9..88a4d4185b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-Notification.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-Notification.md
@@ -13,7 +13,7 @@ title: Get-Notification
 # Get-Notification
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 > [!NOTE]
 > This cmdlet will be deprecated in the cloud-based service. The classic Exchange admin center was deprecated in the cloud-based service in 2023.
@@ -56,7 +56,7 @@ Get-Notification [-ProcessType <AsyncOperationType>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-OMEConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Get-OMEConfiguration.md
index a949238598..a7361a7e95 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-OMEConfiguration.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-OMEConfiguration.md
@@ -27,7 +27,7 @@ Get-OMEConfiguration [[-Identity] <OMEConfigurationIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-OMEMessageStatus.md b/exchange/exchange-ps/ExchangePowerShell/Get-OMEMessageStatus.md
index 336fa65242..94749431a1 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-OMEMessageStatus.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-OMEMessageStatus.md
@@ -27,9 +27,9 @@ Get-OMEMessageStatus -MessageId <String>
 ```
 
 ## DESCRIPTION
-If encryption for the message was successfully revoked, the command will return the message: `The encrypted email with the subject "<subject>" and Message ID "<messageId>" was successfully revoked`.
+If encryption for the message was successfully revoked, the command returns the message: `The encrypted email with the subject "<subject>" and Message ID "<messageId>" was successfully revoked`.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -46,7 +46,7 @@ This example returns the encryption revocation status for the specified message.
 
 > Applicable: Exchange Online
 
-The MessageId parameter specifies the message based on the value the Message-ID header field. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which may include angle brackets) and enclose the value in quotation marks (for example, "<d9683b4c-127b-413a-ae2e-fa7dfb32c69d@DM3NAM06BG401.Eop-nam06.prod.protection.outlook.com>").
+The MessageId parameter specifies the message based on the value the Message-ID header field. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which might include angle brackets) and enclose the value in quotation marks (for example, "<d9683b4c-127b-413a-ae2e-fa7dfb32c69d@DM3NAM06BG401.Eop-nam06.prod.protection.outlook.com>").
 
 You can find the Message ID for a message in Message Trace or the Message Encryption Report in the Microsoft Purview compliance portal.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-OabVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Get-OabVirtualDirectory.md
index 7833b1e3f6..8cad368b7a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-OabVirtualDirectory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-OabVirtualDirectory.md
@@ -40,7 +40,7 @@ Get-OabVirtualDirectory [[-Identity] <VirtualDirectoryIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-OfflineAddressBook.md b/exchange/exchange-ps/ExchangePowerShell/Get-OfflineAddressBook.md
index ff9c978f2a..299ffe54d0 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-OfflineAddressBook.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-OfflineAddressBook.md
@@ -13,7 +13,7 @@ title: Get-OfflineAddressBook
 # Get-OfflineAddressBook
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-OfflineAddressBook cmdlet to view offline address books (OABs).
 
@@ -38,7 +38,7 @@ Get-OfflineAddressBook [[-Identity] <OfflineAddressBookIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-OnPremisesOrganization.md b/exchange/exchange-ps/ExchangePowerShell/Get-OnPremisesOrganization.md
index 14db290342..bb8d46bbe8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-OnPremisesOrganization.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-OnPremisesOrganization.md
@@ -15,7 +15,7 @@ title: Get-OnPremisesOrganization
 ## SYNOPSIS
 This cmdlet is available only in the cloud-based service.
 
-Use the Get-OnPremisesOrganization cmdlet to retrieve settings for the OnPremisesOrganization object that has been created for a hybrid deployment.
+Use the Get-OnPremisesOrganization cmdlet to retrieve settings for the OnPremisesOrganization object that is created for a hybrid deployment.
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
@@ -29,9 +29,9 @@ Get-OnPremisesOrganization [[-Identity] <OnPremisesOrganizationIdParameter>]
 ## DESCRIPTION
 The OnPremisesOrganization object represents an on-premises Exchange organization configured for hybrid deployment with a Microsoft 365 organization. It's used with the Hybrid Configuration wizard and is typically created automatically when the hybrid deployment is initially configured by the wizard. You can use the Get-OnPremisesOrganization cmdlet to view the properties of the OnPremisesOrganization object in the Microsoft 365 organization.
 
-Manual modification of this object may result in hybrid deployment misconfiguration. We strongly recommend that you use the Hybrid Configuration wizard to modify this object in the Microsoft 365 organization.
+Manual modification of this object might result in hybrid deployment misconfiguration. We strongly recommend that you use the Hybrid Configuration wizard to modify this object in the Microsoft 365 organization.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-OnlineMeetingConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Get-OnlineMeetingConfiguration.md
index 7a988d46c5..402cc08950 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-OnlineMeetingConfiguration.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-OnlineMeetingConfiguration.md
@@ -35,7 +35,7 @@ Exchange Online maintains a per-user cache of Skype for Business Online meeting
 - LastSyncTime: The last time Exchange Online successfully synchronized meeting coordinates from Skype for Business Online.
 - LastSuccessfulSyncTime: The last time Exchange Online successfully cleaned the cached of used Skype for Business Online meeting coordinates.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-OrganizationConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-OrganizationConfig.md
index 002af611d2..d269f440c7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-OrganizationConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-OrganizationConfig.md
@@ -13,7 +13,7 @@ title: Get-OrganizationConfig
 # Get-OrganizationConfig
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-OrganizationConfig cmdlet to get configuration data for an Exchange organization.
 
@@ -27,7 +27,7 @@ Get-OrganizationConfig [-DomainController <Fqdn>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-OrganizationRelationship.md b/exchange/exchange-ps/ExchangePowerShell/Get-OrganizationRelationship.md
index 3207111a9e..7effe3c9ad 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-OrganizationRelationship.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-OrganizationRelationship.md
@@ -13,9 +13,9 @@ title: Get-OrganizationRelationship
 # Get-OrganizationRelationship
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
-Use the Get-OrganizationRelationship cmdlet to retrieve settings for an organization relationship that has been created for federated sharing with other federated Exchange organizations or for hybrid deployments with Exchange Online.
+Use the Get-OrganizationRelationship cmdlet to retrieve settings for an organization relationship that is created for federated sharing with other federated Exchange organizations or for hybrid deployments with Exchange Online.
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
@@ -28,7 +28,7 @@ Get-OrganizationRelationship [[-Identity] <OrganizationRelationshipIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-OrganizationalUnit.md b/exchange/exchange-ps/ExchangePowerShell/Get-OrganizationalUnit.md
index b624cd2c69..35252328c5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-OrganizationalUnit.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-OrganizationalUnit.md
@@ -13,7 +13,7 @@ title: Get-OrganizationalUnit
 # Get-OrganizationalUnit
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-OrganizationalUnit cmdlet to view a list of organizational units (OUs) that exist in your organization.
 
@@ -43,7 +43,7 @@ Get-OrganizationalUnit [-SearchText <String>]
 ## DESCRIPTION
 The Get-OrganizationalUnit cmdlet is used by the Exchange admin center to populate fields that display OU information.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-OutboundConnector.md b/exchange/exchange-ps/ExchangePowerShell/Get-OutboundConnector.md
index 49cbedd76e..882495a3e6 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-OutboundConnector.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-OutboundConnector.md
@@ -32,7 +32,7 @@ Get-OutboundConnector [[-Identity] <OutboundConnectorIdParameter>]
 ## DESCRIPTION
 Outbound connectors send email messages to remote domains that require specific configuration options.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -74,7 +74,7 @@ Accept wildcard characters: False
 The IncludeTestModeConnectors parameter filters the results by Outbound connectors that are in test mode. Valid values are:
 
 - $true: Only Outbound connectors that are in test mode are returned in the results.
-- $false: All Outbound connectors that aren't in test mode are returned in the results. This is the default value.
+- $false: All Outbound connectors that aren't in test mode are returned in the results. This value is the default.
 
 You configure an Outbound connector in test mode by using the TestMode parameter on the New-OutboundConnector or Set-OutboundConnector cmdlets.
 
@@ -97,7 +97,7 @@ Accept wildcard characters: False
 The IsTransportRuleScoped parameter filters the results by Outbound connectors that are scoped to transport rules (also known as mail flow rules). Valid values are:
 
 - $true: Only Outbound connectors that are scoped to transport rules are returned in the results.
-- $false: All Outbound connectors that aren't scoped to transport rules are returned in the results. This is the default value.
+- $false: All Outbound connectors that aren't scoped to transport rules are returned in the results. This value is the default.
 
 You scope a transport rule to a specific Outbound connector by using the RouteMessageOutboundConnector parameter on the New-TransportRule or Set-TransportRule cmdlets.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-OutboundConnectorReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-OutboundConnectorReport.md
index 17040b63b4..7df51454de 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-OutboundConnectorReport.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-OutboundConnectorReport.md
@@ -28,7 +28,7 @@ Get-OutboundConnectorReport [-Domain <Fqdn>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-OutlookAnywhere.md b/exchange/exchange-ps/ExchangePowerShell/Get-OutlookAnywhere.md
index 28d5d37d26..112de05d73 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-OutlookAnywhere.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-OutlookAnywhere.md
@@ -40,7 +40,7 @@ Get-OutlookAnywhere [[-Identity] <VirtualDirectoryIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-OutlookProtectionRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-OutlookProtectionRule.md
index 30ab2649a2..c6efe5855d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-OutlookProtectionRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-OutlookProtectionRule.md
@@ -15,7 +15,7 @@ title: Get-OutlookProtectionRule
 ## SYNOPSIS
 **Note**: This cmdlet is no longer supported in the cloud-based service.
 
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-OutlookProtectionRule cmdlet to retrieve Microsoft Outlook protection rules configured in an organization.
 
@@ -32,7 +32,7 @@ Get-OutlookProtectionRule [[-Identity] <RuleIdParameter>]
 ## DESCRIPTION
 Outlook protection rules are used to automatically Information Rights Management (IRM)-protect email messages using a Rights Management Services (RMS) template before the message is sent. However, Outlook protection rules don't inspect message content. To IRM-protect messages based on message content, use transport protection rules. For more information, see [Outlook protection rules](https://learn.microsoft.com/exchange/outlook-protection-rules-exchange-2013-help).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-OutlookProvider.md b/exchange/exchange-ps/ExchangePowerShell/Get-OutlookProvider.md
index e73ad25a0a..d399eecb7f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-OutlookProvider.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-OutlookProvider.md
@@ -30,7 +30,7 @@ Get-OutlookProvider [[-Identity] <OutlookProviderIdParameter>]
 ## DESCRIPTION
 The Get-OutlookProvider cmdlet gets the global settings from the AutoDiscoverConfig object in Active Directory and returns an OutlookProvider object to be managed in the Exchange admin center.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-OwaMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-OwaMailboxPolicy.md
index b282c856fa..6e68f829bf 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-OwaMailboxPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-OwaMailboxPolicy.md
@@ -13,7 +13,7 @@ title: Get-OwaMailboxPolicy
 # Get-OwaMailboxPolicy
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-OwaMailboxPolicy cmdlet to view Outlook on the web mailbox policies in the organization.
 
@@ -28,7 +28,7 @@ Get-OwaMailboxPolicy [[-Identity] <MailboxPolicyIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-OwaVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Get-OwaVirtualDirectory.md
index 255f7385df..e918994ed0 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-OwaVirtualDirectory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-OwaVirtualDirectory.md
@@ -44,7 +44,7 @@ The Get-OwaVirtualDirectory cmdlet can be run on a local server or run remotely
 
 The Get-OwaVirtualDirectory cmdlet can be run on any server that has the Exchange Server administration tools installed.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-PartnerApplication.md b/exchange/exchange-ps/ExchangePowerShell/Get-PartnerApplication.md
index d445571b81..51e6a7a743 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-PartnerApplication.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-PartnerApplication.md
@@ -13,7 +13,7 @@ title: Get-PartnerApplication
 # Get-PartnerApplication
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-PartnerApplication cmdlet to retrieve settings for a partner application.
 
@@ -31,7 +31,7 @@ Get-PartnerApplication [[-Identity] <PartnerApplicationIdParameter>]
 ## DESCRIPTION
 You can configure partner applications such as Microsoft SharePoint to access Exchange resources. For details, see [Plan Exchange 2016 integration with SharePoint and Skype for Business](https://learn.microsoft.com/Exchange/plan-and-deploy/integration-with-sharepoint-and-skype/integration-with-sharepoint-and-skype).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-PendingDelicenseUser.md b/exchange/exchange-ps/ExchangePowerShell/Get-PendingDelicenseUser.md
index dac9418166..ffc321eb50 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-PendingDelicenseUser.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-PendingDelicenseUser.md
@@ -34,7 +34,7 @@ Get-PendingDelicenseUser [-ResultSize <Unlimited>] [-ShowDueObjectsOnly]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-PendingFederatedDomain.md b/exchange/exchange-ps/ExchangePowerShell/Get-PendingFederatedDomain.md
index 67b746dcbc..1b57b6d5c1 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-PendingFederatedDomain.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-PendingFederatedDomain.md
@@ -26,7 +26,7 @@ Get-PendingFederatedDomain [<CommonParameters>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-PhishSimOverridePolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-PhishSimOverridePolicy.md
index c782ae2639..d32e6822a1 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-PhishSimOverridePolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-PhishSimOverridePolicy.md
@@ -26,7 +26,7 @@ Get-PhishSimOverridePolicy [[-Identity] <PolicyIdParameter>] [<CommonParameters>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-Place.md b/exchange/exchange-ps/ExchangePowerShell/Get-Place.md
index 0d99aef484..cd0df94272 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-Place.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-Place.md
@@ -40,7 +40,7 @@ Get-Place [-Type <GetPlaceType>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-PolicyTipConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-PolicyTipConfig.md
index 0f66e454dd..2ac670e3e4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-PolicyTipConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-PolicyTipConfig.md
@@ -13,7 +13,7 @@ title: Get-PolicyTipConfig
 # Get-PolicyTipConfig
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-PolicyTipConfig cmdlet to view the data loss prevention (DLP) Policy Tips in your organization.
 
@@ -38,7 +38,7 @@ Get-PolicyTipConfig [[-Identity] <PolicyTipConfigIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-PopSettings.md b/exchange/exchange-ps/ExchangePowerShell/Get-PopSettings.md
index fdf0c23826..d140d3fa03 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-PopSettings.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-PopSettings.md
@@ -28,7 +28,7 @@ Get-PopSettings [-DomainController <Fqdn>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-PowerShellVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Get-PowerShellVirtualDirectory.md
index a5bc976d2e..4324161baf 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-PowerShellVirtualDirectory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-PowerShellVirtualDirectory.md
@@ -40,7 +40,7 @@ Get-PowerShellVirtualDirectory [[-Identity] <VirtualDirectoryIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolder.md b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolder.md
index 299fc5a598..aeeccce66a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolder.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolder.md
@@ -13,7 +13,7 @@ title: Get-PublicFolder
 # Get-PublicFolder
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-PublicFolder cmdlet to retrieve the attributes of a public folder or a set of public folders.
 
@@ -70,7 +70,7 @@ Get-PublicFolder [[-Identity] <PublicFolderIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -273,7 +273,7 @@ Accept wildcard characters: False
 
 The ResidentFolders switch specifies whether to return public folders that reside in a specific content public folder mailbox. You don't need to specify a value with this switch.
 
-If you don't use this switch, the command will return only public folders whose contents reside in the primary hierarchy public folder mailbox.
+If you don't use this switch, the command returns only public folders whose contents reside in the primary hierarchy public folder mailbox.
 
 ```yaml
 Type: SwitchParameter
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderAdministrativePermission.md b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderAdministrativePermission.md
index 841f2e7c5e..b11d5b7b4e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderAdministrativePermission.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderAdministrativePermission.md
@@ -38,7 +38,7 @@ Get-PublicFolderAdministrativePermission [-Identity] <PublicFolderIdParameter> [
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderClientPermission.md b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderClientPermission.md
index e72bcbe253..2b1aef2051 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderClientPermission.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderClientPermission.md
@@ -13,7 +13,7 @@ title: Get-PublicFolderClientPermission
 # Get-PublicFolderClientPermission
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-PublicFolderClientPermission cmdlet to retrieve the user permissions for a public folder.
 
@@ -34,7 +34,7 @@ Get-PublicFolderClientPermission [-Identity] <PublicFolderIdParameter>
 ## DESCRIPTION
 To view the permissions that are available on public folders, see [Public folder permissions for Exchange Server](https://learn.microsoft.com/exchange/troubleshoot/public-folders/public-folder-permissions-for-exchange-server).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderDatabase.md b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderDatabase.md
index 9850b9ee99..4e6b5127ba 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderDatabase.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderDatabase.md
@@ -46,7 +46,7 @@ You can specify either the Server or Identity parameter, but not both. Only the
 
 When you run the Get-PublicFolderDatabase cmdlet with no parameters, it returns attributes of all of the public folder databases in the Exchange organization. To return specific database properties (including backup and mount status information) where the Get-PublicFolderDatabase cmdlet has to contact servers directly or perform a complex or slow calculation, make sure you use the Status parameter.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderItemStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderItemStatistics.md
index 291f4e40cc..877ef36542 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderItemStatistics.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderItemStatistics.md
@@ -13,7 +13,7 @@ title: Get-PublicFolderItemStatistics
 # Get-PublicFolderItemStatistics
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-PublicFolderItemStatistics cmdlet to view information about items within a specified public folder. Information returned includes subject, last modification time, creation time, attachments, message size, and the type of item. You can use this raw information to better understand the distribution of items and item characteristics across public folders.
 
@@ -31,7 +31,7 @@ Get-PublicFolderItemStatistics [-Identity] <PublicFolderIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMailboxDiagnostics.md b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMailboxDiagnostics.md
index 066a6a5076..3c19ede799 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMailboxDiagnostics.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMailboxDiagnostics.md
@@ -13,7 +13,7 @@ title: Get-PublicFolderMailboxDiagnostics
 # Get-PublicFolderMailboxDiagnostics
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-PublicFolderMailboxDiagnostics cmdlet to view event-level information about a public folder mailbox. This information can be used to troubleshoot public folder issues.
 
@@ -32,7 +32,7 @@ Get-PublicFolderMailboxDiagnostics [-Identity] <MailboxIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMailboxMigrationRequest.md b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMailboxMigrationRequest.md
index ec4334625e..ab22880711 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMailboxMigrationRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMailboxMigrationRequest.md
@@ -13,7 +13,7 @@ title: Get-PublicFolderMailboxMigrationRequest
 # Get-PublicFolderMailboxMigrationRequest
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-PublicFolderMailboxMigrationRequest cmdlet to view the status of individual jobs in public folder migration batches that were created by using the New-MigrationBatch cmdlet.
 
@@ -49,7 +49,7 @@ The Get-PublicFolderMailboxMigrationRequest cmdlet displays the following proper
 - TargetMailbox: The mailbox being migrated.
 - Status: The current status of the job.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMailboxMigrationRequestStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMailboxMigrationRequestStatistics.md
index a29a4656ab..39bb0267b1 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMailboxMigrationRequestStatistics.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMailboxMigrationRequestStatistics.md
@@ -13,7 +13,7 @@ title: Get-PublicFolderMailboxMigrationRequestStatistics
 # Get-PublicFolderMailboxMigrationRequestStatistics
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-PublicFolderMailboxMigrationRequestStatistics cmdlet to view the detailed status of individual jobs in a public folder migration batch created using New-MigrationBatch cmdlet.
 
@@ -62,7 +62,7 @@ The Get-PublicFolderMailboxMigrationRequestStatistics cmdlet displays the follow
 - TargetMailbox: The mailbox being migrated.
 - PercentComplete: The percentage of job completion.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMigrationRequest.md b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMigrationRequest.md
index 14a3d3411d..0bd6706de5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMigrationRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMigrationRequest.md
@@ -46,7 +46,7 @@ Get-PublicFolderMigrationRequest [[-Identity] <PublicFolderMigrationRequestIdPar
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -62,7 +62,7 @@ This example returns the status of in-progress migration requests.
 Get-PublicFolderMigrationRequest -Identity "PFMigrate10_11_12" | Format-List Suspended,AutoSuspended
 ```
 
-This example returns all migration requests that have the name PFMigrate10\_11\_12 and the request has been suspended.
+This example returns all migration requests that have the name PFMigrate10\_11\_12 and the request is suspended.
 
 ## PARAMETERS
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMigrationRequestStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMigrationRequestStatistics.md
index 3a70bb487b..9345f6dc9f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMigrationRequestStatistics.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMigrationRequestStatistics.md
@@ -48,7 +48,7 @@ Get-PublicFolderMigrationRequestStatistics -RequestQueue <DatabaseIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMoveRequest.md b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMoveRequest.md
index e1f09381b8..61e9261c2b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMoveRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMoveRequest.md
@@ -13,7 +13,7 @@ title: Get-PublicFolderMoveRequest
 # Get-PublicFolderMoveRequest
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-PublicFolderMoveRequest cmdlet to view the detailed status of an ongoing public folder move that was initiated using the New-PublicFolderMoveRequest cmdlet.
 
@@ -44,7 +44,7 @@ Get-PublicFolderMoveRequest [-BatchName <String>] [-HighPriority <Boolean>] [-Na
 ## DESCRIPTION
 Public folder move requests are used to move public folders between public folder mailboxes. After the move request is complete, you need to update the hierarchy using the Update-PublicFolderMailbox cmdlet.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -178,7 +178,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
 
-The Name parameter specifies the name of the public folder move request. If you didn't specify a name when creating the move request, PublicFolderMove will be the default name assigned to the request.
+The Name parameter specifies the name of the public folder move request. If you didn't specify a name when creating the move request, PublicFolderMove is the default name assigned to the request.
 
 You can't use this parameter with the Identity parameter.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMoveRequestStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMoveRequestStatistics.md
index bce7688ee7..a2987dd3dc 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMoveRequestStatistics.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMoveRequestStatistics.md
@@ -13,7 +13,7 @@ title: Get-PublicFolderMoveRequestStatistics
 # Get-PublicFolderMoveRequestStatistics
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-PublicFolderMoveRequestStatistics cmdlet to view detailed information about public folder move requests.
 
@@ -48,7 +48,7 @@ Get-PublicFolderMoveRequestStatistics -RequestQueue <DatabaseIdParameter> [-Requ
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderStatistics.md
index e7fb830203..51087f7a02 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderStatistics.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderStatistics.md
@@ -13,7 +13,7 @@ title: Get-PublicFolderStatistics
 # Get-PublicFolderStatistics
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-PublicFolderStatistics cmdlet to retrieve statistical information about public folders, such as folder size and last logon time.
 
@@ -31,7 +31,7 @@ Get-PublicFolderStatistics [[-Identity] <PublicFolderIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-QuarantineMessage.md b/exchange/exchange-ps/ExchangePowerShell/Get-QuarantineMessage.md
index 06e5a73791..d96f13ebbc 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-QuarantineMessage.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-QuarantineMessage.md
@@ -61,7 +61,7 @@ Get-QuarantineMessage
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -167,11 +167,11 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
 
-The EndExpiresDate parameter specifies the latest messages that will automatically be deleted from the quarantine. Use this parameter with the StartExpiresDate parameter.
+The EndExpiresDate parameter specifies the latest messages that are automatically deleted from the quarantine. Use this parameter with the StartExpiresDate parameter.
 
 Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
 
-For example, if you specify the StartExpiresDate value of today's date and the EndExpiresDate value of the date three days from today, you will only see messages that will expire from the quarantine in the next three days.
+For example, if you specify the StartExpiresDate value of today's date and the EndExpiresDate value of the date three days from today, you only see messages that are set to expire from the quarantine in the next three days.
 
 ```yaml
 Type: System.DateTime
@@ -250,7 +250,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
 
-The MessageId parameter filters the results by the Message-ID header field of the message. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which may include angle brackets) and enclose the value in quotation marks (for example, `"<d9683b4c-127b-413a-ae2e-fa7dfb32c69d@DM3NAM06BG401.Eop-nam06.prod.protection.outlook.com>"`).
+The MessageId parameter filters the results by the Message-ID header field of the message. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which might include angle brackets) and enclose the value in quotation marks (for example, `"<d9683b4c-127b-413a-ae2e-fa7dfb32c69d@DM3NAM06BG401.Eop-nam06.prod.protection.outlook.com>"`).
 
 ```yaml
 Type: String
@@ -512,11 +512,11 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
 
-The StartExpiresDate parameter specifies the earliest messages that will automatically be deleted from the quarantine. Use this parameter with the EndExpiresDate parameter.
+The StartExpiresDate parameter specifies the earliest messages that are automatically deleted from the quarantine. Use this parameter with the EndExpiresDate parameter.
 
 Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
 
-For example, if you specify the StartExpiresDate value of today's date and the EndExpiresDate value of the date three days from today, you will only see messages that will expire from the quarantine in the next three days.
+For example, if you specify the StartExpiresDate value of today's date and the EndExpiresDate value of the date three days from today, you only see messages that are set to expire from the quarantine in the next three days.
 
 ```yaml
 Type: System.DateTime
@@ -538,7 +538,7 @@ The StartReceivedDate parameter specifies the earliest messages to return in the
 
 Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
 
-By default, if you don't use the StartReceivedDate and EndReceivedDate parameters, the command will return data for the last 16 days. The maximum value for this parameter is 30 days. If you use a value that's older than 30 days, the value is ignored and only data for the last 30 days is returned.
+By default, if you don't use the StartReceivedDate and EndReceivedDate parameters, the command returns data for the last 16 days. The maximum value for this parameter is 30 days. If you use a value that's older than 30 days, the value is ignored and only data for the last 30 days is returned.
 
 ```yaml
 Type: System.DateTime
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-QuarantineMessageHeader.md b/exchange/exchange-ps/ExchangePowerShell/Get-QuarantineMessageHeader.md
index c7f2ec7c00..d3c413a69a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-QuarantineMessageHeader.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-QuarantineMessageHeader.md
@@ -15,7 +15,7 @@ title: Get-QuarantineMessageHeader
 ## SYNOPSIS
 This cmdlet is available only in the cloud-based service.
 
-Use the Get-QuarantineMessageHeader cmdlet to view the message header of a quarantined message. The command will fail if the specified message is not in quarantine.
+Use the Get-QuarantineMessageHeader cmdlet to view the message header of a quarantined message. The command fails if the specified message is not in quarantine.
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
@@ -31,7 +31,7 @@ Get-QuarantineMessageHeader -Identity <QuarantineMessageIdentity>
 ## DESCRIPTION
 Standard SMTP message header syntax is described in RFC 5322. This cmdlet displays the message header exactly as it appears in the message. Individual header fields are not unfolded.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 

From 91da772d991a0a1e3cf25bd7248add07303d1605 Mon Sep 17 00:00:00 2001
From: Chris Davis <chris.davis@microsoft.com>
Date: Wed, 6 Aug 2025 08:47:32 -0700
Subject: [PATCH 093/145] Acrolinx 8

---
 .../ExchangePowerShell/Get-QuarantinePolicy.md            | 4 ++--
 exchange/exchange-ps/ExchangePowerShell/Get-Queue.md      | 2 +-
 .../exchange-ps/ExchangePowerShell/Get-QueueDigest.md     | 2 +-
 .../exchange-ps/ExchangePowerShell/Get-RMSTemplate.md     | 4 ++--
 .../ExchangePowerShell/Get-ReceiveConnector.md            | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Get-Recipient.md  | 8 ++++----
 .../ExchangePowerShell/Get-RecipientFilterConfig.md       | 2 +-
 .../ExchangePowerShell/Get-RecipientPermission.md         | 2 +-
 .../ExchangePowerShell/Get-RecipientStatisticsReport.md   | 2 +-
 .../ExchangePowerShell/Get-RecoverableItems.md            | 4 ++--
 .../exchange-ps/ExchangePowerShell/Get-RemoteDomain.md    | 4 ++--
 .../exchange-ps/ExchangePowerShell/Get-RemoteMailbox.md   | 2 +-
 .../ExchangePowerShell/Get-ReportExecutionInstance.md     | 4 ++--
 .../ExchangePowerShell/Get-ReportSubmissionPolicy.md      | 2 +-
 .../ExchangePowerShell/Get-ReportSubmissionRule.md        | 2 +-
 .../exchange-ps/ExchangePowerShell/Get-ResourceConfig.md  | 4 ++--
 .../exchange-ps/ExchangePowerShell/Get-ResubmitRequest.md | 2 +-
 .../ExchangePowerShell/Get-RetentionCompliancePolicy.md   | 2 +-
 .../exchange-ps/ExchangePowerShell/Get-RetentionEvent.md  | 2 +-
 .../exchange-ps/ExchangePowerShell/Get-RetentionPolicy.md | 6 +++---
 .../ExchangePowerShell/Get-RetentionPolicyTag.md          | 4 ++--
 .../exchange-ps/ExchangePowerShell/Get-ReviewItems.md     | 6 +++---
 .../ExchangePowerShell/Get-RoleAssignmentPolicy.md        | 4 ++--
 exchange/exchange-ps/ExchangePowerShell/Get-RoleGroup.md  | 4 ++--
 .../exchange-ps/ExchangePowerShell/Get-RoleGroupMember.md | 4 ++--
 .../ExchangePowerShell/Get-RoutingGroupConnector.md       | 2 +-
 .../exchange-ps/ExchangePowerShell/Get-RpcClientAccess.md | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Get-SCInsights.md | 2 +-
 .../ExchangePowerShell/Get-SafeAttachmentPolicy.md        | 2 +-
 .../ExchangePowerShell/Get-SafeAttachmentRule.md          | 2 +-
 .../ExchangePowerShell/Get-SafeLinksAggregateReport.md    | 4 ++--
 .../ExchangePowerShell/Get-SafeLinksDetailReport.md       | 4 ++--
 .../exchange-ps/ExchangePowerShell/Get-SafeLinksPolicy.md | 2 +-
 .../exchange-ps/ExchangePowerShell/Get-SafeLinksRule.md   | 2 +-
 .../ExchangePowerShell/Get-SearchDocumentFormat.md        | 4 ++--
 .../ExchangePowerShell/Get-SecOpsOverridePolicy.md        | 2 +-
 .../ExchangePowerShell/Get-SecurityPrincipal.md           | 4 ++--
 .../exchange-ps/ExchangePowerShell/Get-SendConnector.md   | 2 +-
 .../ExchangePowerShell/Get-SenderFilterConfig.md          | 2 +-
 .../exchange-ps/ExchangePowerShell/Get-SenderIdConfig.md  | 2 +-
 .../ExchangePowerShell/Get-SenderReputationConfig.md      | 2 +-
 .../ExchangePowerShell/Get-ServerComponentState.md        | 2 +-
 .../exchange-ps/ExchangePowerShell/Get-ServerHealth.md    | 4 ++--
 .../ExchangePowerShell/Get-ServerMonitoringOverride.md    | 2 +-
 .../ExchangePowerShell/Get-ServiceDeliveryReport.md       | 2 +-
 .../ExchangePowerShell/Get-ServicePrincipal.md            | 2 +-
 .../exchange-ps/ExchangePowerShell/Get-SettingOverride.md | 2 +-
 .../exchange-ps/ExchangePowerShell/Get-SharingPolicy.md   | 6 +++---
 .../exchange-ps/ExchangePowerShell/Get-SiteMailbox.md     | 6 +++---
 .../ExchangePowerShell/Get-SiteMailboxDiagnostics.md      | 2 +-
 .../Get-SiteMailboxProvisioningPolicy.md                  | 2 +-
 .../exchange-ps/ExchangePowerShell/Get-SmimeConfig.md     | 4 ++--
 .../ExchangePowerShell/Get-SmtpDaneInboundStatus.md       | 2 +-
 .../ExchangePowerShell/Get-SpoofIntelligenceInsight.md    | 2 +-
 .../exchange-ps/ExchangePowerShell/Get-SpoofMailReport.md | 4 ++--
 .../ExchangePowerShell/Get-StoreUsageStatistics.md        | 2 +-
 .../ExchangePowerShell/Get-SupervisoryReviewActivity.md   | 4 ++--
 exchange/exchange-ps/ExchangePowerShell/Get-SweepRule.md  | 4 ++--
 .../exchange-ps/ExchangePowerShell/Get-SystemMessage.md   | 4 ++--
 .../ExchangePowerShell/Get-TeamsProtectionPolicy.md       | 2 +-
 .../ExchangePowerShell/Get-TeamsProtectionPolicyRule.md   | 2 +-
 .../ExchangePowerShell/Get-TenantAllowBlockListItems.md   | 4 ++--
 .../Get-TenantAllowBlockListSpoofItems.md                 | 4 ++--
 .../ExchangePowerShell/Get-TextMessagingAccount.md        | 4 ++--
 .../ExchangePowerShell/Get-ThrottlingPolicy.md            | 2 +-
 .../ExchangePowerShell/Get-ThrottlingPolicyAssociation.md | 2 +-
 .../exchange-ps/ExchangePowerShell/Get-TransportAgent.md  | 2 +-
 .../exchange-ps/ExchangePowerShell/Get-TransportConfig.md | 4 ++--
 .../ExchangePowerShell/Get-TransportPipeline.md           | 2 +-
 .../exchange-ps/ExchangePowerShell/Get-TransportRule.md   | 6 +++---
 .../ExchangePowerShell/Get-TransportRuleAction.md         | 4 ++--
 .../ExchangePowerShell/Get-TransportRulePredicate.md      | 4 ++--
 .../exchange-ps/ExchangePowerShell/Get-TransportServer.md | 2 +-
 .../ExchangePowerShell/Get-TransportService.md            | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Get-Trust.md      | 2 +-
 .../exchange-ps/ExchangePowerShell/Get-UMActiveCalls.md   | 2 +-
 .../exchange-ps/ExchangePowerShell/Get-UMAutoAttendant.md | 2 +-
 .../ExchangePowerShell/Get-UMCallAnsweringRule.md         | 6 +++---
 .../ExchangePowerShell/Get-UMCallDataRecord.md            | 4 ++--
 .../ExchangePowerShell/Get-UMCallRouterSettings.md        | 2 +-
 .../ExchangePowerShell/Get-UMCallSummaryReport.md         | 4 ++--
 exchange/exchange-ps/ExchangePowerShell/Get-UMDialPlan.md | 2 +-
 .../exchange-ps/ExchangePowerShell/Get-UMHuntGroup.md     | 2 +-
 .../exchange-ps/ExchangePowerShell/Get-UMIPGateway.md     | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Get-UMMailbox.md  | 2 +-
 .../exchange-ps/ExchangePowerShell/Get-UMMailboxPin.md    | 4 ++--
 .../exchange-ps/ExchangePowerShell/Get-UMMailboxPolicy.md | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Get-UMServer.md   | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Get-UMService.md  | 2 +-
 .../exchange-ps/ExchangePowerShell/Get-UnifiedGroup.md    | 2 +-
 .../ExchangePowerShell/Get-UnifiedGroupLinks.md           | 2 +-
 exchange/exchange-ps/ExchangePowerShell/Get-User.md       | 4 ++--
 exchange/exchange-ps/ExchangePowerShell/Get-UserPhoto.md  | 2 +-
 .../ExchangePowerShell/Get-UserPrincipalNamesSuffix.md    | 2 +-
 .../ExchangePowerShell/Get-WebServicesVirtualDirectory.md | 2 +-
 95 files changed, 140 insertions(+), 140 deletions(-)

diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-QuarantinePolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-QuarantinePolicy.md
index b36d1fde0f..e4136578f7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-QuarantinePolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-QuarantinePolicy.md
@@ -30,7 +30,7 @@ Get-QuarantinePolicy [[-Identity] <QuarantineTagIdParameter>]
 ## DESCRIPTION
 Quarantine policies define what users are allowed to do to quarantined messages based on why the message was quarantined (for supported features) and quarantine notification settings. For more information, see [Quarantine policies](https://learn.microsoft.com/defender-office-365/quarantine-policies).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -85,7 +85,7 @@ Accept wildcard characters: False
 
 The QuarantinePolicyType parameter filters the results by the specified quarantine policy type. Valid values are:
 
-- QuarantinePolicy: This is the default value, and returns built-in and custom quarantine policies.
+- QuarantinePolicy: This value is the default, and returns built-in and custom quarantine policies.
 - GlobalQuarantinePolicy: This value is required to return the global settings (quarantine notification settings) in the quarantine policy named DefaultGlobalTag.
 
 ```yaml
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-Queue.md b/exchange/exchange-ps/ExchangePowerShell/Get-Queue.md
index a05d1686df..02f901b65b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-Queue.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-Queue.md
@@ -53,7 +53,7 @@ Get-Queue [-Server <ServerIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-QueueDigest.md b/exchange/exchange-ps/ExchangePowerShell/Get-QueueDigest.md
index c4277836aa..3e658ea466 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-QueueDigest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-QueueDigest.md
@@ -68,7 +68,7 @@ Get-QueueDigest -Site <MultiValuedProperty>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-RMSTemplate.md b/exchange/exchange-ps/ExchangePowerShell/Get-RMSTemplate.md
index a4ee2746eb..dcd9a4ad30 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-RMSTemplate.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-RMSTemplate.md
@@ -13,7 +13,7 @@ title: Get-RMSTemplate
 # Get-RMSTemplate
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-RMSTemplate cmdlet to retrieve the current list of active rights policy templates from the Active Directory Rights Management Services (AD RMS) deployment for the organization.
 
@@ -33,7 +33,7 @@ Get-RMSTemplate [[-Identity] <RmsTemplateIdParameter>]
 ## DESCRIPTION
 The Get-RMSTemplate cmdlet doesn't return any active rights policy templates if internal licensing isn't enabled. Use the Get-IRMConfiguration cmdlet to check the InternalLicensingEnabled parameter.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ReceiveConnector.md b/exchange/exchange-ps/ExchangePowerShell/Get-ReceiveConnector.md
index fe560729f4..1405cdb418 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ReceiveConnector.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ReceiveConnector.md
@@ -38,7 +38,7 @@ Get-ReceiveConnector [-Server <ServerIdParameter>]
 ## DESCRIPTION
 You can view Receive connectors on Mailbox servers and Edge Transport servers.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-Recipient.md b/exchange/exchange-ps/ExchangePowerShell/Get-Recipient.md
index 4497518c48..fb5e831977 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-Recipient.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-Recipient.md
@@ -13,7 +13,7 @@ title: Get-Recipient
 # Get-Recipient
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-Recipient cmdlet to view existing recipient objects in your organization. This cmdlet returns all mail-enabled objects (for example, mailboxes, mail users, mail contacts, and distribution groups).
 
@@ -115,9 +115,9 @@ Get-Recipient [-RecipientPreviewFilter <String>]
 ```
 
 ## DESCRIPTION
-The Get-Recipient cmdlet may not return all object-specific properties for a recipient. To view the object-specific properties for a recipient, you need to use the corresponding cmdlet based on the object type (for example, Get-Mailbox, Get-MailUser, or Get-DistributionGroup).
+The Get-Recipient cmdlet might not return all object-specific properties for a recipient. To view the object-specific properties for a recipient, you need to use the corresponding cmdlet based on the object type (for example, Get-Mailbox, Get-MailUser, or Get-DistributionGroup).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -599,7 +599,7 @@ The RecipientTypeDetails parameter filters the results by the specified recipien
 
 You can specify multiple values separated by commas.
 
-The value of the RecipientType parameter affects the values that you can use for this parameter. For example, if you use the RecipientType value MailContact, you can't use the value UserMailbox for this parameter. You'll receive the error: None of the specified RecipientTypeDetails are included in any specified recipient type.
+The value of the RecipientType parameter affects the values that you can use for this parameter. For example, if you use the RecipientType value MailContact, you can't use the value UserMailbox for this parameter. You get the error: None of the specified RecipientTypeDetails are included in any specified recipient type.
 
 ```yaml
 Type: RecipientTypeDetails[]
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-RecipientFilterConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-RecipientFilterConfig.md
index 050feb8da1..bba82d81ec 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-RecipientFilterConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-RecipientFilterConfig.md
@@ -28,7 +28,7 @@ Get-RecipientFilterConfig [[-Identity] <OrganizationIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-RecipientPermission.md b/exchange/exchange-ps/ExchangePowerShell/Get-RecipientPermission.md
index 65d31fe008..a5c68f73cf 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-RecipientPermission.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-RecipientPermission.md
@@ -38,7 +38,7 @@ When a user is given SendAs permission to another user or group, the user can se
 > [!NOTE]
 > This cmdlet doesn't return expected results when the recipient specified by the Trustee parameter has multiple `SecurityPrincipalIdParameter` (Sid) values. When you use the Trustee parameter, the command compares the Sid of the specified Trustee with the recipient's access control list (ACL) record. If some of the recipient's Sid values have changed, there's a mismatch. The workaround is to not to use the user principal name (UPN) value, to use all Sids including the one for history.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-RecipientStatisticsReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-RecipientStatisticsReport.md
index e11d4e6142..aa8daee7d8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-RecipientStatisticsReport.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-RecipientStatisticsReport.md
@@ -28,7 +28,7 @@ Get-RecipientStatisticsReport [<CommonParameters>]
 ## DESCRIPTION
 The recipient statistics report provides information about the total number of mailboxes and the total number of active mailboxes in the organization.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-RecoverableItems.md b/exchange/exchange-ps/ExchangePowerShell/Get-RecoverableItems.md
index 796b999fed..8d5b5d87bb 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-RecoverableItems.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-RecoverableItems.md
@@ -12,7 +12,7 @@ title: Get-RecoverableItems
 # Get-RecoverableItems
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-RecoverableItems items cmdlet to view deleted items in mailboxes. After you find the deleted items, you use the Restore-RecoverableItems cmdlet to restore them.
 
@@ -54,7 +54,7 @@ Get-RecoverableItems -Identity <GeneralMailboxOrMailUserIdParameter[]>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-RemoteDomain.md b/exchange/exchange-ps/ExchangePowerShell/Get-RemoteDomain.md
index 8fa4cd2d7e..7244b020da 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-RemoteDomain.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-RemoteDomain.md
@@ -13,7 +13,7 @@ title: Get-RemoteDomain
 # Get-RemoteDomain
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-RemoteDomain cmdlet to view the configuration information for the remote domains configured in your organization. You can view the remote domain configuration from inside the Exchange organization or from an Edge Transport server in the perimeter network.
 
@@ -29,7 +29,7 @@ Get-RemoteDomain [[-Identity] <RemoteDomainIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-RemoteMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Get-RemoteMailbox.md
index 288f6d8327..b68d619e0f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-RemoteMailbox.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-RemoteMailbox.md
@@ -52,7 +52,7 @@ Get-RemoteMailbox [[-Identity] <RemoteMailboxIdParameter>]
 ## DESCRIPTION
 The Get-RemoteMailbox cmdlet retrieves the mail-related attributes of a mail user in the on-premises Active Directory. It doesn't retrieve the attributes of the associated cloud-based mailbox. Most of the mail-related attributes of the on-premises mail user and the associated cloud-based mailbox should be the same. However, the cloud-based mailbox has additional attributes that you can't view by using this cmdlet. To view the attributes of the cloud-based mailbox, you need to use the Exchange admin center in the cloud-based service, or connect to your cloud-based organization and run the Get-Mailbox cmdlet.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ReportExecutionInstance.md b/exchange/exchange-ps/ExchangePowerShell/Get-ReportExecutionInstance.md
index 8c2a4481b7..ad948f54d5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ReportExecutionInstance.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ReportExecutionInstance.md
@@ -28,7 +28,7 @@ Get-ReportExecutionInstance [-Identity <InstanceIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -70,7 +70,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online, Exchange Online Protection
 
-The ScheduleId parameter filters the results by the specified ScheduleId property value, which is a GUID. Note that multiple report execution instances can have the same ScheduleId value.
+The ScheduleId parameter filters the results by the specified ScheduleId property value, which is a GUID. Multiple report execution instances can have the same ScheduleId value.
 
 ```yaml
 Type: MultiValuedProperty
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ReportSubmissionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-ReportSubmissionPolicy.md
index 5e6ea078a9..09a5ba4f86 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ReportSubmissionPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ReportSubmissionPolicy.md
@@ -30,7 +30,7 @@ The report submission policy controls most of the settings for user submissions
 
 The report submission rule (\*-ReportSubmissionRule cmdlets) controls the email address of the reporting mailbox where user reported messages are delivered.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ReportSubmissionRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-ReportSubmissionRule.md
index 90b8ad8b50..9761c1326e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ReportSubmissionRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ReportSubmissionRule.md
@@ -26,7 +26,7 @@ Get-ReportSubmissionRule [[-Identity] <RuleIdParameter>] [-State <RuleState>] [<
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ResourceConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-ResourceConfig.md
index fc626e15b6..077decbd72 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ResourceConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ResourceConfig.md
@@ -13,7 +13,7 @@ title: Get-ResourceConfig
 # Get-ResourceConfig
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-ResourceConfig cmdlet to view custom room and equipment mailbox properties that you've configured by using the Set-ResourceConfig cmdlet.
 
@@ -28,7 +28,7 @@ Get-ResourceConfig [[-Identity] <OrganizationIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ResubmitRequest.md b/exchange/exchange-ps/ExchangePowerShell/Get-ResubmitRequest.md
index aa641f4105..a4f888b146 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ResubmitRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ResubmitRequest.md
@@ -28,7 +28,7 @@ Get-ResubmitRequest [[-Identity] <ResubmitRequestIdentityParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-RetentionCompliancePolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-RetentionCompliancePolicy.md
index 6f0edb31bd..1e0536d222 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-RetentionCompliancePolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-RetentionCompliancePolicy.md
@@ -37,7 +37,7 @@ Get-RetentionCompliancePolicy [[-Identity] <PolicyIdParameter>]
 This list describes the properties that are displayed by default.
 
 - Name: The unique name of the policy.
-- Workload: At the moment, it will show all workloads (Exchange, SharePoint, OneDriveForBusiness, Skype, ModernGroup) and it will not show the actual workload on which the policy is applied.
+- Workload: Currently, it shows all workloads (Exchange, SharePoint, OneDriveForBusiness, Skype, ModernGroup). It doesn't show the actual workload on which the policy is applied.
 - Enabled: The value True means the policy is enabled.
 - Mode: The current operating mode of the policy. The possible values are Test (the content is tested, but no rules are enforced), AuditAndNotify (when content matches the conditions specified by the policy, the rule is not enforced, but notification emails are sent) or Enforce (all aspects of the policy are enabled and enforced).
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-RetentionEvent.md b/exchange/exchange-ps/ExchangePowerShell/Get-RetentionEvent.md
index e8c112c3ed..d80526413b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-RetentionEvent.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-RetentionEvent.md
@@ -29,7 +29,7 @@ Get-RetentionEvent [[-Identity] <EwsStoreObjectIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-RetentionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-RetentionPolicy.md
index 4b13d321a9..877c8a1f16 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-RetentionPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-RetentionPolicy.md
@@ -13,7 +13,7 @@ title: Get-RetentionPolicy
 # Get-RetentionPolicy
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-RetentionPolicy cmdlet to retrieve the settings for retention policies.
 
@@ -28,9 +28,9 @@ Get-RetentionPolicy [[-Identity] <MailboxPolicyIdParameter>]
 ```
 
 ## DESCRIPTION
-A retention policy is associated with a group of retention policy tags that specify retention settings for items in a mailbox. A policy may contain one default policy tag to move items to an archive mailbox, one default policy tag to delete all items, one default policy tag to delete voicemail items and multiple personal tags to move or delete items. A mailbox can have only one retention policy applied to it. The Get-RetentionPolicy cmdlet displays all policy settings associated with the specified policy.
+A retention policy is associated with a group of retention policy tags that specify retention settings for items in a mailbox. A policy might contain one default policy tag to move items to an archive mailbox, one default policy tag to delete all items, one default policy tag to delete voicemail items and multiple personal tags to move or delete items. A mailbox can have only one retention policy applied to it. The Get-RetentionPolicy cmdlet displays all policy settings associated with the specified policy.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-RetentionPolicyTag.md b/exchange/exchange-ps/ExchangePowerShell/Get-RetentionPolicyTag.md
index 97f1c0a293..a76704a0e9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-RetentionPolicyTag.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-RetentionPolicyTag.md
@@ -13,7 +13,7 @@ title: Get-RetentionPolicyTag
 # Get-RetentionPolicyTag
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-RetentionPolicyTag cmdlet to retrieve settings for a retention tag.
 
@@ -49,7 +49,7 @@ Retention tags are used to apply message retention settings to messages or folde
 
 Retention policy tags are applied to default folders such as Inbox and Deleted Items. Personal tags are available to users to tag items and folders. The default policy tag is applied to all items that don't have a tag applied by the user or aren't inherited from the folder they're located in. The Get-RetentionPolicyTag cmdlet displays all the settings for the specified tag.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ReviewItems.md b/exchange/exchange-ps/ExchangePowerShell/Get-ReviewItems.md
index 63618d7061..24f56ac095 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ReviewItems.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ReviewItems.md
@@ -32,7 +32,7 @@ Get-ReviewItems -TargetLabelId <String>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 The `Get-ReviewItems` cmdlet can be used to export a list of pending or disposed items from disposition review. To learn more about disposition review, see [Disposition of content](https://learn.microsoft.com/purview/disposition).
 
@@ -111,7 +111,7 @@ Accept wildcard characters: False
 The Disposed parameter specifies whether to return disposed items instead of items pending disposition. Valid values are:
 
 - $true: Return disposed items.
-- $false: Return items pending disposition. This is the default value.
+- $false: Return items pending disposition. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -132,7 +132,7 @@ Accept wildcard characters: False
 The IncludeHeaders parameter specifies whether headers are returned as a property with the review items. Valid values are:
 
 - $true: Headers are returned as a property with the review items. This option is useful when converting the output to a PSObject in PowerShell or when exporting to CSV.
-- $false: Headers are not returned as a property with the review items. This is the default value.
+- $false: Headers are not returned as a property with the review items. This value is the default.
 
 ```yaml
 Type: Boolean
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-RoleAssignmentPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-RoleAssignmentPolicy.md
index 0265d8527c..ba3b5931f4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-RoleAssignmentPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-RoleAssignmentPolicy.md
@@ -13,7 +13,7 @@ title: Get-RoleAssignmentPolicy
 # Get-RoleAssignmentPolicy
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-RoleAssignmentPolicy cmdlet to view existing management role assignment policies in your organization.
 
@@ -30,7 +30,7 @@ Get-RoleAssignmentPolicy [[-Identity] <MailboxPolicyIdParameter>]
 ## DESCRIPTION
 For more information about assignment policies, see [Understanding management role assignment policies](https://learn.microsoft.com/exchange/understanding-management-role-assignment-policies-exchange-2013-help).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-RoleGroup.md b/exchange/exchange-ps/ExchangePowerShell/Get-RoleGroup.md
index 2a63f95861..b39c089258 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-RoleGroup.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-RoleGroup.md
@@ -13,7 +13,7 @@ title: Get-RoleGroup
 # Get-RoleGroup
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-RoleGroup cmdlet to retrieve a list of management role groups.
 
@@ -35,7 +35,7 @@ Get-RoleGroup [[-Identity] <RoleGroupIdParameter>]
 ## DESCRIPTION
 For more information about role groups, see [Understanding management role groups](https://learn.microsoft.com/exchange/understanding-management-role-groups-exchange-2013-help).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-RoleGroupMember.md b/exchange/exchange-ps/ExchangePowerShell/Get-RoleGroupMember.md
index eb04094c83..0d162d0acd 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-RoleGroupMember.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-RoleGroupMember.md
@@ -13,7 +13,7 @@ title: Get-RoleGroupMember
 # Get-RoleGroupMember
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-RoleGroupMember cmdlet to retrieve a list of members of a management role group.
 
@@ -32,7 +32,7 @@ Get-RoleGroupMember [-Identity] <RoleGroupMemberIdParameter>
 ## DESCRIPTION
 For more information about role groups, see [Understanding management role groups](https://learn.microsoft.com/exchange/understanding-management-role-groups-exchange-2013-help).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-RoutingGroupConnector.md b/exchange/exchange-ps/ExchangePowerShell/Get-RoutingGroupConnector.md
index 02c53261b2..7825224008 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-RoutingGroupConnector.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-RoutingGroupConnector.md
@@ -30,7 +30,7 @@ Get-RoutingGroupConnector [[-Identity] <RoutingGroupConnectorIdParameter>]
 ## DESCRIPTION
 The Get-RoutingGroupConnector cmdlet displays the configuration details of routing group connectors that exist when an organization is running Exchange 2010 and Exchange Server 2003. A routing group connector is used to send and receive messages between Exchange 2010 Hub Transport servers and Exchange 2003 bridgehead servers.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-RpcClientAccess.md b/exchange/exchange-ps/ExchangePowerShell/Get-RpcClientAccess.md
index 558b8e2687..75649aaa67 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-RpcClientAccess.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-RpcClientAccess.md
@@ -28,7 +28,7 @@ Get-RpcClientAccess [-DomainController <Fqdn>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SCInsights.md b/exchange/exchange-ps/ExchangePowerShell/Get-SCInsights.md
index 4ff893c003..7482a56503 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SCInsights.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-SCInsights.md
@@ -35,7 +35,7 @@ This cmdlet returns the following output:
 - InsightSubType: The value All or Archive.
 - UsersCount: An integer count, or the size in megabytes for the InsightType value.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SafeAttachmentPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-SafeAttachmentPolicy.md
index 126fcd4417..e6b721443e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SafeAttachmentPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-SafeAttachmentPolicy.md
@@ -29,7 +29,7 @@ Get-SafeAttachmentPolicy [[-Identity] <SafeAttachmentPolicyIdParameter>]
 ## DESCRIPTION
 Safe Attachments is a feature in Microsoft Defender for Office 365 that opens email attachments in a special hypervisor environment to detect malicious activity. For more information, see [Safe Attachments in Defender for Office 365](https://learn.microsoft.com/defender-office-365/safe-attachments-about).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SafeAttachmentRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-SafeAttachmentRule.md
index d5b539c3be..d2b729ab89 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SafeAttachmentRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-SafeAttachmentRule.md
@@ -30,7 +30,7 @@ Get-SafeAttachmentRule [[-Identity] <RuleIdParameter>]
 ## DESCRIPTION
 Safe Attachments is a feature in Microsoft Defender for Office 365 that opens email attachments in a special hypervisor environment to detect malicious activity. For more information, see [Safe Attachments in Defender for Office 365](https://learn.microsoft.com/defender-office-365/safe-attachments-about).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SafeLinksAggregateReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-SafeLinksAggregateReport.md
index 921116fc89..a44c75426c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SafeLinksAggregateReport.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-SafeLinksAggregateReport.md
@@ -32,7 +32,7 @@ Get-SafeLinksAggregateReport
 ```
 
 ## DESCRIPTION
-**Note**: If you run Get-SafeLinksAggregateReport without specifying a date range, the command will return an unspecified error.
+**Note**: If you run Get-SafeLinksAggregateReport without specifying a date range, the command returns an unspecified error.
 
 Safe Links is a feature in Microsoft Defender for Office 365 that checks links in email messages to see if they lead to malicious web sites. When a user clicks a link in a message, the URL is temporarily rewritten and checked against a list of known, malicious web sites.
 
@@ -43,7 +43,7 @@ For the reporting period you specify, the cmdlet returns the following informati
 - MessageCount
 - RecipientCount
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SafeLinksDetailReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-SafeLinksDetailReport.md
index 7d26d0b6c1..1bc37e0c2f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SafeLinksDetailReport.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-SafeLinksDetailReport.md
@@ -35,7 +35,7 @@ Get-SafeLinksDetailReport
 ```
 
 ## DESCRIPTION
-**Note**: If you run Get-SafeLinksDetailReport without specifying a date range, the command will return an unspecified error.
+**Note**: If you run Get-SafeLinksDetailReport without specifying a date range, the command returns an unspecified error.
 
 Safe Links is a feature in Microsoft Defender for Office 365 that checks links in email messages to see if they lead to malicious web sites. When a user clicks a link in a message, the URL is temporarily rewritten and checked against a list of known, malicious web sites.
 
@@ -56,7 +56,7 @@ This cmdlet returns the following information:
 - UrlType (currently empty)
 - Flags (0: Allowed 1: Blocked 2: ClickedEvenBlocked 3: ClickedDuringScan)
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SafeLinksPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-SafeLinksPolicy.md
index a50d913ed8..57e426f923 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SafeLinksPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-SafeLinksPolicy.md
@@ -29,7 +29,7 @@ Get-SafeLinksPolicy [[-Identity] <SafeLinksPolicyIdParameter>]
 ## DESCRIPTION
 Safe Links is a feature in Microsoft Defender for Office 365 that checks links in email messages to see if they lead to malicious web sites. When a user clicks a link in a message, the URL is temporarily rewritten and checked against a list of known, malicious web sites. Safe Links includes the URL trace reporting feature to help determine who has clicked through to a malicious web site.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SafeLinksRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-SafeLinksRule.md
index 73b94df76c..bf94afdaa2 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SafeLinksRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-SafeLinksRule.md
@@ -30,7 +30,7 @@ Get-SafeLinksRule [[-Identity] <RuleIdParameter>]
 ## DESCRIPTION
 Safe Links is a feature in Microsoft Defender for Office 365 that checks links in email messages to see if they lead to malicious web sites. When a user clicks a link in a message, the URL is temporarily rewritten and checked against a list of known, malicious web sites. Safe Links includes the URL trace reporting feature to help determine who has clicked through to a malicious web site.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SearchDocumentFormat.md b/exchange/exchange-ps/ExchangePowerShell/Get-SearchDocumentFormat.md
index ddcea38f6a..a9c7d69dd8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SearchDocumentFormat.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-SearchDocumentFormat.md
@@ -13,7 +13,7 @@ title: Get-SearchDocumentFormat
 # Get-SearchDocumentFormat
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-SearchDocumentFormat cmdlet to retrieve details of file formats supported by Exchange Search.
 
@@ -30,7 +30,7 @@ Get-SearchDocumentFormat [[-Identity] <SearchDocumentFormatId>]
 ## DESCRIPTION
 Exchange Search includes built-in support for indexing many file formats. Output from the Get-SearchDocumentFormat cmdlet includes details about each supported file format, including whether content indexing is enabled for the file format, the format handler and the file extension (such as .docx).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SecOpsOverridePolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-SecOpsOverridePolicy.md
index ecff279a3f..88e85ee0b6 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SecOpsOverridePolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-SecOpsOverridePolicy.md
@@ -28,7 +28,7 @@ Get-SecOpsOverridePolicy [[-Identity] <PolicyIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SecurityPrincipal.md b/exchange/exchange-ps/ExchangePowerShell/Get-SecurityPrincipal.md
index 28d3b1a44d..e79ff3157f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SecurityPrincipal.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-SecurityPrincipal.md
@@ -13,7 +13,7 @@ title: Get-SecurityPrincipal
 # Get-SecurityPrincipal
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-SecurityPrincipal cmdlet to return a list of security principals. Security principals are entities, such as users or security groups, which can be assigned permissions and user rights.
 
@@ -36,7 +36,7 @@ Get-SecurityPrincipal [[-Identity] <ExtendedSecurityPrincipalIdParameter>]
 ## DESCRIPTION
 The Get-SecurityPrincipal cmdlet is used by the Exchange admin center to populate fields that display recipient information.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SendConnector.md b/exchange/exchange-ps/ExchangePowerShell/Get-SendConnector.md
index 05f88698a8..b88096e120 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SendConnector.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-SendConnector.md
@@ -28,7 +28,7 @@ Get-SendConnector [[-Identity] <SendConnectorIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SenderFilterConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-SenderFilterConfig.md
index 4cf064d7b1..3a2fac09b4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SenderFilterConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-SenderFilterConfig.md
@@ -28,7 +28,7 @@ Get-SenderFilterConfig [[-Identity] <OrganizationIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SenderIdConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-SenderIdConfig.md
index ec6ce1c598..a48fe97c5b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SenderIdConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-SenderIdConfig.md
@@ -27,7 +27,7 @@ Get-SenderIdConfig [-DomainController <Fqdn>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SenderReputationConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-SenderReputationConfig.md
index 871add3003..8bec50233b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SenderReputationConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-SenderReputationConfig.md
@@ -27,7 +27,7 @@ Get-SenderReputationConfig [-DomainController <Fqdn>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ServerComponentState.md b/exchange/exchange-ps/ExchangePowerShell/Get-ServerComponentState.md
index 5a82a37409..357deadb5d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ServerComponentState.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ServerComponentState.md
@@ -29,7 +29,7 @@ Get-ServerComponentState [-Identity] <ServerIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ServerHealth.md b/exchange/exchange-ps/ExchangePowerShell/Get-ServerHealth.md
index 3dd602e8a9..19532a3368 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ServerHealth.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ServerHealth.md
@@ -29,11 +29,11 @@ Get-ServerHealth [-Identity] <ServerIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 The cmdlet returns health values that you can use to determine the state of the server. See [Server health and performance in Exchange Server](https://learn.microsoft.com/Exchange/server-health/server-health) for related information.
 
-The cmdlet also returns an alert value that provides the specific state of your server. The following values may be returned:
+The cmdlet also returns an alert value that provides the specific state of your server. The following values might be returned:
 
 - Degraded
 - Unhealthy
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ServerMonitoringOverride.md b/exchange/exchange-ps/ExchangePowerShell/Get-ServerMonitoringOverride.md
index 641724b1b8..afcf7555af 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ServerMonitoringOverride.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ServerMonitoringOverride.md
@@ -27,7 +27,7 @@ Get-ServerMonitoringOverride -Server <ServerIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ServiceDeliveryReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-ServiceDeliveryReport.md
index 8b0404f1c8..2b0bbce739 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ServiceDeliveryReport.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ServiceDeliveryReport.md
@@ -28,7 +28,7 @@ Get-ServiceDeliveryReport [-ProbeTag <String>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ServicePrincipal.md b/exchange/exchange-ps/ExchangePowerShell/Get-ServicePrincipal.md
index 19cfbc1188..f8d118cd49 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ServicePrincipal.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ServicePrincipal.md
@@ -32,7 +32,7 @@ Service principals exist in Microsoft Entra ID to define what apps can do, who c
 
 For more information, see [Application and service principal objects in Microsoft Entra ID](https://learn.microsoft.com/entra/identity-platform/app-objects-and-service-principals).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SettingOverride.md b/exchange/exchange-ps/ExchangePowerShell/Get-SettingOverride.md
index 2fb293f518..3a53168c56 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SettingOverride.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-SettingOverride.md
@@ -32,7 +32,7 @@ Get-SettingOverride [[-Identity] <SettingOverrideIdParameter>]
 ## DESCRIPTION
 Setting overrides configure and store Exchange server customizations in Active Directory. The settings can be organization-wide or server-specific, and they persist in Active Directory across Exchange Cumulative Updates (CUs). Exchange customizations in web.config or exe.config XML application configuration files are server-specific, and are lost when you install the next Exchange CU.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SharingPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-SharingPolicy.md
index 928a905807..8f7acb12f7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SharingPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-SharingPolicy.md
@@ -13,7 +13,7 @@ title: Get-SharingPolicy
 # Get-SharingPolicy
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-SharingPolicy cmdlet to view existing sharing policies that control how users inside your organization can share free/busy and contact information with users outside your organization.
 
@@ -28,9 +28,9 @@ Get-SharingPolicy [[-Identity] <SharingPolicyIdParameter>]
 ```
 
 ## DESCRIPTION
-Users can only share free/busy and contact information after federation has been configured between Exchange organizations. After that, users can send sharing invitations to the external recipients as long as those invitations comply with the sharing policy. A sharing policy needs to be assigned to a mailbox to be effective. If a mailbox doesn't have a specific sharing policy assigned, a default policy enforces the sharing settings for the mailbox.
+Users can only share free/busy and contact information after federation is configured between Exchange organizations. After that, users can send sharing invitations to the external recipients as long as those invitations comply with the sharing policy. A sharing policy needs to be assigned to a mailbox to be effective. If a mailbox doesn't have a specific sharing policy assigned, a default policy enforces the sharing settings for the mailbox.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SiteMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Get-SiteMailbox.md
index 1953f1a4b1..72d4c05408 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SiteMailbox.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-SiteMailbox.md
@@ -15,7 +15,7 @@ title: Get-SiteMailbox
 ## SYNOPSIS
 This cmdlet is available only in on-premises Exchange.
 
-Use the Get-SiteMailbox cmdlet to view information about site mailboxes. This cmdlet is primarily used by Microsoft SharePoint and Exchange to display information to users in the user interface. However, you may find it helpful for discovering information such as the site mailbox's owners, members, and lifecycle status.
+Use the Get-SiteMailbox cmdlet to view information about site mailboxes. This cmdlet is primarily used by Microsoft SharePoint and Exchange to display information to users in the user interface. However, you mightht find it helpful for discovering information such as the site mailbox's owners, members, and lifecycle status.
 
 Site mailboxes were deprecated in Exchange Online and SharePoint Online in 2017. For more information, see [Deprecation of Site Mailboxes](https://techcommunity.microsoft.com/t5/microsoft-sharepoint-blog/deprecation-of-site-mailboxes/ba-p/93028).
 
@@ -37,7 +37,7 @@ Get-SiteMailbox [[-Identity] <RecipientIdParameter>]
 ## DESCRIPTION
 If you aren't a member or owner of the site mailbox that you want to view the diagnostics information for, you must use the BypassOwnerCheck parameter when running this cmdlet. If you aren't a member or owner of the site mailbox and you run this cmdlet without using the BypassOwnerCheck parameter, the command fails with an "object not found" error.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -139,7 +139,7 @@ Accept wildcard characters: False
 
 The DeletedSiteMailbox switch returns site mailboxes that have been marked for pending deletion. You don't need to specify a value with this switch.
 
-When the lifecycle application in SharePoint closes a site mailbox, the site mailbox is retained for the period specified in the lifecycle policy in the closed state. The mailbox can then be reactivated by an end user or by a SharePoint administrator. After the retention period, the Exchange site mailbox that's housed in the mailbox database will have its name prepended with MDEL: to indicate that it has been marked for deletion. To free storage space and the alias, use the Remove-Mailbox cmdlet to manually remove these site mailboxes from the mailbox database.
+When the lifecycle application in SharePoint closes a site mailbox, the site mailbox is retained for the period specified in the lifecycle policy in the closed state. The mailbox can then be reactivated by an end user or by a SharePoint administrator. After the retention period, the name of the Exchange site mailbox housed in the mailbox database is prepended with `MDEL:` to indicate it's marked for deletion. To free storage space and the alias, use the Remove-Mailbox cmdlet to manually remove these site mailboxes from the mailbox database.
 
 ```yaml
 Type: SwitchParameter
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SiteMailboxDiagnostics.md b/exchange/exchange-ps/ExchangePowerShell/Get-SiteMailboxDiagnostics.md
index e868fb6ee1..89878ddd9b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SiteMailboxDiagnostics.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-SiteMailboxDiagnostics.md
@@ -35,7 +35,7 @@ Get-SiteMailboxDiagnostics [-Identity] <RecipientIdParameter>
 ## DESCRIPTION
 If you aren't a member or owner of the site mailbox that you want to view the diagnostics information for, you must use the BypassOwnerCheck parameter when running this cmdlet. If you aren't a member or owner of the site mailbox and you run this cmdlet without using the BypassOwnerCheck parameter, the command fails with an "object not found" error.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SiteMailboxProvisioningPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-SiteMailboxProvisioningPolicy.md
index 91b294c205..aa2e7109d2 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SiteMailboxProvisioningPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-SiteMailboxProvisioningPolicy.md
@@ -32,7 +32,7 @@ Get-SiteMailboxProvisioningPolicy [[-Identity] <MailboxPolicyIdParameter>]
 ## DESCRIPTION
 Site mailboxes allow access to both Microsoft SharePoint documents and Exchange email using the same client interface. Site mailbox provisioning policies apply settings to new site mailboxes that you create. You can create multiple site mailbox provisioning policies, but only the default policy is followed when users create site mailboxes. The default site mailbox provisioning policy is named Default.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SmimeConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-SmimeConfig.md
index cdd857bd7f..248d152e27 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SmimeConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-SmimeConfig.md
@@ -13,7 +13,7 @@ title: Get-SmimeConfig
 # Get-SmimeConfig
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-SmimeConfig cmdlet to view the S/MIME configuration for Outlook on the web (formerly known as Outlook Web App).
 
@@ -27,7 +27,7 @@ Get-SmimeConfig [[-Identity] <OrganizationIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SmtpDaneInboundStatus.md b/exchange/exchange-ps/ExchangePowerShell/Get-SmtpDaneInboundStatus.md
index 7c93c5cd2b..68031aabf0 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SmtpDaneInboundStatus.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-SmtpDaneInboundStatus.md
@@ -28,7 +28,7 @@ Get-SmtpDaneInboundStatus [-DomainName] <String> [<CommonParameters>]
 ## DESCRIPTION
 For more information about debugging, enabling, and disabling SMTP DANE with DNSSEC, see [How SMTP DANE works](https://learn.microsoft.com/purview/how-smtp-dane-works).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SpoofIntelligenceInsight.md b/exchange/exchange-ps/ExchangePowerShell/Get-SpoofIntelligenceInsight.md
index 351bcb4516..424b908c26 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SpoofIntelligenceInsight.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-SpoofIntelligenceInsight.md
@@ -35,7 +35,7 @@ The Get-SpoofIntelligenceInsight cmdlet returns the following information:
 - SpoofType: Indicates whether the domain is internal to your organization or external.
 - Action: The two possible values are Allow (messages that contain any spoofed sender email addresses in your organization are allowed from the source email server), and Block (messages that contain any spoofed sender email addresses in your organization are not allowed from the source email server).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SpoofMailReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-SpoofMailReport.md
index 30898b8ba5..404128c301 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SpoofMailReport.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-SpoofMailReport.md
@@ -41,7 +41,7 @@ The Get-SpoofMailReport cmdlet returns the following information:
 - Direction: This value is Inbound.
 - Domain: The sender domain. This corresponds to one of your organization's accepted domains.
 - Spoofed User: The sending email address if the domain is one of your organization's domains, or the sending domain if the domain is external.
-- True Sender: The organizational domain of the PTR record, or pointer record, of the sending IP address, also known as the reverse DNS address. If the sending IP address does not have a PTR record, this field will be blank and the Sender IP column will be filled in. Both columns will not be filled in at the same time.
+- True Sender: The organizational domain of the PTR record, or pointer record, of the sending IP address, also known as the reverse DNS address. If the sending IP address does not have a PTR record, this field is blank and the Sender IP column is filled in. Both columns aren't filled in at the same time.
 - Sending Infrastructure: The true sending domain that's found in the DNS record of the source email server. If no domain is found, the source email server's IP address is shown.
 - Count: The number of spoofed messages that were sent to your organization from the source messaging server during the specified time period.
 - Spoof Type: The relationship between the sender and recipient domain of the spoof mail. If both belong to same domain (including subdomains) or domain owned by the same organization, then Spoof Type is intra-org or Internal. If both belong to different domains, then Spoof Type is cross-org or External.
@@ -52,7 +52,7 @@ The Get-SpoofMailReport cmdlet returns the following information:
 - DKIM
 - DMARC
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-StoreUsageStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-StoreUsageStatistics.md
index ecf022b35a..df48bbb8a6 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-StoreUsageStatistics.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-StoreUsageStatistics.md
@@ -51,7 +51,7 @@ Get-StoreUsageStatistics -Server <ServerIdParameter>
 ## DESCRIPTION
 The Microsoft Exchange Information Store collects per-user information on latency, input/output (I/O), page counts, processor usage, and TimeInServer. The TimeInServer metric represents the total time that synchronous and asynchronous requests spend in the Microsoft Exchange Information Store for a user's mailbox. You can retrieve this resource information in the Microsoft Exchange Information Store for the 25 highest usage accounts on a specified database. Usage of a mailbox is defined as the amount of server time spent in performing operations for that mailbox. The cmdlet reports the top 25 users for every one-minute period for the last 10 minutes (250 objects per ten-minute interval). The resource usage is an indicator of the load that different users are placing on the server.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SupervisoryReviewActivity.md b/exchange/exchange-ps/ExchangePowerShell/Get-SupervisoryReviewActivity.md
index 71f674f883..a8f88c2678 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SupervisoryReviewActivity.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-SupervisoryReviewActivity.md
@@ -15,7 +15,7 @@ title: Get-SupervisoryReviewActivity
 ## SYNOPSIS
 This cmdlet is available only in the cloud-based service.
 
-Use the Get-SupervisoryReviewActivity cmdlet to view all activities performed by a reviewer for a specific supervision policy. This information may be useful if reviewer activities are required in regulatory compliance audits or in litigation.
+Use the Get-SupervisoryReviewActivity cmdlet to view all activities performed by a reviewer for a specific supervision policy. This information might be useful if reviewer activities are required in regulatory compliance audits or in litigation.
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
@@ -27,7 +27,7 @@ Get-SupervisoryReviewActivity -EndDate <ExDateTime> -PolicyId <String> -StartDat
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SweepRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-SweepRule.md
index 4a56442e92..55817a5d14 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SweepRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-SweepRule.md
@@ -13,7 +13,7 @@ title: Get-SweepRule
 # Get-SweepRule
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-SweepRule cmdlet to view Sweep rules in mailboxes. Sweep rules run at regular intervals to help keep your Inbox clean.
 
@@ -32,7 +32,7 @@ Get-SweepRule [[-Identity] <SweepRuleIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SystemMessage.md b/exchange/exchange-ps/ExchangePowerShell/Get-SystemMessage.md
index 86e3e2f970..f04bf393c2 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SystemMessage.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-SystemMessage.md
@@ -38,7 +38,7 @@ Get-SystemMessage [-Original]
 ## DESCRIPTION
 NDRs are issued to the senders of email messages that haven't reached their intended recipients. Quota messages are issued to users whose mailboxes or public folders have reached the specific warning, prohibit send, or prohibit receive quotas. Custom NDRs and quota messages replace the default messages that are included with Exchange.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -70,7 +70,7 @@ Get-SystemMessage -Original | Select-Object -Property Identity,DsnCode,Language,
 
 This example outputs the list of all default system messages in all languages to an HTML file named C:\\My Documents\\Default System Messages.html.
 
-You should output the list to a file, because the list is very long, and you'll receive errors if you don't have the required language packs installed.
+You should output the list to a file, because the list is very long, and you get errors if you don't have the required language packs installed.
 
 ## PARAMETERS
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-TeamsProtectionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-TeamsProtectionPolicy.md
index b7738fa384..eb40e3fa30 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-TeamsProtectionPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-TeamsProtectionPolicy.md
@@ -27,7 +27,7 @@ Get-TeamsProtectionPolicy [[-Identity] <TeamsProtectionPolicyIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-TeamsProtectionPolicyRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-TeamsProtectionPolicyRule.md
index ce99649cfb..25bfac1144 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-TeamsProtectionPolicyRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-TeamsProtectionPolicyRule.md
@@ -28,7 +28,7 @@ Get-TeamsProtectionPolicyRule [[-Identity] <RuleIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-TenantAllowBlockListItems.md b/exchange/exchange-ps/ExchangePowerShell/Get-TenantAllowBlockListItems.md
index 2281e8eb73..cf8b01b151 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-TenantAllowBlockListItems.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-TenantAllowBlockListItems.md
@@ -44,7 +44,7 @@ Get-TenantAllowBlockListItems -ListType <ListType> [-NoExpiration]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -203,7 +203,7 @@ Accept wildcard characters: False
 The ListSubType parameter filters the results by subtype. Valid values are:
 
 - AdvancedDelivery
-- Tenant: This is the default value.
+- Tenant: This value is the default.
 
 ```yaml
 Type: ListSubType[]
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-TenantAllowBlockListSpoofItems.md b/exchange/exchange-ps/ExchangePowerShell/Get-TenantAllowBlockListSpoofItems.md
index 4a6937ad9f..ce29b5cd5d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-TenantAllowBlockListSpoofItems.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-TenantAllowBlockListSpoofItems.md
@@ -31,13 +31,13 @@ Get-TenantAllowBlockListSpoofItems [[-Identity] <HostedConnectionFilterPolicyIdP
 ## DESCRIPTION
 The Get-TenantAllowBlockListSpoofItems cmdlet returns the following information:
 
-- Identity: A random Guid assigned to the spoof pair. This will be used as an **Id parameter** while updating or deleting the spoof pair using **Set-TenantAllowBlockListSpoofItems** and **Remove-TenantAllowBlockListSpoofItems**.
+- Identity: A random Guid assigned to the spoof pair. This value is used as an **Id parameter** while updating or deleting the spoof pair using **Set-TenantAllowBlockListSpoofItems** and **Remove-TenantAllowBlockListSpoofItems**.
 - SpoofedUser: The sending email address if the domain is one of your organization's domains or the sending domain if the domain is external.
 - SendingInfrastructure: The true sending domain that's found in the DNS record of the source email server. If no domain is found, the source email server's IP address is shown.
 - SpoofType: Indicates whether the domain is internal to your organization or external.
 - Action: The two possible values are Allow (messages that contain any spoofed sender email addresses in your organization are allowed from the source email server) or Block (messages that contain any spoofed sender email addresses in your organization are not allowed from the source email server).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-TextMessagingAccount.md b/exchange/exchange-ps/ExchangePowerShell/Get-TextMessagingAccount.md
index 6d7d0bf508..929df3f676 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-TextMessagingAccount.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-TextMessagingAccount.md
@@ -13,7 +13,7 @@ title: Get-TextMessagingAccount
 # Get-TextMessagingAccount
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-TextMessagingAccount cmdlet to view the text notification settings on mailboxes.
 
@@ -33,7 +33,7 @@ Get-TextMessagingAccount [-Identity] <MailboxIdParameter>
 ## DESCRIPTION
 When text messaging notifications are enabled on a mailbox, you can configure calendar notifications, voice mail notifications, and email notifications using an inbox rule.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ThrottlingPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-ThrottlingPolicy.md
index f3cb66dd00..43844b9234 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ThrottlingPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ThrottlingPolicy.md
@@ -35,7 +35,7 @@ The Get-ThrottlingPolicy cmdlet returns the client throttling settings for one o
 
 For more information about how to control the resources consumed by individual users, see [User workload management in Exchange Server](https://learn.microsoft.com/Exchange/server-health/workload-management).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ThrottlingPolicyAssociation.md b/exchange/exchange-ps/ExchangePowerShell/Get-ThrottlingPolicyAssociation.md
index 77d4935205..8ba0ee4aea 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ThrottlingPolicyAssociation.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ThrottlingPolicyAssociation.md
@@ -44,7 +44,7 @@ Get-ThrottlingPolicyAssociation [[-Identity] <ThrottlingPolicyAssociationIdParam
 ## DESCRIPTION
 For more information about how to control the resources consumed by individual users, see [User workload management in Exchange Server](https://learn.microsoft.com/Exchange/server-health/workload-management).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-TransportAgent.md b/exchange/exchange-ps/ExchangePowerShell/Get-TransportAgent.md
index 82e2fe42d4..1be1f2f60b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-TransportAgent.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-TransportAgent.md
@@ -29,7 +29,7 @@ Get-TransportAgent [[-Identity] <TransportAgentObjectId>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-TransportConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-TransportConfig.md
index 02598b341e..ffef43d5a4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-TransportConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-TransportConfig.md
@@ -13,7 +13,7 @@ title: Get-TransportConfig
 # Get-TransportConfig
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-TransportConfig cmdlet to view organization-wide transport configuration settings.
 
@@ -30,7 +30,7 @@ Get-TransportConfig [[-Identity] <OrganizationIdParameter>]
 ## DESCRIPTION
 The Get-TransportConfig cmdlet displays configuration information for global transport settings applied across the organization when the cmdlet is run on a Mailbox server. When this cmdlet is run on an Edge Transport server, only the transportation configuration settings for the local computer are shown.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-TransportPipeline.md b/exchange/exchange-ps/ExchangePowerShell/Get-TransportPipeline.md
index f475a86fd2..31d4c51174 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-TransportPipeline.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-TransportPipeline.md
@@ -35,7 +35,7 @@ The Get-TransportPipeline cmdlet enables you to view all the transport agents th
 
 The associated transport service must be started and at least one email message must be sent through the server since the last service restart before the transport pipeline can be viewed. Only the transport events and agents that were involved in the processing of email messages since the associated service was last started are returned.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-TransportRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-TransportRule.md
index f0b41ab022..00a45e85c7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-TransportRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-TransportRule.md
@@ -13,7 +13,7 @@ title: Get-TransportRule
 # Get-TransportRule
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-TransportRule cmdlet to view transport rules (mail flow rules) in your organization.
 
@@ -35,7 +35,7 @@ Get-TransportRule [[-Identity] <RuleIdParameter>]
 ## DESCRIPTION
 On Mailbox servers, this cmdlet returns all rules in the Exchange organization that are stored in Active Directory. On an Edge Transport server, this cmdlet only returns rules that are configured on the local server.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -169,7 +169,7 @@ This parameter is available only in the cloud-based service.
 The ExcludeConditionActionDetails parameter specifies whether to hide specific details from the results. Valid values are:
 
 - $true: The Description, Conditions, and Actions properties, as well as any configured condition, exception and action property values are blank.
-- $false: No properties or property values are hidden. This is the default value.
+- $false: No properties or property values are hidden. This value is the default.
 
 ```yaml
 Type: Boolean
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-TransportRuleAction.md b/exchange/exchange-ps/ExchangePowerShell/Get-TransportRuleAction.md
index 356cfd7f34..5d266e9ba2 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-TransportRuleAction.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-TransportRuleAction.md
@@ -13,7 +13,7 @@ title: Get-TransportRuleAction
 # Get-TransportRuleAction
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-TransportRuleAction cmdlet to view the actions that are available for transport rules (mail flow rules).
 
@@ -29,7 +29,7 @@ Get-TransportRuleAction [[-Name] <String>]
 ## DESCRIPTION
 In on-premises Exchange, the actions that are available on Mailboxes servers and Edge Transports server are different. Also, the names of some of the actions that are returned by this cmdlet are different than the corresponding parameter names in the New-TransportRule and Set-TransportRule cmdlets.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-TransportRulePredicate.md b/exchange/exchange-ps/ExchangePowerShell/Get-TransportRulePredicate.md
index 002d434fe7..0a039b0a93 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-TransportRulePredicate.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-TransportRulePredicate.md
@@ -13,7 +13,7 @@ title: Get-TransportRulePredicate
 # Get-TransportRulePredicate
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-TransportRulePredicate cmdlet to view the predicates (conditions and exceptions) that are available for transport rules (mal flow rules).
 
@@ -31,7 +31,7 @@ Collectively, the conditions and exceptions in rules are known as predicates, be
 
 In on-premises Exchange, the predicates that are available on Mailboxes servers and Edge Transports server are different.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-TransportServer.md b/exchange/exchange-ps/ExchangePowerShell/Get-TransportServer.md
index be4676662a..c4e3d2faa6 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-TransportServer.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-TransportServer.md
@@ -30,7 +30,7 @@ Get-TransportServer [[-Identity] <TransportServerIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-TransportService.md b/exchange/exchange-ps/ExchangePowerShell/Get-TransportService.md
index a7da169a33..2f68807ab2 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-TransportService.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-TransportService.md
@@ -28,7 +28,7 @@ Get-TransportService [[-Identity] <TransportServerIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-Trust.md b/exchange/exchange-ps/ExchangePowerShell/Get-Trust.md
index 035a77f9d4..a188003b37 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-Trust.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-Trust.md
@@ -29,7 +29,7 @@ Get-Trust [-DomainName <Fqdn>]
 ## DESCRIPTION
 The Get-Trust cmdlet is used by the Exchange admin center in to populate fields that display recipient information.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-UMActiveCalls.md b/exchange/exchange-ps/ExchangePowerShell/Get-UMActiveCalls.md
index 291c7a984f..3b5c18f829 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-UMActiveCalls.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-UMActiveCalls.md
@@ -56,7 +56,7 @@ When a Mailbox server is process cycling, the Get-UMActiveCalls cmdlet doesn't r
 
 After this task is completed, you can see the list of active calls being processed by a Mailbox server.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-UMAutoAttendant.md b/exchange/exchange-ps/ExchangePowerShell/Get-UMAutoAttendant.md
index f8dd5e3588..573e07b1cb 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-UMAutoAttendant.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-UMAutoAttendant.md
@@ -33,7 +33,7 @@ The Get-UMAutoAttendant cmdlet retrieves the properties for a single UM auto att
 
 After this task is completed, if no parameter is supplied with the cmdlet, the cmdlet returns all UM auto attendants in the Active Directory forest. Or, if the UM dial plan ID is supplied but no name is supplied, the cmdlet returns all UM auto attendants linked to the UM dial plan.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-UMCallAnsweringRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-UMCallAnsweringRule.md
index 0c79f7fbfd..bc5e76e829 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-UMCallAnsweringRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-UMCallAnsweringRule.md
@@ -15,7 +15,7 @@ title: Get-UMCallAnsweringRule
 ## SYNOPSIS
 This cmdlet is available only in on-premises Exchange.
 
-Use the Get-UMCallAnsweringRule cmdlet to view the properties of a Unified Messaging (UM) call answering rule that has been created within a UM-enabled mailbox.
+Use the Get-UMCallAnsweringRule cmdlet to view the properties of a Unified Messaging (UM) call answering rule that is created within a UM-enabled mailbox.
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
@@ -29,11 +29,11 @@ Get-UMCallAnsweringRule [[-Identity] <UMCallAnsweringRuleIdParameter>]
 ```
 
 ## DESCRIPTION
-The Get-UMCallAnsweringRule cmdlet enables you to view the properties of a call answering rule that has been created in a UM-enabled user's mailbox. It allows you to retrieve the properties for a single call answering rule or a list of call answering rules in a UM-enabled user's mailbox.
+The Get-UMCallAnsweringRule cmdlet enables you to view the properties of a call answering rule that is created in a UM-enabled user's mailbox. It allows you to retrieve the properties for a single call answering rule or a list of call answering rules in a UM-enabled user's mailbox.
 
 After this task is completed, the cmdlet returns the parameters and the values specified.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-UMCallDataRecord.md b/exchange/exchange-ps/ExchangePowerShell/Get-UMCallDataRecord.md
index ff1aaeaeeb..194e7797f1 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-UMCallDataRecord.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-UMCallDataRecord.md
@@ -31,7 +31,7 @@ Get-UMCallDataRecord -Mailbox <MailboxIdParameter>
 The Get-UMCallDataRecord cmdlet displays UM call data records for the last 90 days for a UM-enabled mailbox that you specify. Each UM call data record provides detailed information about all calls either placed to or received by the specified user. The following list details each of the properties that are returned:
 
 - Date: Date and time of the Mailbox server running the Microsoft Exchange Unified Messaging service that took the call in the Coordinated Universal Time (UTC) format.
-- Duration: Total duration of this call. For Find Me calls, this will always be zero because the call is being transferred and won't be handled by Unified Messaging any longer.
+- Duration: Total duration of this call. For Find Me calls, this value is always zero because the call is being transferred and is no longer handled by Unified Messaging.
 - AudioCodec: Audio codec used for the call including G.711 or Group System Mobile (GSM).
 - DialPlan: Name of the UM dial plan handling the call.
 - CallType: Type of the call (localized in the user's language): Call Answering Voice Message, Call Answering Missed Call, , Auto Attendant, Subscriber Access, Fax, PlayOnPhone, Find Me, None, UnauthenticatedPilotNumber, or PromptProvisioning.
@@ -45,7 +45,7 @@ The Get-UMCallDataRecord cmdlet displays UM call data records for the last 90 da
 - RoundTripMilliseconds: Round trip time for Real Time Control Protocol (RTCP) statistics in milliseconds.
 - BurstLossDurationMilliseconds: Average duration of packet loss during bursts during the call.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-UMCallRouterSettings.md b/exchange/exchange-ps/ExchangePowerShell/Get-UMCallRouterSettings.md
index 45deb8cca3..52e4f24797 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-UMCallRouterSettings.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-UMCallRouterSettings.md
@@ -30,7 +30,7 @@ Get-UMCallRouterSettings [[-Server] <ServerIdParameter>]
 ## DESCRIPTION
 When the cmdlet is used for a single server, it returns the UM call router properties including MaxCalls, MaxFaxCalls and UMDialPlans. The properties and their values are stored in the Unified Messaging section of the Microsoft Exchange configuration object in Active Directory.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-UMCallSummaryReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-UMCallSummaryReport.md
index c37b790bbe..07ada2f752 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-UMCallSummaryReport.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-UMCallSummaryReport.md
@@ -52,7 +52,7 @@ The Get-UMCallSummaryReport cmdlet displays the aggregated statistics about all
 - Burst loss Duration: Average duration of packet loss during bursts of losses for the selected UM dial plan or UM IP gateway.
 - Number of samples: Number of calls sampled, when calculating the averages. A sample refers to any call data record that contains at least one of the audio quality metrics.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -148,7 +148,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
 
-The UMIPGateway parameter specifies the UM IP gateway to show statistics for. If you don't specify a UM IP gateway, statistics are included for all UM IP gateways for a selected dial plan, or, if no dial plan is selected, results will be returned for all UM IP gateways in the organization.
+The UMIPGateway parameter specifies the UM IP gateway to show statistics for. If you don't specify a UM IP gateway, statistics are included for all UM IP gateways for a selected dial plan, or, if no dial plan is selected, results are returned for all UM IP gateways in the organization.
 
 ```yaml
 Type: UMIPGatewayIdParameter
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-UMDialPlan.md b/exchange/exchange-ps/ExchangePowerShell/Get-UMDialPlan.md
index dbac8b385c..c81063f4c2 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-UMDialPlan.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-UMDialPlan.md
@@ -32,7 +32,7 @@ The Get-UMDialPlan cmdlet displays all properties for a UM dial plan.
 
 After this task is completed, when you specify the Identity parameter, you can view the values set. When the Get-UMDialPlan cmdlet is run, if no parameter is supplied, the cmdlet returns all UM dial plans in the Active Directory forest.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-UMHuntGroup.md b/exchange/exchange-ps/ExchangePowerShell/Get-UMHuntGroup.md
index 2c4eae3937..825cf9cf9b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-UMHuntGroup.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-UMHuntGroup.md
@@ -33,7 +33,7 @@ The Get-UMHuntGroup cmdlet retrieves the properties for a single UM hunt group o
 
 After this task is completed, if the Identity parameter is specified, the properties for the UM hunt group are returned. If neither the Identity nor the UMDialPlan parameter is specified, all UM hunt groups in the Active Directory forest are returned.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-UMIPGateway.md b/exchange/exchange-ps/ExchangePowerShell/Get-UMIPGateway.md
index a34b158d04..5efbaf5ed9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-UMIPGateway.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-UMIPGateway.md
@@ -35,7 +35,7 @@ When you're using the Get-UMIPGateway cmdlet, you can't enter the IP address con
 
 After this task is completed, you can view the list of properties and values for a specific UM IP gateway. Or, if the Identity parameter isn't used, the cmdlet returns a list of all UM IP gateways in the forest.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-UMMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Get-UMMailbox.md
index b2de66ff19..67e9225252 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-UMMailbox.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-UMMailbox.md
@@ -50,7 +50,7 @@ Get-UMMailbox [[-Identity] <MailboxIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-UMMailboxPin.md b/exchange/exchange-ps/ExchangePowerShell/Get-UMMailboxPin.md
index 04ded39c11..ad7fbff753 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-UMMailboxPin.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-UMMailboxPin.md
@@ -33,11 +33,11 @@ Get-UMMailboxPin [[-Identity] <MailboxIdParameter>]
 ```
 
 ## DESCRIPTION
-The Get-UMMailboxPin cmdlet returns information calculated from the PIN data stored in encrypted form in the user's mailbox. This cmdlet also shows whether the mailbox or user access has been locked out.
+The Get-UMMailboxPIN cmdlet returns information calculated from the PIN data encrypted and stored in the user's mailbox. This cmdlet also shows whether the mailbox or user access is locked out.
 
 After this task is completed, you can view information on a user's mailbox.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-UMMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-UMMailboxPolicy.md
index 6bb94bc162..17e4fcbc3d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-UMMailboxPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-UMMailboxPolicy.md
@@ -33,7 +33,7 @@ The Get-UMMailboxPolicy cmdlet retrieves the configuration properties and values
 
 After this task is completed, if the Identity parameter is supplied, the properties and values for the specified UM mailbox policy object are returned. If no parameter is specified at the command prompt, all UM mailbox policies in the Active Directory forest are returned.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-UMServer.md b/exchange/exchange-ps/ExchangePowerShell/Get-UMServer.md
index eeb14f3928..416a8f2674 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-UMServer.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-UMServer.md
@@ -34,7 +34,7 @@ The ExchangeVersion attribute that's returned is the minimum version of Microsof
 
 After this task is completed, you can view the parameters and values for a single Unified Messaging server or a list of all of the Unified Messaging servers in Active Directory.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-UMService.md b/exchange/exchange-ps/ExchangePowerShell/Get-UMService.md
index 1baf293205..9089d7734c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-UMService.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-UMService.md
@@ -32,7 +32,7 @@ When the cmdlet is used for a single Exchange server, it returns the Unified Mes
 
 The ExchangeVersion attribute that's returned is the minimum version of Exchange you can use to manage the returned object. This attribute isn't the same as the version of Exchange that's displayed in the Exchange admin center when you select Server Configuration.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-UnifiedGroup.md b/exchange/exchange-ps/ExchangePowerShell/Get-UnifiedGroup.md
index 0673369181..a6d99d02f5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-UnifiedGroup.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-UnifiedGroup.md
@@ -56,7 +56,7 @@ Get-UnifiedGroup [-Anr <String>]
 ## DESCRIPTION
 Microsoft 365 Groups are group objects that are available across Microsoft 365 services.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-UnifiedGroupLinks.md b/exchange/exchange-ps/ExchangePowerShell/Get-UnifiedGroupLinks.md
index daf58d4d2b..889457c6de 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-UnifiedGroupLinks.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-UnifiedGroupLinks.md
@@ -30,7 +30,7 @@ Get-UnifiedGroupLinks [-Identity] <UnifiedGroupIdParameter> -LinkType <LinkType>
 ## DESCRIPTION
 Microsoft 365 Groups are group objects that are available across Microsoft 365 services.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-User.md b/exchange/exchange-ps/ExchangePowerShell/Get-User.md
index e2d12cf058..1c78f20404 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-User.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-User.md
@@ -13,7 +13,7 @@ title: Get-User
 # Get-User
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Get-User cmdlet to view existing user objects in your organization. This cmdlet returns all objects that have user accounts (for example, user mailboxes, mail users, and user accounts).
 
@@ -68,7 +68,7 @@ Get-User [[-Identity] <UserIdParameter>]
 ## DESCRIPTION
 The Get-User cmdlet returns no mail-related properties for mailboxes or mail users. To view the mail-related properties for a user, you need to use the corresponding cmdlet based on the object type (for example, Get-Mailbox or Get-MailUser).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-UserPhoto.md b/exchange/exchange-ps/ExchangePowerShell/Get-UserPhoto.md
index 5112382af9..fe70eb0bcf 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-UserPhoto.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-UserPhoto.md
@@ -60,7 +60,7 @@ Get-UserPhoto [[-Identity] <MailboxIdParameter>]
 ## DESCRIPTION
 The user photos feature allows users to associate a picture with their account. User photos are stored in the user's Active Directory account and in the root directory of the user's Exchange mailbox. The user photo feature must be set for a user before you can run the Get-UserPhoto cmdlet to view information about the user's photo. Otherwise, you get an error message saying the user photo doesn't exist for the specified users. Administrators use the Set-UserPhoto cmdlet or the Exchange admin center (EAC) to configure user photos. Users can upload, preview, and save a user photo to their account by using the Outlook on the web Options page.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-UserPrincipalNamesSuffix.md b/exchange/exchange-ps/ExchangePowerShell/Get-UserPrincipalNamesSuffix.md
index 47c8e975ea..a33308cebd 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-UserPrincipalNamesSuffix.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-UserPrincipalNamesSuffix.md
@@ -33,7 +33,7 @@ The default UPN is contained in the Canonical Name attribute on the Partitions c
 
 If you create user accounts by using Active Directory Users and Computers, every user must have a UPN.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-WebServicesVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Get-WebServicesVirtualDirectory.md
index bfc03e42ee..da0f74a7e0 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-WebServicesVirtualDirectory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-WebServicesVirtualDirectory.md
@@ -44,7 +44,7 @@ The Get-WebServicesVirtualDirectory cmdlet can be run on a local server or run r
 
 The Get-WebServicesVirtualDirectory cmdlet can be run on any server that has the Exchange administration tools installed.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 

From dec58c0794b78e2f90720ebdef1a1c5add081fb2 Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Wed, 6 Aug 2025 08:53:03 -0700
Subject: [PATCH 094/145] Update New-CsCallQueue.md

---
 teams/teams-ps/MicrosoftTeams/New-CsCallQueue.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/teams/teams-ps/MicrosoftTeams/New-CsCallQueue.md b/teams/teams-ps/MicrosoftTeams/New-CsCallQueue.md
index d5edf96b3a..662d585a39 100644
--- a/teams/teams-ps/MicrosoftTeams/New-CsCallQueue.md
+++ b/teams/teams-ps/MicrosoftTeams/New-CsCallQueue.md
@@ -14,7 +14,9 @@ title: New-CsCallQueue
 # New-CsCallQueue
 
 ## SYNOPSIS
-Creates new Call Queue in your Skype for Business Online organization.
+Creates new Call Queue in your Teams organization.
+
+Line to start changes.
 
 ## SYNTAX
 

From 74c170a9fac3944e2987f95ac7b9ed39fdafbd72 Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Wed, 6 Aug 2025 08:54:41 -0700
Subject: [PATCH 095/145] Create Set-CsPersonalAttendantSettings.md

---
 .../Set-CsPersonalAttendantSettings.md        | 334 ++++++++++++++++++
 1 file changed, 334 insertions(+)
 create mode 100644 teams/teams-ps/MicrosoftTeams/Set-CsPersonalAttendantSettings.md

diff --git a/teams/teams-ps/MicrosoftTeams/Set-CsPersonalAttendantSettings.md b/teams/teams-ps/MicrosoftTeams/Set-CsPersonalAttendantSettings.md
new file mode 100644
index 0000000000..7d85cffd03
--- /dev/null
+++ b/teams/teams-ps/MicrosoftTeams/Set-CsPersonalAttendantSettings.md
@@ -0,0 +1,334 @@
+---
+applicable: Microsoft Teams
+author: juliiva
+external help file: Microsoft.Rtc.Management.dll-Help.xml
+Locale: en-US
+manager: jomarque
+Module Name: MicrosoftTeams
+ms.author: juliiva
+online version: https://learn.microsoft.com/powershell/module/microsoftteams/set-cspersonalattendantsettings
+schema: 2.0.0
+title: Set-CsPersonalAttendantSettings
+---
+
+# Set-CsPersonalAttendantSettings
+
+## SYNOPSIS
+
+**Limited Preview:** Functionality described in this document is currently in limited preview and only authorized organizations have access.
+
+This cmdlet will set personal attendant settings for the specified user.
+
+## SYNTAX
+
+```
+Set-CsPersonalAttendantSettings -Identity <String> -IsPersonalAttendantEnabled <Boolean> -DefaultLanguage <String> [-DefaultVoice <String>]  [-CalleeName <String>] [-DefaultTone <String>] -IsBookingCalendarEnabled <Boolean> [-IsNonContactCallbackEnabled <Boolean>] -IsCallScreeningEnabled <Boolean> -AllowInboundInternalCalls <Boolean> -AllowInboundFederatedCalls <Boolean> -AllowInboundPSTNCalls <Boolean>  -IsAutomaticTranscriptionEnabled <Boolean> -IsAutomaticRecordingEnabled <Boolean> [<CommonParameters>]
+```
+
+## DESCRIPTION
+
+This cmdlet sets personal attendant settings for the specified user.
+
+When specifying settings you need to specify all settings, for instance, you can't just turn call screening on. Instead, you need to
+start by getting the current settings, making the necessary changes, and then setting/writing all settings.
+
+## EXAMPLES
+
+### Example 1
+```
+Set-CsPersonalAttendantSettings -Identity user1@contoso.com -IsPersonalAttendantEnabled $true -DefaultLanguage en-US -CalleeName User1 -IsBookingCalendarEnabled $false -IsCallScreeningEnabled $false
+-AllowInboundInternalCalls $true -AllowInboundFederatedCalls $false -AllowInboundPSTNCalls $false -IsAutomaticTranscriptionEnabled $false -IsAutomaticRecordingEnabled $false
+```
+
+This example shows setting up personal attendant for user1@contoso.com. Personal attendant communicates in English. Personal attendant will refer to its owner as User1. 
+Personal attendant is only enabled for inbound Teams calls from the user's domain. Additional capabilities are turned off.
+
+### Example 2
+```
+Set-CsPersonalAttendantSettings -Identity user1@contoso.com -IsPersonalAttendantEnabled $true -DefaultLanguage en-US -CalleeName User1 -IsBookingCalendarEnabled $true -IsCallScreeningEnabled $false
+-AllowInboundInternalCalls $true -AllowInboundFederatedCalls $false -AllowInboundPSTNCalls $false -IsAutomaticTranscriptionEnabled $false -IsAutomaticRecordingEnabled $false
+```
+
+This example shows setting up personal attendant for user1@contoso.com. In addition to previously mentioned capabilities, personal attendant is able to access personal bookings calendar, 
+fetch the user's availability and schedule callbacks on behalf of the user. Calendar operations are enabled for all incoming callers. user1 must specify the bookings link in Teams Personal Attendant settings.
+
+### Example 3
+```
+Set-CsPersonalAttendantSettings -Identity user1@contoso.com -IsPersonalAttendantEnabled $true -DefaultLanguage en-US -CalleeName User1 -IsBookingCalendarEnabled $true -IsCallScreeningEnabled $false
+-AllowInboundInternalCalls $true -AllowInboundFederatedCalls $true -AllowInboundPSTNCalls $true -IsAutomaticTranscriptionEnabled $false -IsAutomaticRecordingEnabled $false
+```
+
+This example shows setting up personal attendant for user1@contoso.com. In addition to previously mentioned capabilities, personal attendant is enabled for all incoming calls: the user's domain, other domains and PSTN.
+
+### Example 4
+```
+Set-CsPersonalAttendantSettings -Identity user1@contoso.com -IsPersonalAttendantEnabled $true -DefaultLanguage en-US -CalleeName User1 -IsBookingCalendarEnabled $true -IsCallScreeningEnabled $true
+-AllowInboundInternalCalls $true -AllowInboundFederatedCalls $true -AllowInboundPSTNCalls $true -IsAutomaticTranscriptionEnabled $false -IsAutomaticRecordingEnabled $false
+```
+
+This example shows setting up personal attendant for user1@contoso.com. In addition to previously mentioned capabilities, personal attendant is enabled to evaluate the call's context and pass the info to the user.
+
+### Example 5
+```
+Set-CsPersonalAttendantSettings -Identity user1@contoso.com -IsPersonalAttendantEnabled $true -DefaultLanguage en-US -CalleeName User1 -IsBookingCalendarEnabled $true -IsCallScreeningEnabled $true
+-AllowInboundInternalCalls $true -AllowInboundFederatedCalls $true -AllowInboundPSTNCalls $true -IsAutomaticTranscriptionEnabled $true -IsAutomaticRecordingEnabled $true
+```
+
+This example shows setting up personal attendant for user1@contoso.com. In addition to previously mentioned capabilities, personal attendant is automatically storing call transcription and recording.
+
+### Example 6
+```
+Set-CsPersonalAttendantSettings -Identity user1@contoso.com -IsPersonalAttendantEnabled $false
+```
+
+This example shows turning off personal attendant for user1@contoso.com.
+
+### Example 7
+```
+Set-CsUserCallingSettings -Identity user1@contoso.com -IsForwardingEnabled $false
+Set-CsPersonalAttendantSettings -Identity user1@contoso.com -IsPersonalAttendantEnabled $true -DefaultLanguage en-US -CalleeName User1 -IsBookingCalendarEnabled $false -IsCallScreeningEnabled $false
+-AllowInboundInternalCalls $true -AllowInboundFederatedCalls $false -AllowInboundPSTNCalls $false -IsAutomaticTranscriptionEnabled $false -IsAutomaticRecordingEnabled $false
+```
+
+This example shows how to set up personal attendant for a user, who has call forwarding enabled.
+
+### Example 8
+```
+Set-CsUserCallingSettings -Identity user1@contoso.com -IsUnansweredEnabled $true -UnansweredTargetType Voicemail -UnansweredDelay 00:00:20
+Set-CsPersonalAttendantSettings -Identity user1@contoso.com -IsPersonalAttendantEnabled $true -DefaultLanguage en-US -CalleeName User1 -IsBookingCalendarEnabled $false -IsCallScreeningEnabled $false
+-AllowInboundInternalCalls $true -AllowInboundFederatedCalls $false -AllowInboundPSTNCalls $false -IsAutomaticTranscriptionEnabled $false -IsAutomaticRecordingEnabled $false
+```
+
+This example shows how to set up personal attendant for a user, who would like to use unanswered call functionality simultaniously with personal attendant.
+
+## PARAMETERS
+
+### -Identity
+The Identity of the user to set	personal attendant settings for. Can be specified using the ObjectId or the SIP address.
+
+```yaml
+Type: System.String
+Parameter Sets: (All)
+Aliases:
+
+Required: True
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -IsPersonalAttendantEnabled
+This parameter controls whether personal attendant is enabled or not. If personal attendant is enabled, then at least one of: AllowInboundInternalCalls, AllowInboundFederatedCalls, AllowInboundPSTNCalls must be enabled.
+
+```yaml
+Type: System.Boolean
+Parameter Sets: (PersonalAttendant,PersonalAttendantOnOff)
+Aliases:
+
+Required: True
+Default value: False
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -DefaultLanguage
+Language to be used by personal attendant in communication. The preliminary list of supported languages is:
+en-US, fr-FR, ar-SA, zh-CN, zh-TW, cs-CZ, da-DK, nl-NL, en-AU, en-GB, fi-FI, fr-CA, de-DE, el-GR, hi-IN, id-ID, it-IT, ja-JP, ko-KR, nb-NO, pl-PL, pt-BR, ru-RU, es-ES, es-US, sv-SE, th-TH, tr-TR
+
+```yaml
+Type: System.String
+Parameter Sets: (PersonalAttendant)
+Aliases:
+
+Required: True
+Default value: en-US
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -DefaultVoice
+Voice to be used by personal attendant in communication. Supported values are Female and Male.
+
+> [!NOTE]
+> This parameter is currently in development and changing it does not change the behavior of Personal Attendant.
+
+```yaml
+Type: System.String
+Parameter Sets: (PersonalAttendant)
+Aliases:
+
+Required: False
+Default value: Female
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -CalleeName
+Name that personal attendant uses when referring to its owner. 
+
+```yaml
+Type: System.String
+Parameter Sets: (PersonalAttendant)
+Aliases:
+
+Required: False
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -DefaultTone
+Tone to be used by personal attendant in communication. Supported values are Formal and Casual.
+
+> [!NOTE]
+> This parameter is currently in development and enabling/disabling it does not change the behavior of Personal Attendant.
+
+```yaml
+Type: System.String
+Parameter Sets: (PersonalAttendant)
+Aliases:
+
+Required: False
+Default value: Formal
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -IsBookingCalendarEnabled
+This parameter controls whether personal attendant can access personal bookings calendar to fetch the user's availability and schedule callbacks on behalf of the user.
+If access to personal calendar is enabled by admin, user must specify the bookings link in Teams Personal Attendant settings.
+
+```yaml
+Type: System.Boolean
+Parameter Sets: (PersonalAttendant)
+Aliases:
+
+Required: True
+Default value: False
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -IsNonContactCallbackEnabled
+This parameter controls whether personal attendant calendar operations for callers not in the user contact list are enabled or not.
+
+> [!NOTE]
+> This parameter is currently in development and enabling/disabling it does not change the behavior of Personal Attendant.
+
+```yaml
+Type: System.Boolean
+Parameter Sets: (PersonalAttendant)
+Aliases:
+
+Required: False
+Default value: False
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -IsCallScreeningEnabled
+This parameter controls whether personal attendant evaluates calls context and passes the info to the user.
+
+```yaml
+Type: System.Boolean
+Parameter Sets: (PersonalAttendant)
+Aliases:
+
+Required: True
+Default value: True
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -AllowInboundInternalCalls
+This parameter controls whether personal attendant for incoming domain calls is enabled or not.
+
+```yaml
+Type: System.Boolean
+Parameter Sets: (PersonalAttendant)
+Aliases:
+
+Required: True
+Default value: True
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -AllowInboundFederatedCalls
+This parameter controls whether personal attendant for incoming calls from other domains is enabled or not.
+
+```yaml
+Type: System.Boolean
+Parameter Sets: (PersonalAttendant)
+Aliases:
+
+Required: True
+Default value: True
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -AllowInboundPSTNCalls
+This parameter controls whether personal attendant for incoming PSTN calls is enabled or not.
+
+```yaml
+Type: System.Boolean
+Parameter Sets: (PersonalAttendant)
+Aliases:
+
+Required: True
+Default value: True
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -IsAutomaticTranscriptionEnabled
+This parameter controls whether automatic storing of transcriptions (of personal attendant calls) is enabled or not.
+
+```yaml
+Type: System.Boolean
+Parameter Sets: (PersonalAttendant)
+Aliases:
+
+Required: True
+Default value: True
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -IsAutomaticRecordingEnabled
+This parameter controls whether automatic storing of recordings (of personal attendant calls) is enabled or not.
+
+```yaml
+Type: System.Boolean
+Parameter Sets: (PersonalAttendant)
+Aliases:
+
+Required: True
+Default value: True
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### CommonParameters
+This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).
+
+## INPUTS
+
+### None
+
+## OUTPUTS
+
+### System.Object
+
+## NOTES
+The cmdlet is available in Teams PowerShell module 7.3.0 or later.
+
+The specified user need to have the Microsoft Phone System license assigned.
+
+The cmdlet is validating different settings and is always writing all the parameters. You might see validation errors from the cmdlet due to
+this behavior. As an example, if you already have call forwarding set up and you want to set up personal attendant, you will get a validation error.
+
+
+## RELATED LINKS
+[Get-CsPersonalAttendantSettings](./get-cspersonalattendantsettings.md)

From 960aaddb6822cdd6324d4e5a13548117515ae6dd Mon Sep 17 00:00:00 2001
From: Chris Davis <chris.davis@microsoft.com>
Date: Wed, 6 Aug 2025 08:58:11 -0700
Subject: [PATCH 096/145] Acrolinx 9

---
 .../Get-X400AuthoritativeDomain.md            |  2 +-
 .../Import-DlpPolicyCollection.md             |  4 +-
 .../Import-DlpPolicyTemplate.md               |  2 +-
 .../Import-ExchangeCertificate.md             |  6 +-
 .../Import-JournalRuleCollection.md           |  2 +-
 .../Import-RecipientDataProperty.md           |  2 +-
 .../Import-TransportRuleCollection.md         |  2 +-
 .../ExchangePowerShell/Import-UMPrompt.md     |  4 +-
 .../Install-TransportAgent.md                 |  4 +-
 .../Invoke-ComplianceSearchActionStep.md      |  2 +-
 .../Invoke-MonitoringProbe.md                 | 14 +--
 .../ExchangePowerShell/Mount-Database.md      |  2 +-
 .../Move-ActiveMailboxDatabase.md             | 20 ++---
 .../ExchangePowerShell/Move-AddressList.md    |  2 +-
 .../ExchangePowerShell/Move-DatabasePath.md   |  2 +-
 .../Move-OfflineAddressBook.md                |  2 +-
 .../New-ATPBuiltInProtectionRule.md           |  2 +-
 .../New-ATPProtectionPolicyRule.md            |  8 +-
 .../ExchangePowerShell/New-AcceptedDomain.md  |  4 +-
 .../New-ActiveSyncDeviceAccessRule.md         |  4 +-
 .../New-ActiveSyncMailboxPolicy.md            |  6 +-
 .../New-ActiveSyncVirtualDirectory.md         | 10 +--
 .../New-AddressBookPolicy.md                  | 36 ++++++--
 .../ExchangePowerShell/New-AddressList.md     |  4 +-
 .../New-AdminAuditLogSearch.md                |  4 +-
 .../ExchangePowerShell/New-AntiPhishPolicy.md | 44 ++++-----
 .../ExchangePowerShell/New-AntiPhishRule.md   |  4 +-
 .../exchange-ps/ExchangePowerShell/New-App.md | 14 +--
 .../New-AppRetentionCompliancePolicy.md       |  6 +-
 .../New-AppRetentionComplianceRule.md         |  6 +-
 .../New-ApplicationAccessPolicy.md            |  6 +-
 .../ExchangePowerShell/New-AuthRedirect.md    |  2 +-
 .../ExchangePowerShell/New-AuthServer.md      | 10 ++-
 .../New-AuthenticationPolicy.md               |  4 +-
 .../New-AutoSensitivityLabelPolicy.md         |  8 +-
 .../New-AutoSensitivityLabelRule.md           | 10 +--
 .../New-AutodiscoverVirtualDirectory.md       | 20 ++---
 .../New-AvailabilityConfig.md                 |  2 +-
 .../New-AvailabilityReportOutage.md           |  2 +-
 .../ExchangePowerShell/New-CaseHoldPolicy.md  |  4 +-
 .../ExchangePowerShell/New-CaseHoldRule.md    |  2 +-
 .../New-ClassificationRuleCollection.md       |  4 +-
 .../New-ClientAccessArray.md                  |  2 +-
 .../New-ClientAccessRule.md                   |  6 +-
 .../ExchangePowerShell/New-ComplianceCase.md  |  2 +-
 .../New-ComplianceRetentionEvent.md           |  2 +-
 .../New-ComplianceSearch.md                   | 14 +--
 .../New-ComplianceSearchAction.md             | 18 ++--
 .../ExchangePowerShell/New-ComplianceTag.md   |  2 +-
 .../New-DataClassification.md                 |  4 +-
 .../New-DataEncryptionPolicy.md               |  4 +-
 .../New-DatabaseAvailabilityGroup.md          |  6 +-
 .../New-DatabaseAvailabilityGroupNetwork.md   |  2 +-
 .../New-DeliveryAgentConnector.md             |  2 +-
 .../New-DeviceConditionalAccessPolicy.md      |  2 +-
 .../New-DeviceConditionalAccessRule.md        | 90 +++++++++----------
 .../New-DeviceConfigurationPolicy.md          |  2 +-
 .../New-DeviceConfigurationRule.md            | 88 +++++++++---------
 .../New-DeviceTenantPolicy.md                 |  2 +-
 .../New-DistributionGroup.md                  | 24 ++---
 .../New-DkimSigningConfig.md                  |  6 +-
 .../New-DlpCompliancePolicy.md                |  8 +-
 .../New-DlpComplianceRule.md                  | 24 ++---
 .../New-DlpKeywordDictionary.md               |  2 +-
 .../ExchangePowerShell/New-DlpPolicy.md       |  6 +-
 .../New-DynamicDistributionGroup.md           | 10 +--
 .../New-EOPProtectionPolicyRule.md            | 10 +--
 .../New-EcpVirtualDirectory.md                | 10 +--
 .../New-EdgeSubscription.md                   |  6 +-
 .../New-EdgeSyncServiceConfig.md              |  8 +-
 .../New-EmailAddressPolicy.md                 |  6 +-
 .../New-ExchangeCertificate.md                |  8 +-
 .../New-ExchangeSettings.md                   |  2 +-
 .../New-ExoPhishSimOverrideRule.md            |  6 +-
 .../New-ExoSecOpsOverrideRule.md              |  6 +-
 .../ExchangePowerShell/New-FederationTrust.md |  2 +-
 .../ExchangePowerShell/New-Fingerprint.md     |  4 +-
 .../New-ForeignConnector.md                   |  6 +-
 .../New-GlobalAddressList.md                  |  4 +-
 .../New-HoldCompliancePolicy.md               |  6 +-
 .../New-HoldComplianceRule.md                 |  6 +-
 .../New-HostedContentFilterPolicy.md          | 80 ++++++++---------
 .../New-HostedContentFilterRule.md            |  2 +-
 .../New-HostedOutboundSpamFilterPolicy.md     | 14 +--
 .../New-HostedOutboundSpamFilterRule.md       |  4 +-
 .../New-HybridConfiguration.md                |  2 +-
 .../New-InboundConnector.md                   | 18 ++--
 .../ExchangePowerShell/New-InboxRule.md       | 16 ++--
 .../New-InformationBarrierPolicy.md           |  2 +-
 .../New-IntraOrganizationConnector.md         |  8 +-
 .../ExchangePowerShell/New-JournalRule.md     |  4 +-
 .../ExchangePowerShell/New-Label.md           |  4 +-
 .../ExchangePowerShell/New-LabelPolicy.md     |  2 +-
 .../New-M365DataAtRestEncryptionPolicy.md     |  4 +-
 .../ExchangePowerShell/New-Mailbox.md         | 20 ++---
 95 files changed, 462 insertions(+), 434 deletions(-)

diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-X400AuthoritativeDomain.md b/exchange/exchange-ps/ExchangePowerShell/Get-X400AuthoritativeDomain.md
index 0779c91d83..a16c7bb305 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-X400AuthoritativeDomain.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-X400AuthoritativeDomain.md
@@ -28,7 +28,7 @@ Get-X400AuthoritativeDomain [[-Identity] <X400AuthoritativeDomainIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Import-DlpPolicyCollection.md b/exchange/exchange-ps/ExchangePowerShell/Import-DlpPolicyCollection.md
index 0785727433..52656dd2d1 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Import-DlpPolicyCollection.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Import-DlpPolicyCollection.md
@@ -13,7 +13,7 @@ title: Import-DlpPolicyCollection
 # Import-DlpPolicyCollection
 
 ## SYNOPSIS
-**Note**: This cmdlet has been retired from the cloud-based service. For more information, see [this blog post](https://techcommunity.microsoft.com/t5/exchange-team-blog/exchange-online-etrs-to-stop-supporting-dlp-policies/ba-p/3886713).
+**Note**: This cmdlet is retired from the cloud-based service. For more information, see [this blog post](https://techcommunity.microsoft.com/t5/exchange-team-blog/exchange-online-etrs-to-stop-supporting-dlp-policies/ba-p/3886713).
 
 This cmdlet is functional only in on-premises Exchange.
 
@@ -37,7 +37,7 @@ The Import-DlpPolicyCollection cmdlet imports all the settings of the DLP polici
 
 Importing a DLP policy collection from an XML file removes or overwrites all pre-existing DLP policies that were defined in your organization. Make sure that you have a backup of your current DLP policy collection before you import and overwrite your current DLP policies.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Import-DlpPolicyTemplate.md b/exchange/exchange-ps/ExchangePowerShell/Import-DlpPolicyTemplate.md
index 7cd67448e0..812c878550 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Import-DlpPolicyTemplate.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Import-DlpPolicyTemplate.md
@@ -29,7 +29,7 @@ Import-DlpPolicyTemplate [-FileData] <Byte[]>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Import-ExchangeCertificate.md b/exchange/exchange-ps/ExchangePowerShell/Import-ExchangeCertificate.md
index 16a6171171..506ea14827 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Import-ExchangeCertificate.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Import-ExchangeCertificate.md
@@ -72,7 +72,7 @@ There are many factors to consider when you configure certificates for Transport
 
 Secure Sockets Layer (SSL) is being replaced by Transport Layer Security (TLS) as the protocol that's used to encrypt data sent between computer systems. They're so closely related that the terms "SSL" and "TLS" (without versions) are often used interchangeably. Because of this similarity, references to "SSL" in Exchange topics, the Exchange admin center and the Exchange Management Shell have often been used to encompass both the SSL and TLS protocols. Typically, "SSL" refers to the actual SSL protocol only when a version is also provided (for example, SSL 3.0). For more information, see [Exchange Server TLS configuration best practices](https://learn.microsoft.com/Exchange/exchange-tls-configuration).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -157,7 +157,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-This parameter has been deprecated and is no longer used.
+This parameter is deprecated and no longer used.
 
 ```yaml
 Type: String[]
@@ -263,7 +263,7 @@ Accept wildcard characters: False
 The PrivateKeyExportable parameter specifies whether the certificate has an exportable private key and controls whether you can export the certificate from this server. Valid values are:
 
 - $true: The private key is exportable, so you can export the certificate from this server.
-- $false: The private key isn't exportable, so you can't export the certificate from this server. This is the default value.
+- $false: The private key isn't exportable, so you can't export the certificate from this server. This value is the default.
 
 ```yaml
 Type: Boolean
diff --git a/exchange/exchange-ps/ExchangePowerShell/Import-JournalRuleCollection.md b/exchange/exchange-ps/ExchangePowerShell/Import-JournalRuleCollection.md
index 20711926b1..66936d5797 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Import-JournalRuleCollection.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Import-JournalRuleCollection.md
@@ -36,7 +36,7 @@ Importing a journal rule collection from an XML file removes or overwrites all p
 
 For more information about how to export a journal rule collection to an XML file, see [Export-JournalRuleCollection](https://learn.microsoft.com/powershell/module/exchangepowershell/export-journalrulecollection).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Import-RecipientDataProperty.md b/exchange/exchange-ps/ExchangePowerShell/Import-RecipientDataProperty.md
index 4aa0575df7..772de76e50 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Import-RecipientDataProperty.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Import-RecipientDataProperty.md
@@ -42,7 +42,7 @@ Import-RecipientDataProperty [-Identity] <MailboxUserContactIdParameter> -FileDa
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Import-TransportRuleCollection.md b/exchange/exchange-ps/ExchangePowerShell/Import-TransportRuleCollection.md
index ac58f3c39e..cb5499437f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Import-TransportRuleCollection.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Import-TransportRuleCollection.md
@@ -37,7 +37,7 @@ Importing a transport rule collection from an XML file removes or overwrites all
 
 For information about how to export a transport rule collection to an XML file, see [Export-TransportRuleCollection](https://learn.microsoft.com/powershell/module/exchangepowershell/export-transportrulecollection).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Import-UMPrompt.md b/exchange/exchange-ps/ExchangePowerShell/Import-UMPrompt.md
index 84ada54feb..69b9d8c936 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Import-UMPrompt.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Import-UMPrompt.md
@@ -62,7 +62,7 @@ The Import-UMPrompt cmdlet imports custom greeting audio files into UM dial plan
 
 After this task is completed, the custom audio file can be used by a UM dial plan or auto attendant.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -131,7 +131,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
 
-The PromptFileStream parameter specifies whether the audio file will be uploaded or imported as an audio stream and not a byte array. The default setting is for the audio file to imported as a byte array.
+The PromptFileStream parameter specifies whether the audio file is uploaded or imported as an audio stream and not a byte array. The default setting is for the audio file to imported as a byte array.
 
 ```yaml
 Type: Stream
diff --git a/exchange/exchange-ps/ExchangePowerShell/Install-TransportAgent.md b/exchange/exchange-ps/ExchangePowerShell/Install-TransportAgent.md
index 92cf1ae653..b05098dde5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Install-TransportAgent.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Install-TransportAgent.md
@@ -31,9 +31,9 @@ Install-TransportAgent [-Name] <String> -AssemblyPath <String> -TransportAgentFa
 ```
 
 ## DESCRIPTION
-Transport agents have full access to all email messages that they encounter. Exchange puts no restrictions on a transport agent's behavior. Transport agents that are unstable or contain security flaws may affect the stability and security of Exchange. Therefore, you need to only install transport agents that you fully trust and that have been fully tested.
+Transport agents have full access to all email messages that they encounter. Exchange puts no restrictions on a transport agent's behavior. Transport agents that are unstable or contain security flaws might affect the stability and security of Exchange. Therefore, you need to only install transport agents that you fully trust and that have been fully tested.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Invoke-ComplianceSearchActionStep.md b/exchange/exchange-ps/ExchangePowerShell/Invoke-ComplianceSearchActionStep.md
index 2faa34ef03..815fd65f2d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Invoke-ComplianceSearchActionStep.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Invoke-ComplianceSearchActionStep.md
@@ -13,7 +13,7 @@ title: Invoke-ComplianceSearchActionStep
 # Invoke-ComplianceSearchActionStep
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 This cmdlet is reserved for internal Microsoft use.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Invoke-MonitoringProbe.md b/exchange/exchange-ps/ExchangePowerShell/Invoke-MonitoringProbe.md
index 7292433a9c..62068c483c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Invoke-MonitoringProbe.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Invoke-MonitoringProbe.md
@@ -17,7 +17,7 @@ This cmdlet is available only in on-premises Exchange.
 
 Use the Invoke-MonitoringProbe cmdlet to run a Managed Availability probe on a selected server.
 
-This cmdlet cannot be used to run every Managed Availability probe. Only some probes (mainly the deep test probes) can be run manually using this cmdlet. Probes that cannot be run with this cmdlet will generate an error message when Invoke-MonitoringProbe is used to run them.
+This cmdlet can't be used to run every Managed Availability probe. Only some probes (mainly the deep test probes) can be run manually using this cmdlet. Probes that can't be run with this cmdlet return error messages when you use Invoke-MonitoringProbe to run them.
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
@@ -38,7 +38,7 @@ Invoke-MonitoringProbe [-Identity] <String> -Server <ServerIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -98,7 +98,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-The Account parameter specifies the identity of the mailbox or user account that will run the monitoring probe.
+The Account parameter specifies the identity of the mailbox or user account that's used to run the monitoring probe.
 
 ```yaml
 Type: String
@@ -134,7 +134,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-The ItemTargetExtension parameter specifies cmdlet extension data that you can pass to the monitoring probe. The probe that runs on the server may require specific data for its execution. This data is presented to the probe on execution in an XML format.
+The ItemTargetExtension parameter specifies cmdlet extension data that you can pass to the monitoring probe. The probe that runs on the server might require specific data for its execution. This data is presented to the probe on execution in an XML format.
 
 ```yaml
 Type: String
@@ -152,7 +152,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-The Password parameter specifies the password of the mailbox or user account that will run the monitoring probe.
+The Password parameter specifies the password of the mailbox or user account that's used to run the monitoring probe.
 
 ```yaml
 Type: String
@@ -188,7 +188,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-The SecondaryAccount parameter specifies the identity of the delegate mailbox or user account that will run the monitoring probe.
+The SecondaryAccount parameter specifies the identity of the delegate mailbox or user account that's used to run the monitoring probe.
 
 ```yaml
 Type: String
@@ -224,7 +224,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-The SecondaryPassword parameter specifies the password of the delegate mailbox or user account that will run the monitoring probe.
+The SecondaryPassword parameter specifies the password of the delegate mailbox or user account that's used to run the monitoring probe.
 
 ```yaml
 Type: String
diff --git a/exchange/exchange-ps/ExchangePowerShell/Mount-Database.md b/exchange/exchange-ps/ExchangePowerShell/Mount-Database.md
index b9d8d46279..041d064d31 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Mount-Database.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Mount-Database.md
@@ -33,7 +33,7 @@ Mount-Database [-Identity] <DatabaseIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Move-ActiveMailboxDatabase.md b/exchange/exchange-ps/ExchangePowerShell/Move-ActiveMailboxDatabase.md
index 20923aba50..34ab7820b4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Move-ActiveMailboxDatabase.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Move-ActiveMailboxDatabase.md
@@ -100,7 +100,7 @@ Move-ActiveMailboxDatabase [-Identity] <DatabaseIdParameter> [-ActivateOnServer]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -130,7 +130,7 @@ This example performs a switchover of the database DB3 to the Mailbox server MBX
 Move-ActiveMailboxDatabase -Server MBX1
 ```
 
-This example performs a server switchover for the Mailbox server MBX1. All active mailbox database copies on MBX1 will be activated on one or more other Mailbox servers with healthy copies of the active databases on MBX1.
+This example performs a server switchover for the Mailbox server MBX1. All active mailbox database copies on MBX1 are activated on one or more other Mailbox servers with healthy copies of the active databases on MBX1.
 
 ## PARAMETERS
 
@@ -291,13 +291,13 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-The MountDialOverride parameter is used to override the auto database mount dial (AutoDatabaseMountDial) setting for the target server and specify an alternate setting. The following are possible values:
+The MountDialOverride parameter is used to override the auto database mount dial (AutoDatabaseMountDial) setting for the target server and specify an alternate setting. Valid value are:
 
-- None: When using this value, the currently configured auto database mount dial setting on the target server will be used.
-- Lossless: This is the default value. When using this value, the database doesn't automatically mount until all log files that were generated on the original active copy have been copied to the passive copy.
-- GoodAvailability: If you specify this value, the database automatically mounts immediately after a failover if the copy queue length is less than or equal to 6. If the copy queue length is greater than 6, the database doesn't automatically mount. When the copy queue length is less than or equal to 6, Microsoft Exchange attempts to replicate the remaining logs to the passive copy and then mounts the database.
-- BestEffort: If you specify this value, the database automatically mounts regardless of the size of the copy queue length. Because the database will mount with any amount of log loss, using this value could result in a large amount of data loss.
-- BestAvailability: If you specify this value, the database automatically mounts immediately after a failover if the copy queue length is less than or equal to 12. The copy queue length is the number of logs recognized by the passive copy that needs to be replicated. If the copy queue length is more than 12, the database doesn't automatically mount. When the copy queue length is less than or equal to 12, Exchange attempts to replicate the remaining logs to the passive copy and then mounts the database.
+- None: The currently configured auto database mount dial setting on the target server is used.
+- Lossless: This value is the default. The database doesn't automatically mount until all log files that were generated on the original active copy have been copied to the passive copy.
+- GoodAvailability: The database automatically mounts immediately after a failover if the copy queue length is less than or equal to 6. If the copy queue length is greater than 6, the database doesn't automatically mount. When the copy queue length is less than or equal to 6, Microsoft Exchange attempts to replicate the remaining logs to the passive copy and then mounts the database.
+- BestEffort: The database automatically mounts regardless of the size of the copy queue length. Because the database mounts with any amount of log loss, using this value could result in a large amount of data loss.
+- BestAvailability: The database automatically mounts immediately after a failover if the copy queue length is less than or equal to 12. The copy queue length is the number of logs recognized by the passive copy that needs to be replicated. If the copy queue length is more than 12, the database doesn't automatically mount. When the copy queue length is less than or equal to 12, Exchange attempts to replicate the remaining logs to the passive copy and then mounts the database.
 
 ```yaml
 Type: DatabaseMountDialOverride
@@ -373,7 +373,7 @@ Accept wildcard characters: False
 
 The SkipClientExperienceChecks switch specifies whether to skip the search catalog (content index) state check to see if the search catalog is healthy and up to date. You don't need to specify a value with this switch.
 
-If the search catalog for the database copy you're activating is in an unhealthy or unusable state and you use this parameter to skip the search catalog health check and activate the database copy, you will need to either re-crawl or reseed the search catalog.
+If the search catalog for the database copy you're activating is in an unhealthy or unusable state and you use this parameter to skip the search catalog health check and activate the database copy, you need to either re-crawl or reseed the search catalog.
 
 ```yaml
 Type: SwitchParameter
@@ -449,7 +449,7 @@ Accept wildcard characters: False
 
 The SkipMaximumActiveDatabasesChecks switch specifies whether to skip checking the value of MaximumPreferredActiveDatabases during the best copy and server selection (BCSS) process. You don't need to specify a value with this switch.
 
-Any configured value for MaximumActiveDatabases will still be honored during the BCSS process and by the Information Store.
+Any configured value for MaximumActiveDatabases is honored during the BCSS process and by the Information Store.
 
 ```yaml
 Type: SwitchParameter
diff --git a/exchange/exchange-ps/ExchangePowerShell/Move-AddressList.md b/exchange/exchange-ps/ExchangePowerShell/Move-AddressList.md
index 8a33bcacdd..fa8ea18b19 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Move-AddressList.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Move-AddressList.md
@@ -30,7 +30,7 @@ Move-AddressList [-Identity] <AddressListIdParameter> -Target <AddressListIdPara
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Move-DatabasePath.md b/exchange/exchange-ps/ExchangePowerShell/Move-DatabasePath.md
index 3a1b166654..529019505c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Move-DatabasePath.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Move-DatabasePath.md
@@ -41,7 +41,7 @@ When you use the Move-DatabasePath cmdlet, consider the following:
 - In Exchange 2013 or earlier, you can only run this cmdlet on the affected Mailbox server. If you include the ConfigurationOnly parameter with the value $true, you can run the cmdlet on an administrator's workstation. This does not apply to Exchange 2016 or later (you can run the cmdlet anywhere).
 - This cmdlet can't be run against replicated mailbox databases. To move the path of a replicated database, you must first remove all replicated copies, and then you can perform the move operation. After the move operation is complete, you can add copies of the mailbox database.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Move-OfflineAddressBook.md b/exchange/exchange-ps/ExchangePowerShell/Move-OfflineAddressBook.md
index c66383eeb8..a9ca973abe 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Move-OfflineAddressBook.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Move-OfflineAddressBook.md
@@ -31,7 +31,7 @@ Move-OfflineAddressBook [-Identity] <OfflineAddressBookIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ATPBuiltInProtectionRule.md b/exchange/exchange-ps/ExchangePowerShell/New-ATPBuiltInProtectionRule.md
index 05e0967f85..1f49fba1f2 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-ATPBuiltInProtectionRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-ATPBuiltInProtectionRule.md
@@ -41,7 +41,7 @@ For more information about preset security policies in PowerShell, see [Preset s
 > [!IMPORTANT]
 > Different types of recipient exceptions use OR logic (the recipient must satisfy **any** of the specified exceptions). For more information, see [Profiles in preset security policies](https://learn.microsoft.com/defender-office-365/preset-security-policies#profiles-in-preset-security-policies).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ATPProtectionPolicyRule.md b/exchange/exchange-ps/ExchangePowerShell/New-ATPProtectionPolicyRule.md
index 5d3eb131cf..5ad446e0c5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-ATPProtectionPolicyRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-ATPProtectionPolicyRule.md
@@ -45,7 +45,7 @@ For more information about preset security policies in PowerShell, see [Preset s
 > [!IMPORTANT]
 > Different types of recipient conditions use AND logic (the recipient must satisfy **all** specified conditions). Different types of recipient exceptions use OR logic (the recipient must satisfy **any** of the specified exceptions). For more information, see [Profiles in preset security policies](https://learn.microsoft.com/defender-office-365/preset-security-policies#profiles-in-preset-security-policies).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -84,7 +84,7 @@ Accept wildcard characters: False
 
 The SafeAttachmentPolicy parameter specifies the existing Safe Attachments policy that's associated with the preset security policy.
 
-If you ever turned on the preset security policy in the Microsoft Defender portal, the name of the Safe Attachments policy will be one of the following values:
+If you ever turned on the preset security policy in the Microsoft Defender portal, the name of the Safe Attachments policy is one of the following values:
 
 - Standard Preset Security Policy\<13-digit number\>. For example, `Standard Preset Security Policy1622650008019`.
 - Strict Preset Security Policy\<13-digit number\>. For example, `Strict Preset Security Policy1642034872546`.
@@ -109,7 +109,7 @@ Accept wildcard characters: False
 
 The SafeLinksPolicy parameter specifies the existing Safe Links policy that's associated with the preset security policy.
 
-If you ever turned on the preset security policy in the Microsoft Defender portal, the name of the Safe Attachments policy will be one of the following values:
+If you ever turned on the preset security policy in the Microsoft Defender portal, the name of the Safe Attachments policy is one of the following values:
 
 - Standard Preset Security Policy\<13-digit number\>. For example, `Standard Preset Security Policy1622650008534`.
 - Strict Preset Security Policy\<13-digit number\>. For example, `Strict Preset Security Policy1642034873192`.
@@ -173,7 +173,7 @@ Accept wildcard characters: False
 
 The Enabled parameter specifies whether the rule is enabled. Valid values are:
 
-- $true: The rule is enabled. The State value of the rule is Enabled. This is the default value.
+- $true: The rule is enabled. The State value of the rule is Enabled. This value is the default.
 - $false: The rule is disabled. The State value of the rule is Disabled.
 
 After you create the rule, you turn on or turn off the preset security policy using one of the following commands:
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AcceptedDomain.md b/exchange/exchange-ps/ExchangePowerShell/New-AcceptedDomain.md
index 7b60a5bca3..bd520684c0 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-AcceptedDomain.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-AcceptedDomain.md
@@ -31,7 +31,7 @@ New-AcceptedDomain [-Name] <String> -DomainName <SmtpDomainWithSubdomains>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -68,7 +68,7 @@ Accept wildcard characters: False
 
 The DomainName parameter specifies the SMTP domain that you want to establish as an accepted domain. Valid input for the DomainName parameter is an SMTP domain. You can use a wildcard character to specify all subdomains of a specified domain, as shown in the following example: \*.contoso.com.
 
-However, you can't embed a wildcard character, as shown in the following example: domain.\*.contoso.com. The domain name string may not contain more than 256 characters.
+However, you can't embed a wildcard character, as shown in the following example: domain.\*.contoso.com. The domain name string might not contain more than 256 characters.
 
 ```yaml
 Type: SmtpDomainWithSubdomains
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ActiveSyncDeviceAccessRule.md b/exchange/exchange-ps/ExchangePowerShell/New-ActiveSyncDeviceAccessRule.md
index 81e0237759..831cfa333c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-ActiveSyncDeviceAccessRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-ActiveSyncDeviceAccessRule.md
@@ -13,7 +13,7 @@ title: New-ActiveSyncDeviceAccessRule
 # New-ActiveSyncDeviceAccessRule
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the New-ActiveSyncDeviceAccessRule cmdlet to define the access levels for Exchange ActiveSync devices based on the identity of the device.
 
@@ -32,7 +32,7 @@ New-ActiveSyncDeviceAccessRule -AccessLevel <DeviceAccessLevel> -Characteristic
 ## DESCRIPTION
 You can create multiple rules that define groups of devices: Allowed devices, blocked devices and quarantined devices.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ActiveSyncMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-ActiveSyncMailboxPolicy.md
index 9d14e34c18..2b7ff6ccd4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-ActiveSyncMailboxPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-ActiveSyncMailboxPolicy.md
@@ -13,7 +13,7 @@ title: New-ActiveSyncMailboxPolicy
 # New-ActiveSyncMailboxPolicy
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the New-ActiveSyncMailboxPolicy cmdlet to create a Microsoft Mobile Device mailbox policy object.
 
@@ -89,7 +89,7 @@ The New-ActiveSyncMailboxPolicy cmdlet creates a Mobile Device mailbox policy fo
 
 Some Mobile Device mailbox policy settings require the mobile device to have certain built-in features that enforce these security and device management settings. If your organization allows all devices, you must set the AllowNonProvisionableDevices parameter to $true. This allows devices that can't enforce all policy settings to synchronize with your server.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -112,7 +112,7 @@ This example creates the Mobile Device mailbox policy Management that has severa
 New-ActiveSyncMailboxPolicy -Name:"Contoso" -DevicePasswordEnabled:$true -AlphanumericDevicePasswordRequired:$true -PasswordRecoveryEnabled:$true -MinDevicePasswordComplexCharacters:3 -IsDefault:$true -DevicePasswordHistory:10
 ```
 
-This example creates the Mobile Device mailbox policy Contoso that has several preconfigured values. This policy is configured to be the default policy for the organization. The default policy will be assigned to all new users.
+This example creates the Mobile Device mailbox policy Contoso that has several preconfigured values. This policy is configured to be the default policy for the organization. The default policy is assigned to all new users.
 
 ## PARAMETERS
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ActiveSyncVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/New-ActiveSyncVirtualDirectory.md
index 7580c9fdba..ff2968558b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-ActiveSyncVirtualDirectory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-ActiveSyncVirtualDirectory.md
@@ -45,7 +45,7 @@ New-ActiveSyncVirtualDirectory [-ApplicationRoot <String>]
 ## DESCRIPTION
 The New-ActiveSyncVirtualDirectory cmdlet creates an Exchange ActiveSync virtual directory on the specified server under the specified website. The Exchange ActiveSync virtual directory created is named Microsoft-Server-ActiveSync. Only one Exchange ActiveSync virtual directory can exist in each Exchange ActiveSync website.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -157,7 +157,7 @@ The ExtendedProtectionFlags parameter specifies custom settings for Extended Pro
 - AllowDotlessSPN: Required if you want to use Service Principal Name (SPN) values that don't contain FQDNs (for example, HTTP/ContosoMail instead of HTTP/mail.contoso.com). You specify SPNs with the ExtendedProtectionSPNList parameter. This setting makes Extended Protection for Authentication less secure because dotless certificates aren't unique, so it isn't possible to ensure that the client-to-proxy connection was established over a secure channel.
 - NoServiceNameCheck: The SPN list isn't checked to validate a channel binding token. This setting makes Extended Protection for Authentication less secure. We generally don't recommend this setting.
 - Proxy: A proxy server is responsible for terminating the SSL channel. To use this setting, you need to register an SPN by using the ExtendedProtectionSPNList parameter.
-- ProxyCoHosting: HTTP and HTTPS traffic may be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server.
+- ProxyCoHosting: HTTP and HTTPS traffic might be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server.
 
 ```yaml
 Type: MultiValuedProperty
@@ -177,7 +177,7 @@ Accept wildcard characters: False
 
 The ExtendedProtectionSPNList parameter specifies a list of valid Service Principal Names (SPNs) if you're using Extended Protection for Authentication on the virtual directory. Valid values are:
 
-- $null: This is the default value.
+- $null: This value is the default.
 - Single SPN or comma delimited list of valid SPNs: The SPN value format is `Protocol\FQDN`. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter.
 
 ```yaml
@@ -198,8 +198,8 @@ Accept wildcard characters: False
 
 The ExtendedProtectionTokenChecking parameter defines how you want to use Extended Protection for Authentication on the virtual directory. Extended Protection for Authentication isn't enabled by default. Valid values are:
 
-- None: Extended Protection for Authentication isn't be used on the virtual directory. This is the default value.
-- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication will work, but may not be as secure as connections that use Extended Protection for Authentication.
+- None: Extended Protection for Authentication isn't be used on the virtual directory. This value is the default.
+- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication work, but might not be as secure as connections that use Extended Protection for Authentication.
 - Require: Extended Protection for Authentication is used for all connections between clients and the virtual directory. If either the client or server doesn't support it, the connection will fail. If you use this value, you also need to set an SPN value for the ExtendedProtectionSPNList parameter.
 
 **Note**: If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter.
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AddressBookPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-AddressBookPolicy.md
index 0549ac3edd..36f586f9a4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-AddressBookPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-AddressBookPolicy.md
@@ -13,9 +13,9 @@ title: New-AddressBookPolicy
 # New-AddressBookPolicy
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
-Use the New-AddressBookPolicy cmdlet to create an address book policy. Address book policies define the global address list (GAL), offline address book (OAB), room list, and address lists that will be displayed to mailbox users who are assigned the policy.
+Use the New-AddressBookPolicy cmdlet to create an address book policy. Address book policies define the global address list (GAL), offline address book (OAB), room list, and address lists shown to mailbox users who are assigned the policy.
 
 In Exchange Online, this cmdlet is available only in the Address Lists role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Address Lists role to a role group (for example, to the Organization Management role group). For more information, see [Add a role to a role group](https://learn.microsoft.com/Exchange/permissions/role-groups#add-a-role-to-a-role-group).
 
@@ -32,7 +32,7 @@ New-AddressBookPolicy [-Name] <String> -AddressLists <AddressListIdParameter[]>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -73,7 +73,15 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
 
-The AddressLists parameter specifies the address lists that will be used by mailbox users who are assigned this address book policy. This parameter accepts multiple values, which should be separated by a comma. For example, "\\Mr. Munson's Class","Mrs. McKay's Class","Mrs. Count's Class".
+The AddressLists parameter specifies the address lists for mailbox users who are assigned this address book policy. You can use any value that uniquely identifies the address list. For example:
+
+- Name
+- Distinguished name (DN)
+- GUID
+
+You can enter multiple values separated by commas. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`.
+
+You can find the identify values of address lists by using the Get-AddressList cmdlet.
 
 ```yaml
 Type: AddressListIdParameter[]
@@ -91,7 +99,15 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
 
-The GlobalAddressList parameter specifies the identity of the GAL that will be used by mailbox users who are assigned this address book policy. You can specify only one GAL for each address book policy.
+The GlobalAddressList parameter specifies the GAL for mailbox users who are assigned this address book policy. You can use any value that uniquely identifies the GAL. For example:
+
+- Name
+- Distinguished name (DN)
+- GUID
+
+You can find the identify values of GALs by using the Get-GlobalAddressList cmdlet.
+
+You can specify only one GAL for each address book policy.
 
 ```yaml
 Type: GlobalAddressListIdParameter
@@ -109,7 +125,15 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
 
-The OfflineAddressBook parameter specifies the identity of the OAB that will be used by mailbox users who are assigned this address book policy. You can specify only one OAB for each address book policy.
+The OfflineAddressBook parameter specifies the OAB for mailbox users who are assigned this address book policy. You can use any value that uniquely identifies the OAB. For example:
+
+- Name
+- Distinguished name (DN)
+- GUID
+
+You can find the identify values of OABs by using the Get-OfflineAddressBook cmdlet.
+
+You can specify only one OAB for each address book policy.
 
 ```yaml
 Type: OfflineAddressBookIdParameter
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AddressList.md b/exchange/exchange-ps/ExchangePowerShell/New-AddressList.md
index b0e5d2457b..8c147fdbe2 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-AddressList.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-AddressList.md
@@ -13,7 +13,7 @@ title: New-AddressList
 # New-AddressList
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the New-AddressList cmdlet to create address lists and apply them to recipients.
 
@@ -74,7 +74,7 @@ The Conditional parameters that are used with the IncludedRecipients parameter a
 
 To create flexible filters that use any available recipient property and that aren't subject to these limitations, you can use the RecipientFilter parameter to create an OPATH filter.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AdminAuditLogSearch.md b/exchange/exchange-ps/ExchangePowerShell/New-AdminAuditLogSearch.md
index 6f6e1a5d91..18a80d3e96 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-AdminAuditLogSearch.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-AdminAuditLogSearch.md
@@ -16,7 +16,7 @@ title: New-AdminAuditLogSearch
 > [!NOTE]
 > This cmdlet will be deprecated in the cloud-based service. To access audit log data, use the Search-UnifiedAuditLog cmdlet. For more information, see this blog post: <https://aka.ms/AdminAuditCmdletBlog>.
 
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the New-AdminAuditLogSearch cmdlet to search the contents of the administrator audit log and send the results to one or more mailboxes that you specify.
 
@@ -41,7 +41,7 @@ New-AdminAuditLogSearch -EndDate <ExDateTime> -StartDate <ExDateTime> -StatusMai
 ## DESCRIPTION
 After the New-AdminAuditLogSearch cmdlet is run, the report is delivered to the mailboxes you specify within 15 minutes. The log is included as an XML attachment on the report email message. The maximum size of the log that can be generated is 10 megabytes (MB).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AntiPhishPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-AntiPhishPolicy.md
index 3275adc777..697abf3319 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-AntiPhishPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-AntiPhishPolicy.md
@@ -72,7 +72,7 @@ Phishing messages contain fraudulent links or spoofed domains in an effort to ge
 
 New policies that you create using this cmdlet aren't applied to users and aren't visible in admin centers. You need to use the AntiPhishPolicy parameter on the New-AntiPhishRule or Set-AntiPhishRule cmdlets to associate the policy with a rule.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -135,7 +135,7 @@ This setting is part of spoof protection.
 
 The AuthenticationFailAction parameter specifies the action to take when the message fails composite authentication (a mixture of traditional SPF, DKIM, and DMARC email authentication checks and proprietary backend intelligence). Valid values are:
 
-- MoveToJmf: This is the default value. Deliver the message to the Junk Email folder in the recipient's mailbox.
+- MoveToJmf: This value is the default. Deliver the message to the Junk Email folder in the recipient's mailbox.
 - Quarantine: Deliver the message to quarantine. Quarantined high confidence phishing messages are available only to admins. As of April 2020, quarantined phishing messages are available to the intended recipients.
 
 ```yaml
@@ -180,7 +180,7 @@ This setting is part of spoof protection.
 The DmarcQuarantineAction parameter specifies the action to take when a message fails DMARC checks and the sender's DMARC policy is `p=quarantine`. Valid values are:
 
 - MoveToJmf: Deliver the message to the Junk Email folder in the recipient's mailbox.
-- Quarantine: Deliver the message to quarantine. This is the default value.
+- Quarantine: Deliver the message to quarantine. This value is the default.
 
 This parameter is meaningful only when the HonorDmarcPolicy parameter is set to the value $true.
 
@@ -205,7 +205,7 @@ This setting is part of spoof protection.
 The DmarcRejectAction parameter specifies the action to take when a message fails DMARC checks and the sender's DMARC policy is `p=reject`. Valid values are:
 
 - Quarantine: Deliver the message to quarantine.
-- Reject: Reject the message. This is the default value.
+- Reject: Reject the message. This value is the default.
 
 This parameter is meaningful only when the HonorDmarcPolicy parameter is set to the value $true.
 
@@ -252,7 +252,7 @@ Accept wildcard characters: False
 The EnableFirstContactSafetyTips parameter specifies whether to enable or disable the safety tip that's shown when recipients first receive an email from a sender or do not often receive email from a sender. Valid values are:
 
 - $true: First contact safety tips are enabled.
-- $false: First contact safety tips are disabled. This is the default value.
+- $false: First contact safety tips are disabled. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -274,7 +274,7 @@ This setting is part of impersonation protection and is available only in Micros
 
 The EnableMailboxIntelligence parameter specifies whether to enable or disable mailbox intelligence, which is artificial intelligence (AI) that determines user email patterns with their frequent contacts. Mailbox intelligence helps distinguish between messages from legitimate and impersonated senders based on a recipient's previous communication history. Valid values are:
 
-- $true: Mailbox intelligence is enabled. This is the default value.
+- $true: Mailbox intelligence is enabled. This value is the default.
 - $false: Mailbox intelligence is disabled. The values of the EnableMailboxIntelligenceProtection and MailboxIntelligenceProtectionAction parameters are ignored.
 
 ```yaml
@@ -298,7 +298,7 @@ This setting is part of impersonation protection and is available only in Micros
 The EnableMailboxIntelligenceProtection specifies whether to enable or disable taking action for impersonation detections from mailbox intelligence results. Valid values are:
 
 - $true: Take action for impersonation detections from mailbox intelligence results. Use the MailboxIntelligenceProtectionAction parameter to specify the action.
-- $false: Don't take action for impersonation detections from mailbox intelligence results. The value of the MailboxIntelligenceProtectionAction parameter is ignored. This is the default value.
+- $false: Don't take action for impersonation detections from mailbox intelligence results. The value of the MailboxIntelligenceProtectionAction parameter is ignored. This value is the default.
 
 This parameter is meaningful only if the EnableMailboxIntelligence parameter is set to the value $true.
 
@@ -325,7 +325,7 @@ This setting is part of impersonation protection and is available only in Micros
 The EnableOrganizationDomainsProtection parameter specifies whether to enable domain impersonation protection for all registered domains in the Microsoft 365 organization. Valid values are:
 
 - $true: Domain impersonation protection is enabled for all registered domains in the Microsoft 365 organization.
-- $false: Domain impersonation protection isn't enabled for all registered domains in the Microsoft 365 organization. This is the default value. You can enable protection for specific domains by using the EnableTargetedDomainsProtection and TargetedDomainsToProtect parameters.
+- $false: Domain impersonation protection isn't enabled for all registered domains in the Microsoft 365 organization. This value is the default. You can enable protection for specific domains by using the EnableTargetedDomainsProtection and TargetedDomainsToProtect parameters.
 
 ```yaml
 Type: Boolean
@@ -348,7 +348,7 @@ This setting is part of impersonation protection and is available only in Micros
 The EnableSimilarDomainsSafetyTips parameter specifies whether to enable the safety tip that's shown to recipients for domain impersonation detections. Valid values are:
 
 - $true: Safety tips for similar domains are enabled.
-- $false: Safety tips for similar domains are disabled. This is the default value.
+- $false: Safety tips for similar domains are disabled. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -371,7 +371,7 @@ This setting is part of impersonation protection and is available only in Micros
 The EnableSimilarUsersSafetyTips parameter specifies whether to enable the safety tip that's shown to recipients for user impersonation detections. Valid values are:
 
 - $true: Safety tips for similar users are enabled.
-- $false: Safety tips for similar users are disabled. This is the default value.
+- $false: Safety tips for similar users are disabled. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -417,7 +417,7 @@ This setting is part of impersonation protection and is available only in Micros
 The EnableTargetedDomainsProtection parameter specifies whether to enable domain impersonation protection for a list of specified domains. Valid values are:
 
 - $true: Domain impersonation protection is enabled for the domains specified by the TargetedDomainsToProtect parameter.
-- $false: The TargetedDomainsToProtect parameter isn't used. This is the default value.
+- $false: The TargetedDomainsToProtect parameter isn't used. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -440,7 +440,7 @@ This setting is part of impersonation protection and is available only in Micros
 The EnableTargetedUserProtection parameter specifies whether to enable user impersonation protection for a list of specified users. Valid values are:
 
 - $true: User impersonation protection is enabled for the users specified by the TargetedUsersToProtect parameter.
-- $false: The TargetedUsersToProtect parameter isn't used. This is the default value.
+- $false: The TargetedUsersToProtect parameter isn't used. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -462,7 +462,7 @@ This setting is part of spoof protection.
 
 The EnableUnauthenticatedSender parameter enables or disables unauthenticated sender identification in Outlook. Valid values are:
 
-- $true: This is the default value. A question mark (?) is applied to the sender's photo if the message does not pass SPF or DKIM checks AND the message does not pass DMARC or composite authentication.
+- $true: This value is the default. A question mark (?) is applied to the sender's photo if the message does not pass SPF or DKIM checks AND the message does not pass DMARC or composite authentication.
 - $false: A question mark is never applied to the sender's photo.
 
 To prevent these identifiers from being added to messages from specific senders, you have the following options:
@@ -491,7 +491,7 @@ This setting is part of impersonation protection and is available only in Micros
 The EnableUnusualCharactersSafetyTips parameter specifies whether to enable the safety tip that's shown to recipients for unusual characters in domain and user impersonation detections. Valid values are:
 
 - $true: Safety tips for unusual characters are enabled.
-- $false: Safety tips for unusual characters are disabled. This is the default value.
+- $false: Safety tips for unusual characters are disabled. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -513,7 +513,7 @@ This setting is part of spoof protection.
 
 The EnableViaTag parameter enables or disables adding the via tag to the From address in Outlook (chris@contso.com via fabrikam.com). Valid values are:
 
-- $true: The via tag is added to the From address (the message sender that's displayed in email clients) if the domain in the From address is different from the domain in the DKIM signature or the MAIL FROM address. This is the default value.
+- $true: The via tag is added to the From address (the message sender that's displayed in email clients) if the domain in the From address is different from the domain in the DKIM signature or the MAIL FROM address. This value is the default.
 - $false: The via tag is not added to the From address.
 
 To prevent the via tag from being added to messages from specific senders, you have the following options:
@@ -587,7 +587,7 @@ This setting is part of spoof protection.
 
 The HonorDmarcPolicy enables or disables using the sender's DMARC policy to determine what to do to messages that fail DMARC checks. Valid values are:
 
-- $true: If a message fails DMARC and the sender's DMARC policy is `p=quarantine` or `p=reject`, the DmarcQuarantineAction or DmarcRejectAction parameters specify the action to take on the message. This is the default value.
+- $true: If a message fails DMARC and the sender's DMARC policy is `p=quarantine` or `p=reject`, the DmarcQuarantineAction or DmarcRejectAction parameters specify the action to take on the message. This value is the default.
 - $false: If the message fails DMARC, ignore the action in the sender's DMARC policy. The AuthenticationFailAction parameter specifies the action to take on the message.
 
 ```yaml
@@ -610,8 +610,8 @@ This setting is part of impersonation protection and is available only in Micros
 
 The ImpersonationProtectionState parameter specifies the configuration of impersonation protection. Valid values are:
 
-- Automatic: This is the default value in the default policy named Office365 AntiPhish Policy.
-- Manual: This is the default value in custom policies that you create.
+- Automatic: This value is the default in the default policy named Office365 AntiPhish Policy.
+- Manual: This value is the default in custom policies that you create.
 - Off
 
 ```yaml
@@ -634,7 +634,7 @@ This setting is part of impersonation protection and is available only in Micros
 
 The MailboxIntelligenceProtectionAction parameter specifies what to do with messages that fail mailbox intelligence protection. Valid values are:
 
-- NoAction: This is the default value. Note that this value has the same result as setting the EnableMailboxIntelligenceProtection parameter to $false when the EnableMailboxIntelligence parameter is $true.
+- NoAction: This value is the default. This value has the same result as setting the EnableMailboxIntelligenceProtection parameter to $false when the EnableMailboxIntelligence parameter is $true.
 - BccMessage: Add the recipients specified by the MailboxIntelligenceProtectionActionRecipients parameter to the Bcc field of the message.
 - Delete: Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message.
 - MoveToJmf: Deliver the message to the Junk Email folder in the recipient's mailbox.
@@ -735,7 +735,7 @@ This setting is part of advanced settings and is available only in Microsoft Def
 
 The PhishThresholdLevel parameter specifies the tolerance level that's used by machine learning in the handling of phishing messages. Valid values are:
 
-- 1: Standard: This is the default value. The severity of the action that's taken on the message depends on the degree of confidence that the message is phishing (low, medium, high, or very high confidence). For example, messages that are identified as phishing with a very high degree of confidence have the most severe actions applied, while messages that are identified as phishing with a low degree of confidence have less severe actions applied.
+- 1: Standard: This value is the default. The severity of the action that's taken on the message depends on the degree of confidence that the message is phishing (low, medium, high, or very high confidence). For example, messages that are identified as phishing with a very high degree of confidence have the most severe actions applied, while messages that are identified as phishing with a low degree of confidence have less severe actions applied.
 - 2: Aggressive: Messages that are identified as phishing with a high degree of confidence are treated as if they were identified with a very high degree of confidence.
 - 3: More aggressive: Messages that are identified as phishing with a medium or high degree of confidence are treated as if they were identified with a very high degree of confidence.
 - 4: Most aggressive: Messages that are identified as phishing with a low, medium, or high degree of confidence are treated as if they were identified with a very high degree of confidence.
@@ -864,7 +864,7 @@ This setting is part of impersonation protection and is available only in Micros
 
 The TargetedDomainProtectionAction parameter specifies the action to take on detected domain impersonation messages. You specify the protected domains in the TargetedDomainsToProtect parameter. Valid values are:
 
-- NoAction: This is the default value.
+- NoAction: This value is the default.
 - BccMessage: Add the recipients specified by the TargetedDomainActionRecipients parameter to the Bcc field of the message.
 - Delete: Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message.
 - MoveToJmf: Deliver the message to the Junk Email folder in the recipient's mailbox.
@@ -965,7 +965,7 @@ This setting is part of impersonation protection and is available only in Micros
 
 The TargetedUserProtectionAction parameter specifies the action to take on detected user impersonation messages. You specify the protected users in the TargetedUsersToProtect parameter. Valid values are:
 
-- NoAction: This is the default value.
+- NoAction: This value is the default.
 - BccMessage: Add the recipients specified by the TargetedDomainActionRecipients parameter to the Bcc field of the message.
 - Delete: Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message.
 - MoveToJmf: Deliver the message to the Junk Email folder in the recipient's mailbox.
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AntiPhishRule.md b/exchange/exchange-ps/ExchangePowerShell/New-AntiPhishRule.md
index b779bdcd5c..c51ee1499b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-AntiPhishRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-AntiPhishRule.md
@@ -43,7 +43,7 @@ You need to add the antiphish rule to an existing policy by using the AntiPhishP
 > [!IMPORTANT]
 > Different types of recipient conditions use AND logic (the recipient must satisfy **all** specified conditions). Different types of recipient exceptions use OR logic (the recipient must satisfy **any** of the specified exceptions). For more information, see [Common policy settings](https://learn.microsoft.com/defender-office-365/anti-phishing-policies-about#common-policy-settings).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -148,7 +148,7 @@ Accept wildcard characters: False
 
 The Enabled parameter specifies whether the rule is enabled. Valid values are:
 
-- $true: The rule is enabled. This is the default value.
+- $true: The rule is enabled. This value is the default.
 - $false: The rule is disabled.
 
 In the properties of the rule, the value of this parameter is visible in the State property.
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-App.md b/exchange/exchange-ps/ExchangePowerShell/New-App.md
index 36786d92f6..89e31054bb 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-App.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-App.md
@@ -13,7 +13,7 @@ title: New-App
 # New-App
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the New-App cmdlet to install apps for Outlook.
 
@@ -126,7 +126,7 @@ If the app is enabled for the entire organization, users can activate the new ap
 
 For more information, see [Manage user access to add-ins for Outlook in Exchange Server](https://learn.microsoft.com/Exchange/manage-user-access-to-add-ins-exchange-2013-help) and [Manage deployment of add-ins in the Microsoft 365 admin center](https://learn.microsoft.com/office365/admin/manage/manage-deployment-of-add-ins).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -135,7 +135,7 @@ You need to be assigned permissions before you can run this cmdlet. Although thi
 New-App -FileData ([System.IO.File]::ReadAllBytes('C:\Apps\FinanceTestApp.xml'))
 ```
 
-This example installs the Finance Test app manifest file that has been copied to the local hard disk.
+This example installs the Finance Test app manifest file that is copied to the local hard disk.
 
 ### Example 2
 ```powershell
@@ -272,7 +272,7 @@ Accept wildcard characters: False
 The DefaultStateForUser parameter specifies the default initial state of an organization app. Valid values are:
 
 - Enabled: The organization app is enabled by default.
-- Disabled: The organization app is disabled by default. This is the default value.
+- Disabled: The organization app is disabled by default. This value is the default.
 - AlwaysEnabled: The organization app is enabled and users can't disable it.
 
 You need to use the OrganizationApp switch when you use this parameter.
@@ -335,7 +335,7 @@ Accept wildcard characters: False
 
 The Enabled parameter specifies whether the app is available to users in the organization. Valid values are:
 
-- $true: The app is available to the specified users. This is the default value.
+- $true: The app is available to the specified users. This value is the default.
 - $false: The app is hidden from all users in the organization.
 
 This setting overrides the ProvidedTo, UserList and DefaultStateForUser settings. This setting doesn't prevent users from installing their own instance of the app if they have install permissions.
@@ -589,8 +589,8 @@ Accept wildcard characters: False
 
 The ProvidedTo parameter specifies the availability of the app in your organization. Valid values are:
 
-- Everyone: This is the default value. This app is provided to every user in the organization. Every user sees this app listed in the installed apps list in Outlook on the web Options. When an app in the installed apps list is enabled, users can use the features of this app in their email. All users are blocked from installing their own instances of this app, including but not limited to users with install apps permissions.
-- SpecificUsers: This app is provided to only the users specified by the UserList parameter. All other users don't see this organizational app in their management view, nor will it activate in their mail or calendar items. The specified users are also blocked from installing their own instance of this app. Unlisted users aren't blocked from installing their own instance of this app.
+- Everyone: This value is the default. This app is provided to every user in the organization. Every user sees this app listed in the installed apps list in Outlook on the web Options. When an app in the installed apps list is enabled, users can use the features of this app in their email. All users are blocked from installing their own instances of this app, including but not limited to users with install apps permissions.
+- SpecificUsers: This app is provided to only the users specified by the UserList parameter. All other users don't see this organizational app in their management view, nor does it activate in their mail or calendar items. The specified users are also blocked from installing their own instance of this app. Unlisted users aren't blocked from installing their own instance of this app.
 
 You use this parameter with the OrganizationApp switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AppRetentionCompliancePolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-AppRetentionCompliancePolicy.md
index 3e58c6fc38..ff23d6c486 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-AppRetentionCompliancePolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-AppRetentionCompliancePolicy.md
@@ -197,7 +197,7 @@ Accept wildcard characters: False
 
 The Enabled parameter enables or disables the policy. Valid values are:
 
-- $true: The policy is enabled. This is the default value.
+- $true: The policy is enabled. This value is the default.
 - $false: The policy is disabled.
 
 ```yaml
@@ -379,9 +379,9 @@ Accept wildcard characters: False
 The RestrictiveRetention parameter specifies whether Preservation Lock is enabled for the policy. Valid values are:
 
 - $true: Preservation Lock is enabled for the policy. No one -- including an administrator -- can turn off the policy or make it less restrictive.
-- $false: Preservation Lock isn't enabled for the policy. This is the default value.
+- $false: Preservation Lock isn't enabled for the policy. This value is the default.
 
-After a policy has been locked, no one can turn off or disable it, or remove apps from the policy. The only ways that you can modify the policy are by adding apps to it, or extending its duration. A locked policy can be increased or extended, but it can't be reduced, disabled, or turned off.
+After a policy is locked, no one can turn off or disable it, or remove apps from the policy. The only ways that you can modify the policy are by adding apps to it, or extending its duration. A locked policy can be increased or extended, but it can't be reduced, disabled, or turned off.
 
 Therefore, before you lock a policy, it's critical that you understand your organization's compliance requirements, and that you don't lock a policy until you are certain that it's what you need.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AppRetentionComplianceRule.md b/exchange/exchange-ps/ExchangePowerShell/New-AppRetentionComplianceRule.md
index 03b4a2058f..677746709d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-AppRetentionComplianceRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-AppRetentionComplianceRule.md
@@ -188,7 +188,7 @@ Accept wildcard characters: False
 
 > Applicable: Security & Compliance
 
-The ExcludedItemClasses parameter specifies the types of messages to exclude from the rule. You can use this parameter only to exclude items from a hold policy, which excludes the specified item class from being held. Using this parameter won't exclude items from deletion policies. Typically, you use this parameter to exclude voicemail messages, IM conversations, and other Skype for Business Online content from being held by a hold policy. Common Skype for Business values include:
+The ExcludedItemClasses parameter specifies the types of messages to exclude from the rule. You can use this parameter only to exclude items from a hold policy, which excludes the specified item class from being held. Using this parameter doesn't exclude items from deletion policies. Typically, you use this parameter to exclude voicemail messages, IM conversations, and other Skype for Business Online content from being held by a hold policy. Common Skype for Business values include:
 
 - IPM.Note.Microsoft.Conversation
 - IPM.Note.Microsoft.Conversation.Voice
@@ -199,7 +199,7 @@ The ExcludedItemClasses parameter specifies the types of messages to exclude fro
 - IPM.Note.Microsoft.Voicemail.UM
 - IPM.Note.Microsoft.Voicemail.UM.CA
 
-Additionally, you can specify [message classes for Exchange items](https://learn.microsoft.com/office/vba/outlook/concepts/forms/item-types-and-message-classes) and custom or non-Microsoft message classes. Note that the values you specify aren't validated, so the parameter accepts any text value.
+Additionally, you can specify [message classes for Exchange items](https://learn.microsoft.com/office/vba/outlook/concepts/forms/item-types-and-message-classes) and custom or non-Microsoft message classes. The values you specify aren't validated, so the parameter accepts any text value.
 
 You can specify multiple item class values by using the following syntax: `"Value1","Value2",..."ValueN"`.
 
@@ -307,7 +307,7 @@ The RetentionDurationDisplayHint parameter specifies the units that are used to
 - Months
 - Years
 
-For example, if this parameter is set to the value Years, and the RetentionDuration parameter is set to the value 365, the Microsoft Purview compliance portal will display 1 year as the content hold duration.
+For example, if this parameter is set to the value Years, and the RetentionDuration parameter is set to the value 365, the Microsoft Purview compliance portal displays 1 year as the content hold duration.
 
 ```yaml
 Type: HoldDurationHint
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ApplicationAccessPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-ApplicationAccessPolicy.md
index 7fb71820ea..0e3793c107 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-ApplicationAccessPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-ApplicationAccessPolicy.md
@@ -32,9 +32,9 @@ New-ApplicationAccessPolicy -AccessRight <ApplicationAccessPolicyRight> -AppId <
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
-You can create a limited number of policies in your organization based on a fixed amount of space. If your organization runs out of space for these policies, you'll see the error: "The total size of App Access Policies exceeded the limit." To maximize the number of policies and reduce the amount of space that's consumed by the policies, set a one space character description for the policy. This method will allow approximately 300 policies (versus a previous limit of 100 policies).
+You can create a limited number of policies in your organization based on a fixed amount of space. If your organization runs out of space for these policies, you get the error: "The total size of App Access Policies exceeded the limit." To maximize the number of policies and reduce the amount of space that's consumed by the policies, set a one space character description for the policy. This method allows approximately 300 policies (versus a previous limit of 100 policies).
 
 While scope-based resource access like Mail.Read or Calendar.Read is effective to ensure that the application can only read email or events within a mailbox and not do anything else, application access policies allow admins to enforce limits that are based on a list of mailboxes. For example, apps developed for one country/region shouldn't have access to data from other countries/regions. Or, or a CRM integration application should only access calendars in the Sales organization and no other departments.
 
@@ -147,7 +147,7 @@ You can use any value that uniquely identifies the recipient. For example:
 
 To verify that a recipient is a security principal, run either of the following commands: `Get-Recipient -Identity <RecipientIdentity> | Select-Object IsValidSecurityPrincipal` or `Get-Recipient -ResultSize unlimited | Format-Table -Auto Name,RecipientType,RecipientTypeDetails,IsValidSecurityPrincipal`.
 
-You can't use recipients that aren't security principals with this parameter. For example, the following types of recipients won't work:
+You can specify only security principals with this parameter. For example, the following types of recipients don't work:
 
 - Discovery mailboxes (DiscoveryMailbox)
 - Dynamic distribution groups (DynamicDistributionGroup)
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AuthRedirect.md b/exchange/exchange-ps/ExchangePowerShell/New-AuthRedirect.md
index ce878ff18c..4b5e2d74af 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-AuthRedirect.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-AuthRedirect.md
@@ -32,7 +32,7 @@ New-AuthRedirect -AuthScheme <AuthScheme> -TargetUrl <String>
 ## DESCRIPTION
 Exchange 2010 Client Access servers don't support OAuth authentication requests. Use this cmdlet to redirect OAuth authentication requests to Exchange servers that are running later versions of Exchange. This cmdlet is only useful if your organization has Exchange 2010 Client Access servers.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AuthServer.md b/exchange/exchange-ps/ExchangePowerShell/New-AuthServer.md
index cbcdf925ab..7b361bd869 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-AuthServer.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-AuthServer.md
@@ -60,7 +60,7 @@ New-AuthServer [-Name] <String> -Type <AuthServerType>
 ## DESCRIPTION
 Partner applications authorized by Exchange can access their resources after they're authenticated using server-to-server authentication. A partner application can authenticate by using self-issued tokens trusted by Exchange or by using an authorization server trusted by Exchange.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -196,7 +196,11 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2016, Exchange Server 2019
 
-{{ Fill DomainName Description }}
+This parameter is available only in Exchange Server 2016 (CU18 or higher) and Exchange Server 2019 (CU7 or higher).
+
+The DomainName parameter links a cloud-based organization to the corresponding AuthServer object in the Multi-Tenant Exchange Hybrid. This parameter uses the syntax: "domain.onmicrosoft.com".
+
+For example, if the DomainName value is contoso.onmicrosoft.com, the AuthServer object is associated with the contoso cloud-based organization.
 
 ```yaml
 Type: MultiValuedProperty
@@ -216,7 +220,7 @@ Accept wildcard characters: False
 
 The Enabled parameter specifies whether the authorization server is enabled. Valid values are:
 
-- $true: Authorization tokens that are issued by the authorization server are accepted. This is the default value
+- $true: Authorization tokens that are issued by the authorization server are accepted. This value is the default
 - $false: Authorization tokens that are issued by the authorization server are not accepted.
 
 ```yaml
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AuthenticationPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-AuthenticationPolicy.md
index e623800578..a0774f7214 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-AuthenticationPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-AuthenticationPolicy.md
@@ -13,7 +13,7 @@ title: New-AuthenticationPolicy
 # New-AuthenticationPolicy
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the New-AuthenticationPolicy cmdlet to create authentication policies in your organization.
 
@@ -57,7 +57,7 @@ New-AuthenticationPolicy [[-Name] <String>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AutoSensitivityLabelPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-AutoSensitivityLabelPolicy.md
index ed2a9f99e1..506ad13cb3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-AutoSensitivityLabelPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-AutoSensitivityLabelPolicy.md
@@ -67,7 +67,7 @@ To use this cmdlet in Security & Compliance PowerShell, you need to be assigned
 New-AutoSensitivityLabelPolicy -Name "GlobalPolicy" -Comment "Primary policy" -SharePointLocation "https://my.url","https://my.url2" -OneDriveLocation "https://my.url3","https://my.url4" -Mode TestWithoutNotifications -ApplySensitivityLabel "Test"
 ```
 
-This example creates an auto-labeling policy named GlobalPolicy for the specified SharePoint and OneDrive locations with the label "Test". The new policy has a descriptive comment and will be in simulation mode on creation.
+This example creates an auto-labeling policy named GlobalPolicy for the specified SharePoint and OneDrive locations with the label "Test". The new policy has a descriptive comment and is created in simulation mode.
 
 ## PARAMETERS
 
@@ -420,7 +420,7 @@ Accept wildcard characters: False
 
 The Mode parameter specifies the action and notification level of the auto-labeling policy. Valid values are:
 
-- Enable: The policy is enabled for actions and notifications. This is the default value.
+- Enable: The policy is enabled for actions and notifications. This value is the default.
 - Disable: The policy is disabled.
 - TestWithNotifications: No actions are taken, but notifications are sent.
 - TestWithoutNotifications: An audit mode where no actions are taken, and no notifications are sent.
@@ -563,7 +563,7 @@ Accept wildcard characters: False
 The OverwriteLabel parameter specifies whether to overwrite a manual label. Valid values are:
 
 - $true: Overwrite the manual label.
-- $false: Don't overwrite the manual label. This is the default value.
+- $false: Don't overwrite the manual label. This value is the default.
 
 This parameter works only on Exchange locations.
 
@@ -621,7 +621,7 @@ Accept wildcard characters: False
 
 > Applicable: Security & Compliance
 
-The Priority parameter specifies the priority of the policy. The highest priority policy will take action over lower priority policies if two policies are applicable for a file.
+The Priority parameter specifies the priority of the policy. The highest priority policy takes precedence over lower priority policies if two policies are applicable for a file.
 
 ```yaml
 Type: System.Int32
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AutoSensitivityLabelRule.md b/exchange/exchange-ps/ExchangePowerShell/New-AutoSensitivityLabelRule.md
index b329df41b6..e8a9aa3f46 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-AutoSensitivityLabelRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-AutoSensitivityLabelRule.md
@@ -335,7 +335,7 @@ Accept wildcard characters: False
 The Disabled parameter specifies whether the auto-labeling policy rule is enabled or disabled. Valid values are:
 
 - $true: The rule is disabled.
-- $false: The rule is enabled. This is the default value.
+- $false: The rule is enabled. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -447,7 +447,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 You can use this condition in auto-labeling policy rules that are scoped only to Exchange.
 
@@ -690,7 +690,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 You can use this exception in auto-labeling policy rules that are scoped only to Exchange.
 
@@ -1199,7 +1199,7 @@ Accept wildcard characters: False
 The ReportSeverityLevel parameter specifies the severity level of the incident report for content detections based on the rule. Valid values are:
 
 - None: You can't select this value if the rule has no actions configured.
-- Low: This is the default value.
+- Low: This value is the default.
 - Medium
 - High
 
@@ -1224,7 +1224,7 @@ The RuleErrorAction parameter specifies what to do if an error is encountered du
 
 - Ignore
 - RetryThenBlock
-- Blank (the value $null): This is the default value.
+- Blank (the value $null): This value is the default.
 
 ```yaml
 Type: PolicyRuleErrorAction
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AutodiscoverVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/New-AutodiscoverVirtualDirectory.md
index 80f2a0f3bf..044ee90f33 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-AutodiscoverVirtualDirectory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-AutodiscoverVirtualDirectory.md
@@ -49,7 +49,7 @@ If your organization has multiple email domains and each requires its own Autodi
 
 When you're creating an Autodiscover virtual directory, we recommend that you enable Secure Sockets Layer (SSL) for the Autodiscover service.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -104,7 +104,7 @@ Accept wildcard characters: False
 
 The BasicAuthentication parameter specifies whether Basic authentication is enabled on the virtual directory. Valid values are:
 
-- $true: Basic authentication is enabled. This is the default value.
+- $true: Basic authentication is enabled. This value is the default.
 - $false: Basic authentication is disabled.
 
 ```yaml
@@ -147,7 +147,7 @@ Accept wildcard characters: False
 The DigestAuthentication parameter specifies whether Digest authentication is enabled on the virtual directory. Valid values are:
 
 - $true: Digest authentication is enabled.
-- $false: Digest authentication is disabled. This is the default value.
+- $false: Digest authentication is disabled. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -189,7 +189,7 @@ The ExtendedProtectionFlags parameter specifies custom settings for Extended Pro
 - AllowDotlessSPN: Required if you want to use Service Principal Name (SPN) values that don't contain FQDNs (for example, HTTP/ContosoMail instead of HTTP/mail.contoso.com). You specify SPNs with the ExtendedProtectionSPNList parameter. This setting makes Extended Protection for Authentication less secure because dotless certificates aren't unique, so it isn't possible to ensure that the client-to-proxy connection was established over a secure channel.
 - NoServiceNameCheck: The SPN list isn't checked to validate a channel binding token. This setting makes Extended Protection for Authentication less secure. We generally don't recommend this setting.
 - Proxy: A proxy server is responsible for terminating the SSL channel. To use this setting, you need to register an SPN by using the ExtendedProtectionSPNList parameter.
-- ProxyCoHosting: HTTP and HTTPS traffic may be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server.
+- ProxyCoHosting: HTTP and HTTPS traffic might be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server.
 
 ```yaml
 Type: MultiValuedProperty
@@ -209,7 +209,7 @@ Accept wildcard characters: False
 
 The ExtendedProtectionSPNList parameter specifies a list of valid Service Principal Names (SPNs) if you're using Extended Protection for Authentication on the virtual directory. Valid values are:
 
-- $null: This is the default value.
+- $null: This value is the default.
 - Single SPN or comma delimited list of valid SPNs: The SPN value format is `Protocol\FQDN`. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter.
 
 ```yaml
@@ -230,8 +230,8 @@ Accept wildcard characters: False
 
 The ExtendedProtectionTokenChecking parameter defines how you want to use Extended Protection for Authentication on the virtual directory. Extended Protection for Authentication isn't enabled by default. Valid values are:
 
-- None: Extended Protection for Authentication isn't be used on the virtual directory. This is the default value.
-- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication will work, but may not be as secure as connections that use Extended Protection for Authentication.
+- None: Extended Protection for Authentication isn't be used on the virtual directory. This value is the default.
+- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication work, but might not be as secure as connections that use Extended Protection for Authentication.
 - Require: Extended Protection for Authentication is used for all connections between clients and the virtual directory. If either the client or server doesn't support it, the connection will fail. If you use this value, you also need to set an SPN value for the ExtendedProtectionSPNList parameter.
 
 **Note**: If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter.
@@ -294,7 +294,7 @@ Accept wildcard characters: False
 
 The OAuthAuthentication parameter specifies whether OAuth authentication is enabled on the virtual directory. Valid values are:
 
-- $true: OAuth authentication is enabled. This is the default value.
+- $true: OAuth authentication is enabled. This value is the default.
 - $false: OAuth authentication is disabled.
 
 ```yaml
@@ -415,7 +415,7 @@ Accept wildcard characters: False
 
 The WindowsAuthentication parameter specifies whether Integrated Windows authentication is enabled on the virtual directory. Valid values are:
 
-- $true: Integrated Windows authentication is enabled. This is the default value.
+- $true: Integrated Windows authentication is enabled. This value is the default.
 - $false: Integrated Windows authentication is disabled.
 
 ```yaml
@@ -436,7 +436,7 @@ Accept wildcard characters: False
 
 The WSSecurityAuthentication parameter specifies whether WS-Security (Web Services Security) authentication is enabled on the virtual directory. Valid values are:
 
-- $true: WS-Security authentication is enabled. This is the default value.
+- $true: WS-Security authentication is enabled. This value is the default.
 - $false: WS-Security authentication is disabled.
 
 ```yaml
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AvailabilityConfig.md b/exchange/exchange-ps/ExchangePowerShell/New-AvailabilityConfig.md
index 1617b9203b..d9d4f7cd86 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-AvailabilityConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-AvailabilityConfig.md
@@ -31,7 +31,7 @@ New-AvailabilityConfig
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AvailabilityReportOutage.md b/exchange/exchange-ps/ExchangePowerShell/New-AvailabilityReportOutage.md
index f41f532d23..031e3b3e2f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-AvailabilityReportOutage.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-AvailabilityReportOutage.md
@@ -32,7 +32,7 @@ New-AvailabilityReportOutage [-SiteName] <String> -Comment <String> -DowntimeMin
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-CaseHoldPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-CaseHoldPolicy.md
index a2a84309b5..c401cd7ed0 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-CaseHoldPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-CaseHoldPolicy.md
@@ -18,7 +18,7 @@ This cmdlet is available only in Security & Compliance PowerShell. For more info
 Use the New-CaseHoldPolicy cmdlet to create new case hold policies in the Microsoft Purview compliance portal.
 
 > [!NOTE]
-> After you use the New-CaseHoldPolicy cmdlet to create a case hold policy, you need to use the New-CaseHoldRule cmdlet to create a case hold rule and assign the rule to the policy. **If you don't create a rule for the policy, the hold won't be created, and content locations won't be placed on hold**.
+> After you use the New-CaseHoldPolicy cmdlet to create a case hold policy, you need to use the New-CaseHoldRule cmdlet to create a case hold rule and assign the rule to the policy. **If you don't create a rule for the policy, the hold isn't created, and content locations aren't placed on hold**.
 >
 > Running this cmdlet causes a full synchronization across your organization, which is a significant operation. If you need to create multiple policies, wait until the policy distribution is successful before running the cmdlet again for the next policy. For information about the distribution status, see [Get-CaseHoldPolicy](https://learn.microsoft.com/powershell/module/exchangepowershell/get-caseholdpolicy).
 
@@ -141,7 +141,7 @@ Accept wildcard characters: False
 
 The Enabled parameter specifies whether the policy is enabled or disabled. Valid values are:
 
-- $true: The policy is enabled. This is the default value.
+- $true: The policy is enabled. This value is the default.
 - $false: The policy is disabled.
 
 ```yaml
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-CaseHoldRule.md b/exchange/exchange-ps/ExchangePowerShell/New-CaseHoldRule.md
index 917d74060d..40f1e04187 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-CaseHoldRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-CaseHoldRule.md
@@ -160,7 +160,7 @@ Accept wildcard characters: False
 The Disabled parameter specifies whether the case hold rule is enabled or disabled. Valid values are:
 
 - $true: The rule is disabled.
-- $false: The rule is enabled. This is the default value.
+- $false: The rule is enabled. This value is the default.
 
 ```yaml
 Type: Boolean
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ClassificationRuleCollection.md b/exchange/exchange-ps/ExchangePowerShell/New-ClassificationRuleCollection.md
index 9cfa7a8d54..3c89147d16 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-ClassificationRuleCollection.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-ClassificationRuleCollection.md
@@ -13,7 +13,7 @@ title: New-ClassificationRuleCollection
 # New-ClassificationRuleCollection
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the New-ClassificationRuleCollection cmdlet to import new classification rule collections into your organization.
 
@@ -32,7 +32,7 @@ New-ClassificationRuleCollection [-FileData] <Byte[]>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ClientAccessArray.md b/exchange/exchange-ps/ExchangePowerShell/New-ClientAccessArray.md
index a81bd4b402..17f59324a8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-ClientAccessArray.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-ClientAccessArray.md
@@ -34,7 +34,7 @@ The New-ClientAccessArray cmdlet creates an object that represents a load balanc
 
 Client Access arrays allow Outlook clients in an Active Directory site to access the Client Access servers in the array by using RPC over TCP to a single, unified, fully qualified domain name (FQDN). The RpcClientAccessServer property of new mailbox databases is automatically populated with the FQDN of the Client Access array and this value is used during the creation of Outlook profiles for mailboxes in those databases.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ClientAccessRule.md b/exchange/exchange-ps/ExchangePowerShell/New-ClientAccessRule.md
index 38b6934b7f..ee0bc3376f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-ClientAccessRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-ClientAccessRule.md
@@ -16,7 +16,7 @@ title: New-ClientAccessRule
 > [!NOTE]
 > Beginning in October 2022, client access rules were deprecated for all Exchange Online organizations that weren't using them. Client access rules will be deprecated for all remaining organizations on September 1, 2025. If you choose to turn off client access rules before the deadline, the feature will be disabled in your organization. For more information, see [Update on Client Access Rules Deprecation in Exchange Online](https://techcommunity.microsoft.com/blog/exchange/update-on-client-access-rules-deprecation-in-exchange-online/4354809).
 
-This cmdlet is functional only in Exchange Server 2019 and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is functional only in Exchange Server 2019 and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the New-ClientAccessRule cmdlet to create client access rules. Client access rules help you control access to your organization based on the properties of the connection.
 
@@ -71,7 +71,7 @@ Protocols that don't support authentication type filters:
 - REST
 - UniversalOutlook
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -80,7 +80,7 @@ You need to be assigned permissions before you can run this cmdlet. Although thi
 New-ClientAccessRule -Name AllowRemotePS -Action Allow -AnyOfProtocols RemotePowerShell -Priority 1
 ```
 
-This example creates a highest priority rule that allows access to remote PowerShell. This rule is an important safeguard to preserve access to your organization. Without this rule, if you create rules that block your access to remote PowerShell, or that block all protocols for everyone, you'll lose the ability to fix the rules yourself (you'll need to call Microsoft Customer Service and Support).
+This example creates a highest priority rule that allows access to remote PowerShell. This rule is an important safeguard to preserve access to your organization. Without this rule, if you create rules that block your access to remote PowerShell, or that block all protocols for everyone, you lose the ability to fix the rules yourself (you need to call Microsoft Customer Service and Support).
 
 ### Example 2
 ```powershell
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ComplianceCase.md b/exchange/exchange-ps/ExchangePowerShell/New-ComplianceCase.md
index 28d59c54ab..a92b1a421c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-ComplianceCase.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-ComplianceCase.md
@@ -84,7 +84,7 @@ The CaseType parameter specifies the type of compliance case that you want to cr
 - ComplianceWorkspace: This value is reserved for internal Microsoft use.
 - DataInvestigation: Data investigation cases are used to investigate data spillage incidents.
 - DSR: Data Subject Request (DSR) cases are used to manage General Data Protection Regulation (GDPR) DSR investigations.
-- eDiscovery: eDiscovery (also called eDiscovery Standard) cases are used to manage legal or other types of investigations. This is the default value.
+- eDiscovery: eDiscovery (also called eDiscovery Standard) cases are used to manage legal or other types of investigations. This value is the default.
 - InsiderRisk: Insider risk cases are use to manage insider risk management cases. Typically, insider risk management cases are manually created in the Microsoft Purview compliance portal to further investigate activity based on a risk alert.
 - InternalInvestigation: This value is reserved for internal Microsoft use.
 - SupervisionPolicy: This type of case corresponds to communication compliance policy.
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ComplianceRetentionEvent.md b/exchange/exchange-ps/ExchangePowerShell/New-ComplianceRetentionEvent.md
index 175e4be26e..5c071cf02f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-ComplianceRetentionEvent.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-ComplianceRetentionEvent.md
@@ -196,7 +196,7 @@ Accept wildcard characters: False
 
 > Applicable: Security & Compliance
 
-The EventType parameter specifies the GUID value of the event that will start the retention period for labels that use this event type. Run the following command to see the available GUID values: `Get-ComplianceRetentionEventType | Format-Table Name,GUID`.
+The EventType parameter specifies the GUID value of the event that starts the retention period for labels that use this event type. Run the following command to see the available GUID values: `Get-ComplianceRetentionEventType | Format-Table Name,GUID`.
 
 ```yaml
 Type: ComplianceRuleIdParameter
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ComplianceSearch.md b/exchange/exchange-ps/ExchangePowerShell/New-ComplianceSearch.md
index dde0f3b69a..d3311f357a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-ComplianceSearch.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-ComplianceSearch.md
@@ -13,7 +13,7 @@ title: New-ComplianceSearch
 # New-ComplianceSearch
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the New-ComplianceSearch cmdlet to create compliance searches in Exchange Server 2016 or later and in the Microsoft Purview compliance portal. You use this cmdlet to define the search criteria.
 
@@ -50,7 +50,7 @@ A compliance search requires at least one location. For example, mailboxes using
 
 After you create a compliance search using the New-ComplianceSearch cmdlet, you run the search using the Start-ComplianceSearch cmdlet.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 In on-premises Exchange, this cmdlet is available in the Mailbox Search role. By default, this role is assigned only to the Discovery Management role group.
 
@@ -108,7 +108,7 @@ Accept wildcard characters: False
 The AllowNotFoundExchangeLocationsEnabled parameter specifies whether to include mailboxes other than regular user mailboxes in the compliance search. Valid values are:
 
 - $true: The search doesn't try to validate the existence of the mailbox before proceeding. This value is required if you want to search mailboxes that don't resolve as regular mailboxes.
-- $false: The search tries to validate the existence of the mailbox before proceeding. If you specify a mailbox that isn't a regular user mailbox, the search will fail. This is the default value.
+- $false: The search tries to validate the existence of the mailbox before proceeding. If you specify a mailbox that isn't a regular user mailbox, the search will fail. This value is the default.
 
 The mailbox types that are affected by the value of this parameter include:
 
@@ -287,9 +287,9 @@ Accept wildcard characters: False
 
 This parameter is available only in the cloud-based service.
 
-The HoldNames parameter specifies that the content locations that have been placed on hold in the specified eDiscovery case will be searched. You use the value All for this parameter. You also need to specify the name of an eDiscovery case by using the Case parameter.
+The HoldNames parameter specifies the content locations placed on hold in the specified eDiscovery case are searched. You use the value All for this parameter. You also need to specify the name of an eDiscovery case by using the Case parameter.
 
-Also, if a content location was placed on a query-based case hold, only items that are on hold will be searched when you run this compliance search. For example, if a user was placed on a query-based case hold that preserves items that were sent or created before a specific date, only those items would be searched by using the search criteria specified by this compliance search.
+Also, if a content location was placed on a query-based case hold, only items that are on hold are searched when you run this compliance search. For example, if a user was placed on a query-based case hold that preserves items that were sent or created before a specific date, only those items would be searched by using the search criteria specified by this compliance search.
 
 ```yaml
 Type: String[]
@@ -329,8 +329,8 @@ This parameter is available only in the cloud-based service.
 
 The IncludeUserAppContent parameter specifies that you want to search the cloud-based storage location for users who don't have a regular Microsoft 365 user account in your organization. These types of users include users without an Exchange Online license who use Office applications, Microsoft 365 guest users, and on-premises users whose identity is synchronized with your Microsoft 365 organization. Valid values are:
 
-- $true: The cloud-based storage location for the users specified in the ExchangeLocation parameter will be included in the search. If you use the value All for the ExchangeLocation parameter, the cloud-based storage location for any guest or on-premises user will be included in the search.
-- $false: The cloud-based storage location for the users specified in the ExchangeLocation parameter won't be included in the search. This is the default value.
+- $true: The cloud-based storage location for the users specified in the ExchangeLocation parameter are included in the search. If you use the value All for the ExchangeLocation parameter, the cloud-based storage location for any guest or on-premises user are included in the search.
+- $false: The cloud-based storage location for the users specified in the ExchangeLocation parameter isn't included in the search. This value is the default.
 
 ```yaml
 Type: Boolean
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ComplianceSearchAction.md b/exchange/exchange-ps/ExchangePowerShell/New-ComplianceSearchAction.md
index 0ed529ffc5..bb12c6f155 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-ComplianceSearchAction.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-ComplianceSearchAction.md
@@ -13,7 +13,7 @@ title: New-ComplianceSearchAction
 # New-ComplianceSearchAction
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the New-ComplianceSearchAction cmdlet to create actions for content searches in Exchange Server and in the Microsoft Purview compliance portal.
 
@@ -99,7 +99,7 @@ After you create a content search using the New-ComplianceSearch cmdlet and run
 
 In on-premises Exchange, this cmdlet is available in the Mailbox Search role. By default, this role is assigned only to the Discovery Management role group.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 In Microsoft 365, the account that you use to run this cmdlet must have a valid Microsoft 365 license assigned.
 
@@ -128,7 +128,7 @@ This example creates an export search action for the content search named Projec
 New-ComplianceSearchAction -SearchName "Remove Phishing Message" -Purge -PurgeType SoftDelete
 ```
 
-This example deletes the search results returned by a content search named Remove Phishing Message. Note that unindexed items aren't deleted when you use the Purge parameter.
+This example deletes the search results returned by a content search named Remove Phishing Message. Unindexed items aren't deleted when you use the Purge parameter.
 
 ### Example 4
 ```powershell
@@ -185,7 +185,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
 
-This parameter has been deprecated and is no longer used.
+This parameter is deprecated and no longer used.
 
 To specify the format for Exchange search results, use the ExchangeArchiveFormat parameter. To specify the format for SharePoint and OneDrive search results, use the SharePointArchiveFormat parameter.
 
@@ -259,7 +259,7 @@ The ExchangeArchiveFormat parameter specifies how to export Exchange search resu
 - PerUserPst: One PST file for each mailbox.
 - SinglePst: One PST file that contains all exported messages.
 - SingleFolderPst: One PST file with a single root folder for the entire export.
-- IndividualMessage: Export each message as an .msg message file. This is the default value.
+- IndividualMessage: Export each message as an .msg message file. This value is the default.
 - PerUserZip: One ZIP file for each mailbox. Each ZIP file contains the exported .msg message files from the mailbox.
 - SingleZip: One ZIP file for all mailboxes. The ZIP file contains all exported .msg message files from all mailboxes. This output setting is available only in PowerShell.
 
@@ -396,7 +396,7 @@ This parameter is available only in the cloud-based service.
 The IncludeSharePointDocumentVersions parameter specifies whether to export previous versions of the document when you use the Export switch. Valid values are:
 
 - $true: Export all versions of the document.
-- $false: Export only the current published version of the topic. This is the default value.
+- $false: Export only the current published version of the topic. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -508,7 +508,7 @@ The Purge switch specifies the action for the content search is to remove items
 
   **Tip**: To purge more than 10 items, refer to [ediscoverySearch: purgeData](https://learn.microsoft.com/graph/api/security-ediscoverysearch-purgedata) in the Microsoft Graph API, which allows purging a maximum of 100 items per location.
 
-- You can remove items from a maximum of 50,000 mailboxes using a single content search. To remove items from more than 50,000 mailboxes, you'll have to create separate content searches. For more information, see [Search for and delete email messages in your Microsoft 365 organization](https://learn.microsoft.com/purview/ediscovery-search-for-and-delete-email-messages).
+- You can remove items from a maximum of 50,000 mailboxes using a single content search. To remove items from more than 50,000 mailboxes, you need to create separate content searches. For more information, see [Search for and delete email messages in your Microsoft 365 organization](https://learn.microsoft.com/purview/ediscovery-search-for-and-delete-email-messages).
 - Unindexed items aren't removed from mailboxes when you use this switch.
 - The value of the PurgeType parameter controls how the items are removed.
 
@@ -533,7 +533,7 @@ Accept wildcard characters: False
 The PurgeType parameter specifies how to remove items when the action is Purge. Valid values are:
 
 - SoftDelete: Purged items are recoverable by users until the deleted item retention period expires.
-- HardDelete (cloud only): Purged items are marked for permanent removal from the mailbox and will be permanently removed the next time the mailbox is processed by the Managed Folder Assistant. If single item recovery is enabled on the mailbox, purged items will be permanently removed after the deleted item retention period expires.
+- HardDelete (cloud only): Purged items are marked for permanent removal from the mailbox and are permanently removed the next time the mailbox is processed by the Managed Folder Assistant. If single item recovery is enabled on the mailbox, purged items are permanently removed after the deleted item retention period expires.
 
 ```yaml
 Type: ComplianceDestroyType
@@ -728,7 +728,7 @@ This parameter requires the Export role. By default, this role is assigned only
 
 The SharePointArchiveFormat parameter specifies how to export SharePoint and OneDrive search results. Valid values are:
 
-- IndividualMessage: Export the files uncompressed. This is the default value.
+- IndividualMessage: Export the files uncompressed. This value is the default.
 - PerUserZip: One ZIP file for each user. Each ZIP file contains the exported files for the user.
 - SingleZip: One ZIP file for all users. The ZIP file contains all exported files from all users. This output setting is available only in PowerShell.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ComplianceTag.md b/exchange/exchange-ps/ExchangePowerShell/New-ComplianceTag.md
index e58199a8c7..a1340d5858 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-ComplianceTag.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-ComplianceTag.md
@@ -373,7 +373,7 @@ Accept wildcard characters: False
 The IsRecordLabel parameter specifies whether the label is a record label. Valid values are:
 
 - $true: The label is a record label. Once the label is applied to content, the label can't be removed.
-- $false: The label isn't a record label. This is the default value.
+- $false: The label isn't a record label. This value is the default.
 
 ```yaml
 Type: Boolean
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DataClassification.md b/exchange/exchange-ps/ExchangePowerShell/New-DataClassification.md
index ef07895c85..4fd215d87d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-DataClassification.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-DataClassification.md
@@ -15,7 +15,7 @@ title: New-DataClassification
 ## SYNOPSIS
 This cmdlet is functional only in on-premises Exchange.
 
-In Exchange Online, this cmdlet has been replaced by the [New-DlpSensitiveInformationType](https://learn.microsoft.com/powershell/module/exchangepowershell/new-dlpsensitiveinformationtype) cmdlet in Security & Compliance PowerShell.
+In Exchange Online, this cmdlet is replaced by the [New-DlpSensitiveInformationType](https://learn.microsoft.com/powershell/module/exchangepowershell/new-dlpsensitiveinformationtype) cmdlet in Security & Compliance PowerShell.
 
 Use the New-DataClassification cmdlet to create data classification rules that use document fingerprints.
 
@@ -36,7 +36,7 @@ New-DataClassification [-Name] <String> -Description <String> -Fingerprints <Mul
 ## DESCRIPTION
 Classification rule packages are used by data loss prevention (DLP) to detect sensitive content in messages.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DataEncryptionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-DataEncryptionPolicy.md
index f042b32c86..b38fc22108 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-DataEncryptionPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-DataEncryptionPolicy.md
@@ -36,7 +36,7 @@ Data encryption policy cmdlets are the Exchange Online part of Customer Key. For
 
 You can assign a data encryption policy to a mailbox by using the DataEncryptionPolicy parameter on the Set-Mailbox cmdlet in Exchange Online PowerShell.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -150,7 +150,7 @@ Accept wildcard characters: False
 
 The Enabled parameter enables or disable the data encryption policy. Valid values are:
 
-- $true: The policy is enabled. This is the default value.
+- $true: The policy is enabled. This value is the default.
 - $false: The policy is disabled.
 
 ```yaml
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DatabaseAvailabilityGroup.md b/exchange/exchange-ps/ExchangePowerShell/New-DatabaseAvailabilityGroup.md
index e5d42b21af..dbe1a8d9f5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-DatabaseAvailabilityGroup.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-DatabaseAvailabilityGroup.md
@@ -52,9 +52,9 @@ The following combinations of options and behaviors are available:
 
 If the witness server that you specify isn't an Exchange server, you need to add the Exchange Trusted Subsystem universal security group (USG) to the local Administrators group on the witness server. If the witness server is a directory server, you need to add the Exchange Trusted Subsystem USG to the Builtin\\Administrators group. These security permissions are necessary to ensure that Exchange can create a directory and share on the witness server as needed.
 
-In Windows Server 2012 R2 or later, a DAG is created without a cluster administrative access point by default. In this scenario, you don't need to provide any IP addresses to the DAG. However, in all supported versions of Windows, you have the option of assigning static IP addresses to the DAG by using the DatabaseAvailabilityGroupIpAddresses parameter. If you specify Any or 0.0.0.0, the task attempts to use Dynamic Host Configuration Protocol (DHCP) to obtain IP addresses. If you omit this parameter or configure the parameter with a value of None or 255.255.255.255, the DAG will not have a cluster administrative access point.
+In Windows Server 2012 R2 or later, a DAG is created without a cluster administrative access point by default. In this scenario, you don't need to provide any IP addresses to the DAG. However, in all supported versions of Windows, you have the option of assigning static IP addresses to the DAG by using the DatabaseAvailabilityGroupIpAddresses parameter. If you specify Any or 0.0.0.0, the task attempts to use Dynamic Host Configuration Protocol (DHCP) to obtain IP addresses. If you omit this parameter or configure the parameter with a value of None or 255.255.255.255, the DAG doesn't have a cluster administrative access point.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -77,7 +77,7 @@ This example creates the DAG named DAG2 with a witness server named SERVER2. The
 New-DatabaseAvailabilityGroup -Name DAG3 -WitnessServer SERVER1 -WitnessDirectory C:\DAG3 -DatabaseAvailabilityGroupIpAddresses 10.0.0.8,192.168.0.8
 ```
 
-This example creates a DAG named DAG3. DAG3 is configured to use SERVER1 for the witness server, and a witness directory on SERVER1 of C:\\DAG3. DAG3 is assigned multiple static IP addresses because the MAPI network for the DAG contains or will contain multiple subnets (10.0.0.x and 192.168.0.x).
+This example creates a DAG named DAG3. DAG3 is configured to use SERVER1 for the witness server, and a witness directory on SERVER1 of C:\\DAG3. DAG3 is assigned multiple static IP addresses because the MAPI network for the DAG contains multiple subnets (10.0.0.x and 192.168.0.x).
 
 ## PARAMETERS
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DatabaseAvailabilityGroupNetwork.md b/exchange/exchange-ps/ExchangePowerShell/New-DatabaseAvailabilityGroupNetwork.md
index 8363b20c66..002a7d6101 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-DatabaseAvailabilityGroupNetwork.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-DatabaseAvailabilityGroupNetwork.md
@@ -34,7 +34,7 @@ New-DatabaseAvailabilityGroupNetwork [-Name] <String> [-DatabaseAvailabilityGrou
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DeliveryAgentConnector.md b/exchange/exchange-ps/ExchangePowerShell/New-DeliveryAgentConnector.md
index 8727a41a18..3320d9ce11 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-DeliveryAgentConnector.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-DeliveryAgentConnector.md
@@ -39,7 +39,7 @@ New-DeliveryAgentConnector [-Name] <String> -AddressSpaces <MultiValuedProperty>
 ## DESCRIPTION
 Delivery agent connectors are used to route messages addressed to foreign systems that don't utilize the SMTP protocol. When a message is routed to a delivery agent connector, the associated delivery agent performs the content conversion and message delivery. Delivery agent connectors allow queue management of foreign connectors, thereby eliminating the need for storing messages on the file system in the Drop and Pickup directories. For more information, see [Delivery agents and Delivery Agent connectors](https://learn.microsoft.com/exchange/delivery-agents-and-delivery-agent-connectors-exchange-2013-help).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DeviceConditionalAccessPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-DeviceConditionalAccessPolicy.md
index c39103379a..e43f3ef571 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-DeviceConditionalAccessPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-DeviceConditionalAccessPolicy.md
@@ -117,7 +117,7 @@ Accept wildcard characters: False
 
 The Enabled parameter specifies whether the policy is enabled. Valid values are:
 
-- $true: The policy is enabled. This is the default value.
+- $true: The policy is enabled. This value is the default.
 - $false: The policy is disabled.
 
 ```yaml
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DeviceConditionalAccessRule.md b/exchange/exchange-ps/ExchangePowerShell/New-DeviceConditionalAccessRule.md
index 1b89079368..a2aff5f1c4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-DeviceConditionalAccessRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-DeviceConditionalAccessRule.md
@@ -152,7 +152,7 @@ Accept wildcard characters: False
 The AccountName parameter specifies the account name. Valid values for this parameter are:
 
 - A text value.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 ```yaml
 Type: String
@@ -173,7 +173,7 @@ Accept wildcard characters: False
 The AccountUserName parameter specifies the account user name. Valid values for this parameter are:
 
 - A text value.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 ```yaml
 Type: String
@@ -195,7 +195,7 @@ The AllowAppStore parameter specifies whether to allow access to the app store o
 
 - $true: Access to the app store is allowed.
 - $false: Access to the app store isn't allowed.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available on the following types of devices:
 
@@ -222,7 +222,7 @@ The AllowAssistantWhileLocked parameter specifies whether to allow the use of th
 
 - $true: The voice assistant can be used while devices are locked.
 - $false: The voice assistant can't be used while devices are locked.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available only on Apple iOS 6+ devices.
 
@@ -246,7 +246,7 @@ The AllowConvenienceLogon parameter specifies whether to allow convenience logon
 
 - $true: Convenience logons are allowed.
 - $false: Convenience logons aren't allowed.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available only on Windows 8.1 RT devices.
 
@@ -270,7 +270,7 @@ The AllowDiagnosticSubmission parameter specifies whether to allow diagnostic su
 
 - $true: Diagnostic submissions are allowed.
 - $false: Diagnostic submissions aren't allowed.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available on the following types of devices:
 
@@ -298,7 +298,7 @@ The AllowiCloudBackup parameter specifies whether to allow Apple iCloud Backup f
 
 - $true: iCloud Backup is allowed.
 - $false: iCloud Backup isn't allowed.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available on the following types of devices:
 
@@ -325,7 +325,7 @@ The AllowiCloudDocSync parameter specifies whether to allow Apple iCloud Documen
 
 - $true: iCloud Documents & Data sync is allowed.
 - $false: iCloud Documents & Data sync isn't allowed.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available on the following types of devices:
 
@@ -352,7 +352,7 @@ The AllowiCloudPhotoSync parameter specifies whether to allow Apple iCloud Photo
 
 - $true: iCloud Photos sync is allowed.
 - $false: iCloud Photo sync isn't allowed.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available on the following types of devices:
 
@@ -379,7 +379,7 @@ The AllowJailbroken parameter specifies whether to allow access to your organiza
 
 - $true: Jailbroken devices are allowed.
 - $false: Jailbroken devices aren't allowed.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available on the following types of devices:
 
@@ -406,7 +406,7 @@ The AllowPassbookWhileLocked parameter specifies whether to allow the use of App
 
 - $true: Passbook is available while devices are locked.
 - $false: Passbook isn't available while devices are locked.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available only on Apple iOS 6+ devices.
 
@@ -430,7 +430,7 @@ The AllowScreenshot parameter specifies whether to allow screenshots on devices.
 
 - $true: Screenshots are allowed.
 - $false: Screenshots aren't allowed.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available on the following types of devices:
 
@@ -457,7 +457,7 @@ The AllowSimplePassword parameter specifies whether to allow simple or non-compl
 
 - $true: Simple passwords are allowed.
 - $false: Simple passwords aren't allowed.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available on the following types of devices:
 
@@ -485,7 +485,7 @@ The AllowVideoConferencing parameter specifies whether to allow video conferenci
 
 - $true: Video conferencing is allowed.
 - $false: Video conferencing isn't allowed.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available only on Apple iOS 6+ devices.
 
@@ -509,7 +509,7 @@ The AllowVoiceAssistant parameter specifies whether to allow using the voice ass
 
 - $true: The voice assistant is allowed.
 - $false: The voice assistant isn't allowed.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available only on Apple iOS 6+ devices.
 
@@ -533,7 +533,7 @@ The AllowVoiceDialing parameter specifies whether to allow voice-activated telep
 
 - $true: Voice dialing is allowed.
 - $false: Voice dialing isn't allowed.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available only on Apple iOS 6+ devices.
 
@@ -556,7 +556,7 @@ Accept wildcard characters: False
 The AntiVirusSignatureStatus parameter specifies the antivirus signature status. Valid values for this parameter are:
 
 - An integer.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available only on Windows 8.1 RT devices.
 
@@ -579,7 +579,7 @@ Accept wildcard characters: False
 The AntiVirusStatus parameter specifies the antivirus status. Valid values for this parameter are:
 
 - An integer.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available only on Windows 8.1 RT devices.
 
@@ -606,7 +606,7 @@ The AppsRating parameter species the maximum or most restrictive rating of apps
 - Rating9plus
 - Rating12plus
 - Rating17plus
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available only on Apple iOS 6+ devices.
 
@@ -633,7 +633,7 @@ The AutoUpdateStatus parameter specifies the update settings for devices. Valid
 - AutomaticUpdatesRequired
 - DeviceDefault
 - NeverCheckUpdates
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available only on Windows 8.1 RT devices.
 
@@ -657,7 +657,7 @@ The BluetoothEnabled parameter specifies whether to enable or disable Bluetooth
 
 - $true: Bluetooth is enabled.
 - $false: Bluetooth is disabled.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available only on Windows Phone 8.1 devices.
 
@@ -681,7 +681,7 @@ The CameraEnabled parameter specifies whether to enable or disable cameras on de
 
 - $true: Cameras are enabled.
 - $false: Cameras are disabled.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available on the following types of devices:
 
@@ -747,7 +747,7 @@ Accept wildcard characters: False
 The EmailAddress parameter specifies the email address. Valid values are:
 
 - An email address: For example, julia@contoso.com.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 ```yaml
 Type: String
@@ -769,7 +769,7 @@ The EnableRemovableStorage parameter specifies whether removable storage can be
 
 - $true: Removable storage can be used.
 - $false: Removable storage can't be used.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available only on Windows Phone 8.1 devices.
 
@@ -792,7 +792,7 @@ Accept wildcard characters: False
 The ExchangeActiveSyncHost parameter specifies the Exchange ActiveSync host. Valid values for this parameter are:
 
 - A text value.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 ```yaml
 Type: String
@@ -813,7 +813,7 @@ Accept wildcard characters: False
 The FirewallStatus parameter specifies the acceptable firewall status values on devices. Valid values for this parameter are:
 
 - Required
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available only on Windows 8.1 RT devices.
 
@@ -837,7 +837,7 @@ The ForceAppStorePassword parameter specifies whether to require a password to u
 
 - $true: App store passwords are required.
 - $false: App store passwords aren't required.
-- $null (blank): The feature isn't allowed or blocked by the rule. This is the default value.
+- $null (blank): The feature isn't allowed or blocked by the rule. This value is the default.
 
 This setting is available only on Apple iOS 6+ devices.
 
@@ -861,7 +861,7 @@ The ForceEncryptedBackup parameter specifies whether to force encrypted backups
 
 - $true: Encrypted backups are required.
 - $false: Encrypted backups aren't required.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available on the following types of devices:
 
@@ -887,7 +887,7 @@ Accept wildcard characters: False
 The MaxPasswordAttemptsBeforeWipe parameter specifies the number of incorrect password attempts that cause devices to be automatically wiped. Valid values for this parameter are:
 
 - An integer.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available on the following types of devices:
 
@@ -940,7 +940,7 @@ Valid values for the MoviesRating parameter are:
 
 - AllowAll: All movies are allowed, regardless of their rating.
 - DontAllow: No movies are allowed, regardless of their rating.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 Australia
 
@@ -1039,7 +1039,7 @@ Accept wildcard characters: False
 The PasswordComplexity parameter specifies the password complexity. Valid values for this parameter are:
 
 - An integer.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 ```yaml
 Type: Int64
@@ -1060,7 +1060,7 @@ Accept wildcard characters: False
 The PasswordExpirationDays parameter specifies the number of days that the same password can be used on devices before users are required to change their passwords . Valid values for this parameter are:
 
 - An integer.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available on the following types of devices:
 
@@ -1088,7 +1088,7 @@ Accept wildcard characters: False
 The PasswordHistoryCount parameter specifies the minimum number of unique new passwords that are required on devices before an old password can be reused. Valid values for this parameter are:
 
 - An integer.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available on the following types of devices:
 
@@ -1116,7 +1116,7 @@ Accept wildcard characters: False
 The PasswordMinComplexChars parameter specifies the minimum number of complex characters that are required for device passwords. A complex character isn't a letter. Valid values for this parameter are:
 
 - An integer.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 ```yaml
 Type: Int32
@@ -1137,7 +1137,7 @@ Accept wildcard characters: False
 The PasswordMinimumLength parameter specifies the minimum number of characters that are required for device passwords. Valid values for this parameter are:
 
 - An integer.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available on the following types of devices:
 
@@ -1167,7 +1167,7 @@ The PasswordQuality parameter specifies the minimum password quality rating that
 Valid values for this parameter are:
 
 - An integer.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available only on Android 4+ devices.
 
@@ -1191,7 +1191,7 @@ The PasswordRequired parameter specifies whether a password is required to acces
 
 - $true: Device passwords are required.
 - $false: Device passwords aren't required.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available on the following types of devices:
 
@@ -1246,7 +1246,7 @@ The PhoneMemoryEncrypted parameter specifies whether to encrypt the memory on de
 
 - $true: Memory is encrypted.
 - $false: Memory isn't encrypted.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available on the following types of devices:
 
@@ -1273,7 +1273,7 @@ The RegionRatings parameter specifies the rating system (country/region) to use
 
 Valid values for the RegionRating parameter are:
 
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 - au: Australia
 - ca: Canada
 - de: Germany
@@ -1306,7 +1306,7 @@ The RequireEmailProfile parameter specifies whether an email profile is required
 
 - $true: An email profile is required. This value is required for selective wipe on iOS devices.
 - $false: An email profile isn't required.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -1328,7 +1328,7 @@ The SmartScreenEnabled parameter specifies whether to requireWindows SmartScreen
 
 - $true: SmartScreen is enabled.
 - $false: SmartScreen is disabled.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available only on Windows 8.1 RT devices.
 
@@ -1352,7 +1352,7 @@ The SystemSecurityTLS parameter specifies whether TLS encryption is used on devi
 
 - $true: TLS encryption is used.
 - $false: TLS encryption isn't used.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available only on Apple iOS 6+ devices.
 
@@ -1378,7 +1378,7 @@ Valid values for the TVShowsRating parameter are:
 
 - AllowAll: All television shows are allowed, regardless of their rating.
 - DontAllow: No televisions shows are allowed, regardless of their rating.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 Australia
 
@@ -1465,7 +1465,7 @@ Accept wildcard characters: False
 
 The UserAccountControlStatus parameter specifies how User Account Control messages are presented on devices. Valid values for this parameter are:
 
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 - AlwaysNotify
 - NeverNotify
 - NotifyAppChanges
@@ -1511,7 +1511,7 @@ The WLANEnabled parameter specifies whether Wi-Fi is enabled devices. Valid valu
 
 - $true: Wi-Fi is enabled.
 - $false: Wi-Fi is disabled.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available only on Microsoft Windows Phone 8.1 devices.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DeviceConfigurationPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-DeviceConfigurationPolicy.md
index f3e3e885f1..09a319872c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-DeviceConfigurationPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-DeviceConfigurationPolicy.md
@@ -117,7 +117,7 @@ Accept wildcard characters: False
 
 The Enabled parameter specifies whether the policy is enabled. Valid values are:
 
-- $true: The policy is enabled. This is the default value.
+- $true: The policy is enabled. This value is the default.
 - $false: The policy is disabled.
 
 ```yaml
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DeviceConfigurationRule.md b/exchange/exchange-ps/ExchangePowerShell/New-DeviceConfigurationRule.md
index 47cb277d91..73b027f3ff 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-DeviceConfigurationRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-DeviceConfigurationRule.md
@@ -151,7 +151,7 @@ Accept wildcard characters: False
 The AccountName parameter specifies the account name. Valid values for this parameter are:
 
 - A text value.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 ```yaml
 Type: String
@@ -172,7 +172,7 @@ Accept wildcard characters: False
 The AccountUserName parameter specifies the account user name. Valid values for this parameter are:
 
 - A text value.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 ```yaml
 Type: String
@@ -194,7 +194,7 @@ The AllowAppStore parameter specifies whether to allow access to the app store o
 
 - $true: Access to the app store is allowed.
 - $false: Access to the app store isn't allowed.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available on the following types of devices:
 
@@ -221,7 +221,7 @@ The AllowAssistantWhileLocked parameter specifies whether to allow the use of th
 
 - $true: The voice assistant can be used while devices are locked.
 - $false: The voice assistant can't be used while devices are locked.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available only on Apple iOS 6+ devices.
 
@@ -245,7 +245,7 @@ The AllowConvenienceLogon parameter specifies whether to allow convenience logon
 
 - $true: Convenience logons are allowed.
 - $false: Convenience logons aren't allowed.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available only on Windows 8.1 RT devices.
 
@@ -269,7 +269,7 @@ The AllowDiagnosticSubmission parameter specifies whether to allow diagnostic su
 
 - $true: Diagnostic submissions are allowed.
 - $false: Diagnostic submissions aren't allowed.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available on the following types of devices:
 
@@ -297,7 +297,7 @@ The AllowiCloudBackup parameter specifies whether to allow Apple iCloud Backup f
 
 - $true: iCloud Backup is allowed.
 - $false: iCloud Backup isn't allowed.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available on the following types of devices:
 
@@ -324,7 +324,7 @@ The AllowiCloudDocSync parameter specifies whether to allow Apple iCloud Documen
 
 - $true: iCloud Documents & Data sync is allowed.
 - $false: iCloud Documents & Data sync isn't allowed.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available on the following types of devices:
 
@@ -351,7 +351,7 @@ The AllowiCloudPhotoSync parameter specifies whether to allow Apple iCloud Photo
 
 - $true: iCloud Photos sync is allowed.
 - $false: iCloud Photo sync isn't allowed.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available on the following types of devices:
 
@@ -378,7 +378,7 @@ The AllowPassbookWhileLocked parameter specifies whether to allow the use of App
 
 - $true: Passbook is available while devices are locked.
 - $false: Passbook isn't available while devices are locked.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available only on Apple iOS 6+ devices.
 
@@ -402,7 +402,7 @@ The AllowScreenshot parameter specifies whether to allow screenshots on devices.
 
 - $true: Screenshots are allowed.
 - $false: Screenshots aren't allowed.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available on the following types of devices:
 
@@ -429,7 +429,7 @@ The AllowSimplePassword parameter specifies whether to allow simple or non-compl
 
 - $true: Simple passwords are allowed.
 - $false: Simple passwords aren't allowed.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available on the following types of devices:
 
@@ -457,7 +457,7 @@ The AllowVideoConferencing parameter specifies whether to allow video conferenci
 
 - $true: Video conferencing is allowed.
 - $false: Video conferencing isn't allowed.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available only on Apple iOS 6+ devices.
 
@@ -481,7 +481,7 @@ The AllowVoiceAssistant parameter specifies whether to allow using the voice ass
 
 - $true: The voice assistant is allowed.
 - $false: The voice assistant isn't allowed.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available only on Apple iOS 6+ devices.
 
@@ -505,7 +505,7 @@ The AllowVoiceDialing parameter specifies whether to allow voice-activated telep
 
 - $true: Voice dialing is allowed.
 - $false: Voice dialing isn't allowed.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available only on Apple iOS 6+ devices.
 
@@ -528,7 +528,7 @@ Accept wildcard characters: False
 The AntiVirusSignatureStatus parameter specifies the antivirus signature status. Valid values for this parameter are:
 
 - An integer.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available only on Windows 8.1 RT devices.
 
@@ -551,7 +551,7 @@ Accept wildcard characters: False
 The AntiVirusStatus parameter specifies the antivirus status. Valid values for this parameter are:
 
 - An integer.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available only on Windows 8.1 RT devices.
 
@@ -578,7 +578,7 @@ The AppsRating parameter species the maximum or most restrictive rating of apps
 - Rating9plus
 - Rating12plus
 - Rating17plus
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available only on Apple iOS 6+ devices.
 
@@ -605,7 +605,7 @@ The AutoUpdateStatus parameter specifies the update settings for devices. Valid
 - AutomaticUpdatesRequired
 - DeviceDefault
 - NeverCheckUpdates
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available only on Windows 8.1 RT devices.
 
@@ -629,7 +629,7 @@ The BluetoothEnabled parameter specifies whether to enable or disable Bluetooth
 
 - $true: Bluetooth is enabled.
 - $false: Bluetooth is disabled.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available only on Windows Phone 8.1 devices.
 
@@ -653,7 +653,7 @@ The CameraEnabled parameter specifies whether to enable or disable cameras on de
 
 - $true: Cameras are enabled.
 - $false: Cameras are disabled.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available on the following types of devices:
 
@@ -719,7 +719,7 @@ Accept wildcard characters: False
 The EmailAddress parameter specifies the email address. Valid values are:
 
 - An email address: For example, julia@contoso.com.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 ```yaml
 Type: String
@@ -741,7 +741,7 @@ The EnableRemovableStorage parameter specifies whether removable storage can be
 
 - $true: Removable storage can be used.
 - $false: Removable storage can't be used.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available only on Windows Phone 8.1 devices.
 
@@ -764,7 +764,7 @@ Accept wildcard characters: False
 The ExchangeActiveSyncHost parameter specifies the Exchange ActiveSync host. Valid values for this parameter are:
 
 - A text value.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 ```yaml
 Type: String
@@ -785,7 +785,7 @@ Accept wildcard characters: False
 The FirewallStatus parameter specifies the acceptable firewall status values on devices. Valid values for this parameter are:
 
 - Required
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available only on Windows 8.1 RT devices.
 
@@ -809,7 +809,7 @@ The ForceAppStorePassword parameter specifies whether to require a password to u
 
 - $true: App store passwords are required.
 - $false: App store passwords aren't required.
-- $null (blank): The feature isn't allowed or blocked by the rule. This is the default value.
+- $null (blank): The feature isn't allowed or blocked by the rule. This value is the default.
 
 This setting is available only on Apple iOS 6+ devices.
 
@@ -833,7 +833,7 @@ The ForceEncryptedBackup parameter specifies whether to force encrypted backups
 
 - $true: Encrypted backups are required.
 - $false: Encrypted backups aren't required.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available on the following types of devices:
 
@@ -859,7 +859,7 @@ Accept wildcard characters: False
 The MaxPasswordAttemptsBeforeWipe parameter specifies the number of incorrect password attempts that cause devices to be automatically wiped. Valid values for this parameter are:
 
 - An integer.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available on the following types of devices:
 
@@ -912,7 +912,7 @@ Valid values for the MoviesRating parameter are:
 
 - AllowAll: All movies are allowed, regardless of their rating.
 - DontAllow: No movies are allowed, regardless of their rating.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 Australia
 
@@ -1011,7 +1011,7 @@ Accept wildcard characters: False
 The PasswordComplexity parameter specifies the password complexity. Valid values for this parameter are:
 
 - An integer.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 ```yaml
 Type: Int64
@@ -1032,7 +1032,7 @@ Accept wildcard characters: False
 The PasswordExpirationDays parameter specifies the number of days that the same password can be used on devices before users are required to change their passwords . Valid values for this parameter are:
 
 - An integer.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available on the following types of devices:
 
@@ -1060,7 +1060,7 @@ Accept wildcard characters: False
 The PasswordHistoryCount parameter specifies the minimum number of unique new passwords that are required on devices before an old password can be reused. Valid values for this parameter are:
 
 - An integer.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available on the following types of devices:
 
@@ -1088,7 +1088,7 @@ Accept wildcard characters: False
 The PasswordMinComplexChars parameter specifies the minimum number of complex characters that are required for device passwords. A complex character isn't a letter. Valid values for this parameter are:
 
 - An integer.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 ```yaml
 Type: Int32
@@ -1109,7 +1109,7 @@ Accept wildcard characters: False
 The PasswordMinimumLength parameter specifies the minimum number of characters that are required for device passwords. Valid values for this parameter are:
 
 - An integer.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available on the following types of devices:
 
@@ -1139,7 +1139,7 @@ The PasswordQuality parameter specifies the minimum password quality rating that
 Valid values for this parameter are:
 
 - An integer.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available only on Android 4+ devices.
 
@@ -1163,7 +1163,7 @@ The PasswordRequired parameter specifies whether a password is required to acces
 
 - $true: Device passwords are required.
 - $false: Device passwords aren't required.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available on the following types of devices:
 
@@ -1218,7 +1218,7 @@ The PhoneMemoryEncrypted parameter specifies whether to encrypt the memory on de
 
 - $true: Memory is encrypted.
 - $false: Memory isn't encrypted.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available on the following types of devices:
 
@@ -1245,7 +1245,7 @@ The RegionRatings parameter specifies the rating system (country/region) to use
 
 Valid values for the RegionRating parameter are:
 
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 - au: Australia
 - ca: Canada
 - de: Germany
@@ -1278,7 +1278,7 @@ The RequireEmailProfile parameter specifies whether an email profile is required
 
 - $true: An email profile is required. This value is required for selective wipe on iOS devices.
 - $false: An email profile isn't required.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -1300,7 +1300,7 @@ The SmartScreenEnabled parameter specifies whether to requireWindows SmartScreen
 
 - $true: SmartScreen is enabled.
 - $false: SmartScreen is disabled.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available only on Windows 8.1 RT devices.
 
@@ -1324,7 +1324,7 @@ The SystemSecurityTLS parameter specifies whether TLS encryption is used on devi
 
 - $true: TLS encryption is used.
 - $false: TLS encryption isn't used.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available only on Apple iOS 6+ devices.
 
@@ -1350,7 +1350,7 @@ Valid values for the TVShowsRating parameter are:
 
 - AllowAll: All television shows are allowed, regardless of their rating.
 - DontAllow: No televisions shows are allowed, regardless of their rating.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 Australia
 
@@ -1437,7 +1437,7 @@ Accept wildcard characters: False
 
 The UserAccountControlStatus parameter specifies how User Account Control messages are presented on devices. Valid values for this parameter are:
 
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 - AlwaysNotify
 - NeverNotify
 - NotifyAppChanges
@@ -1483,7 +1483,7 @@ The WLANEnabled parameter specifies whether Wi-Fi is enabled devices. Valid valu
 
 - $true: Wi-Fi is enabled.
 - $false: Wi-Fi is disabled.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available only on Microsoft Windows Phone 8.1 devices.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DeviceTenantPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-DeviceTenantPolicy.md
index dbfdd374b4..e41f6654c8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-DeviceTenantPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-DeviceTenantPolicy.md
@@ -98,7 +98,7 @@ Accept wildcard characters: False
 
 The Enabled parameter specifies whether the policy is enabled. Valid values are:
 
-- $true: The policy is enabled. This is the default value.
+- $true: The policy is enabled. This value is the default.
 - $false: The policy is disabled.
 
 ```yaml
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DistributionGroup.md b/exchange/exchange-ps/ExchangePowerShell/New-DistributionGroup.md
index ac577a237c..a8e5f0ae79 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-DistributionGroup.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-DistributionGroup.md
@@ -13,7 +13,7 @@ title: New-DistributionGroup
 # New-DistributionGroup
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the New-DistributionGroup cmdlet to create distribution groups and mail-enabled security groups.
 
@@ -60,7 +60,7 @@ You can use the New-DistributionGroup cmdlet to create the following types of gr
 
 Distribution groups are used to consolidate groups of recipients into a single point of contact for email messages. Distribution groups aren't security principals, and therefore can't be assigned permissions. However, you can assign permissions to mail-enabled security groups.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 In Exchange Server, the [CommonParameters](https://go.microsoft.com/fwlink/p/?LinkID=113216) InformationVariable and InformationAction don't work.
 
@@ -180,7 +180,7 @@ This parameter is available only in the cloud-based service.
 The BccBlocked parameter specifies whether members of the group don't receive messages if the group is used in the Bcc line. Valid values are:
 
 - $true: If the group is used in the Bcc line, members of the group don't receive the message, and the sender receives a non-delivery report (also known as an NDR or bounce message). Other recipients of the message aren't blocked. If an external sender uses the group in the Bcc line, members of the group aren't blocked. For nested groups, the message is blocked only for members of the top-level group.
-- $false: There are no restrictions for using the group in the Bcc line of messages. This is the default value.
+- $false: There are no restrictions for using the group in the Bcc line of messages. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -201,7 +201,7 @@ Accept wildcard characters: False
 The ByPassNestedModerationEnabled parameter specifies how to handle message approval when a moderated group contains other moderated groups as members. Valid values are:
 
 - $true: After a moderator approves a message sent to the group, the message is automatically approved for all other moderated groups that are members of the group.
-- $false: After a moderator approves a message sent to the group, separate approval is required for each moderated group that's a member of the group. This is the default value.
+- $false: After a moderator approves a message sent to the group, separate approval is required for each moderated group that's a member of the group. This value is the default.
 
 This parameter can be used only by top-level organization and tenant administrators.
 
@@ -418,8 +418,8 @@ Accept wildcard characters: False
 
 The MemberDepartRestriction parameter specifies the restrictions that you put on requests to leave the group. Valid values are:
 
-- Open: Members can leave the group without approval from one of the group owners. This is the default value for universal distribution groups. You can't use this value on universal security groups.
-- Closed: Members can't remove themselves from the group, and requests to leave the group are rejected automatically. Group membership is controlled by the group owners. This is the default value for universal security groups.
+- Open: Members can leave the group without approval from one of the group owners. This value is the default for universal distribution groups. You can't use this value on universal security groups.
+- Closed: Members can't remove themselves from the group, and requests to leave the group are rejected automatically. Group membership is controlled by the group owners. This value is the default for universal security groups.
 
 ```yaml
 Type: MemberUpdateType
@@ -440,7 +440,7 @@ Accept wildcard characters: False
 The MemberJoinRestriction parameter specifies the restrictions that you put on requests to join the group. Valid values are:
 
 - Open: Users can add themselves to the group without approval from a group owner. You can't use this value on universal security groups.
-- Closed: Users can't add themselves to the group, and requests to join the group are rejected automatically. Group membership is controlled by the group owners. This is the default value on universal security groups and universal distribution groups.
+- Closed: Users can't add themselves to the group, and requests to join the group are rejected automatically. Group membership is controlled by the group owners. This value is the default on universal security groups and universal distribution groups.
 - ApprovalRequired: Users can request to join the group. The user is added to the group after the request is approved by one of the group owners. Although you can use this value on universal security groups, user requests to join the group aren't sent to the group owners, so this setting is only effective on universal distribution groups.
 
 ```yaml
@@ -472,7 +472,7 @@ You can enter multiple values separated by commas. If the values contain spaces
 
 After you create the group, you use the Get-DistributionGroupMember cmdlet to view the group members, and the Add-DistributionGroupMember, Remove-DistributionGroupMember, and Update-DistributionGroupMember cmdlets to manage group membership.
 
-Although it isn't required, it's a good idea to add only security principals (for example, mailboxes and mail users with user accounts or other mail-enabled security groups) to mail-enabled security groups. If you assign permissions to a mail-enabled security group, any members that aren't security principals (for example, mail contacts or distribution groups) won't have the permissions assigned.
+Although it isn't required, it's a good idea to add only security principals (for example, mailboxes and mail users with user accounts or other mail-enabled security groups) to mail-enabled security groups. If you assign permissions to a mail-enabled security group, any members that aren't security principals (for example, mail contacts or distribution groups) don't have the permissions assigned.
 
 The maximum number of entries for this parameter is 10000.
 
@@ -526,7 +526,7 @@ Accept wildcard characters: False
 The ModerationEnabled parameter specifies whether moderation is enabled for this recipient. Valid value are:
 
 - $true: Moderation is enabled for this recipient. Messages sent to this recipient must be approved by a moderator before the messages are delivered.
-- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This is the default value.
+- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This value is the default.
 
 You use the ModeratedBy parameter to specify the moderators.
 
@@ -652,7 +652,7 @@ Accept wildcard characters: False
 
 This parameter is available only in on-premises Exchange.
 
-The SamAccountName parameter (also known as the pre-Windows 2000 user account or group name) specifies an object identifier that's compatible with older versions of Microsoft Windows client and server operating systems. The value can contain letters, numbers, spaces, periods (.), and the following characters: !, #, $, %, ^, &, -, \_, {, }, and ~. The last character can't be a period. Unicode characters are allowed, but accented characters may generate collisions (for example, o and ö match).
+The SamAccountName parameter (also known as the pre-Windows 2000 user account or group name) specifies an object identifier that's compatible with older versions of Microsoft Windows client and server operating systems. The value can contain letters, numbers, spaces, periods (.), and the following characters: !, #, $, %, ^, &, -, \_, {, }, and ~. The last character can't be a period. Unicode characters are allowed, but accented characters might generate collisions (for example, o and ö match).
 
 ```yaml
 Type: String
@@ -672,7 +672,7 @@ Accept wildcard characters: False
 
 The SendModerationNotifications parameter specifies when moderation notification messages are sent. Valid values are:
 
-- Always: Notify all senders when their messages aren't approved. This is the default value.
+- Always: Notify all senders when their messages aren't approved. This value is the default.
 - Internal: Notify senders in the organization when their messages aren't approved.
 - Never: Don't notify anyone when a message isn't approved.
 
@@ -696,7 +696,7 @@ Accept wildcard characters: False
 
 The Type parameter specifies the type of group that you want to create. Valid values are:
 
-- Distribution: A distribution group. These groups can't have permissions assigned. This is the default value.
+- Distribution: A distribution group. These groups can't have permissions assigned. This value is the default.
 - Security: A mail-enabled security group. These groups can have permissions assigned.
 
 The group's scope is always Universal.
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DkimSigningConfig.md b/exchange/exchange-ps/ExchangePowerShell/New-DkimSigningConfig.md
index 0dfaee8eb1..66fa40daa5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-DkimSigningConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-DkimSigningConfig.md
@@ -35,7 +35,7 @@ New-DkimSigningConfig [-DomainName] <SmtpDomainWithSubdomains> [-Enabled] <Boole
 ## DESCRIPTION
 DKIM in Microsoft 365 is an email authentication method that uses a public key infrastructure (PKI), message headers, and CNAME records in DNS to authenticate the message sender, which is stamped in the DKIM-Signature header field. DKIM helps prevent forged sender email addresses (also known as spoofing) by verifying that the domain in the From address matches the domain in the DKIM-Signature header field.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -115,7 +115,7 @@ Accept wildcard characters: False
 
 The BodyCanonicalization parameter specifies the canonicalization algorithm that's used to create and verify the message body part of the DKIM signature. This value effectively controls the sensitivity of DKIM to changes to the message body in transit. Valid values are:
 
-- Relaxed: Changes in whitespace and changes in empty lines at the end of the message body are tolerated. This is the default value.
+- Relaxed: Changes in whitespace and changes in empty lines at the end of the message body are tolerated. This value is the default.
 - Simple: Only changes in empty lines at the end of the message body are tolerated.
 
 ```yaml
@@ -157,7 +157,7 @@ Accept wildcard characters: False
 
 The HeaderCanonicalization parameter specifies the canonicalization algorithm that's used to create and verify the message header part of the DKIM signature. This value effectively controls the sensitivity of DKIM to changes to the message headers in transit. Valid values are:
 
-- Relaxed: Common modifications to the message header are tolerated (for example, Header field line rewrapping, changes in unnecessary whitespace or empty lines, and changes in case for header fields). This is the default value.
+- Relaxed: Common modifications to the message header are tolerated (for example, Header field line rewrapping, changes in unnecessary whitespace or empty lines, and changes in case for header fields). This value is the default.
 - Simple: No changes to the header fields are tolerated.
 
 ```yaml
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DlpCompliancePolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-DlpCompliancePolicy.md
index bc1368c34b..e3be4ce80a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-DlpCompliancePolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-DlpCompliancePolicy.md
@@ -80,21 +80,21 @@ To use this cmdlet in Security & Compliance PowerShell, you need to be assigned
 New-DlpCompliancePolicy -Name "GlobalPolicy" -SharePointLocation All
 ```
 
-This example creates a DLP policy named GlobalPolicy that will be enforced across all SharePoint locations.
+This example creates a DLP policy named GlobalPolicy that's enforced across all SharePoint locations.
 
 ### Example 2
 ```powershell
 New-DlpCompliancePolicy -Name "GlobalPolicy" -Comment "Primary policy" -SharePointLocation "https://my.url","https://my.url2" -OneDriveLocation "https://my.url3","https://my.url4" -Mode Enable
 ```
 
-This example creates a DLP policy named GlobalPolicy for the specified SharePoint and OneDrive locations. The new policy has a descriptive comment and will be enabled on creation.
+This example creates a DLP policy named GlobalPolicy for the specified SharePoint and OneDrive locations. The new policy has a descriptive comment and is enabled on creation.
 
 ### Example 3
 ```powershell
 New-DlpCompliancePolicy -Name "PowerBIPolicy" -Comment "Primary policy" -PowerBIDlpLocation "All" -PowerBIDlpLocationException "workspaceID1","workspaceID2","workspaceID3" -Mode Enable
 ```
 
-This example creates a DLP policy named PowerBIPolicy for all qualifying Power BI workspaces (that is, those hosted on Premium Gen2 capacities) except for the specified workspaces. The new policy has a descriptive comment and will be enabled on creation.
+This example creates a DLP policy named PowerBIPolicy for all qualifying Power BI workspaces (that is, those hosted on Premium Gen2 capacities) except for the specified workspaces. The new policy has a descriptive comment and is enabled on creation.
 
 ### Example 4
 ```powershell
@@ -586,7 +586,7 @@ Accept wildcard characters: False
 
 The Mode parameter specifies the action and notification level of the DLP policy. Valid values are:
 
-- Enable: The policy is enabled for actions and notifications. This is the default value.
+- Enable: The policy is enabled for actions and notifications. This value is the default.
 - Disable: The policy is disabled.
 - TestWithNotifications: Simulation mode where no actions are taken, but notifications **are** sent.
 - TestWithoutNotifications: Simulation mode where no actions are taken, and no notifications are sent.
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DlpComplianceRule.md b/exchange/exchange-ps/ExchangePowerShell/New-DlpComplianceRule.md
index eceadf5ef2..cd6695eb76 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-DlpComplianceRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-DlpComplianceRule.md
@@ -348,7 +348,7 @@ Accept wildcard characters: False
 
 > Applicable: Security & Compliance
 
-The Policy parameter specifies the existing DLP policy that will contain the new DLP rule. You can use any value that uniquely identifies the policy. For example:
+The Policy parameter specifies the existing DLP policy that contains the new DLP rule. You can use any value that uniquely identifies the policy. For example:
 
 - Name
 - Distinguished name (DN)
@@ -587,7 +587,7 @@ Accept wildcard characters: False
 The BlockAccess parameter specifies an action for the DLP rule that blocks access to the source item when the conditions of the rule are met. Valid values are:
 
 - $true: Blocks further access to the source item that matched the rule. The owner, author, and site owner can still access the item.
-- $false: Allows access to the source item that matched the rule. This is the default value.
+- $false: Allows access to the source item that matched the rule. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -815,7 +815,7 @@ Accept wildcard characters: False
 The Disabled parameter specifies whether the DLP rule is disabled. Valid values are:
 
 - $true: The rule is disabled.
-- $false: The rule is enabled. This is the default value.
+- $false: The rule is enabled. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -1013,7 +1013,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 You can use this condition in DLP policies that are scoped only to Exchange.
 
@@ -1553,7 +1553,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 You can use this exception in DLP policies that are scoped only to Exchange.
 
@@ -1759,7 +1759,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 You can use this exception in DLP policies that are scoped only to Exchange.
 
@@ -2602,7 +2602,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 You can use this condition in DLP policies that are scoped only to Exchange.
 
@@ -2961,7 +2961,7 @@ Accept wildcard characters: False
 
 The NotifyPolicyTipDialogOption parameter specifies a display option for the policy tip. Valid values are:
 
-- Tip: Displays policy tip at the top of the mail. This is the default value.
+- Tip: Displays policy tip at the top of the mail. This value is the default.
 - Dialog: Displays policy tip at the top of the mail and as a popup dialog. (exchange only)
 
 ```yaml
@@ -3366,7 +3366,7 @@ Accept wildcard characters: False
 The ReportSeverityLevel parameter specifies the severity level of the incident report for content detections based on the rule. Valid values are:
 
 - None: You can't select this value if the rule has no actions configured.
-- Low: This is the default value.
+- Low: This value is the default.
 - Medium
 - High
 
@@ -3426,7 +3426,7 @@ The RuleErrorAction parameter specifies what to do if an error is encountered du
 
 - Ignore
 - RetryThenBlock
-- Blank (the value $null): This is the default value.
+- Blank (the value $null): This value is the default.
 
 ```yaml
 Type: Microsoft.Office.CompliancePolicy.PolicyEvaluation.PolicyRuleErrorAction
@@ -3550,11 +3550,11 @@ Accept wildcard characters: False
 
 The SenderAddressLocation parameter specifies where to look for sender addresses in conditions and exceptions that examine sender email addresses. Valid values are:
 
-- Header: Only examine senders in the message headers (for example, the From, Sender, or Reply-To fields). This is the default value.
+- Header: Only examine senders in the message headers (for example, the From, Sender, or Reply-To fields). This value is the default.
 - Envelope: Only examine senders from the message envelope (the MAIL FROM value that was used in the SMTP transmission, which is typically stored in the Return-Path field).
 - HeaderOrEnvelope: Examine senders in the message header and the message envelope.
 
-Note that message envelope searching is available only for the following conditions and exceptions:
+Message envelope searching is available only for the following conditions and exceptions:
 
 - From and ExceptIfFrom
 - FromAddressContainsWords and ExceptIfFromAddressContainsWords
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DlpKeywordDictionary.md b/exchange/exchange-ps/ExchangePowerShell/New-DlpKeywordDictionary.md
index 143373bf26..b788cd9e15 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-DlpKeywordDictionary.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-DlpKeywordDictionary.md
@@ -33,7 +33,7 @@ New-DlpKeywordDictionary -Name <String>
 ```
 
 ## DESCRIPTION
-After you create a custom sensitive information type that specifies the identity (GUID value) of the DLP keyword dictionary, the dictionary will appear in your list of sensitive information types, and you can use it in policies.
+After you create a custom sensitive information type that specifies the identity (GUID value) of the DLP keyword dictionary, the dictionary appears in your list of sensitive information types, and you can use it in policies.
 
 To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions).
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DlpPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-DlpPolicy.md
index 6f345ee2f5..e366f86920 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-DlpPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-DlpPolicy.md
@@ -13,7 +13,7 @@ title: New-DlpPolicy
 # New-DlpPolicy
 
 ## SYNOPSIS
-**Note**: This cmdlet has been retired from the cloud-based service. For more information, see [this blog post](https://techcommunity.microsoft.com/t5/exchange-team-blog/exchange-online-etrs-to-stop-supporting-dlp-policies/ba-p/3886713). Use the New-DlpCompliancePolicy and New-DlpComplianceRule cmdlets instead.
+**Note**: This cmdlet is retired from the cloud-based service. For more information, see [this blog post](https://techcommunity.microsoft.com/t5/exchange-team-blog/exchange-online-etrs-to-stop-supporting-dlp-policies/ba-p/3886713). Use the New-DlpCompliancePolicy and New-DlpComplianceRule cmdlets instead.
 
 This cmdlet is functional only in on-premises Exchange.
 
@@ -38,7 +38,7 @@ New-DlpPolicy [[-Name] <String>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -157,7 +157,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
 
-The Parameters parameter specifies the parameter values that are required by the DLP policy template that you specify using the Template or TemplateData parameters. DLP policy templates may contain parameters that need to be populated with values from your organization. For example, a DLP policy template may include an exception group that defines users who are exempt from the DLP policy.
+The Parameters parameter specifies the parameter values that are required by the DLP policy template that you specify using the Template or TemplateData parameters. DLP policy templates might contain parameters that need to be populated with values from your organization. For example, a DLP policy template might include an exception group that defines users who are exempt from the DLP policy.
 
 This parameter uses the syntax: `@{Parameter1="Value1";Parameter2="Value2"...}`.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DynamicDistributionGroup.md b/exchange/exchange-ps/ExchangePowerShell/New-DynamicDistributionGroup.md
index fa1137e12b..97a2f8867f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-DynamicDistributionGroup.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-DynamicDistributionGroup.md
@@ -13,7 +13,7 @@ title: New-DynamicDistributionGroup
 # New-DynamicDistributionGroup
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the New-DynamicDistributionGroup cmdlet to create dynamic distribution groups. A dynamic distribution group queries mail-enabled objects and builds the group membership based on the results. The group membership is recalculated whenever an email message is sent to the group.
 
@@ -86,7 +86,7 @@ The Conditional parameters that are used with the IncludedRecipients parameter a
 
 To create flexible filters that use any available recipient property and that aren't subject to these limitations, you can use the RecipientFilter parameter to create a custom OPATH filter.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -766,7 +766,7 @@ Accept wildcard characters: False
 The ModerationEnabled parameter specifies whether moderation is enabled for this recipient. Valid value are:
 
 - $true: Moderation is enabled for this recipient. Messages sent to this recipient must be approved by a moderator before the messages are delivered.
-- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This is the default value.
+- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This value is the default.
 
 You use the ModeratedBy parameter to specify the moderators.
 
@@ -844,7 +844,7 @@ The RecipientContainer parameter specifies a filter that's based on the recipien
 
 If you don't use this parameter, the default value is the OU where the object was created.
 
-Note that the RecipientContainer property can't be blank. The group is always limited to looking for recipients in a specific location (the value you specify for this parameter, or the location where the group was created).
+The RecipientContainer property can't be blank. The group is always limited to looking for recipients in a specific location (the value you specify for this parameter, or the location where the group was created).
 
 **Note**: Although this parameter is available in Exchange Online, there's only one usable OU in an Exchange Online organization, so using this parameter has no effect.
 
@@ -866,7 +866,7 @@ Accept wildcard characters: False
 
 The SendModerationNotifications parameter specifies when moderation notification messages are sent. Valid values are:
 
-- Always: Notify all senders when their messages aren't approved. This is the default value.
+- Always: Notify all senders when their messages aren't approved. This value is the default.
 - Internal: Notify senders in the organization when their messages aren't approved.
 - Never: Don't notify anyone when a message isn't approved.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-EOPProtectionPolicyRule.md b/exchange/exchange-ps/ExchangePowerShell/New-EOPProtectionPolicyRule.md
index 93ddfc0f15..02b42f2322 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-EOPProtectionPolicyRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-EOPProtectionPolicyRule.md
@@ -44,7 +44,7 @@ For more information about preset security policies in PowerShell, see [Preset s
 > [!IMPORTANT]
 > Different types of recipient conditions use AND logic (the recipient must satisfy **all** specified conditions). Different types of recipient exceptions use OR logic (the recipient must satisfy **any** of the specified exceptions). For more information, see [Profiles in preset security policies](https://learn.microsoft.com/defender-office-365/preset-security-policies#profiles-in-preset-security-policies).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -83,7 +83,7 @@ Accept wildcard characters: False
 
 The AntiPhishPolicy parameter specifies the existing anti-phishing policy that's associated with the preset security policy.
 
-If you ever turned on the preset security policy in the Microsoft Defender portal, the name of the anti-phishing policy will be one of the following values:
+If you ever turned on the preset security policy in the Microsoft Defender portal, the name of the anti-phishing policy is one of the following values:
 
 - Standard Preset Security Policy\<13-digit number\>. For example, `Standard Preset Security Policy1622650005393`.
 - Strict Preset Security Policy\<13-digit number\>. For example, `Strict Preset Security Policy1642034844713`.
@@ -108,7 +108,7 @@ Accept wildcard characters: False
 
 The HostedContentFilterPolicy parameter specifies the existing anti-spam policy that's associated with the preset security policy.
 
-If you ever turned on the preset security policy in the Microsoft Defender portal, the name of the anti-spam policy will be one of the following values:
+If you ever turned on the preset security policy in the Microsoft Defender portal, the name of the anti-spam policy is one of the following values:
 
 - Standard Preset Security Policy\<13-digit number\>. For example, `Standard Preset Security Policy1622650006407`.
 - Strict Preset Security Policy\<13-digit number\>. For example, `Strict Preset Security Policy1642034847393`.
@@ -133,7 +133,7 @@ Accept wildcard characters: False
 
 The HostedContentFilterPolicy parameter specifies the existing anti-malware policy that's associated with the preset security policy.
 
-If you ever turned on the preset security policy in the Microsoft Defender portal, the name of the anti-malware policy will be one of the following values:
+If you ever turned on the preset security policy in the Microsoft Defender portal, the name of the anti-malware policy is one of the following values:
 
 - Standard Preset Security Policy\<13-digit number\>. For example, `Standard Preset Security Policy1622650007658`.
 - Strict Preset Security Policy\<13-digit number\>. For example, `Strict Preset Security Policy1642034871908`.
@@ -197,7 +197,7 @@ Accept wildcard characters: False
 
 The Enabled parameter specifies whether the rule is enabled. Valid values are:
 
-- $true: The rule is enabled. The State value of the rule is Enabled. This is the default value.
+- $true: The rule is enabled. The State value of the rule is Enabled. This value is the default.
 - $false: The rule is disabled. The State value of the rule is Disabled.
 
 After you create the rule, you turn on or turn off the preset security policy using one of the following commands:
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-EcpVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/New-EcpVirtualDirectory.md
index 99729e8485..d7db96a683 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-EcpVirtualDirectory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-EcpVirtualDirectory.md
@@ -41,7 +41,7 @@ New-EcpVirtualDirectory [-AppPoolId <String>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -121,7 +121,7 @@ The ExtendedProtectionFlags parameter specifies custom settings for Extended Pro
 - AllowDotlessSPN: Required if you want to use Service Principal Name (SPN) values that don't contain FQDNs (for example, HTTP/ContosoMail instead of HTTP/mail.contoso.com). You specify SPNs with the ExtendedProtectionSPNList parameter. This setting makes Extended Protection for Authentication less secure because dotless certificates aren't unique, so it isn't possible to ensure that the client-to-proxy connection was established over a secure channel.
 - NoServiceNameCheck: The SPN list isn't checked to validate a channel binding token. This setting makes Extended Protection for Authentication less secure. We generally don't recommend this setting.
 - Proxy: A proxy server is responsible for terminating the SSL channel. To use this setting, you need to register an SPN by using the ExtendedProtectionSPNList parameter.
-- ProxyCoHosting: HTTP and HTTPS traffic may be accessing the virtual directory and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server.
+- ProxyCoHosting: HTTP and HTTPS traffic might be accessing the virtual directory and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server.
 
 ```yaml
 Type: MultiValuedProperty
@@ -141,7 +141,7 @@ Accept wildcard characters: False
 
 The ExtendedProtectionSPNList parameter specifies a list of valid Service Principal Names (SPNs) if you're using Extended Protection for Authentication on the virtual directory. Valid values are:
 
-- $null: This is the default value.
+- $null: This value is the default.
 - Single SPN or comma delimited list of valid SPNs: The SPN value format is `Protocol\FQDN`. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter.
 
 ```yaml
@@ -162,8 +162,8 @@ Accept wildcard characters: False
 
 The ExtendedProtectionTokenChecking parameter defines how you want to use Extended Protection for Authentication on the virtual directory. Extended Protection for Authentication isn't enabled by default. Valid values are:
 
-- None: Extended Protection for Authentication isn't be used on the virtual directory. This is the default value.
-- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication will work, but may not be as secure as connections that use Extended Protection for Authentication.
+- None: Extended Protection for Authentication isn't be used on the virtual directory. This value is the default.
+- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication work, but might not be as secure as connections that use Extended Protection for Authentication.
 - Require: Extended Protection for Authentication is used for all connections between clients and the virtual directory. If either the client or server doesn't support it, the connection will fail. If you use this value, you also need to set an SPN value for the ExtendedProtectionSPNList parameter.
 
 **Note**: If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter.
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-EdgeSubscription.md b/exchange/exchange-ps/ExchangePowerShell/New-EdgeSubscription.md
index 9df879d76c..0f3c1a24b3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-EdgeSubscription.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-EdgeSubscription.md
@@ -36,9 +36,9 @@ New-EdgeSubscription [-AccountExpiryDuration <TimeSpan>]
 ```
 
 ## DESCRIPTION
-The Edge Transport server doesn't have access to Active Directory. All configuration and recipient information is stored in the Active Directory Lightweight Directory Services (AD LDS) instance. The New-EdgeSubscription cmdlet creates the Edge Subscription file that will be imported on a Mailbox server in the Active Directory site to which you want to subscribe this Edge Transport server.
+The Edge Transport server doesn't have access to Active Directory. All configuration and recipient information is stored in the Active Directory Lightweight Directory Services (AD LDS) instance. The New-EdgeSubscription cmdlet creates the Edge Subscription file to import on a Mailbox server in the Active Directory site where you want to subscribe this Edge Transport server.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -73,7 +73,7 @@ This example also imports the Edge Subscription file generated in Example 1 to t
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-The AccountExpiryDuration parameter specifies how soon the EdgeSync bootstrap replication account (ESBRA) created by this command will expire.
+The AccountExpiryDuration parameter specifies how soon the EdgeSync bootstrap replication account (ESBRA) created by this command expires.
 
 To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes and ss = seconds.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-EdgeSyncServiceConfig.md b/exchange/exchange-ps/ExchangePowerShell/New-EdgeSyncServiceConfig.md
index a8168f3519..c64ac8e72c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-EdgeSyncServiceConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-EdgeSyncServiceConfig.md
@@ -43,7 +43,7 @@ New-EdgeSyncServiceConfig [-ConfigurationSyncInterval <EnhancedTimeSpan>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -224,7 +224,7 @@ Accept wildcard characters: False
 
 The LogLevel parameter specifies the EdgeSync logging level. Valid values are:
 
-- None (This is the default value)
+- None (default value)
 - Low
 - Medium
 - High
@@ -275,7 +275,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value of the LogMaxFileSize parameter must be less than or equal to the value of the LogMaxDirectorySize parameter. The valid input range for either parameter is from 1 through 9223372036854775807 bytes. If you enter a value of unlimited, no size limit is imposed on the EdgeSyncLLog directory.
 
@@ -305,7 +305,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value of the LogMaxFileSize parameter must be less than or equal to the value of the LogMaxDirectorySize parameter. The valid input range for either parameter is from 1 through 9223372036854775807 bytes. If you enter a value of unlimited, no size limit is imposed on the EdgeSyncLog files.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-EmailAddressPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-EmailAddressPolicy.md
index 6b5b760e67..aaa242cc86 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-EmailAddressPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-EmailAddressPolicy.md
@@ -13,7 +13,7 @@ title: New-EmailAddressPolicy
 # New-EmailAddressPolicy
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the New-EmailAddressPolicy cmdlet to create email address policies. In Exchange Online, email address policies are available only for Microsoft 365 Groups.
 
@@ -141,7 +141,7 @@ The Conditional parameters that are used with the IncludedRecipients parameter a
 
 To create flexible filters that use any available recipient property and that aren't subject to these limitations, you can use the RecipientFilter parameter to create an OPATH filter.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -793,7 +793,7 @@ The DisabledEmailAddressTemplates parameter specifies the proxy email addresses
 
 Valid syntax for this parameter is `Type:AddressFormat`:
 
-- Type: A valid email address type as described in the "Address types" section in [Email address policies in Exchange Server](https://learn.microsoft.com/Exchange/email-addresses-and-address-books/email-address-policies/email-address-policies). For example, smtp or X400. Note that you can't use SMTP to specify a disabled primary SMTP email address.
+- Type: A valid email address type as described in the "Address types" section in [Email address policies in Exchange Server](https://learn.microsoft.com/Exchange/email-addresses-and-address-books/email-address-policies/email-address-policies). For example, smtp or X400. You can't use SMTP to specify a disabled primary SMTP email address.
 - AddressFormat: For SMTP email addresses, a domain or subdomain that's configured as accepted domain (authoritative or internal relay), and valid variables and ASCII text characters as described in the "Address formats" section in [Email address policies in Exchange Server](https://learn.microsoft.com/Exchange/email-addresses-and-address-books/email-address-policies/email-address-policies). For example: alias@contoso.com requires the value `%m@contoso.com`, and firstname.lastname@contoso.com requires the value `%g.%s@contoso.com`.
 
 You can specify multiple disabled email address templates separated by commas: `"[Type1:]EmailAddress1","[Type2:]EmailAddress2",..."[TypeN:]EmailAddressN"`.
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ExchangeCertificate.md b/exchange/exchange-ps/ExchangePowerShell/New-ExchangeCertificate.md
index 365938a134..9c2195d866 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-ExchangeCertificate.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-ExchangeCertificate.md
@@ -72,7 +72,7 @@ There are many factors to consider when you configure certificates for Transport
 
 Secure Sockets Layer (SSL) is being replaced by Transport Layer Security (TLS) as the protocol that's used to encrypt data sent between computer systems. They're so closely related that the terms "SSL" and "TLS" (without versions) are often used interchangeably. Because of this similarity, references to "SSL" in Exchange topics, the Exchange admin center, and the Exchange Management Shell have often been used to encompass both the SSL and TLS protocols. Typically, "SSL" refers to the actual SSL protocol only when a version is also provided (for example, SSL 3.0). To find out why you should disable the SSL protocol and switch to TLS, check out [Protecting you against the SSL 3.0 vulnerability](https://azure.microsoft.com/blog/protecting-against-the-ssl-3-0-vulnerability/).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -431,7 +431,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-This parameter has been deprecated and is no longer used.
+This parameter is deprecated and no longer used.
 
 ```yaml
 Type: X509Certificate2
@@ -452,7 +452,7 @@ Accept wildcard characters: False
 The KeySize parameter specifies the size (in bits) of the RSA public key that's associated with the new certificate request or self-signed certificate. Valid values are:
 
 - 1024
-- 2048 (This is the default value)
+- 2048 (default value)
 - 4096
 
 ```yaml
@@ -474,7 +474,7 @@ Accept wildcard characters: False
 The PrivateKeyExportable parameter specifies whether the certificate has an exportable private key, and controls whether you can export the certificate from the server (and import the certificate on other servers). Valid values are:
 
 - $true: The private key is exportable, so you can export the certificate from the server.
-- $false: The private key isn't exportable, so you can't export the certificate. This is the default value.
+- $false: The private key isn't exportable, so you can't export the certificate. This value is the default.
 
 ```yaml
 Type: Boolean
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ExchangeSettings.md b/exchange/exchange-ps/ExchangePowerShell/New-ExchangeSettings.md
index a39cde59db..230a474641 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-ExchangeSettings.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-ExchangeSettings.md
@@ -31,7 +31,7 @@ New-ExchangeSettings [-Name] <String>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ExoPhishSimOverrideRule.md b/exchange/exchange-ps/ExchangePowerShell/New-ExoPhishSimOverrideRule.md
index 1c3e6a1a8f..89aac16ff6 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-ExoPhishSimOverrideRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-ExoPhishSimOverrideRule.md
@@ -34,7 +34,7 @@ New-ExoPhishSimOverrideRule -Policy <PolicyIdParameter> -SenderIpRanges <MultiVa
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -43,7 +43,7 @@ You need to be assigned permissions before you can run this cmdlet. Although thi
 New-ExoPhishSimOverrideRule -Policy PhishSimOverridePolicy -Domains fabrikam.com,wingtiptoys.com -SenderIpRanges 192.168.1.55
 ```
 
-This example creates a new phishing simulation override rule with the specified settings. Regardless of the Name value specified, the rule name will be `_Exe:PhishSimOverr:<GUID\>` \[sic\] where \<GUID\> is a unique GUID value (for example, 6fed4b63-3563-495d-a481-b24a311f8329).
+This example creates a new phishing simulation override rule with the specified settings. Regardless of the Name value specified, the rule name is `_Exe:PhishSimOverr:<GUID\>` \[sic\] where \<GUID\> is a unique GUID value (for example, 6fed4b63-3563-495d-a481-b24a311f8329).
 
 ## PARAMETERS
 
@@ -182,7 +182,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online
 
-The Name parameter specifies the name for the policy. Regardless of the value you specify, the name will be `_Exe:PhishSimOverr:<GUID\>` \[sic\] where \<GUID\> is a unique GUID value (for example, 6fed4b63-3563-495d-a481-b24a311f8329).
+The Name parameter specifies the name for the policy. Regardless of the value you specify, the name is `_Exe:PhishSimOverr:<GUID\>` \[sic\] where \<GUID\> is a unique GUID value (for example, 6fed4b63-3563-495d-a481-b24a311f8329).
 
 ```yaml
 Type: String
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ExoSecOpsOverrideRule.md b/exchange/exchange-ps/ExchangePowerShell/New-ExoSecOpsOverrideRule.md
index 919af1904f..675ba08cc7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-ExoSecOpsOverrideRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-ExoSecOpsOverrideRule.md
@@ -33,7 +33,7 @@ New-ExoSecOpsOverrideRule -Policy <PolicyIdParametert>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -42,7 +42,7 @@ You need to be assigned permissions before you can run this cmdlet. Although thi
 New-ExoSecOpsOverrideRule -Name SecOpsOverrideRule -Policy SecOpsOverridePolicy
 ```
 
-This example creates the SecOps mailbox override rule with the specified settings. Regardless of the Name value specified, the rule name will be `_Exe:SecOpsOverrid:<GUID\>` \[sic\] where \<GUID\> is a unique GUID value (for example, 312c23cf-0377-4162-b93d-6548a9977efb).
+This example creates the SecOps mailbox override rule with the specified settings. Regardless of the Name value specified, the rule name is `_Exe:SecOpsOverrid:<GUID\>` \[sic\] where \<GUID\> is a unique GUID value (for example, 312c23cf-0377-4162-b93d-6548a9977efb).
 
 ## PARAMETERS
 
@@ -127,7 +127,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online
 
-The Name parameter specifies the name for the policy. Regardless of the value you specify, the name will be `_Exe:SecOpsOverrid:<GUID\>` \[sic\] where \<GUID\> is a unique GUID value (for example, 312c23cf-0377-4162-b93d-6548a9977ef).
+The Name parameter specifies the name for the policy. Regardless of the value you specify, the name is `_Exe:SecOpsOverrid:<GUID>` \[sic\] where \<GUID\> is a unique GUID value (for example, 312c23cf-0377-4162-b93d-6548a9977ef).
 
 ```yaml
 Type: String
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-FederationTrust.md b/exchange/exchange-ps/ExchangePowerShell/New-FederationTrust.md
index 1ef2e0094b..15c47b377e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-FederationTrust.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-FederationTrust.md
@@ -51,7 +51,7 @@ Federation trusts are trusts created between an Exchange organization and the Mi
 
 For more information, see [Federation](https://learn.microsoft.com/exchange/federation-exchange-2013-help).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-Fingerprint.md b/exchange/exchange-ps/ExchangePowerShell/New-Fingerprint.md
index f72b4bc2e4..223d295bfa 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-Fingerprint.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-Fingerprint.md
@@ -15,7 +15,7 @@ title: New-Fingerprint
 ## SYNOPSIS
 This cmdlet is functional only in on-premises Exchange.
 
-**Note**: In Exchange Online, this cmdlet has been replaced by the [New-DlpFingerPrint](https://learn.microsoft.com/powershell/module/exchangepowershell/new-dlpfingerprint) cmdlet in Security & Compliance PowerShell.
+**Note**: In Exchange Online, this cmdlet is replaced by the [New-DlpFingerPrint](https://learn.microsoft.com/powershell/module/exchangepowershell/new-dlpfingerprint) cmdlet in Security & Compliance PowerShell.
 
 Use the New-Fingerprint cmdlet to create document fingerprints that are used with data classification rules. Because the results of New-Fingerprint are not stored outside of the data classification rule, you always run New-Fingerprint and New-DataClassification or Set-DataClassification in the same PowerShell session.
 
@@ -33,7 +33,7 @@ New-Fingerprint [[-FileData] <Byte[]>] -Description <String>
 ## DESCRIPTION
 Classification rule packages are used by data loss prevention (DLP) to detect sensitive content in messages.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ForeignConnector.md b/exchange/exchange-ps/ExchangePowerShell/New-ForeignConnector.md
index 38a27b3040..4dc46016af 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-ForeignConnector.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-ForeignConnector.md
@@ -34,7 +34,7 @@ New-ForeignConnector [-Name] <String> -AddressSpaces <MultiValuedProperty>
 ## DESCRIPTION
 A Foreign connector uses a Drop directory in the Transport service of a Mailbox server to send messages to a local messaging server that doesn't use SMTP as its primary transport mechanism. These messaging servers are known as foreign gateway servers. Non-Microsoft fax gateway servers are examples of foreign gateway servers. The address spaces assigned to a Foreign connector can be SMTP or non-SMTP.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -77,7 +77,7 @@ Accept wildcard characters: False
 
 The AddressSpaces parameter specifies the domain names to which the Foreign connector sends messages. The complete syntax for entering each address space is: `AddressSpaceType:AddressSpace;AddressSpaceCost`.
 
-- AddressSpaceType: The address space type may be SMTP, X400, or any other text string. If you omit the address space type, an SMTP address space type is assumed.
+- AddressSpaceType: The address space type might be SMTP, X400, or any other text string. If you omit the address space type, an SMTP address space type is assumed.
 - AddressSpace: For SMTP address space types, the address space that you enter must be RFC 1035-compliant. For example, \*, \*.com, and \*.contoso.com are permitted, but \*contoso.com isn't permitted. For X.400 address space types, the address space that you enter must be RFC 1685-compliant, such as o=MySite;p=MyOrg;a=adatum;c=us. For all other values of an address type, you can enter any text for the address space.
 - AddressSpaceCost: The valid input range for the cost is from 1 through 100. A lower cost indicates a better route. If you omit the address space cost, a cost of 1 is assumed. If you enter a non-SMTP address space that contains the semicolon character (;), you must specify the address space cost.
 
@@ -88,7 +88,7 @@ If you specify the address space type or the address space cost, you must enclos
 - "SMTP:contoso.com"
 - contoso.com
 
-You may specify multiple address spaces by separating the address spaces with commas, for example: `contoso.com,fabrikam.com`. If you specify the address space type or the address space cost, you must enclose the address space in quotation marks ("), for example: `"contoso.com;2","fabrikam.com;3"`.
+You might specify multiple address spaces by separating the address spaces with commas, for example: `contoso.com,fabrikam.com`. If you specify the address space type or the address space cost, you must enclose the address space in quotation marks ("), for example: `"contoso.com;2","fabrikam.com;3"`.
 
 ```yaml
 Type: MultiValuedProperty
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-GlobalAddressList.md b/exchange/exchange-ps/ExchangePowerShell/New-GlobalAddressList.md
index a51e891a50..e642369e00 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-GlobalAddressList.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-GlobalAddressList.md
@@ -13,7 +13,7 @@ title: New-GlobalAddressList
 # New-GlobalAddressList
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the New-GlobalAddressList cmdlet to create a global address list (GAL).
 
@@ -70,7 +70,7 @@ The Conditional parameters that are used with the IncludedRecipients parameter a
 
 To create flexible filters that use any available recipient property and that aren't subject to these limitations, you can use the RecipientFilter parameter to create an OPATH filter.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-HoldCompliancePolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-HoldCompliancePolicy.md
index f791c26aab..38416ce39a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-HoldCompliancePolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-HoldCompliancePolicy.md
@@ -17,7 +17,7 @@ This cmdlet is available only in Security & Compliance PowerShell. For more info
 
 Use the New-HoldCompliancePolicy cmdlet to create new preservation policies in the Microsoft Purview compliance portal.
 
-**Note**: The New-HoldCompliancePolicy cmdlet has been replaced by the New-RetentionCompliancePolicy cmdlet. If you have scripts that use New-HoldCompliancePolicy, update them to use New-RetentionCompliancePolicy.
+**Note**: The New-HoldCompliancePolicy cmdlet is replaced by the New-RetentionCompliancePolicy cmdlet. If you have scripts that use New-HoldCompliancePolicy, update them to use New-RetentionCompliancePolicy.
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
@@ -37,7 +37,7 @@ New-HoldCompliancePolicy [-Name] <String>
 ```
 
 ## DESCRIPTION
-New policies are not valid and will not be applied until a preservation rule is added to the policy.
+New policies are not valid and aren't applied until a preservation rule is added to the policy.
 
 To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions).
 
@@ -115,7 +115,7 @@ Accept wildcard characters: False
 
 The Enabled parameter specifies whether the policy is enabled or disabled. Valid values are:
 
-- $true: The policy is enabled. This is the default value.
+- $true: The policy is enabled. This value is the default.
 - $false: The policy is disabled.
 
 ```yaml
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-HoldComplianceRule.md b/exchange/exchange-ps/ExchangePowerShell/New-HoldComplianceRule.md
index 59af4874f5..8dab017d8b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-HoldComplianceRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-HoldComplianceRule.md
@@ -17,7 +17,7 @@ This cmdlet is available only in Security & Compliance PowerShell. For more info
 
 Use the New-HoldComplianceRule cmdlet to create new preservation rules in the Microsoft Purview compliance portal.
 
-**Note**: The New-HoldComplianceRule cmdlet has been replaced by the New-RetentionComplianceRule cmdlet. If you have scripts that use New-HoldComplianceRule, update them to use New-RetentionComplianceRule.
+**Note**: The New-HoldComplianceRule cmdlet is replaced by the New-RetentionComplianceRule cmdlet. If you have scripts that use New-HoldComplianceRule, update them to use New-RetentionComplianceRule.
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
@@ -49,7 +49,7 @@ To use this cmdlet in Security & Compliance PowerShell, you need to be assigned
 New-HoldComplianceRule -Name SeptOneYear -Policy "Internal Company Policy" -ContentDateFrom "09/10/14 5:00 PM" -ContentDateTo "09/10/15 5:00 PM" -HoldContent Unlimited
 ```
 
-This example creates a new preservation rule named SeptOneYear and adds it to the existing preservation policy named "Internal Company Policy". Content created or updated between the specified dates will be held indefinitely.
+This example creates a new preservation rule named SeptOneYear and adds it to the existing preservation policy named "Internal Company Policy". Content created or updated between the specified dates is held indefinitely.
 
 ## PARAMETERS
 
@@ -237,7 +237,7 @@ The HoldDurationDisplayHint parameter specifies the units that are used to displ
 - Months
 - Years
 
-For example, if this parameter is set to the value Years, and the HoldContent parameter is set to the value 365, the Microsoft Purview compliance portal will display 1 year as the content hold duration.
+For example, if this parameter is set to the value Years, and the HoldContent parameter is set to the value 365, the Microsoft Purview compliance portal displays 1 year as the content hold duration.
 
 ```yaml
 Type: HoldDurationHint
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-HostedContentFilterPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-HostedContentFilterPolicy.md
index 8bb8f78675..94dea10d3e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-HostedContentFilterPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-HostedContentFilterPolicy.md
@@ -84,7 +84,7 @@ New-HostedContentFilterPolicy [-Name] <String>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 For more information about the limits for allowed and blocked senders, see [Exchange Online Protection Limits](https://learn.microsoft.com/office365/servicedescriptions/exchange-online-protection-service-description/exchange-online-protection-limits).
 
@@ -139,7 +139,7 @@ For example, if you enter the value `X-This-is-my-custom-header`, the X-header t
 
 If you enter a value that contains spaces or colons (:), the value is ignored, and the default X-header is added to the message (`X-This-Is-Spam: This message appears to be spam.`).
 
-Note that this setting is independent of the AddXHeader value of the TestModeAction parameter.
+This setting is independent of the AddXHeader value of the TestModeAction parameter.
 
 ```yaml
 Type: String
@@ -304,7 +304,7 @@ The BulkSpamAction parameter specifies the action to take on messages that are m
 - AddXHeader: Add the AddXHeaderValue parameter value to the message header and deliver the message.
 - Delete: Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message.
 - ModifySubject: Add the ModifySubject parameter value to the beginning of the subject line, deliver the message, and move the message to the Junk Email folder (same caveats as MoveToJmf).
-- MoveToJmf: This is the default value. Deliver the message to the Junk Email folder in the recipient's mailbox. Hybrid environments need mail flow rules in the on-premises Exchange organization. For instructions, see [Configure standalone EOP to deliver spam to the Junk Email folder in hybrid environments](https://learn.microsoft.com/exchange/standalone-eop/configure-eop-spam-protection-hybrid).
+- MoveToJmf: This value is the default. Deliver the message to the Junk Email folder in the recipient's mailbox. Hybrid environments need mail flow rules in the on-premises Exchange organization. For instructions, see [Configure standalone EOP to deliver spam to the Junk Email folder in hybrid environments](https://learn.microsoft.com/exchange/standalone-eop/configure-eop-spam-protection-hybrid).
 - NoAction
 - Quarantine: Deliver the message to quarantine. By default, messages that are quarantined as bulk email are available to the intended recipients and admins. Or, you can use the BulkQuarantineTag parameter to specify what end-users are allowed to do on quarantined messages.
 - Redirect: Redirect the message to the recipients specified by the RedirectToRecipients parameter.
@@ -325,7 +325,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online, Exchange Online Protection
 
-The BulkThreshold parameter specifies the BCL on messages that triggers the action specified by the BulkSpamAction parameter (greater than or equal to the specified BCL value). A valid value is an integer from 1 to 9. The default value is 7, which means a BCL of 7, 8, or 9 on messages will trigger the action that's specified by the BulkSpamAction parameter.
+The BulkThreshold parameter specifies the BCL on messages that triggers the action specified by the BulkSpamAction parameter (greater than or equal to the specified BCL value). A valid value is an integer from 1 to 9. The default value is 7, which means a BCL of 7, 8, or 9 on messages trigger the action specified by the BulkSpamAction parameter.
 
 A higher BCL indicates the message is more likely to generate complaints (and is therefore more likely to be spam). For more information, see [Bulk complaint level (BCL) in EOP](https://learn.microsoft.com/defender-office-365/anti-spam-bulk-complaint-level-bcl-about).
 
@@ -366,7 +366,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online, Exchange Online Protection
 
-This parameter has been deprecated and is no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters.
+This parameter is deprecated and no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters.
 
 ```yaml
 Type: Boolean
@@ -384,7 +384,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online, Exchange Online Protection
 
-This parameter has been deprecated and is no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters.
+This parameter is deprecated and no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters.
 
 ```yaml
 Type: Boolean
@@ -405,7 +405,7 @@ Accept wildcard characters: False
 The EnableLanguageBlockList parameter enables or disables marking messages that were written in specific languages as spam. Valid values are:
 
 - $true: Mark messages hat were written in the languages specified by the LanguageBlockList parameter as spam.
-- $false: Don't mark messages as spam solely based on their languages. This is the default value.
+- $false: Don't mark messages as spam solely based on their languages. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -426,7 +426,7 @@ Accept wildcard characters: False
 The EnableRegionBlockList parameter enables or disables marking messages that are sent from specific countries or regions as spam. Valid values are:
 
 - $true: Mark messages from senders in the RegionBlockList parameter as spam.
-- $false: Don't mark messages as spam solely based on the source country or region. This is the default value.
+- $false: Don't mark messages as spam solely based on the source country or region. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -444,7 +444,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online, Exchange Online Protection
 
-This parameter has been deprecated and is no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters.
+This parameter is deprecated and no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters.
 
 ```yaml
 Type: SmtpAddress
@@ -462,7 +462,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online, Exchange Online Protection
 
-This parameter has been deprecated and is no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters.
+This parameter is deprecated and no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters.
 
 ```yaml
 Type: String
@@ -480,7 +480,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online, Exchange Online Protection
 
-This parameter has been deprecated and is no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters.
+This parameter is deprecated and no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters.
 
 ```yaml
 Type: String
@@ -498,7 +498,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online, Exchange Online Protection
 
-This parameter has been deprecated and is no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters.
+This parameter is deprecated and no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters.
 
 ```yaml
 Type: Int32
@@ -516,7 +516,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online, Exchange Online Protection
 
-This parameter has been deprecated and is no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters.
+This parameter is deprecated and no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters.
 
 ```yaml
 Type: EsnLanguage
@@ -656,8 +656,8 @@ Accept wildcard characters: False
 
 The IncreaseScoreWithBizOrInfoUrls parameter increases the spam score of messages that contain links to .biz or .info domains. Valid values are:
 
-- Off: The setting is disabled. This is the default value, and we recommend that you don't change it.
-- On: The setting is enabled. Messages that contain links to .biz or .info domains are given a higher spam score and therefore have a higher chance of getting marked as spam with SCL 5 or 6, and the X-header `X-CustomSpam: URL to .biz or .info websites` is added to the message. Not all messages that match this setting will be marked as spam.
+- Off: The setting is disabled. This value is the default, and we recommend that you don't change it.
+- On: The setting is enabled. Messages that contain links to .biz or .info domains are given a higher spam score and therefore have a higher chance of getting marked as spam with SCL 5 or 6, and the X-header `X-CustomSpam: URL to .biz or .info websites` is added to the message. Not all messages that match this setting are marked as spam.
 - Test: The action specified by the TestModeAction parameter is taken on the message.
 
 ```yaml
@@ -678,8 +678,8 @@ Accept wildcard characters: False
 
 The IncreaseScoreWithImageLinks parameter increases the spam score of messages that contain image links to remote websites. Valid values are:
 
-- Off: The setting is disabled. This is the default value, and we recommend that you don't change it.
-- On: The setting is enabled. Messages that contain image links to remote websites are given a higher spam score and therefore have a higher chance of getting marked as spam with SCL 5 or 6, and the X-header `X-CustomSpam: Image links to remote sites` is added to the message. Not all messages that match this setting will be marked as spam.
+- Off: The setting is disabled. This value is the default, and we recommend that you don't change it.
+- On: The setting is enabled. Messages that contain image links to remote websites are given a higher spam score and therefore have a higher chance of getting marked as spam with SCL 5 or 6, and the X-header `X-CustomSpam: Image links to remote sites` is added to the message. Not all messages that match this setting are marked as spam.
 - Test: The action specified by the TestModeAction parameter is taken on the message.
 
 ```yaml
@@ -700,8 +700,8 @@ Accept wildcard characters: False
 
 The IncreaseScoreWithNumericIps parameter increases the spam score of messages that contain links to IP addresses. Valid values are:
 
-- Off: The setting is disabled. This is the default value, and we recommend that you don't change it.
-- On: The setting is enabled. Messages that contain links to IP addresses are given a higher spam score and therefore have a higher chance of getting marked as spam with SCL 5 or 6, and the X-header `X-CustomSpam: Numeric IP in URL` is added to the message. Note that not all messages which matches the setting will be marked as spam.
+- Off: The setting is disabled. This value is the default, and we recommend that you don't change it.
+- On: The setting is enabled. Messages that contain links to IP addresses are given a higher spam score and therefore have a higher chance of getting marked as spam with SCL 5 or 6, and the X-header `X-CustomSpam: Numeric IP in URL` is added to the message. Not all messages which matches the setting are marked as spam.
 - Test: The action specified by the TestModeAction parameter is taken on the message.
 
 ```yaml
@@ -722,8 +722,8 @@ Accept wildcard characters: False
 
 The IncreaseScoreWithRedirectToOtherPort parameter increases the spam score of messages that contain links that redirect to TCP ports other than 80 (HTTP), 8080 (alternate HTTP), or 443 (HTTPS). Valid values are:
 
-- Off: The setting is disabled. This is the default value, and we recommend that you don't change it.
-- On: The setting is enabled. Messages that contain links that redirect to other TCP ports are given a higher spam score and therefore have a higher chance of getting marked as spam with SCL 5 or 6, and the X-header `X-CustomSpam: URL redirect to other port` is added to the message. Note that not all messages which matches the setting will be marked as spam.
+- Off: The setting is disabled. This value is the default, and we recommend that you don't change it.
+- On: The setting is enabled. Messages that contain links that redirect to other TCP ports are given a higher spam score and therefore have a higher chance of getting marked as spam with SCL 5 or 6, and the X-header `X-CustomSpam: URL redirect to other port` is added to the message. Not all messages that match this setting are marked as spam.
 - Test: The action specified by the TestModeAction parameter is taken on the message.
 
 ```yaml
@@ -744,7 +744,7 @@ Accept wildcard characters: False
 
 The InlineSafetyTipsEnabled parameter specifies whether to enable or disable safety tips that are shown to recipients in messages. Valid values are:
 
-- $true: Safety tips are enabled. This is the default value.
+- $true: Safety tips are enabled. This value is the default.
 - $false: Safety tips are disabled.
 
 ```yaml
@@ -765,7 +765,7 @@ Accept wildcard characters: False
 
 The IntraOrgFilterState parameter specifies whether to enable anti-spam filtering for messages sent between internal users (users in the same organization). The action that's configured in the policy for the specified spam filter verdicts is taken on messages sent between internal users. Valid values are:
 
-- Default: This is the default value. Currently, this value is the same as HighConfidencePhish.
+- Default: This value is the default. Currently, this value is the same as HighConfidencePhish.
 - HighConfidencePhish
 - Phish: Includes phishing and high confidence phishing.
 - HighConfidenceSpam: Includes high confidence spam, phishing, and high confidence phishing.
@@ -815,7 +815,7 @@ Accept wildcard characters: False
 The MarkAsSpamBulkMail parameter allows spam filtering to act on bulk email messages. Valid values are:
 
 - Off: The message is stamped with the BCL, but no action is taken for a bulk email filtering verdict. In effect, the values of the BulkThreshold and BulkSpamAction parameters are irrelevant.
-- On: This is the default value. A BCL that's greater than the BulkThreshold value is converted to an SCL 6 that corresponds to a filtering verdict of spam, and the BulkSpamAction value is taken on the message.
+- On: This value is the default. A BCL that's greater than the BulkThreshold value is converted to an SCL 6 that corresponds to a filtering verdict of spam, and the BulkSpamAction value is taken on the message.
 - Test: This value is available, but isn't used for this parameter.
 
 ```yaml
@@ -836,7 +836,7 @@ Accept wildcard characters: False
 
 The MarkAsSpamEmbedTagsInHtml parameter marks a message as spam when the message contains HTML \<embed\> tags. Valid values are:
 
-- Off: The setting is disabled. This is the default value, and we recommend that you don't change it.
+- Off: The setting is disabled. This value is the default, and we recommend that you don't change it.
 - On: The setting is enabled. Messages that contain HTML \<embed\> tags are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Embed tag in html` is added to the message.
 - Test: The action specified by the TestModeAction parameter is taken on the message.
 
@@ -858,7 +858,7 @@ Accept wildcard characters: False
 
 The MarkAsSpamEmptyMessages parameter marks a message as spam when the message contains no subject, no content in the message body, and no attachments. Valid values are:
 
-- Off: The setting is disabled. This is the default value, and we recommend that you don't change it.
+- Off: The setting is disabled. This value is the default, and we recommend that you don't change it.
 - On: The setting is enabled. Empty messages are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Empty Message` is added to the message.
 - Test: The action specified by the TestModeAction parameter is taken on the message.
 
@@ -880,7 +880,7 @@ Accept wildcard characters: False
 
 The MarkAsSpamFormTagsInHtml parameter marks a message as spam when the message contains HTML \<form\> tags. Valid values are:
 
-- Off: The setting is disabled. This is the default value, and we recommend that you don't change it.
+- Off: The setting is disabled. This value is the default, and we recommend that you don't change it.
 - On: The setting is enabled. Messages that contain HTML \<form\> tags are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Form tag in html` is added to the message.
 - Test: The action specified by the TestModeAction parameter is taken on the message.
 
@@ -902,7 +902,7 @@ Accept wildcard characters: False
 
 The MarkAsSpamFramesInHtml parameter marks a message as spam when the message contains HTML \<frame\> or \<iframe\> tags. Valid values are:
 
-- Off: The setting is disabled. This is the default value, and we recommend that you don't change it.
+- Off: The setting is disabled. This value is the default, and we recommend that you don't change it.
 - On: The setting is enabled. Messages that contain HTML \<frame\> or \<iframe\> tags are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: IFRAME or FRAME in HTML` is added to the message.
 - Test: The action specified by the TestModeAction parameter is taken on the message.
 
@@ -924,7 +924,7 @@ Accept wildcard characters: False
 
 The MarkAsSpamFromAddressAuthFail parameter marks a message as spam when Sender ID filtering encounters a hard fail. This setting combines an Sender Policy Framework (SPF) check with a Sender ID check to help protect against message headers that contain forged senders. Valid values are:
 
-- Off: The setting is disabled. This is the default value, and we recommend that you don't change it.
+- Off: The setting is disabled. This value is the default, and we recommend that you don't change it.
 - On: The setting is enabled. Messages where Sender ID filtering encounters a hard fail are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: SPF From Record Fail` is added to the message.
 
 ```yaml
@@ -945,7 +945,7 @@ Accept wildcard characters: False
 
 The MarkAsSpamJavaScriptInHtml parameter marks a message as spam when the message contains JavaScript or VBScript. Valid values are:
 
-- Off: The setting is disabled. This is the default value, and we recommend that you don't change it.
+- Off: The setting is disabled. This value is the default, and we recommend that you don't change it.
 - On: The setting is enabled. Messages that contain JavaScript or VBScript are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Javascript or VBscript tags in HTML` is added to the message.
 - Test: The action specified by the TestModeAction parameter is taken on the message.
 
@@ -967,7 +967,7 @@ Accept wildcard characters: False
 
 The MarkAsSpamNdrBackscatter parameter marks a message as spam when the message is a non-delivery report (also known as an NDR or bounce messages) sent to a forged sender (known as *backscatter*). Valid values are:
 
-- Off: The setting is disabled. This is the default value, and we recommend that you don't change it.
+- Off: The setting is disabled. This value is the default, and we recommend that you don't change it.
 - On: The setting is enabled. Backscatter is given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Backscatter NDR` is added to the message.
 
 ```yaml
@@ -988,7 +988,7 @@ Accept wildcard characters: False
 
 The MarkAsSpamObjectTagsInHtml parameter marks a message as spam when the message contains HTML \<object\> tags. Valid values are:
 
-- Off: The setting is disabled. This is the default value, and we recommend that you don't change it.
+- Off: The setting is disabled. This value is the default, and we recommend that you don't change it.
 - On: The setting is enabled. Messages that contain HTML \<object\> tags are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Object tag in html` is added to the message.
 - Test: The action specified by the TestModeAction parameter is taken on the message.
 
@@ -1010,7 +1010,7 @@ Accept wildcard characters: False
 
 The MarkAsSpamSensitiveWordList parameter marks a message as spam when the message contains words from the sensitive words list. Microsoft maintains a dynamic but non-editable list of words that are associated with potentially offensive messages. Valid values are:
 
-- Off: The setting is disabled. This is the default value, and we recommend that you don't change it.
+- Off: The setting is disabled. This value is the default, and we recommend that you don't change it.
 - On: The setting is enabled. Messages that contain words from the sensitive word list in the subject or message body are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Sensitive word in subject/body` is added to the message.
 - Test: The action specified by the TestModeAction parameter is taken on the message.
 
@@ -1032,7 +1032,7 @@ Accept wildcard characters: False
 
 The MarkAsSpamSpfRecordHardFail parameter marks a message as spam when SPF record checking encounters a hard fail. Valid values are:
 
-- Off: The setting is disabled. This is the default value, and we recommend that you don't change it.
+- Off: The setting is disabled. This value is the default, and we recommend that you don't change it.
 - On: The setting is enabled. Messages sent from an IP address that isn't specified in the SPF Sender Policy Framework (SPF) record in DNS are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: SPF Record Fail` is added to the message.
 
 ```yaml
@@ -1053,7 +1053,7 @@ Accept wildcard characters: False
 
 The MarkAsSpamWebBugsInHtml parameter marks a message as spam when the message contains web bugs (also known as web beacons). Valid values are:
 
-- Off: The setting is disabled. This is the default value, and we recommend that you don't change it.
+- Off: The setting is disabled. This value is the default, and we recommend that you don't change it.
 - On: The setting is enabled. Messages that contain web bugs are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Web bug` is added to the message.
 - Test: The action specified by the TestModeAction parameter is taken on the message.
 
@@ -1132,7 +1132,7 @@ The PhishSpamAction parameter specifies the action to take on messages that are
 - Delete: Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message.
 - ModifySubject: Add the ModifySubject parameter value to the beginning of the subject line, deliver the message, and move the message to the Junk Email folder (same caveats as MoveToJmf).
 - MoveToJmf: Deliver the message to the Junk Email folder in the recipient's mailbox.
-- Quarantine: Move the message to the quarantine. This is the default value. The quarantined message is available to the intended recipients (as of April, 2020) and admins.
+- Quarantine: Move the message to the quarantine. This value is the default. The quarantined message is available to the intended recipients (as of April, 2020) and admins.
 - Quarantine: Deliver the message to quarantine. By default, messages that are quarantined as phishing are available to admins and (as of April 2020) the intended recipients. Or, you can use the PhishQuarantineTag parameter to specify what end-users are allowed to do on quarantined messages.
 - Redirect: Redirect the message to the recipients specified by the RedirectToRecipients parameter.
 
@@ -1154,7 +1154,7 @@ Accept wildcard characters: False
 
 The PhishZapEnabled parameter enables or disables zero-hour auto purge (ZAP) to detect phishing in already delivered messages in Exchange Online mailboxes. Valid values are:
 
-- $true: ZAP for phishing messages is enabled. This is the default value. The result depends on the spam filtering verdict action for phishing messages: MoveToJmf = Read and unread phishing messages are moved to the Junk Email folder. Delete, Redirect, or Quarantine = Read and unread phishing messages are quarantined. AddXHeader or ModifySubject = no action is taken on the message.
+- $true: ZAP for phishing messages is enabled. This value is the default. The result depends on the spam filtering verdict action for phishing messages: MoveToJmf = Read and unread phishing messages are moved to the Junk Email folder. Delete, Redirect, or Quarantine = Read and unread phishing messages are quarantined. AddXHeader or ModifySubject = no action is taken on the message.
 - $false: ZAP for phishing messages is disabled.
 
 You configure ZAP for spam with the SpamZapEnabled parameter.
@@ -1279,7 +1279,7 @@ The SpamAction parameter specifies the action to take on messages that are marke
 - AddXHeader: Add the AddXHeaderValue parameter value to the message header, deliver the message, and move the message to the Junk Email folder (same caveats as MoveToJmf).
 - Delete : Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message.
 - ModifySubject: Add the ModifySubject parameter value to the beginning of the subject line, deliver the message, and move the message to the Junk Email folder (same caveats as MoveToJmf).
-- MoveToJmf: This is the default value. Deliver the message to the Junk Email folder in the recipient's mailbox. Hybrid environments need mail flow rules in the on-premises Exchange organization. For instructions, see [Configure standalone EOP to deliver spam to the Junk Email folder in hybrid environments](https://learn.microsoft.com/exchange/standalone-eop/configure-eop-spam-protection-hybrid).
+- MoveToJmf: This value is the default. Deliver the message to the Junk Email folder in the recipient's mailbox. Hybrid environments need mail flow rules in the on-premises Exchange organization. For instructions, see [Configure standalone EOP to deliver spam to the Junk Email folder in hybrid environments](https://learn.microsoft.com/exchange/standalone-eop/configure-eop-spam-protection-hybrid).
 - Quarantine: Deliver the message to quarantine. By default, messages that are quarantined as spam are available to the intended recipients and admins. Or, you can use the SpamQuarantineTag parameter to specify what end-users are allowed to do on quarantined messages.
 - Redirect: Redirect the message to the recipients specified by the RedirectToRecipients parameter.
 
@@ -1329,7 +1329,7 @@ Accept wildcard characters: False
 
 The SpamZapEnabled parameter enables or disables zero-hour auto purge (ZAP) to detect spam in already delivered messages in Exchange Online mailboxes. Valid values are:
 
-- $true: ZAP for spam is enabled. This is the default value. The result depends on the spam filtering verdict action for spam messages: MoveToJmf = Unread spam messages are moved to the Junk Email folder. Delete, Redirect, or Quarantine = Unread spam messages are quarantined. AddXHeader or ModifySubject = no action is taken on the message.
+- $true: ZAP for spam is enabled. This value is the default. The result depends on the spam filtering verdict action for spam messages: MoveToJmf = Unread spam messages are moved to the Junk Email folder. Delete, Redirect, or Quarantine = Unread spam messages are quarantined. AddXHeader or ModifySubject = no action is taken on the message.
 - $false: ZAP for spam is disabled.
 
 You configure ZAP for phishing messages with the PhishZapEnabled parameter.
@@ -1352,7 +1352,7 @@ Accept wildcard characters: False
 
 The TestModeAction parameter specifies the additional action to take on messages when one or more IncreaseScoreWith\* or MarkAsSpam\* ASF parameters are set to the value Test. Valid values are:
 
-- None: This is the default value, and we recommend that you don't change it.
+- None: This value is the default, and we recommend that you don't change it.
 - AddXHeader: The X-header value `X-CustomSpam: This message was filtered by the custom spam filter option` is added to the message.
 - BccMessage: Redirect the message to the recipients specified by the TestModeBccToRecipients parameter.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-HostedContentFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/New-HostedContentFilterRule.md
index 7dc54be6f6..4560b98a1b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-HostedContentFilterRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-HostedContentFilterRule.md
@@ -41,7 +41,7 @@ New-HostedContentFilterRule [-Name] <String> -HostedContentFilterPolicy <HostedC
 > [!IMPORTANT]
 > Different types of recipient conditions use AND logic (the recipient must satisfy **all** specified conditions). Different types of recipient exceptions use OR logic (the recipient must satisfy **any** of the specified exceptions). For more information, see [Use the Microsoft Defender portal to create anti-spam policies](https://learn.microsoft.com/defender-office-365/anti-spam-policies-configure#use-the-microsoft-defender-portal-to-create-anti-spam-policies).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-HostedOutboundSpamFilterPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-HostedOutboundSpamFilterPolicy.md
index d838d30f5b..944b15fa76 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-HostedOutboundSpamFilterPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-HostedOutboundSpamFilterPolicy.md
@@ -40,7 +40,7 @@ New-HostedOutboundSpamFilterPolicy [-Name] <String>
 ## DESCRIPTION
 New policies that you create using this cmdlet aren't applied to users and aren't visible in admin centers. You need to use the HostedOutboundSpamFilterPolicy parameter on the New-HostedOutboundSpamFilterRule or Set-HostedOutboundSpamFilterRule cmdlets to associate the policy with a rule.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -82,7 +82,7 @@ The ActionWhenThresholdReach parameter specifies the action to take when any of
 
 - Alert: No action, alert only.
 - BlockUser: Prevent the user from sending email messages.
-- BlockUserForToday: Prevent the user from sending email messages until the following day. This is the default value.
+- BlockUserForToday: Prevent the user from sending email messages until the following day. This value is the default.
 
 ```yaml
 Type: OutboundRecipientLimitsExceededAction
@@ -121,7 +121,7 @@ Accept wildcard characters: False
 
 The AutoForwardingMode specifies how the policy controls automatic email forwarding to external recipients. Valid values are:
 
-- Automatic: This is the default value. This value is now the same as Off. When this value was originally introduced, it was equivalent to On. Over time, thanks to the principles of [secure by default](https://learn.microsoft.com/defender-office-365/secure-by-default), the effect of this value was eventually changed to Off for all customers. For more information, see [this blog post](https://techcommunity.microsoft.com/t5/exchange-team-blog/all-you-need-to-know-about-automatic-email-forwarding-in/ba-p/2074888).
+- Automatic: This value is the default. This value is now the same as Off. When this value was originally introduced, it was equivalent to On. Over time, thanks to the principles of [secure by default](https://learn.microsoft.com/defender-office-365/secure-by-default), the effect of this value was eventually changed to Off for all customers. For more information, see [this blog post](https://techcommunity.microsoft.com/t5/exchange-team-blog/all-you-need-to-know-about-automatic-email-forwarding-in/ba-p/2074888).
 - On: Automatic external email forwarding isn't disabled by the policy.
 - Off: Automatic external email forwarding is disabled by the policy and results in a non-delivery report (also known as an NDR or bounce message) to the sender.
 
@@ -167,7 +167,7 @@ Accept wildcard characters: False
 The BccSuspiciousOutboundMail parameter specifies whether to add recipients to the Bcc field of outgoing spam messages. Valid values are:
 
 - $true: The recipients specified by the BccSuspiciousOutboundAdditionalRecipients parameter are added to outgoing spam messages.
-- $false: No additional messages are added to outgoing spam messages. This is the default value.
+- $false: No additional messages are added to outgoing spam messages. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -185,12 +185,12 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online, Exchange Online Protection
 
-**Note**: This setting has been replaced by the default alert policy named **User restricted from sending email**, which sends notification messages to admins. We recommend that you use the alert policy rather than this setting to notify admins and other users. For instructions, see [Verify the alert settings for restricted users](https://learn.microsoft.com/defender-office-365/outbound-spam-restore-restricted-users#verify-the-alert-settings-for-restricted-users).
+**Note**: This setting is replaced by the default alert policy named **User restricted from sending email**, which sends notification messages to admins. We recommend that you use the alert policy rather than this setting to notify admins and other users. For instructions, see [Verify the alert settings for restricted users](https://learn.microsoft.com/defender-office-365/outbound-spam-restore-restricted-users#verify-the-alert-settings-for-restricted-users).
 
 The NotifyOutboundSpam parameter specify whether to notify admins when outgoing spam is detected. Valid values are:
 
 - $true: Notify the admins specified by the NotifyOutboundSpamRecipients parameter.
-- $false: Don't send notifications. This is the default value.
+- $false: Don't send notifications. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -208,7 +208,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online, Exchange Online Protection
 
-**Note**: This setting has been replaced by the default alert policy named **User restricted from sending email**, which sends notification messages to admins. We recommend that you use the alert policy rather than this setting to notify admins and other users. For instructions, see [Verify the alert settings for restricted users](https://learn.microsoft.com/defender-office-365/outbound-spam-restore-restricted-users#verify-the-alert-settings-for-restricted-users).
+**Note**: This setting is replaced by the default alert policy named **User restricted from sending email**, which sends notification messages to admins. We recommend that you use the alert policy rather than this setting to notify admins and other users. For instructions, see [Verify the alert settings for restricted users](https://learn.microsoft.com/defender-office-365/outbound-spam-restore-restricted-users#verify-the-alert-settings-for-restricted-users).
 
 The NotifyOutboundSpamRecipients parameter specifies the email addresses of admins to notify when an outgoing spam is detected. You can specify multiple email addresses separated by commas.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-HostedOutboundSpamFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/New-HostedOutboundSpamFilterRule.md
index 1afdd51735..423016b19a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-HostedOutboundSpamFilterRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-HostedOutboundSpamFilterRule.md
@@ -38,7 +38,7 @@ New-HostedOutboundSpamFilterRule [-Name] <String> -HostedOutboundSpamFilterPolic
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -142,7 +142,7 @@ Accept wildcard characters: False
 
 The Enabled parameter specifies whether the rule is enabled. Valid values are:
 
-- $true: The rule is enabled. This is the default value.
+- $true: The rule is enabled. This value is the default.
 - $false: The rule is disabled.
 
 In the properties of the rule, the value of this parameter is visible in the State property.
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-HybridConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/New-HybridConfiguration.md
index eeb2dd5b03..8ba792670c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-HybridConfiguration.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-HybridConfiguration.md
@@ -51,7 +51,7 @@ The available settings in this cmdlet are configured when the Hybrid Configurati
 
 For more information, see [Exchange Server hybrid deployments](https://learn.microsoft.com/exchange/exchange-hybrid).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-InboundConnector.md b/exchange/exchange-ps/ExchangePowerShell/New-InboundConnector.md
index bed3ce6485..8c1f5d800e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-InboundConnector.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-InboundConnector.md
@@ -53,7 +53,7 @@ New-InboundConnector [-Name] <String> -SenderDomains <MultiValuedProperty>
 ## DESCRIPTION
 Inbound connectors accept email messages from remote domains that require specific configuration options.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -162,7 +162,7 @@ The CloudServicesMailEnabled parameter specifies whether the connector is used f
 
 Valid values are:
 
-- $true: The connector is used for mail flow in hybrid organizations, so cross-premises headers are preserved or promoted in messages that flow through the connector. This is the default value for connectors that are created by the Hybrid Configuration wizard. Certain X-MS-Exchange-Organization-\* headers in outbound messages that are sent from one side of the hybrid organization to the other are converted to X-MS-Exchange-CrossPremises-\* headers and are thereby preserved in messages. X-MS-Exchange-CrossPremises-\* headers in inbound messages that are received on one side of the hybrid organization from the other are promoted to X-MS-Exchange-Organization-\* headers. These promoted headers replace any instances of the same X-MS-Exchange-Organization-\* headers that already exist in messages.
+- $true: The connector is used for mail flow in hybrid organizations, so cross-premises headers are preserved or promoted in messages that flow through the connector. This value is the default for connectors that are created by the Hybrid Configuration wizard. Certain X-MS-Exchange-Organization-\* headers in outbound messages that are sent from one side of the hybrid organization to the other are converted to X-MS-Exchange-CrossPremises-\* headers and are thereby preserved in messages. X-MS-Exchange-CrossPremises-\* headers in inbound messages that are received on one side of the hybrid organization from the other are promoted to X-MS-Exchange-Organization-\* headers. These promoted headers replace any instances of the same X-MS-Exchange-Organization-\* headers that already exist in messages.
 - $false: The connector isn't used for mail flow in hybrid organizations, so any cross-premises headers are removed from messages that flow through the connector.
 
 ```yaml
@@ -222,7 +222,7 @@ Accept wildcard characters: False
 
 The ConnectorSource parameter specifies how the connector is created. Valid input for this parameter includes the following values:
 
-- Default: The connector is manually created. This is the default value.
+- Default: The connector is manually created. This value is the default.
 - HybridWizard: The connector is automatically created by the Hybrid Configuration Wizard.
 - Migrated: The connector was originally created in Microsoft Forefront Online Protection for Exchange.
 
@@ -292,7 +292,7 @@ Accept wildcard characters: False
 The EFSkipIPs parameter specifies the behavior of Enhanced Filtering for Connectors. Valid values are:
 
 - $true: Only the last message source is skipped.
-- $false: Skip the source IP addresses specified by the EFSkipIPs parameter. If no IP addresses are specified, Enhanced Filtering for Connectors is disabled on the connector. This is the default value.
+- $false: Skip the source IP addresses specified by the EFSkipIPs parameter. If no IP addresses are specified, Enhanced Filtering for Connectors is disabled on the connector. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -368,7 +368,7 @@ Accept wildcard characters: False
 
 The Enabled parameter enables or disables the connector. Valid values are:
 
-- $true: The connector is enabled. This is the default value.
+- $true: The connector is enabled. This value is the default.
 - $false: The connector is disabled.
 
 ```yaml
@@ -389,7 +389,7 @@ Accept wildcard characters: False
 
 The RequireTLS parameter specifies whether to require TLS transmission for all messages that are received by a Partner type connector. Valid values are:
 
-- $true: Reject messages if they aren't sent over TLS. This is the default value
+- $true: Reject messages if they aren't sent over TLS. This value is the default
 - $false: Allow messages if they aren't sent over TLS.
 
 **Note**: This parameter applies only to Partner type connectors.
@@ -413,7 +413,7 @@ Accept wildcard characters: False
 The RestrictDomainsToCertificate parameter specifies whether the Subject value of the TLS certificate is checked before messages can use the Partner type connector. Valid values are:
 
 - $true: Mail is allowed to use the connector only if the Subject value of the TLS certificate that the source email server uses to authenticate matches the TlsSenderCertificateName parameter value.
-- $false: The Subject value of the TLS certificate that the source email server uses to authenticate doesn't control whether mail from that source uses the connector. This is the default value.
+- $false: The Subject value of the TLS certificate that the source email server uses to authenticate doesn't control whether mail from that source uses the connector. This value is the default.
 
 **Note**: This parameter applies only to Partner type connectors.
 
@@ -436,7 +436,7 @@ Accept wildcard characters: False
 The RestrictDomainsToIPAddresses parameter specifies whether to reject mail that comes from unknown source IP addresses for Partner type connectors. Valid values are:
 
 - $true: Automatically reject mail from domains that are specified by the SenderDomains parameter if the source IP address isn't also specified by the SenderIPAddress parameter.
-- $false: Don't automatically reject mail from domains that are specified by the SenderDomains parameter based on the source IP address. This is the default value.
+- $false: Don't automatically reject mail from domains that are specified by the SenderDomains parameter based on the source IP address. This value is the default.
 
 **Note**: This parameter applies only to Partner type connectors.
 
@@ -522,7 +522,7 @@ Accept wildcard characters: False
 The TreatMessagesAsInternal parameter specifies an alternative method to identify messages sent from an on-premises organization as internal messages. You should only consider using this parameter when your on-premises organization doesn't use Exchange. Valid values are:
 
 - $true: Messages are considered internal if the sender's domain matches a domain that's configured in Microsoft 365. This setting allows internal mail flow between Microsoft 365 and on-premises organizations that don't have Exchange Server 2010 or later installed. However, this setting has potential security risks (for example, internal messages bypass antispam filtering), so use caution when configuring this setting.
-- $false: Messages aren't considered internal. This is the default value.
+- $false: Messages aren't considered internal. This value is the default.
 
 In hybrid environments, you don't need to use this parameter, because the Hybrid Configuration wizard automatically configures the required settings on the Inbound connector in Microsoft 365 and the Send connector in the on-premises Exchange organization (the CloudServicesMailEnabled parameter).
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-InboxRule.md b/exchange/exchange-ps/ExchangePowerShell/New-InboxRule.md
index c9db1ab9c4..7afb9dee03 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-InboxRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-InboxRule.md
@@ -13,7 +13,7 @@ title: New-InboxRule
 # New-InboxRule
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the New-InboxRule cmdlet to create Inbox rules in mailboxes. Inbox rules process messages in the Inbox based on conditions and take actions such as moving a message to a specified folder or deleting a message.
 
@@ -117,7 +117,7 @@ When you create, modify, remove, enable, or disable an Inbox rule in Exchange Po
 
 Parameters that are used for conditions also have corresponding exception parameters. When conditions specified in an exception are matched, the rule isn't applied to the message. Exception parameters begin with ExceptIf. For example, the exception parameter for SubjectOrBodyContainsWords is ExceptIfSubjectOrBodyContainsWords.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -179,7 +179,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
 
-The ValidateOnly switch tells the cmdlet to evaluate the conditions and requirements necessary to perform the operation and then reports whether the operation will succeed or fail. No changes are made when the ValidateOnly switch is used.
+The ValidateOnly switch specifies whether to evaluate the potential success or failure of the command without making changes. You don't need to specify a value with this switch.
 
 ```yaml
 Type: SwitchParameter
@@ -944,7 +944,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 You need to use this parameter with the ExceptIfWithinSizeRangeMinimum parameter, and the value of this parameter must be greater than the value of ExceptIfWithinSizeRangeMinimum.
 
@@ -976,7 +976,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 You need to use this parameter with the ExceptIfWithinSizeRangeMaximum parameter, and the value of this parameter must be less than the value of ExceptIfWithinSizeRangeMaximum.
 
@@ -1055,7 +1055,7 @@ Accept wildcard characters: False
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
-A confirmation prompt warns you if the mailbox contains rules that were created by Outlook, because any client-side rules will be removed by the actions of this cmdlet.
+A confirmation prompt warns you if the mailbox contains rules that were created by Outlook, because any client-side rules are removed by the actions of this cmdlet.
 
 ```yaml
 Type: SwitchParameter
@@ -1823,7 +1823,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 You need to use this parameter with the WithinSizeRangeMinimum parameter, and the value of this parameter must be greater than the value of WithinSizeRangeMinimum.
 
@@ -1855,7 +1855,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 You need to use this parameter with the WithinSizeRangeMaximum parameter, and the value of this parameter must be less than the value of WithinSizeRangeMaximum.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-InformationBarrierPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-InformationBarrierPolicy.md
index 8b9e46152e..9937381641 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-InformationBarrierPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-InformationBarrierPolicy.md
@@ -269,7 +269,7 @@ Accept wildcard characters: False
 The State parameter specifies whether the information barrier policy is active or inactive. Valid values are:
 
 - Active
-- Inactive (This is the default value.)
+- Inactive (This value is the default.)
 
 ```yaml
 Type: EopInformationBarrierPolicyState
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-IntraOrganizationConnector.md b/exchange/exchange-ps/ExchangePowerShell/New-IntraOrganizationConnector.md
index dd86a9f2b3..69e235ceee 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-IntraOrganizationConnector.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-IntraOrganizationConnector.md
@@ -13,7 +13,7 @@ title: New-IntraOrganizationConnector
 # New-IntraOrganizationConnector
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the New-IntraOrganizationConnector cmdlet to create an Intra-Organization connector between two on-premises Exchange forests in an organization, between an Exchange on-premises organization and an Exchange Online organization, or between two Exchange Online organizations. This connector enables feature availability and service connectivity across the organizations using a common connector and connection endpoints.
 
@@ -36,7 +36,7 @@ The New-IntraOrganizationConnector cmdlet is used to create a connection for fea
 
 For hybrid deployments between on-premises Exchange and Exchange Online organizations, the New-IntraOrganizationConnector cmdlet is used by the Hybrid Configuration wizard. Typically, the Intra-Organization connector is configured when the hybrid deployment is initially created by the wizard. We strongly recommend that you use the Hybrid Configuration wizard to create the Intra-Organization connector when configuring a hybrid deployment with an Exchange Online organization.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -89,7 +89,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
 
-The TargetAddressDomains parameter specifies the domain namespaces that will be used in the Intra-organization connector. These domains must have valid Autodiscover endpoints defined in their organizations. The domains and their associated Autodiscover endpoints are used by the Intra-Organization connector for feature and service connectivity.
+The TargetAddressDomains parameter specifies the domain namespaces to use in the Intra-organization connector. These domains must have valid Autodiscover endpoints defined in their organizations. The domains and their associated Autodiscover endpoints are used by the Intra-Organization connector for feature and service connectivity.
 
 You specify multiple domain values separated by commas.
 
@@ -172,7 +172,7 @@ Accept wildcard characters: False
 
 This parameter is available only in the cloud-based service.
 
-The TargetSharingEpr parameter specifies the URL of the target Exchange Web Services that will be used in the Intra-Organization connector.
+The TargetSharingEpr parameter specifies the URL of the target Exchange Web Services to use in the Intra-Organization connector.
 
 ```yaml
 Type: Uri
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-JournalRule.md b/exchange/exchange-ps/ExchangePowerShell/New-JournalRule.md
index 0103a92195..97291cdb9b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-JournalRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-JournalRule.md
@@ -13,7 +13,7 @@ title: New-JournalRule
 # New-JournalRule
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the New-JournalRule cmdlet to create a journal rule in your organization.
 
@@ -37,7 +37,7 @@ The New-JournalRule cmdlet creates a journal rule in your organization.
 
 By default, new journal rules are disabled unless the Enabled parameter is set to $true. For more information about how to enable a new journal rule that was created in a disabled state, see [Enable-JournalRule](https://learn.microsoft.com/powershell/module/exchangepowershell/enable-journalrule).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-Label.md b/exchange/exchange-ps/ExchangePowerShell/New-Label.md
index 6a8b3932a6..a7369fefac 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-Label.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-Label.md
@@ -183,7 +183,7 @@ Some of the settings that you configure with this parameter are supported only b
 
 Supported settings for built-in labeling:
 
-- **BlockContentAnalysisServices**: Specifies a privacy setting to allow or prevent content in Word, Excel, PowerPoint, and Outlook from being sent to Microsoft for content analysis. Available values are True, and False (the default). This setting impacts services such as data loss prevention policy tips, automatic and recommended labeling, and Microsoft Copilot for Microsoft 365. Example: `New-Label -Identity Confidential -AdvancedSettings @{BlockContentAnalysisServices="True"}`. For more information, see [Prevent some connected experiences that analyze content](https://learn.microsoft.com/purview/sensitivity-labels-office-apps#prevent-some-connected-experiences-that-analyze-content).
+- **BlockContentAnalysisServices**: Specifies a privacy setting to allow or prevent content in Word, Excel, PowerPoint, and Outlook from being sent to Microsoft for content analysis. Available values are True, and False (the default). This setting affects services such as data loss prevention policy tips, automatic and recommended labeling, and Microsoft Copilot for Microsoft 365. Example: `New-Label -Identity Confidential -AdvancedSettings @{BlockContentAnalysisServices="True"}`. For more information, see [Prevent some connected experiences that analyze content](https://learn.microsoft.com/purview/sensitivity-labels-office-apps#prevent-some-connected-experiences-that-analyze-content).
 
 - **Color**: Specifies a label color as a hex triplet code for the red, green, and blue (RGB) components of the color. Example: `New-Label -DisplayName "General" -Name "General" -Tooltip "Business data that is not intended for public consumption." -AdvancedSettings @{color="#40e0d0"}`. For more information, see [Configuring custom colors by using PowerShell](https://learn.microsoft.com/purview/sensitivity-labels-office-apps#configuring-custom-colors-by-using-powershell).
 
@@ -878,7 +878,7 @@ The feature for this parameter is currently in Public Preview, and is not availa
 
 The EncryptionDoubleKeyEncryptionUrl parameter specifies the Double Key Encryption endpoint URL.
 
-You can't remove the URL after the label has been created; you can only modify it.
+You can't remove the URL after the label is created; you can only modify it.
 
 This parameter is meaningful only when the EncryptionEnabled parameter value is either $true or $false.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-LabelPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-LabelPolicy.md
index ab078d7da6..c4edd6a938 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-LabelPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-LabelPolicy.md
@@ -130,7 +130,7 @@ Supported settings for built-in labeling:
 
 - **teamworkdefaultlabelid**: Outlook and Teams apps that support this setting apply a default label, or no label for meetings. Example: `New-LabelPolicy -Identity Global -AdvancedSettings @{teamworkdefaultlabelid="General"}`. For more information about labeling meetings, see [Use sensitivity labels to protect calendar items, Teams meetings, and chat](https://learn.microsoft.com/purview/sensitivity-labels-meetings).
 
-- **HideBarByDefault**: For Office apps that support the sensitivity bar, don't display the sensitivity label name on the window bar title so that there's more space to display long file names. Just the label icon and color (if configured) will be displayed. Users can't revert this setting in the app. Example: `New-LabelPolicy -Identity Global -AdvancedSettings @{HideBarByDefault="True"}`
+- **HideBarByDefault**: For Office apps that support the sensitivity bar, don't display the sensitivity label name on the window bar title so that there's more space to display long file names. Just the label icon and color (if configured) are displayed. Users can't revert this setting in the app. Example: `New-LabelPolicy -Identity Global -AdvancedSettings @{HideBarByDefault="True"}`
 
 Additionally, for Power BI:
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-M365DataAtRestEncryptionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-M365DataAtRestEncryptionPolicy.md
index ad9a4a3cdd..2554ec465a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-M365DataAtRestEncryptionPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-M365DataAtRestEncryptionPolicy.md
@@ -34,7 +34,7 @@ New-M365DataAtRestEncryptionPolicy [-Name] <String> -AzureKeyIDs <MultiValuedPro
 ## DESCRIPTION
 Use the New-M365DataAtRestEncryptionPolicy cmdlet to create a new Microsoft 365 data-at-rest encryption policy for multi-workload usage. For more information, see [Service encryption with Microsoft Purview Customer Key](https://learn.microsoft.com/purview/customer-key-overview).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -148,7 +148,7 @@ Accept wildcard characters: False
 
 The Enabled parameter specifies whether the policy is enabled or disabled. Valid values are:
 
-- $true: The policy is enabled. This is the default value.
+- $true: The policy is enabled. This value is the default.
 - $false: The policy is disabled.
 
 ```yaml
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-Mailbox.md b/exchange/exchange-ps/ExchangePowerShell/New-Mailbox.md
index 6e85684156..28c5437879 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-Mailbox.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-Mailbox.md
@@ -13,7 +13,7 @@ title: New-Mailbox
 # New-Mailbox
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the New-Mailbox cmdlet to create mailboxes and user accounts at the same time.
 
@@ -764,7 +764,7 @@ New-Mailbox [-Name] <String> [-SupervisoryReviewPolicy]
  ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 In Exchange Server, the [CommonParameters](https://go.microsoft.com/fwlink/p/?LinkID=113216) InformationVariable and InformationAction don't work.
 
@@ -802,7 +802,7 @@ Set-Mailbox -Identity Sales -GrantSendOnBehalfTo MarketingSG
 Add-MailboxPermission -Identity Sales -User MarketingSG -AccessRights FullAccess -InheritanceType All
 ```
 
-This example creates the shared mailbox "Sales Department" and grants Full Access and Send on Behalf permissions for the security group "MarketingSG". Users who are members of the security group will be granted the permissions to the mailbox.
+This example creates the shared mailbox "Sales Department" and grants Full Access and Send on Behalf permissions for the security group "MarketingSG". Users who are members of the security group are granted the permissions to the mailbox.
 
 This example assumes that you've already created a mail-enabled security group named "MarketingSG" by using the New-DistributionGroup cmdlet.
 
@@ -1584,7 +1584,7 @@ The HoldForMigration switch specifies whether to prevent any client or user, exc
 
 You need to use this parameter when you create the first public folder, which is called the hierarchy mailbox, in your organization.
 
-Use this parameter only if you plan to migrate legacy Exchange 2010 public folders to Exchange 2016. If you use this switch but don't have legacy public folders to migrate, you won't be able to create any public folders.
+Use this parameter only if you plan to migrate legacy Exchange 2010 public folders to Exchange 2016. If you use this switch but don't have legacy public folders to migrate, you can't create any public folders.
 
 ```yaml
 Type: SwitchParameter
@@ -1640,7 +1640,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
 
-The IsExcludedFromServingHierarchy parameter prevents users from accessing the public folder hierarchy on this public folder mailbox. For load-balancing purposes, users are equally distributed across public folder mailboxes by default. When this parameter is set on a public folder mailbox, that mailbox isn't included in this automatic load-balancing and won't be accessed by users to retrieve the public folder hierarchy. However, if an administrator has set the DefaultPublicFolderMailbox property on a user mailbox to a specific public folder mailbox, the user will still access the specified public folder mailbox even if the IsExcludedFromServingHierarchy parameter is set for that public folder mailbox.
+The IsExcludedFromServingHierarchy parameter prevents users from accessing the public folder hierarchy on this public folder mailbox. For load-balancing purposes, users are equally distributed across public folder mailboxes by default. When this parameter is set on a public folder mailbox, that mailbox isn't included in this automatic load-balancing and can't be accessed by users to retrieve the public folder hierarchy. However, if an administrator has set the DefaultPublicFolderMailbox property on a user mailbox to a specific public folder mailbox, the user can still access the specified public folder mailbox, even if the IsExcludedFromServingHierarchy parameter is set for that public folder mailbox.
 
 ```yaml
 Type: Boolean
@@ -1828,7 +1828,7 @@ Accept wildcard characters: False
 The ModerationEnabled parameter specifies whether moderation is enabled for this recipient. Valid value are:
 
 - $true: Moderation is enabled for this recipient. Messages sent to this recipient must be approved by a moderator before the messages are delivered.
-- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This is the default value.
+- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This value is the default.
 
 You use the ModeratedBy parameter to specify the moderators.
 
@@ -1971,7 +1971,7 @@ Accept wildcard characters: False
 
 The RemotePowerShellEnabled parameter specifies whether the user has access to Exchange PowerShell. Valid values are:
 
-- $true: The user has access to Exchange Online PowerShell, the Exchange Management Shell, and the Exchange admin center (EAC). This is the default value.
+- $true: The user has access to Exchange Online PowerShell, the Exchange Management Shell, and the Exchange admin center (EAC). This value is the default.
 - $false: The user has doesn't have access to Exchange Online PowerShell, the Exchange Management Shell, or the EAC.
 
 Access to Exchange PowerShell is required even if you're trying to open the Exchange Management Shell or the EAC on the local Exchange server.
@@ -1997,7 +1997,7 @@ Accept wildcard characters: False
 The ResetPasswordOnNextLogon parameter specifies whether the user is required to change their password the next time they log on to their mailbox. Valid values are:
 
 - $true: The user is required to change their password the next time they log on to their mailbox.
-- $false: The user isn't required to change their password the next time they log on to their mailbox. This is the default value.
+- $false: The user isn't required to change their password the next time they log on to their mailbox. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -2127,7 +2127,7 @@ Accept wildcard characters: False
 
 This parameter is available only in on-premises Exchange.
 
-The SamAccountName parameter (also known as the pre-Windows 2000 user account or group name) specifies an object identifier that's compatible with older versions of Microsoft Windows client and server operating systems. The value can contain letters, numbers, spaces, periods (.), and the following characters: !, #, $, %, ^, &, -, \_, {, }, and ~. The last character can't be a period. Unicode characters are allowed, but accented characters may generate collisions (for example, o and ö match). The maximum length is 20 characters.
+The SamAccountName parameter (also known as the pre-Windows 2000 user account or group name) specifies an object identifier that's compatible with older versions of Microsoft Windows client and server operating systems. The value can contain letters, numbers, spaces, periods (.), and the following characters: !, #, $, %, ^, &, -, \_, {, }, and ~. The last character can't be a period. Unicode characters are allowed, but accented characters might generate collisions (for example, o and ö match). The maximum length is 20 characters.
 
 ```yaml
 Type: String
@@ -2147,7 +2147,7 @@ Accept wildcard characters: False
 
 The SendModerationNotifications parameter specifies when moderation notification messages are sent. Valid values are:
 
-- Always: Notify all senders when their messages aren't approved. This is the default value.
+- Always: Notify all senders when their messages aren't approved. This value is the default.
 - Internal: Notify senders in the organization when their messages aren't approved.
 - Never: Don't notify anyone when a message isn't approved.
 

From 41405d1658954ff0da362c06afe205adef1153c6 Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Wed, 6 Aug 2025 08:58:32 -0700
Subject: [PATCH 097/145] Update New-CsCallQueue.md

---
 teams/teams-ps/MicrosoftTeams/New-CsCallQueue.md | 2 --
 1 file changed, 2 deletions(-)

diff --git a/teams/teams-ps/MicrosoftTeams/New-CsCallQueue.md b/teams/teams-ps/MicrosoftTeams/New-CsCallQueue.md
index 662d585a39..e970422246 100644
--- a/teams/teams-ps/MicrosoftTeams/New-CsCallQueue.md
+++ b/teams/teams-ps/MicrosoftTeams/New-CsCallQueue.md
@@ -16,8 +16,6 @@ title: New-CsCallQueue
 ## SYNOPSIS
 Creates new Call Queue in your Teams organization.
 
-Line to start changes.
-
 ## SYNTAX
 
 ```

From 9eba564c2cc3af05a247227e3a63f08940f7d917 Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Wed, 6 Aug 2025 09:01:06 -0700
Subject: [PATCH 098/145] Create Get-CsPersonalAttendantSettings.md

---
 .../Get-CsPersonalAttendantSettings.md        | 201 ++++++++++++++++++
 1 file changed, 201 insertions(+)
 create mode 100644 teams/teams-ps/MicrosoftTeams/Get-CsPersonalAttendantSettings.md

diff --git a/teams/teams-ps/MicrosoftTeams/Get-CsPersonalAttendantSettings.md b/teams/teams-ps/MicrosoftTeams/Get-CsPersonalAttendantSettings.md
new file mode 100644
index 0000000000..e7a446e77b
--- /dev/null
+++ b/teams/teams-ps/MicrosoftTeams/Get-CsPersonalAttendantSettings.md
@@ -0,0 +1,201 @@
+---
+applicable: Microsoft Teams
+author: juliiva
+external help file: Microsoft.Rtc.Management.dll-Help.xml
+Locale: en-US
+manager: jomarque
+Module Name: MicrosoftTeams
+ms.author: juliiva
+online version: https://learn.microsoft.com/powershell/module/microsoftteams/get-cspersonalattendantsettings
+schema: 2.0.0
+title: Get-CsPersonalAttendantSettings
+---
+
+# Get-CsPersonalAttendantSettings
+
+## SYNOPSIS
+
+**Limited Preview:** Functionality described in this document is currently in limited preview and only authorized organizations have access.
+
+This cmdlet will show personal attendant settings for a user.
+
+## SYNTAX
+
+```
+Get-CsPersonalAttendantSettings -Identity <String> [<CommonParameters>]
+
+```
+
+## DESCRIPTION
+
+This cmdlet shows the personal attendant settings for a user.
+
+## EXAMPLES
+
+### Example 1
+```
+Get-CsPersonalAttendantSettings -Identity user1@contoso.com
+```
+```output
+IsPersonalAttendantEnabled       : True
+DefaultLanguage                  : en-US
+DefaultVoice                     : Female
+CalleeName				         : User1
+DefaultTone				         : Formal
+IsBookingCalendarEnabled         : False
+IsNonContactCallbackEnabled      : False
+IsCallScreeningEnabled           : False
+AllowInboundInternalCalls        : True
+AllowInboundFederatedCalls       : False
+AllowInboundPSTNCalls            : False
+IsAutomaticTranscriptionEnabled  : False
+IsAutomaticRecordingEnabled      : False
+```
+
+This example shows that user1@contoso.com has personal attendant enabled (personal attendant communicates in English). Personal attendant will refer to its owner as User1. 
+Personal attendant is only enabled for inbound Teams calls from the user's domain. Additional capabilities are turned off.
+
+### Example 2
+```
+Get-CsPersonalAttendantSettings -Identity user1@contoso.com
+```
+```output
+IsPersonalAttendantEnabled       : True
+DefaultLanguage                  : en-US
+DefaultVoice                     : Female
+CalleeName				         : User1
+DefaultTone				         : Formal
+IsBookingCalendarEnabled         : True
+IsNonContactCallbackEnabled      : False
+IsCallScreeningEnabled           : False
+AllowInboundInternalCalls        : True
+AllowInboundFederatedCalls       : False
+AllowInboundPSTNCalls            : False
+IsAutomaticTranscriptionEnabled  : False
+IsAutomaticRecordingEnabled      : False
+```
+
+This example shows that user1@contoso.com has personal attendant enabled. In addition to previously mentioned capabilities, personal attendant is able to access personal bookings calendar, 
+fetch the user's availability and schedule callbacks on behalf of the user. Calendar operations are enabled for all incoming callers. user1 must specify the bookings link in Teams Personal Attendant settings.
+
+### Example 3
+```
+Get-CsPersonalAttendantSettings -Identity user1@contoso.com
+```
+```output
+IsPersonalAttendantEnabled       : True
+DefaultLanguage                  : en-US
+DefaultVoice                     : Female
+CalleeName				         : User1
+DefaultTone				         : Formal
+IsBookingCalendarEnabled         : True
+IsNonContactCallbackEnabled      : True
+IsCallScreeningEnabled           : False
+AllowInboundInternalCalls        : True
+AllowInboundFederatedCalls       : True
+AllowInboundPSTNCalls            : True
+IsAutomaticTranscriptionEnabled  : False
+IsAutomaticRecordingEnabled      : False
+```
+
+This example shows that user1@contoso.com has personal attendant enabled. In addition to previously mentioned capabilities, personal attendant is enabled for all incoming calls: the user's domain, other domains and PSTN.
+
+### Example 4
+```
+Get-CsPersonalAttendantSettings -Identity user1@contoso.com
+```
+```output
+IsPersonalAttendantEnabled       : True
+DefaultLanguage                  : en-US
+DefaultVoice                     : Female
+CalleeName				         : User1
+DefaultTone				         : Formal
+IsBookingCalendarEnabled         : True
+IsNonContactCallbackEnabled      : True
+IsCallScreeningEnabled           : True
+AllowInboundInternalCalls        : True
+AllowInboundFederatedCalls       : True
+AllowInboundPSTNCalls            : True
+IsAutomaticTranscriptionEnabled  : False
+IsAutomaticRecordingEnabled      : False
+```
+
+This example shows that user1@contoso.com has personal attendant enabled. In addition to previously mentioned capabilities, personal attendant is enabled to evaluate the call's context and pass the info to the user.
+
+### Example 5
+```
+Get-CsPersonalAttendantSettings -Identity user1@contoso.com
+```
+```output
+IsPersonalAttendantEnabled       : True
+DefaultLanguage                  : en-US
+DefaultVoice                     : Female
+CalleeName				         : User1
+DefaultTone				         : Formal
+IsBookingCalendarEnabled         : True
+IsNonContactCallbackEnabled      : True
+IsCallScreeningEnabled           : True
+AllowInboundInternalCalls        : True
+AllowInboundFederatedCalls       : True
+AllowInboundPSTNCalls            : True
+IsAutomaticTranscriptionEnabled  : True
+IsAutomaticRecordingEnabled      : True
+```
+
+This example shows that user1@contoso.com has personal attendant enabled. In addition to previously mentioned capabilities, personal attendant is automatically storing call transcription and recording.
+
+### Example 6
+```
+Get-CsPersonalAttendantSettings -Identity user11@contoso.com
+```
+```output
+IsPersonalAttendantEnabled       : False
+DefaultLanguage                  : en-US
+DefaultVoice                     : Female
+CalleeName				         : 
+DefaultTone				         : Formal
+IsBookingCalendarEnabled         : False
+IsNonContactCallbackEnabled      : False
+IsCallScreeningEnabled           : True
+AllowInboundInternalCalls        : True
+AllowInboundFederatedCalls       : True
+AllowInboundPSTNCalls            : True
+IsAutomaticTranscriptionEnabled  : True
+IsAutomaticRecordingEnabled      : True
+```
+
+This example shows the default settings for the user that has never changed the personal attendant settings via Microsoft Teams.
+
+## PARAMETERS
+
+### -Identity
+The Identity of the user to show personal attendant settings for. Can be specified using the ObjectId or the SIP address.
+
+```yaml
+Type: System.String
+Parameter Sets: (All)
+Aliases:
+
+Required: True
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### CommonParameters
+This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).
+
+## INPUTS
+
+### None
+
+## OUTPUTS
+
+### System.Object
+
+## NOTES
+The cmdlet is available in Teams PowerShell module 7.3.0 or later.
+
+## RELATED LINKS
+
+[Set-CsPersonalAttendantSettings](./set-cspersonalattendantsettings.md)

From 5bb61064611430afacf98c0224d8a01d23f56e48 Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Wed, 6 Aug 2025 09:04:07 -0700
Subject: [PATCH 099/145] Update Set-CsPersonalAttendantSettings.md

---
 .../Set-CsPersonalAttendantSettings.md        | 26 +++++++++----------
 1 file changed, 13 insertions(+), 13 deletions(-)

diff --git a/teams/teams-ps/MicrosoftTeams/Set-CsPersonalAttendantSettings.md b/teams/teams-ps/MicrosoftTeams/Set-CsPersonalAttendantSettings.md
index 7d85cffd03..3c45a93930 100644
--- a/teams/teams-ps/MicrosoftTeams/Set-CsPersonalAttendantSettings.md
+++ b/teams/teams-ps/MicrosoftTeams/Set-CsPersonalAttendantSettings.md
@@ -122,7 +122,7 @@ This parameter controls whether personal attendant is enabled or not. If persona
 
 ```yaml
 Type: System.Boolean
-Parameter Sets: (PersonalAttendant,PersonalAttendantOnOff)
+Parameter Sets: (All)
 Aliases:
 
 Required: True
@@ -137,7 +137,7 @@ en-US, fr-FR, ar-SA, zh-CN, zh-TW, cs-CZ, da-DK, nl-NL, en-AU, en-GB, fi-FI, fr-
 
 ```yaml
 Type: System.String
-Parameter Sets: (PersonalAttendant)
+Parameter Sets: (All)
 Aliases:
 
 Required: True
@@ -154,7 +154,7 @@ Voice to be used by personal attendant in communication. Supported values are Fe
 
 ```yaml
 Type: System.String
-Parameter Sets: (PersonalAttendant)
+Parameter Sets: (All)
 Aliases:
 
 Required: False
@@ -168,7 +168,7 @@ Name that personal attendant uses when referring to its owner.
 
 ```yaml
 Type: System.String
-Parameter Sets: (PersonalAttendant)
+Parameter Sets: (All)
 Aliases:
 
 Required: False
@@ -185,7 +185,7 @@ Tone to be used by personal attendant in communication. Supported values are For
 
 ```yaml
 Type: System.String
-Parameter Sets: (PersonalAttendant)
+Parameter Sets: (All)
 Aliases:
 
 Required: False
@@ -200,7 +200,7 @@ If access to personal calendar is enabled by admin, user must specify the bookin
 
 ```yaml
 Type: System.Boolean
-Parameter Sets: (PersonalAttendant)
+Parameter Sets: (All)
 Aliases:
 
 Required: True
@@ -217,7 +217,7 @@ This parameter controls whether personal attendant calendar operations for calle
 
 ```yaml
 Type: System.Boolean
-Parameter Sets: (PersonalAttendant)
+Parameter Sets: (All)
 Aliases:
 
 Required: False
@@ -231,7 +231,7 @@ This parameter controls whether personal attendant evaluates calls context and p
 
 ```yaml
 Type: System.Boolean
-Parameter Sets: (PersonalAttendant)
+Parameter Sets: (All)
 Aliases:
 
 Required: True
@@ -245,7 +245,7 @@ This parameter controls whether personal attendant for incoming domain calls is
 
 ```yaml
 Type: System.Boolean
-Parameter Sets: (PersonalAttendant)
+Parameter Sets: (All)
 Aliases:
 
 Required: True
@@ -259,7 +259,7 @@ This parameter controls whether personal attendant for incoming calls from other
 
 ```yaml
 Type: System.Boolean
-Parameter Sets: (PersonalAttendant)
+Parameter Sets: (All)
 Aliases:
 
 Required: True
@@ -273,7 +273,7 @@ This parameter controls whether personal attendant for incoming PSTN calls is en
 
 ```yaml
 Type: System.Boolean
-Parameter Sets: (PersonalAttendant)
+Parameter Sets: (All)
 Aliases:
 
 Required: True
@@ -287,7 +287,7 @@ This parameter controls whether automatic storing of transcriptions (of personal
 
 ```yaml
 Type: System.Boolean
-Parameter Sets: (PersonalAttendant)
+Parameter Sets: (All)
 Aliases:
 
 Required: True
@@ -301,7 +301,7 @@ This parameter controls whether automatic storing of recordings (of personal att
 
 ```yaml
 Type: System.Boolean
-Parameter Sets: (PersonalAttendant)
+Parameter Sets: (All)
 Aliases:
 
 Required: True

From b44ac70deed00e037411179c4e3b77b4ea8a8380 Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Wed, 6 Aug 2025 09:07:27 -0700
Subject: [PATCH 100/145] Update Get-CsPersonalAttendantSettings.md

---
 teams/teams-ps/MicrosoftTeams/Get-CsPersonalAttendantSettings.md | 1 -
 1 file changed, 1 deletion(-)

diff --git a/teams/teams-ps/MicrosoftTeams/Get-CsPersonalAttendantSettings.md b/teams/teams-ps/MicrosoftTeams/Get-CsPersonalAttendantSettings.md
index e7a446e77b..732fec719f 100644
--- a/teams/teams-ps/MicrosoftTeams/Get-CsPersonalAttendantSettings.md
+++ b/teams/teams-ps/MicrosoftTeams/Get-CsPersonalAttendantSettings.md
@@ -23,7 +23,6 @@ This cmdlet will show personal attendant settings for a user.
 
 ```
 Get-CsPersonalAttendantSettings -Identity <String> [<CommonParameters>]
-
 ```
 
 ## DESCRIPTION

From 5e0d6f9f6894d96a110f9f895d0a3d514c8c41f3 Mon Sep 17 00:00:00 2001
From: Chris Davis <chris.davis@microsoft.com>
Date: Wed, 6 Aug 2025 09:08:27 -0700
Subject: [PATCH 101/145] Acrolinx 10

---
 .../ExchangePowerShell/New-MailContact.md     | 16 ++---
 .../ExchangePowerShell/New-MailMessage.md     |  4 +-
 .../ExchangePowerShell/New-MailUser.md        | 22 +++----
 .../New-MailboxAuditLogSearch.md              |  6 +-
 .../ExchangePowerShell/New-MailboxDatabase.md |  2 +-
 .../New-MailboxExportRequest.md               | 18 +++---
 .../ExchangePowerShell/New-MailboxFolder.md   |  4 +-
 .../New-MailboxImportRequest.md               | 12 ++--
 .../New-MailboxRepairRequest.md               |  2 +-
 .../New-MailboxRestoreRequest.md              | 26 ++++----
 .../ExchangePowerShell/New-MailboxSearch.md   | 20 +++---
 .../New-MalwareFilterPolicy.md                | 24 +++----
 .../New-MalwareFilterRule.md                  |  4 +-
 .../New-ManagedContentSettings.md             |  6 +-
 .../ExchangePowerShell/New-ManagedFolder.md   |  4 +-
 .../New-ManagedFolderMailboxPolicy.md         |  2 +-
 .../ExchangePowerShell/New-ManagementRole.md  |  6 +-
 .../New-ManagementRoleAssignment.md           |  8 +--
 .../ExchangePowerShell/New-ManagementScope.md |  4 +-
 .../New-MapiVirtualDirectory.md               | 10 +--
 .../New-MessageClassification.md              | 12 ++--
 .../ExchangePowerShell/New-MigrationBatch.md  | 46 +++++++-------
 .../New-MigrationEndpoint.md                  | 20 +++---
 .../New-MobileDeviceMailboxPolicy.md          |  8 +--
 .../ExchangePowerShell/New-MoveRequest.md     | 22 +++----
 .../New-OMEConfiguration.md                   | 12 ++--
 .../New-OabVirtualDirectory.md                | 14 ++---
 .../New-OfflineAddressBook.md                 | 12 ++--
 .../New-OnPremisesOrganization.md             |  6 +-
 .../New-OrganizationRelationship.md           | 26 ++++----
 .../New-OutboundConnector.md                  | 22 +++----
 .../New-OutlookProtectionRule.md              |  4 +-
 .../ExchangePowerShell/New-OutlookProvider.md |  2 +-
 .../New-OwaMailboxPolicy.md                   |  6 +-
 .../New-OwaVirtualDirectory.md                | 10 +--
 .../New-PartnerApplication.md                 |  4 +-
 .../New-PhishSimOverridePolicy.md             |  6 +-
 .../ExchangePowerShell/New-PolicyTipConfig.md |  4 +-
 .../New-PowerShellVirtualDirectory.md         | 12 ++--
 .../ExchangePowerShell/New-ProtectionAlert.md | 16 ++---
 .../ExchangePowerShell/New-PublicFolder.md    |  4 +-
 .../New-PublicFolderDatabase.md               |  2 +-
 .../New-PublicFolderDatabaseRepairRequest.md  |  2 +-
 .../New-PublicFolderMigrationRequest.md       |  6 +-
 .../New-PublicFolderMoveRequest.md            | 16 ++---
 .../New-QuarantinePermissions.md              | 14 ++---
 .../New-QuarantinePolicy.md                   |  6 +-
 .../New-ReceiveConnector.md                   | 54 ++++++++--------
 .../ExchangePowerShell/New-RemoteDomain.md    |  4 +-
 .../ExchangePowerShell/New-RemoteMailbox.md   | 14 ++---
 .../New-ReportSubmissionPolicy.md             |  6 +-
 .../New-ReportSubmissionRule.md               |  4 +-
 .../New-RetentionCompliancePolicy.md          | 10 +--
 .../New-RetentionComplianceRule.md            | 10 +--
 .../ExchangePowerShell/New-RetentionPolicy.md |  8 +--
 .../New-RetentionPolicyTag.md                 | 10 +--
 .../New-RoleAssignmentPolicy.md               |  6 +-
 .../ExchangePowerShell/New-RoleGroup.md       |  6 +-
 .../New-RoutingGroupConnector.md              |  2 +-
 .../ExchangePowerShell/New-RpcClientAccess.md |  2 +-
 .../New-SafeAttachmentPolicy.md               | 14 ++---
 .../New-SafeAttachmentRule.md                 |  4 +-
 .../ExchangePowerShell/New-SafeLinksPolicy.md | 26 ++++----
 .../ExchangePowerShell/New-SafeLinksRule.md   |  4 +-
 .../New-SearchDocumentFormat.md               |  6 +-
 .../New-SecOpsOverridePolicy.md               |  6 +-
 .../ExchangePowerShell/New-SendConnector.md   | 12 ++--
 .../New-ServicePrincipal.md                   |  2 +-
 .../ExchangePowerShell/New-SettingOverride.md |  2 +-
 .../ExchangePowerShell/New-SharingPolicy.md   |  8 +--
 .../ExchangePowerShell/New-SiteMailbox.md     |  2 +-
 .../New-SiteMailboxProvisioningPolicy.md      | 12 ++--
 .../ExchangePowerShell/New-SweepRule.md       |  6 +-
 .../New-SyncMailPublicFolder.md               | 10 +--
 .../ExchangePowerShell/New-SystemMessage.md   |  4 +-
 .../New-TeamsProtectionPolicy.md              |  4 +-
 .../New-TeamsProtectionPolicyRule.md          |  2 +-
 .../New-TenantAllowBlockListItems.md          |  4 +-
 .../New-TenantAllowBlockListSpoofItems.md     |  2 +-
 .../New-ThrottlingPolicy.md                   | 14 ++---
 .../ExchangePowerShell/New-TransportRule.md   | 62 +++++++++----------
 .../ExchangePowerShell/New-UMAutoAttendant.md |  6 +-
 .../New-UMCallAnsweringRule.md                | 12 ++--
 .../ExchangePowerShell/New-UMDialPlan.md      |  2 +-
 .../ExchangePowerShell/New-UMHuntGroup.md     |  2 +-
 .../ExchangePowerShell/New-UMIPGateway.md     | 10 +--
 .../ExchangePowerShell/New-UMMailboxPolicy.md |  2 +-
 .../New-UnifiedAuditLogRetentionPolicy.md     |  2 +-
 .../ExchangePowerShell/New-UnifiedGroup.md    | 18 +++---
 .../New-WebServicesVirtualDirectory.md        | 24 +++----
 .../New-X400AuthoritativeDomain.md            |  2 +-
 .../Preview-QuarantineMessage.md              |  2 +-
 .../ExchangePowerShell/Redirect-Message.md    |  4 +-
 .../Release-QuarantineMessage.md              |  4 +-
 .../Remove-AcceptedDomain.md                  |  2 +-
 .../Remove-ActiveSyncDevice.md                |  4 +-
 .../Remove-ActiveSyncDeviceAccessRule.md      |  4 +-
 97 files changed, 480 insertions(+), 476 deletions(-)

diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MailContact.md b/exchange/exchange-ps/ExchangePowerShell/New-MailContact.md
index 7c7abb37c4..38a1dafa95 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-MailContact.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-MailContact.md
@@ -13,7 +13,7 @@ title: New-MailContact
 # New-MailContact
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the New-MailContact cmdlet to create mail contacts.
 
@@ -45,7 +45,7 @@ New-MailContact -Name <String> -ExternalEmailAddress <ProxyAddress>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -286,7 +286,7 @@ Accept wildcard characters: False
 
 The MacAttachmentFormat parameter specifies the Apple Macintosh operating system attachment format to use for messages sent to the mail contact or mail user. Valid values are:
 
-- BinHex (This is the default value)
+- BinHex (default value)
 - UuEncode
 - AppleSingle
 - AppleDouble
@@ -316,7 +316,7 @@ The MessageBodyFormat parameter specifies the message body format for messages s
 
 - Text
 - Html
-- TextAndHtml (This is the default value)
+- TextAndHtml (default value)
 
 The MessageFormat and MessageBodyFormat parameters are interdependent:
 
@@ -343,7 +343,7 @@ The MessageBodyFormat parameter specifies the message body format for messages s
 
 - Text
 - Html
-- TextAndHtml (This is the default value)
+- TextAndHtml (default value)
 
 The MessageFormat and MessageBodyFormat parameters are interdependent:
 
@@ -398,7 +398,7 @@ Accept wildcard characters: False
 The ModerationEnabled parameter specifies whether moderation is enabled for this recipient. Valid value are:
 
 - $true: Moderation is enabled for this recipient. Messages sent to this recipient must be approved by a moderator before the messages are delivered.
-- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This is the default value.
+- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This value is the default.
 
 You use the ModeratedBy parameter to specify the moderators.
 
@@ -469,7 +469,7 @@ Accept wildcard characters: False
 
 The SendModerationNotifications parameter specifies when moderation notification messages are sent. Valid values are:
 
-- Always: Notify all senders when their messages aren't approved. This is the default value.
+- Always: Notify all senders when their messages aren't approved. This value is the default.
 - Internal: Notify senders in the organization when their messages aren't approved.
 - Never: Don't notify anyone when a message isn't approved.
 
@@ -494,7 +494,7 @@ Accept wildcard characters: False
 The UsePreferMessageFormat specifies whether the message format settings configured for the mail user or mail contact override the global settings configured for the remote domain or configured by the message sender. Valid value are:
 
 - $true: Messages sent to the mail user or mail contact use the message format that's configured for the mail user or mail contact.
-- $false: Messages sent to the mail user or mail contact use the message format that's configured for the remote domain (the default remote domain or a specific remote domain) or configured by the message sender. This is the default value.
+- $false: Messages sent to the mail user or mail contact use the message format that's configured for the remote domain (the default remote domain or a specific remote domain) or configured by the message sender. This value is the default.
 
 ```yaml
 Type: Boolean
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MailMessage.md b/exchange/exchange-ps/ExchangePowerShell/New-MailMessage.md
index 15dda9b258..a2f50ad71e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-MailMessage.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-MailMessage.md
@@ -13,7 +13,7 @@ title: New-MailMessage
 # New-MailMessage
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the New-MailMessage cmdlet to create an email message for the specified user mailbox and place the email message in the Drafts folder of the user's mailbox.
 
@@ -35,7 +35,7 @@ New-MailMessage
 ## DESCRIPTION
 If the cmdlet is run without specifying the Subject or Body parameters, an empty email message is placed in the user's Drafts folder.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MailUser.md b/exchange/exchange-ps/ExchangePowerShell/New-MailUser.md
index b40c8f5a49..3aa57b37d4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-MailUser.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-MailUser.md
@@ -13,7 +13,7 @@ title: New-MailUser
 # New-MailUser
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the New-MailUser cmdlet to create mail users. Mail users (also known as mail-enabled users) have email addresses and accounts in the Exchange organization, but they don't have Exchange mailboxes. Email messages sent to mail users are delivered to the specified external email address.
 
@@ -221,7 +221,7 @@ New-MailUser [-Name] <String> -MicrosoftOnlineServicesID <WindowsLiveId> -Passwo
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -604,7 +604,7 @@ Accept wildcard characters: False
 
 The MacAttachmentFormat parameter specifies the Apple Macintosh operating system attachment format to use for messages sent to the mail contact or mail user. Valid values are:
 
-- BinHex (This is the default value)
+- BinHex (default value)
 - UuEncode
 - AppleSingle
 - AppleDouble
@@ -654,7 +654,7 @@ The MessageBodyFormat parameter specifies the message body format for messages s
 
 - Text
 - Html
-- TextAndHtml (This is the default value)
+- TextAndHtml (default value)
 
 The MessageFormat and MessageBodyFormat parameters are interdependent:
 
@@ -680,7 +680,7 @@ Accept wildcard characters: False
 The MessageFormat parameter specifies the message format for messages sent to the mail contact or mail user. Valid values are:
 
 - Text
-- Mime (This is the default value)
+- Mime (default value)
 
 The MessageFormat and MessageBodyFormat parameters are interdependent:
 
@@ -737,7 +737,7 @@ Accept wildcard characters: False
 The ModerationEnabled parameter specifies whether moderation is enabled for this recipient. Valid value are:
 
 - $true: Moderation is enabled for this recipient. Messages sent to this recipient must be approved by a moderator before the messages are delivered.
-- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This is the default value.
+- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This value is the default.
 
 You use the ModeratedBy parameter to specify the moderators.
 
@@ -808,7 +808,7 @@ Accept wildcard characters: False
 
 The RemotePowerShellEnabled parameter specifies whether the user has access to Exchange PowerShell. Valid values are:
 
-- $true: The user has access to Exchange Online PowerShell, the Exchange Management Shell, and the Exchange admin center (EAC). This is the default value.
+- $true: The user has access to Exchange Online PowerShell, the Exchange Management Shell, and the Exchange admin center (EAC). This value is the default.
 - $false: The user has doesn't have access to Exchange Online PowerShell, the Exchange Management Shell, or the EAC.
 
 Access to Exchange PowerShell is required even if you're trying to open the Exchange Management Shell or the EAC on the local Exchange server.
@@ -836,7 +836,7 @@ This parameter is available only in on-premises Exchange.
 The ResetPasswordOnNextLogon parameter specifies whether the user must change their password the next time they log on. Valid values are:
 
 - $true: The user is required to change their password the next time they log on.
-- $false: The user isn't required to change their password the next time they log on. This is the default value.
+- $false: The user isn't required to change their password the next time they log on. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -856,7 +856,7 @@ Accept wildcard characters: False
 
 This parameter is available only in on-premises Exchange.
 
-The SamAccountName parameter (also known as the pre-Windows 2000 user account or group name) specifies an object identifier that's compatible with older versions of Microsoft Windows client and server operating systems. The value can contain letters, numbers, spaces, periods (.), and the following characters: !, #, $, %, ^, &, -, \_, {, }, and ~. The last character can't be a period. Unicode characters are allowed, but accented characters may generate collisions (for example, o and ö match). The maximum length is 20 characters.
+The SamAccountName parameter (also known as the pre-Windows 2000 user account or group name) specifies an object identifier that's compatible with older versions of Microsoft Windows client and server operating systems. The value can contain letters, numbers, spaces, periods (.), and the following characters: !, #, $, %, ^, &, -, \_, {, }, and ~. The last character can't be a period. Unicode characters are allowed, but accented characters might generate collisions (for example, o and ö match). The maximum length is 20 characters.
 
 ```yaml
 Type: String
@@ -876,7 +876,7 @@ Accept wildcard characters: False
 
 The SendModerationNotifications parameter specifies when moderation notification messages are sent. Valid values are:
 
-- Always: Notify all senders when their messages aren't approved. This is the default value.
+- Always: Notify all senders when their messages aren't approved. This value is the default.
 - Internal: Notify senders in the organization when their messages aren't approved.
 - Never: Don't notify anyone when a message isn't approved.
 
@@ -901,7 +901,7 @@ Accept wildcard characters: False
 The UsePreferMessageFormat specifies whether the message format settings configured for the mail user or mail contact override the global settings configured for the remote domain or configured by the message sender. Valid value are:
 
 - $true: Messages sent to the mail user or mail contact use the message format that's configured for the mail user or mail contact.
-- $false: Messages sent to the mail user or mail contact use the message format that's configured for the remote domain (the default remote domain or a specific remote domain) or configured by the message sender. This is the default value.
+- $false: Messages sent to the mail user or mail contact use the message format that's configured for the remote domain (the default remote domain or a specific remote domain) or configured by the message sender. This value is the default.
 
 ```yaml
 Type: Boolean
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MailboxAuditLogSearch.md b/exchange/exchange-ps/ExchangePowerShell/New-MailboxAuditLogSearch.md
index 668aa944b8..4aa8ca23e8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-MailboxAuditLogSearch.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-MailboxAuditLogSearch.md
@@ -16,7 +16,7 @@ title: New-MailboxAuditLogSearch
 > [!NOTE]
 > This cmdlet will be deprecated in the cloud-based service. To access audit log data, use the Search-UnifiedAuditLog cmdlet. For more information, see this blog post: <https://aka.ms/AuditCmdletBlog>.
 
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the New-MailboxAuditLogSearch cmdlet to search mailbox audit logs and have search results sent via email to specified recipients.
 
@@ -45,7 +45,7 @@ The New-MailboxAuditLogSearch cmdlet performs an asynchronous search of mailbox
 
 To search mailbox audit logs for a single mailbox and have the results displayed in the Exchange Management Shell window, use the Search-MailboxAuditLog cmdlet instead. To learn more about mailbox audit logging, see [Mailbox audit logging in Exchange Server](https://learn.microsoft.com/Exchange/policy-and-compliance/mailbox-audit-logging/mailbox-audit-logging).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -172,7 +172,7 @@ The ExternalAccess parameter specifies whether to return only audit log entries
 
 $true: Audit log entries for mailbox access by external users or Microsoft datacenter administrators are returned.
 
-$false: Audit log entries for mailbox access by external users or Microsoft datacenter administrators are ignored. This is the default value.
+$false: Audit log entries for mailbox access by external users or Microsoft datacenter administrators are ignored. This value is the default.
 
 ```yaml
 Type: Boolean
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MailboxDatabase.md b/exchange/exchange-ps/ExchangePowerShell/New-MailboxDatabase.md
index 6626bb96cf..13b7f9cdaf 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-MailboxDatabase.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-MailboxDatabase.md
@@ -53,7 +53,7 @@ New-MailboxDatabase [[-Name] <String>] -Server <ServerIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MailboxExportRequest.md b/exchange/exchange-ps/ExchangePowerShell/New-MailboxExportRequest.md
index 60444e5677..a4d5b91ef0 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-MailboxExportRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-MailboxExportRequest.md
@@ -120,14 +120,14 @@ New-MailboxExportRequest [-Mailbox] <MailboxLocationIdParameter> -ComplianceStor
 ## DESCRIPTION
 You can create more than one mailbox export request per mailbox, and each mailbox export request must have a unique name. Microsoft Exchange automatically generates up to 10 unique names for a mailbox export request. However, to create more than 10 export requests for a mailbox, you need to specify a unique name when creating the export request. You can remove existing export requests with the Remove-MailboxExportRequest cmdlet before starting a new request with the default request name `<alias>\MailboxExportX` (where X = 0-9).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 You need to grant the following permission to the group Exchange Trusted Subsystem to the network share where you want to export or import PST files:
 
 - To import PST files from the share: Read permission
 - To save exported PST files to the share: Read/Write permission.
 
-If you don't grant this permission, you will receive an error message stating that Exchange is unable to establish a connection to the PST file on the network share.
+If you don't grant this permission, you get an error message stating that Exchange is unable to establish a connection to the PST file on the network share.
 
 ## EXAMPLES
 
@@ -223,7 +223,7 @@ You need to grant the following permission to the group Exchange Trusted Subsyst
 - To import PST files from the share: Read permission
 - To save exported PST files to the share: Read/Write permission.
 
-If you don't grant this permission, you will receive an error message stating that Exchange is unable to establish a connection to the PST file on the network share.
+If you don't grant this permission, you get an error message stating that Exchange is unable to establish a connection to the PST file on the network share.
 
 ```yaml
 Type: LongPath
@@ -345,7 +345,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-The CompletedRequestAgeLimit parameter specifies how long the request will be kept after it has completed before being automatically removed. The default CompletedRequestAgeLimit is 30 days.
+The CompletedRequestAgeLimit parameter specifies how long the request is kept after completion before it's automatically removed. The default value is 30 days.
 
 ```yaml
 Type: Unlimited
@@ -389,7 +389,7 @@ The ConflictResolutionOption parameter specifies what to do if there are multipl
 - ForceCopy
 - KeepAll
 - KeepLatestItem
-- KeepSourceItem (This is the default value.)
+- KeepSourceItem (This value is the default.)
 - KeepTargetItem
 - UpdateFromSource
 
@@ -409,9 +409,9 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-**Important**: You can't use this parameter to export between two dates. If you try, you'll get system convert errors. You can export from a specific date, or export to a specific date, but not both.
+**Important**: You can't use this parameter to export between two dates. You can export from a specific date, or export to a specific date, but not both.
 
-The ContentFilter parameter uses OPATH filter syntax to filter the results by the specified properties and values. Only contents that match the ContentFilter parameter will be exported into the .pst file. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`.
+The ContentFilter parameter uses OPATH filter syntax to filter the results by the specified properties and values. Only contents that match the ContentFilter parameter are exported into the .pst file. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`.
 
 - Enclose the whole OPATH filter in double quotation marks " ". If the filter contains system values (for example, `$true`, `$false`, or `$null`), use single quotation marks ' ' instead. Although this parameter is a string (not a system block), you can also use braces { }, but only if the filter doesn't contain variables.
 - Property is a filterable property. For filterable properties, see [Filterable properties for the ContentFilter parameter](https://learn.microsoft.com/exchange/filterable-properties-for-the-contentfilter-parameter).
@@ -721,7 +721,7 @@ The Priority parameter specifies the order in which the request should be proces
 
 - Lower
 - Low
-- Normal (This is the default value.)
+- Normal (This value is the default.)
 - High
 - Higher
 - Highest
@@ -824,7 +824,7 @@ Accept wildcard characters: False
 
 The Suspend switch specifies whether to suspend the request. You don't need to specify a value with this switch.
 
-If you use this switch, the request is queued, but the request won't reach the status of InProgress until you resume the request with the relevant resume cmdlet.
+If you use this switch, the request is queued, but the request doesn't reach the status of InProgress until you resume the request with the relevant resume cmdlet.
 
 ```yaml
 Type: SwitchParameter
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MailboxFolder.md b/exchange/exchange-ps/ExchangePowerShell/New-MailboxFolder.md
index 01dfb10e92..d7e9d64fe5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-MailboxFolder.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-MailboxFolder.md
@@ -13,7 +13,7 @@ title: New-MailboxFolder
 # New-MailboxFolder
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the New-MailboxFolder cmdlet to create folders in your own mailbox. Administrators can't use this cmdlet to create folders in other mailboxes (the cmdlet is available only from the MyBaseOptions user role).
 
@@ -32,7 +32,7 @@ New-MailboxFolder [-Name] <String> -Parent <MailboxFolderIdParameter>
 ## DESCRIPTION
 If no parent folder is specified, the cmdlet creates a mail folder in the root folder hierarchy of the mailbox. If the mailbox isn't specified, the cmdlet creates the folder in the mailbox of the user currently running the task. When run, the cmdlet returns the new folder name and the folder path as the output.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). .
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). .
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MailboxImportRequest.md b/exchange/exchange-ps/ExchangePowerShell/New-MailboxImportRequest.md
index 935c6d2a7b..3354f48df9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-MailboxImportRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-MailboxImportRequest.md
@@ -13,7 +13,7 @@ title: New-MailboxImportRequest
 # New-MailboxImportRequest
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the New-MailboxImportRequest cmdlet to begin the process of importing a .pst file to a mailbox or archive.
 
@@ -133,7 +133,7 @@ In on-premises Exchange, you need to grant the following permission to the group
 - To import PST files from the share: Read permission
 - To save exported PST files to the share: Read/Write permission.
 
-If you don't grant this permission, you will receive an error message stating that Exchange is unable to establish a connection to the PST file on the network share.
+If you don't grant this permission, you get an error message stating that Exchange is unable to establish a connection to the PST file on the network share.
 
 ## EXAMPLES
 
@@ -246,7 +246,7 @@ You need to grant the following permission to the group Exchange Trusted Subsyst
 - To import PST files from the share: Read permission
 - To save exported PST files to the share: Read/Write permission.
 
-If you don't grant this permission, you will receive an error message stating that Exchange is unable to establish a connection to the PST file on the network share.
+If you don't grant this permission, you get an error message stating that Exchange is unable to establish a connection to the PST file on the network share.
 
 ```yaml
 Type: LongPath
@@ -370,7 +370,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
 
-The CompletedRequestAgeLimit parameter specifies how long the request will be kept after it has completed before being automatically removed. The default value of the CompletedRequestAgeLimit parameter is 30 days.
+The CompletedRequestAgeLimit parameter specifies how long the request is kept after completion before being automatically removed. The default value is 30 days.
 
 ```yaml
 Type: Unlimited
@@ -414,7 +414,7 @@ The ConflictResolutionOption parameter specifies what to do if there are multipl
 - ForceCopy (Exchange 2016 or later)
 - KeepAll
 - KeepLatestItem
-- KeepSourceItem (This is the default value)
+- KeepSourceItem (default value)
 - KeepTargetItem (Exchange 2016 or later)
 - UpdateFromSource (Exchange 2016 or later)
 
@@ -894,7 +894,7 @@ Accept wildcard characters: False
 
 The Suspend switch specifies whether to suspend the request. You don't need to specify a value with this switch.
 
-If you use this switch, the request is queued, but the request won't reach the status of InProgress until you resume the request with the relevant resume cmdlet.
+If you use this switch, the request is queued, but the request doesn't reach the status of InProgress until you resume the request with the relevant resume cmdlet.
 
 ```yaml
 Type: SwitchParameter
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MailboxRepairRequest.md b/exchange/exchange-ps/ExchangePowerShell/New-MailboxRepairRequest.md
index e79715622b..4342464833 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-MailboxRepairRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-MailboxRepairRequest.md
@@ -51,7 +51,7 @@ After you begin a repair request, you can't stop it unless you dismount the data
 
 To avoid performance problems, only one request can be active on a server for a database-level repair, or up to 100 requests can be active on a server for a mailbox-level repair.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MailboxRestoreRequest.md b/exchange/exchange-ps/ExchangePowerShell/New-MailboxRestoreRequest.md
index b5a99217c4..4df394dfdc 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-MailboxRestoreRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-MailboxRestoreRequest.md
@@ -13,7 +13,7 @@ title: New-MailboxRestoreRequest
 # New-MailboxRestoreRequest
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the New-MailboxRestoreRequest cmdlet to restore a soft-deleted or disconnected mailbox. This cmdlet starts the process of moving content from the soft-deleted mailbox, disabled mailbox, or any mailbox in a recovery database into a connected primary or archive mailbox.
 
@@ -220,15 +220,15 @@ To view soft-deleted mailboxes, run the Get-MailboxStatistics cmdlet against a d
 
 A mailbox is marked as Disabled a short time after the Disable-Mailbox or Remove-Mailbox command completes.
 
-The mailbox won't be marked as Disabled until the Microsoft Exchange Information Store service determines that Active Directory has been updated with the disabled mailbox's information. You can expedite the process by running the Update-StoreMailboxState cmdlet against that database.
+The mailbox isn't marked as Disabled until the Microsoft Exchange Information Store service determines that Active Directory is updated with the disabled mailbox's information. You can expedite the process by running the Update-StoreMailboxState cmdlet against that database.
 
 Exchange retains disabled mailboxes in the mailbox database based on the deleted mailbox retention settings configured for that mailbox database. After the specified period of time, the mailbox is permanently deleted.
 
 To view disabled mailboxes, run the Get-MailboxStatistics cmdlet against a database and look for results that have a DisconnectReason with a value of Disabled. For more information, see Examples 2 and 3 later in this topic.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
-**Note**: To restore the contents of a primary mailbox to an archive mailbox, use the TargetRootFolder parameter to specify the archive mailbox folders to migrate the content to. This content will be visible after it's restored. If you don't use this parameter, the restored content is not visible because it's mapped to locations in the archive mailbox that aren't visible to users.
+**Note**: To restore the contents of a primary mailbox to an archive mailbox, use the TargetRootFolder parameter to specify the archive mailbox folders to migrate the content to. This content is visible after it's restored. If you don't use this parameter, the restored content is not visible because it's mapped to locations in the archive mailbox that aren't visible to users.
 
 ## EXAMPLES
 
@@ -563,7 +563,7 @@ The AssociatedMessagesCopyOption parameter specifies whether associated messages
 
 - DoNotCopy: The associated messages aren't copied.
 - MapByMessageClass: Find the associated message by looking up the MessageClass attribute of the source message. If there's an associated message of this class in both source and target folders, it overwrites the associated message in the target. If there isn't an associated message in the target, it creates a copy in the target.
-- Copy: Copy associated messages from the source to the target. If the same message type exists both in the source and the target location, these associated messages are duplicated. This is the default value.
+- Copy: Copy associated messages from the source to the target. If the same message type exists both in the source and the target location, these associated messages are duplicated. This value is the default.
 
 Content filtering doesn't apply to associated messages.
 
@@ -589,7 +589,7 @@ Valid input for this parameter is an integer or the value unlimited. The default
 
 In Exchange 2010, if you set this value to 51 or higher, you also need to use the AcceptLargeDataLoss switch. Otherwise, the command will fail.
 
-**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics will be used instead.
+**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics are used instead.
 
 ```yaml
 Type: Unlimited
@@ -669,7 +669,7 @@ The ConflictResolutionOption parameter specifies what to do if there are multipl
 - ForceCopy
 - KeepAll
 - KeepLatestItem
-- KeepSourceItem (This is the default value.)
+- KeepSourceItem (This value is the default.)
 - KeepTargetItem
 - UpdateFromSource
 
@@ -691,7 +691,7 @@ Accept wildcard characters: False
 
 This parameter is available only in the cloud-based service.
 
-The ContentFilter parameter uses OPATH filter syntax to filter the results by the specified properties and values. Only contents that match the ContentFilter parameter will be restored. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`.
+The ContentFilter parameter uses OPATH filter syntax to filter the results by the specified properties and values. Only contents that match the ContentFilter parameter are restored. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`.
 
 - Enclose the whole OPATH filter in double quotation marks " ". If the filter contains system values (for example, `$true`, `$false`, or `$null`), use single quotation marks ' ' instead. Although this parameter is a string (not a system block), you can also use braces { }, but only if the filter doesn't contain variables.
 - Property is a filterable property. For filterable properties, see [Filterable properties for the ContentFilter parameter](https://learn.microsoft.com/exchange/filterable-properties-for-the-contentfilter-parameter).
@@ -907,7 +907,7 @@ Valid input for this parameter is an integer or the value unlimited. The default
 
 If you set this value to 51 or higher, you also need to use the AcceptLargeDataLoss switch. Otherwise, the command will fail.
 
-**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics will be used instead.
+**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics are used instead.
 
 ```yaml
 Type: Unlimited
@@ -972,7 +972,7 @@ The Priority parameter specifies the order in which the request should be proces
 - Lowest
 - Lower
 - Low
-- Normal (This is the default value.)
+- Normal (This value is the default.)
 - High
 - Higher
 - Highest
@@ -1086,7 +1086,7 @@ Accept wildcard characters: False
 
 The Suspend switch specifies whether to suspend the request. You don't need to specify a value with this switch.
 
-If you use this switch, the request is queued, but the request won't reach the status of InProgress until you resume the request with the relevant resume cmdlet.
+If you use this switch, the request is queued, but the request doesn't reach the status of InProgress until you resume the request with the relevant resume cmdlet.
 
 ```yaml
 Type: SwitchParameter
@@ -1142,7 +1142,7 @@ Accept wildcard characters: False
 
 The TargetRootFolder parameter specifies the top-level folder in which to restore data. If you don't specify this parameter, the command restores folders to the top of the folder structure in the target mailbox or archive. Content is merged under existing folders, and new folders are created if they don't already exist in the target folder structure.
 
-**Note**: To restore the contents of a primary mailbox to an archive mailbox, use this parameter to specify the archive mailbox folders to migrate the content to. This content will be visible after it's restored. If you don't use this parameter, the restored content is not visible because it's mapped to locations in the archive mailbox that aren't visible to users.
+**Note**: To restore the contents of a primary mailbox to an archive mailbox, use this parameter to specify the archive mailbox folders to migrate the content to. This content is visible after it's restored. If you don't use this parameter, the restored content is not visible because it's mapped to locations in the archive mailbox that aren't visible to users.
 
 ```yaml
 Type: String
@@ -1164,7 +1164,7 @@ The TargetType parameter specifies the type of mailbox that's the target for the
 
 - Archive
 - MailboxLocation
-- Primary (This is the default value)
+- Primary (default value)
 
 ```yaml
 Type: TargetTypeComponent
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MailboxSearch.md b/exchange/exchange-ps/ExchangePowerShell/New-MailboxSearch.md
index 33a76bb56f..36cb459e8b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-MailboxSearch.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-MailboxSearch.md
@@ -13,7 +13,7 @@ title: New-MailboxSearch
 # New-MailboxSearch
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the New-MailboxSearch cmdlet to create a mailbox search and either get an estimate of search results, place search results on In-Place Hold or copy them to a Discovery mailbox. You can also place all contents in a mailbox on hold by not specifying a search query, which accomplishes similar results as Litigation Hold.
 
@@ -62,7 +62,7 @@ By default, mailbox searches are performed across all Exchange 2013 or later Mai
 
 For more information, see [In-Place eDiscovery in Exchange Server](https://learn.microsoft.com/Exchange/policy-and-compliance/ediscovery/ediscovery) and [In-Place Hold and Litigation Hold in Exchange Server](https://learn.microsoft.com/Exchange/policy-and-compliance/holds/holds).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -130,7 +130,7 @@ Accept wildcard characters: False
 The AllPublicFolderSources parameter specifies whether to include all public folders in the organization in the search. Valid values are:
 
 - $true: All public folders are included in the search. This value is required when the value of the AllSourceMailboxes parameter is $false and you don't specify one or more source mailboxes by using the SourceMailboxes parameter (the parameter value is blank [$null]).
-- $false: No public folders are included in the search. This is the default value. You can use this value when the value of the AllSourceMailboxes parameter is $true or you specify one or more source mailboxes by using the SourceMailboxes parameter (the parameter value isn't blank [$null]).
+- $false: No public folders are included in the search. This value is the default. You can use this value when the value of the AllSourceMailboxes parameter is $true or you specify one or more source mailboxes by using the SourceMailboxes parameter (the parameter value isn't blank [$null]).
 
 ```yaml
 Type: Boolean
@@ -151,7 +151,7 @@ Accept wildcard characters: False
 The AllSourceMailboxes parameter specifies whether to include all mailboxes in the search. Valid values are:
 
 - $true: All mailboxes are included in the search. This value is required when the value of the AllPublicFolderSources parameter is $false and you don't specify one or more source mailboxes by using the SourceMailboxes parameter (the parameter value is blank [$null]).
-- $false: All mailboxes aren't included in the search. This is the default value. You can use this value when the value of the AllPublicFolderSources parameter is $true or you specify one or more source mailboxes by using the SourceMailboxes parameter (the parameter value isn't blank [$null]).
+- $false: All mailboxes aren't included in the search. This value is the default. You can use this value when the value of the AllPublicFolderSources parameter is $true or you specify one or more source mailboxes by using the SourceMailboxes parameter (the parameter value isn't blank [$null]).
 
 ```yaml
 Type: Boolean
@@ -270,7 +270,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
 
-The EstimateOnly switch specifies that only an estimate of the number of items that will be returned is provided. You don't need to specify a value with this switch.
+The EstimateOnly switch specifies that only an estimate of the number of items to be returned is provided. You don't need to specify a value with this switch.
 
 If you don't use this switch, messages are copied to the target mailbox.
 
@@ -292,7 +292,7 @@ Accept wildcard characters: False
 
 The ExcludeDuplicateMessages parameter eliminates duplication of messages in search results. Valid values are:
 
-- $true: Copy a single instance of a message if the same message exists in multiple folders or mailboxes. This is the default value.
+- $true: Copy a single instance of a message if the same message exists in multiple folders or mailboxes. This value is the default.
 - $false: Copy all instances of a message if the same message exists in multiple folders or mailboxes.
 
 ```yaml
@@ -372,11 +372,11 @@ Accept wildcard characters: False
 The InPlaceHoldEnabled parameter specifies whether to set an In-Place Hold on items in the search results. Valid values are:
 
 - $true: In-Place Hold is enabled on the search results.
-- $false: In-Place Hold isn't enabled on the search results. This is the default value.
+- $false: In-Place Hold isn't enabled on the search results. This value is the default.
 
 You can't set an In-Place Hold on the search results when the AllSourceMailboxes parameter is $true.
 
-If you attempt to place a hold but don't specify mailboxes using the SourceMailboxes parameter, the command may succeed but the mailboxes are not placed on In-Place Hold.
+If you attempt to place a hold but don't specify mailboxes using the SourceMailboxes parameter, the command might succeed but the mailboxes are not placed on In-Place Hold.
 
 ```yaml
 Type: Boolean
@@ -415,7 +415,7 @@ Accept wildcard characters: False
 The ItemHoldPeriod parameter specifies the number of days for the In-Place Hold onthe mailbox items (all mailbox items or the items that are returned in the search query results). The duration is calculated from the time the item is received or created in the mailbox. Valid values are:
 
 - An integer.
-- The value unlimited. This is the default value. Items are held until you remove the In-Place Hold by removing the search by using the Remove-MailboxSearch cmdlet, removing the source mailbox from the search by using the Set-MailboxSearch cmdlet and the SourceMailboxes parameter, or in on-premises Exchange, you remove all public folders from the search by using the Set-MailboxSearch cmdlet to change the AllPublicFolderSources parameter from $true to $false.
+- The value unlimited. This value is the default. Items are held until you remove the In-Place Hold by removing the search by using the Remove-MailboxSearch cmdlet, removing the source mailbox from the search by using the Set-MailboxSearch cmdlet and the SourceMailboxes parameter, or in on-premises Exchange, you remove all public folders from the search by using the Set-MailboxSearch cmdlet to change the AllPublicFolderSources parameter from $true to $false.
 
 ```yaml
 Type: Unlimited
@@ -456,7 +456,7 @@ Accept wildcard characters: False
 The LogLevel parameter specifies the logging level for the search. Valid values are:
 
 - Suppress: No logs are kept.
-- Basic: Basic information about the query and who ran it is kept. This is the default value.
+- Basic: Basic information about the query and who ran it is kept. This value is the default.
 - Full: In addition to the information kept by the Basic log level, the Full log level adds a complete list of search results.
 
 ```yaml
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MalwareFilterPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-MalwareFilterPolicy.md
index b137806a42..952710db59 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-MalwareFilterPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-MalwareFilterPolicy.md
@@ -13,7 +13,7 @@ title: New-MalwareFilterPolicy
 # New-MalwareFilterPolicy
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the New-MalwareFilterPolicy cmdlet to create malware filter policies in your organization.
 
@@ -56,7 +56,7 @@ New-MalwareFilterPolicy [-Name] <String>
 ## DESCRIPTION
 New policies that you create using this cmdlet aren't applied to users and aren't visible in admin centers. You need to use the MalwareFilterPolicy parameter on the New-MalwareFilterRule or Set-MalwareFilterRule cmdlets to associate the policy with a rule.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -98,7 +98,7 @@ This parameter is available only in on-premises Exchange.
 
 The Action parameter specifies the action to take when malware is detected in a message. Valid values are:
 
-- DeleteMessage: Handles the message without notifying the recipients. This is the default value.
+- DeleteMessage: Handles the message without notifying the recipients. This value is the default.
 - DeleteAttachmentAndUseDefaultAlert: Delivers the message, but replaces all attachments with a file named Malware Alert Text.txt that contains the default alert text.
 - DeleteAttachmentAndUseCustomAlert: Delivers the message, but replaces all attachments with a file named Malware Alert Text.txt that contains the custom alert text specified by the CustomAlertText parameter.
 
@@ -141,7 +141,7 @@ This parameter is available only in on-premises Exchange.
 The BypassInboundMessages parameter enables or disables malware filtering on incoming messages (messages entering the organization). Valid values are:
 
 - $true: Malware filtering is disabled on inbound messages.
-- $false: Malware filtering is enabled on inbound messages. This is the default value.
+- $false: Malware filtering is enabled on inbound messages. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -164,7 +164,7 @@ This parameter is available only in on-premises Exchange.
 The BypassOutboundMessages parameter enables or disables malware filtering on outgoing messages (messages leaving the organization). Valid values are:
 
 - $true: Malware filtering is disabled on outbound messages.
-- $false: Malware filtering is enabled on outbound messages. This is the default value.
+- $false: Malware filtering is enabled on outbound messages. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -418,7 +418,7 @@ Accept wildcard characters: False
 The EnableExternalSenderAdminNotifications parameter enables or disables sending notification messages to an administrator for malware detections in messages from internal senders. Valid values are:
 
 - $true: When malware attachments are detected in messages from external senders, a notification messages is sent to the email address that's specified by the ExternalSenderAdminAddress parameter.
-- $false: Notifications aren't sent for malware attachment detections in messages from external senders. This is the default value.
+- $false: Notifications aren't sent for malware attachment detections in messages from external senders. This value is the default.
 
 **Note**: Admin notifications are sent only for _attachments_ that are classified as malware.
 
@@ -443,7 +443,7 @@ This parameter is available only in on-premises Exchange.
 The EnableExternalSenderNotifications parameter enables or disables sending notification messages to external senders for malware detections in their messages. Valid values are:
 
 - $true: When malware is detected in a message from an external sender, send them a notification message.
-- $false: Don't send malware detection notification messages to external message senders. This is the default value.
+- $false: Don't send malware detection notification messages to external message senders. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -465,7 +465,7 @@ This parameter is available only in the cloud-based service.
 
 The EnableFileFilter parameter enables or disables the common attachments filter (also known as common attachment blocking). Valid values are:
 
-- $true: The common attachments filter is enabled. This is the default value.
+- $true: The common attachments filter is enabled. This value is the default.
 - $false: The common attachments filter is disabled.
 
 You specify the file types using the FileTypes parameter. A default list of values is automatically provided, but you can customize it.
@@ -491,7 +491,7 @@ Accept wildcard characters: False
 The EnableInternalSenderAdminNotifications parameter enables or disables sending notification messages to an administrator for malware detections in messages from internal senders. Valid values are:
 
 - $true: When malware attachments are detected in messages from internal senders, a notification messages is sent to the email address that's specified by the InternalSenderAdminAddress parameter.
-- $false: Notifications aren't sent for malware attachment detections in messages from internal senders. This is the default value.
+- $false: Notifications aren't sent for malware attachment detections in messages from internal senders. This value is the default.
 
 **Note**: Admin notifications are sent only for _attachments_ that are classified as malware.
 
@@ -516,7 +516,7 @@ This parameter is available only in on-premises Exchange.
 The EnableInternalSenderNotifications parameter enables or disables sending notification messages to internal senders for malware detections in their messages. Valid values are:
 
 - $true: When malware is detected in a message from an internal sender, send them a notification message.
-- $false: Don't send malware detection notification messages to internal message senders. This is the default value.
+- $false: Don't send malware detection notification messages to internal message senders. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -559,7 +559,7 @@ This parameter is available only in the cloud-based service.
 The FileTypeAction parameter specifies what happens to messages that contain one or more attachments where the file extension is included in the FileTypes parameter (the common attachments filter). Valid values are:
 
 - Quarantine: Quarantine the message. Whether or not the recipient is notified depends on the quarantine notification settings in the quarantine policy that's selected for the malware filter policy by the QuarantineTag parameter.
-- Reject: The message is rejected in a non-delivery report (also known as an NDR or bounce message) to the sender. The message is not available in quarantine. This is the default value.
+- Reject: The message is rejected in a non-delivery report (also known as an NDR or bounce message) to the sender. The message is not available in quarantine. This value is the default.
 
 This parameter is meaningful only when the value of the EnableFileFilter parameter is $true.
 
@@ -701,7 +701,7 @@ This parameter is available only in the cloud-based service.
 
 The ZapEnabled parameter specifies whether to enable zero-hour auto purge (ZAP) for malware in cloud mailboxes. ZAP detects malware in unread messages that have already been delivered to the user's Inbox. Valid values are:
 
-- $true: ZAP for malware is enabled. Unread messages in the user's Inbox that contain malware are moved to the Junk Email folder. This is the default value.
+- $true: ZAP for malware is enabled. Unread messages in the user's Inbox that contain malware are moved to the Junk Email folder. This value is the default.
 - $false: ZAP for malware is disabled.
 
 ```yaml
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MalwareFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/New-MalwareFilterRule.md
index 31f0a6a755..2b3a5a5742 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-MalwareFilterRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-MalwareFilterRule.md
@@ -13,7 +13,7 @@ title: New-MalwareFilterRule
 # New-MalwareFilterRule
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the New-MalwareFilterRule cmdlet to create malware filter rules in your organization.
 
@@ -42,7 +42,7 @@ New-MalwareFilterRule [-Name] <String> -MalwareFilterPolicy <MalwareFilterPolicy
 > [!IMPORTANT]
 > Different types of recipient conditions use AND logic (the recipient must satisfy **all** specified conditions). Different types of recipient exceptions use OR logic (the recipient must satisfy **any** of the specified exceptions). For more information, see [Anti-malware policies](https://learn.microsoft.com/defender-office-365/anti-malware-protection-about#anti-malware-policies).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ManagedContentSettings.md b/exchange/exchange-ps/ExchangePowerShell/New-ManagedContentSettings.md
index 926d185d37..18d380d7d6 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-ManagedContentSettings.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-ManagedContentSettings.md
@@ -46,7 +46,7 @@ Managed content settings are settings that you associate with managed folders to
 
 For more information about managed content settings, see [Messaging Records Management](https://learn.microsoft.com/previous-versions/office/exchange-server-2010/bb123507(v=exchg.141)).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -55,7 +55,7 @@ You need to be assigned permissions before you can run this cmdlet. Although thi
 New-ManagedContentSettings -Name "CS-Exec-DeletedItems" -FolderName "Exec-DeletedItems" -MessageClass * -RetentionEnabled $true -RetentionAction DeleteAndAllowRecovery -AgeLimitForRetention 30.00:00:00 -TriggerForRetention WhenDelivered
 ```
 
-This example creates managed content settings for the managed default folder Exec-DeletedItems. When added to a managed folder mailbox policy and applied to a mailbox, items in the Deleted Items folder will be permanently deleted 30 days from the date of delivery.
+This example creates managed content settings for the managed default folder Exec-DeletedItems. When added to a managed folder mailbox policy and applied to a mailbox, items in the Deleted Items folder are permanently deleted 30 days from the date of delivery.
 
 ### Example 2
 ```powershell
@@ -362,7 +362,7 @@ Valid values include:
 - WhenDelivered
 - WhenMoved
 
-This value corresponds to the 0x4 bit of the msExchELCFlags attribute in Active Directory. The flag is set to $true if the item will expire based on the date it was moved and $false if the item will expire based on the delivery date.
+This value corresponds to the 0x4 bit of the msExchELCFlags attribute in Active Directory. The flag is set to $true if the item expires based on the date it was moved and $false if the item expires based on the delivery date.
 
 If this parameter isn't present and the RetentionEnabled parameter is set to $true, an error is returned.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ManagedFolder.md b/exchange/exchange-ps/ExchangePowerShell/New-ManagedFolder.md
index 83bb4f8e24..826712ca3c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-ManagedFolder.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-ManagedFolder.md
@@ -62,7 +62,7 @@ The New-ManagedFolder cmdlet creates a new managed folder in Active Directory. A
 
 By default, managed custom folders are created with this cmdlet. However, you can also create additional copies of managed default folders using the DefaultFolderType parameter to specify which type of default folder to create (for example, an additional Inbox folder). When you create multiple copies of a managed default folder, you can assign different content settings to each one. For example, you could have two Inbox folders, one named InboxSixMonths and another named InboxOneYear. Then, you could assign a retention time of six months to the first folder and one year to the second folder with the New-ManagedContentSettings cmdlet (or using the New Managed Content Settings wizard in the Exchange Management Console). You must assign a unique name (using the Name parameter) to each of the managed default folders that you create. Users, however, always see the unaltered default folder name. In the example, whether users are assigned an InboxSixMonths folder or an InboxOneYear folder, the Inbox that they see in their mailbox is labeled Inbox. Although the folder names that users see in their mailboxes can be reassigned for managed custom folders (using the Set-ManagedFolder command FolderName parameter), the folder names seen by users for managed default folders can't be changed.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -305,7 +305,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010
 
-The StorageQuota parameter specifies the storage size limit for the mailbox folder. When the folder size exceeds this limit, no additional items may be added. Storage size limits can be specified in kilobytes (KB) or megabytes (MB), for example, 100 KB or 5 MB.
+The StorageQuota parameter specifies the storage size limit for the mailbox folder. When the folder size exceeds this limit, no additional items might be added. Storage size limits can be specified in kilobytes (KB) or megabytes (MB), for example, 100 KB or 5 MB.
 
 ```yaml
 Type: Unlimited
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ManagedFolderMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-ManagedFolderMailboxPolicy.md
index f969abf078..5a615b5bc8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-ManagedFolderMailboxPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-ManagedFolderMailboxPolicy.md
@@ -33,7 +33,7 @@ New-ManagedFolderMailboxPolicy [-Name] <String>
 ## DESCRIPTION
 Managed folder mailbox policies are applied to user mailboxes to control message retention settings.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 Managed custom folders are a premium feature of messaging records management (MRM). Mailboxes with policies that include managed custom folders require an Exchange Server Enterprise client access license (CAL).
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ManagementRole.md b/exchange/exchange-ps/ExchangePowerShell/New-ManagementRole.md
index 8a9bd82382..fa552a0a5e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-ManagementRole.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-ManagementRole.md
@@ -13,7 +13,7 @@ title: New-ManagementRole
 # New-ManagementRole
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the New-ManagementRole cmdlet to create a management role based on an existing role or create an unscoped management role.
 
@@ -56,7 +56,7 @@ After you create a role, you can change the management role entries on the role
 
 For more information about management roles, see [Understanding management roles](https://learn.microsoft.com/exchange/understanding-management-roles-exchange-2013-help).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -81,7 +81,7 @@ For more information about pipelining and the Where cmdlet, see the following to
 New-ManagementRole -Name "In-house scripts" -UnScopedTopLevel
 ```
 
-In on-premises Exchange, this example creates the unscoped management role In-house scripts. Note that the UnScopedTopLevel switch requires the Unscoped Role Management role, which isn't assigned to any role group by default.
+In on-premises Exchange, this example creates the unscoped management role In-house scripts. The UnScopedTopLevel switch requires the Unscoped Role Management role, which isn't assigned to any role group by default.
 
 ## PARAMETERS
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ManagementRoleAssignment.md b/exchange/exchange-ps/ExchangePowerShell/New-ManagementRoleAssignment.md
index 49a991694b..1e4c1d0ef6 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-ManagementRoleAssignment.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-ManagementRoleAssignment.md
@@ -13,7 +13,7 @@ title: New-ManagementRoleAssignment
 # New-ManagementRoleAssignment
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the New-ManagementRoleAssignment cmdlet to assign a management role to a management role group, management role assignment policy, user, or universal security group (USG).
 
@@ -118,7 +118,7 @@ You can create custom management scopes using the New-ManagementScope cmdlet and
 
 For more information about management role assignments, see [Understanding management role assignments](https://learn.microsoft.com/exchange/understanding-management-role-assignments-exchange-2013-help).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -138,7 +138,7 @@ New-ManagementRoleAssignment -Role "MyVoiceMail" -Policy "Sales end-users"
 
 This example assigns the MyVoiceMail role to the "Sales end-users" role assignment policy. First, the IsEndUserRole property on the MyVoiceMail role is verified to be sure it's set to $true, indicating it's an end-user role.
 
-After the role has been verified to be an end-user role, the role is assigned to the "Sales end-users" role assignment policy.
+After the role is verified to be an end-user role, the role is assigned to the "Sales end-users" role assignment policy.
 
 ### Example 3
 ```powershell
@@ -181,7 +181,7 @@ This example assigns the Mail Recipients role to the Contoso Sub - Seattle role
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
 
-The Name parameter specifies a name for the new management role assignment. The maximum length of the name is 64 characters. If the management role assignment name contains spaces, enclose the name in quotation marks ("). If you don't specify a name, one will be created automatically.
+The Name parameter specifies a name for the new management role assignment. The maximum length of the name is 64 characters. If the management role assignment name contains spaces, enclose the name in quotation marks ("). If you don't specify a name, a name is created automatically.
 
 ```yaml
 Type: String
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ManagementScope.md b/exchange/exchange-ps/ExchangePowerShell/New-ManagementScope.md
index 61f701edc8..7689690822 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-ManagementScope.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-ManagementScope.md
@@ -13,7 +13,7 @@ title: New-ManagementScope
 # New-ManagementScope
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the New-ManagementScope cmdlet to create a regular or exclusive management scope.
 
@@ -82,7 +82,7 @@ After you create a regular or exclusive scope, you need to associate the scope w
 
 For more information about regular and exclusive scopes, see [Understanding management role scopes](https://learn.microsoft.com/exchange/understanding-management-role-scopes-exchange-2013-help).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MapiVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/New-MapiVirtualDirectory.md
index 631e4cc9bc..2e66284d4f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-MapiVirtualDirectory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-MapiVirtualDirectory.md
@@ -39,7 +39,7 @@ New-MapiVirtualDirectory
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -104,7 +104,7 @@ The ExtendedProtectionFlags parameter specifies custom settings for Extended Pro
 - AllowDotlessSPN: Required if you want to use Service Principal Name (SPN) values that don't contain FQDNs (for example, HTTP/ContosoMail instead of HTTP/mail.contoso.com). You specify SPNs with the ExtendedProtectionSPNList parameter. This setting makes Extended Protection for Authentication less secure because dotless certificates aren't unique, so it isn't possible to ensure that the client-to-proxy connection was established over a secure channel.
 - NoServiceNameCheck: The SPN list isn't checked to validate a channel binding token. This setting makes Extended Protection for Authentication less secure. We generally don't recommend this setting.
 - Proxy: A proxy server is responsible for terminating the SSL channel. To use this setting, you need to register an SPN by using the ExtendedProtectionSPNList parameter.
-- ProxyCoHosting: HTTP and HTTPS traffic may be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server.
+- ProxyCoHosting: HTTP and HTTPS traffic might be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server.
 
 ```yaml
 Type: MultiValuedProperty
@@ -124,7 +124,7 @@ Accept wildcard characters: False
 
 The ExtendedProtectionSPNList parameter specifies a list of valid Service Principal Names (SPNs) if you're using Extended Protection for Authentication on the virtual directory. Valid values are:
 
-- $null: This is the default value.
+- $null: This value is the default.
 - Single SPN or comma delimited list of valid SPNs: The SPN value format is `Protocol\FQDN`. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter.
 
 ```yaml
@@ -145,8 +145,8 @@ Accept wildcard characters: False
 
 The ExtendedProtectionTokenChecking parameter defines how you want to use Extended Protection for Authentication on the virtual directory. Extended Protection for Authentication isn't enabled by default. Valid values are:
 
-- None: Extended Protection for Authentication isn't be used on the virtual directory. This is the default value.
-- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication will work, but may not be as secure as connections that use Extended Protection for Authentication.
+- None: Extended Protection for Authentication isn't be used on the virtual directory. This value is the default.
+- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication work, but might not be as secure as connections that use Extended Protection for Authentication.
 - Require: Extended Protection for Authentication is used for all connections between clients and the virtual directory. If either the client or server doesn't support it, the connection will fail. If you use this value, you also need to set an SPN value for the ExtendedProtectionSPNList parameter.
 
 **Note**: If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter.
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MessageClassification.md b/exchange/exchange-ps/ExchangePowerShell/New-MessageClassification.md
index 08169fc9b2..bf7fa10717 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-MessageClassification.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-MessageClassification.md
@@ -13,7 +13,7 @@ title: New-MessageClassification
 # New-MessageClassification
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the New-MessageClassification cmdlet to create a message classification instance in your organization.
 
@@ -50,7 +50,7 @@ After you create a new message classification, you can specify the message class
 
 When you create a message classification, it has no locale. By default, the new message classification is used for all locales. After a default message classification is defined, you can add new locales of the classification by running the New-MessageClassification cmdlet and by specifying the default message classification identity that you want to localize.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -196,19 +196,19 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
 
-The DisplayPrecedence parameter specifies the relative precedence of the message classification to other message classifications that may be applied to a specified message. Valid values are:
+The DisplayPrecedence parameter specifies the relative precedence of the message classification to other message classifications that might be applied to a specified message. Valid values are:
 
 - Highest
 - Higher
 - High
 - MediumHigh
-- Medium (This is the default value)
+- Medium (default value)
 - MediumLow
 - Low
 - Lower
 - Lowest
 
-Although Outlook only lets a user specify a single classification for a message, transport rules may apply other classifications to a message. The classification with the highest precedence is shown first and the subsequent classifications, which are those with lesser precedence as defined by this parameter, are appended in the appropriate order thereafter.
+Although Outlook only lets a user specify a single classification for a message, transport rules might apply other classifications to a message. The classification with the highest precedence is shown first and the subsequent classifications, which are those with lesser precedence as defined by this parameter, are appended in the appropriate order thereafter.
 
 ```yaml
 Type: ClassificationDisplayPrecedenceLevel
@@ -250,7 +250,7 @@ Accept wildcard characters: False
 
 The PermissionMenuVisible parameter specifies whether the values that you entered for the DisplayName and RecipientDescription parameters are displayed in Outlook as the user composes a message. Valid values are:
 
-- $true: Users can assign the message classification to messages before they're sent, and the classification information is displayed. This is the default value.
+- $true: Users can assign the message classification to messages before they're sent, and the classification information is displayed. This value is the default.
 - $false: Users can't assign the message classification to messages before they're sent, However, messages received with this message classification still display the classification information.
 
 ```yaml
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MigrationBatch.md b/exchange/exchange-ps/ExchangePowerShell/New-MigrationBatch.md
index ef66847557..e928c46162 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-MigrationBatch.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-MigrationBatch.md
@@ -13,7 +13,7 @@ title: New-MigrationBatch
 # New-MigrationBatch
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the New-MigrationBatch cmdlet to submit a new migration request for a batch of users.
 
@@ -454,12 +454,12 @@ Onboarding and offboarding in Exchange Online
 
   Both onboarding and offboarding remote move migrations are initiated from your Exchange Online organization.
 
-- Cutover Exchange migration: This is another type of onboarding migration and is used to migrate all mailboxes in an on-premises Exchange organization to Exchange Online. You can migrate a maximum of 1,000 Exchange Server 2003, Exchange Server 2007, or Exchange Server 2010 mailboxes using a cutover migration. Mailboxes will be automatically provisioned in Exchange Online when you perform a cutover Exchange migration. For more information, see Example 5.
+- Cutover Exchange migration: This is another type of onboarding migration and is used to migrate all mailboxes in an on-premises Exchange organization to Exchange Online. You can migrate a maximum of 1,000 Exchange Server 2003, Exchange Server 2007, or Exchange Server 2010 mailboxes using a cutover migration. Mailboxes are automatically provisioned in Exchange Online when you perform a cutover Exchange migration. For more information, see Example 5.
 - Staged Exchange migration: You can also migrate a subset of mailboxes from an on-premises Exchange organization to Exchange Online. This is another type of onboarding migration. Migrating mailboxes from Exchange 2010 or later versions of Exchange isn't supported using a staged migration. Prior to running a staged migration, you have to use directory synchronization or some other method to provision mail users in your Exchange Online organization. For more information, see Example 6.
 - IMAP migration: This onboarding migration type migrates mailbox data from an IMAP server (including Exchange) to Exchange Online. For an IMAP migration, you must first provision mailboxes in Exchange Online before you can migrate mailbox data. For more information, see Example 7.
 - Google Workspace (formerly G Suite) migration: This onboarding migration type migrates mailbox data from a Google Workspace organization to Exchange Online. For a Google Workspace migration, you must first provision mail users (or mailboxes) in Exchange Online before you can migrate mailbox data. For more information, see Example 10.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -470,7 +470,7 @@ New-MigrationBatch -Local -Name LocalMove1 -CSVData ([System.IO.File]::ReadAllBy
 Start-MigrationBatch -Identity LocalMove1
 ```
 
-This example creates a migration batch for a local move, where the mailboxes in the specified CSV file are moved to a different mailbox database. This CSV file contains a single column with the email address for the mailboxes that will be moved. The header for this column must be named EmailAddress. The migration batch in this example must be started manually by using the Start-MigrationBatch cmdlet or the Exchange admin center. Alternatively, you can use the AutoStart parameter to start the migration batch automatically.
+This example creates a migration batch for a local move, where the mailboxes in the specified CSV file are moved to a different mailbox database. This CSV file contains a single column with the email address for the mailboxes to be moved. The header for this column must be named EmailAddress. The migration batch in this example must be started manually by using the Start-MigrationBatch cmdlet or the Exchange admin center. Alternatively, you can use the AutoStart parameter to start the migration batch automatically.
 
 ### Example 2
 ```powershell
@@ -483,7 +483,7 @@ $CrossForestBatch = New-MigrationBatch -Name CrossForestBatch1 -SourceEndpoint $
 Start-MigrationBatch -Identity $CrossForestBatch.Identity
 ```
 
-This example creates a migration batch for a cross-forest enterprise move, where the mailboxes for the mail users specified in the CSV file are moved to a different forest. A new migration endpoint is created, which identifies the domain where the mailboxes are currently located. The endpoint is used to create the migration batch. Then the migration batch is started with the Start-MigrationBatch cmdlet. Note that cross-forest moves are initiated from the target forest, which is the forest that you want to move the mailboxes to.
+This example creates a migration batch for a cross-forest enterprise move, where the mailboxes for the mail users specified in the CSV file are moved to a different forest. A new migration endpoint is created, which identifies the domain where the mailboxes are currently located. The endpoint is used to create the migration batch. Then the migration batch is started with the Start-MigrationBatch cmdlet. Cross-forest moves are initiated from the target forest, which is the forest that you want to move the mailboxes to.
 
 ### Example 3
 ```powershell
@@ -496,7 +496,7 @@ $OnboardingBatch = New-MigrationBatch -Name RemoteOnBoarding1 -SourceEndpoint $M
 Start-MigrationBatch -Identity $OnboardingBatch.Identity.Name
 ```
 
-This example creates a migration batch for an onboarding remote move migration from an on-premises Exchange organization to Exchange Online. The syntax is similar to that of a cross-forest move, but it's initiated from the Exchange Online organization. A new migration endpoint is created, which points to the on-premises organization as the source location of the mailboxes that will be migrated. This endpoint is used to create the migration batch. Then the migration batch is started with the Start-MigrationBatch cmdlet.
+This example creates a migration batch for an onboarding remote move migration from an on-premises Exchange organization to Exchange Online. The syntax is similar to that of a cross-forest move, but it's initiated from the Exchange Online organization. A new migration endpoint is created, which points to the on-premises organization as the source location of the mailboxes to be migrated. This endpoint is used to create the migration batch. Then the migration batch is started with the Start-MigrationBatch cmdlet.
 
 ### Example 4
 ```powershell
@@ -555,7 +555,7 @@ $OnboardingBatch = New-MigrationBatch -Name RemoteOnBoarding1 -SourceEndpoint $M
 Start-MigrationBatch -Identity $OnboardingBatch.Identity
 ```
 
-This example is the same as Example 3, but the CompleteAfter parameter is also used. Data migration for the batch will start, but won't complete until 09/01/2018 7:00 PM (UTC). This method allows you to start a migration and then leave it to complete after business hours if your time zone is Coordinated Universal Time.
+This example is the same as Example 3, but the CompleteAfter parameter is also used. Data migration for the batch starts but doesn't complete until 09/01/2018 7:00 PM (UTC). This method allows you to start a migration and then leave it to complete after business hours if your time zone is Coordinated Universal Time.
 
 ### Example 9
 ```powershell
@@ -568,7 +568,7 @@ $OnboardingBatch = New-MigrationBatch -Name RemoteOnBoarding1 -SourceEndpoint $M
 Start-MigrationBatch -Identity $OnboardingBatch.Identity
 ```
 
-This example is the same as Example 8, but the TimeZone parameter is also used. Data migration for the batch will start, but won't complete until 09/01/2018 7:00 PM (PST). This method allows you to start a migration and then leave it to complete after business hours if your time zone is Pacific Standard Time.
+This example is the same as Example 8, but the TimeZone parameter is also used. Data migration for the batch starts but doesn't complete until 09/01/2018 7:00 PM (PST). This method allows you to start a migration and then leave it to complete after business hours if your time zone is Pacific Standard Time.
 
 ### Example 10
 ```powershell
@@ -699,7 +699,7 @@ The CSVData parameter specifies the CSV file that contains information about the
 
 A valid value for this parameter requires you to read the file to a byte-encoded object using the following syntax: `([System.IO.File]::ReadAllBytes('<Path>\<FileName>'))`. You can use this command as the parameter value, or you can write the output to a variable (`$data = [System.IO.File]::ReadAllBytes('<Path>\<FileName>')`) and use the variable as the parameter value (`$data`).
 
-**Note**: This parameter doesn't validate the availability of the mailboxes based on RBAC scope. All mailboxes that are specified in the CSV file will be migrated, even if they are outside of the RBAC scope (for example, an OU) that gives the admin permissions to migrate mailboxes.
+**Note**: This parameter doesn't validate the availability of the mailboxes based on RBAC scope. All mailboxes specified in the CSV file will be migrated, even if they are outside of the RBAC scope (for example, an OU) that gives the admin permissions to migrate mailboxes.
 
 ```yaml
 Type: Byte[]
@@ -785,8 +785,8 @@ This parameter is available only in on-premises Exchange.
 
 The AllowIncrementalSyncs parameter specifies whether to enable or disable incremental synchronization. Valid values are:
 
-- $true: Incremental synchronization is enabled. Any new messages that are sent to the source mailbox are copied to the corresponding target mailbox once every 24 hours. This is the default value.
-- $false: Incremental synchronization is disabled. The migration batch will go into the Stopped state after the initial synchronization is complete. To complete a migration batch for local moves, cross-forest moves, or remote move migrations, you need to enable incremental synchronization by using the Set-MigrationBatch cmdlet.
+- $true: Incremental synchronization is enabled. Any new messages that are sent to the source mailbox are copied to the corresponding target mailbox once every 24 hours. This value is the default.
+- $false: Incremental synchronization is disabled. The migration batch goes into the Stopped state after the initial synchronization is complete. To complete a migration batch for local moves, cross-forest moves, or remote move migrations, you need to enable incremental synchronization by using the Set-MigrationBatch cmdlet.
 
 ```yaml
 Type: Boolean
@@ -807,7 +807,7 @@ Accept wildcard characters: False
 The AllowUnknownColumnsInCsv parameter specifies whether to allow extra columns in the CSV file that aren't used by migration. Valid values are:
 
 - $true: The migration ignores (silently skips) unknown columns in the CSV file (including optional columns with misspelled column headers). All unknown columns are treated like extra columns that aren't used by migration.
-- $false: The migration fails if there are any unknown columns in the CSV file.This setting protects against spelling errors in column headers. This is the default value.
+- $false: The migration fails if there are any unknown columns in the CSV file.This setting protects against spelling errors in column headers. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -973,7 +973,7 @@ The BadItemLimit parameter specifies the maximum number of bad items that are al
 
 Valid input for this parameter is an integer or the value unlimited. The default value is 0, which means the migration request will fail if any bad items are detected. If you are OK with leaving a few bad items behind, you can set this parameter to a reasonable value (we recommend 10 or lower) so the migration request can proceed. If too many bad items are detected, consider using the New-MailboxRepairRequest cmdlet to attempt to fix corrupted items in the source mailbox, and try the migration request again.
 
-**Note**: This parameter is being deprecated in the cloud-based service. In the future, if neither the BadItemLimit or LargeItemLimit parameters are specified, the migration will use Skipped Item approval semantics instead of BadItemLimit semantics.
+**Note**: This parameter is being deprecated in the cloud-based service. In the future, if neither the BadItemLimit or LargeItemLimit parameters are specified, the migration uses Skipped Item approval semantics instead of BadItemLimit semantics.
 
 ```yaml
 Type: Unlimited
@@ -993,14 +993,14 @@ Accept wildcard characters: False
 
 This parameter is functional only in the cloud-based service.
 
-The CompleteAfter parameter specifies a delay before the batch is completed. Data migration for the batch will start, but completion won't start until the date/time you specify with this parameter.
+The CompleteAfter parameter specifies a delay before the batch is completed. Data migration for the batch starts, but completion doesn't start until the date/time you specify with this parameter.
 
 Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
 
 In Exchange Online PowerShell, if you specify a date/time value without a time zone, the value is in Coordinated Universal Time (UTC). To specify a value, use either of the following options:
 
 - Specify the date/time value in UTC: For example, `"7/30/2020 9:00PM Z"`.
-- Specify the date/time value in your local time zone: For example, `"7/30/2020 9:00PM -700"`. The value will be converted to UTC if you don't use the TimeZone parameter.
+- Specify the date/time value in your local time zone: For example, `"7/30/2020 9:00PM -700"`. The value is converted to UTC if you don't use the TimeZone parameter.
 
 ```yaml
 Type: DateTime
@@ -1041,7 +1041,7 @@ Accept wildcard characters: False
 
 This parameter is available only in the cloud-based service for IMAP migration and Google Workspace migration.
 
-The ContentFilter parameter uses OPATH filter syntax to filter the messages by Received time. Only content that match the ContentFilter parameter will be moved to Exchange online. For example:
+The ContentFilter parameter uses OPATH filter syntax to filter the messages by Received time. Only content that matches the ContentFilter parameter is moved to Exchange online. For example:
 
 - `"Received -gt '8/23/2020'"`
 - `"Received -le '2019/01/01'"`
@@ -1350,7 +1350,7 @@ For more information about maximum message size values, see the following topics
 
 Valid input for this parameter is an integer or the value unlimited. The default value is 0, which means the migration request will fail if any large items are detected. If you are OK with leaving a few large items behind, you can set this parameter to a reasonable value (we recommend 10 or lower) so the migration request can proceed.
 
-**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics will be used instead.
+**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics are used instead.
 
 ```yaml
 Type: Unlimited
@@ -1732,7 +1732,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
 
-This parameter has been replaced by the MoveOptions parameter.
+This parameter is replaced by the MoveOptions parameter.
 
 The SkipMoving parameter specifies the stages of the migration that you want to skip for debugging purposes. Don't use this parameter unless you're directed to do so by Microsoft Customer Service and Support or specific documentation.
 
@@ -1814,7 +1814,7 @@ This parameter is available only in on-premises Exchange.
 
 The SkipSteps parameter specifies the steps in the staged Exchange migration that you want to skip. Valid values are:
 
-- None (This is the default value)
+- None (default value)
 - SettingTargetAddress: Don't set the target email address on the source mailbox. This setting prevents mail from being forwarded from the original mailbox to the new migrated mailbox.
 
 This parameter is only enforced for staged Exchange migrations.
@@ -1878,14 +1878,14 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
 
-The StartAfter parameter specifies a delay before the data migration for the users within the batch is started. The migration will be prepared, but the actual data migration for the user won't start until the date/time you specify with this parameter.
+The StartAfter parameter specifies a delay before the data migration for the users within the batch is started. The migration is prepared, but the actual data migration for the user doesn't start until the date/time you specify with this parameter.
 
 Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
 
 In Exchange Online PowerShell, if you specify a date/time value without a time zone, the value is in Coordinated Universal Time (UTC). To specify a value, use either of the following options:
 
 - Specify the date/time value in UTC: For example, `"7/30/2020 9:00PM Z"`.
-- Specify the date/time value in your local time zone. For example, `"7/30/2020 9:00PM -700"`. The value will be converted to UTC if you don't use the TimeZone parameter.
+- Specify the date/time value in your local time zone. For example, `"7/30/2020 9:00PM -700"`. The value is converted to UTC if you don't use the TimeZone parameter.
 
 ```yaml
 Type: DateTime
@@ -1903,7 +1903,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
 
-The TargetArchiveDatabases parameter specifies the database where the archive mailboxes specified in the migration batch will be migrated to. You can use any value that uniquely identifies the database. For example:
+The TargetArchiveDatabases parameter specifies the database where the archive mailboxes specified in the migration batch are migrated to. You can use any value that uniquely identifies the database. For example:
 
 - Name
 - Distinguished name (DN)
@@ -2052,7 +2052,7 @@ Accept wildcard characters: False
 
 The WorkflowControlFlags parameter specifies advanced controls for the steps that are performed in the migration. Valid values are:
 
-- None (This is the default value)
+- None (default value)
 - InjectAndForget
 - SkipSwitchover
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MigrationEndpoint.md b/exchange/exchange-ps/ExchangePowerShell/New-MigrationEndpoint.md
index b70b95edb7..137f345d59 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-MigrationEndpoint.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-MigrationEndpoint.md
@@ -13,7 +13,7 @@ title: New-MigrationEndpoint
 # New-MigrationEndpoint
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the New-MigrationEndpoint cmdlet to configure the connection settings for cross-forests moves, remote move migrations, cutover or staged Exchange migrations, IMAP migrations, and Google Workspace (formerly G Suite) migrations.
 
@@ -245,7 +245,7 @@ The New-MigrationEndpoint cmdlet configures the connection settings for differen
 
 Moving mailboxes between different servers or databases within a single on-premises Exchange forest (called a local move) doesn't require a migration endpoint.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -270,23 +270,23 @@ $Credentials = Get-Credential
 New-MigrationEndpoint -ExchangeOutlookAnywhere -Name EXCH-AutoDiscover -Autodiscover -EmailAddress administrator@contoso.com -Credentials $Credentials
 ```
 
-This example creates an Outlook Anywhere migration endpoint by using the Autodiscover parameter to detect the connection settings to the on-premises organization. Outlook Anywhere endpoints are used for cutover and staged Exchange migrations. The Get-Credential cmdlet is used to obtain the credentials for an on-premises account that has the necessary administrative privileges in the domain and that can access the mailboxes that will be migrated. When prompted for the user name, you can use either the email address or the domain\\username format for the administrator account. This account can be the same one that is specified by the EmailAddress parameter.
+This example creates an Outlook Anywhere migration endpoint by using the Autodiscover parameter to detect the connection settings to the on-premises organization. Outlook Anywhere endpoints are used for cutover and staged Exchange migrations. The Get-Credential cmdlet is used to obtain the credentials for an on-premises account that has the necessary administrative privileges in the domain and that can access the migrated mailboxes. When prompted for the user name, you can use either the email address or the domain\\username format for the administrator account. This account can be the same one that is specified by the EmailAddress parameter.
 
 ### Example 4
 ```powershell
 New-MigrationEndpoint -ExchangeOutlookAnywhere -Name EXCH_Manual -ExchangeServer EXCH-01-MBX.contoso.com -RPCProxyServer EXCH-02-CAS.contoso.com -Credentials (Get-Credential administrator@contoso.com) -EmailAddress annb@contoso.com
 ```
 
-This example creates an Outlook Anywhere migration endpoint by specifying the connection settings manually. Outlook Anywhere endpoints are used for cutover and staged Exchange migrations. The value for the ExchangeServer parameter specifies the on-premises Exchange server that hosts the mailboxes that will be migrated. The value for the RPCProxyServer parameter specifies the Exchange server in the on-premises organization that has the Client Access server role installed that directly accepts and proxies client connections. The EmailAddress parameter can specify any mailbox in the on-premises domain.
+This example creates an Outlook Anywhere migration endpoint by specifying the connection settings manually. Outlook Anywhere endpoints are used for cutover and staged Exchange migrations. The value for the ExchangeServer parameter specifies the on-premises Exchange server that hosts the migrated mailboxes. The value for the RPCProxyServer parameter specifies the Exchange server in the on-premises organization that has the Client Access server role installed that directly accepts and proxies client connections. The EmailAddress parameter can specify any mailbox in the on-premises domain.
 
-It's recommended that you use a migration endpoint created with connection settings that are automatically discovered (see Example 3) because the Autodiscover service will be used to connect to each user mailbox in the migration batch. If you manually specify the connection settings for the endpoint and a user mailbox isn't located on the server specified by the ExchangeServer parameter, the migration for that user will fail. This is important if you have multiple on-premises Outlook Anywhere servers. Otherwise, you may need to create different migration endpoints that correspond to each on-premises server.
+We recommend that you use a migration endpoint created with connection settings that are automatically discovered (see Example 3) because the Autodiscover service is used to connect to each user mailbox in the migration batch. If you manually specify the connection settings for the endpoint and a user mailbox isn't located on the server specified by the ExchangeServer parameter, the migration for that user will fail. This is important if you have multiple on-premises Outlook Anywhere servers. Otherwise, you might need to create different migration endpoints that correspond to each on-premises server.
 
 ### Example 5
 ```powershell
 New-MigrationEndpoint -IMAP -Name IMAPEndpoint -RemoteServer imap.contoso.com -Port 993 -Security Ssl
 ```
 
-This example creates an IMAP migration endpoint. The value for the RemoteServer parameter specifies the FQDN of the IMAP server that hosts the mailboxes that will be migrated. The endpoint is configured to use port 993 for SSL encryption.
+This example creates an IMAP migration endpoint. The value for the RemoteServer parameter specifies the FQDN of the IMAP server that hosts the migrated mailboxes. The endpoint is configured to use port 993 for SSL encryption.
 
 ### Example 6
 ```powershell
@@ -592,7 +592,7 @@ Accept wildcard characters: False
 
 This parameter is available only in the cloud-based service.
 
-The RpcProxyServer parameter specifies the FQDN of the Exchange server in the on-premises Exchange organization that has the Client Access server role installed that directly accepts and proxies client connections. This parameter is used when you create an Outlook Anywhere migration endpoint for cutover and staged Exchange migrations. Typically, this FQDN will be the same as your Outlook on the web URL; for example, mail.contoso.com. This is also the URL for the proxy server that Outlook uses to connect to an Exchange server.
+The RpcProxyServer parameter specifies the FQDN of the Exchange server in the on-premises Exchange organization that has the Client Access server role installed that directly accepts and proxies client connections. This parameter is used when you create an Outlook Anywhere migration endpoint for cutover and staged Exchange migrations. Typically, this FQDN wis the same as your Outlook on the web URL. For example, mail.contoso.com. This is also the URL for the proxy server that Outlook uses to connect to an Exchange server.
 
 This parameter is required only when you don't use the Autodiscover parameter.
 
@@ -614,7 +614,7 @@ Accept wildcard characters: False
 
 This parameter is available only in the cloud-based service.
 
-The ServiceAccountKeyFileData parameter is used to specify information needed to authenticate as a service account. The data should come from the JSON key file that is downloaded when the service account that has been granted access to your remote tenant is created.
+The ServiceAccountKeyFileData parameter is used to specify information needed to authenticate as a service account. The data should come from the JSON key file that is downloaded when the service account that is granted access to your remote tenant is created.
 
 A valid value for this parameter requires you to read the file to a byte-encoded object using the following syntax: `([System.IO.File]::ReadAllBytes('<Path>\<FileName>'))`. You can use this command as the parameter value, or you can write the output to a variable (`$data = [System.IO.File]::ReadAllBytes('<Path>\<FileName>')`) and use the variable as the parameter value (`$data`).
 
@@ -777,7 +777,7 @@ Accept wildcard characters: False
 
 This parameter is available only in the cloud-based service.
 
-The ExchangeServer parameter specifies the FQDN of the on-premises Exchange server that hosts the mailboxes that will be migrated. This parameter is used when you create an Outlook Anywhere migration endpoint for cutover and staged Exchange migrations.
+The ExchangeServer parameter specifies the FQDN of the on-premises Exchange server that hosts the migrated mailboxes. This parameter is used when you create an Outlook Anywhere migration endpoint for cutover and staged Exchange migrations.
 
 This parameter is required only when you don't use the Autodiscover parameter.
 
@@ -804,7 +804,7 @@ The MailboxPermission parameter specifies what permissions to use to access the
 The migration administrator account specified for the endpoint must have one of the following permissions:
 
 - Admin: The account is a domain administrator who can access any mailbox they want to migrate.
-- FullAccess: The account is assigned either the Full Access permission to the mailboxes they want to migrate or the Receive As permission to the mailbox database that hosts the mailboxes that will be migrated.
+- FullAccess: The account is assigned either the Full Access permission to the mailboxes they want to migrate or the Receive As permission to the mailbox database that hosts the migrated mailboxes.
 
 If this parameter isn't specified, the cmdlet tries to access source mailboxes using the domain administrator permission and if that fails, it then tries to access the source mailboxes using the Full Access or Receive As permissions.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MobileDeviceMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-MobileDeviceMailboxPolicy.md
index 38821c4cb2..8d609417e7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-MobileDeviceMailboxPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-MobileDeviceMailboxPolicy.md
@@ -13,7 +13,7 @@ title: New-MobileDeviceMailboxPolicy
 # New-MobileDeviceMailboxPolicy
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the New-MobileDeviceMailboxPolicy cmdlet to create mobile device mailbox policies.
 
@@ -90,7 +90,7 @@ Some mobile device mailbox policy settings require the mobile device to have cer
 
 Some settings in this cmdlet are supported by Outlook for iOS and Android. For more information, see [Leveraging Exchange Online mobile device policies](https://learn.microsoft.com/exchange/clients-and-mobile-in-exchange-online/outlook-for-ios-and-android/secure-outlook-for-ios-and-android#leveraging-exchange-online-mobile-device-policies).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -900,7 +900,7 @@ Accept wildcard characters: False
 The MaxInactivityTimeLock parameter specifies the length of time that the mobile device can be inactive before the password is required to reactivate it. Valid values are:
 
 - A timespan: hh:mm:ss, where hh = hours, mm = minutes and ss= seconds. The valid input range is 00:01:00 to 01:00:00 (one minute to one hour).
-- The value Unlimited. This is the default value.
+- The value Unlimited. This value is the default.
 
 ```yaml
 Type: Unlimited
@@ -1017,7 +1017,7 @@ Accept wildcard characters: False
 The PasswordExpiration parameter specifies how long a password can be used on a mobile device before the user is forced to change the password. Valid values are:
 
 - A timespan: ddd.hh:mm:ss, where ddd = days, hh = hours, mm = minutes and ss= seconds. The valid input range is 1.00:00:00 to 730.00:00:00 (one day to two years).
-- The value Unlimited. This is the default value
+- The value Unlimited. This value is the default
 
 ```yaml
 Type: Unlimited
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MoveRequest.md b/exchange/exchange-ps/ExchangePowerShell/New-MoveRequest.md
index 315eb64fbe..f6067d134f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-MoveRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-MoveRequest.md
@@ -13,7 +13,7 @@ title: New-MoveRequest
 # New-MoveRequest
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the New-MoveRequest cmdlet to begin the process of an asynchronous mailbox or personal archive move. You can also check mailbox readiness to be moved by using the WhatIf parameter.
 
@@ -256,7 +256,7 @@ New-MoveRequest [-Identity] <MailboxOrMailUserIdParameter> -TargetDeliveryDomain
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -561,7 +561,7 @@ Valid input for this parameter is an integer or the value unlimited. The default
 
 In Exchange 2010, if you set this value to 51 or higher, you also need to use the AcceptLargeDataLoss switch. Otherwise, the command will fail.
 
-**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics will be used instead.
+**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics are used instead.
 
 ```yaml
 Type: Unlimited
@@ -624,7 +624,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
 
-The CompletedRequestAgeLimit parameter specifies how long the request will be kept after it has completed before being automatically removed. The default CompletedRequestAgeLimit parameter value is 30 days.
+The CompletedRequestAgeLimit parameter specifies how long the request are kept after it has completed before being automatically removed. The default CompletedRequestAgeLimit parameter value is 30 days.
 
 ```yaml
 Type: Unlimited
@@ -707,7 +707,7 @@ Accept wildcard characters: False
 
 The ForceOffline switch forces the mailbox move to be performed in offline mode. You don't need to specify a value with this switch.
 
-Moving a mailbox in offline mode means the user will have no access to email during the mailbox move.
+Moving a mailbox in offline mode means the user has no access to email during the mailbox move.
 
 ```yaml
 Type: SwitchParameter
@@ -789,7 +789,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
 
-The IncrementalSyncInterval parameter specifies the wait time between incremental syncs. This parameter is used together with the CompleteAfter parameter to create a move request that will do periodic incremental syncs after the initial sync is complete.
+The IncrementalSyncInterval parameter specifies the wait time between incremental syncs. Use this parameter with the CompleteAfter parameter to create a move request that does periodic incremental syncs after the initial sync is complete.
 
 To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds.
 
@@ -842,7 +842,7 @@ Valid input for this parameter is an integer or the value unlimited. The default
 
 If you set this value to 51 or higher, you also need to use the AcceptLargeDataLoss switch. Otherwise, the command will fail.
 
-**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics will be used instead.
+**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics are used instead.
 
 ```yaml
 Type: Unlimited
@@ -949,7 +949,7 @@ The Priority parameter specifies the order in which the request should be proces
 - Lowest
 - Lower
 - Low
-- Normal: This is the default value.
+- Normal: This value is the default.
 - High
 - Higher
 - Highest
@@ -1105,7 +1105,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
 
-This parameter has been replaced by the MoveOptions parameter.
+This parameter is replaced by the MoveOptions parameter.
 
 The SkipMoving parameter specifies the stages of the move that you want to skip for debugging purposes. Don't use this parameter unless you're directed to do so by Microsoft Customer Service and Support or specific documentation.
 
@@ -1174,7 +1174,7 @@ Accept wildcard characters: False
 
 The Suspend switch specifies whether to suspend the request. You don't need to specify a value with this switch.
 
-If you use this switch, the request is queued, but the request won't reach the status of InProgress until you resume the request with the relevant resume cmdlet.
+If you use this switch, the request is queued, but the request doesn't reach the status of InProgress until you resume the request with the relevant resume cmdlet.
 
 ```yaml
 Type: SwitchParameter
@@ -1238,7 +1238,7 @@ The TargetDatabase parameter specifies the destination mailbox database for the
 - Distinguished name (DN)
 - GUID
 
-If you don't use this parameter, the automatic distribution logic will select a random database in the Active Directory site where you are running the command.
+If you don't use this parameter, the automatic distribution logic selects a random database in the Active Directory site where you are running the command.
 
 ```yaml
 Type: DatabaseIdParameter
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-OMEConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/New-OMEConfiguration.md
index 42c85225eb..1453b4cf91 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-OMEConfiguration.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-OMEConfiguration.md
@@ -40,7 +40,7 @@ New-OMEConfiguration [-Identity] <OrganizationIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -79,7 +79,7 @@ The BackgroundColor parameter specifies the background color. Valid values are:
 
 - An available HTML hexadecimal (hex triplet) color code value (for example, `0x000000` is white).
 - An available text value (for example, `yellow` is 0x00FFFF00).
-- $null (blank). This is the default value.
+- $null (blank). This value is the default.
 
 For more information, see [Add your organization's brand to your encrypted messages](https://learn.microsoft.com/purview/add-your-organization-brand-to-encrypted-messages).
 
@@ -155,7 +155,7 @@ Accept wildcard characters: False
 
 This parameter is available only with a Microsoft 365 Advanced Message Encryption subscription.
 
-The ExternalMailExpiryInDays parameter specifies the number of days that the encrypted message is available to external recipients in the Microsoft 365 portal. A valid value is an integer from 0 to 730. The value 0 means the messages will never expire. The default value is 0.
+The ExternalMailExpiryInDays parameter specifies the number of days that the encrypted message is available to external recipients in the Microsoft 365 portal. A valid value is an integer from 0 to 730. The value 0 means the messages never expire. The default value is 0.
 
 In the output of the Get-OMEConfiguration cmdlet, the value of this parameter is displayed in the ExternalMailExpiryInterval property.
 
@@ -175,7 +175,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online
 
-The Image parameter identifies and uploads an image that will be displayed in the email message and in the Microsoft 365 admin center.
+The Image parameter identifies and uploads an image that's displayed in the email message and in the Microsoft 365 admin center.
 
 A valid value for this parameter requires you to read the file to a byte-encoded object using the following syntax: `([System.IO.File]::ReadAllBytes('<Path>\<FileName>'))`. You can use this command as the parameter value, or you can write the output to a variable (`$data = [System.IO.File]::ReadAllBytes('<Path>\<FileName>')`) and use the variable as the parameter value (`$data`).
 
@@ -219,7 +219,7 @@ Accept wildcard characters: False
 
 The OTPEnabled parameter specifies whether to allow recipients to use a one-time passcode to view encrypted messages. Valid values are:
 
-- $true: Recipients can use a one-time passcode to view encrypted messages. This is the default value.
+- $true: Recipients can use a one-time passcode to view encrypted messages. This value is the default.
 - $false: Recipients can't use a one-time passcode to view encrypted messages. The recipient is required to sign in using a Microsoft 365 work or school account.
 
 ```yaml
@@ -294,7 +294,7 @@ Accept wildcard characters: False
 
 The SocialIdSignIn parameter specifies whether a user is allowed to view an encrypted message in the Microsoft 365 admin center using their own social network id (Google, Yahoo, etc). Valid values are:
 
-- $true: Social network ID sign in is allowed. This is the default value.
+- $true: Social network ID sign in is allowed. This value is the default.
 - $false: Social network ID sign in is not allowed. Whether the recipient can use a one-time passcode or their Microsoft 365 work or school account is controlled by the OTPEnabled parameter.
 
 ```yaml
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-OabVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/New-OabVirtualDirectory.md
index 6b565f5cfd..e521394787 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-OabVirtualDirectory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-OabVirtualDirectory.md
@@ -45,7 +45,7 @@ The New-OABVirtualDirectory cmdlet configures a web distribution point for an OA
 
 You have to manually create the file system folder on the server that hosts the OAB files.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -107,7 +107,7 @@ The ExtendedProtectionFlags parameter specifies custom settings for Extended Pro
 - AllowDotlessSPN: Required if you want to use Service Principal Name (SPN) values that don't contain FQDNs (for example, HTTP/ContosoMail instead of HTTP/mail.contoso.com). You specify SPNs with the ExtendedProtectionSPNList parameter. This setting makes Extended Protection for Authentication less secure because dotless certificates aren't unique, so it isn't possible to ensure that the client-to-proxy connection was established over a secure channel.
 - NoServiceNameCheck: The SPN list isn't checked to validate a channel binding token. This setting makes Extended Protection for Authentication less secure. We generally don't recommend this setting.
 - Proxy: A proxy server is responsible for terminating the SSL channel. To use this setting, you need to register an SPN by using the ExtendedProtectionSPNList parameter.
-- ProxyCoHosting: HTTP and HTTPS traffic may be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server.
+- ProxyCoHosting: HTTP and HTTPS traffic might be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server.
 
 ```yaml
 Type: MultiValuedProperty
@@ -127,7 +127,7 @@ Accept wildcard characters: False
 
 The ExtendedProtectionSPNList parameter specifies a list of valid Service Principal Names (SPNs) if you're using Extended Protection for Authentication on the virtual directory. Valid values are:
 
-- $null: This is the default value.
+- $null: This value is the default.
 - Single SPN or comma delimited list of valid SPNs: The SPN value format is `Protocol\FQDN`. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter.
 
 ```yaml
@@ -148,9 +148,9 @@ Accept wildcard characters: False
 
 The ExtendedProtectionTokenChecking parameter defines how you want to use Extended Protection for Authentication on the virtual directory. Extended Protection for Authentication isn't enabled by default. Valid values are:
 
-- None: Extended Protection for Authentication isn't be used on the virtual directory. This is the default value.
-- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication will work, but may not be as secure as connections that use Extended Protection for Authentication.
-- Require: Extended Protection for Authentication is used for all connections between clients and the virtual directory. If either the client or server doesn't support it, the connection will fail. If you use this value, you also need to set an SPN value for the ExtendedProtectionSPNList parameter.
+- None: Extended Protection for Authentication isn't be used on the virtual directory. This value is the default.
+- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication work, but might not be as secure as connections that use Extended Protection for Authentication.
+- Require: Extended Protection for Authentication is used for all connections between clients and the virtual directory. If either the client or server doesn't support it, the connection fails. If you use this value, you also need to set an SPN value for the ExtendedProtectionSPNList parameter.
 
 **Note**: If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter.
 
@@ -262,7 +262,7 @@ Accept wildcard characters: False
 
 The RequireSSL parameter specifies whether the client connection to the virtual directory requires Secure Sockets Layer (SSL) encryption. Valid values are:
 
-- $true: SSL encryption is required to connect to the virtual directory. This is the default value.
+- $true: SSL encryption is required to connect to the virtual directory. This value is the default.
 - $false: SSL encryption isn't required to connect to the virtual directory.
 
 ```yaml
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-OfflineAddressBook.md b/exchange/exchange-ps/ExchangePowerShell/New-OfflineAddressBook.md
index d0e3db120c..02ba871661 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-OfflineAddressBook.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-OfflineAddressBook.md
@@ -13,7 +13,7 @@ title: New-OfflineAddressBook
 # New-OfflineAddressBook
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the New-OfflineAddressBook cmdlet to create offline address books (OABs).
 
@@ -44,7 +44,7 @@ New-OfflineAddressBook [-Name] <String> -AddressLists <AddressBookBaseIdParamete
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -85,7 +85,7 @@ New-OfflineAddressBook -Name "Legacy OAB" -AddressLists "\Default Global Address
 
 In Exchange Server 2010, this example creates the OAB Legacy OAB that uses public folder distribution for Outlook 2003 Service Pack 1 (SP1) and Outlook 98 Service Pack 2 (SP2) clients on SERVER01.
 
-If you configure OABs to use public folder distribution, but your organization doesn't have any public folder infrastructure, an error will be returned. For more information, see [Managing Public Folders](https://learn.microsoft.com/previous-versions/office/exchange-server-2010/bb124411(v=exchg.141)).
+If you configure OABs to use public folder distribution, but your organization doesn't have any public folder infrastructure, an error is returned. For more information, see [Managing Public Folders](https://learn.microsoft.com/previous-versions/office/exchange-server-2010/bb124411(v=exchg.141)).
 
 ## PARAMETERS
 
@@ -236,7 +236,7 @@ This parameter is available only in on-premises Exchange.
 The GlobalWebDistributionEnabled parameter specifies whether all OAB virtual directories in the organization can accept requests to download the OAB. These locations are advertised by the Autodiscover service. Valid values are:
 
 - $true: Any OAB virtual directory in the organization can accept requests to download the OAB. You can't use this setting with the VirtualDirectories parameter.
-- $false: Only the OAB virtual directories that are specified by the VirtualDirectories parameter accept requests to download the OAB. This is the default value.
+- $false: Only the OAB virtual directories that are specified by the VirtualDirectories parameter accept requests to download the OAB. This value is the default.
 
 In Exchange 2013 CU7 or later, we recommend that you use the value $true for this parameter. The Client Access services on any Mailbox server can proxy incoming OAB download requests to the correct location.
 
@@ -259,7 +259,7 @@ Accept wildcard characters: False
 The IsDefault parameter specifies whether the OAB is used by all mailboxes and mailbox databases that don't have an OAB specified. Valid values are:
 
 - $true: The OAB is the default OAB.
-- $false: The OAB is isn't the default OAB. This is the default value.
+- $false: The OAB is isn't the default OAB. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -395,7 +395,7 @@ This parameter is available only in on-premises Exchange.
 The ShadowMailboxDistributionEnabled parameter specifies whether a read only copy of the OAB (also known as a shadow copy) is distributed to all other OAB generation mailboxes (also known as organization mailboxes). This allows additional Mailbox servers to be endpoints for requests to download the OAB, which can help prevent users from downloading the OAB across slow WAN links. Valid values are:
 
 - $true: The OAB is distributed to all other organization mailboxes.
-- $false: The OAB is isn't distributed to other organization mailboxes. This is the default value.
+- $false: The OAB is isn't distributed to other organization mailboxes. This value is the default.
 
 The value of this parameter is only meaningful if you have multiple organization mailboxes, and is only beneficial in Exchange organizations that have multiple Active Directory sites.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-OnPremisesOrganization.md b/exchange/exchange-ps/ExchangePowerShell/New-OnPremisesOrganization.md
index 07fd386992..9acf6fb82a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-OnPremisesOrganization.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-OnPremisesOrganization.md
@@ -32,9 +32,9 @@ New-OnPremisesOrganization [-Name] <String> -HybridDomains <MultiValuedProperty>
 ```
 
 ## DESCRIPTION
-The OnPremisesOrganization object represents an on-premises Microsoft Exchange organization configured for hybrid deployment with a Microsoft 365 organization. It's used with the Hybrid Configuration wizard and is typically created automatically when the hybrid deployment is initially configured by the wizard. Manual modification of this object may result in hybrid deployment misconfiguration; therefore, we strongly recommend that you use the Hybrid Configuration wizard to update this object in the Microsoft 365 organization.
+The OnPremisesOrganization object represents an on-premises Microsoft Exchange organization configured for hybrid deployment with a Microsoft 365 organization. It's used with the Hybrid Configuration wizard and is typically created automatically when the hybrid deployment is initially configured by the wizard. Manual modification of this object might result in hybrid deployment misconfiguration; therefore, we strongly recommend that you use the Hybrid Configuration wizard to update this object in the Microsoft 365 organization.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -69,7 +69,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online, Exchange Online Protection
 
-The HybridDomains parameter specifies the domains that are configured in the hybrid deployment between a Microsoft 365 organization and an on-premises Exchange organization. The domains specified in this parameter must match the domains listed in the HybridConfiguration object for the on-premises Exchange organization configured by the Hybrid Configuration wizard. Multiple domains may be listed and must be separated by a comma, for example, "contoso.com, sales.contoso.com".
+The HybridDomains parameter specifies the domains that are configured in the hybrid deployment between a Microsoft 365 organization and an on-premises Exchange organization. The domains specified in this parameter must match the domains listed in the HybridConfiguration object for the on-premises Exchange organization configured by the Hybrid Configuration wizard. Multiple domains might be listed and must be separated by a comma, for example, "contoso.com, sales.contoso.com".
 
 ```yaml
 Type: MultiValuedProperty
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-OrganizationRelationship.md b/exchange/exchange-ps/ExchangePowerShell/New-OrganizationRelationship.md
index e18434a74d..976f4da310 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-OrganizationRelationship.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-OrganizationRelationship.md
@@ -13,7 +13,7 @@ title: New-OrganizationRelationship
 # New-OrganizationRelationship
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the New-OrganizationRelationship cmdlet to create organization relationships. Organization relationships define the settings that are used with external Exchange organizations to access calendar free/busy information or to move mailboxes between on-premises Exchange servers and Exchange Online as part of hybrid deployments.
 
@@ -51,7 +51,7 @@ New-OrganizationRelationship [-Name] <String> -DomainNames <MultiValuedProperty>
 ## DESCRIPTION
 Before you can create an organization relationship, you must first create a federation trust. For more information, see [Federation](https://learn.microsoft.com/exchange/federation-exchange-2013-help).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -131,10 +131,10 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
 
-The ArchiveAccessEnabled parameter specifies whether the organization relationship has been configured to provide remote archive access. Valid values are:
+The ArchiveAccessEnabled parameter specifies whether the organization relationship is configured to provide remote archive access. Valid values are:
 
 - $true: The external organization provides remote access to mailbox archives.
-- $false: The external organization doesn't provide remote access to mailbox archives. This is the default value.
+- $false: The external organization doesn't provide remote access to mailbox archives. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -176,9 +176,9 @@ Accept wildcard characters: False
 The DeliveryReportEnabled parameter specifies whether Delivery Reports should be shared over the organization relationship. Valid values are:
 
 - $true: Delivery Reports should be shared over the organization relationship. This value means the organization has agreed to share all Delivery Reports with the external organization, and the organization relationship should be used to retrieve Delivery Report information from the external organization.
-- $false: Delivery Reports shouldn't be shared over the organization relationship. This is the default value
+- $false: Delivery Reports shouldn't be shared over the organization relationship. This value is the default
 
-For message tracking to work in a cross-premises Exchange scenario, this parameter must be set to $true on both sides of the organization relationship. If the value of this parameter is set to $false on one or both sides of the organization relationship, message tracking between the organizations won't work in either direction.
+For message tracking to work in a cross-premises Exchange scenario, this parameter must be set to $true on both sides of the organization relationship. If the value of this parameter is set to $false on one or both sides of the organization relationship, message tracking between the organizations doesn't work in either direction.
 
 ```yaml
 Type: Boolean
@@ -218,7 +218,7 @@ Accept wildcard characters: False
 
 The Enabled parameter specifies whether to enable the organization relationship. Valid values are:
 
-- $true: The organization relationship is enabled. This is the default value.
+- $true: The organization relationship is enabled. This value is the default.
 - $false: The organization relationship is disabled. This value completely stops sharing for the organization relationship.
 
 ```yaml
@@ -240,7 +240,7 @@ Accept wildcard characters: False
 The FreeBusyAccessEnabled parameter specifies whether the organization relationship should be used to retrieve free/busy information from the external organization. Valid values are:
 
 - $true: Free/busy information is retrieved from the external organization.
-- $false: Free/busy information isn't retrieved from the external organization. This is the default value.
+- $false: Free/busy information isn't retrieved from the external organization. This value is the default.
 
 You control the free/busy access level and scope by using the FreeBusyAccessLevel and FreeBusyAccessScope parameters.
 
@@ -339,7 +339,7 @@ Accept wildcard characters: False
 The MailboxMoveEnabled parameter specifies whether the organization relationship enables moving mailboxes to or from the external organization. Valid values are:
 
 - $true: Mailbox moves to or from the external organization are allowed.
-- $false: Mailbox moves to or from the external organization aren't allowed. This is the default value.
+- $false: Mailbox moves to or from the external organization aren't allowed. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -389,7 +389,7 @@ Accept wildcard characters: False
 The MailTipsAccessEnabled parameter specifies whether MailTips for users in this organization are returned over this organization relationship. Valid values are:
 
 - $true: MailTips for users in this organization are returned over the organization relationship.
-- $false: MailTips for users in this organization aren't returned over the organization relationship. This is the default value.
+- $false: MailTips for users in this organization aren't returned over the organization relationship. This value is the default.
 
 You control the MailTips access level by using the MailTipsAccessLevel parameter.
 
@@ -412,8 +412,8 @@ Accept wildcard characters: False
 The MailTipsAccessLevel parameter specifies the level of MailTips data that's externally shared over this organization relationship. This parameter can have the following values:
 
 - All: All MailTips are returned, but the recipients in the remote organization are considered external. For the Auto Reply MailTip, the external Auto Reply message is returned.
-- Limited: Only those MailTips that could prevent a non-delivery report (NDR) or an Auto Reply are returned. Custom MailTips, the Large Audience MailTip, and Moderated Recipient MailTips won't be returned.
-- None: No MailTips are returned to the remote organization. This is the default value.
+- Limited: Only those MailTips that could prevent a non-delivery report (NDR) or an Auto Reply are returned. Custom MailTips, the Large Audience MailTip, and Moderated Recipient MailTips aren't returned.
+- None: No MailTips are returned to the remote organization. This value is the default.
 
 This parameter is only meaningful when the MailTipsAccessEnabled parameter value is $true.
 
@@ -509,7 +509,7 @@ Accept wildcard characters: False
 The PhotosEnabled parameter specifies whether photos for users in the internal organization are returned over the organization relationship. Valid values are:
 
 - $true: Photos for users in this organization are returned over the organization relationship.
-- $false: Photos for users in this organization aren't returned over the organization relationship. This is the default value.
+- $false: Photos for users in this organization aren't returned over the organization relationship. This value is the default.
 
 ```yaml
 Type: Boolean
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-OutboundConnector.md b/exchange/exchange-ps/ExchangePowerShell/New-OutboundConnector.md
index 69dd558e8e..539c5c9b79 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-OutboundConnector.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-OutboundConnector.md
@@ -47,7 +47,7 @@ New-OutboundConnector [-Name] <String>
 ## DESCRIPTION
 Outbound connectors send email messages to remote domains that require specific configuration options.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -88,7 +88,7 @@ Accept wildcard characters: False
 The AllAcceptedDomains parameter specifies whether the Outbound connector is used in hybrid organizations where message recipients are in accepted domains of the cloud-based organization. Valid values are:
 
 - $true: The Outbound connector is used in hybrid organizations when message recipients are in an accepted domain of the cloud-based organization. This setting requires OnPremises for the ConnectorType value.
-- $false: The Outbound connector isn't used in hybrid organizations. This is the default value.
+- $false: The Outbound connector isn't used in hybrid organizations. This value is the default.
 
 This parameter is effective only for OnPremises connectors.
 
@@ -114,7 +114,7 @@ The CloudServicesMailEnabled parameter specifies whether the connector is used f
 
 Valid values are:
 
-- $true: The connector is used for mail flow in hybrid organizations, so cross-premises headers are preserved or promoted in messages that flow through the connector. This is the default value for connectors that are created by the Hybrid Configuration wizard. Certain X-MS-Exchange-Organization-\* headers in outbound messages that are sent from one side of the hybrid organization to the other are converted to X-MS-Exchange-CrossPremises-\* headers and are thereby preserved in messages. X-MS-Exchange-CrossPremises-\* headers in inbound messages that are received on one side of the hybrid organization from the other are promoted to X-MS-Exchange-Organization-\* headers. These promoted headers replace any instances of the same X-MS-Exchange-Organization-\* headers that already exist in messages.
+- $true: The connector is used for mail flow in hybrid organizations, so cross-premises headers are preserved or promoted in messages that flow through the connector. This value is the default for connectors that are created by the Hybrid Configuration wizard. Certain X-MS-Exchange-Organization-\* headers in outbound messages that are sent from one side of the hybrid organization to the other are converted to X-MS-Exchange-CrossPremises-\* headers and are thereby preserved in messages. X-MS-Exchange-CrossPremises-\* headers in inbound messages that are received on one side of the hybrid organization from the other are promoted to X-MS-Exchange-Organization-\* headers. These promoted headers replace any instances of the same X-MS-Exchange-Organization-\* headers that already exist in messages.
 - $false: The connector isn't used for mail flow in hybrid organizations, so any cross-premises headers are removed from messages that flow through the connector.
 
 ```yaml
@@ -174,7 +174,7 @@ Accept wildcard characters: False
 
 The ConnectorSource parameter specifies how the connector is created. Valid values are:
 
-- Default: The connector is manually created. This is the default value when you use this cmdlet, and we recommend that you don't change this value.
+- Default: The connector is manually created. This value is the default when you use this cmdlet, and we recommend that you don't change this value.
 - HybridWizard: The connector is automatically created by the Hybrid Configuration Wizard.
 - Migrated: The connector was originally created in Microsoft Forefront Online Protection for Exchange.
 
@@ -217,7 +217,7 @@ Accept wildcard characters: False
 
 The Enabled parameter specifies whether to enable or disable the Outbound connector. Valid values are:
 
-- $true: The connector is enabled. This is the default value.
+- $true: The connector is enabled. This value is the default.
 - $false: The connector is disabled.
 
 ```yaml
@@ -239,7 +239,7 @@ Accept wildcard characters: False
 The IsTransportRuleScoped parameter specifies whether the Outbound connector is associated with a transport rule (also known as a mail flow rule). Valid values are:
 
 - $true: The connector is associated with a transport rule.
-- $false: The connector isn't associated with a transport rule. This is the default value.
+- $false: The connector isn't associated with a transport rule. This value is the default.
 
 You scope a transport rule to an Outbound connector by using the RouteMessageOutboundConnector parameter on the New-TransportRule or Set-TransportRule cmdlets. Messages that match the conditions of the transport rule are routed to their destinations by using the specified Outbound connector.
 
@@ -300,7 +300,7 @@ Accept wildcard characters: False
 The RouteAllMessagesViaOnPremises parameter specifies that all messages serviced by this connector are first routed through the on-premises email system in hybrid organizations. Valid values are:
 
 - $true: Messages are routed through the on-premises email system. This setting requires OnPremises for the ConnectorType value.
-- $false: Messages aren't routed through the on-premises email system. This is the default value.
+- $false: Messages aren't routed through the on-premises email system. This value is the default.
 
 This parameter is effective only for OnPremises connectors.
 
@@ -323,7 +323,7 @@ Accept wildcard characters: False
 The SenderRewritingEnabled parameter specifies that all messages that normally qualify for SRS rewriting are rewritten for routing through the on-premises email system. Valid values are:
 
 - $true: Messages are rewritten by SRS as needed before being routed through the on-premises email system. This setting requires OnPremises for the ConnectorType value.
-- $false: Messages aren't rewritten by SRS before being routed through the on-premises email system. This is the default value.
+- $false: Messages aren't rewritten by SRS before being routed through the on-premises email system. This value is the default.
 
 This parameter is effective only for OnPremises connectors.
 
@@ -372,7 +372,7 @@ Accept wildcard characters: False
 The TestMode parameter specifies whether you want to enabled or disable test mode for the Outbound connector. Valid values are:
 
 - $true: Test mode is enabled.
-- $false: Test mode is disabled. This is the default value.
+- $false: Test mode is disabled. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -417,7 +417,7 @@ The TlsSettings parameter specifies the TLS authentication level that's used for
 - EncryptionOnly: TLS is used only to encrypt the communication channel. No certificate authentication is performed.
 - CertificateValidation: TLS is used to encrypt the channel and certificate chain validation and revocation lists checks are performed.
 - DomainValidation: In addition to channel encryption and certificate validation, the Outbound connector also verifies that the FQDN of the target certificate matches the domain specified in the TlsDomain parameter.
-- $null (blank): This is the default value.
+- $null (blank): This value is the default.
 
 ```yaml
 Type: TlsAuthLevel
@@ -437,7 +437,7 @@ Accept wildcard characters: False
 
 The UseMXRecord parameter enables or disables DNS routing for the connector. Valid values are:
 
-- $true: The connector uses DNS routing (MX records in DNS) to deliver email. This is the default value.
+- $true: The connector uses DNS routing (MX records in DNS) to deliver email. This value is the default.
 - $false: The connector delivers email to one or more smart hosts. This setting requires one or more smart hosts for the SmartHosts value.
 
 ```yaml
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-OutlookProtectionRule.md b/exchange/exchange-ps/ExchangePowerShell/New-OutlookProtectionRule.md
index 264a04ed65..05485cdd9b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-OutlookProtectionRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-OutlookProtectionRule.md
@@ -15,7 +15,7 @@ title: New-OutlookProtectionRule
 ## SYNOPSIS
 **Note**: This cmdlet is no longer supported in the cloud-based service.
 
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the New-OutlookProtectionRule cmdlet to create a Microsoft Outlook protection rule.
 
@@ -45,7 +45,7 @@ For more information, see [Outlook protection rules](https://learn.microsoft.com
 
 Outlook protection rules created without a condition apply to all messages.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-OutlookProvider.md b/exchange/exchange-ps/ExchangePowerShell/New-OutlookProvider.md
index af0e3feeb6..9e7a811556 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-OutlookProvider.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-OutlookProvider.md
@@ -32,7 +32,7 @@ New-OutlookProvider [-Name] <String>
 ## DESCRIPTION
 The New-OutlookProvider cmdlet creates the AutoDiscoverConfig object under the Global Settings object in Active Directory and sets the attributes specified.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-OwaMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-OwaMailboxPolicy.md
index 0ea3a13dbb..c0311a932d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-OwaMailboxPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-OwaMailboxPolicy.md
@@ -13,7 +13,7 @@ title: New-OwaMailboxPolicy
 # New-OwaMailboxPolicy
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the New-OwaMailboxPolicy cmdlet to create Outlook on the web mailbox policies.
 
@@ -33,9 +33,9 @@ New-OwaMailboxPolicy [-Name] <String>
 ## DESCRIPTION
 Use the Set-OwaMailboxPolicy cmdlet to configure the new policy.
 
-Changes to Outlook on the web mailbox policies may take up to 60 minutes to take effect. In on-premises Exchange, you can force an update by restarting IIS (Stop-Service WAS -Force and Start-Service W3SVC).
+Changes to Outlook on the web mailbox policies might take up to 60 minutes to take effect. In on-premises Exchange, you can force an update by restarting IIS (Stop-Service WAS -Force and Start-Service W3SVC).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-OwaVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/New-OwaVirtualDirectory.md
index 291b08b57f..e051fb1584 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-OwaVirtualDirectory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-OwaVirtualDirectory.md
@@ -45,7 +45,7 @@ New-OwaVirtualDirectory
 ## DESCRIPTION
 By default, when Exchange is installed, the Outlook on the web virtual directory owa is created in the default IIS website on the server.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -163,7 +163,7 @@ The ExtendedProtectionFlags parameter specifies custom settings for Extended Pro
 - AllowDotlessSPN: Required if you want to use Service Principal Name (SPN) values that don't contain FQDNs (for example, HTTP/ContosoMail instead of HTTP/mail.contoso.com). You specify SPNs with the ExtendedProtectionSPNList parameter. This setting makes Extended Protection for Authentication less secure because dotless certificates aren't unique, so it isn't possible to ensure that the client-to-proxy connection was established over a secure channel.
 - NoServiceNameCheck: The SPN list isn't checked to validate a channel binding token. This setting makes Extended Protection for Authentication less secure. We generally don't recommend this setting.
 - Proxy: A proxy server is responsible for terminating the SSL channel. To use this setting, you need to register an SPN by using the ExtendedProtectionSPNList parameter.
-- ProxyCoHosting: HTTP and HTTPS traffic may be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server.
+- ProxyCoHosting: HTTP and HTTPS traffic might be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server.
 
 ```yaml
 Type: MultiValuedProperty
@@ -183,7 +183,7 @@ Accept wildcard characters: False
 
 The ExtendedProtectionSPNList parameter specifies a list of valid Service Principal Names (SPNs) if you're using Extended Protection for Authentication on the virtual directory. Valid values are:
 
-- $null: This is the default value.
+- $null: This value is the default.
 - Single SPN or comma delimited list of valid SPNs: The SPN value format is `Protocol\FQDN`. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter.
 
 ```yaml
@@ -204,8 +204,8 @@ Accept wildcard characters: False
 
 The ExtendedProtectionTokenChecking parameter defines how you want to use Extended Protection for Authentication on the virtual directory. Extended Protection for Authentication isn't enabled by default. Valid values are:
 
-- None: Extended Protection for Authentication isn't be used on the virtual directory. This is the default value.
-- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication will work, but may not be as secure as connections that use Extended Protection for Authentication.
+- None: Extended Protection for Authentication isn't be used on the virtual directory. This value is the default.
+- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication works, but might not be as secure as connections that use Extended Protection for Authentication.
 - Require: Extended Protection for Authentication is used for all connections between clients and the virtual directory. If either the client or server doesn't support it, the connection will fail. If you use this value, you also need to set an SPN value for the ExtendedProtectionSPNList parameter.
 
 **Note**: If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter.
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-PartnerApplication.md b/exchange/exchange-ps/ExchangePowerShell/New-PartnerApplication.md
index f78ea97f86..af5db2924b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-PartnerApplication.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-PartnerApplication.md
@@ -60,7 +60,7 @@ You can configure partner applications such as Microsoft SharePoint to access Ex
 
 We recommend that you use the Configure-EnterprisePartnerApplication.ps1 script in the %ExchangeInstallPath%Scripts folder to configure partner applications.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -153,7 +153,7 @@ Accept wildcard characters: False
 
 The AccountType parameter specifies the type of Microsoft account that's required for the partner application. Valid values are:
 
-- OrganizationalAccount (This is the default value)
+- OrganizationalAccount (default value)
 - ConsumerAccount
 
 ```yaml
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-PhishSimOverridePolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-PhishSimOverridePolicy.md
index 3edf56b20a..fda8e38416 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-PhishSimOverridePolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-PhishSimOverridePolicy.md
@@ -33,7 +33,7 @@ New-PhishSimOverridePolicy [-Name] <String>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -50,7 +50,7 @@ This example creates the phishing simulation override policy named PhishSimOverr
 
 > Applicable: Exchange Online
 
-The Name parameter specifies the name for the phishing simulation override policy. Regardless of the value you specify, the name will be PhishSimOverridePolicy.
+The Name parameter specifies the name for the phishing simulation override policy. Regardless of the value you specify, the name is PhishSimOverridePolicy.
 
 ```yaml
 Type: String
@@ -127,7 +127,7 @@ Accept wildcard characters: False
 
 The Enabled parameter specifies whether the policy is enabled. Valid values are:
 
-- $true: The policy is enabled. This is the default value.
+- $true: The policy is enabled. This value is the default.
 - $false: The policy is disabled.
 
 ```yaml
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-PolicyTipConfig.md b/exchange/exchange-ps/ExchangePowerShell/New-PolicyTipConfig.md
index bb9efbeb94..0eb6102ca0 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-PolicyTipConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-PolicyTipConfig.md
@@ -13,7 +13,7 @@ title: New-PolicyTipConfig
 # New-PolicyTipConfig
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-PolicyTipConfig cmdlet to create custom Policy Tips in your organization.
 
@@ -30,7 +30,7 @@ New-PolicyTipConfig [-Name] <String> -Value <String>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-PowerShellVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/New-PowerShellVirtualDirectory.md
index 6314ea56c9..b79b93eb6b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-PowerShellVirtualDirectory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-PowerShellVirtualDirectory.md
@@ -42,7 +42,7 @@ New-PowerShellVirtualDirectory [-Name] <String>
 ## DESCRIPTION
 Although it's possible to create a Windows PowerShell virtual directory, we recommend that you only do so at the request of Microsoft Customer Service and Support.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -59,7 +59,7 @@ This example creates a Windows PowerShell virtual directory and configures it to
 
 > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-The Name parameter specifies the name of the new PowerShell virtual directory. The name you provide will have the name of the website it's created under appended to it. If the name you provide contains spaces, enclose the name in quotation marks (").
+The Name parameter specifies the name of the new PowerShell virtual directory. The name you provide has the name of the website it's created under appended to it. If the name you provide contains spaces, enclose the name in quotation marks (").
 
 ```yaml
 Type: String
@@ -140,7 +140,7 @@ The ExtendedProtectionFlags parameter specifies custom settings for Extended Pro
 - AllowDotlessSPN: Required if you want to use Service Principal Name (SPN) values that don't contain FQDNs (for example, HTTP/ContosoMail instead of HTTP/mail.contoso.com). You specify SPNs with the ExtendedProtectionSPNList parameter. This setting makes Extended Protection for Authentication less secure because dotless certificates aren't unique, so it isn't possible to ensure that the client-to-proxy connection was established over a secure channel.
 - NoServiceNameCheck: The SPN list isn't checked to validate a channel binding token. This setting makes Extended Protection for Authentication less secure. We generally don't recommend this setting.
 - Proxy: A proxy server is responsible for terminating the SSL channel. To use this setting, you need to register an SPN by using the ExtendedProtectionSPNList parameter.
-- ProxyCoHosting: HTTP and HTTPS traffic may be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server.
+- ProxyCoHosting: HTTP and HTTPS traffic might be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server.
 
 ```yaml
 Type: MultiValuedProperty
@@ -160,7 +160,7 @@ Accept wildcard characters: False
 
 The ExtendedProtectionSPNList parameter specifies a list of valid Service Principal Names (SPNs) if you're using Extended Protection for Authentication on the virtual directory. Valid values are:
 
-- $null: This is the default value.
+- $null: This value is the default.
 - Single SPN or comma delimited list of valid SPNs: The SPN value format is `Protocol\FQDN`. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter.
 
 ```yaml
@@ -181,8 +181,8 @@ Accept wildcard characters: False
 
 The ExtendedProtectionTokenChecking parameter defines how you want to use Extended Protection for Authentication on the virtual directory. Extended Protection for Authentication isn't enabled by default. Valid values are:
 
-- None: Extended Protection for Authentication isn't be used on the virtual directory. This is the default value.
-- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication will work, but may not be as secure as connections that use Extended Protection for Authentication.
+- None: Extended Protection for Authentication isn't be used on the virtual directory. This value is the default.
+- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication work, but might not be as secure as connections that use Extended Protection for Authentication.
 - Require: Extended Protection for Authentication is used for all connections between clients and the virtual directory. If either the client or server doesn't support it, the connection will fail. If you use this value, you also need to set an SPN value for the ExtendedProtectionSPNList parameter.
 
 **Note**: If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter.
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ProtectionAlert.md b/exchange/exchange-ps/ExchangePowerShell/New-ProtectionAlert.md
index 1174020b1c..f52a7470fb 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-ProtectionAlert.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-ProtectionAlert.md
@@ -174,8 +174,8 @@ Accept wildcard characters: False
 The AggregationType parameter specifies the how the alert policy triggers alerts for multiple occurrences of monitored activity. Valid values are:
 
 - None: Alerts are triggered for every occurrence of the activity.
-- SimpleAggregation: Alerts are triggered based on the volume of activity in a given time window (the values of the Threshold and TimeWindow parameters). This is the default value.
-- AnomalousAggregation: Alerts are triggered when the volume of activity reaches unusual levels (greatly exceeds the normal baseline that's established for the activity). Note that it can take up to 7 days for Microsoft 365 to establish the baseline. During the baseline calculation period, no alerts are generated for the activity.
+- SimpleAggregation: Alerts are triggered based on the volume of activity in a given time window (the values of the Threshold and TimeWindow parameters). This value is the default.
+- AnomalousAggregation: Alerts are triggered when the volume of activity reaches unusual levels (greatly exceeds the normal baseline that's established for the activity). It can take up to 7 days for Microsoft 365 to establish the baseline. During the baseline calculation period, no alerts are generated for the activity.
 
 ```yaml
 Type: AlertAggregationType
@@ -332,7 +332,7 @@ Accept wildcard characters: False
 The Disabled parameter enables or disables the alert policy. Valid values are:
 
 - $true: The alert policy is disabled.
-- $false: The alert policy is enabled. This is the default value.
+- $false: The alert policy is enabled. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -479,7 +479,7 @@ Accept wildcard characters: False
 The NotifyUserOnFilterMatch parameter specifies whether to trigger an alert for a single event when the alert policy is configured for aggregated activity. Valid values are:
 
 - $true: Even though the alert is configured for aggregated activity, a notification is triggered during a match for the activity (basically, an early warning).
-- $false: Alerts are triggered according to the specified aggregation type. This is the default value.
+- $false: Alerts are triggered according to the specified aggregation type. This value is the default.
 
 You can't use this parameter when the AggregationType parameter value is None (alerts are triggered for every occurrence of the activity).
 
@@ -519,10 +519,10 @@ Accept wildcard characters: False
 
 > Applicable: Security & Compliance
 
-The NotifyUserThrottleThreshold parameter specifies the maximum number of notifications for the alert policy within the time period specified by the NotifyUserThrottleWindow parameter. Once the maximum number of notifications has been reached in the time period, no more notifications are sent for the alert. Valid values are:
+The NotifyUserThrottleThreshold parameter specifies the maximum number of notifications for the alert policy within the time period specified by the NotifyUserThrottleWindow parameter. Once the maximum number of notifications is reached in the time period, no more notifications are sent for the alert. Valid values are:
 
 - An integer.
-- The value $null. This is the default value (no maximum number of notifications for an alert).
+- The value $null. This value is the default (no maximum number of notifications for an alert).
 
 ```yaml
 Type: Int32
@@ -543,7 +543,7 @@ Accept wildcard characters: False
 The NotifyUserThrottleWindow parameter specifies the time interval in minutes that's used by the NotifyUserThrottleThreshold parameter. Valid values are:
 
 - An integer.
-- The value $null. This is the default value (no interval for notification throttling).
+- The value $null. This value is the default (no interval for notification throttling).
 
 ```yaml
 Type: Int32
@@ -639,7 +639,7 @@ Accept wildcard characters: False
 
 The Severity parameter specifies the severity of the detection. Valid values are:
 
-- Low (This is the default value)
+- Low (default value)
 - Medium
 - High
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-PublicFolder.md b/exchange/exchange-ps/ExchangePowerShell/New-PublicFolder.md
index 8f7f1f561f..77226a0eca 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-PublicFolder.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-PublicFolder.md
@@ -13,7 +13,7 @@ title: New-PublicFolder
 # New-PublicFolder
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the New-PublicFolder cmdlet to create a public folder with the specified name.
 
@@ -34,7 +34,7 @@ New-PublicFolder [-Name] <String>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-PublicFolderDatabase.md b/exchange/exchange-ps/ExchangePowerShell/New-PublicFolderDatabase.md
index 4b6ccdc335..a22d12b805 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-PublicFolderDatabase.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-PublicFolderDatabase.md
@@ -34,7 +34,7 @@ New-PublicFolderDatabase [-Name] <String> -Server <ServerIdParameter>
 ## DESCRIPTION
 The new database must be mounted after it's created. For more information about mounting databases, see [Mount a Database](https://learn.microsoft.com/previous-versions/office/exchange-server-2010/bb123587(v=exchg.141)).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-PublicFolderDatabaseRepairRequest.md b/exchange/exchange-ps/ExchangePowerShell/New-PublicFolderDatabaseRepairRequest.md
index 231d0ed6c1..b7047a7953 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-PublicFolderDatabaseRepairRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-PublicFolderDatabaseRepairRequest.md
@@ -35,7 +35,7 @@ Public folders on the public folder database can still be accessed while the req
 
 After you begin the repair request, it can't be stopped unless you dismount the database. For more information, see [Dismount a Database](https://learn.microsoft.com/previous-versions/office/exchange-server-2010/bb123903(v=exchg.141)).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-PublicFolderMigrationRequest.md b/exchange/exchange-ps/ExchangePowerShell/New-PublicFolderMigrationRequest.md
index 6cc054734f..e096e2cdf4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-PublicFolderMigrationRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-PublicFolderMigrationRequest.md
@@ -50,7 +50,7 @@ New-PublicFolderMigrationRequest [[-Name] <String>] -SourceDatabase <DatabaseIdP
 ## DESCRIPTION
 Migrating public folders is a multi-step process. For more information before you attempt a public folder migration, see [Use serial migration to migrate public folders to Exchange 2013 from previous versions](https://learn.microsoft.com/previous-versions/exchange-server/exchange-150/jj150486(v=exchg.150)).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -332,7 +332,7 @@ The Priority parameter specifies the order in which the request should be proces
 - Lowest
 - Lower
 - Low
-- Normal: This is the default value.
+- Normal: This value is the default.
 - High
 - Higher
 - Highest
@@ -417,7 +417,7 @@ Accept wildcard characters: False
 
 The Suspend switch specifies whether to suspend the request. You don't need to specify a value with this switch.
 
-If you use this switch, the request is queued, but the request won't reach the status of InProgress until you resume the request with the relevant resume cmdlet.
+If you use this switch, the request is queued, but the request doesn't reach the status of InProgress until you resume the request with the relevant resume cmdlet.
 
 ```yaml
 Type: SwitchParameter
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-PublicFolderMoveRequest.md b/exchange/exchange-ps/ExchangePowerShell/New-PublicFolderMoveRequest.md
index 03c3853697..94bd9c8323 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-PublicFolderMoveRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-PublicFolderMoveRequest.md
@@ -13,11 +13,11 @@ title: New-PublicFolderMoveRequest
 # New-PublicFolderMoveRequest
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the New-PublicFolderMoveRequest cmdlet to begin the process of moving public folder contents between public folder mailboxes. Moving public folders only moves the physical contents of the public folder; it doesn't change the logical hierarchy. When the move request is completed, you must run the Remove-PublicFolderMoveRequest cmdlet to remove the request or wait until the time specified in the CompletedRequestAgeLimit parameter has passed. The request must be removed before you can run another move request.
 
-Be aware that the target public folder mailbox will be locked while the move request is active. For more information, see the Description section.
+Be aware that the target public folder mailbox wis locked while the move request is active. For more information, see the Description section.
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
@@ -45,11 +45,11 @@ New-PublicFolderMoveRequest -Folders <PublicFolderIdParameter[]> -TargetMailbox
 ```
 
 ## DESCRIPTION
-The New-PublicFolderMoveRequest cmdlet moves public folders from a source public folder mailbox to a target public folder mailbox. While the move request is active, the target public folder mailbox will be locked. As a result, public folders already residing in the target public folder mailbox will be inaccessible until the move request is complete. Therefore, before you begin the move request, you should ensure that no users are accessing public folder data in that target public folder mailbox.
+The New-PublicFolderMoveRequest cmdlet moves public folders from a source public folder mailbox to a target public folder mailbox. While the move request is active, the target public folder mailbox is locked. As a result, public folders already residing in the target public folder mailbox are inaccessible until the move request is complete. Therefore, before you begin the move request, you should ensure that no users are accessing public folder data in that target public folder mailbox.
 
 To move the public folder mailbox to another mailbox database, use the New-MoveRequest cmdlet. To ensure that this folder is already in the target public folder mailbox, run the Update-PublicFolderMailbox cmdlet against the target public folder mailbox. You can only perform one move request at a time. You can also move public folders by using the Move-PublicFolderBranch.ps1 script.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -84,7 +84,7 @@ This example moves all public folders from public folder mailbox Pub1 to public
 
 > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
 
-The Folders parameter specifies the public folders that you want to move. If the public folder has child public folders, these child public folders won't be moved unless you explicitly state them in the command. You can move multiple public folders by separating them with a comma, for example, \\Dev\\CustomerEngagements,\\Dev\\RequestsforChange,\\Dev\\Usability.
+The Folders parameter specifies the public folders that you want to move. If the public folder has child public folders, these child public folders aren't moved unless you explicitly state them in the command. You can move multiple public folders by separating them with a comma, for example, \\Dev\\CustomerEngagements,\\Dev\\RequestsforChange,\\Dev\\Usability.
 
 ```yaml
 Type: PublicFolderIdParameter[]
@@ -191,7 +191,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
 
-The CompletedRequestAgeLimit parameter specifies how long the request will be kept after it has been completed before being automatically removed. The default value for this parameter is 30 days.
+The CompletedRequestAgeLimit parameter specifies how long the request is kept after completion before being automatically removed. The default value for this parameter is 30 days.
 
 ```yaml
 Type: Unlimited
@@ -311,7 +311,7 @@ The Priority parameter specifies the order in which the request should be proces
 - Lowest
 - Lower
 - Low
-- Normal: This is the default value.
+- Normal: This value is the default.
 - High
 - Higher
 - Highest
@@ -360,7 +360,7 @@ Accept wildcard characters: False
 
 The Suspend switch specifies whether to suspend the request. You don't need to specify a value with this switch.
 
-If you use this switch, the request is queued, but the request won't reach the status of InProgress until you resume the request with the relevant resume cmdlet.
+If you use this switch, the request is queued, but the request doesn't reach the status of InProgress until you resume the request with the relevant resume cmdlet.
 
 ```yaml
 Type: SwitchParameter
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-QuarantinePermissions.md b/exchange/exchange-ps/ExchangePowerShell/New-QuarantinePermissions.md
index a5f3e8220a..07e69cfb7f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-QuarantinePermissions.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-QuarantinePermissions.md
@@ -39,7 +39,7 @@ New-QuarantinePermissions
 ## DESCRIPTION
 The default value for any parameters that you don't use is $false, so you only need to use parameters (permissions) that you want to set to $true.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -79,7 +79,7 @@ In the same PowerShell session, you can use `$FullAccess` for the _EndUserQuaran
 The PermissionToAllowSender parameter specifies whether users are allowed to add the quarantined message sender to their Safe Senders list. Valid values are:
 
 - $true: Allow sender is available for affected messages in quarantine.
-- $false: Allow sender isn't available for affected messages in quarantine. This is the default value.
+- $false: Allow sender isn't available for affected messages in quarantine. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -100,7 +100,7 @@ Accept wildcard characters: False
 The PermissionToBlockSender parameter specifies whether users are allowed to add the quarantined message sender to their Blocked Senders list. Valid values are:
 
 - $true: Block sender is available in quarantine notifications for affected messages, and Block sender is available for affected messages in quarantine.
-- $false: Block sender isn't available in quarantine notifications for affected messages, and Block sender isn't available for affected messages in quarantine. This is the default value.
+- $false: Block sender isn't available in quarantine notifications for affected messages, and Block sender isn't available for affected messages in quarantine. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -121,7 +121,7 @@ Accept wildcard characters: False
 The PermissionToDelete parameter specifies whether users are allowed to delete messages from quarantine. Valid values are:
 
 - $true: Delete messages and Delete from quarantine are available for affected messages in quarantine.
-- $false: Delete messages and Delete from quarantine aren't available for affected messages in quarantine. This is the default value.
+- $false: Delete messages and Delete from quarantine aren't available for affected messages in quarantine. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -142,7 +142,7 @@ Accept wildcard characters: False
 The PermissionToDownload parameter specifies whether users are allowed to download messages from quarantine. Valid values are:
 
 - $true: The permission is enabled.
-- $false: The permission is disabled. This is the default value.
+- $false: The permission is disabled. This value is the default.
 
 Currently, this value has no effect on the available actions in quarantine notifications or quarantine for affected messages. End-users can't download quarantined messages.
 
@@ -165,7 +165,7 @@ Accept wildcard characters: False
 The PermissionToPreview parameter specifies whether users are allowed to preview quarantined messages. Valid values are:
 
 - $true: Preview message is available for affected messages in quarantine.
-- $false: Preview message isn't available for affected messages in quarantine. This is the default value.
+- $false: Preview message isn't available for affected messages in quarantine. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -232,7 +232,7 @@ Accept wildcard characters: False
 The PermissionToViewHeader parameter specifies whether users are allowed to view the message headers of quarantined messages. Valid values are:
 
 - $true: The permission is enabled.
-- $false: The permission is disabled. This is the default value.
+- $false: The permission is disabled. This value is the default.
 
 Currently, this value has no effect on the available actions in quarantine notifications or quarantine for affected messages. View message header is always available for affected messages in quarantine.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-QuarantinePolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-QuarantinePolicy.md
index 8a7e07202b..6cfaa0b09b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-QuarantinePolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-QuarantinePolicy.md
@@ -51,7 +51,7 @@ New-QuarantinePolicy [-Name] <String>
 ## DESCRIPTION
 Quarantine policies define what users are allowed to do to quarantined messages based on why the message was quarantined (for supported features) and quarantine notification settings. For more information, see [Quarantine policies](https://learn.microsoft.com/defender-office-365/quarantine-policies).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -382,7 +382,7 @@ Accept wildcard characters: False
 The ESNEnabled parameter specifies whether to enable quarantine notifications (formerly known as end-user spam notifications) for the policy. Valid values are:
 
 - $true: Quarantine notifications are enabled.
-- $false: Quarantine notifications are disabled. User can only access quarantined messages in quarantine, not in email notifications. This is the default value.
+- $false: Quarantine notifications are disabled. User can only access quarantined messages in quarantine, not in email notifications. This value is the default.
 
 **Note**: If the value of this parameter is $true and the value of the EndUserQuarantinePermissionsValue parameter is 0 (No access where all permissions are turned off), users can see their messages in quarantine, but the only available action for the messages is **View message header**.
 
@@ -405,7 +405,7 @@ Accept wildcard characters: False
 The IncludeMessagesFromBlockedSenderAddress parameter specifies whether to send quarantine notifications for quarantined messages from blocked sender addresses. Valid values are:
 
 - $true: Recipients get quarantine notifications for affected messages from blocked senders.
-- $false: Recipients don't get quarantine notifications for affected messages from blocked senders. This is the default value.
+- $false: Recipients don't get quarantine notifications for affected messages from blocked senders. This value is the default.
 
 ```yaml
 Type: Boolean
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ReceiveConnector.md b/exchange/exchange-ps/ExchangePowerShell/New-ReceiveConnector.md
index 72b383e6a6..99f534f8f4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-ReceiveConnector.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-ReceiveConnector.md
@@ -384,7 +384,7 @@ On Mailbox servers, you can create Receive connectors in the Front End Transport
 
 For more information about Receive connector usage types, permission groups, and authentication methods, see [Receive connectors](https://learn.microsoft.com/Exchange/mail-flow/connectors/receive-connectors).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -652,7 +652,7 @@ Accept wildcard characters: False
 The AdvertiseClientSettings parameter specifies whether the SMTP server name, port number, and authentication settings for the Receive connector are displayed to users in the options of Outlook on the web. Valid values are:
 
 - $true: The SMTP values are displayed in Outlook on the web. Typically, you would only use this setting for a Receive connector with the usage type Client (authenticated SMTP connections on TCP port 587 for POP3 and IMAP4 clients).
-- $false: The SMTP values are displayed in Outlook on the web. This is the default value.
+- $false: The SMTP values are displayed in Outlook on the web. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -704,7 +704,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2016, Exchange Server 2019
 
-The AuthTarpitInterval parameter specifies the period of time to delay responses to failed authentication attempts from remote servers that may be abusing the connection. The default value is 5 seconds.
+The AuthTarpitInterval parameter specifies the period of time to delay responses to failed authentication attempts from remote servers that might be abusing the connection. The default value is 5 seconds.
 
 To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds.
 
@@ -752,7 +752,7 @@ Accept wildcard characters: False
 
 The BinaryMimeEnabled parameter specifies whether the BINARYMIME Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are:
 
-- $true: BINARYMIME is enabled and is advertised in the EHLO response. This setting requires that the ChunkingEnabled parameter is also set to the value $true. This is the default value.
+- $true: BINARYMIME is enabled and is advertised in the EHLO response. This setting requires that the ChunkingEnabled parameter is also set to the value $true. This value is the default.
 - $false: BINARYMIME is disabled and isn't advertised in the EHLO response.
 
 The binary MIME extension is defined in RFC 3030.
@@ -775,7 +775,7 @@ Accept wildcard characters: False
 
 The ChunkingEnabled parameter specifies whether the CHUNKING Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are:
 
-- $true: CHUNKING is enabled and is advertised in the EHLO response. This is the default value.
+- $true: CHUNKING is enabled and is advertised in the EHLO response. This value is the default.
 - $false: CHUNKING is disabled and isn't advertised in the EHLO response.
 
 Chunking is defined in RFC 3030.
@@ -896,7 +896,7 @@ This usage type assigns the following default permission groups and authenticati
 
 When you use this switch, you also need to use the Bindings and RemoteIPRanges parameters.
 
-If you don't also use the PermissionGroups parameter to assign at least one permission group, you'll need to use the PermissionGroups parameter on the Set-ReceiveConnector cmdlet after you create the Receive connector (otherwise, the Receive connector can't accept inbound SMTP connections).
+If you don't also use the PermissionGroups parameter to assign at least one permission group, you need to use the PermissionGroups parameter on the Set-ReceiveConnector cmdlet after you create the Receive connector (otherwise, the Receive connector can't accept inbound SMTP connections).
 
 You can't use this switch with any other usage type parameters (Client, Internal, Internet, Partner, or Usage).
 
@@ -946,7 +946,7 @@ Accept wildcard characters: False
 
 The DeliveryStatusNotificationEnabled parameter specifies whether the DSN (delivery status notification) Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are:
 
-- $true: DSN is enabled and is advertised in the EHLO response. This is the default value.
+- $true: DSN is enabled and is advertised in the EHLO response. This value is the default.
 - $false: DSN is disabled and isn't advertised in the EHLO response.
 
 Delivery status notifications are defined in RFC 3461.
@@ -992,7 +992,7 @@ The DomainSecureEnabled parameter specifies whether to enable or disable mutual
 - $true: Mutual TLS authentication is enabled.
 - $false: Mutual TLS authentication is disabled.
 
-Note that setting this parameter to the value $true is only part of the requirements for enabling mutual TLS authentication:
+Setting this parameter to the value $true is only part of the requirements for enabling mutual TLS authentication:
 
 - The AuthMechanism parameter must contain the value Tls, and can't contain the value ExternalAuthoritative.
 - The domain that's used for mutual TLS authentication must be configured in the following locations:
@@ -1018,7 +1018,7 @@ Accept wildcard characters: False
 
 The EightBitMimeEnabled parameter specifies whether the 8BITMIME Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are:
 
-- $true: 8BITMIME is enabled and is advertised in the EHLO response. This is the default value.
+- $true: 8BITMIME is enabled and is advertised in the EHLO response. This value is the default.
 - $false: 8BITMIME is disabled and isn't advertised in the EHLO response.
 
 8-bit data transmission is defined in RFC 6152.
@@ -1064,7 +1064,7 @@ Accept wildcard characters: False
 
 The Enabled parameter specifies whether to enable or disable the Receive connector. Valid values are:
 
-- $true: The Receive connector is enabled. This is the default value.
+- $true: The Receive connector is enabled. This value is the default.
 - $false: The Receive connector is disabled.
 
 ```yaml
@@ -1085,7 +1085,7 @@ Accept wildcard characters: False
 
 The EnhancedStatusCodesEnabled parameter specifies whether the ENHANCEDSTATUSCODES Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are:
 
-- $true: ENHANCEDSTATUSCODES is enabled and is advertised in the EHLO response. This is the default value.
+- $true: ENHANCEDSTATUSCODES is enabled and is advertised in the EHLO response. This value is the default.
 - $false: ENHANCEDSTATUSCODES is disabled and isn't advertised in the EHLO response.
 
 Enhanced status codes are defined in RFC 2034.
@@ -1108,7 +1108,7 @@ Accept wildcard characters: False
 
 The ExtendedProtectionPolicy parameter specifies how Extended Protection for Authentication is implemented on the Receive connector. Valid values are:
 
-- None: Extended Protection for Authentication isn't used. This is the default value.
+- None: Extended Protection for Authentication isn't used. This value is the default.
 - Allow: Extended Protection for Authentication is used only if the connecting host supports it. Otherwise, connections are established without Extended Protection for Authentication.
 - Require: Extended Protection for Authentication is required for all incoming connections to this Receive connector. If the connecting host doesn't support Extended Protection for Authentication, the connection is rejected.
 
@@ -1158,7 +1158,7 @@ Accept wildcard characters: False
 The LongAddressesEnabled parameter specifies whether the Receive connector accepts long X.400 email addresses. The X.400 email addresses are encapsulated in SMTP email addresses by using the Internet Mail Connector Encapsulated Address (IMCEA) encapsulation method. Valid values are
 
 - $true: X.400 email addresses can be up to 1,860 characters long after IMCEA encapsulation.
-- $false: The maximum length of a complete SMTP email address is 571 characters. This is the default value.
+- $false: The maximum length of a complete SMTP email address is 571 characters. This value is the default.
 
 When you set this parameter to the value $true, the following changes are made to the Receive connector:
 
@@ -1186,7 +1186,7 @@ Accept wildcard characters: False
 
 This parameter isn't used by Exchange Server 2016. It's used only by Exchange 2010 servers in coexistence environments.
 
-The MaxAcknowledgementDelay parameter specifies the maximum period the transport server delays acknowledgment until it verifies that the message has been successfully delivered to all recipients. When receiving messages from a host that doesn't support shadow redundancy, an Exchange Server 2010 transport server will delay issuing an acknowledgment until it verifies that the message has been successfully delivered to all recipients. However, if it takes too long to verify successful delivery, the transport server will time out and issue an acknowledgment anyway.
+The MaxAcknowledgementDelay parameter specifies the maximum period the transport server delays acknowledgment until it verifies that the message is successfully delivered to all recipients. When receiving messages from a host that doesn't support shadow redundancy, an Exchange Server 2010 transport server delays issuing an acknowledgment until it verifies that the message is successfully delivered to all recipients. However, if it takes too long to verify successful delivery, the transport server times out and issue an acknowledgment anyway.
 
 To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds.
 
@@ -1217,7 +1217,7 @@ When you enter a value, qualify the value with one of the following units:
 - MB (megabytes)
 - GB (gigabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 A valid value is from 1 to 2147483647 bytes.
 
@@ -1374,7 +1374,7 @@ When you enter a value, qualify the value with one of the following units:
 - MB (megabytes)
 - GB (gigabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 A valid value for this parameter is from 65536 to 2147483647 bytes.
 
@@ -1488,7 +1488,7 @@ Accept wildcard characters: False
 The OrarEnabled parameter enables or disables Originator Requested Alternate Recipient (ORAR) on the Receive connector. Valid values are:
 
 - $true: ORAR is enabled and is advertised in the XORAR keyword in the EHLO response. The actual ORAR information is transmitted in the RCPT TO SMTP command.
-- $false: ORAR is disabled and is isn't advertised in the EHLO response. This is the default value.
+- $false: ORAR is disabled and is isn't advertised in the EHLO response. This value is the default.
 
 If the email address specified in the ORAR information is a long X.400 email address, you need to set the LongAddressesEnabled parameter to the value $true.
 
@@ -1542,7 +1542,7 @@ Accept wildcard characters: False
 
 The PipeliningEnabled parameter specifies whether the PIPELINING Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are:
 
-- $true: PIPELINING is enabled and is advertised in the EHLO response. This is the default value.
+- $true: PIPELINING is enabled and is advertised in the EHLO response. This value is the default.
 - $false: PIPELINING is disabled and isn't advertised in the EHLO response.
 
 Pipelining is defined in RFC 2920.
@@ -1565,7 +1565,7 @@ Accept wildcard characters: False
 
 The ProtocolLoggingLevel parameter specifies whether to enable or disable protocol logging for the Receive connector. Valid values are:
 
-- None: Protocol logging is disabled on the Receive connector. This is the default value.
+- None: Protocol logging is disabled on the Receive connector. This value is the default.
 - Verbose: Protocol logging is enabled on the Receive connector.
 
 For more information about protocol logging, see [Protocol logging](https://learn.microsoft.com/Exchange/mail-flow/connectors/protocol-logging).
@@ -1589,7 +1589,7 @@ Accept wildcard characters: False
 The RejectReservedSecondLevelRecipientDomains parameter specifies whether to reject connections that contain recipients in reserved second-level domains as specified in RFC 2606 (example.com, example.net, or example.org). Valid value are:
 
 - $true: RCPT TO commands that contain reserved second-level domains are rejected.
-- $false: RCPT TO commands that contain reserved second-level domains aren't rejected. This is the default value.
+- $false: RCPT TO commands that contain reserved second-level domains aren't rejected. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -1610,7 +1610,7 @@ Accept wildcard characters: False
 The RejectReservedTopLevelRecipientDomains parameter specifies whether to reject connections that contain recipients in reserved top-level domains (TLDs) as specified in RFC 2606 (.test, .example, .invalid, or .localhost). Valid value are:
 
 - $true: RCPT TO commands that contain reserved TLDs are rejected.
-- $false: RCPT TO commands that contain reserved TLDs aren't rejected. This is the default value.
+- $false: RCPT TO commands that contain reserved TLDs aren't rejected. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -1631,7 +1631,7 @@ Accept wildcard characters: False
 The RejectSingleLabelRecipientDomains parameter specifies whether to reject connections that contain recipients in single-label domains (for example, chris@contoso instead of chris@contoso.com). Valid values are:
 
 - $true: RCPT TO commands that contain single-label domains are rejected.
-- $false: RCPT TO commands that contain single-label domains aren't rejected. This is the default value.
+- $false: RCPT TO commands that contain single-label domains aren't rejected. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -1652,7 +1652,7 @@ Accept wildcard characters: False
 The RequireEHLODomain parameter specifies whether the client must provide a domain name in the EHLO handshake after the SMTP connection is established. Valid values are:
 
 - $true: The client must provide a domain name in the EHLO handshake. If it doesn't, the SMTP connection is closed.
-- $false: The client isn't required to provide a domain name in the EHLO handshake. This is the default value.
+- $false: The client isn't required to provide a domain name in the EHLO handshake. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -1673,7 +1673,7 @@ Accept wildcard characters: False
 The RequireTLS parameter specifies whether to require TLS transmission for inbound messages on the Receive connector. Valid values are:
 
 - $true: Inbound messages on the Receive connector require TLS transmission.
-- $false: Inbound messages on the Receive connector don't require TLS transmission. This is the default value.
+- $false: Inbound messages on the Receive connector don't require TLS transmission. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -1736,7 +1736,7 @@ Accept wildcard characters: False
 
 The SizeEnabled parameter specifies how the SIZE Extended SMTP extension is used on the Receive connector. Valid values are:
 
-- Enabled: SIZE is enabled and is advertised in the EHLO response along with the value of the MaxMessageSize parameter. If the size of the inbound message exceeds the specified value, the Receive connector closes the connection with an error code. This is the default value.
+- Enabled: SIZE is enabled and is advertised in the EHLO response along with the value of the MaxMessageSize parameter. If the size of the inbound message exceeds the specified value, the Receive connector closes the connection with an error code. This value is the default.
 - Disabled: SIZE is disabled and isn't advertised in the EHLO response.
 - EnabledwithoutValue: SIZE is enabled and is advertised in the EHLO response, but the value of the MaxMessageSize parameter isn't disclosed in the EHLO response. This setting allows messages to bypass message size checks for authenticated connections between Mailbox servers.
 
@@ -1761,7 +1761,7 @@ Accept wildcard characters: False
 The SuppressXAnonymousTls parameter specifies whether the X-ANONYMOUSTLS Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are:
 
 - $true: X-ANONYMOUSTLS is disabled and isn't advertised in the EHLO response. This setting also requires that you set the UseDownGradedExchangeServerAuth parameter to the value $true on the Set-TransportService cmdlet on the server.
-- $false: X-ANONYMOUSTLS is enabled and is advertised in the EHLO response. This is the default value.
+- $false: X-ANONYMOUSTLS is enabled and is advertised in the EHLO response. This value is the default.
 
 The X-ANONYMOUSTLS extension is important when the AuthMechanism parameter contains the value ExchangeServer.
 
@@ -1781,7 +1781,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-The TarpitInterval parameter specifies the amount of time to delay an SMTP response to a remote server that may be abusing the connection. The default value is 00:00:05 (5 seconds.).
+The TarpitInterval parameter specifies the amount of time to delay an SMTP response to a remote server that might be abusing the connection. The default value is 00:00:05 (5 seconds).
 
 To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-RemoteDomain.md b/exchange/exchange-ps/ExchangePowerShell/New-RemoteDomain.md
index 23e939498a..2b47aa2592 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-RemoteDomain.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-RemoteDomain.md
@@ -13,7 +13,7 @@ title: New-RemoteDomain
 # New-RemoteDomain
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the New-RemoteDomain cmdlet to create a managed connection for a remote domain. When you create a remote domain, you can control mail flow with more precision, apply message formatting and messaging policies and specify acceptable character sets for messages sent to and received from the remote domain.
 
@@ -30,7 +30,7 @@ New-RemoteDomain [-Name] <String> -DomainName <SmtpDomainWithSubdomains>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-RemoteMailbox.md b/exchange/exchange-ps/ExchangePowerShell/New-RemoteMailbox.md
index f82e91d586..ad9e5e75d8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-RemoteMailbox.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-RemoteMailbox.md
@@ -158,7 +158,7 @@ Directory synchronization must be configured correctly for a mailbox to be creat
 
 The policies that you apply to recipients in the on-premises Exchange organization, such as Unified Messaging or compliance policies, aren't applied to mailboxes in the service. You must configure policies in the service if you want policies to be applied to recipients in the service.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -169,7 +169,7 @@ $Credentials = Get-Credential
 New-RemoteMailbox -Name "Kim Akers" -Password $Credentials.Password -UserPrincipalName kim@corp.contoso.com
 ```
 
-This example creates an on-premises mail user and its associated mailbox in the service. The remote routing address doesn't need to be specified because mail flow between the on-premises organization and the service has been configured. Using this configuration, the New-RemoteMailbox cmdlet automatically calculates the SMTP address of the mailbox to be used with the RemoteRoutingAddress parameter. This example also assumes directory synchronization has been configured.
+This example creates an on-premises mail user and its associated mailbox in the service. The remote routing address doesn't need to be specified because mail flow between the on-premises organization and the service is configured. Using this configuration, the New-RemoteMailbox cmdlet automatically calculates the SMTP address of the mailbox to be used with the RemoteRoutingAddress parameter. This example also assumes directory synchronization is configured.
 
 The first command stores the password to use with the new remote mailbox in a variable by using the Get-Credential cmdlet. The last command creates the mail user.
 
@@ -577,7 +577,7 @@ Accept wildcard characters: False
 The ModerationEnabled parameter specifies whether moderation is enabled for this recipient. Valid value are:
 
 - $true: Moderation is enabled for this recipient. Messages sent to this recipient must be approved by a moderator before the messages are delivered.
-- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This is the default value.
+- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This value is the default.
 
 You use the ModeratedBy parameter to specify the moderators.
 
@@ -644,7 +644,7 @@ Accept wildcard characters: False
 
 The RemotePowerShellEnabled parameter specifies whether the user has access to Exchange PowerShell. Valid values are:
 
-- $true: The user has access to Exchange Online PowerShell, the Exchange Management Shell, and the Exchange admin center (EAC). This is the default value.
+- $true: The user has access to Exchange Online PowerShell, the Exchange Management Shell, and the Exchange admin center (EAC). This value is the default.
 - $false: The user has doesn't have access to Exchange Online PowerShell, the Exchange Management Shell, or the EAC.
 
 Access to Exchange PowerShell is required even if you're trying to open the Exchange Management Shell or the EAC on the local Exchange server.
@@ -690,7 +690,7 @@ Accept wildcard characters: False
 The ResetPasswordOnNextLogon parameter specifies whether the user must change their password the next time they log on. Valid values are:
 
 - $true: The user is required to change their password the next time they log on.
-- $false: The user isn't required to change their password the next time they log on. This is the default value.
+- $false: The user isn't required to change their password the next time they log on. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -708,7 +708,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-The SamAccountName parameter (also known as the pre-Windows 2000 user account or group name) specifies an object identifier that's compatible with older versions of Microsoft Windows client and server operating systems. The value can contain letters, numbers, spaces, periods (.), and the following characters: !, #, $, %, ^, &, -, \_, {, }, and ~. The last character can't be a period. Unicode characters are allowed, but accented characters may generate collisions (for example, o and ö match). The maximum length is 20 characters.
+The SamAccountName parameter (also known as the pre-Windows 2000 user account or group name) specifies an object identifier that's compatible with older versions of Microsoft Windows client and server operating systems. The value can contain letters, numbers, spaces, periods (.), and the following characters: !, #, $, %, ^, &, -, \_, {, }, and ~. The last character can't be a period. Unicode characters are allowed, but accented characters might generate collisions (for example, o and ö match). The maximum length is 20 characters.
 
 ```yaml
 Type: String
@@ -728,7 +728,7 @@ Accept wildcard characters: False
 
 The SendModerationNotifications parameter specifies when moderation notification messages are sent. Valid values are:
 
-- Always: Notify all senders when their messages aren't approved. This is the default value.
+- Always: Notify all senders when their messages aren't approved. This value is the default.
 - Internal: Notify senders in the organization when their messages aren't approved.
 - Never: Don't notify anyone when a message isn't approved.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ReportSubmissionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-ReportSubmissionPolicy.md
index b692122c77..ed307ad3f4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-ReportSubmissionPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-ReportSubmissionPolicy.md
@@ -85,7 +85,7 @@ When you set the email address of the reporting mailbox in the Microsoft Defende
 - Microsoft integrated reporting using Microsoft reporting tools in Outlook: The ReportJunkAddresses, ReportNotJunkAddresses, and ReportPhishAddresses parameters.
 - Microsoft integrated reporting using non-Microsoft tools in Outlook: The ThirdPartyReportAddresses parameter.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -151,7 +151,7 @@ This example creates the report submission policy with the following values: rep
 The DisableQuarantineReportingOption parameter allows or prevents users from reporting messages in quarantine. Valid values are:
 
 - $true: Users can't report quarantined messages from quarantine.
-- $false: Users can report quarantined messages from quarantine. This is the default value.
+- $false: Users can report quarantined messages from quarantine. This value is the default.
 
 This parameter is meaningful only reporting in Outlook is enabled as described in the EnableReportToMicrosoft parameter.
 
@@ -210,7 +210,7 @@ Accept wildcard characters: False
 The EnableCustomNotificationSender parameter specifies whether a custom sender email address is used for result messages after an admin reviews and marks the reported messages as junk, not junk, or phishing. Valid values are:
 
 - $true: Use a custom Microsoft 365 sender email address.
-- $false: Use the default sender email address. This is the default value.
+- $false: Use the default sender email address. This value is the default.
 
 You specify the sender email address using the NotificationSenderAddress parameter.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ReportSubmissionRule.md b/exchange/exchange-ps/ExchangePowerShell/New-ReportSubmissionRule.md
index e15468aa90..277ab07e3d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-ReportSubmissionRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-ReportSubmissionRule.md
@@ -48,7 +48,7 @@ When you set the email address of the reporting mailbox in the Microsoft Defende
 
 When you use this cmdlet to set the email address of the reporting mailbox, the corresponding parameters in the *\-ReportSubmissionPolicy cmdlets are not updated.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -142,7 +142,7 @@ Accept wildcard characters: False
 
 The Enabled parameter specifies whether the rule is enabled or disabled. Valid values are:
 
-- $true: The rule is enabled. This is the default value.
+- $true: The rule is enabled. This value is the default.
 - $false: The rule is disabled.
 
 After you create the rule, use the Enable-ReportSubmissionRule and Disable-ReportSubmissionRule cmdlets to enable or disable the rule.
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-RetentionCompliancePolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-RetentionCompliancePolicy.md
index b7d58bc239..bf34b33313 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-RetentionCompliancePolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-RetentionCompliancePolicy.md
@@ -164,7 +164,7 @@ The Applications parameter specifies the target when Microsoft 365 Groups are in
 - `Group:Exchange` for the mailbox that's connected to the Microsoft 365 Group.
 - `Group:SharePoint` for the SharePoint site that's connected to the Microsoft 365 Group.
 - `"Group:Exchange,SharePoint"` for both the mailbox and the SharePoint site that are connected to the Microsoft 365 Group.
-- blank (`$null`): This is the default value, and is functionally equivalent to the value `"Group:Exchange,SharePoint"`.
+- blank (`$null`): This value is the default, and is functionally equivalent to the value `"Group:Exchange,SharePoint"`.
 
 ```yaml
 Type: MultiValuedProperty
@@ -223,7 +223,7 @@ Accept wildcard characters: False
 
 The Enabled parameter specifies whether the policy is enabled or disabled. Valid values are:
 
-- $true: The policy is enabled. This is the default value.
+- $true: The policy is enabled. This value is the default.
 - $false: The policy is disabled.
 
 ```yaml
@@ -523,9 +523,9 @@ Accept wildcard characters: False
 The RestrictiveRetention parameter specifies whether Preservation Lock is enabled for the policy. Valid values are:
 
 - $true: Preservation Lock is enabled for the policy. No one -- including an administrator -- can turn off the policy or make it less restrictive.
-- $false: Preservation Lock isn't enabled for the policy. This is the default value.
+- $false: Preservation Lock isn't enabled for the policy. This value is the default.
 
-After a policy has been locked, no one can turn off or disable it, or remove content from the policy. And it's not possible to modify or delete content that's subject to the policy during the retention period. The only ways that you can modify the retention policy are by adding content to it, or extending its duration. A locked policy can be increased or extended, but it can't be reduced, disabled, or turned off.
+After a policy is locked, no one can turn off or disable it, or remove content from the policy. And it's not possible to modify or delete content that's subject to the policy during the retention period. The only ways that you can modify the retention policy are by adding content to it, or extending its duration. A locked policy can be increased or extended, but it can't be reduced, disabled, or turned off.
 
 Therefore, before you lock a retention policy, it's critical that you understand your organization's compliance requirements, and that you don't lock a policy until you are certain that it's what you need.
 
@@ -550,7 +550,7 @@ Accept wildcard characters: False
 The RetainCloudAttachment parameter specifies that this is a cloud attachment policy. Valid values are:
 
 - $true: The policy is a cloud attachment policy.
-- $false: The policy is not a cloud attachment policy. This is the default value.
+- $false: The policy is not a cloud attachment policy. This value is the default.
 
 For the value $true, you can only use the following location parameters:
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-RetentionComplianceRule.md b/exchange/exchange-ps/ExchangePowerShell/New-RetentionComplianceRule.md
index 70672338c9..5744f9b2f0 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-RetentionComplianceRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-RetentionComplianceRule.md
@@ -75,14 +75,14 @@ To use this cmdlet in Security & Compliance PowerShell, you need to be assigned
 New-RetentionComplianceRule -Name InternalCompanyRule -Policy "Internal Company Policy" -RetentionDuration Unlimited
 ```
 
-This example creates a new case hold rule named InternalCompanyRule and adds it to the existing case hold policy named "Internal Company Policy". Content will be held indefinitely.
+This example creates a new case hold rule named InternalCompanyRule and adds it to the existing case hold policy named "Internal Company Policy". Content is held indefinitely.
 
 ### Example 2
 ```powershell
 New-RetentionComplianceRule -Name SeptOneYear -Policy "Internal Company Policy" -RetentionDuration 365 -RetentionComplianceAction KeepAndDelete -ExpirationDateOption ModificationAgeInDays
 ```
 
-This example creates a new retention rule named SeptOneYear and adds it to the existing retention policy named "Internal Company Policy". Content will be held for one year from the day content was last modified before it is deleted.
+This example creates a new retention rule named SeptOneYear and adds it to the existing retention policy named "Internal Company Policy". Content is held for one year from the day content was last modified before it is deleted.
 
 ## PARAMETERS
 
@@ -285,7 +285,7 @@ Accept wildcard characters: False
 
 > Applicable: Security & Compliance
 
-The ExcludedItemClasses parameter specifies the types of messages to exclude from the rule. You can use this parameter only to exclude items from a hold policy, which excludes the specified item class from being held. Using this parameter won't exclude items from deletion policies. Typically, you use this parameter to exclude voicemail messages, IM conversations, and other Skype for Business Online content from being held by a hold policy. Common Skype for Business values include:
+The ExcludedItemClasses parameter specifies the types of messages to exclude from the rule. You can use this parameter only to exclude items from a hold policy, which excludes the specified item class from being held. Using this parameter doesn't exclude items from deletion policies. Typically, you use this parameter to exclude voicemail messages, IM conversations, and other Skype for Business Online content from being held by a hold policy. Common Skype for Business values include:
 
 - IPM.Note.Microsoft.Conversation
 - IPM.Note.Microsoft.Conversation.Voice
@@ -296,7 +296,7 @@ The ExcludedItemClasses parameter specifies the types of messages to exclude fro
 - IPM.Note.Microsoft.Voicemail.UM
 - IPM.Note.Microsoft.Voicemail.UM.CA
 
-Additionally, you can specify [message classes for Exchange items](https://learn.microsoft.com/office/vba/outlook/concepts/forms/item-types-and-message-classes) and custom or non-Microsoft message classes. Note that the values you specify aren't validated, so the parameter accepts any text value.
+Additionally, you can specify [message classes for Exchange items](https://learn.microsoft.com/office/vba/outlook/concepts/forms/item-types-and-message-classes) and custom or non-Microsoft message classes. The values you specify aren't validated, so the parameter accepts any text value.
 
 You can specify multiple item class values by using the following syntax: `"Value1","Value2",..."ValueN"`.
 
@@ -428,7 +428,7 @@ The RetentionDurationDisplayHint parameter specifies the units that are used to
 - Months
 - Years
 
-For example, if this parameter is set to the value Years, and the RetentionDuration parameter is set to the value 365, the Microsoft Purview compliance portal will display 1 year as the content hold duration.
+For example, if this parameter is set to the value Years, and the RetentionDuration parameter is set to the value 365, the Microsoft Purview compliance portal displays 1 year as the content hold duration.
 
 You can't use this parameter for Teams retention rules.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-RetentionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-RetentionPolicy.md
index 68bc9f02ec..e52f0a2909 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-RetentionPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-RetentionPolicy.md
@@ -13,7 +13,7 @@ title: New-RetentionPolicy
 # New-RetentionPolicy
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the New-RetentionPolicy cmdlet to create a retention policy.
 
@@ -36,7 +36,7 @@ New-RetentionPolicy [-Name] <String>
 ## DESCRIPTION
 Retention policy tags are associated with a retention policy. When a retention policy is applied to a mailbox, tags associated with the policy are available to the mailbox user.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -125,14 +125,14 @@ This parameter is available only in the cloud-based service.
 
 The IsDefault switch specifies that this retention policy is the default retention policy. You don't need to specify a value with this switch.
 
-When you use this switch, you'll get a warning that this retention policy will replace the current default retention policy (the policy where the IsDefault property value is currently True) as the default. By default, the default retention policy is named Default MRM Policy.
+When you use this switch, you get a warning that this retention policy replaces the current default retention policy (the policy where the IsDefault property value is currently True) as the default. By default, the default retention policy is named Default MRM Policy.
 
 **Note**: Changing which retention policy is the default might or might not affect new and existing mailboxes based on the value of the RetentionPolicy parameter on all mailbox plans:
 
 - $null (blank): Changes to which retention policy is the default are continually reflected in new and existing mailboxes.
 - A retention policy is specified: The value of the RetentionPolicy parameter for all mailbox plans should be $null (blank) or match the Exchange retention policy that's configured as default policy for the organization. Otherwise, the experience might be inconsistent when creating new mailboxes, enabling disabled mailboxes, and changing licenses. For more information see [Mailbox plans in Exchange Online](https://learn.microsoft.com/exchange/recipients-in-exchange-online/manage-user-mailboxes/mailbox-plans).
 
-If a mailbox is assigned an Exchange retention policy that's not the default policy, the RetentionPolicy value of the mailbox will be overwritten when changing licenses and will need to be manually reset to the original value.
+If a mailbox is assigned an Exchange retention policy that's not the default policy, the RetentionPolicy value of the mailbox is overwritten when changing licenses. You need to manually reset the RetentionPolicy to the original value.
 
 Changes to the default retention policy that affect existing mailboxes can potentially saturate the network if there are hundreds or thousands of mailboxes that require updates.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-RetentionPolicyTag.md b/exchange/exchange-ps/ExchangePowerShell/New-RetentionPolicyTag.md
index f38d4c2f54..cd0aad232e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-RetentionPolicyTag.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-RetentionPolicyTag.md
@@ -13,7 +13,7 @@ title: New-RetentionPolicyTag
 # New-RetentionPolicyTag
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the New-RetentionPolicyTag cmdlet to create a retention tag.
 
@@ -72,7 +72,7 @@ Retention tags are used to apply message retention settings to folders and items
 
 Retention tags support a display of the tag name and an optional comment in localized languages. Language culture codes from the CultureInfo class are used for this purpose.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -88,7 +88,7 @@ This example creates the retention policy tag Finance-DeletedItems for the Delet
 New-RetentionPolicyTag "Finance-Default" -Type All -RetentionEnabled $true -AgeLimitForRetention 365 -RetentionAction PermanentlyDelete
 ```
 
-This example creates the default policy tag Finance-Default. When applied to a mailbox as part of a retention policy, the tag permanently deletes all items without a retention tag within 365 days. Items of a particular message class such as Voicemail, for which a default tag (a retention tag of type All) exists, aren't impacted.
+This example creates the default policy tag Finance-Default. When applied to a mailbox as part of a retention policy, the tag permanently deletes all items without a retention tag within 365 days. Items of a particular message class such as Voicemail, for which a default tag (a retention tag of type All) exists, aren't affected.
 
 ### Example 3
 ```powershell
@@ -421,7 +421,7 @@ The RetentionAction parameter specifies the action for the retention policy. Val
 - DeleteAndAllowRecovery: Deletes a message and allows recovery from the Recoverable Items folder.
 - MarkAsPastRetentionLimit: Messages are marked as past the retention limit.
 - MoveToArchive: Moves a message to the user's archive mailbox. You can use this action for retention tags of type All, Personal and RecoverableItems.
-- PermanentlyDelete: Permanently deletes a message. A message that has been permanently deleted can't be recovered using the Recoverable Items folder. Permanently deleted messages aren't returned in a Discovery search, unless litigation hold is enabled for the mailbox.
+- PermanentlyDelete: Permanently deletes a message. A message that is permanently deleted can't be recovered using the Recoverable Items folder. Permanently deleted messages aren't returned in a Discovery search, unless litigation hold is enabled for the mailbox.
 
 The MoveToDeletedItems and MoveToFolder actions are available, but don't work. These actions are available for upgrades from messaging records management (MRM) 1.0 (managed folders) to MRM 2.0 (retention policies). MRM 2.0 was introduced in Exchange 2010 Service Pack 1 (SP1).
 
@@ -447,7 +447,7 @@ The RetentionEnabled parameter specifies whether the tag is enabled. When set to
 
 Messages with a disabled tag are still considered tagged, so any tags of the same type as the disabled tag in the user's retention policy aren't applied to such messages.
 
-When you set the RetentionEnabled parameter to $false, the retention period for the tag is shown as Never. Users may apply this tag to items they want to indicate should never be deleted or should never be moved to the archive. Enabling the tag later may result in unintentional deletion or archiving of items. To avoid this situation, if a retention policy is disabled temporarily, it may be advisable to change the name of that tag so that users are discouraged from using it, such as `DISABLED_<Original Name>`.
+When you set the RetentionEnabled parameter to $false, the retention period for the tag is shown as Never. Users might apply this tag to items they want to indicate should never be deleted or should never be moved to the archive. Enabling the tag later might result in unintentional deletion or archiving of items. To avoid this situation, if a retention policy is disabled temporarily, it might be advisable to change the name of that tag so that users are discouraged from using it, such as `DISABLED_<Original Name>`.
 
 ```yaml
 Type: Boolean
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-RoleAssignmentPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-RoleAssignmentPolicy.md
index d3ed1851f8..fcd51b4f49 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-RoleAssignmentPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-RoleAssignmentPolicy.md
@@ -13,7 +13,7 @@ title: New-RoleAssignmentPolicy
 # New-RoleAssignmentPolicy
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the New-RoleAssignmentPolicy cmdlet to create management role assignment policies in your organization.
 
@@ -35,11 +35,11 @@ New-RoleAssignmentPolicy [-Name] <String>
 ## DESCRIPTION
 When you create an assignment policy, you can assign it to users using the New-Mailbox, Set-Mailbox, or Enable-Mailbox cmdlets. If you make the new assignment policy the default assignment policy, it's assigned to all new mailboxes that don't have an explicit assignment policy assigned to them.
 
-You can add management roles to the new assignment policy when you create it, or you can create the assignment policy and add roles later. You must assign at least one management role to the new assignment policy for it to apply permissions to a mailbox. Without any roles assigned to the new assignment policy, users assigned to it won't be able to manage their mailbox configuration. To assign a management role after the assignment policy has been created, use the New-ManagementRoleAssignment cmdlet. For more information, see [Manage role assignment policies](https://learn.microsoft.com/Exchange/permissions/role-assignment-policies).
+You can add management roles to the new assignment policy when you create it, or you can create the assignment policy and add roles later. You must assign at least one management role to the new assignment policy for it to apply permissions to a mailbox. Without any roles assigned to the new assignment policy, users assigned to it can't manage their mailbox configuration. To assign a management role after the assignment policy is created, use the New-ManagementRoleAssignment cmdlet. For more information, see [Manage role assignment policies](https://learn.microsoft.com/Exchange/permissions/role-assignment-policies).
 
 For more information about assignment policies, see [Understanding management role assignment policies](https://learn.microsoft.com/exchange/understanding-management-role-assignment-policies-exchange-2013-help).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-RoleGroup.md b/exchange/exchange-ps/ExchangePowerShell/New-RoleGroup.md
index c73a9903bb..ac057d2934 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-RoleGroup.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-RoleGroup.md
@@ -13,7 +13,7 @@ title: New-RoleGroup
 # New-RoleGroup
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the New-RoleGroup cmdlet to create management role groups.
 
@@ -69,7 +69,7 @@ When you create a role group, you can create the group and add members to it dir
 
 For more information about role groups, see [Understanding management role groups](https://learn.microsoft.com/exchange/understanding-management-role-groups-exchange-2013-help).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -462,7 +462,7 @@ Accept wildcard characters: False
 
 This parameter is available only in on-premises Exchange.
 
-The SamAccountName parameter (also known as the pre-Windows 2000 user account or group name) specifies an object identifier that's compatible with older versions of Microsoft Windows client and server operating systems. The value can contain letters, numbers, spaces, periods (.), and the following characters: !, #, $, %, ^, &, -, \_, {, }, and ~. The last character can't be a period. Unicode characters are allowed, but accented characters may generate collisions (for example, o and ö match). The maximum length is 20 characters.
+The SamAccountName parameter (also known as the pre-Windows 2000 user account or group name) specifies an object identifier that's compatible with older versions of Microsoft Windows client and server operating systems. The value can contain letters, numbers, spaces, periods (.), and the following characters: !, #, $, %, ^, &, -, \_, {, }, and ~. The last character can't be a period. Unicode characters are allowed, but accented characters might generate collisions (for example, o and ö match). The maximum length is 20 characters.
 
 ```yaml
 Type: String
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-RoutingGroupConnector.md b/exchange/exchange-ps/ExchangePowerShell/New-RoutingGroupConnector.md
index 353c3f4107..61483c3359 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-RoutingGroupConnector.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-RoutingGroupConnector.md
@@ -37,7 +37,7 @@ The New-RoutingGroupConnector cmdlet creates a new routing group connector betwe
 
 To create the routing group connector, you must specify the source servers from the originating routing group and the target servers in the destination routing group. The routing group connector is created in the routing group of which the source server is a member. By using the Bidirectional parameter, you can specify whether the connector is used for one-way or two-way mail flow. If you specify a two-way connector, a reciprocal connector is created in the target routing group. The source and target servers must be Exchange 2010 Hub Transport servers or Exchange 2003 bridgehead servers.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-RpcClientAccess.md b/exchange/exchange-ps/ExchangePowerShell/New-RpcClientAccess.md
index 0cfc7ea229..a64f68eb70 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-RpcClientAccess.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-RpcClientAccess.md
@@ -35,7 +35,7 @@ New-RpcClientAccess -Server <ServerIdParameter>
 ## DESCRIPTION
 After you run this command, you must start the Exchange RPC Client Access service on the Exchange Client Access server to enable RPC client access.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-SafeAttachmentPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-SafeAttachmentPolicy.md
index 7830f1bf89..39965ff971 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-SafeAttachmentPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-SafeAttachmentPolicy.md
@@ -43,7 +43,7 @@ New safe attachment policies that you create using this cmdlet aren't applied to
 
 A safe attachment policy can be assigned to only one safe attachment rule.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -54,9 +54,9 @@ New-SafeAttachmentPolicy -Name "Marketing Block Attachments" -Enable $true -Redi
 
 This example creates a new safe attachment policy named Marketing Block Attachments with the following options:
 
-- The action is Block. This is the default value of the Action parameter, so you don't need to specify it.
-- The value $true for the Enable parameter is required so the policy will actually use the default Action parameter value of Block (or any other Action parameter value).
-- Enable redirection for detected malware attachments and send the messages to admin@contoso.com.
+- The action is Block. This value is the default of the Action parameter, so you don't need to specify it.
+- The value $true for the Enable parameter is required so the policy actually uses the default Action parameter value of Block (or any other Action parameter value).
+- Enable redirection for detected malware attachments and send the messages to `admin@contoso.com`.
 - If Safe Attachments scanning isn't available or encounters errors, don't deliver the message as normal. The default value of the ActionOnError parameter is $true, so you don't need to specify it.
 
 ## PARAMETERS
@@ -86,7 +86,7 @@ Accept wildcard characters: False
 The Action parameter specifies the action for the safe attachment policy. Valid values are:
 
 - Allow: Deliver the message if malware is detected in the attachment and track scanning results. This value corresponds to **Monitor** for the **Safe Attachments unknown malware response** property of the policy in the Microsoft Defender portal.
-- Block: Block the email message that contains the malware attachment. This is the default value.
+- Block: Block the email message that contains the malware attachment. This value is the default.
 - DynamicDelivery: Deliver the email message with a placeholder for each email attachment. The placeholder remains until a copy of the attachment is scanned and determined to be safe. For more information, see [Dynamic Delivery in Safe Attachments policies](https://learn.microsoft.com/defender-office-365/safe-attachments-about#dynamic-delivery-in-safe-attachments-policies).
 
 The value of this parameter is meaningful only when the value of the Enable parameter is $true (the default value is $false).
@@ -153,7 +153,7 @@ Accept wildcard characters: False
 The Enable parameter works with the Action parameter to specify the action for the safe attachment policy. Valid values are:
 
 - $true: The Action parameter specifies the action for the Safe Attachment policy.
-- $false: This is the default value. Attachments are not scanned by Safe Attachments, regardless of the value of the Action parameter. This value corresponds to the **Off** selection for the **Safe Attachments unknown malware response** setting of the policy in the Microsoft Defender portal.
+- $false: This value is the default. Attachments are not scanned by Safe Attachments, regardless of the value of the Action parameter. This value corresponds to the **Off** selection for the **Safe Attachments unknown malware response** setting of the policy in the Microsoft Defender portal.
 
 To enable or disable a complete Safe Attachments policy in the Microsoft Defender portal (the combination of the rule and the corresponding associated policy in PowerShell), use the Enable-SafeAttachmentRule or Disable-SafeAttachmentRule cmdlets.
 
@@ -240,7 +240,7 @@ Accept wildcard characters: False
 The Redirect parameter specifies whether to deliver messages to an alternate email address if malware is detected in an attachment. Valid values are:
 
 - $true: Messages that contain malware attachments are delivered to the email address specified by the RedirectAddress parameter. This value is meaningful only when the value of the Action parameter is Allow.
-- $false: Messages that contain malware attachments aren't delivered to another email address. This is the default value.
+- $false: Messages that contain malware attachments aren't delivered to another email address. This value is the default.
 
 ```yaml
 Type: Boolean
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-SafeAttachmentRule.md b/exchange/exchange-ps/ExchangePowerShell/New-SafeAttachmentRule.md
index 31aa541218..2edb57afa5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-SafeAttachmentRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-SafeAttachmentRule.md
@@ -47,7 +47,7 @@ Safe Attachments is a feature in Microsoft Defender for Office 365 that opens em
 > [!IMPORTANT]
 > Different types of recipient conditions use AND logic (the recipient must satisfy **all** specified conditions). Different types of recipient exceptions use OR logic (the recipient must satisfy **any** of the specified exceptions). For more information, see [Safe Attachments policy settings](https://learn.microsoft.com/defender-office-365/safe-attachments-about#safe-attachments-policy-settings).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -153,7 +153,7 @@ Accept wildcard characters: False
 
 The Enabled parameter specifies whether the rule is enabled. Valid values are:
 
-- $true: The rule is enabled. This is the default value.
+- $true: The rule is enabled. This value is the default.
 - $false: The rule is disabled.
 
 In the properties of the rule, the value of this parameter is visible in the State property.
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-SafeLinksPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-SafeLinksPolicy.md
index 0528b6b005..3ab8987a5c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-SafeLinksPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-SafeLinksPolicy.md
@@ -49,7 +49,7 @@ Safe Links is a feature in Microsoft Defender for Office 365 that checks links t
 
 New policies that you create using this cmdlet aren't applied to users and aren't visible in admin centers. You need to use the SafeLinksPolicy parameter on the New-SafeLinksRule or Set-SafeLinksRule cmdlets to associate the policy with a rule.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -62,7 +62,7 @@ This example creates a new Safe Links policy named Marketing Block URL with the
 
 - The policy is enabled.
 - Users aren't allowed to click through to the original URL.
-- User clicks on URLs are tracked. This is the default value of the TrackClicks parameter, so you don't need to specify it.
+- User clicks on URLs are tracked. This value is the default of the TrackClicks parameter, so you don't need to specify it.
 
 ## PARAMETERS
 
@@ -170,7 +170,7 @@ Accept wildcard characters: False
 
 The DeliverMessageAfterScan parameter specifies whether to deliver email messages only after Safe Links scanning is complete. Valid values are:
 
-- $true: Wait until Safe Links scanning is complete before delivering the message. Messages that contain malicious links are not delivered. This is the default value.
+- $true: Wait until Safe Links scanning is complete before delivering the message. Messages that contain malicious links are not delivered. This value is the default.
 - $false: If Safe Links scanning can't complete, deliver the message anyway.
 
 ```yaml
@@ -192,7 +192,7 @@ Accept wildcard characters: False
 The DisableUrlRewrite parameter specifies whether to rewrite (wrap) URLs in email messages. Valid values are:
 
 - $true: URLs in messages are not rewritten, but messages are still scanned by Safe Links prior to delivery. Time of click checks on links are done using the Safe Links API in supported Outlook clients (currently, Outlook for Windows and Outlook for Mac).
-- $false: URLs in messages are rewritten. API checks still occur on unwrapped URLs in supported clients if the user is in a valid Safe Links policy. This is the default value.
+- $false: URLs in messages are rewritten. API checks still occur on unwrapped URLs in supported clients if the user is in a valid Safe Links policy. This value is the default.
 
 In PowerShell, the default value is $false. In new Safe Links policies created in the Microsoft Defender portal, the default value is $true.
 
@@ -238,7 +238,7 @@ Accept wildcard characters: False
 
 The EnableForInternalSenders parameter specifies whether the Safe Links policy is applied to messages sent between internal senders and internal recipients within the same Exchange Online organization. Valid values are:
 
-- $true: The policy is applied to internal and external senders. This is the default value.
+- $true: The policy is applied to internal and external senders. This value is the default.
 - $false: The policy is applied only to external senders.
 
 ```yaml
@@ -260,7 +260,7 @@ Accept wildcard characters: False
 The EnableOrganizationBranding parameter specifies whether your organization's logo is displayed on Safe Links warning and notification pages. Valid values are:
 
 - $true: Organization branding is displayed on Safe Links warning and notification pages. Before you configure this value, you need to follow the instructions in [Customize the Microsoft 365 theme for your organization](https://learn.microsoft.com/microsoft-365/admin/setup/customize-your-organization-theme) to upload your company logo.
-- $false: Organization branding is not displayed on Safe Links warning and notification pages. This is the default value.
+- $false: Organization branding is not displayed on Safe Links warning and notification pages. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -280,7 +280,7 @@ Accept wildcard characters: False
 
 The EnableSafeLinksForEmail parameter specifies whether to enable Safe Links protection for email messages. Valid values are:
 
-- $true: Safe Links is enabled for email. This is the default value. When a user clicks a link in an email, the link is checked by Safe Links. If the link is found to be malicious, a warning page appears in the default web browser.
+- $true: Safe Links is enabled for email. This value is the default. When a user clicks a link in an email, the link is checked by Safe Links. If the link is found to be malicious, a warning page appears in the default web browser.
 - $false: Safe Links isn't enabled for email.
 
 ```yaml
@@ -301,10 +301,10 @@ Accept wildcard characters: False
 
 The EnableSafeLinksForOffice parameter specifies whether to enable Safe Links protection for supported Office desktop, mobile, or web apps. Valid values are:
 
-- $true: Safe Links scanning is enabled in Office apps. This is the default value. When a user opens a file in a supported Office app and clicks a link in the file, the link is checked by Safe Links. If the link is found to be malicious, a warning page appears in the default web browser.
+- $true: Safe Links scanning is enabled in Office apps. This value is the default. When a user opens a file in a supported Office app and clicks a link in the file, the link is checked by Safe Links. If the link is found to be malicious, a warning page appears in the default web browser.
 - $false: Safe Links isn't enabled for Office apps.
 
-Note that this protection applies to links in Office documents, not links in email messages.
+This protection applies to links in Office documents, not links in email messages.
 
 ```yaml
 Type: Boolean
@@ -324,7 +324,7 @@ Accept wildcard characters: False
 
 The EnableSafeLinksForTeams parameter specifies whether Safe Links is enabled for Microsoft Teams. Valid values are:
 
-- $true: Safe Links is enabled for Teams. This is the default value. When a user clicks a link in a Teams conversation, group chat, or from channels, the link is checked by Safe Links. If the link is found to be malicious, a warning page appears in the default web browser.
+- $true: Safe Links is enabled for Teams. This value is the default. When a user clicks a link in a Teams conversation, group chat, or from channels, the link is checked by Safe Links. If the link is found to be malicious, a warning page appears in the default web browser.
 - $false: Safe Links isn't enabled for Teams.
 
 ```yaml
@@ -381,7 +381,7 @@ Accept wildcard characters: False
 
 The ScanUrls parameter specifies whether to enable or disable real-time scanning of clicked links in email messages. Valid values are:
 
-- $true: Real-time scanning of clicked links, including links that point to files, is enabled. This is the default value.
+- $true: Real-time scanning of clicked links, including links that point to files, is enabled. This value is the default.
 - $false: Real-time scanning of clicked links, including links that point to files, is disabled.
 
 ```yaml
@@ -402,7 +402,7 @@ Accept wildcard characters: False
 
 The TrackClicks parameter specifies whether to track user clicks related to Safe Links protection of links. Valid values are:
 
-- $true: User clicks messages are tracked. This is the default value.
+- $true: User clicks messages are tracked. This value is the default.
 - $false: User clicks messages aren't tracked.
 
 ```yaml
@@ -424,7 +424,7 @@ Accept wildcard characters: False
 The UseTranslatedNotificationText specifies whether to use Microsoft Translator to automatically localize the custom notification text that you specified with the CustomNotificationText parameter. Valid values are:
 
 - $true: Translate custom notification text to the user's language.
-- $false: Don't translate custom notification text to the user's language. This is the default value.
+- $false: Don't translate custom notification text to the user's language. This value is the default.
 
 ```yaml
 Type: Boolean
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-SafeLinksRule.md b/exchange/exchange-ps/ExchangePowerShell/New-SafeLinksRule.md
index f0bcda85ea..b097258420 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-SafeLinksRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-SafeLinksRule.md
@@ -45,7 +45,7 @@ Safe Links is a feature in Microsoft Defender for Office 365 that checks links i
 > [!IMPORTANT]
 > Different types of recipient conditions use AND logic (the recipient must satisfy **all** specified conditions). Different types of recipient exceptions use OR logic (the recipient must satisfy **any** of the specified exceptions). For more information, see [Recipient filters in Safe Links policies](https://learn.microsoft.com/defender-office-365/safe-links-about#recipient-filters-in-safe-links-policies).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -176,7 +176,7 @@ Accept wildcard characters: False
 
 The Enabled parameter specifies whether the rule is enabled. Valid values are:
 
-- $true: The rule is enabled. This is the default value.
+- $true: The rule is enabled. This value is the default.
 - $false: The rule is disabled.
 
 In the properties of the rule, the value of this parameter is visible in the State property.
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-SearchDocumentFormat.md b/exchange/exchange-ps/ExchangePowerShell/New-SearchDocumentFormat.md
index bc6b60fcfa..4396c8006d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-SearchDocumentFormat.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-SearchDocumentFormat.md
@@ -31,9 +31,11 @@ New-SearchDocumentFormat [-Identity] <SearchDocumentFormatId> -Extension <String
 ```
 
 ## DESCRIPTION
-After running the New-SearchDocumentFormat cmdlet, your must run the following cmdlet to restart the search service. There will be a brief search outage.
+After running the New-SearchDocumentFormat cmdlet, you must run the following cmdlet to restart the search service. There will be a brief search outage.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+`Restart-Service HostControllerService`
+
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-SecOpsOverridePolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-SecOpsOverridePolicy.md
index 1cdb8d8f17..5c0f20c3ed 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-SecOpsOverridePolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-SecOpsOverridePolicy.md
@@ -33,7 +33,7 @@ New-SecOpsOverridePolicy [-Name] <String> -SentTo <MultiValuedProperty>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -50,7 +50,7 @@ This example creates the SecOps mailbox override policy with the specified setti
 
 > Applicable: Exchange Online
 
-The Name parameter specifies the name for the SecOps mailbox override policy. Regardless of the value you specify, the name will be SecOpsOverridePolicy.
+The Name parameter specifies the name for the SecOps mailbox override policy. Regardless of the value you specify, the name is SecOpsOverridePolicy.
 
 ```yaml
 Type: String
@@ -147,7 +147,7 @@ Accept wildcard characters: False
 
 The Enabled parameter specifies whether the policy is enabled. Valid values are:
 
-- $true: The policy is enabled. This is the default value.
+- $true: The policy is enabled. This value is the default.
 - $false: The policy is disabled.
 
 ```yaml
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-SendConnector.md b/exchange/exchange-ps/ExchangePowerShell/New-SendConnector.md
index 25a2ec45c2..c200e2ff41 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-SendConnector.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-SendConnector.md
@@ -106,7 +106,7 @@ New-SendConnector [-Name] <String>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -161,7 +161,7 @@ Accept wildcard characters: False
 
 The AddressSpaces parameter specifies the domain names to which the Send connector routes mail. The complete syntax for entering each address space is: `AddressSpaceType:AddressSpace;AddressSpaceCost`.
 
-- AddressSpaceType: On an Edge server, the address space type must be SMTP. In the Transport service on a Mailbox server, the address space type may be SMTP, X400, or any other text string. If you omit the address space type, SMTP is assumed.
+- AddressSpaceType: On an Edge server, the address space type must be SMTP. In the Transport service on a Mailbox server, the address space type might be SMTP, X400, or any other text string. If you omit the address space type, SMTP is assumed.
 - AddressSpace: For SMTP address space types, the address space that you enter must be RFC 1035-compliant. For example, \*, \*.com, and \*.contoso.com are permitted, but \*contoso.com is not. For X.400 address space types, the address space that you enter must be RFC 1685-compliant, such as o=MySite;p=MyOrg;a=adatum;c=us. For all other values of address space type, you can enter any text for the address space.
 - AddressSpaceCost: The valid input range for the cost is from 1 through 100. A lower cost indicates a better route. This parameter is optional. If you omit the address space cost, a cost of 1 is assumed. If you enter a non-SMTP address space that contains the semicolon character (;), you must specify the address space cost.
 
@@ -172,7 +172,7 @@ If you specify the address space type or the address space cost, you must enclos
 - "SMTP:contoso.com"
 - contoso.com
 
-You may specify multiple address spaces by separating the address spaces with commas, for example: contoso.com,fabrikam.com. If you specify the address space type or the address space cost, enclose the address space in quotation marks ("), for example: "contoso.com;2","fabrikam.com;3".
+You might specify multiple address spaces by separating the address spaces with commas, for example: contoso.com,fabrikam.com. If you specify the address space type or the address space cost, enclose the address space in quotation marks ("), for example: "contoso.com;2","fabrikam.com;3".
 
 If you specify a non-SMTP address space type on a Send connector configured in the Transport service on a Mailbox server, you must configure the following parameters:
 
@@ -223,7 +223,7 @@ The CloudServicesMailEnabled parameter specifies whether the connector is used f
 
 Valid values are:
 
-- $true: The connector is used for mail flow in hybrid organizations, so cross-premises headers are preserved or promoted in messages that flow through the connector. This is the default value for connectors that are created by the Hybrid Configuration wizard. Certain X-MS-Exchange-Organization-\* headers in outbound messages that are sent from one side of the hybrid organization to the other are converted to X-MS-Exchange-CrossPremises-\* headers and are thereby preserved in messages. X-MS-Exchange-CrossPremises-\* headers in inbound messages that are received on one side of the hybrid organization from the other are promoted to X-MS-Exchange-Organization-\* headers. These promoted headers replace any instances of the same X-MS-Exchange-Organization-\* headers that already exist in messages.
+- $true: The connector is used for mail flow in hybrid organizations, so cross-premises headers are preserved or promoted in messages that flow through the connector. This value is the default for connectors that are created by the Hybrid Configuration wizard. Certain X-MS-Exchange-Organization-\* headers in outbound messages that are sent from one side of the hybrid organization to the other are converted to X-MS-Exchange-CrossPremises-\* headers and are thereby preserved in messages. X-MS-Exchange-CrossPremises-\* headers in inbound messages that are received on one side of the hybrid organization from the other are promoted to X-MS-Exchange-Organization-\* headers. These promoted headers replace any instances of the same X-MS-Exchange-Organization-\* headers that already exist in messages.
 - $false: The connector isn't used for mail flow in hybrid organizations, so any cross-premises headers are removed from messages that flow through the connector.
 
 ```yaml
@@ -305,7 +305,7 @@ Accept wildcard characters: False
 
 The ConnectorType parameter specifies whether the connector is used in hybrid deployments to send messages to Microsoft 365. Valid values are:
 
-- Default: The connector isn't used to send messages to Microsoft 365. This is the default value.
+- Default: The connector isn't used to send messages to Microsoft 365. This value is the default.
 - XPremises: The connector is used to send messages to Microsoft 365.
 
 ```yaml
@@ -698,7 +698,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 Values entered in bytes are rounded up to nearest kilobyte. The valid input range for this parameter is 0 to 2147483647 bytes. To remove the message size limit on a Send connector, enter a value of unlimited.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ServicePrincipal.md b/exchange/exchange-ps/ExchangePowerShell/New-ServicePrincipal.md
index 57d018af70..6189996d80 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-ServicePrincipal.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-ServicePrincipal.md
@@ -36,7 +36,7 @@ Service principals exist in Microsoft Entra ID to define what apps can do, who c
 
 For more information, see [Application and service principal objects in Microsoft Entra ID](https://learn.microsoft.com/entra/identity-platform/app-objects-and-service-principals).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-SettingOverride.md b/exchange/exchange-ps/ExchangePowerShell/New-SettingOverride.md
index 7ed4d11a9f..cbecf3513b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-SettingOverride.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-SettingOverride.md
@@ -38,7 +38,7 @@ New-SettingOverride [-Name] <String> -Component <String> -Parameters <MultiValue
 ## DESCRIPTION
 Setting overrides configure and store Exchange server customizations in Active Directory. The settings can be organization-wide or server-specific, and they persist in Active Directory across Exchange Cumulative Updates (CUs). Exchange customizations in web.config or exe.config XML application configuration files are server-specific, and are lost when you install the next Exchange CU.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-SharingPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-SharingPolicy.md
index 677c2045d7..fd98707686 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-SharingPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-SharingPolicy.md
@@ -13,9 +13,9 @@ title: New-SharingPolicy
 # New-SharingPolicy
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
-Use the New-SharingPolicy cmdlet to create a sharing policy to regulate how users inside your organization can share calendar and contact information with users outside the organization. Users can only share this information after federation has been configured in Exchange. After federation is configured, users can send sharing invitations that comply with a sharing policy to external recipients in other Exchange Server 2010 or later organizations that have federation enabled. A sharing policy needs to get assigned to a mailbox to be effective. If a mailbox doesn't have a specific sharing policy assigned, a default policy enforces the level of sharing permitted for this mailbox.
+Use the New-SharingPolicy cmdlet to create a sharing policy to regulate how users inside your organization can share calendar and contact information with users outside the organization. Users can only share this information after federation is configured in Exchange. After federation is configured, users can send sharing invitations that comply with a sharing policy to external recipients in other Exchange Server 2010 or later organizations that have federation enabled. A sharing policy needs to get assigned to a mailbox to be effective. If a mailbox doesn't have a specific sharing policy assigned, a default policy enforces the level of sharing permitted for this mailbox.
 
 Sharing policies provide user-established, people-to-people sharing of both calendar and contact information with different types of external users. Sharing policies allow users to share both their free/busy and contact information (including the Calendar and Contacts folders) with recipients in other external federated Exchange organizations. For recipients that aren't in an external federated organization or are in non-Exchange organizations, sharing policies allow people-to-people sharing of their calendar information with anonymous users through the use of Internet Calendar Publishing.
 
@@ -34,7 +34,7 @@ New-SharingPolicy [-Name] <String> -Domains <MultiValuedProperty>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -132,7 +132,7 @@ Accept wildcard characters: False
 
 The Default switch specifies that this sharing policy is the default sharing policy for all mailboxes. You don't need to specify a value with this switch.
 
-If no sharing policy has been applied to a mailbox, the default policy is automatically applied. If you want to disable sharing across your organization, you can set the default policy as disabled.
+If no sharing policy is applied to a mailbox, the default policy is automatically applied. If you want to disable sharing across your organization, you can set the default policy as disabled.
 
 ```yaml
 Type: SwitchParameter
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-SiteMailbox.md b/exchange/exchange-ps/ExchangePowerShell/New-SiteMailbox.md
index 6519e1a622..6d87b66bcf 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-SiteMailbox.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-SiteMailbox.md
@@ -38,7 +38,7 @@ New-SiteMailbox [[-DisplayName] <String>] -SharePointUrl <Uri>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-SiteMailboxProvisioningPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-SiteMailboxProvisioningPolicy.md
index 1c8207891f..78730144a7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-SiteMailboxProvisioningPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-SiteMailboxProvisioningPolicy.md
@@ -40,7 +40,7 @@ New-SiteMailboxProvisioningPolicy [-Name] <String>
 ## DESCRIPTION
 Site mailboxes allow access to both Microsoft SharePoint documents and Exchange email using the same client interface. Site mailbox provisioning policies apply settings to new site mailboxes that you create. You can create multiple site mailbox provisioning policies, but only the default policy is followed when users create site mailboxes. The default site mailbox provisioning policy is named Default.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -96,7 +96,7 @@ Accept wildcard characters: False
 The AliasPrefix parameter specifies the custom text prefix to add to the aliases of new site mailboxes. Valid values are:
 
 - A text string that's 8 characters or less. When you specify a text value, the value of the DefaultAliasPrefixEnabled parameter ignored and aliases get the text prefix you specified.
-- The value $null. This is the default value. The results of this value depend on the DefaultAliasPrefixEnabled parameter value. When it's $true, aliases get the default prefix text. When it's $false, aliases don't get any prefix text.
+- The value $null. This value is the default. The results of this value depend on the DefaultAliasPrefixEnabled parameter value. When it's $true, aliases get the default prefix text. When it's $false, aliases don't get any prefix text.
 
 ```yaml
 Type: String
@@ -137,7 +137,7 @@ Accept wildcard characters: False
 
 The DefaultAliasPrefixEnabled parameter specifies whether new site mailboxes have the default prefix text added to the alias. Valid values are:
 
-- $true: Aliases get the default prefix text. This is the default value. In Microsoft 365, the default prefix text is `SMO-` (for example, the alias value `BugBash_2016` becomes `SMO-BugBash_2016`). In on-premises Exchange, the default prefix text is `SM-` (for example, the alias value `BugBash_2016` becomes `SM-BugBash_2016`).
+- $true: Aliases get the default prefix text. This value is the default. In Microsoft 365, the default prefix text is `SMO-` (for example, the alias value `BugBash_2016` becomes `SMO-BugBash_2016`). In on-premises Exchange, the default prefix text is `SM-` (for example, the alias value `BugBash_2016` becomes `SM-BugBash_2016`).
 - $false: Aliases don't get the default prefix text.
 
 The value of this parameter is related to the value of the AliasPrefix parameter. If you specify a text string for AliasPrefix, the DefaultAliasPrefixEnabled value is ignored. Specifying a text value for AliasPrefix automatically sets the value to $false, but even if you set it to $true, the default alias prefix text isn't used.
@@ -206,7 +206,7 @@ A valid value is a number up to 1.999999999 terabytes (2199023254528 bytes) or t
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The IssueWarningQuota value must be less than or equal to the ProhibitSendReceiveQuota value.
 
@@ -237,7 +237,7 @@ When you enter a value, qualify the value with one of the following units:
 - MB (megabytes)
 - GB (gigabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 A valid value is a number up to 1.999999 gigabytes (2147482624 bytes) or the value unlimited. The default value is 36 MB.
 
@@ -267,7 +267,7 @@ A valid value is a number up to 1.999999999 terabytes (2199023254528 bytes) or t
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value must be greater than or equal to the ProhibitSendQuota or IssueWarningQuota values.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-SweepRule.md b/exchange/exchange-ps/ExchangePowerShell/New-SweepRule.md
index 8b8cb8b880..a0e63f4d33 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-SweepRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-SweepRule.md
@@ -13,7 +13,7 @@ title: New-SweepRule
 # New-SweepRule
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the New-SweepRule cmdlet to create Sweep rules in mailboxes. Sweep rules run at regular intervals to help keep your Inbox clean.
 
@@ -40,7 +40,7 @@ New-SweepRule [-Name] <String> -Provider <String>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -184,7 +184,7 @@ Accept wildcard characters: False
 
 The Enabled parameter specifies whether the Sweep rule is enabled or disabled. Valid values are:
 
-- $true: The rule is enabled. This is the default value.
+- $true: The rule is enabled. This value is the default.
 - $false: The rule is disabled.
 
 After you create the rule, you can enable or disable it by using the Enable-SweepRule and Disable-SweepRule cmdlets.
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-SyncMailPublicFolder.md b/exchange/exchange-ps/ExchangePowerShell/New-SyncMailPublicFolder.md
index 41a1745507..8c39847c58 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-SyncMailPublicFolder.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-SyncMailPublicFolder.md
@@ -13,7 +13,7 @@ title: New-SyncMailPublicFolder
 # New-SyncMailPublicFolder
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 The New-SyncMailPublicFolder cmdlet is used by the Import-MailPublicFoldersForMigration.ps1 and Sync-MailPublicFolders.ps1 scripts to create mail-enabled public folder recipient objects in Exchange Online (the scripts synchronize mail-enabled public folder objects from the source on-premises Exchange organization to Exchange Online). Don't use this cmdlet unless you are directed to do so by Microsoft Customer Service and Support or by specific documentation.
 
@@ -63,7 +63,7 @@ New-SyncMailPublicFolder [-Name] <String> [-Alias] <String> -EntryId <String>
 ## DESCRIPTION
 This cmdlet is only used by the Import-MailPublicFoldersForMigration.ps1 and Sync-MailPublicFolders.ps1 scripts. Don't run this cmdlet in the Exchange Management Shell or in Exchange Online PowerShell.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -510,7 +510,7 @@ Accept wildcard characters: False
 The DeliverToMailboxAndForward parameter specifies the message delivery behavior when a forwarding address is specified by the ForwardingAddress parameter. Valid values are:
 
 - $true: Messages are delivered to this mail-enabled public folder and forwarded to the specified recipient or email address.
-- $false: If a forwarding recipient is configured, messages are delivered only to the specified recipient, and messages aren't delivered to this mail-enabled public folder. If no forwarding recipient is configured, messages are delivered only to this mailbox. This is the default value.
+- $false: If a forwarding recipient is configured, messages are delivered only to the specified recipient, and messages aren't delivered to this mail-enabled public folder. If no forwarding recipient is configured, messages are delivered only to this mailbox. This value is the default.
 
 The default value is $false. This parameter is meaningful only if you configure a forwarding recipient by using the ForwardingAddress parameter.
 
@@ -711,7 +711,7 @@ When you enter a value, qualify the value with one of the following units:
 - MB (megabytes)
 - GB (gigabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 A valid value is a number up to 1.999999 gigabytes (2147483647 bytes) or the value unlimited. The default value is unlimited, which indicates the maximum size is imposed elsewhere (for example, organization, server, or connector limits).
 
@@ -742,7 +742,7 @@ When you enter a value, qualify the value with one of the following units:
 - MB (megabytes)
 - GB (gigabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 A valid value is a number up to 1.999999 gigabytes (2147483647 bytes) or the value unlimited. The default value is unlimited, which indicates the maximum size is imposed elsewhere (for example, organization, server, or connector limits).
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-SystemMessage.md b/exchange/exchange-ps/ExchangePowerShell/New-SystemMessage.md
index 66b63211c0..5f57d4f5d4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-SystemMessage.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-SystemMessage.md
@@ -42,7 +42,7 @@ New-SystemMessage -Language <CultureInfo> -QuotaMessageType <QuotaMessageType> -
 ## DESCRIPTION
 NDRs are issued to the senders of email messages that haven't reached their intended recipients. Quota messages are issued to users whose mailboxes or public folders have reached the specific warning, prohibit send, or prohibit receive quotas. Custom NDRs and quota messages replace the default messages that are included with Exchange.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -205,7 +205,7 @@ The following HTML tags are available:
 - `<EM>` and `</EM>` (italic)
 - `<BR>` (line break)
 - `<P>` and `</P>` (paragraph)
-- `<A HREF="url">` and `</A>` (hyperlink). **Note**: You need to use single quotation marks (not double quotation marks) around the complete text string if you use this tag. Otherwise, you'll receive an error (because of the double quotation marks in the tag).
+- `<A HREF="url">` and `</A>` (hyperlink). **Note**: You need to use single quotation marks (not double quotation marks) around the complete text string if you use this tag. Otherwise, you get an error (because of the double quotation marks in the tag).
 
 Use the following escape codes for these special characters:
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-TeamsProtectionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-TeamsProtectionPolicy.md
index bfee67b53a..0968adb205 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-TeamsProtectionPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-TeamsProtectionPolicy.md
@@ -35,7 +35,7 @@ New-TeamsProtectionPolicy [-Name] <String>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -184,7 +184,7 @@ Accept wildcard characters: False
 
 The ZapEnabled parameter specifies whether to enable zero-hour auto purge (ZAP) for malware and high confidence phishing messages in Teams messages. Valid values are:
 
-- $true: ZAP for malware and high confidence phishing messages in Teams is enabled. This is the default value.
+- $true: ZAP for malware and high confidence phishing messages in Teams is enabled. This value is the default.
 - $false: ZAP for malware and high confidence phishing messages in Teams is disabled.
 
 ```yaml
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-TeamsProtectionPolicyRule.md b/exchange/exchange-ps/ExchangePowerShell/New-TeamsProtectionPolicyRule.md
index e9a52ab70d..dae92b700a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-TeamsProtectionPolicyRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-TeamsProtectionPolicyRule.md
@@ -45,7 +45,7 @@ You can use this cmdlet only if the following statements are true:
 > [!IMPORTANT]
 > Different types of recipient exceptions use OR logic (the recipient must satisfy **any** of the specified exceptions). For more information, see [Configure ZAP for Teams protection in Defender for Office 365 Plan 2](https://learn.microsoft.com/defender-office-365/mdo-support-teams-about#configure-zap-for-teams-protection-in-defender-for-office-365-plan-2).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-TenantAllowBlockListItems.md b/exchange/exchange-ps/ExchangePowerShell/New-TenantAllowBlockListItems.md
index 0c72896810..f4de39cad9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-TenantAllowBlockListItems.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-TenantAllowBlockListItems.md
@@ -50,7 +50,7 @@ New-TenantAllowBlockListItems -Entries <String[]> -ListType <ListType> [-NoExpir
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -254,7 +254,7 @@ Accept wildcard characters: False
 The ListSubType parameter specifies the subtype for this entry. Valid values are:
 
 - AdvancedDelivery: Use this value for phishing simulation URLs. For more information, see [Configure the advanced delivery policy for non-Microsoft phishing simulations and email delivery to SecOps mailboxes](https://learn.microsoft.com/defender-office-365/advanced-delivery-policy-configure).
-- Tenant: This is the default value.
+- Tenant: This value is the default.
 
 ```yaml
 Type: ListSubType
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-TenantAllowBlockListSpoofItems.md b/exchange/exchange-ps/ExchangePowerShell/New-TenantAllowBlockListSpoofItems.md
index dcb4b1d95f..049fb245fe 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-TenantAllowBlockListSpoofItems.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-TenantAllowBlockListSpoofItems.md
@@ -31,7 +31,7 @@ New-TenantAllowBlockListSpoofItems [-Identity] <HostedConnectionFilterPolicyIdPa
 ## DESCRIPTION
 This cmdlet adds a spoof pair (the combination of the spoofed user and the sending infrastructure) to the Tenant Allow/Block List.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ThrottlingPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-ThrottlingPolicy.md
index 17b477043c..d98958dff8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-ThrottlingPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-ThrottlingPolicy.md
@@ -178,7 +178,7 @@ By default, there is one default throttling policy named `GlobalThrottlingPolicy
 
 For more information about how to control how resources are consumed by individual users, see [User workload management in Exchange Server](https://learn.microsoft.com/Exchange/server-health/workload-management).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -808,7 +808,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-This parameter isn't used and will be removed.
+This parameter is reserved for internal Microsoft use.
 
 ```yaml
 Type: Unlimited
@@ -880,7 +880,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-The DiscoverySearchTimeoutPeriod parameter specifies the number of minutes that a discovery search will run before it times out.
+The DiscoverySearchTimeoutPeriod parameter specifies the number of minutes that a discovery search runs before it times out.
 
 ```yaml
 Type: Unlimited
@@ -1008,7 +1008,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-The EasMaxInactivityForDeviceCleanup parameter specifies the length of time that a user's device partnerships will remain active. By default, there is no limit to the number of days that a user's device partnerships will remain active. Use this value if you want to minimize the amount of inactive device partnerships in your organization. To use this setting, specify a value in days since the user's last sync time to cause the device partnership to be removed.
+The EasMaxInactivityForDeviceCleanup parameter specifies the length of time that a user's device partnerships remain active. By default, there is no limit to the number of days that a user's device partnerships remain active. Use this value if you want to minimize the amount of inactive device partnerships in your organization. To use this setting, specify a value in days since the user's last sync time to cause the device partnership to be removed.
 
 ```yaml
 Type: Unlimited
@@ -2168,7 +2168,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-The PowerShellMaxCmdletQueueDepth parameter specifies the number of operations allowed to be executed by the user. This value directly affects the behavior of the PowerShellMaxCmdlets and PowerShellMaxConcurrency parameters. For example, the PowerShellMaxConcurrency parameter consumes at least two operations defined by the PowerShellMaxCmdletQueueDepth parameter but additional operations are also consumed per cmdlet execution. The number of operations depends on the cmdlets executed. We recommend that the value for the PowerShellMaxCmdletQueueDepth parameter be at least three times larger than the value of the PowerShellMaxConcurrency parameter. This parameter won't affect Exchange admin center operations or Exchange Web Services operations.
+The PowerShellMaxCmdletQueueDepth parameter specifies the number of operations allowed to be executed by the user. This value directly affects the behavior of the PowerShellMaxCmdlets and PowerShellMaxConcurrency parameters. For example, the PowerShellMaxConcurrency parameter consumes at least two operations defined by the PowerShellMaxCmdletQueueDepth parameter but additional operations are also consumed per cmdlet execution. The number of operations depends on the cmdlets executed. We recommend that the value for the PowerShellMaxCmdletQueueDepth parameter be at least three times larger than the value of the PowerShellMaxConcurrency parameter. This parameter doesn't affect Exchange admin center operations or Exchange Web Services operations.
 
 ```yaml
 Type: UInt32
@@ -2245,7 +2245,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-The PowerShellMaxDestructiveCmdlets parameter specifies the number of destructive cmdlets that can be executed within a specific time period before their execution is stopped. Destructive cmdlets are cmdlets that can make significant changes to user data and configuration settings in your Exchange organization. Throttling these cmdlets may help prevent accidental data loss. The following cmdlets are designated as destructive:
+The PowerShellMaxDestructiveCmdlets parameter specifies the number of destructive cmdlets that can be executed within a specific time period before their execution is stopped. Destructive cmdlets are cmdlets that can make significant changes to user data and configuration settings in your Exchange organization. Throttling these cmdlets might help prevent accidental data loss. The following cmdlets are designated as destructive:
 
 - Disable-Mailbox
 - Move-ActiveMailboxDatabase
@@ -2293,7 +2293,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-The PowerShellMaxOperations parameter specifies the protocol-level operations that are used to send and receive data. If the execution of a cmdlet results in a significant number of operations (for example, if there is a lot of input/output occurring), throttling may occur. The default setting is Unlimited.
+The PowerShellMaxOperations parameter specifies the protocol-level operations that are used to send and receive data. If the execution of a cmdlet results in a significant number of operations (for example, if there is a lot of input/output occurring), throttling might occur. The default setting is Unlimited.
 
 ```yaml
 Type: Unlimited
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-TransportRule.md b/exchange/exchange-ps/ExchangePowerShell/New-TransportRule.md
index 930b4c4913..465d011257 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-TransportRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-TransportRule.md
@@ -13,7 +13,7 @@ title: New-TransportRule
 # New-TransportRule
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the New-TransportRule cmdlet to create transport rules (mail flow rules) in your organization.
 
@@ -211,9 +211,9 @@ New-TransportRule [-Name] <String>
 ## DESCRIPTION
 In on-premises Exchange organizations, rules created on Mailbox servers are stored in Active Directory. All Mailbox servers in the organization have access to the same set of rules. On Edge Transport servers, rules are saved in the local copy of Active Directory Lightweight Directory Services (AD LDS). Rules aren't shared or replicated between Edge Transport servers or between Mailbox servers and Edge Transport servers. Also, some conditions and actions are exclusive to each server role.
 
-The search for words or text patterns in the subject or other header fields in the message occurs after the message has been decoded from the MIME content transfer encoding method that was used to transmit the binary message between SMTP servers in ASCII text. You can't use conditions or exceptions to search for the raw (typically, Base64) encoded values of the subject or other header fields in messages.
+The search for words or text patterns in the subject or other header fields in the message occurs after the message is decoded from the MIME content transfer encoding method that was used to transmit the binary message between SMTP servers in ASCII text. You can't use conditions or exceptions to search for the raw (typically, Base64) encoded values of the subject or other header fields in messages.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -226,7 +226,7 @@ This example creates a rule with the following settings:
 
 - Name: Ethical Wall - Sales and Brokerage Departments
 - Conditions: Messages that are sent between members of the groups named Sales Department and Brokerage Department.
-- Actions: The message is rejected, and the custom rejection text is Messages sent between the Sales and Brokerage departments are strictly prohibited. Note that the default enhanced status code 5.7.1 is used, because we didn't use the RejectMessageEnhancedStatusCode parameter.
+- Actions: The message is rejected, and the custom rejection text is Messages sent between the Sales and Brokerage departments are strictly prohibited. The default enhanced status code 5.7.1 is used, because we didn't use the RejectMessageEnhancedStatusCode parameter.
 - Exceptions: The Subject field contains the phrases Press Release or Corporate Communication or the message was sent by Tony Smith or Pilar Ackerman.
 
 ## PARAMETERS
@@ -253,7 +253,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
 
-The ActivationDate parameter specifies when the rule starts processing messages. The rule won't take any action on messages until the specified date/time.
+The ActivationDate parameter specifies when the rule starts processing messages. The rule doesn't take any action on messages until the specified date/time.
 
 Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
 
@@ -333,7 +333,7 @@ In on-premises Exchange, this condition is available only on Mailbox servers.
 
 The ADComparisonOperator parameter specifies the comparison operator for the ADComparisonAttribute parameter. Valid values are:
 
-- Equal (This is the default value)
+- Equal (default value)
 - NotEqual
 
 ```yaml
@@ -704,7 +704,7 @@ In on-premises Exchange, this action is available only on Mailbox servers.
 
 The ApplyHtmlDisclaimerFallbackAction parameter specifies what to do if the HTML disclaimer can't be applied to a message (for example, encrypted or signed messages where the contents can't be altered). Valid values are:
 
-- Wrap: This is the default value. A new message is created and the original message is added to it as an attachment. The disclaimer text is added to the new message, which is delivered to the recipients.
+- Wrap: This value is the default. A new message is created and the original message is added to it as an attachment. The disclaimer text is added to the new message, which is delivered to the recipients.
 
   If you want other rules to examine and act on the original message (which is now an attachment in the new message), make sure those rules are applied _before_ the disclaimer rule by using a lower priority for the disclaimer rule and higher priority for other rules.
 
@@ -739,7 +739,7 @@ In on-premises Exchange, this action is available only on Mailbox servers.
 
 The ApplyHtmlDisclaimerLocation parameter specifies where to insert the HTML disclaimer text in the body of messages. Valid values are:
 
-- Append: The disclaimer is added to the end of the message body. This is the default value.
+- Append: The disclaimer is added to the end of the message body. This value is the default.
 - Prepend: The disclaimer is inserted at the beginning of the message body.
 
 If you don't use this parameter with the ApplyHtmlDisclaimerText parameter, the default value Append is used.
@@ -1148,9 +1148,9 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
-The embedded images are treated as attachments (for example, messages with a picture in the signature); for this reason, we do not recommend using a very small value since unexpected messages will be blocked.
+The embedded images are treated as attachments (for example, messages with a picture in the signature); for this reason, we do not recommend using a very small value since unexpected messages are blocked.
 
 ```yaml
 Type: ByteQuantifiedSize
@@ -1449,7 +1449,7 @@ Accept wildcard characters: False
 
 The Enabled parameter specifies whether the new rule is created as enabled or disabled. Valid values are:
 
-- $true: The new rule is enabled. This is the default value.
+- $true: The new rule is enabled. This value is the default.
 - $false: The new rule is disabled.
 
 To enable or disable a rule after you create it, use the Enable-TransportRule and Disable-TransportRule cmdlets.
@@ -1530,7 +1530,7 @@ In on-premises Exchange, this exception is available only on Mailbox servers.
 
 The ExceptIfADComparisonOperator parameter specifies the comparison operator for the ExceptIfADComparisonAttribute parameter. Valid values are:
 
-- Equal (This is the default value)
+- Equal (default value)
 - NotEqual
 
 ```yaml
@@ -2072,7 +2072,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 ```yaml
 Type: ByteQuantifiedSize
@@ -2593,7 +2593,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 ```yaml
 Type: ByteQuantifiedSize
@@ -2618,7 +2618,7 @@ In on-premises Exchange, this exception is available only on Mailbox servers.
 The ExceptIfMessageTypeMatches parameter specifies an exception that looks for messages of the specified type. Valid values are:
 
 - OOF: Auto-reply messages configured by the user.
-- AutoForward: Messages automatically forwarded to an alternative recipient. In Exchange Online, if the message has been forwarded using [mailbox forwarding](https://learn.microsoft.com/exchange/recipients-in-exchange-online/manage-user-mailboxes/configure-email-forwarding) (also known as SMTP forwarding), this exception **will not** match during mail flow rule evaluation.
+- AutoForward: Messages automatically forwarded to an alternative recipient. In Exchange Online, if the message is forwarded using [mailbox forwarding](https://learn.microsoft.com/exchange/recipients-in-exchange-online/manage-user-mailboxes/configure-email-forwarding) (also known as SMTP forwarding), this exception **does not** match during mail flow rule evaluation.
 - Encrypted: S/MIME encrypted messages. In thin clients like Outlook on the web, encryption as a message type is currently not supported.
 - Calendaring: Meeting requests and responses.
 - PermissionControlled: Messages that have specific permissions configured using Office 365 Message Encryption (OME), Rights Management, and sensitivity labels (with encryption).
@@ -3300,7 +3300,7 @@ Accept wildcard characters: False
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
-The ExpiryDate parameter specifies when this rule will stop processing messages. The rule won't take any action on messages after the specified date/time.
+The ExpiryDate parameter specifies when this rule stops processing messages. The rule doesn't take any action on messages after the specified date/time.
 
 Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
 
@@ -3706,10 +3706,10 @@ In on-premises Exchange, this action is available only on Mailbox servers.
 The IncidentReportContent parameter specifies the message properties that are included in the incident report. Valid values are:
 
 - Sender: The sender of the message.
-- Recipients: The recipients in the To field of the message. Only the first 10 recipients are displayed in the incident report. If there are more than 10 recipients, the remaining number of recipients will be displayed.
+- Recipients: The recipients in the To field of the message. Only the first 10 recipients are displayed in the incident report. If there are more than 10 recipients, the remaining number of recipients are displayed.
 - Subject: The Subject field of the message.
-- CC: The recipients in the Cc field of the message. Only the first 10 recipients are displayed in the incident report. If there are more than 10 recipients, the remaining number of recipients will be displayed.
-- BCC: The recipients in the Bcc field of the message. Only the first 10 recipients are displayed in the incident report. If there are more than 10 recipients, the remaining number of recipients will be displayed.
+- CC: The recipients in the Cc field of the message. Only the first 10 recipients are displayed in the incident report. If there are more than 10 recipients, the remaining number of recipients are displayed.
+- BCC: The recipients in the Bcc field of the message. Only the first 10 recipients are displayed in the incident report. If there are more than 10 recipients, the remaining number of recipients are displayed.
 - Severity: The audit severity of the rule that was triggered. If the message was processed by more than one rule, the highest severity is displayed.
 - RuleDetections: The list of rules that the message triggered.
 - FalsePositive: The false positive if the sender marked the message as a false positive for a PolicyTip.
@@ -3740,13 +3740,13 @@ Accept wildcard characters: False
 
 This parameter is available only in Exchange Server 2013.
 
-This parameter has been deprecated and is no longer used. Use the IncidentReportContent parameter instead. The value AttachOriginalMail on the IncidentReportContent parameter is equivalent to setting this parameter to the value IncludeOriginalMail.
+This parameter is deprecated and no longer used. Use the IncidentReportContent parameter instead. The value AttachOriginalMail on the IncidentReportContent parameter is equivalent to setting this parameter to the value IncludeOriginalMail.
 
 This parameter specifies an action or part of an action for the rule.
 
 In on-premises Exchange, this action is available only on Mailbox servers.
 
-The IncidentReportOriginalMail parameter specifies whether to include the original message with the incident report. This parameter is used together with the GenerateIncidentReport parameter. Valid values are:
+The IncidentReportOriginalMail parameter specifies whether to include the original message with the incident report. Use this parameter with the GenerateIncidentReport parameter. Valid values are:
 
 - IncludeOriginalMail
 - DoNotIncludeOriginalMail (this is the default value)
@@ -3901,7 +3901,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 ```yaml
 Type: ByteQuantifiedSize
@@ -3926,7 +3926,7 @@ In on-premises Exchange, this condition is available only on Mailbox servers.
 The MessageTypeMatches parameter specifies a condition that looks for messages of the specified type. Valid values are:
 
 - OOF: Auto-reply messages configured by the user.
-- AutoForward: Messages automatically forwarded to an alternative recipient. In Exchange Online, if the message has been forwarded using [mailbox forwarding](https://learn.microsoft.com/exchange/recipients-in-exchange-online/manage-user-mailboxes/configure-email-forwarding) (also known as SMTP forwarding), this condition **will not** match during mail flow rule evaluation.
+- AutoForward: Messages automatically forwarded to an alternative recipient. In Exchange Online, if the message is forwarded using [mailbox forwarding](https://learn.microsoft.com/exchange/recipients-in-exchange-online/manage-user-mailboxes/configure-email-forwarding) (also known as SMTP forwarding), this condition **does not** match during mail flow rule evaluation.
 - Encrypted: S/MIME encrypted messages. In thin clients like Outlook on the web, encryption as a message type is currently not supported.
 - Calendaring: Meeting requests and responses.
 - PermissionControlled: Messages that have specific permissions configured using Office 365 Message Encryption (OME), Rights Management, and sensitivity labels (with encryption).
@@ -3953,9 +3953,9 @@ Accept wildcard characters: False
 
 The Mode parameter specifies how the rule operates. Valid values are:
 
-- Audit: The actions that the rule would have taken are written to the message tracking log, but no action that impacts message delivery is taken on the message. The GenerateIncidentReport action occurs.
-- AuditAndNotify: The actions that the rule would have taken are written to the message tracking log, but no action that impacts message delivery is taken on the message. The GenerateIncidentReport and GenerateNotification actions occur.
-- Enforce: All actions specified in the rule are taken. This is the default value.
+- Audit: The actions that the rule would have taken are written to the message tracking log, but no action that affects message delivery is taken on the message. The GenerateIncidentReport action occurs.
+- AuditAndNotify: The actions that the rule would have taken are written to the message tracking log, but no action that affects message delivery is taken on the message. The GenerateIncidentReport and GenerateNotification actions occur.
+- Enforce: All actions specified in the rule are taken. This value is the default.
 
 ```yaml
 Type: RuleMode
@@ -4051,7 +4051,7 @@ For all values except NotifyOnly, you can specify an enhanced status code and a
 
 If you use this parameter, you also need to specify a condition that looks for sensitive information types in messages by using the MessageContainsDataClassifications parameter.
 
-This action is applicable to messages sent by internal users only. External senders will not receive notifications.
+This action is applicable to messages sent by internal users only. External senders don't receive notifications.
 
 ```yaml
 Type: NotifySenderType
@@ -4311,7 +4311,7 @@ This parameter is available only in the cloud-based service.
 The RecipientAddressType parameter specifies how conditions and exceptions check recipient email addresses. Valid values are:
 
 - Original: The rule checks the original address in the To field of the message.
-- Resolved: The rule checks the recipient's primary SMTP email address without checking any proxy addresses. This is the default value.
+- Resolved: The rule checks the recipient's primary SMTP email address without checking any proxy addresses. This value is the default.
 
 ```yaml
 Type: RecipientAddressType
@@ -4616,7 +4616,7 @@ Accept wildcard characters: False
 
 The RuleErrorAction parameter specifies what to do if rule processing can't be completed on messages. Valid values are:
 
-- Ignore: The message is sent anyway. This is the default value.
+- Ignore: The message is sent anyway. This value is the default.
 - Defer: The message is deferred so the rules engine can attempt to process the message again.
 
 ```yaml
@@ -4638,7 +4638,7 @@ Accept wildcard characters: False
 The RuleSubType parameter specifies the rule type. Valid values are:
 
 - Dlp: The rule is associated with a DLP policy. This value is meaningful only in on-premises Exchange.
-- None: The rule is a regular transport rule. This is the default value.
+- None: The rule is a regular transport rule. This value is the default.
 
 ```yaml
 Type: RuleSubType
@@ -4799,7 +4799,7 @@ Accept wildcard characters: False
 
 The SenderAddressLocation parameter specifies where to look for sender addresses in conditions and exceptions that examine sender email addresses. Valid values are:
 
-- Header: Only examine senders in the message headers. For example, in on-premises Exchange the From, Sender, or Reply-To fields. In Exchange Online, the From field only. This is the default value, and is the way rules worked before Exchange 2013 Cumulative Update 1 (CU1).
+- Header: Only examine senders in the message headers. For example, in on-premises Exchange the From, Sender, or Reply-To fields. In Exchange Online, the From field only. This value is the default, and is the way rules worked before Exchange 2013 Cumulative Update 1 (CU1).
 - Envelope: Only examine senders from the message envelope (the MAIL FROM value that was used in the SMTP transmission, which is typically stored in the Return-Path field).
 - HeaderOrEnvelope: Examine senders in the message header and the message envelope.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-UMAutoAttendant.md b/exchange/exchange-ps/ExchangePowerShell/New-UMAutoAttendant.md
index 1ce66f96fd..dbd81be6da 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-UMAutoAttendant.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-UMAutoAttendant.md
@@ -38,7 +38,7 @@ The New-UMAutoAttendant cmdlet creates one or more UM auto attendants. UM auto a
 
 After this task is completed, a UM auto attendant is created.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -191,10 +191,10 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
 
-The Status parameter specifies whether the UM auto attendant being created will be enabled. Valid values are:
+The Status parameter specifies whether the UM auto attendant is enabled. Valid values are:
 
 - Enabled
-- Disabled (This is the default value)
+- Disabled (default value)
 
 ```yaml
 Type: StatusEnum
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-UMCallAnsweringRule.md b/exchange/exchange-ps/ExchangePowerShell/New-UMCallAnsweringRule.md
index b90838c318..4c24b04506 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-UMCallAnsweringRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-UMCallAnsweringRule.md
@@ -54,7 +54,7 @@ You can also specify the following actions:
 
 After this task is completed, the cmdlet sets the parameters and the values specified.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -93,10 +93,10 @@ This example creates the call answering rule MyCallAnsweringRule in the mailbox
 - Sets the priority of the call answering rule to 2.
 - Creates key mappings for the call answering rule.
 
-If the caller reaches the voice mail for the user and the status of the user is set to Busy, the caller can:
+If the caller reaches the voice mail for the user and the status of the user is set to Busy, the caller can take the following actions:
 
-- Press the 1 key and be transferred to a receptionist at extension 45678.
-- Press the 2 key and the Find Me feature will be used for urgent issues and ring extension 23456 first, and then 45671.
+- Press the 1 key to be transferred to a receptionist at extension 45678.
+- Press the 2 key to use the Find Me feature for urgent issues and ring extension 23456 first, and then 45671.
 
 ### Example 5
 ```powershell
@@ -302,7 +302,9 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016
 
-The Priority parameter specifies the order that the call answering rule will be evaluated against other existing call answering rules. Call answering rules are processed in order of increasing priority values. The priority must be unique between all call answering rules in the UM-enabled mailbox. The priority on the call answering rule must be between 1 (highest) and 9 (lowest). The default is 9.
+The Priority parameter specifies a priority value for the rule that determines the order of rule processing. A lower integer value indicates a higher priority, and rules can't have the same priority value.
+
+A valid value is an integer from 1 (highest priority) to 9 (lowest priority). The default value is 9.
 
 ```yaml
 Type: Int32
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-UMDialPlan.md b/exchange/exchange-ps/ExchangePowerShell/New-UMDialPlan.md
index ae5a236e98..ec35aabbf5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-UMDialPlan.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-UMDialPlan.md
@@ -42,7 +42,7 @@ After the new UM dial plan is created, a UM IP gateway and a Mailbox server must
 
 After this task is completed, a new UM dial plan is created.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-UMHuntGroup.md b/exchange/exchange-ps/ExchangePowerShell/New-UMHuntGroup.md
index 01d67f8d5e..db2ed984de 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-UMHuntGroup.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-UMHuntGroup.md
@@ -35,7 +35,7 @@ The New-UMHuntGroup cmdlet creates a UM hunt group in Active Directory. Running
 
 After this task is completed, a new UM hunt group is created.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-UMIPGateway.md b/exchange/exchange-ps/ExchangePowerShell/New-UMIPGateway.md
index 16e27a7fae..f9dca59459 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-UMIPGateway.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-UMIPGateway.md
@@ -36,7 +36,7 @@ A UM IP gateway has organization-wide scope and references a single physical IP
 
 This cmdlet is scheduled to be removed from Exchange Online on December 1, 2019. For more information, see this [blog post](https://techcommunity.microsoft.com/t5/Exchange-Team-Blog/New-date-for-discontinuation-of-support-for-Session-Border/ba-p/607853).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -144,11 +144,11 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016
 
-The IPAddressFamily parameter specifies whether the UM IP gateway will use Internet Protocol version 4 (IPv4), IPv6, or both to communicate. Valid values are:
+The IPAddressFamily parameter specifies the Internet Protocol (IP) version to use. Valid values are:
 
-- IPv4Only: The UM IP gateway will only use IPv4 to communicate. This is the default value.
-- IPv6Only: The UM IP gateway will only use IPv6.
-- Any: IPv6 will be used first, and then if necessary, it will fall back to IPv4.
+- IPv4Only: The UM IP gateway uses only IPv4 to communicate. This value is the default.
+- IPv6Only: The UM IP gateway uses only IPv6.
+- Any: IPv6 is used first. If IPv6 isn't available, IPV4 is used.
 
 ```yaml
 Type: IPAddressFamily
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-UMMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-UMMailboxPolicy.md
index 66e7527fc8..996149bc7e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-UMMailboxPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-UMMailboxPolicy.md
@@ -34,7 +34,7 @@ The New-UMMailboxPolicy cmdlet creates a UM mailbox policy that has organization
 
 After this task is completed, a new UM mailbox policy is created.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-UnifiedAuditLogRetentionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-UnifiedAuditLogRetentionPolicy.md
index cf6d755473..b0062846ba 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-UnifiedAuditLogRetentionPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-UnifiedAuditLogRetentionPolicy.md
@@ -81,7 +81,7 @@ The Priority parameter specifies a priority value for the policy that determines
 
 This parameter is required when you create an audit log retention policy, and you must use a unique priority value.
 
-Any custom audit log retention policy that you create will take precedence over the default audit log retention policy. For more information, see [Manage audit log retention policies](https://learn.microsoft.com/purview/audit-log-retention-policies).
+Any custom audit log retention policy that you create take precedence over the default audit log retention policy. For more information, see [Manage audit log retention policies](https://learn.microsoft.com/purview/audit-log-retention-policies).
 
 ```yaml
 Type: Int32
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-UnifiedGroup.md b/exchange/exchange-ps/ExchangePowerShell/New-UnifiedGroup.md
index 644cb77055..840c3aec79 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-UnifiedGroup.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-UnifiedGroup.md
@@ -127,7 +127,7 @@ New-UnifiedGroup -DlIdentity <DistributionGroupIdParameter>
 ## DESCRIPTION
 Microsoft 365 Groups are group objects that are available across Microsoft 365 services.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -197,7 +197,7 @@ Accept wildcard characters: False
 
 The AccessType parameter specifies the privacy type for the Microsoft 365 Group. Valid values are:
 
-- Public: The group content and conversations are available to everyone, and anyone can join the group without approval from a group owner. This is the default value.
+- Public: The group content and conversations are available to everyone, and anyone can join the group without approval from a group owner. This value is the default.
 - Private: The group content and conversations are available only to members of the group, and joining the group requires approval from a group owner.
 
 You can change the privacy type at any point in the lifecycle of the group.
@@ -229,7 +229,7 @@ The Alias value can contain letters, numbers and the following characters:
 - Periods (.) must be surrounded by other valid characters (for example, `help.desk`).
 - Unicode characters U+00A1 to U+00FF.
 
-If you don't use the Alias parameter when you create a Microsoft 365 Group, the value of the DisplayName parameter is used for the Alias value. Spaces are removed, unsupported characters are converted to question marks (?), and numbers may be added to maintain the uniqueness of the Alias value.
+If you don't use the Alias parameter when you create a Microsoft 365 Group, the value of the DisplayName parameter is used for the Alias value. Spaces are removed, unsupported characters are converted to question marks (?), and numbers might be added to maintain the uniqueness of the Alias value.
 
 When you create a Microsoft 365 Group without using the EmailAddresses parameter, the Alias value is used to generate the primary email address (`alias@domain`). Supported Unicode characters are mapped to best-fit US-ASCII text characters. For example, U+00F6 (ö) is changed to `oe` in the primary email address.
 
@@ -253,8 +253,8 @@ Accept wildcard characters: False
 
 The AlwaysSubscribeMembersToCalendarEvents switch controls the default subscription settings of new members that are added to the Microsoft 365 Group.
 
-- If you use this switch without a value, all future members that are added to the group will have their subscriptions set to ReplyAndEvents.
-- If you use this exact syntax: `-AlwaysSubscribeMembersToCalendarEvents:$false`, all future members that are added to the group will have their subscriptions set to ReplyOnly.
+- If you use this switch without a value, all future members that are added to the group  have their subscriptions set to ReplyAndEvents.
+- If you use this exact syntax: `-AlwaysSubscribeMembersToCalendarEvents:$false`, all future members that are added to the group have their subscriptions set to ReplyOnly.
 
 Group members can change their own subscription settings, which can override your intended use of this switch.
 
@@ -339,7 +339,7 @@ The ConvertClosedDlToPrivateGroup switch specifies whether to migrate the closed
 
 By default, this switch is always applied when migrating closed distribution groups, and is no longer required.
 
-If the distribution group has the value Closed for the MemberDepartRestriction or MemberJoinRestriction parameters, the distribution group will always be migrated to a private Microsoft 365 Group. For open distribution groups, the migrated Microsoft 365 Group is always public, not private.
+If the distribution group has the value Closed for the MemberDepartRestriction or MemberJoinRestriction parameters, the distribution group is always migrated to a private Microsoft 365 Group. For open distribution groups, the migrated Microsoft 365 Group is always public, not private.
 
 You can only use this switch with the DlIdentity parameter.
 
@@ -475,7 +475,7 @@ The HiddenGroupMembershipEnabled switch specifies whether to hide the members of
 
 You can use this setting to help comply with regulations that require you to hide group membership from outsiders (for example, a Microsoft 365 Group that represents students enrolled in a class).
 
-**Note**: You can't change this setting after you create the group. If you create the group with hidden membership, you can't edit the group later to reveal the membership to the group, or vice-versa. In addition, any Microsoft 365 Groups with this setting will not be supported in sensitivity labeling policies.
+**Note**: You can't change this setting after you create the group. If you create the group with hidden membership, you can't edit the group later to reveal the membership to the group, or vice-versa. Also, any Microsoft 365 Groups with hidden group membership aren't supported in sensitivity labeling policies.
 
 ```yaml
 Type: SwitchParameter
@@ -594,7 +594,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online, Exchange Online Protection
 
-This parameter has been deprecated and is no longer used.
+This parameter is deprecated and no longer used.
 
 Previously, if you specified a value for this parameter, a random GUID value was added and used as the Name property value for the Microsoft 365 Group (`Name_<RandomGUID>`). Now, the value of the Name property is populated by the Alias parameter value and the ExternalDirectoryObjectId property value (`<Alias>_<ExternalDirectoryObjectId>`).
 
@@ -736,7 +736,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online, Exchange Online Protection
 
-This parameter has been deprecated and is no longer used.
+This parameter is deprecated and no longer used.
 
 ```yaml
 Type: SwitchParameter
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-WebServicesVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/New-WebServicesVirtualDirectory.md
index 8cf2548106..a3d3fc0bc0 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-WebServicesVirtualDirectory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-WebServicesVirtualDirectory.md
@@ -53,7 +53,7 @@ New-WebServicesVirtualDirectory [-ApplicationRoot <String>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -126,7 +126,7 @@ Accept wildcard characters: False
 
 The BasicAuthentication parameter specifies whether Basic authentication is enabled on the virtual directory. Valid values are:
 
-- $true: Basic authentication is enabled. This is the default value.
+- $true: Basic authentication is enabled. This value is the default.
 - $false: Basic authentication is disabled.
 
 ```yaml
@@ -169,7 +169,7 @@ Accept wildcard characters: False
 The DigestAuthentication parameter specifies whether Digest authentication is enabled on the virtual directory. Valid values are:
 
 - $true: Digest authentication is enabled.
-- $false: Digest authentication is disabled. This is the default value.
+- $false: Digest authentication is disabled. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -211,7 +211,7 @@ The ExtendedProtectionFlags parameter specifies custom settings for Extended Pro
 - AllowDotlessSPN: Required if you want to use Service Principal Name (SPN) values that don't contain FQDNs (for example, HTTP/ContosoMail instead of HTTP/mail.contoso.com). You specify SPNs with the ExtendedProtectionSPNList parameter. This setting makes Extended Protection for Authentication less secure because dotless certificates aren't unique, so it isn't possible to ensure that the client-to-proxy connection was established over a secure channel.
 - NoServiceNameCheck: The SPN list isn't checked to validate a channel binding token. This setting makes Extended Protection for Authentication less secure. We generally don't recommend this setting.
 - Proxy: A proxy server is responsible for terminating the SSL channel. To use this setting, you need to register an SPN by using the ExtendedProtectionSPNList parameter.
-- ProxyCoHosting: HTTP and HTTPS traffic may be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server.
+- ProxyCoHosting: HTTP and HTTPS traffic might be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server.
 
 ```yaml
 Type: MultiValuedProperty
@@ -231,7 +231,7 @@ Accept wildcard characters: False
 
 The ExtendedProtectionSPNList parameter specifies a list of valid Service Principal Names (SPNs) if you're using Extended Protection for Authentication on the virtual directory. Valid values are:
 
-- $null: This is the default value.
+- $null: This value is the default.
 - Single SPN or comma delimited list of valid SPNs: The SPN value format is `Protocol\FQDN`. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter.
 
 ```yaml
@@ -252,8 +252,8 @@ Accept wildcard characters: False
 
 The ExtendedProtectionTokenChecking parameter defines how you want to use Extended Protection for Authentication on the virtual directory. Extended Protection for Authentication isn't enabled by default. Valid values are:
 
-- None: Extended Protection for Authentication isn't be used on the virtual directory. This is the default value.
-- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication will work, but may not be as secure as connections that use Extended Protection for Authentication.
+- None: Extended Protection for Authentication isn't be used on the virtual directory. This value is the default.
+- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication work, but might not be as secure as connections that use Extended Protection for Authentication.
 - Require: Extended Protection for Authentication is used for all connections between clients and the virtual directory. If either the client or server doesn't support it, the connection will fail. If you use this value, you also need to set an SPN value for the ExtendedProtectionSPNList parameter.
 
 **Note**: If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter.
@@ -317,7 +317,7 @@ Accept wildcard characters: False
 The GzipLevel parameter sets the Gzip configuration for the Exchange Web Services virtual directory. Valid values are:
 
 - Off: No compression.
-- Low: Static compression only. This is the default value. This value has the same result as the Off value, because Exchange Web Services content is dynamic.
+- Low: Static compression only. This value is the default. This value has the same result as the Off value, because Exchange Web Services content is dynamic.
 - High: Static and dynamic compression. Content from Exchange Web Services is compressed if clients indicate support for Gzip compression in their requests.
 - Error: Identifies errors in the Gzip compression configuration.
 
@@ -397,7 +397,7 @@ Accept wildcard characters: False
 
 This parameter is available only in Exchange Server 2010.
 
-The MRSProxyMaxConnections parameter specifies the maximum number of simultaneous move sessions that an instance of MRSProxy will accept. This setting accepts values from 0 to unlimited. The default value is 100. For more information about MRSProxy, see [Understanding Move Requests](https://learn.microsoft.com/previous-versions/office/exchange-server-2010/dd298174(v=exchg.141)).
+The MRSProxyMaxConnections parameter specifies the maximum number of simultaneous move sessions that an instance of MRSProxy accepts. This setting accepts values from 0 to unlimited. The default value is 100. For more information about MRSProxy, see [Understanding Move Requests](https://learn.microsoft.com/previous-versions/office/exchange-server-2010/dd298174(v=exchg.141)).
 
 ```yaml
 Type: Unlimited
@@ -417,7 +417,7 @@ Accept wildcard characters: False
 
 The OAuthAuthentication parameter specifies whether OAuth authentication is enabled on the virtual directory. Valid values are:
 
-- $true: OAuth authentication is enabled. This is the default value.
+- $true: OAuth authentication is enabled. This value is the default.
 - $false: OAuth authentication is disabled.
 
 ```yaml
@@ -538,7 +538,7 @@ Accept wildcard characters: False
 
 The WindowsAuthentication parameter specifies whether Integrated Windows authentication is enabled on the virtual directory. Valid values are:
 
-- $true: Integrated Windows authentication is enabled. This is the default value.
+- $true: Integrated Windows authentication is enabled. This value is the default.
 - $false: Integrated Windows authentication is disabled.
 
 ```yaml
@@ -559,7 +559,7 @@ Accept wildcard characters: False
 
 The WSSecurityAuthentication parameter specifies whether WS-Security (Web Services Security) authentication is enabled on the virtual directory. Valid values are:
 
-- $true: WS-Security authentication is enabled. This is the default value.
+- $true: WS-Security authentication is enabled. This value is the default.
 - $false: WS-Security authentication is disabled.
 
 ```yaml
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-X400AuthoritativeDomain.md b/exchange/exchange-ps/ExchangePowerShell/New-X400AuthoritativeDomain.md
index 75b1a7057a..af13148098 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-X400AuthoritativeDomain.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-X400AuthoritativeDomain.md
@@ -65,7 +65,7 @@ organizational unit name
 - Abbreviation: OU1 to OU4
 - Maximum character length: 32
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Preview-QuarantineMessage.md b/exchange/exchange-ps/ExchangePowerShell/Preview-QuarantineMessage.md
index d4ecdb9cff..d111fb6995 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Preview-QuarantineMessage.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Preview-QuarantineMessage.md
@@ -29,7 +29,7 @@ Preview-QuarantineMessage -Identity <QuarantineMessageIdentity>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Redirect-Message.md b/exchange/exchange-ps/ExchangePowerShell/Redirect-Message.md
index 7235d9cac0..4ff9812e91 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Redirect-Message.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Redirect-Message.md
@@ -33,9 +33,9 @@ When a message queue is drained, the active messages in the queues on the source
 
 - Only active messages are drained. Shadow queues aren't drained.
 - Messages in the poison message queue aren't drained.
-- The source server won't accept new messages while the queues are drained.
+- The source server doesn't accept new messages while the queues are drained.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Release-QuarantineMessage.md b/exchange/exchange-ps/ExchangePowerShell/Release-QuarantineMessage.md
index 4e44347bf6..211696a797 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Release-QuarantineMessage.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Release-QuarantineMessage.md
@@ -78,7 +78,7 @@ Release-QuarantineMessage -Identity <QuarantineMessageIdentity>
 ## DESCRIPTION
 Consider the following scenario: john@gmail.com sends a message to faith@contoso.com and john@subsidiary.contoso.com. Gmail bifurcates this message into two copies that are both routed to quarantine as phishing in Microsoft. An admin releases both of these messages to admin@contoso.com. The first released message that reaches the admin mailbox is delivered. The second released message is identified as duplicate delivery and is skipped. Message are identified as duplicates if they have the same message ID and received time.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -228,7 +228,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online, Security & Compliance, Exchange Online Protection
 
-The AllowSender switch specifies that all future messages from the sender won't be quarantined. You don't need to specify a value with this switch.
+The AllowSender switch specifies that all future messages from the sender isn't quarantined. You don't need to specify a value with this switch.
 
 If the message was quarantined because of a transport rule or blocked sender, messages from the sender can still be blocked in the future.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-AcceptedDomain.md b/exchange/exchange-ps/ExchangePowerShell/Remove-AcceptedDomain.md
index 63652b6d44..4d52a5ac4c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-AcceptedDomain.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-AcceptedDomain.md
@@ -30,7 +30,7 @@ Remove-AcceptedDomain [-Identity] <AcceptedDomainIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncDevice.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncDevice.md
index 7e6cbd67b6..53d507564f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncDevice.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncDevice.md
@@ -13,7 +13,7 @@ title: Remove-ActiveSyncDevice
 # Remove-ActiveSyncDevice
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Remove-ActiveSyncDevice cmdlet to remove mobile device partnerships that identify the devices that are configured to synchronize with user mailboxes.
 
@@ -34,7 +34,7 @@ Remove-ActiveSyncDevice [-Identity] <ActiveSyncDeviceIdParameter>
 ## DESCRIPTION
 The Remove-ActiveSyncDevice cmdlet is useful for removing mobile devices that no longer synchronize successfully with the server.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncDeviceAccessRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncDeviceAccessRule.md
index bbd927ed8e..252701126d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncDeviceAccessRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncDeviceAccessRule.md
@@ -13,7 +13,7 @@ title: Remove-ActiveSyncDeviceAccessRule
 # Remove-ActiveSyncDeviceAccessRule
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Remove-ActiveSyncDeviceAccessRule cmdlet to remove any existing device access rule.
 
@@ -32,7 +32,7 @@ Remove-ActiveSyncDeviceAccessRule [-Identity] <ActiveSyncDeviceAccessRuleIdParam
 ## DESCRIPTION
 If you've created device access rules for groups of devices, you can use the Remove-ActiveSyncDeviceAccessRule cmdlet to remove any access rule.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 

From 4c5ae75e36360d42a45d62fb8820696388943684 Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Wed, 6 Aug 2025 09:09:08 -0700
Subject: [PATCH 102/145] Update Get-CsPersonalAttendantSettings.md

---
 .../Get-CsPersonalAttendantSettings.md        | 30 -------------------
 1 file changed, 30 deletions(-)

diff --git a/teams/teams-ps/MicrosoftTeams/Get-CsPersonalAttendantSettings.md b/teams/teams-ps/MicrosoftTeams/Get-CsPersonalAttendantSettings.md
index 732fec719f..a8f4f1147c 100644
--- a/teams/teams-ps/MicrosoftTeams/Get-CsPersonalAttendantSettings.md
+++ b/teams/teams-ps/MicrosoftTeams/Get-CsPersonalAttendantSettings.md
@@ -125,21 +125,6 @@ This example shows that user1@contoso.com has personal attendant enabled. In add
 ```
 Get-CsPersonalAttendantSettings -Identity user1@contoso.com
 ```
-```output
-IsPersonalAttendantEnabled       : True
-DefaultLanguage                  : en-US
-DefaultVoice                     : Female
-CalleeName				         : User1
-DefaultTone				         : Formal
-IsBookingCalendarEnabled         : True
-IsNonContactCallbackEnabled      : True
-IsCallScreeningEnabled           : True
-AllowInboundInternalCalls        : True
-AllowInboundFederatedCalls       : True
-AllowInboundPSTNCalls            : True
-IsAutomaticTranscriptionEnabled  : True
-IsAutomaticRecordingEnabled      : True
-```
 
 This example shows that user1@contoso.com has personal attendant enabled. In addition to previously mentioned capabilities, personal attendant is automatically storing call transcription and recording.
 
@@ -147,21 +132,6 @@ This example shows that user1@contoso.com has personal attendant enabled. In add
 ```
 Get-CsPersonalAttendantSettings -Identity user11@contoso.com
 ```
-```output
-IsPersonalAttendantEnabled       : False
-DefaultLanguage                  : en-US
-DefaultVoice                     : Female
-CalleeName				         : 
-DefaultTone				         : Formal
-IsBookingCalendarEnabled         : False
-IsNonContactCallbackEnabled      : False
-IsCallScreeningEnabled           : True
-AllowInboundInternalCalls        : True
-AllowInboundFederatedCalls       : True
-AllowInboundPSTNCalls            : True
-IsAutomaticTranscriptionEnabled  : True
-IsAutomaticRecordingEnabled      : True
-```
 
 This example shows the default settings for the user that has never changed the personal attendant settings via Microsoft Teams.
 

From 715878a07bff000b3752802e97c1c62d6d309a52 Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Wed, 6 Aug 2025 09:15:55 -0700
Subject: [PATCH 103/145] Update Get-CsPersonalAttendantSettings.md

---
 .../Get-CsPersonalAttendantSettings.md        | 60 -------------------
 1 file changed, 60 deletions(-)

diff --git a/teams/teams-ps/MicrosoftTeams/Get-CsPersonalAttendantSettings.md b/teams/teams-ps/MicrosoftTeams/Get-CsPersonalAttendantSettings.md
index a8f4f1147c..ca795dc70d 100644
--- a/teams/teams-ps/MicrosoftTeams/Get-CsPersonalAttendantSettings.md
+++ b/teams/teams-ps/MicrosoftTeams/Get-CsPersonalAttendantSettings.md
@@ -35,21 +35,6 @@ This cmdlet shows the personal attendant settings for a user.
 ```
 Get-CsPersonalAttendantSettings -Identity user1@contoso.com
 ```
-```output
-IsPersonalAttendantEnabled       : True
-DefaultLanguage                  : en-US
-DefaultVoice                     : Female
-CalleeName				         : User1
-DefaultTone				         : Formal
-IsBookingCalendarEnabled         : False
-IsNonContactCallbackEnabled      : False
-IsCallScreeningEnabled           : False
-AllowInboundInternalCalls        : True
-AllowInboundFederatedCalls       : False
-AllowInboundPSTNCalls            : False
-IsAutomaticTranscriptionEnabled  : False
-IsAutomaticRecordingEnabled      : False
-```
 
 This example shows that user1@contoso.com has personal attendant enabled (personal attendant communicates in English). Personal attendant will refer to its owner as User1. 
 Personal attendant is only enabled for inbound Teams calls from the user's domain. Additional capabilities are turned off.
@@ -58,21 +43,6 @@ Personal attendant is only enabled for inbound Teams calls from the user's domai
 ```
 Get-CsPersonalAttendantSettings -Identity user1@contoso.com
 ```
-```output
-IsPersonalAttendantEnabled       : True
-DefaultLanguage                  : en-US
-DefaultVoice                     : Female
-CalleeName				         : User1
-DefaultTone				         : Formal
-IsBookingCalendarEnabled         : True
-IsNonContactCallbackEnabled      : False
-IsCallScreeningEnabled           : False
-AllowInboundInternalCalls        : True
-AllowInboundFederatedCalls       : False
-AllowInboundPSTNCalls            : False
-IsAutomaticTranscriptionEnabled  : False
-IsAutomaticRecordingEnabled      : False
-```
 
 This example shows that user1@contoso.com has personal attendant enabled. In addition to previously mentioned capabilities, personal attendant is able to access personal bookings calendar, 
 fetch the user's availability and schedule callbacks on behalf of the user. Calendar operations are enabled for all incoming callers. user1 must specify the bookings link in Teams Personal Attendant settings.
@@ -81,21 +51,6 @@ fetch the user's availability and schedule callbacks on behalf of the user. Cale
 ```
 Get-CsPersonalAttendantSettings -Identity user1@contoso.com
 ```
-```output
-IsPersonalAttendantEnabled       : True
-DefaultLanguage                  : en-US
-DefaultVoice                     : Female
-CalleeName				         : User1
-DefaultTone				         : Formal
-IsBookingCalendarEnabled         : True
-IsNonContactCallbackEnabled      : True
-IsCallScreeningEnabled           : False
-AllowInboundInternalCalls        : True
-AllowInboundFederatedCalls       : True
-AllowInboundPSTNCalls            : True
-IsAutomaticTranscriptionEnabled  : False
-IsAutomaticRecordingEnabled      : False
-```
 
 This example shows that user1@contoso.com has personal attendant enabled. In addition to previously mentioned capabilities, personal attendant is enabled for all incoming calls: the user's domain, other domains and PSTN.
 
@@ -103,21 +58,6 @@ This example shows that user1@contoso.com has personal attendant enabled. In add
 ```
 Get-CsPersonalAttendantSettings -Identity user1@contoso.com
 ```
-```output
-IsPersonalAttendantEnabled       : True
-DefaultLanguage                  : en-US
-DefaultVoice                     : Female
-CalleeName				         : User1
-DefaultTone				         : Formal
-IsBookingCalendarEnabled         : True
-IsNonContactCallbackEnabled      : True
-IsCallScreeningEnabled           : True
-AllowInboundInternalCalls        : True
-AllowInboundFederatedCalls       : True
-AllowInboundPSTNCalls            : True
-IsAutomaticTranscriptionEnabled  : False
-IsAutomaticRecordingEnabled      : False
-```
 
 This example shows that user1@contoso.com has personal attendant enabled. In addition to previously mentioned capabilities, personal attendant is enabled to evaluate the call's context and pass the info to the user.
 

From 8ff04ea57b1ba77da75a3fb3449bf15090075f7b Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Wed, 6 Aug 2025 09:19:34 -0700
Subject: [PATCH 104/145] Update Get-CsPersonalAttendantSettings.md

---
 teams/teams-ps/MicrosoftTeams/Get-CsPersonalAttendantSettings.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/teams/teams-ps/MicrosoftTeams/Get-CsPersonalAttendantSettings.md b/teams/teams-ps/MicrosoftTeams/Get-CsPersonalAttendantSettings.md
index ca795dc70d..c74a4875e7 100644
--- a/teams/teams-ps/MicrosoftTeams/Get-CsPersonalAttendantSettings.md
+++ b/teams/teams-ps/MicrosoftTeams/Get-CsPersonalAttendantSettings.md
@@ -86,6 +86,7 @@ Parameter Sets: (All)
 Aliases:
 
 Required: True
+Position: Named
 Default value: None
 Accept pipeline input: False
 Accept wildcard characters: False

From 62bc5dd69ca79faf003a3bfae7c153935ebb326d Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Wed, 6 Aug 2025 09:21:05 -0700
Subject: [PATCH 105/145] Update Set-CsPersonalAttendantSettings.md

---
 .../Set-CsPersonalAttendantSettings.md             | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/teams/teams-ps/MicrosoftTeams/Set-CsPersonalAttendantSettings.md b/teams/teams-ps/MicrosoftTeams/Set-CsPersonalAttendantSettings.md
index 3c45a93930..a9a9293b23 100644
--- a/teams/teams-ps/MicrosoftTeams/Set-CsPersonalAttendantSettings.md
+++ b/teams/teams-ps/MicrosoftTeams/Set-CsPersonalAttendantSettings.md
@@ -112,6 +112,7 @@ Parameter Sets: (All)
 Aliases:
 
 Required: True
+Position: Named
 Default value: None
 Accept pipeline input: False
 Accept wildcard characters: False
@@ -126,6 +127,7 @@ Parameter Sets: (All)
 Aliases:
 
 Required: True
+Position: Named
 Default value: False
 Accept pipeline input: False
 Accept wildcard characters: False
@@ -141,6 +143,7 @@ Parameter Sets: (All)
 Aliases:
 
 Required: True
+Position: Named
 Default value: en-US
 Accept pipeline input: False
 Accept wildcard characters: False
@@ -158,6 +161,7 @@ Parameter Sets: (All)
 Aliases:
 
 Required: False
+Position: Named
 Default value: Female
 Accept pipeline input: False
 Accept wildcard characters: False
@@ -172,6 +176,7 @@ Parameter Sets: (All)
 Aliases:
 
 Required: False
+Position: Named
 Default value: None
 Accept pipeline input: False
 Accept wildcard characters: False
@@ -189,6 +194,7 @@ Parameter Sets: (All)
 Aliases:
 
 Required: False
+Position: Named
 Default value: Formal
 Accept pipeline input: False
 Accept wildcard characters: False
@@ -204,6 +210,7 @@ Parameter Sets: (All)
 Aliases:
 
 Required: True
+Position: Named
 Default value: False
 Accept pipeline input: False
 Accept wildcard characters: False
@@ -221,6 +228,7 @@ Parameter Sets: (All)
 Aliases:
 
 Required: False
+Position: Named
 Default value: False
 Accept pipeline input: False
 Accept wildcard characters: False
@@ -235,6 +243,7 @@ Parameter Sets: (All)
 Aliases:
 
 Required: True
+Position: Named
 Default value: True
 Accept pipeline input: False
 Accept wildcard characters: False
@@ -249,6 +258,7 @@ Parameter Sets: (All)
 Aliases:
 
 Required: True
+Position: Named
 Default value: True
 Accept pipeline input: False
 Accept wildcard characters: False
@@ -263,6 +273,7 @@ Parameter Sets: (All)
 Aliases:
 
 Required: True
+Position: Named
 Default value: True
 Accept pipeline input: False
 Accept wildcard characters: False
@@ -277,6 +288,7 @@ Parameter Sets: (All)
 Aliases:
 
 Required: True
+Position: Named
 Default value: True
 Accept pipeline input: False
 Accept wildcard characters: False
@@ -291,6 +303,7 @@ Parameter Sets: (All)
 Aliases:
 
 Required: True
+Position: Named
 Default value: True
 Accept pipeline input: False
 Accept wildcard characters: False
@@ -305,6 +318,7 @@ Parameter Sets: (All)
 Aliases:
 
 Required: True
+Position: Named
 Default value: True
 Accept pipeline input: False
 Accept wildcard characters: False

From 5f09e4ebe04929a957c0668a38103afe02ff3249 Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Wed, 6 Aug 2025 09:22:49 -0700
Subject: [PATCH 106/145] Update Get-CsPersonalAttendantSettings.md

---
 .../Get-CsPersonalAttendantSettings.md            | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

diff --git a/teams/teams-ps/MicrosoftTeams/Get-CsPersonalAttendantSettings.md b/teams/teams-ps/MicrosoftTeams/Get-CsPersonalAttendantSettings.md
index c74a4875e7..4b6f375a58 100644
--- a/teams/teams-ps/MicrosoftTeams/Get-CsPersonalAttendantSettings.md
+++ b/teams/teams-ps/MicrosoftTeams/Get-CsPersonalAttendantSettings.md
@@ -35,6 +35,21 @@ This cmdlet shows the personal attendant settings for a user.
 ```
 Get-CsPersonalAttendantSettings -Identity user1@contoso.com
 ```
+```output
+IsPersonalAttendantEnabled       : True
+DefaultLanguage                  : en-US
+DefaultVoice                     : Female
+CalleeName				         : User1
+DefaultTone				         : Formal
+IsBookingCalendarEnabled         : False
+IsNonContactCallbackEnabled      : False
+IsCallScreeningEnabled           : False
+AllowInboundInternalCalls        : True
+AllowInboundFederatedCalls       : False
+AllowInboundPSTNCalls            : False
+IsAutomaticTranscriptionEnabled  : False
+IsAutomaticRecordingEnabled      : False
+```
 
 This example shows that user1@contoso.com has personal attendant enabled (personal attendant communicates in English). Personal attendant will refer to its owner as User1. 
 Personal attendant is only enabled for inbound Teams calls from the user's domain. Additional capabilities are turned off.

From 453f1bb45e33cb5769fc2f1ab575cedaf8f6bae7 Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Wed, 6 Aug 2025 09:32:28 -0700
Subject: [PATCH 107/145] Update Get-CsPersonalAttendantSettings.md

---
 .../Get-CsPersonalAttendantSettings.md        | 75 +++++++++++++++++++
 1 file changed, 75 insertions(+)

diff --git a/teams/teams-ps/MicrosoftTeams/Get-CsPersonalAttendantSettings.md b/teams/teams-ps/MicrosoftTeams/Get-CsPersonalAttendantSettings.md
index 4b6f375a58..bd61deb0f6 100644
--- a/teams/teams-ps/MicrosoftTeams/Get-CsPersonalAttendantSettings.md
+++ b/teams/teams-ps/MicrosoftTeams/Get-CsPersonalAttendantSettings.md
@@ -58,6 +58,21 @@ Personal attendant is only enabled for inbound Teams calls from the user's domai
 ```
 Get-CsPersonalAttendantSettings -Identity user1@contoso.com
 ```
+```output
+IsPersonalAttendantEnabled       : True
+DefaultLanguage                  : en-US
+DefaultVoice                     : Female
+CalleeName				         : User1
+DefaultTone				         : Formal
+IsBookingCalendarEnabled         : True
+IsNonContactCallbackEnabled      : False
+IsCallScreeningEnabled           : False
+AllowInboundInternalCalls        : True
+AllowInboundFederatedCalls       : False
+AllowInboundPSTNCalls            : False
+IsAutomaticTranscriptionEnabled  : False
+IsAutomaticRecordingEnabled      : False
+```
 
 This example shows that user1@contoso.com has personal attendant enabled. In addition to previously mentioned capabilities, personal attendant is able to access personal bookings calendar, 
 fetch the user's availability and schedule callbacks on behalf of the user. Calendar operations are enabled for all incoming callers. user1 must specify the bookings link in Teams Personal Attendant settings.
@@ -66,6 +81,21 @@ fetch the user's availability and schedule callbacks on behalf of the user. Cale
 ```
 Get-CsPersonalAttendantSettings -Identity user1@contoso.com
 ```
+```output
+IsPersonalAttendantEnabled       : True
+DefaultLanguage                  : en-US
+DefaultVoice                     : Female
+CalleeName				         : User1
+DefaultTone				         : Formal
+IsBookingCalendarEnabled         : True
+IsNonContactCallbackEnabled      : True
+IsCallScreeningEnabled           : False
+AllowInboundInternalCalls        : True
+AllowInboundFederatedCalls       : True
+AllowInboundPSTNCalls            : True
+IsAutomaticTranscriptionEnabled  : False
+IsAutomaticRecordingEnabled      : False
+```
 
 This example shows that user1@contoso.com has personal attendant enabled. In addition to previously mentioned capabilities, personal attendant is enabled for all incoming calls: the user's domain, other domains and PSTN.
 
@@ -73,6 +103,21 @@ This example shows that user1@contoso.com has personal attendant enabled. In add
 ```
 Get-CsPersonalAttendantSettings -Identity user1@contoso.com
 ```
+```output
+IsPersonalAttendantEnabled       : True
+DefaultLanguage                  : en-US
+DefaultVoice                     : Female
+CalleeName				         : User1
+DefaultTone				         : Formal
+IsBookingCalendarEnabled         : True
+IsNonContactCallbackEnabled      : True
+IsCallScreeningEnabled           : True
+AllowInboundInternalCalls        : True
+AllowInboundFederatedCalls       : True
+AllowInboundPSTNCalls            : True
+IsAutomaticTranscriptionEnabled  : False
+IsAutomaticRecordingEnabled      : False
+```
 
 This example shows that user1@contoso.com has personal attendant enabled. In addition to previously mentioned capabilities, personal attendant is enabled to evaluate the call's context and pass the info to the user.
 
@@ -80,6 +125,21 @@ This example shows that user1@contoso.com has personal attendant enabled. In add
 ```
 Get-CsPersonalAttendantSettings -Identity user1@contoso.com
 ```
+```output
+IsPersonalAttendantEnabled       : True
+DefaultLanguage                  : en-US
+DefaultVoice                     : Female
+CalleeName				         : User1
+DefaultTone				         : Formal
+IsBookingCalendarEnabled         : True
+IsNonContactCallbackEnabled      : True
+IsCallScreeningEnabled           : True
+AllowInboundInternalCalls        : True
+AllowInboundFederatedCalls       : True
+AllowInboundPSTNCalls            : True
+IsAutomaticTranscriptionEnabled  : True
+IsAutomaticRecordingEnabled      : True
+```
 
 This example shows that user1@contoso.com has personal attendant enabled. In addition to previously mentioned capabilities, personal attendant is automatically storing call transcription and recording.
 
@@ -87,6 +147,21 @@ This example shows that user1@contoso.com has personal attendant enabled. In add
 ```
 Get-CsPersonalAttendantSettings -Identity user11@contoso.com
 ```
+```output
+IsPersonalAttendantEnabled       : False
+DefaultLanguage                  : en-US
+DefaultVoice                     : Female
+CalleeName				         : 
+DefaultTone				         : Formal
+IsBookingCalendarEnabled         : False
+IsNonContactCallbackEnabled      : False
+IsCallScreeningEnabled           : True
+AllowInboundInternalCalls        : True
+AllowInboundFederatedCalls       : True
+AllowInboundPSTNCalls            : True
+IsAutomaticTranscriptionEnabled  : True
+IsAutomaticRecordingEnabled      : True
+```
 
 This example shows the default settings for the user that has never changed the personal attendant settings via Microsoft Teams.
 

From 74fee88fd6f4e55350711afc3a7236fb355a505e Mon Sep 17 00:00:00 2001
From: Chris Davis <chris.davis@microsoft.com>
Date: Wed, 6 Aug 2025 09:40:16 -0700
Subject: [PATCH 108/145] Acrolinx 11

---
 .../ExchangePowerShell/Remove-ADPermission.md          |  4 ++--
 .../Remove-ATPProtectionPolicyRule.md                  |  4 ++--
 .../ExchangePowerShell/Remove-ActiveSyncDeviceClass.md |  2 +-
 .../Remove-ActiveSyncMailboxPolicy.md                  |  4 ++--
 .../Remove-ActiveSyncVirtualDirectory.md               |  2 +-
 .../ExchangePowerShell/Remove-AddressBookPolicy.md     |  4 ++--
 .../ExchangePowerShell/Remove-AddressList.md           |  4 ++--
 .../ExchangePowerShell/Remove-AntiPhishPolicy.md       |  2 +-
 .../ExchangePowerShell/Remove-AntiPhishRule.md         |  2 +-
 exchange/exchange-ps/ExchangePowerShell/Remove-App.md  |  6 +++---
 .../Remove-ApplicationAccessPolicy.md                  |  4 ++--
 .../ExchangePowerShell/Remove-AuthRedirect.md          |  2 +-
 .../ExchangePowerShell/Remove-AuthServer.md            |  2 +-
 .../ExchangePowerShell/Remove-AuthenticationPolicy.md  |  4 ++--
 .../Remove-AutodiscoverVirtualDirectory.md             |  2 +-
 .../Remove-AvailabilityAddressSpace.md                 |  4 ++--
 .../ExchangePowerShell/Remove-AvailabilityConfig.md    |  2 +-
 .../Remove-AvailabilityReportOutage.md                 |  2 +-
 .../ExchangePowerShell/Remove-BlockedConnector.md      |  2 +-
 .../ExchangePowerShell/Remove-BlockedSenderAddress.md  |  6 +++---
 .../ExchangePowerShell/Remove-CalendarEvents.md        |  4 ++--
 .../Remove-ClassificationRuleCollection.md             |  4 ++--
 .../ExchangePowerShell/Remove-ClientAccessArray.md     |  2 +-
 .../ExchangePowerShell/Remove-ClientAccessRule.md      |  4 ++--
 .../Remove-ComplianceRetentionEventType.md             |  2 +-
 .../ExchangePowerShell/Remove-ComplianceSearch.md      |  4 ++--
 .../ExchangePowerShell/Remove-ContentFilterPhrase.md   |  2 +-
 .../ExchangePowerShell/Remove-DataClassification.md    |  4 ++--
 .../Remove-DatabaseAvailabilityGroup.md                |  2 +-
 .../Remove-DatabaseAvailabilityGroupNetwork.md         |  2 +-
 .../Remove-DatabaseAvailabilityGroupServer.md          |  4 ++--
 .../Remove-DeliveryAgentConnector.md                   |  2 +-
 .../ExchangePowerShell/Remove-DistributionGroup.md     |  4 ++--
 .../Remove-DistributionGroupMember.md                  |  4 ++--
 .../exchange-ps/ExchangePowerShell/Remove-DlpPolicy.md |  4 ++--
 .../ExchangePowerShell/Remove-DlpPolicyTemplate.md     |  2 +-
 .../Remove-DynamicDistributionGroup.md                 |  4 ++--
 .../Remove-EOPProtectionPolicyRule.md                  |  2 +-
 .../ExchangePowerShell/Remove-EcpVirtualDirectory.md   |  2 +-
 .../ExchangePowerShell/Remove-EdgeSubscription.md      |  4 ++--
 .../ExchangePowerShell/Remove-EmailAddressPolicy.md    |  4 ++--
 .../ExchangePowerShell/Remove-ExchangeCertificate.md   |  2 +-
 .../Remove-ExoPhishSimOverrideRule.md                  |  2 +-
 .../ExchangePowerShell/Remove-ExoSecOpsOverrideRule.md |  2 +-
 .../ExchangePowerShell/Remove-FederatedDomain.md       |  2 +-
 .../ExchangePowerShell/Remove-FederationTrust.md       |  2 +-
 .../ExchangePowerShell/Remove-ForeignConnector.md      |  4 ++--
 .../ExchangePowerShell/Remove-GlobalAddressList.md     |  4 ++--
 .../Remove-GlobalMonitoringOverride.md                 |  4 ++--
 .../ExchangePowerShell/Remove-HoldCompliancePolicy.md  |  2 +-
 .../ExchangePowerShell/Remove-HoldComplianceRule.md    |  2 +-
 .../Remove-HostedContentFilterPolicy.md                |  2 +-
 .../Remove-HostedContentFilterRule.md                  |  2 +-
 .../Remove-HostedOutboundSpamFilterPolicy.md           |  2 +-
 .../Remove-HostedOutboundSpamFilterRule.md             |  2 +-
 .../ExchangePowerShell/Remove-HybridConfiguration.md   |  6 +++---
 .../ExchangePowerShell/Remove-InboundConnector.md      |  2 +-
 .../exchange-ps/ExchangePowerShell/Remove-InboxRule.md |  6 +++---
 .../Remove-IntraOrganizationConnector.md               |  4 ++--
 .../ExchangePowerShell/Remove-JournalRule.md           |  4 ++--
 .../ExchangePowerShell/Remove-MailContact.md           |  4 ++--
 .../exchange-ps/ExchangePowerShell/Remove-MailUser.md  |  4 ++--
 .../exchange-ps/ExchangePowerShell/Remove-Mailbox.md   |  8 ++++----
 .../ExchangePowerShell/Remove-MailboxDatabase.md       |  2 +-
 .../ExchangePowerShell/Remove-MailboxDatabaseCopy.md   |  4 ++--
 .../ExchangePowerShell/Remove-MailboxExportRequest.md  |  2 +-
 .../Remove-MailboxFolderPermission.md                  | 10 +++++-----
 .../ExchangePowerShell/Remove-MailboxIRMAccess.md      |  2 +-
 .../ExchangePowerShell/Remove-MailboxImportRequest.md  |  6 +++---
 .../ExchangePowerShell/Remove-MailboxPermission.md     |  4 ++--
 .../ExchangePowerShell/Remove-MailboxRepairRequest.md  |  4 ++--
 .../ExchangePowerShell/Remove-MailboxRestoreRequest.md |  4 ++--
 .../ExchangePowerShell/Remove-MailboxSearch.md         |  4 ++--
 .../Remove-MailboxUserConfiguration.md                 |  4 ++--
 .../ExchangePowerShell/Remove-MalwareFilterPolicy.md   |  4 ++--
 .../ExchangePowerShell/Remove-MalwareFilterRule.md     |  4 ++--
 .../Remove-ManagedContentSettings.md                   |  2 +-
 .../ExchangePowerShell/Remove-ManagedFolder.md         |  2 +-
 .../Remove-ManagedFolderMailboxPolicy.md               |  4 ++--
 .../ExchangePowerShell/Remove-ManagementRole.md        |  6 +++---
 .../Remove-ManagementRoleAssignment.md                 |  4 ++--
 .../ExchangePowerShell/Remove-ManagementRoleEntry.md   |  4 ++--
 .../ExchangePowerShell/Remove-ManagementScope.md       |  4 ++--
 .../ExchangePowerShell/Remove-MapiVirtualDirectory.md  |  2 +-
 .../exchange-ps/ExchangePowerShell/Remove-Message.md   |  2 +-
 .../ExchangePowerShell/Remove-MessageClassification.md |  4 ++--
 .../ExchangePowerShell/Remove-MigrationBatch.md        |  6 +++---
 .../ExchangePowerShell/Remove-MigrationEndpoint.md     |  4 ++--
 .../ExchangePowerShell/Remove-MigrationUser.md         |  4 ++--
 .../ExchangePowerShell/Remove-MobileDevice.md          |  4 ++--
 .../Remove-MobileDeviceMailboxPolicy.md                |  4 ++--
 .../ExchangePowerShell/Remove-MoveRequest.md           |  4 ++--
 .../ExchangePowerShell/Remove-OMEConfiguration.md      |  2 +-
 .../ExchangePowerShell/Remove-OabVirtualDirectory.md   |  2 +-
 .../ExchangePowerShell/Remove-OfflineAddressBook.md    |  4 ++--
 .../Remove-OnPremisesOrganization.md                   |  4 ++--
 .../Remove-OrganizationRelationship.md                 |  4 ++--
 97 files changed, 166 insertions(+), 166 deletions(-)

diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ADPermission.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ADPermission.md
index ca71f92469..590b14b804 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-ADPermission.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ADPermission.md
@@ -64,9 +64,9 @@ Remove-ADPermission [[-Identity] <ADRawEntryIdParameter>] -Instance <ADAcePresen
 ```
 
 ## DESCRIPTION
-The ADPermission cmdlets can be used to directly modify Active Directory access control lists (ACLs). Although some Microsoft Exchange features may continue to use the ADPermission cmdlets to manage permissions (for example Send and Receive connectors), Exchange 2013 and later versions no longer use customized ACLs to manage administrative permissions. If you want to grant or deny administrative permissions in Exchange 2013 or later, you need to use Role Based Access Control (RBAC). For more information about RBAC, see [Permissions in Exchange Server](https://learn.microsoft.com/Exchange/permissions/permissions).
+The ADPermission cmdlets can be used to directly modify Active Directory access control lists (ACLs). Although some Microsoft Exchange features might continue to use the ADPermission cmdlets to manage permissions (for example Send and Receive connectors), Exchange 2013 and later versions no longer use customized ACLs to manage administrative permissions. If you want to grant or deny administrative permissions in Exchange 2013 or later, you need to use Role Based Access Control (RBAC). For more information about RBAC, see [Permissions in Exchange Server](https://learn.microsoft.com/Exchange/permissions/permissions).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ATPProtectionPolicyRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ATPProtectionPolicyRule.md
index 5da3e07228..5a8ea95946 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-ATPProtectionPolicyRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ATPProtectionPolicyRule.md
@@ -17,7 +17,7 @@ This cmdlet is available only in the cloud-based service.
 
 Use the Remove-ATPProtectionPolicyRule cmdlet to remove rules from Microsoft Defender for Office 365 protections in preset security policies. The rules specify recipient conditions and exceptions for the protection, and also allow you to turn on and turn off the associated preset security policies.
 
-**Note**: Use this cmdlet to remove a rule only if you plan to immediately recreate the rule using the New-ATPProtectionPolicyRule cmdlet. The affected preset security policy won't function without a corresponding rule.
+**Note**: Use this cmdlet to remove a rule only if you plan to immediately recreate the rule using the New-ATPProtectionPolicyRule cmdlet. The affected preset security policy doesn't function without a corresponding rule.
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
@@ -33,7 +33,7 @@ Remove-ATPProtectionPolicyRule [-Identity] <RuleIdParameter>
 ## DESCRIPTION
 For more information about preset security policies in PowerShell, see [Preset security policies in Exchange Online PowerShell](https://learn.microsoft.com/defender-office-365/preset-security-policies#preset-security-policies-in-exchange-online-powershell).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncDeviceClass.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncDeviceClass.md
index a08d9400d8..4cb1c29820 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncDeviceClass.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncDeviceClass.md
@@ -32,7 +32,7 @@ Remove-ActiveSyncDeviceClass [-Identity] <ActiveSyncDeviceClassIdParameter>
 ## DESCRIPTION
 The Remove-ActiveSyncDeviceClass cmdlet cleans up the list of devices that are associated with your organization. Mobile phones and devices that are inactive or have been remote wiped are removed from the list and the Microsoft Exchange ActiveSync process regenerates the list with the current mobile phones and devices.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncMailboxPolicy.md
index 2841e91d45..529397252e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncMailboxPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncMailboxPolicy.md
@@ -13,7 +13,7 @@ title: Remove-ActiveSyncMailboxPolicy
 # Remove-ActiveSyncMailboxPolicy
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Remove-ActiveSyncMailboxPolicy cmdlet to remove mobile device mailbox policies.
 
@@ -35,7 +35,7 @@ Remove-ActiveSyncMailboxPolicy [-Identity] <MailboxPolicyIdParameter>
 ## DESCRIPTION
 A mobile device mailbox policy is a group of settings that specifies how mobile phones connect to Exchange. Exchange supports multiple mobile device mailbox policies. If any users are assigned to the policy when you attempt to remove it, the command fails.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncVirtualDirectory.md
index 5a164c4717..781217db58 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncVirtualDirectory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncVirtualDirectory.md
@@ -32,7 +32,7 @@ Remove-ActiveSyncVirtualDirectory [-Identity] <VirtualDirectoryIdParameter>
 ## DESCRIPTION
 When the Exchange ActiveSync virtual directory is removed from a specified server and website, the virtual directory is also removed from Active Directory.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-AddressBookPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-AddressBookPolicy.md
index d68f6ae1c5..e878164f2d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-AddressBookPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-AddressBookPolicy.md
@@ -13,7 +13,7 @@ title: Remove-AddressBookPolicy
 # Remove-AddressBookPolicy
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Remove-AddressBookPolicy cmdlet to delete an address book policy. You can't remove the address book policy if it's still assigned to a user's mailbox.
 
@@ -36,7 +36,7 @@ You can't delete an address book policy if it's assigned to a user. To determine
 
 `Get-Mailbox -ResultSize unlimited -Filter "AddressBookPolicy -eq '$((Get-AddressBookPolicy "Murchison's Class").DistinguishedName)'"`
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-AddressList.md b/exchange/exchange-ps/ExchangePowerShell/Remove-AddressList.md
index c74e1d44d6..02ce9abe28 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-AddressList.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-AddressList.md
@@ -13,7 +13,7 @@ title: Remove-AddressList
 # Remove-AddressList
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Remove-AddressList cmdlet to remove existing address lists.
 
@@ -38,7 +38,7 @@ You can use the Remove-AddressList cmdlet with the Get-AddressList cmdlet in the
 - Use the Get-AddressList cmdlet to get address list information, and then pipe the output to the Format-List cmdlet to get the GUID, distinguished name (DN), or path and name of an existing address list.
 - Use the Get-AddressList cmdlet to get a specific existing address list, and then pipe the output directly to the Remove-AddressList cmdlet.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-AntiPhishPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-AntiPhishPolicy.md
index 62b3f8de89..4c0519e57b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-AntiPhishPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-AntiPhishPolicy.md
@@ -30,7 +30,7 @@ Remove-AntiPhishPolicy [-Identity] <AntiPhishPolicyIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-AntiPhishRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-AntiPhishRule.md
index 2f16d1e2f0..6977beb97b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-AntiPhishRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-AntiPhishRule.md
@@ -29,7 +29,7 @@ Remove-AntiPhishRule [-Identity] <RuleIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-App.md b/exchange/exchange-ps/ExchangePowerShell/Remove-App.md
index 87256dfcde..1c77501a84 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-App.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-App.md
@@ -13,7 +13,7 @@ title: Remove-App
 # Remove-App
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Remove-App cmdlet to uninstall an app.
 
@@ -34,9 +34,9 @@ Remove-App [-Identity] <AppIdParameter>
 ```
 
 ## DESCRIPTION
-The Remove-App cmdlet requires that the specified app has already been installed (for example, that the app has been installed with the New-App cmdlet. Apps installed by default can't be uninstalled, but they can be disabled.
+The Remove-App cmdlet requires that the specified app has already been installed (for example, that the app is installed with the New-App cmdlet. Apps installed by default can't be uninstalled, but they can be disabled.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ApplicationAccessPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ApplicationAccessPolicy.md
index 9434a09c97..484f3eeee3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-ApplicationAccessPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ApplicationAccessPolicy.md
@@ -15,7 +15,7 @@ title: Remove-ApplicationAccessPolicy
 ## SYNOPSIS
 This cmdlet is available only in the cloud-based service.
 
-Use the Remove-ApplicationAccessPolicy cmdlet to remove application access policies. These changes may take up to 30 minutes to go live.
+Use the Remove-ApplicationAccessPolicy cmdlet to remove application access policies. These changes might take up to 30 minutes to go live.
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
@@ -29,7 +29,7 @@ Remove-ApplicationAccessPolicy [-Identity] <ApplicationAccessPolicyIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-AuthRedirect.md b/exchange/exchange-ps/ExchangePowerShell/Remove-AuthRedirect.md
index 04c48fbf3e..42edc677b5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-AuthRedirect.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-AuthRedirect.md
@@ -30,7 +30,7 @@ Remove-AuthRedirect [-Identity] <AuthRedirectIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-AuthServer.md b/exchange/exchange-ps/ExchangePowerShell/Remove-AuthServer.md
index 95ab8e8b0d..a611561cbd 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-AuthServer.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-AuthServer.md
@@ -30,7 +30,7 @@ Remove-AuthServer [-Identity] <AuthServerIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-AuthenticationPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-AuthenticationPolicy.md
index 1d83ba7551..2a4e144071 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-AuthenticationPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-AuthenticationPolicy.md
@@ -13,7 +13,7 @@ title: Remove-AuthenticationPolicy
 # Remove-AuthenticationPolicy
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Remove-AuthenticationPolicy cmdlet to remove authentication policies from your organization.
 
@@ -31,7 +31,7 @@ Remove-AuthenticationPolicy [-Identity] <AuthPolicyIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-AutodiscoverVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Remove-AutodiscoverVirtualDirectory.md
index f87faad103..32c9ff50f0 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-AutodiscoverVirtualDirectory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-AutodiscoverVirtualDirectory.md
@@ -30,7 +30,7 @@ Remove-AutodiscoverVirtualDirectory [-Identity] <VirtualDirectoryIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-AvailabilityAddressSpace.md b/exchange/exchange-ps/ExchangePowerShell/Remove-AvailabilityAddressSpace.md
index 5f3792e4d4..3f035835bd 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-AvailabilityAddressSpace.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-AvailabilityAddressSpace.md
@@ -13,7 +13,7 @@ title: Remove-AvailabilityAddressSpace
 # Remove-AvailabilityAddressSpace
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Remove-AvailabilityAddressSpace cmdlet to remove existing availability address space objects and the associated credentials that were used to share free/busy data across Exchange organizations.
 
@@ -32,7 +32,7 @@ Remove-AvailabilityAddressSpace [-Identity] <AvailabilityAddressSpaceIdParameter
 ## DESCRIPTION
 In on-premises Exchange organizations, you run the Remove-AvailabilityAddressSpace cmdlet on Exchange servers that have the Client Access server role installed.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-AvailabilityConfig.md b/exchange/exchange-ps/ExchangePowerShell/Remove-AvailabilityConfig.md
index 17980f03fd..f5d7462be5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-AvailabilityConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-AvailabilityConfig.md
@@ -29,7 +29,7 @@ Remove-AvailabilityConfig [[-Identity] <AvailabilityConfigIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-AvailabilityReportOutage.md b/exchange/exchange-ps/ExchangePowerShell/Remove-AvailabilityReportOutage.md
index 66bd5aaed6..24ba21761f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-AvailabilityReportOutage.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-AvailabilityReportOutage.md
@@ -32,7 +32,7 @@ Remove-AvailabilityReportOutage [-SiteName] <String> -ReportDate <ExDateTime>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-BlockedConnector.md b/exchange/exchange-ps/ExchangePowerShell/Remove-BlockedConnector.md
index 35eb04fb6e..b89de490a5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-BlockedConnector.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-BlockedConnector.md
@@ -26,7 +26,7 @@ Remove-BlockedConnector -ConnectorId <Guid> [-Reason <String>] [<CommonParameter
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-BlockedSenderAddress.md b/exchange/exchange-ps/ExchangePowerShell/Remove-BlockedSenderAddress.md
index af83a8c60a..0e9b5b1757 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-BlockedSenderAddress.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-BlockedSenderAddress.md
@@ -15,9 +15,9 @@ title: Remove-BlockedSenderAddress
 ## SYNOPSIS
 This cmdlet is available only in the cloud-based service.
 
-Use the Remove-BlockedSenderAddress cmdlet to unblock users in your Microsoft 365 organization that were impacted by the protection system. These users sent multiple messages that were classified as spam, so they were blocked from sending messages.
+Use the Remove-BlockedSenderAddress cmdlet to unblock users in your Microsoft 365 organization that were affected by the protection system. These users sent multiple messages that were classified as spam, so they were blocked from sending messages.
 
-**Note**: There's a limit to the number of times you can unblock a Microsoft 365 account. If you exceed the unblock limit for a user, you'll receive an error, and you'll need to contact support to unblock the user.
+**Note**: There's a limit to the number of times you can unblock a Microsoft 365 account. If you exceed the unblock limit for a user, you get an error, and you need to contact Microsoft Support to unblock the user.
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
@@ -30,7 +30,7 @@ Remove-BlockedSenderAddress -SenderAddress <SmtpAddress>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-CalendarEvents.md b/exchange/exchange-ps/ExchangePowerShell/Remove-CalendarEvents.md
index 23dd9a41c8..37af6e5b5e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-CalendarEvents.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-CalendarEvents.md
@@ -13,7 +13,7 @@ title: Remove-CalendarEvents
 # Remove-CalendarEvents
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Remove-CalendarEvents cmdlet to cancel future meetings in user or resource mailboxes. Cancelling future meetings removes them from attendee and resource calendars (for example, you're going to remove the mailbox, or the user is going on a leave of absence).
 
@@ -35,7 +35,7 @@ Remove-CalendarEvents [-Identity] <MailboxIdParameter> -QueryWindowInDays <Int32
 ## DESCRIPTION
 This cmdlet cancels meetings in the specified mailbox where the mailbox is the meeting organizer, and the meeting has one or more attendees or resources. It doesn't cancel appointments or meetings without attendees or resources. Because meeting cancellations must be sent out, the mailbox must still be enabled to send mail.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ClassificationRuleCollection.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ClassificationRuleCollection.md
index f408d63a88..67d123a26f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-ClassificationRuleCollection.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ClassificationRuleCollection.md
@@ -13,7 +13,7 @@ title: Remove-ClassificationRuleCollection
 # Remove-ClassificationRuleCollection
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Remove-ClassificationRuleCollection to remove classification rule collections from your organization.
 
@@ -32,7 +32,7 @@ Remove-ClassificationRuleCollection [-Identity] <ClassificationRuleCollectionIdP
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ClientAccessArray.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ClientAccessArray.md
index 8a835d7bb8..5f4132e715 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-ClientAccessArray.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ClientAccessArray.md
@@ -30,7 +30,7 @@ Remove-ClientAccessArray [-Identity] <ClientAccessArrayIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ClientAccessRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ClientAccessRule.md
index 780d8f60b7..81d804fa9c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-ClientAccessRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ClientAccessRule.md
@@ -16,7 +16,7 @@ title: Remove-ClientAccessRule
 > [!NOTE]
 > Beginning in October 2022, client access rules were deprecated for all Exchange Online organizations that weren't using them. Client access rules will be deprecated for all remaining organizations on September 1, 2025. If you choose to turn off client access rules before the deadline, the feature will be disabled in your organization. For more information, see [Update on Client Access Rules Deprecation in Exchange Online](https://techcommunity.microsoft.com/blog/exchange/update-on-client-access-rules-deprecation-in-exchange-online/4354809).
 
-This cmdlet is functional only in Exchange Server 2019 and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is functional only in Exchange Server 2019 and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Remove-ClientAccessRule cmdlet to remove client access rules. Client access rules help you control access to your cloud-based organization based on the properties of the connection.
 
@@ -35,7 +35,7 @@ Remove-ClientAccessRule [-Identity] <ClientAccessRuleIdParameter>
 ## DESCRIPTION
 Client access rules are like mail flow rules (also known as transport rules) for client connections to your organization. You use conditions and exceptions to identify the connections based on their properties, and actions that allow or block the connections.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ComplianceRetentionEventType.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ComplianceRetentionEventType.md
index 3a13bfbf98..22edb5ed6a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-ComplianceRetentionEventType.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ComplianceRetentionEventType.md
@@ -30,7 +30,7 @@ Remove-ComplianceRetentionEventType -Identity <PolicyIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ComplianceSearch.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ComplianceSearch.md
index 882cb412ba..523371b286 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-ComplianceSearch.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ComplianceSearch.md
@@ -13,7 +13,7 @@ title: Remove-ComplianceSearch
 # Remove-ComplianceSearch
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Remove-ComplianceSearch cmdlet to remove compliance searches from Exchange Server 2016 and from the Microsoft Purview compliance portal. The searches must be stopped or completed.
 
@@ -29,7 +29,7 @@ Remove-ComplianceSearch [-Identity] <ComplianceSearchIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 In on-premises Exchange, this cmdlet is available in the Mailbox Search role. By default, this role is assigned only to the Discovery Management role group.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ContentFilterPhrase.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ContentFilterPhrase.md
index 3ae844829d..8598c8c44c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-ContentFilterPhrase.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ContentFilterPhrase.md
@@ -40,7 +40,7 @@ Remove-ContentFilterPhrase [-Phrase <ContentFilterPhraseIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-DataClassification.md b/exchange/exchange-ps/ExchangePowerShell/Remove-DataClassification.md
index 80df1068f7..11847d2a17 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-DataClassification.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-DataClassification.md
@@ -15,7 +15,7 @@ title: Remove-DataClassification
 ## SYNOPSIS
 This cmdlet is functional only in on-premises Exchange.
 
-In Exchange Online, this cmdlet has been replaced by the [Remove-DlpSensitiveInformationType](https://learn.microsoft.com/powershell/module/exchangepowershell/remove-dlpsensitiveinformationtype) cmdlet in Security & Compliance PowerShell.
+In Exchange Online, this cmdlet is replaced by the [Remove-DlpSensitiveInformationType](https://learn.microsoft.com/powershell/module/exchangepowershell/remove-dlpsensitiveinformationtype) cmdlet in Security & Compliance PowerShell.
 
 Use the Remove-DataClassification cmdlet to remove data classification rules that use document fingerprints. You can't use this cmdlet to remove built-in data classification rules.
 
@@ -34,7 +34,7 @@ Remove-DataClassification [-Identity] <DataClassificationIdParameter>
 ## DESCRIPTION
 Classification rule packages are used by data loss prevention (DLP) to detect sensitive content in messages.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-DatabaseAvailabilityGroup.md b/exchange/exchange-ps/ExchangePowerShell/Remove-DatabaseAvailabilityGroup.md
index eee46900a9..d80ad23b93 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-DatabaseAvailabilityGroup.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-DatabaseAvailabilityGroup.md
@@ -30,7 +30,7 @@ Remove-DatabaseAvailabilityGroup [-Identity] <DatabaseAvailabilityGroupIdParamet
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-DatabaseAvailabilityGroupNetwork.md b/exchange/exchange-ps/ExchangePowerShell/Remove-DatabaseAvailabilityGroupNetwork.md
index b27a7b0fbc..398452c4aa 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-DatabaseAvailabilityGroupNetwork.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-DatabaseAvailabilityGroupNetwork.md
@@ -30,7 +30,7 @@ Remove-DatabaseAvailabilityGroupNetwork [-Identity] <DatabaseAvailabilityGroupNe
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-DatabaseAvailabilityGroupServer.md b/exchange/exchange-ps/ExchangePowerShell/Remove-DatabaseAvailabilityGroupServer.md
index a3974b525b..47cfb67982 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-DatabaseAvailabilityGroupServer.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-DatabaseAvailabilityGroupServer.md
@@ -32,7 +32,7 @@ Remove-DatabaseAvailabilityGroupServer [-Identity] <DatabaseAvailabilityGroupIdP
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -101,7 +101,7 @@ The ConfigurationOnly switch remove the Mailbox server from the DAG object in Ac
 
 If the Mailbox server is offline but the DAG has quorum, the Mailbox server is evicted from the DAG's cluster and removed from the DAG object in Active Directory.
 
-You should use this switch only if the Mailbox server has been lost and can no longer be contacted, or in situations when the Mailbox server can't be restored to operational service before the messaging service is needed.
+You should use this switch only if the Mailbox server is lost and can no longer be contacted, or in situations when the Mailbox server can't be restored to operational service before the messaging service is needed.
 
 ```yaml
 Type: SwitchParameter
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-DeliveryAgentConnector.md b/exchange/exchange-ps/ExchangePowerShell/Remove-DeliveryAgentConnector.md
index 3b8f0c168e..f44ef1cb27 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-DeliveryAgentConnector.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-DeliveryAgentConnector.md
@@ -32,7 +32,7 @@ Remove-DeliveryAgentConnector [-Identity] <DeliveryAgentConnectorIdParameter>
 ## DESCRIPTION
 Delivery agent connectors are used to route messages addressed to foreign systems that don't use the SMTP protocol. When a message is routed to a delivery agent connector, the associated delivery agent performs the content conversion and message delivery. Delivery agent connectors allow queue management of foreign connectors, thereby eliminating the need for storing messages on the file system in Drop and Pickup directories. For more information, see [Delivery agents and Delivery Agent connectors](https://learn.microsoft.com/exchange/delivery-agents-and-delivery-agent-connectors-exchange-2013-help).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-DistributionGroup.md b/exchange/exchange-ps/ExchangePowerShell/Remove-DistributionGroup.md
index fe40250ea6..cf0c056d74 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-DistributionGroup.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-DistributionGroup.md
@@ -13,7 +13,7 @@ title: Remove-DistributionGroup
 # Remove-DistributionGroup
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Remove-DistributionGroup cmdlet to remove distribution groups and mail-enabled security groups.
 
@@ -32,7 +32,7 @@ Remove-DistributionGroup [-Identity] <DistributionGroupIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-DistributionGroupMember.md b/exchange/exchange-ps/ExchangePowerShell/Remove-DistributionGroupMember.md
index 9d8ad97a3d..4e4bc7777a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-DistributionGroupMember.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-DistributionGroupMember.md
@@ -13,7 +13,7 @@ title: Remove-DistributionGroupMember
 # Remove-DistributionGroupMember
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Remove-DistributionGroupMember cmdlet to remove a single member from distribution groups or mail-enabled security groups. To replace all members, use the Update-DistributionGroupMember cmdlet.
 
@@ -34,7 +34,7 @@ Remove-DistributionGroupMember [-Identity] <DistributionGroupIdParameter>
 ## DESCRIPTION
 You can't use the Remove-DistributionGroupMember cmdlet to remove the member of a dynamic distribution group. A dynamic distribution group's membership is calculated from query results.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-DlpPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-DlpPolicy.md
index 316c9cd1a2..7f63c45109 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-DlpPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-DlpPolicy.md
@@ -13,7 +13,7 @@ title: Remove-DlpPolicy
 # Remove-DlpPolicy
 
 ## SYNOPSIS
-**Note**: This cmdlet has been retired from the cloud-based service. For more information, see [this blog post](https://techcommunity.microsoft.com/t5/exchange-team-blog/exchange-online-etrs-to-stop-supporting-dlp-policies/ba-p/3886713). Use the Remove-DlpCompliancePolicy and Remove-DlpComplianceRule cmdlets instead.
+**Note**: This cmdlet is retired from the cloud-based service. For more information, see [this blog post](https://techcommunity.microsoft.com/t5/exchange-team-blog/exchange-online-etrs-to-stop-supporting-dlp-policies/ba-p/3886713). Use the Remove-DlpCompliancePolicy and Remove-DlpComplianceRule cmdlets instead.
 
 This cmdlet is functional only in on-premises Exchange.
 
@@ -32,7 +32,7 @@ Remove-DlpPolicy [-Identity] <DlpPolicyIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-DlpPolicyTemplate.md b/exchange/exchange-ps/ExchangePowerShell/Remove-DlpPolicyTemplate.md
index 1a5970540d..bce7076d60 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-DlpPolicyTemplate.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-DlpPolicyTemplate.md
@@ -30,7 +30,7 @@ Remove-DlpPolicyTemplate [[-Identity] <DlpPolicyIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-DynamicDistributionGroup.md b/exchange/exchange-ps/ExchangePowerShell/Remove-DynamicDistributionGroup.md
index 34d08a77f7..2070951572 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-DynamicDistributionGroup.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-DynamicDistributionGroup.md
@@ -13,7 +13,7 @@ title: Remove-DynamicDistributionGroup
 # Remove-DynamicDistributionGroup
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Remove-DynamicDistributionGroup cmdlet to delete dynamic distribution groups.
 
@@ -31,7 +31,7 @@ Remove-DynamicDistributionGroup [-Identity] <DynamicGroupIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-EOPProtectionPolicyRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-EOPProtectionPolicyRule.md
index 3581bd35c2..5c64c8e9df 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-EOPProtectionPolicyRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-EOPProtectionPolicyRule.md
@@ -33,7 +33,7 @@ Remove-EOPProtectionPolicyRule [-Identity] <RuleIdParameter>
 ## DESCRIPTION
 For more information about preset security policies in PowerShell, see [Preset security policies in Exchange Online PowerShell](https://learn.microsoft.com/defender-office-365/preset-security-policies#preset-security-policies-in-exchange-online-powershell).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-EcpVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Remove-EcpVirtualDirectory.md
index 5cecafe529..f38307da67 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-EcpVirtualDirectory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-EcpVirtualDirectory.md
@@ -32,7 +32,7 @@ Remove-EcpVirtualDirectory [-Identity] <VirtualDirectoryIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-EdgeSubscription.md b/exchange/exchange-ps/ExchangePowerShell/Remove-EdgeSubscription.md
index b5b4a410da..ab2e694756 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-EdgeSubscription.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-EdgeSubscription.md
@@ -38,7 +38,7 @@ When you remove an Edge Subscription, the following changes are made:
 - The Edge Transport server is removed from the list of source servers for any Send connector.
 - If the Edge Transport server is the only source server for any Send connector, the Send connector is removed.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -116,7 +116,7 @@ Accept wildcard characters: False
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
-If you don't use this switch, the command will inform you that the removal of the replicated recipient data from AD LDS can take a long time and will give you the option to cancel the operation.
+If you don't use this switch, the command informs you that the removal of the replicated recipient data from AD LDS can take a long time and gives you the option to cancel the operation.
 
 ```yaml
 Type: SwitchParameter
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-EmailAddressPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-EmailAddressPolicy.md
index c69eced8d4..659c486619 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-EmailAddressPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-EmailAddressPolicy.md
@@ -13,7 +13,7 @@ title: Remove-EmailAddressPolicy
 # Remove-EmailAddressPolicy
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Remove-EmailAddressPolicy cmdlet to remove existing email address policies and update the affected recipients. In Exchange Online, email address policies are available only for Microsoft 365 Groups.
 
@@ -30,7 +30,7 @@ Remove-EmailAddressPolicy [-Identity] <EmailAddressPolicyIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ExchangeCertificate.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ExchangeCertificate.md
index 2d4b35d81b..759c87b53a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-ExchangeCertificate.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ExchangeCertificate.md
@@ -47,7 +47,7 @@ There are many factors to consider when you configure certificates for Transport
 
 Secure Sockets Layer (SSL) is being replaced by Transport Layer Security (TLS) as the protocol that's used to encrypt data sent between computer systems. They're so closely related that the terms "SSL" and "TLS" (without versions) are often used interchangeably. Because of this similarity, references to "SSL" in Exchange topics, the Exchange admin center and the Exchange Management Shell have often been used to encompass both the SSL and TLS protocols. Typically, "SSL" refers to the actual SSL protocol only when a version is also provided (for example, SSL 3.0). For more information, see [Exchange Server TLS configuration best practices](https://learn.microsoft.com/Exchange/exchange-tls-configuration).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ExoPhishSimOverrideRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ExoPhishSimOverrideRule.md
index d8fa30e9df..cca2ee0b20 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-ExoPhishSimOverrideRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ExoPhishSimOverrideRule.md
@@ -30,7 +30,7 @@ Remove-ExoPhishSimOverrideRule [-Identity] <ComplianceRuleIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ExoSecOpsOverrideRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ExoSecOpsOverrideRule.md
index 38d2d1fda7..78b46cde3f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-ExoSecOpsOverrideRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ExoSecOpsOverrideRule.md
@@ -30,7 +30,7 @@ Remove-ExoSecOpsOverrideRule [-Identity] <ComplianceRuleIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-FederatedDomain.md b/exchange/exchange-ps/ExchangePowerShell/Remove-FederatedDomain.md
index 0269e862b1..a902c0d79e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-FederatedDomain.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-FederatedDomain.md
@@ -37,7 +37,7 @@ Remove-FederatedDomain [[-Identity] <OrganizationIdParameter>] -DomainName <Smtp
 ## DESCRIPTION
 An Exchange organization's federated organization identifier is generally created using the organization's primary domain name. Additional domain names can be added and removed. The Remove-FederatedDomain cmdlet removes a federated domain from the federated organization identifier.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-FederationTrust.md b/exchange/exchange-ps/ExchangePowerShell/Remove-FederationTrust.md
index 69e84008a4..7fe23723a4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-FederationTrust.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-FederationTrust.md
@@ -32,7 +32,7 @@ Remove-FederationTrust [-Identity] <FederationTrustIdParameter>
 ## DESCRIPTION
 Federation trusts are set up with Microsoft Federation Gateway to enable calendar sharing and free/busy sharing with external Exchange organizations or individuals. The Remove-FederationTrust cmdlet removes a federation trust.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ForeignConnector.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ForeignConnector.md
index cca67c8bde..ec31d4ab73 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-ForeignConnector.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ForeignConnector.md
@@ -32,9 +32,9 @@ Remove-ForeignConnector [-Identity] <ForeignConnectorIdParameter>
 ## DESCRIPTION
 The Remove-ForeignConnector cmdlet deletes the object and the configuration information for a Foreign connector.
 
-Although a Foreign connector is configured on a local Mailbox server, if you delete a Foreign connector, you may affect mail flow throughout the organization.
+Although a Foreign connector is configured on a local Mailbox server, if you delete a Foreign connector, you might affect mail flow throughout the organization.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-GlobalAddressList.md b/exchange/exchange-ps/ExchangePowerShell/Remove-GlobalAddressList.md
index 24d6c5a6f3..aa81c3aac7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-GlobalAddressList.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-GlobalAddressList.md
@@ -13,7 +13,7 @@ title: Remove-GlobalAddressList
 # Remove-GlobalAddressList
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Remove-GlobalAddressList cmdlet to remove an existing global address list (GAL).
 
@@ -32,7 +32,7 @@ Remove-GlobalAddressList [-Identity] <GlobalAddressListIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-GlobalMonitoringOverride.md b/exchange/exchange-ps/ExchangePowerShell/Remove-GlobalMonitoringOverride.md
index c8e627d480..a2657bb1a4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-GlobalMonitoringOverride.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-GlobalMonitoringOverride.md
@@ -15,7 +15,7 @@ title: Remove-GlobalMonitoringOverride
 ## SYNOPSIS
 This cmdlet is available only in on-premises Exchange.
 
-Use the Remove-GlobalMonitoringOverride cmdlet to remove a managed availability global override that has been configured for a probe, monitor or responder.
+Use the Remove-GlobalMonitoringOverride cmdlet to remove a managed availability global override that is configured for a probe, monitor or responder.
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
@@ -32,7 +32,7 @@ Remove-GlobalMonitoringOverride [-Identity] <String> -ItemType <MonitoringItemTy
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-HoldCompliancePolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-HoldCompliancePolicy.md
index bdefe64fb1..242c392d15 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-HoldCompliancePolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-HoldCompliancePolicy.md
@@ -17,7 +17,7 @@ This cmdlet is available only in Security & Compliance PowerShell. For more info
 
 Use the Remove-HoldCompliancePolicy cmdlet to remove preservation policies from the Microsoft Purview compliance portal.
 
-**Note**: The Remove-HoldCompliancePolicy cmdlet has been replaced by the Remove-RetentionCompliancePolicy cmdlet. If you have scripts that use Remove-HoldCompliancePolicy, update them to use Remove-RetentionCompliancePolicy.
+**Note**: The Remove-HoldCompliancePolicy cmdlet is replaced by the Remove-RetentionCompliancePolicy cmdlet. If you have scripts that use Remove-HoldCompliancePolicy, update them to use Remove-RetentionCompliancePolicy.
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-HoldComplianceRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-HoldComplianceRule.md
index 377d8164f2..a035716833 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-HoldComplianceRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-HoldComplianceRule.md
@@ -17,7 +17,7 @@ This cmdlet is available only in Security & Compliance PowerShell. For more info
 
 Use the Remove-HoldComplianceRule cmdlet to remove preservation rules from the Microsoft Purview compliance portal.
 
-**Note**: The Remove-HoldComplianceRule cmdlet has been replaced by the Remove-RetentionComplianceRule cmdlet. If you have scripts that use Remove-HoldComplianceRule, update them to use Remove-RetentionComplianceRule.
+**Note**: The Remove-HoldComplianceRule cmdlet is replaced by the Remove-RetentionComplianceRule cmdlet. If you have scripts that use Remove-HoldComplianceRule, update them to use Remove-RetentionComplianceRule.
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-HostedContentFilterPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-HostedContentFilterPolicy.md
index 1bcc3282ae..2de6203b68 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-HostedContentFilterPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-HostedContentFilterPolicy.md
@@ -31,7 +31,7 @@ Remove-HostedContentFilterPolicy [-Identity] <HostedContentFilterPolicyIdParamet
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-HostedContentFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-HostedContentFilterRule.md
index b5601178f5..1a10fd29d9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-HostedContentFilterRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-HostedContentFilterRule.md
@@ -29,7 +29,7 @@ Remove-HostedContentFilterRule [-Identity] <RuleIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-HostedOutboundSpamFilterPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-HostedOutboundSpamFilterPolicy.md
index ccbdb0fe1d..0d328a1aaa 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-HostedOutboundSpamFilterPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-HostedOutboundSpamFilterPolicy.md
@@ -30,7 +30,7 @@ Remove-HostedOutboundSpamFilterPolicy [-Identity] <HostedOutboundSpamFilterPolic
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-HostedOutboundSpamFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-HostedOutboundSpamFilterRule.md
index 48779d9ef1..928860c35e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-HostedOutboundSpamFilterRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-HostedOutboundSpamFilterRule.md
@@ -29,7 +29,7 @@ Remove-HostedOutboundSpamFilterRule [-Identity] <RuleIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-HybridConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Remove-HybridConfiguration.md
index 678ece27dd..612fd6ffd0 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-HybridConfiguration.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-HybridConfiguration.md
@@ -13,7 +13,7 @@ title: Remove-HybridConfiguration
 # Remove-HybridConfiguration
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Remove-HybridConfiguration cmdlet to delete the HybridConfigurationActive Directory object for your on-premises Exchange organization.
 
@@ -29,9 +29,9 @@ Remove-HybridConfiguration [-Confirm]
 ```
 
 ## DESCRIPTION
-Removing a HybridConfiguration object should typically only be performed in circumstances where the hybrid deployment state is corrupt and under the direction of Microsoft Customer Service and Support. After removing the HybridConfiguration object, your existing hybrid deployment configuration settings aren't disabled or removed. However, when the Hybrid Configuration wizard is run again after removing the HybridConfiguration object, the wizard won't have a hybrid configuration reference point for your existing feature settings. As a result, it will automatically create a HybridConfiguration object and record the new hybrid deployment configuration feature values defined in the wizard. The feature settings associated with the hybrid deployment, such as organization relationship or Send and Receive connector parameters, which were configured with the HybridConfiguration object that's removed, aren't removed or modified until the Hybrid Configuration wizard is run again.
+Removing a HybridConfiguration object should typically only be performed in circumstances where the hybrid deployment state is corrupt and under the direction of Microsoft Customer Service and Support. After removing the HybridConfiguration object, your existing hybrid deployment configuration settings aren't disabled or removed. However, when the Hybrid Configuration wizard is run again after removing the HybridConfiguration object, the wizard don't have a hybrid configuration reference point for your existing feature settings. As a result, it automatically creates a HybridConfiguration object and record the new hybrid deployment configuration feature values defined in the wizard. The feature settings associated with the hybrid deployment, such as organization relationship or Send and Receive connector parameters, which were configured with the HybridConfiguration object that's removed, aren't removed or modified until the Hybrid Configuration wizard is run again.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-InboundConnector.md b/exchange/exchange-ps/ExchangePowerShell/Remove-InboundConnector.md
index ab3d6ef257..b75c6d0852 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-InboundConnector.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-InboundConnector.md
@@ -31,7 +31,7 @@ Remove-InboundConnector [-Identity] <InboundConnectorIdParameter>
 ## DESCRIPTION
 Inbound connectors accept email messages from remote domains that require specific configuration options.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-InboxRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-InboxRule.md
index 7fa5cb1815..c4f3397c11 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-InboxRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-InboxRule.md
@@ -13,7 +13,7 @@ title: Remove-InboxRule
 # Remove-InboxRule
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Remove-InboxRule cmdlet to remove an Inbox rule.
 
@@ -35,7 +35,7 @@ Remove-InboxRule [-Identity] <InboxRuleIdParameter>
 ## DESCRIPTION
 When you create, modify, remove, enable, or disable an Inbox rule in Exchange PowerShell, any client-side rules created by Microsoft Outlook are removed.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -143,7 +143,7 @@ Accept wildcard characters: False
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
-A confirmation prompt warns you if the mailbox contains rules that were created by Outlook, because any client-side rules will be removed by the actions of this cmdlet.
+A confirmation prompt warns you if the mailbox contains rules that were created by Outlook, because any client-side rules are removed by the actions of this cmdlet.
 
 ```yaml
 Type: SwitchParameter
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-IntraOrganizationConnector.md b/exchange/exchange-ps/ExchangePowerShell/Remove-IntraOrganizationConnector.md
index 63bd0b6700..426008cadc 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-IntraOrganizationConnector.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-IntraOrganizationConnector.md
@@ -13,7 +13,7 @@ title: Remove-IntraOrganizationConnector
 # Remove-IntraOrganizationConnector
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Remove-IntraOrganizationConnector cmdlet to remove existing Intra-Organization connectors.
 
@@ -34,7 +34,7 @@ Intra-Organizational connectors enable features and services between divisions i
 
 The Remove-IntraOrganizationConnector cmdlet removes the connector objects. To stop feature or service connectivity without removing the connector object, run the command: `Set-IntraOrganizationConnector <ConnectorIdentity> -Enabled $false`.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-JournalRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-JournalRule.md
index 751b3b50ad..58e379d9f0 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-JournalRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-JournalRule.md
@@ -13,7 +13,7 @@ title: Remove-JournalRule
 # Remove-JournalRule
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Remove-JournalRule cmdlet to remove an existing journal rule.
 
@@ -32,7 +32,7 @@ Remove-JournalRule [-Identity] <RuleIdParameter>
 ## DESCRIPTION
 The Remove-JournalRule cmdlet removes the specified journal rule from Active Directory.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-MailContact.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MailContact.md
index a45da6931e..41677f24f9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-MailContact.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MailContact.md
@@ -13,7 +13,7 @@ title: Remove-MailContact
 # Remove-MailContact
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Remove-MailContact cmdlet to delete existing mail contacts.
 
@@ -31,7 +31,7 @@ Remove-MailContact [-Identity] <MailContactIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-MailUser.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MailUser.md
index 65fa8bfa18..550a45c9ff 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-MailUser.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MailUser.md
@@ -13,7 +13,7 @@ title: Remove-MailUser
 # Remove-MailUser
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Remove-MailUser cmdlet to remove existing mail users.
 
@@ -33,7 +33,7 @@ Remove-MailUser [-Identity] <MailUserIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-Mailbox.md b/exchange/exchange-ps/ExchangePowerShell/Remove-Mailbox.md
index 3aeeb163aa..0765f501d9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-Mailbox.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-Mailbox.md
@@ -13,7 +13,7 @@ title: Remove-Mailbox
 # Remove-Mailbox
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Remove-Mailbox cmdlet to delete mailboxes and the associated user accounts.
 
@@ -81,7 +81,7 @@ Use the Identity and Permanent parameters to disconnect the mailbox from the use
 
 Use the Disable-Mailbox cmdlet to disconnect the mailbox from the user account, but keep the user account. The mailbox is retained until the deleted mailbox retention period for the database or the mailbox expires, and then the mailbox is permanently deleted (purged). Or, you can immediately purge the disconnected mailbox by using the Database and StoreMailboxIdentity parameters on the Remove-Mailbox cmdlet.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -106,7 +106,7 @@ $Temp = Get-Mailbox | Where {$_.DisplayName -eq 'John Rodman'}
 Remove-Mailbox -Database Server01\Database01 -StoreMailboxIdentity $Temp.MailboxGuid
 ```
 
-In on-premises Exchange, this example removes John Rodman's mailbox from the mailbox database after the mailbox has been disconnected from the user account. The example uses the Get-Mailbox cmdlet to retrieve the mailbox GUID value of the disconnected mailbox, which is required by the StoreMailboxIdentity parameter.
+In on-premises Exchange, this example removes John Rodman's mailbox from the mailbox database after the mailbox is disconnected from the user account. The example uses the Get-Mailbox cmdlet to retrieve the mailbox GUID value of the disconnected mailbox, which is required by the StoreMailboxIdentity parameter.
 
 ### Example 4
 ```powershell
@@ -409,7 +409,7 @@ This parameter is available only in on-premises Exchange.
 The Permanent parameter specifies whether to permanently delete the mailbox from the mailbox database. Valid values are:
 
 - $true: The mailbox is immediately and permanently deleted (purged). You can't reconnect or restore the mailbox.
-- $false: The mailbox disabled and retained until the deleted mailbox retention period expires. You can reconnect or restore the mailbox until the deleted mailbox retention period expires. This is the default value.
+- $false: The mailbox disabled and retained until the deleted mailbox retention period expires. You can reconnect or restore the mailbox until the deleted mailbox retention period expires. This value is the default.
 
 ```yaml
 Type: Boolean
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxDatabase.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxDatabase.md
index 943286d523..25db72c47c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxDatabase.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxDatabase.md
@@ -34,7 +34,7 @@ If the mailbox database has a database copy, the Remove-MailboxDatabase cmdlet a
 
 The Remove-MailboxDatabase cmdlet removes only the database object from Active Directory. It doesn't remove the physical database files. You must remove the database files manually after you run the Remove-MailboxDatabase cmdlet.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxDatabaseCopy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxDatabaseCopy.md
index e6b2cbbd4e..04f4669b42 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxDatabaseCopy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxDatabaseCopy.md
@@ -33,11 +33,11 @@ Remove-MailboxDatabaseCopy [-Identity] <DatabaseCopyIdParameter>
 To use the Remove-MailboxDatabaseCopy cmdlet to remove a mailbox database copy, the following criteria must be met:
 
 - The database availability group (DAG) hosting the mailbox database must have quorum and all cluster and network functions must be healthy.
-- If you're removing the last passive copy of the database, continuous replication circular logging (CRCL) must not be enabled for the specified mailbox database. If CRCL is enabled, you must first disable it. After the mailbox database copy has been removed, circular logging can be enabled. After enabling circular logging for a non-replicated mailbox database, JET circular logging is used instead of CRCL. If you aren't removing the last passive copy of a database, CRCL can remain enabled.
+- If you're removing the last passive copy of the database, continuous replication circular logging (CRCL) must not be enabled for the specified mailbox database. If CRCL is enabled, you must first disable it. After the mailbox database copy is removed, circular logging can be enabled. After enabling circular logging for a non-replicated mailbox database, JET circular logging is used instead of CRCL. If you aren't removing the last passive copy of a database, CRCL can remain enabled.
 
 You can't use this cmdlet to remove the active copy of a mailbox database. To remove the active copy of a mailbox database, you must first remove all passive copies of the database and then use the Remove-MailboxDatabase cmdlet to remove the active copy.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 Running this cmdlet removes the mailbox database copy configuration, but doesn't delete the database copy's files. If necessary, you can manually delete those files.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxExportRequest.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxExportRequest.md
index 9e5d6dcdcb..f4371e2ec3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxExportRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxExportRequest.md
@@ -49,7 +49,7 @@ The parameter set that requires the Identity parameter allows you to remove a fu
 
 The parameter set that requires the RequestGuid and RequestQueue parameters is used for Microsoft Exchange Mailbox Replication service (MRS) debugging purposes only.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxFolderPermission.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxFolderPermission.md
index ba7741eb85..fd615eb7b3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxFolderPermission.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxFolderPermission.md
@@ -13,7 +13,7 @@ title: Remove-MailboxFolderPermission
 # Remove-MailboxFolderPermission
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Remove-MailboxFolderPermission cmdlet to remove folder-level permissions for users in mailboxes.
 
@@ -53,7 +53,7 @@ Remove-MailboxFolderPermission [-Identity] <MailboxFolderIdParameter> [-ResetDel
 ## DESCRIPTION
 You can't use this cmdlet to selectively remove permissions from a user on a mailbox folder. The cmdlet removes all permissions that are assigned to the user on the specified folder. To modify the permissions that are assigned to the user on a mailbox folder, use the Set-MailboxFolderPermission cmdlet.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -69,7 +69,7 @@ This example removes John's permissions to the Training folder in Kim's mailbox.
 Remove-MailboxFolderPermission -Identity kim@contoso.com:\Calendar -ResetDelegateUserCollection
 ```
 
-This example will clear any corrupted delegate information from Kim's mailbox.
+This example clears any corrupted delegate information from Kim's mailbox.
 
 ## PARAMETERS
 
@@ -205,7 +205,7 @@ Accept wildcard characters: False
 
 The ResetDelegateUserCollection switch forces the removal of the LocalFreeBusy or the PR_FREEBUSY_ENTRYIDs files in case of corruption. You don't need to specify a value with this switch.
 
-Use this switch if you encounter problems trying add, change, or remove delegate permissions. Using this switch deletes those files and downgrades any existing delegates to Editor permissions. You'll need to grant delegate permissions again using `-SharingPermissionFlag Delegate`.
+Use this switch if you encounter problems trying add, change, or remove delegate permissions. Using this switch deletes those files and downgrades any existing delegates to Editor permissions. You need to grant delegate permissions again using `-SharingPermissionFlag Delegate`.
 
 When you use this switch, the value of Identity should be the user's primary calendar folder (for example, `kim@contoso.com:\Calendar`).
 
@@ -230,7 +230,7 @@ This parameter is available only in the cloud-based service.
 The SendNotificationToUser parameter specifies whether to send a notification to the user when you remove their calendar permissions. Valid values are:
 
 - $true: A notification is sent.
-- $false: No notification is sent. This is the default value.
+- $false: No notification is sent. This value is the default.
 
 This parameter only applies to calendar folders.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxIRMAccess.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxIRMAccess.md
index 1c949e5443..ff233167dc 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxIRMAccess.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxIRMAccess.md
@@ -30,7 +30,7 @@ Remove-MailboxIRMAccess [-Identity] <MailboxIdParameter> -User <SecurityPrincipa
 > [!NOTE]
 > This cmdlet works only for delegates who already have Full Access permission to the mailbox. For more information, see [Manage permissions for recipients in Exchange Online](https://learn.microsoft.com/exchange/recipients-in-exchange-online/manage-permissions-for-recipients).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxImportRequest.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxImportRequest.md
index 88ffe57767..4b0ccfcb1b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxImportRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxImportRequest.md
@@ -13,7 +13,7 @@ title: Remove-MailboxImportRequest
 # Remove-MailboxImportRequest
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Remove-MailboxImportRequest cmdlet to remove fully or partially completed import requests. Completed import requests aren't automatically cleared. Requests need to be removed by using the Remove-MailboxImportRequest cmdlet. Multiple import requests can exist against the same mailbox if you provide a distinct import request name.
 
@@ -21,7 +21,7 @@ NOTE: This cmdlet is no longer supported in Exchange Online. To import a .pst fi
 
 This cmdlet is available only in the Mailbox Import Export role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Mailbox Import Export role to a role group (for example, to the Organization Management role group). For more information, see [Add a role to a role group](https://learn.microsoft.com/Exchange/permissions/role-groups#add-a-role-to-a-role-group).
 
-Removing a partially completed import request removes the request from the Microsoft Exchange Mailbox Replication service (MRS) job queue. Any import progress that was made until the removal won't be reverted.
+Removing a partially completed import request removes the request from the Microsoft Exchange Mailbox Replication service (MRS) job queue. Any import progress made before the removal isn't reverted.
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
@@ -51,7 +51,7 @@ The parameter set that requires the Identity parameter allows you to remove a fu
 
 The parameter set that requires the RequestGuid and RequestQueue parameters is used for MRS debugging purposes only.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxPermission.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxPermission.md
index 64516015a0..49d7dc1c4e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxPermission.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxPermission.md
@@ -13,7 +13,7 @@ title: Remove-MailboxPermission
 # Remove-MailboxPermission
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Remove-MailboxPermission cmdlet to remove permissions from a user's mailbox or from an Exchange Server 2016, Exchange Server 2019 or Exchange Online mail user.
 
@@ -87,7 +87,7 @@ Remove-MailboxPermission [-Identity] <MailboxIdParameter> [-ResetDefault]
 ## DESCRIPTION
 The Remove-MailboxPermission cmdlet allows you to remove permissions from a user's mailbox, for example, removing full access to another user's mailbox.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxRepairRequest.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxRepairRequest.md
index 714bff2d94..0f77f23c1c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxRepairRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxRepairRequest.md
@@ -30,9 +30,9 @@ Remove-MailboxRepairRequest [-Identity] <StoreIntegrityCheckJobIdParameter>
 ```
 
 ## DESCRIPTION
-You can run the Remove-MailboxRepairRequest cmdlet to remove all mailbox repair requests for a specific database, for a group of related mailbox repair requests, or for a specific mailbox repair request. Mailbox repair requests are identified by a complex GUID with the following format: `DatabaseGuid\RequestGuid\JobGuid`. The DatabaseGuid identifies the mailbox database where the mailbox being repaired is located. The RequestGuid identifies related requests that may contain more than one job if the request runs more than one task or targets more than one mailbox. The JobGuid identifies a unique job. See the examples to remove all requests on a mailbox database, remove a group of related requests that share the same RequestGuid, or remove a specific request by specifying the complete `DatabaseGuid\RequestGuid\JobGuid` value.
+You can run the Remove-MailboxRepairRequest cmdlet to remove all mailbox repair requests for a specific database, for a group of related mailbox repair requests, or for a specific mailbox repair request. Mailbox repair requests are identified by a complex GUID with the following format: `DatabaseGuid\RequestGuid\JobGuid`. The DatabaseGuid identifies the mailbox database where the mailbox being repaired is located. The RequestGuid identifies related requests that might contain more than one job if the request runs more than one task or targets more than one mailbox. The JobGuid identifies a unique job. See the examples to remove all requests on a mailbox database, remove a group of related requests that share the same RequestGuid, or remove a specific request by specifying the complete `DatabaseGuid\RequestGuid\JobGuid` value.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxRestoreRequest.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxRestoreRequest.md
index 9a86971144..3b1bd245ff 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxRestoreRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxRestoreRequest.md
@@ -13,7 +13,7 @@ title: Remove-MailboxRestoreRequest
 # Remove-MailboxRestoreRequest
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Remove-MailboxRestoreRequest cmdlet to remove fully or partially completed restore requests.
 
@@ -45,7 +45,7 @@ The parameter set that requires the Identity parameter allows you to remove a fu
 
 The parameter set that requires the RequestGuid and RequestQueue parameters is used for Microsoft Exchange Mailbox Replication service (MRS) debugging purposes only.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxSearch.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxSearch.md
index 0c67e70f83..90b6f263d9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxSearch.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxSearch.md
@@ -13,7 +13,7 @@ title: Remove-MailboxSearch
 # Remove-MailboxSearch
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Remove-MailboxSearch cmdlet to remove a mailbox search.
 
@@ -34,7 +34,7 @@ Remove-MailboxSearch [-Identity] <SearchObjectIdParameter>
 ## DESCRIPTION
 In on-premises Exchange, mailbox searches are used for In-Place eDiscovery and In-Place Hold. You can't remove an In-Place Hold without first disabling the hold.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxUserConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxUserConfiguration.md
index c8bd7e9dd0..df48043dd3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxUserConfiguration.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxUserConfiguration.md
@@ -13,7 +13,7 @@ title: Remove-MailboxUserConfiguration
 # Remove-MailboxUserConfiguration
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Remove-MailboxUserConfiguration cmdlet to remove user configuration items from mailboxes. Typically, after you delete a user configuration item, it's automatically recreated the next time the user uses that feature in their mailbox.
 
@@ -30,7 +30,7 @@ Remove-MailboxUserConfiguration [-Identity] <MailboxUserConfigurationIdParameter
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-MalwareFilterPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MalwareFilterPolicy.md
index 61b270394e..c839114494 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-MalwareFilterPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MalwareFilterPolicy.md
@@ -13,7 +13,7 @@ title: Remove-MalwareFilterPolicy
 # Remove-MalwareFilterPolicy
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Remove-MalwareFilterPolicy cmdlet to remove malware filter policies from your organization.
 
@@ -33,7 +33,7 @@ Remove-MalwareFilterPolicy [-Identity] <MalwareFilterPolicyIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-MalwareFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MalwareFilterRule.md
index 9ef8eb5d88..eea5a20e1b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-MalwareFilterRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MalwareFilterRule.md
@@ -13,7 +13,7 @@ title: Remove-MalwareFilterRule
 # Remove-MalwareFilterRule
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Remove-MalwareFilterRule cmdlet to remove malware filter rules from your organization.
 
@@ -30,7 +30,7 @@ Remove-MalwareFilterRule [-Identity] <RuleIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ManagedContentSettings.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ManagedContentSettings.md
index 15b27f5dc3..ece20ad599 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-ManagedContentSettings.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ManagedContentSettings.md
@@ -32,7 +32,7 @@ Remove-ManagedContentSettings [-Identity] <ELCContentSettingsIdParameter>
 ## DESCRIPTION
 When managed content settings are removed from a managed folder, the folder effectively ceases to be a managed folder, and folder contents are no longer under messaging records management (MRM). Removing managed content settings disables any retention and journaling policies for the folder. It doesn't affect whether you can move, delete, or rename the folder, or whether the folder has a quota or policy statement that's displayed in Microsoft Outlook or Microsoft Office Outlook Web App.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ManagedFolder.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ManagedFolder.md
index 47dd5e5805..3c1c9a65e9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-ManagedFolder.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ManagedFolder.md
@@ -32,7 +32,7 @@ Remove-ManagedFolder [-Identity] <ELCFolderIdParameter>
 ## DESCRIPTION
 The Remove-ManagedFolder cmdlet accepts a managed folder object or a mailbox identity as pipelined input.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ManagedFolderMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ManagedFolderMailboxPolicy.md
index 4a3882a8e3..67fa7e4aa1 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-ManagedFolderMailboxPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ManagedFolderMailboxPolicy.md
@@ -31,9 +31,9 @@ Remove-ManagedFolderMailboxPolicy [-Identity] <MailboxPolicyIdParameter>
 ```
 
 ## DESCRIPTION
-If you remove a managed folder mailbox policy that's applied to users' mailboxes, the affected mailboxes may no longer have retention settings. Therefore, before using this cmdlet to remove a policy, you should determine if the managed folder mailbox policy is applied to any users, and apply another policy to those users.
+If you remove a managed folder mailbox policy that's applied to users' mailboxes, the affected mailboxes might no longer have retention settings. Therefore, before using this cmdlet to remove a policy, you should determine if the managed folder mailbox policy is applied to any users, and apply another policy to those users.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ManagementRole.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ManagementRole.md
index c55c9255c5..39277631d6 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-ManagementRole.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ManagementRole.md
@@ -13,7 +13,7 @@ title: Remove-ManagementRole
 # Remove-ManagementRole
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Remove-ManagementRole cmdlet to remove custom management roles that you don't need anymore.
 
@@ -35,7 +35,7 @@ Remove-ManagementRole [-Identity] <RoleIdParameter>
 ## DESCRIPTION
 You need to remove all the management role assignments from a role before you delete it. If the role is the parent of child roles, the child roles must be removed before you remove the parent role, or you must use the Recurse parameter when you remove the parent role. You can only remove custom roles. Built-in roles, such as the Mail Recipients role, can't be removed. For more information about how to remove a custom role, see [Remove a role](https://learn.microsoft.com/exchange/remove-a-role-exchange-2013-help).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -67,7 +67,7 @@ This example uses the Get-ManagementRole cmdlet to get a list of roles that cont
 Remove-ManagementRole "In-house scripts" -UnScopedTopLevel
 ```
 
-In on-premises Exchange, this example removes the In-house scripts unscoped top-level management role. Because this is an unscoped top-level role, the UnScopedTopLevel switch must be used. Note that the UnScopedTopLevel switch requires the UnScoped Role Management role, which isn't assigned to any role groups by default.
+In on-premises Exchange, this example removes the In-house scripts unscoped top-level management role. Because this is an unscoped top-level role, the UnScopedTopLevel switch must be used. The UnScopedTopLevel switch requires the UnScoped Role Management role, which isn't assigned to any role groups by default.
 
 For more information about unscoped top-level management roles, see [Understanding management roles](https://learn.microsoft.com/exchange/understanding-management-roles-exchange-2013-help).
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ManagementRoleAssignment.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ManagementRoleAssignment.md
index 41c64180c4..4a4e87c6c9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-ManagementRoleAssignment.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ManagementRoleAssignment.md
@@ -13,7 +13,7 @@ title: Remove-ManagementRoleAssignment
 # Remove-ManagementRoleAssignment
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Remove-ManagementRoleAssignment cmdlet to remove management role assignments.
 
@@ -33,7 +33,7 @@ Remove-ManagementRoleAssignment [-Identity] <RoleAssignmentIdParameter>
 ## DESCRIPTION
 When you remove a role assignment, the management role group, management role assignment, user, or universal security group (USG) that was assigned the associated role can no longer access the cmdlets or parameters made available by the role. For more information about management role assignments, see [Understanding management role assignments](https://learn.microsoft.com/exchange/understanding-management-role-assignments-exchange-2013-help).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ManagementRoleEntry.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ManagementRoleEntry.md
index fa22bd85fe..def11dc9d1 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-ManagementRoleEntry.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ManagementRoleEntry.md
@@ -13,7 +13,7 @@ title: Remove-ManagementRoleEntry
 # Remove-ManagementRoleEntry
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Remove-ManagementRoleEntry cmdlet to remove existing management role entries.
 
@@ -35,7 +35,7 @@ The Remove-ManagementRoleEntry cmdlet removes existing role entries. However, yo
 
 For more information about management role entries, see [Understanding management roles](https://learn.microsoft.com/exchange/understanding-management-roles-exchange-2013-help).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ManagementScope.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ManagementScope.md
index da3e698805..d21c285668 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-ManagementScope.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ManagementScope.md
@@ -13,7 +13,7 @@ title: Remove-ManagementScope
 # Remove-ManagementScope
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Remove-ManagementScope cmdlet to remove an existing management scope.
 
@@ -33,7 +33,7 @@ Remove-ManagementScope [-Identity] <ManagementScopeIdParameter>
 ## DESCRIPTION
 You can't remove a management scope if it's associated with a management role assignment. Use the Get-ManagementScope cmdlet to retrieve a list of orphaned scopes. For more information about regular and exclusive scopes, see [Understanding management role scopes](https://learn.microsoft.com/exchange/understanding-management-role-scopes-exchange-2013-help).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-MapiVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MapiVirtualDirectory.md
index 743e25116c..b5634346e1 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-MapiVirtualDirectory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MapiVirtualDirectory.md
@@ -30,7 +30,7 @@ Remove-MapiVirtualDirectory [-Identity] <VirtualDirectoryIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-Message.md b/exchange/exchange-ps/ExchangePowerShell/Remove-Message.md
index f61b55fd1a..462f8cf196 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-Message.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-Message.md
@@ -42,7 +42,7 @@ Remove-Message [-Identity] <MessageIdentity>
 ## DESCRIPTION
 A message being transmitted to multiple recipients might be located in multiple queues. If you specify an Identity parameter, the message is removed from a single queue if that identity matches only a single message. If the identity matches more than one message, you receive an error. To remove a message from more than one queue in a single operation, you must use the Filter parameter. If you try to remove a message currently being delivered, the message status changes to PendingDelete. Message delivery isn't interrupted, but if the delivery fails and causes the message to re-enter the queue, it's then removed.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-MessageClassification.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MessageClassification.md
index 488a7efb2d..3ad8456773 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-MessageClassification.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MessageClassification.md
@@ -13,7 +13,7 @@ title: Remove-MessageClassification
 # Remove-MessageClassification
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Remove-MessageClassification cmdlet to delete an existing message classification instance from your organization.
 
@@ -30,7 +30,7 @@ Remove-MessageClassification [-Identity] <MessageClassificationIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-MigrationBatch.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MigrationBatch.md
index 1c7dc32bba..621ad34cae 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-MigrationBatch.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MigrationBatch.md
@@ -13,9 +13,9 @@ title: Remove-MigrationBatch
 # Remove-MigrationBatch
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
-Use the Remove-MigrationBatch cmdlet to delete a migration batch that either isn't running or has been completed. If necessary, you can run the Get-MigrationBatch cmdlet to determine the status of a migration batch before you remove it.
+Use the Remove-MigrationBatch cmdlet to delete a migration batch that either isn't running or is completed. If necessary, you can run the Get-MigrationBatch cmdlet to determine the status of a migration batch before you remove it.
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
@@ -36,7 +36,7 @@ The Remove-MigrationBatch cmdlet removes a migration batch. All subscriptions ar
 
 If you use the Force switch with this cmdlet, the individual user requests and subscriptions that were part of the removed migration batch aren't removed. You need to remove the individual migration user requests with the command: `Remove-MigrationUser <Identity> -Force`.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-MigrationEndpoint.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MigrationEndpoint.md
index a5d4823b42..b550b89413 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-MigrationEndpoint.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MigrationEndpoint.md
@@ -13,7 +13,7 @@ title: Remove-MigrationEndpoint
 # Remove-MigrationEndpoint
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Remove-MigrationEndpoint cmdlet to remove existing migration endpoints for source or destination servers for cutover or staged Exchange migrations, IMAP migrations and remote moves.
 
@@ -35,7 +35,7 @@ Use the Remove-MigrationEndpoint cmdlet to remove an existing migration endpoint
 
 For more information about migration endpoints, see [Set-MigrationEndpoint](https://learn.microsoft.com/powershell/module/exchangepowershell/set-migrationendpoint) and [New-MigrationEndpoint](https://learn.microsoft.com/powershell/module/exchangepowershell/new-migrationendpoint).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-MigrationUser.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MigrationUser.md
index 6b633b250b..21265c4d48 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-MigrationUser.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MigrationUser.md
@@ -13,7 +13,7 @@ title: Remove-MigrationUser
 # Remove-MigrationUser
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Remove-MigrationUser cmdlet to remove a migration user from a batch.
 
@@ -32,7 +32,7 @@ Remove-MigrationUser [-Identity] <MigrationUserIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-MobileDevice.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MobileDevice.md
index a77fdb44ad..d47d20a69c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-MobileDevice.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MobileDevice.md
@@ -13,7 +13,7 @@ title: Remove-MobileDevice
 # Remove-MobileDevice
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Remove-MobileDevice cmdlet to remove mobile device partnerships that identify the devices that are configured to synchronize with user mailboxes.
 
@@ -32,7 +32,7 @@ Remove-MobileDevice [-Identity] <MobileDeviceIdParameter>
 ## DESCRIPTION
 The Remove-MobileDevice cmdlet is useful for removing mobile devices that no longer synchronize successfully with the server.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-MobileDeviceMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MobileDeviceMailboxPolicy.md
index ca89c8284e..978c5c882f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-MobileDeviceMailboxPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MobileDeviceMailboxPolicy.md
@@ -13,7 +13,7 @@ title: Remove-MobileDeviceMailboxPolicy
 # Remove-MobileDeviceMailboxPolicy
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Remove-MobileDeviceMailboxPolicy cmdlet to remove mobile device mailbox policies from Exchange servers.
 
@@ -33,7 +33,7 @@ Remove-MobileDeviceMailboxPolicy [-Identity] <MailboxPolicyIdParameter>
 ## DESCRIPTION
 A Mobile Device mailbox policy is a group of settings that specifies how mobile phones connect to Exchange. Exchange supports multiple mobile device mailbox policies. The Remove-MobileDeviceMailboxPolicy cmdlet removes a specific mobile device mailbox policy. If any users are assigned to the policy when you remove it, the Remove-MobileDeviceMailboxPolicy cmdlet fails.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-MoveRequest.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MoveRequest.md
index ba85c16ce2..3c1e58353f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-MoveRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MoveRequest.md
@@ -13,7 +13,7 @@ title: Remove-MoveRequest
 # Remove-MoveRequest
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Remove-MoveRequest cmdlet to cancel a mailbox move initiated using the New-MoveRequest cmdlet.
 
@@ -49,7 +49,7 @@ In Exchange 2010, you need to use the Remove-MoveRequest cmdlet on completed mov
 
 The MoveRequestQueue and MailboxGuid parameters are for debugging purposes only.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-OMEConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Remove-OMEConfiguration.md
index b883db3f6a..11da253b2d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-OMEConfiguration.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-OMEConfiguration.md
@@ -29,7 +29,7 @@ Remove-OMEConfiguration [-Identity] <OMEConfigurationIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-OabVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Remove-OabVirtualDirectory.md
index 9fbb317d05..ce326f3292 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-OabVirtualDirectory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-OabVirtualDirectory.md
@@ -33,7 +33,7 @@ Remove-OabVirtualDirectory [-Identity] <VirtualDirectoryIdParameter>
 ## DESCRIPTION
 Some situations require the removal of an OAB virtual directory. For example, to uninstall an Exchange server that contains an OAB distribution points list, you need to remove the OAB virtual directory and then re-create it on another server.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-OfflineAddressBook.md b/exchange/exchange-ps/ExchangePowerShell/Remove-OfflineAddressBook.md
index ae2cf79c53..7d7ab5b347 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-OfflineAddressBook.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-OfflineAddressBook.md
@@ -13,7 +13,7 @@ title: Remove-OfflineAddressBook
 # Remove-OfflineAddressBook
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Remove-OfflineAddressBook cmdlet to remove (delete) offline address books (OABs).
 
@@ -35,7 +35,7 @@ Remove-OfflineAddressBook [-Identity] <OfflineAddressBookIdParameter>
 ## DESCRIPTION
 If you remove the default OAB, you need to configure another OAB as the default by using the IsDefault parameter on the New-OfflineAddressBook or Set-OfflineAddressBook cmdlets.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-OnPremisesOrganization.md b/exchange/exchange-ps/ExchangePowerShell/Remove-OnPremisesOrganization.md
index 02de5ee8ee..1c96267990 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-OnPremisesOrganization.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-OnPremisesOrganization.md
@@ -29,9 +29,9 @@ Remove-OnPremisesOrganization [-Identity] <OnPremisesOrganizationIdParameter>
 ```
 
 ## DESCRIPTION
-Removing an OnPremisesOrganization object should only be used in circumstances where the hybrid deployment state is corrupt and under the direction and supervision of Microsoft Customer Service and Support. After removing the OnPremisesOrganization object, any related hybrid deployment configured with this object won't be functional and will need to be re-created and reconfigured.
+Removing an OnPremisesOrganization object should only be used in circumstances where the hybrid deployment state is corrupt and under the direction and supervision of Microsoft Customer Service and Support. After removing the OnPremisesOrganization object, any related hybrid deployment configured with this object aren't functional and need to be re-created and reconfigured.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-OrganizationRelationship.md b/exchange/exchange-ps/ExchangePowerShell/Remove-OrganizationRelationship.md
index 006af945f7..e1a750ebb3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-OrganizationRelationship.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-OrganizationRelationship.md
@@ -13,7 +13,7 @@ title: Remove-OrganizationRelationship
 # Remove-OrganizationRelationship
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Remove-OrganizationRelationship cmdlet to remove the organization relationship with an external Exchange organization.
 
@@ -32,7 +32,7 @@ Remove-OrganizationRelationship [-Identity] <OrganizationRelationshipIdParameter
 ## DESCRIPTION
 The Remove-OrganizationRelationship cmdlet removes the organization relationship objects. To stop sharing information without removing the organization relationship objects, disable the organization relationship by using the Set-OrganizationRelationship cmdlet.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 

From 2ca45d5529b435bf0ae7b31d49e66eab3c670b3b Mon Sep 17 00:00:00 2001
From: Chris Davis <chris.davis@microsoft.com>
Date: Wed, 6 Aug 2025 09:49:09 -0700
Subject: [PATCH 109/145] Acrolinx 12

---
 .../Remove-OutboundConnector.md               |  2 +-
 .../Remove-OutlookProtectionRule.md           |  4 +--
 .../Remove-OutlookProvider.md                 |  2 +-
 .../Remove-OwaMailboxPolicy.md                |  6 ++--
 .../Remove-OwaVirtualDirectory.md             |  2 +-
 .../Remove-PartnerApplication.md              |  4 +--
 .../Remove-PhishSimOverridePolicy.md          |  2 +-
 .../Remove-PolicyTipConfig.md                 |  4 +--
 .../Remove-PowerShellVirtualDirectory.md      |  4 +--
 .../ExchangePowerShell/Remove-PublicFolder.md |  4 +--
 ...ve-PublicFolderAdministrativePermission.md |  2 +-
 .../Remove-PublicFolderClientPermission.md    |  4 +--
 .../Remove-PublicFolderDatabase.md            |  2 +-
 ...ove-PublicFolderMailboxMigrationRequest.md |  4 +--
 .../Remove-PublicFolderMigrationRequest.md    |  2 +-
 .../Remove-PublicFolderMoveRequest.md         |  6 ++--
 .../Remove-QuarantinePolicy.md                |  2 +-
 .../Remove-ReceiveConnector.md                |  2 +-
 .../Remove-RecipientPermission.md             |  2 +-
 .../ExchangePowerShell/Remove-RemoteDomain.md |  4 +--
 .../Remove-RemoteMailbox.md                   |  4 +--
 .../Remove-ReportSubmissionPolicy.md          |  2 +-
 .../Remove-ReportSubmissionRule.md            |  2 +-
 .../Remove-ResubmitRequest.md                 |  2 +-
 .../Remove-RetentionPolicy.md                 |  6 ++--
 .../Remove-RetentionPolicyTag.md              |  6 ++--
 .../Remove-RoleAssignmentPolicy.md            |  4 +--
 .../ExchangePowerShell/Remove-RoleGroup.md    |  6 ++--
 .../Remove-RoleGroupMember.md                 |  6 ++--
 .../Remove-RoutingGroupConnector.md           |  2 +-
 .../Remove-RpcClientAccess.md                 |  4 +--
 .../Remove-SafeAttachmentPolicy.md            |  2 +-
 .../Remove-SafeAttachmentRule.md              |  2 +-
 .../Remove-SafeLinksPolicy.md                 |  2 +-
 .../Remove-SafeLinksRule.md                   |  2 +-
 .../Remove-SearchDocumentFormat.md            |  6 ++--
 .../Remove-SecOpsOverridePolicy.md            |  2 +-
 .../Remove-SendConnector.md                   |  4 +--
 .../Remove-ServerMonitoringOverride.md        |  4 +--
 .../Remove-ServicePrincipal.md                |  2 +-
 .../Remove-SettingOverride.md                 |  2 +-
 .../Remove-SharingPolicy.md                   |  4 +--
 .../Remove-SiteMailboxProvisioningPolicy.md   |  2 +-
 .../ExchangePowerShell/Remove-StoreMailbox.md |  2 +-
 .../ExchangePowerShell/Remove-SweepRule.md    |  4 +--
 .../Remove-SyncMailPublicFolder.md            |  4 +--
 .../Remove-SystemMessage.md                   |  2 +-
 .../Remove-TenantAllowBlockListItems.md       |  4 +--
 .../Remove-TenantAllowBlockListSpoofItems.md  |  2 +-
 .../Remove-ThrottlingPolicy.md                |  2 +-
 .../Remove-TransportRule.md                   |  4 +--
 .../Remove-UMAutoAttendant.md                 |  2 +-
 .../Remove-UMCallAnsweringRule.md             |  4 +--
 .../ExchangePowerShell/Remove-UMDialPlan.md   |  2 +-
 .../ExchangePowerShell/Remove-UMHuntGroup.md  |  2 +-
 .../ExchangePowerShell/Remove-UMIPGateway.md  |  2 +-
 .../Remove-UMMailboxPolicy.md                 |  2 +-
 .../ExchangePowerShell/Remove-UnifiedGroup.md |  2 +-
 .../Remove-UnifiedGroupLinks.md               |  2 +-
 .../ExchangePowerShell/Remove-UserPhoto.md    |  4 +--
 .../Remove-VivaModuleFeaturePolicy.md         |  2 +-
 .../Remove-WebServicesVirtualDirectory.md     |  2 +-
 .../Remove-X400AuthoritativeDomain.md         |  2 +-
 .../Reset-ProvisioningCache.md                |  4 +--
 .../Restore-DatabaseAvailabilityGroup.md      |  2 +-
 .../Restore-DetailsTemplate.md                |  2 +-
 .../ExchangePowerShell/Restore-Mailbox.md     |  8 ++---
 .../Restore-RecoverableItems.md               |  8 ++---
 .../Resume-MailboxDatabaseCopy.md             |  2 +-
 .../Resume-MailboxExportRequest.md            |  2 +-
 .../Resume-MailboxImportRequest.md            |  4 +--
 .../Resume-MailboxRestoreRequest.md           |  4 +--
 .../ExchangePowerShell/Resume-Message.md      |  4 +--
 .../ExchangePowerShell/Resume-MoveRequest.md  |  6 ++--
 .../Resume-PublicFolderMigrationRequest.md    |  2 +-
 .../Resume-PublicFolderMoveRequest.md         |  4 +--
 .../Resume-PublicFolderReplication.md         |  2 +-
 .../ExchangePowerShell/Resume-Queue.md        |  2 +-
 .../ExchangePowerShell/Retry-Queue.md         |  2 +-
 .../Rotate-DkimSigningConfig.md               |  2 +-
 .../Search-AdminAuditLog.md                   |  8 ++---
 .../ExchangePowerShell/Search-Mailbox.md      |  2 +-
 .../Search-MailboxAuditLog.md                 |  6 ++--
 .../Search-MessageTrackingReport.md           |  4 +--
 .../Search-UnifiedAuditLog.md                 | 12 +++----
 .../Send-TextMessagingVerificationCode.md     |  4 +--
 .../Set-ADServerSettings.md                   |  2 +-
 .../ExchangePowerShell/Set-AcceptedDomain.md  |  8 ++---
 .../Set-AccessToCustomerDataRequest.md        |  2 +-
 .../Set-ActiveSyncDeviceAccessRule.md         |  4 +--
 .../Set-ActiveSyncDeviceAutoblockThreshold.md |  6 ++--
 .../Set-ActiveSyncMailboxPolicy.md            |  4 +--
 .../Set-ActiveSyncOrganizationSettings.md     |  8 ++---
 .../Set-ActiveSyncVirtualDirectory.md         | 12 +++----
 .../Set-AddressBookPolicy.md                  | 34 ++++++++++++++++---
 .../ExchangePowerShell/Set-AddressList.md     |  4 +--
 .../Set-AdminAuditLogConfig.md                | 16 ++++-----
 97 files changed, 207 insertions(+), 183 deletions(-)

diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-OutboundConnector.md b/exchange/exchange-ps/ExchangePowerShell/Remove-OutboundConnector.md
index c2852cf820..9a4192bf4c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-OutboundConnector.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-OutboundConnector.md
@@ -31,7 +31,7 @@ Remove-OutboundConnector [-Identity] <OutboundConnectorIdParameter>
 ## DESCRIPTION
 Outbound connectors send email messages to remote domains that require specific configuration options.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-OutlookProtectionRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-OutlookProtectionRule.md
index dcfd7ccd4c..9c740ebb31 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-OutlookProtectionRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-OutlookProtectionRule.md
@@ -15,7 +15,7 @@ title: Remove-OutlookProtectionRule
 ## SYNOPSIS
 **Note**: This cmdlet is no longer supported in the cloud-based service.
 
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Remove-OutlookProtectionRule cmdlet to remove Outlook protection rules.
 
@@ -34,7 +34,7 @@ Remove-OutlookProtectionRule [-Identity] <RuleIdParameter>
 ## DESCRIPTION
 Outlook protection rules use an Active Directory Rights Management Services (AD RMS) rights template to automatically apply Information Rights Management (IRM) protection to messages before they're sent. For more information, see [Outlook protection rules](https://learn.microsoft.com/exchange/outlook-protection-rules-exchange-2013-help).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-OutlookProvider.md b/exchange/exchange-ps/ExchangePowerShell/Remove-OutlookProvider.md
index ca4e1e331e..963f8c71d9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-OutlookProvider.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-OutlookProvider.md
@@ -32,7 +32,7 @@ Remove-OutlookProvider [-Identity] <OutlookProviderIdParameter>
 ## DESCRIPTION
 The Remove-OutlookProvider cmdlet deletes the AutoDiscoverConfig object under the Global Settings object in Active Directory.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-OwaMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-OwaMailboxPolicy.md
index 0bd84f979a..5b620c8bb2 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-OwaMailboxPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-OwaMailboxPolicy.md
@@ -13,7 +13,7 @@ title: Remove-OwaMailboxPolicy
 # Remove-OwaMailboxPolicy
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Remove-OwaMailboxPolicy cmdlet to remove Outlook on the web mailbox policies from the organization.
 
@@ -31,9 +31,9 @@ Remove-OwaMailboxPolicy [-Identity] <MailboxPolicyIdParameter>
 ```
 
 ## DESCRIPTION
-Changes to Outlook on the web mailbox policies may take up to 60 minutes to take effect. In on-premises Exchange, you can force an update by restarting IIS (Stop-Service WAS -Force and Start-Service W3SVC).
+Changes to Outlook on the web mailbox policies might take up to 60 minutes to take effect. In on-premises Exchange, you can force an update by restarting IIS (Stop-Service WAS -Force and Start-Service W3SVC).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-OwaVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Remove-OwaVirtualDirectory.md
index 8eb57c6379..a124400754 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-OwaVirtualDirectory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-OwaVirtualDirectory.md
@@ -37,7 +37,7 @@ You might be required to use the Remove-OwaVirtualDirectory cmdlet in the follow
 
 Remove-OwaVirtualDirectory permanently removes an Outlook on the web virtual directory or directories. When you use this cmdlet, make sure that you don't accidentally delete the default Outlook on the web virtual directory.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-PartnerApplication.md b/exchange/exchange-ps/ExchangePowerShell/Remove-PartnerApplication.md
index 1badd61959..936b9caaf0 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-PartnerApplication.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-PartnerApplication.md
@@ -13,7 +13,7 @@ title: Remove-PartnerApplication
 # Remove-PartnerApplication
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Remove-PartnerApplication cmdlet to remove a partner application configuration.
 
@@ -34,7 +34,7 @@ You can configure partner applications such as Microsoft SharePoint to access Ex
 
 We recommend that you use the Configure-EnterprisePartnerApplication.ps1 script in the %ExchangeInstallPath%Scripts folder to configure partner applications.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-PhishSimOverridePolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-PhishSimOverridePolicy.md
index eef6fba7a1..3943fd117f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-PhishSimOverridePolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-PhishSimOverridePolicy.md
@@ -31,7 +31,7 @@ Remove-PhishSimOverridePolicy [-Identity] <PolicyIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-PolicyTipConfig.md b/exchange/exchange-ps/ExchangePowerShell/Remove-PolicyTipConfig.md
index e2011f2ab5..d20d920506 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-PolicyTipConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-PolicyTipConfig.md
@@ -13,7 +13,7 @@ title: Remove-PolicyTipConfig
 # Remove-PolicyTipConfig
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Remove-PolicyTipConfig cmdlet to remove custom data loss prevention (DLP) Policy Tips from your organization. You can't remove built-in Policy Tips.
 
@@ -30,7 +30,7 @@ Remove-PolicyTipConfig [-Identity] <PolicyTipConfigIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-PowerShellVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Remove-PowerShellVirtualDirectory.md
index 2174fd682c..72abe8d4c1 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-PowerShellVirtualDirectory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-PowerShellVirtualDirectory.md
@@ -32,7 +32,7 @@ Remove-PowerShellVirtualDirectory [-Identity] <VirtualDirectoryIdParameter>
 ## DESCRIPTION
 Although it's possible to remove a Windows PowerShell virtual directory, we recommend that you only do so at the request of Microsoft Customer Service and Support.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -43,7 +43,7 @@ Remove-PowerShellVirtualDirectory "Internal (Default Web Site)" -Confirm:$False
 
 This example removes a Windows PowerShell virtual directory without confirmation.
 
-Be careful when using the Remove-PowerShellVirtualDirectory cmdlet without confirmation. You won't be prompted before the virtual directory is deleted.
+Be careful when using the Remove-PowerShellVirtualDirectory cmdlet without confirmation. You aren't prompted before the virtual directory is deleted.
 
 ## PARAMETERS
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolder.md b/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolder.md
index c1eeb1b2cd..d3d0cdf444 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolder.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolder.md
@@ -13,7 +13,7 @@ title: Remove-PublicFolder
 # Remove-PublicFolder
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Remove-PublicFolder cmdlet to remove an existing public folder.
 
@@ -35,7 +35,7 @@ Remove-PublicFolder [-Identity] <PublicFolderIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderAdministrativePermission.md b/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderAdministrativePermission.md
index 23f93a12d8..8a8bf774bd 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderAdministrativePermission.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderAdministrativePermission.md
@@ -48,7 +48,7 @@ Remove-PublicFolderAdministrativePermission [[-Identity] <PublicFolderIdParamete
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderClientPermission.md b/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderClientPermission.md
index 89687cc43f..4d3cc811a7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderClientPermission.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderClientPermission.md
@@ -13,7 +13,7 @@ title: Remove-PublicFolderClientPermission
 # Remove-PublicFolderClientPermission
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Remove-PublicFolderClientPermission cmdlet to remove permissions from public folders.
 
@@ -31,7 +31,7 @@ Remove-PublicFolderClientPermission [-Identity] <PublicFolderIdParameter> -Acces
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderDatabase.md b/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderDatabase.md
index bdd0ea1ad5..8f6803762a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderDatabase.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderDatabase.md
@@ -31,7 +31,7 @@ Remove-PublicFolderDatabase [-Identity] <DatabaseIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 Removing a public folder database can have a broad range of serious consequences. (This is particularly true when removing the last public folder database in the organization.) For more information, see [Remove Public Folder Databases](https://learn.microsoft.com/previous-versions/office/exchange-server-2010/dd876883(v=exchg.141)).
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderMailboxMigrationRequest.md b/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderMailboxMigrationRequest.md
index 72b59a29e3..0667881178 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderMailboxMigrationRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderMailboxMigrationRequest.md
@@ -13,7 +13,7 @@ title: Remove-PublicFolderMailboxMigrationRequest
 # Remove-PublicFolderMailboxMigrationRequest
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Remove-PublicFolderMailboxMigrationRequest cmdlet to remove individual jobs from public folder migration batches that were created by using the New-MigrationBatch cmdlet.
 
@@ -41,7 +41,7 @@ Remove-PublicFolderMailboxMigrationRequest -RequestGuid <Guid> -RequestQueue <Da
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderMigrationRequest.md b/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderMigrationRequest.md
index 23185321d3..8d030b34ca 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderMigrationRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderMigrationRequest.md
@@ -45,7 +45,7 @@ Remove-PublicFolderMigrationRequest -RequestGuid <Guid> -RequestQueue <DatabaseI
 ## DESCRIPTION
 The RequestQueue and RequestGuid parameters are for debugging purposes only.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderMoveRequest.md b/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderMoveRequest.md
index 9f98237964..26486f972c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderMoveRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderMoveRequest.md
@@ -13,9 +13,9 @@ title: Remove-PublicFolderMoveRequest
 # Remove-PublicFolderMoveRequest
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
-Use the Remove-PublicFolderMoveRequest cmdlet to cancel a mailbox move initiated using the New-MoveRequest cmdlet. After the move has been finalized, you can't undo the move request.
+Use the Remove-PublicFolderMoveRequest cmdlet to cancel a mailbox move initiated using the New-MoveRequest cmdlet. After the move is finalized, you can't undo the move request.
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
@@ -43,7 +43,7 @@ Remove-PublicFolderMoveRequest -RequestGuid <Guid> -RequestQueue <DatabaseIdPara
 ## DESCRIPTION
 The RequestQueue and RequestGuid parameters are for debugging purposes only.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-QuarantinePolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-QuarantinePolicy.md
index 3eb8f8cf88..4661faef74 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-QuarantinePolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-QuarantinePolicy.md
@@ -30,7 +30,7 @@ Remove-QuarantinePolicy [-Identity] <QuarantineTagIdParameter>
 ## DESCRIPTION
 You can't remove the built-in quarantine policies named AdminOnlyAccessPolicy or DefaultFullAccessPolicy.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ReceiveConnector.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ReceiveConnector.md
index 1bacd5e932..f8720a5197 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-ReceiveConnector.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ReceiveConnector.md
@@ -32,7 +32,7 @@ Remove-ReceiveConnector [-Identity] <ReceiveConnectorIdParameter>
 ## DESCRIPTION
 Removing a Receive connector from the server might affect mail flow throughout the organization.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-RecipientPermission.md b/exchange/exchange-ps/ExchangePowerShell/Remove-RecipientPermission.md
index 5532764950..ac050e0a57 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-RecipientPermission.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-RecipientPermission.md
@@ -36,7 +36,7 @@ Remove-RecipientPermission [-Identity] <RecipientIdParameter> -AccessRights <Mul
 ## DESCRIPTION
 When a user is given SendAs permission to another user or group, the user can send messages that appear to come from the other user or group.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-RemoteDomain.md b/exchange/exchange-ps/ExchangePowerShell/Remove-RemoteDomain.md
index 77c88b69b1..a4d1dfe0c2 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-RemoteDomain.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-RemoteDomain.md
@@ -13,7 +13,7 @@ title: Remove-RemoteDomain
 # Remove-RemoteDomain
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Remove-RemoteDomain cmdlet to remove a remote domain. When you remove a remote domain, the remote domain object is deleted. Removing a remote domain doesn't disable mail flow to that domain.
 
@@ -30,7 +30,7 @@ Remove-RemoteDomain [-Identity] <RemoteDomainIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-RemoteMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Remove-RemoteMailbox.md
index 8b72bc15ab..fd6ab9e40a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-RemoteMailbox.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-RemoteMailbox.md
@@ -36,7 +36,7 @@ With the Remove-RemoteMailbox cmdlet, you can remove an on-premises mail-enabled
 
 Directory synchronization must be configured correctly for a mailbox to be removed from the service. Removal of the mailbox from the service isn't immediate and depends on the directory synchronization schedule.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -45,7 +45,7 @@ You need to be assigned permissions before you can run this cmdlet. Although thi
 Remove-RemoteMailbox "Kim Akers"
 ```
 
-This example removes the on-premises mail-enabled user Kim Akers and the associated mailbox from the service. This example assumes directory synchronization has been configured.
+This example removes the on-premises mail-enabled user Kim Akers and the associated mailbox from the service. This example assumes directory synchronization is configured.
 
 ## PARAMETERS
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ReportSubmissionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ReportSubmissionPolicy.md
index 68777847fb..37601a5812 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-ReportSubmissionPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ReportSubmissionPolicy.md
@@ -28,7 +28,7 @@ Remove-ReportSubmissionPolicy [-Identity] <ReportSubmissionPolicyIdParameter> [<
 ## DESCRIPTION
 There's only one report submission policy in an organization, and it's named DefaultReportSubmissionPolicy. You can remove the policy and then use the New-ReportSubmissionPolicy cmdlet to recreate it with the default settings.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ReportSubmissionRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ReportSubmissionRule.md
index fabd608925..40faf43a7b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-ReportSubmissionRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ReportSubmissionRule.md
@@ -31,7 +31,7 @@ Remove-ReportSubmissionRule [-Identity] <RuleIdParameter>
 ## DESCRIPTION
 To disable the report submission rule without deleting it, use the Disable-ReportSubmissionRule cmdlet.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ResubmitRequest.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ResubmitRequest.md
index 73733485fe..c85c142160 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-ResubmitRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ResubmitRequest.md
@@ -30,7 +30,7 @@ Remove-ResubmitRequest [-Identity] <ResubmitRequestIdentityParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-RetentionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-RetentionPolicy.md
index c8d5021c8d..0475a58a8f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-RetentionPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-RetentionPolicy.md
@@ -13,7 +13,7 @@ title: Remove-RetentionPolicy
 # Remove-RetentionPolicy
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Remove-RetentionPolicy cmdlet to remove a retention policy.
 
@@ -33,9 +33,9 @@ Remove-RetentionPolicy [-Identity] <MailboxPolicyIdParameter>
 ## DESCRIPTION
 Retention policies are used to apply message retention settings to folders and items in a mailbox. The Remove-RetentionPolicy cmdlet removes an existing retention policy.
 
-If you remove a retention policy that's assigned to users and they don't have another retention policy assigned, messages in those mailboxes may never expire. This may be a violation of the organization's messaging retention policies. When you attempt to remove a policy that's assigned to users, Microsoft Exchange displays a confirmation message indicating that the policy is assigned to users. Note that this message is in addition to the confirmation prompt displayed when removing a retention policy.
+If you remove a retention policy that's assigned to users and they don't have another retention policy assigned, messages in those mailboxes might never expire. This might be a violation of the organization's messaging retention policies. When you attempt to remove a policy that's assigned to users, Microsoft Exchange displays a confirmation message indicating that the policy is assigned to users. This message is in addition to the confirmation prompt displayed when removing a retention policy.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-RetentionPolicyTag.md b/exchange/exchange-ps/ExchangePowerShell/Remove-RetentionPolicyTag.md
index 782489d23e..d8d0bfdde8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-RetentionPolicyTag.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-RetentionPolicyTag.md
@@ -13,7 +13,7 @@ title: Remove-RetentionPolicyTag
 # Remove-RetentionPolicyTag
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Remove-RetentionPolicyTag cmdlet to remove a retention tag.
 
@@ -32,11 +32,11 @@ Remove-RetentionPolicyTag [-Identity] <RetentionPolicyTagIdParameter>
 ## DESCRIPTION
 Retention tags are added to a retention policy, which is applied to a mailbox.
 
-When you use the Remove-RetentionPolicyTag cmdlet to remove a retention tag, it removes the tag definition stored in Active Directory. The next time the Managed Folder Assistant runs, it processes all items that have the removed tag applied and restamps them. Depending on the number of mailboxes and messages, this process may result in significant resource consumption on all Mailbox servers that contain mailboxes with a retention policy that includes the removed tag.
+When you use the Remove-RetentionPolicyTag cmdlet to remove a retention tag, it removes the tag definition stored in Active Directory. The next time the Managed Folder Assistant runs, it processes all items that have the removed tag applied and restamps them. Depending on the number of mailboxes and messages, this process might result in significant resource consumption on all Mailbox servers that contain mailboxes with a retention policy that includes the removed tag.
 
 For more information about retention tags, see [Retention tags and retention policies in Exchange Server](https://learn.microsoft.com/Exchange/policy-and-compliance/mrm/retention-tags-and-retention-policies).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-RoleAssignmentPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-RoleAssignmentPolicy.md
index 20586d4cb2..5b564b0d0d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-RoleAssignmentPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-RoleAssignmentPolicy.md
@@ -13,7 +13,7 @@ title: Remove-RoleAssignmentPolicy
 # Remove-RoleAssignmentPolicy
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Remove-RoleAssignmentPolicy cmdlet to remove existing management role assignment policies from your organization.
 
@@ -38,7 +38,7 @@ The assignment policy you want to remove can't be assigned to any mailboxes or m
 
 For more information about assignment policies, see [Understanding management role assignment policies](https://learn.microsoft.com/exchange/understanding-management-role-assignment-policies-exchange-2013-help).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-RoleGroup.md b/exchange/exchange-ps/ExchangePowerShell/Remove-RoleGroup.md
index f23147c627..8823aa5d8b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-RoleGroup.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-RoleGroup.md
@@ -13,7 +13,7 @@ title: Remove-RoleGroup
 # Remove-RoleGroup
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Remove-RoleGroup cmdlet to remove a management role group.
 
@@ -36,11 +36,11 @@ When you remove a role group, all the management role assignments assigned manag
 
 You can't remove built-in role groups.
 
-If the ManagedBy property has been populated with role group managers, the user removing the role group must be a role group manager. Alternately, if the user is a member of the Organization Management role group or is directly or indirectly assigned the Role Management role, the BypassSecurityGroupManagerCheck switch can be used to override the security group management check.
+If the ManagedBy property is populated with role group managers, the user removing the role group must be a role group manager. Alternately, if the user is a member of the Organization Management role group or is directly or indirectly assigned the Role Management role, the BypassSecurityGroupManagerCheck switch can be used to override the security group management check.
 
 For more information about role groups, see [Understanding management role groups](https://learn.microsoft.com/exchange/understanding-management-role-groups-exchange-2013-help).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-RoleGroupMember.md b/exchange/exchange-ps/ExchangePowerShell/Remove-RoleGroupMember.md
index 7abb07e98f..a7c39c03c7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-RoleGroupMember.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-RoleGroupMember.md
@@ -13,7 +13,7 @@ title: Remove-RoleGroupMember
 # Remove-RoleGroupMember
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Remove-RoleGroupMember cmdlet to remove a member of a management role group.
 
@@ -33,13 +33,13 @@ Remove-RoleGroupMember [-Identity] <RoleGroupIdParameter> -Member <SecurityPrinc
 ## DESCRIPTION
 When you remove a member from a role group, that member can no longer manage the features made available by the role group if the role group is the only means by which the member is granted access to the feature.
 
-If the ManagedBy property has been populated with role group managers, the user removing a role group member must be a role group manager. Alternately, if the user is a member of the Organization Management role group or is directly or indirectly assigned the Role Management role, the BypassSecurityGroupManagerCheck switch can be used to override the security group management check.
+If the ManagedBy property is populated with role group managers, the user removing a role group member must be a role group manager. Alternately, if the user is a member of the Organization Management role group or is directly or indirectly assigned the Role Management role, the BypassSecurityGroupManagerCheck switch can be used to override the security group management check.
 
 If the role group is a linked role group, you can't use the Remove-RoleGroupMember cmdlet to remove members from the role group. Instead, you need to remove members from the foreign universal security group (USG) linked to the linked role group. To find the foreign USG linked to a role group, use the Get-RoleGroup cmdlet.
 
 For more information about role groups, see [Understanding management role groups](https://learn.microsoft.com/exchange/understanding-management-role-groups-exchange-2013-help).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-RoutingGroupConnector.md b/exchange/exchange-ps/ExchangePowerShell/Remove-RoutingGroupConnector.md
index 32f6baf648..9c6e3d0b0e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-RoutingGroupConnector.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-RoutingGroupConnector.md
@@ -34,7 +34,7 @@ A routing group connector is used to send and receive messages between computers
 
 The Exchange 2003 servers used as source servers for the specified routing group connector are automatically removed from the ExchangeLegacyInterop universal security group.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-RpcClientAccess.md b/exchange/exchange-ps/ExchangePowerShell/Remove-RpcClientAccess.md
index 0735dc06c7..1b204769fa 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-RpcClientAccess.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-RpcClientAccess.md
@@ -30,9 +30,9 @@ Remove-RpcClientAccess -Server <ServerIdParameter>
 ```
 
 ## DESCRIPTION
-Disabling RPC client access on a server blocks all RPC access through the specified Client Access server. Therefore, RPC clients (for example, clients running Microsoft Office Outlook 2007) with mailboxes on any mailbox databases configured to use the specified Client Access server won't be able to connect.
+Disabling RPC client access on a server blocks all RPC access through the specified Client Access server. Therefore, RPC clients (for example, clients running Microsoft Office Outlook 2007) with mailboxes on any mailbox databases configured to use the specified Client Access server can't connect.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-SafeAttachmentPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-SafeAttachmentPolicy.md
index d79cf3b777..97148431b9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-SafeAttachmentPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-SafeAttachmentPolicy.md
@@ -32,7 +32,7 @@ Remove-SafeAttachmentPolicy [-Identity] <SafeAttachmentPolicyIdParameter>
 ## DESCRIPTION
 Safe Attachments is a feature in Microsoft Defender for Office 365 that opens email attachments in a special hypervisor environment to detect malicious activity. For more information, see [Safe Attachments in Defender for Office 365](https://learn.microsoft.com/defender-office-365/safe-attachments-about).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-SafeAttachmentRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-SafeAttachmentRule.md
index 74fae37eb9..28b2b0c067 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-SafeAttachmentRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-SafeAttachmentRule.md
@@ -31,7 +31,7 @@ Remove-SafeAttachmentRule [-Identity] <RuleIdParameter>
 ## DESCRIPTION
 Safe Attachments is a feature in Microsoft Defender for Office 365 that opens email attachments in a special hypervisor environment to detect malicious activity. For more information, see [Safe Attachments in Defender for Office 365](https://learn.microsoft.com/defender-office-365/safe-attachments-about).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-SafeLinksPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-SafeLinksPolicy.md
index e4fcd71186..40c1b76e66 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-SafeLinksPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-SafeLinksPolicy.md
@@ -34,7 +34,7 @@ You can't remove the default Safe Links policy (the policy where the IsDefault p
 
 Safe Links is a feature in Microsoft Defender for Office 365 that checks links in email messages to see if they lead to malicious web sites. When a user clicks a link in a message, the URL is temporarily rewritten and checked against a list of known, malicious web sites. Safe Links includes the URL trace reporting feature to help determine who has clicked through to a malicious web site.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-SafeLinksRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-SafeLinksRule.md
index a8c412145f..3fd4cb00d9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-SafeLinksRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-SafeLinksRule.md
@@ -31,7 +31,7 @@ Remove-SafeLinksRule [-Identity] <RuleIdParameter>
 ## DESCRIPTION
 Safe Links is a feature in Microsoft Defender for Office 365 that checks links in email messages to see if they lead to malicious web sites. When a user clicks a link in a message, the URL is temporarily rewritten and checked against a list of known, malicious web sites. Safe Links includes the URL trace reporting feature to help determine who has clicked through to a malicious web site.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-SearchDocumentFormat.md b/exchange/exchange-ps/ExchangePowerShell/Remove-SearchDocumentFormat.md
index fd539a83c6..f0db065269 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-SearchDocumentFormat.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-SearchDocumentFormat.md
@@ -30,9 +30,11 @@ Remove-SearchDocumentFormat [-Identity] <SearchDocumentFormatId>
 ```
 
 ## DESCRIPTION
-After running the Remove-SearchDocumentFormat cmdlet, your must run the following cmdlet to restart the search service. There will be a brief search outage.
+After running the Remove-SearchDocumentFormat cmdlet, you must run the following cmdlet to restart the search service. There will be a brief search outage.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+`Restart-Service HostControllerService`
+
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-SecOpsOverridePolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-SecOpsOverridePolicy.md
index 878683aaa8..a8094fee23 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-SecOpsOverridePolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-SecOpsOverridePolicy.md
@@ -31,7 +31,7 @@ Remove-SecOpsOverridePolicy [-Identity] <PolicyIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-SendConnector.md b/exchange/exchange-ps/ExchangePowerShell/Remove-SendConnector.md
index ef7ec0522d..731a453bec 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-SendConnector.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-SendConnector.md
@@ -32,9 +32,9 @@ Remove-SendConnector [-Identity] <SendConnectorIdParameter>
 ## DESCRIPTION
 The Remove-SendConnector cmdlet deletes the object and the configuration settings for the Send connector.
 
-Although a Send connector is configured locally in the Transport service on a Mailbox server or on an Edge server, deleting a Send connector may affect mail flow throughout the organization.
+Although a Send connector is configured locally in the Transport service on a Mailbox server or on an Edge server, deleting a Send connector might affect mail flow throughout the organization.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ServerMonitoringOverride.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ServerMonitoringOverride.md
index 8797d26742..d4d2e18a65 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-ServerMonitoringOverride.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ServerMonitoringOverride.md
@@ -15,7 +15,7 @@ title: Remove-ServerMonitoringOverride
 ## SYNOPSIS
 This cmdlet is available only in on-premises Exchange.
 
-Use the Remove-ServerMonitoringOverride cmdlet to remove a managed availability local server override that has been configured for a probe, monitor or responder.
+Use the Remove-ServerMonitoringOverride cmdlet to remove a managed availability local server override that is configured for a probe, monitor or responder.
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
@@ -29,7 +29,7 @@ Remove-ServerMonitoringOverride [-Identity] <String> -ItemType <MonitoringItemTy
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ServicePrincipal.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ServicePrincipal.md
index 720e5bb4b6..c335f5b35f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-ServicePrincipal.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ServicePrincipal.md
@@ -29,7 +29,7 @@ Remove-ServicePrincipal [-Identity] <ServicePrincipalIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-SettingOverride.md b/exchange/exchange-ps/ExchangePowerShell/Remove-SettingOverride.md
index f1f2727920..be10212190 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-SettingOverride.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-SettingOverride.md
@@ -34,7 +34,7 @@ Remove-SettingOverride [-Identity] <SettingOverrideIdParameter>
 ## DESCRIPTION
 Setting overrides configure and store Exchange server customizations in Active Directory. The settings can be organization-wide or server-specific, and they persist in Active Directory across Exchange Cumulative Updates (CUs). Exchange customizations in web.config or exe.config XML application configuration files are server-specific, and they're lost when you install the next Exchange CU.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-SharingPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-SharingPolicy.md
index 2422bc4285..719d9621a8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-SharingPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-SharingPolicy.md
@@ -13,7 +13,7 @@ title: Remove-SharingPolicy
 # Remove-SharingPolicy
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Remove-SharingPolicy cmdlet to remove a sharing policy. Before you can remove a sharing policy, you must ensure that no mailbox users are provisioned to use that policy.
 
@@ -30,7 +30,7 @@ Remove-SharingPolicy [-Identity] <SharingPolicyIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-SiteMailboxProvisioningPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-SiteMailboxProvisioningPolicy.md
index f896036b30..78406d422b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-SiteMailboxProvisioningPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-SiteMailboxProvisioningPolicy.md
@@ -34,7 +34,7 @@ Remove-SiteMailboxProvisioningPolicy [-Identity] <MailboxPolicyIdParameter>
 ## DESCRIPTION
 You can't delete the default site mailbox provisioning policy. You need to create a new default policy by using the New-SiteMailboxProvisioningPolicy cmdlet or designate an existing policy as the default policy by using the Set-SiteMailboxProvisioningPolicy cmdlet.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-StoreMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Remove-StoreMailbox.md
index eced30b9b1..7f22253212 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-StoreMailbox.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-StoreMailbox.md
@@ -37,7 +37,7 @@ A mailbox is marked as Disabled immediately after the Disable-Mailbox or Remove-
 
 To view disabled mailboxes, run the Get-MailboxStatistics cmdlet against a database using the property DisconnectReason with a value of Disabled.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-SweepRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-SweepRule.md
index 35879232b1..3815b75020 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-SweepRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-SweepRule.md
@@ -13,7 +13,7 @@ title: Remove-SweepRule
 # Remove-SweepRule
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Remove-SweepRule cmdlet to remove Sweep rules from mailboxes.
 
@@ -31,7 +31,7 @@ Remove-SweepRule [-Identity] <SweepRuleIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-SyncMailPublicFolder.md b/exchange/exchange-ps/ExchangePowerShell/Remove-SyncMailPublicFolder.md
index 76b893ba88..5b7c3b265b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-SyncMailPublicFolder.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-SyncMailPublicFolder.md
@@ -13,7 +13,7 @@ title: Remove-SyncMailPublicFolder
 # Remove-SyncMailPublicFolder
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 The Remove-SyncMailPublicFolder cmdlet is used by the Sync-MailPublicFolders.ps1 script to remove mail-enabled public folder recipient objects from Exchange Online (the script synchronizes mail-enabled public folder objects from the source on-premises Exchange organization to Exchange Online). Don't use this cmdlet unless you are directed to do so by Microsoft Customer Service and Support or by specific documentation.
 
@@ -32,7 +32,7 @@ Remove-SyncMailPublicFolder [-Identity] <MailPublicFolderIdParameter>
 ## DESCRIPTION
 This cmdlet is only used by the Sync-MailPublicFolders.ps1 script. Don't run this cmdlet in the Exchange Management Shell or in Exchange Online PowerShell.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-SystemMessage.md b/exchange/exchange-ps/ExchangePowerShell/Remove-SystemMessage.md
index 0ee365aefb..159bf7e9fa 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-SystemMessage.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-SystemMessage.md
@@ -32,7 +32,7 @@ Remove-SystemMessage [-Identity] <SystemMessageIdParameter>
 ## DESCRIPTION
 You can't remove a default system message that's included with Exchange. When you remove a custom system message, the message text reverts to the text in the corresponding system message (if any) that's included with Exchange.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-TenantAllowBlockListItems.md b/exchange/exchange-ps/ExchangePowerShell/Remove-TenantAllowBlockListItems.md
index 7bf6419833..98cf2e12da 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-TenantAllowBlockListItems.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-TenantAllowBlockListItems.md
@@ -38,7 +38,7 @@ Remove-TenantAllowBlockListItems -Ids <String[]> -ListType <ListType>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -139,7 +139,7 @@ Accept wildcard characters: False
 The ListSubType specifies further specifies the type of entry that you want to remove. Valid values are:
 
 - AdvancedDelivery: Use this value for phishing simulation URLs.
-- Tenant: This is the default value.
+- Tenant: This value is the default.
 
 ```yaml
 Type: ListSubType
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-TenantAllowBlockListSpoofItems.md b/exchange/exchange-ps/ExchangePowerShell/Remove-TenantAllowBlockListSpoofItems.md
index be8e893e78..8e2392eaba 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-TenantAllowBlockListSpoofItems.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-TenantAllowBlockListSpoofItems.md
@@ -31,7 +31,7 @@ Remove-TenantAllowBlockListSpoofItems [-Identity] <HostedConnectionFilterPolicyI
 ## DESCRIPTION
 This cmdlet removes spoof pairs (the combination of the spoofed user and the sending infrastructure) from the Tenant Allow/Block List.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ThrottlingPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ThrottlingPolicy.md
index 13919e09b3..34b4dbf066 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-ThrottlingPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ThrottlingPolicy.md
@@ -35,7 +35,7 @@ You can't remove the default client throttling policy. Also, you can't remove a
 
 For more information about how to control the resources consumed by individual users, see [User workload management in Exchange Server](https://learn.microsoft.com/Exchange/server-health/workload-management).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-TransportRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-TransportRule.md
index 974d3d827d..6efbe05339 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-TransportRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-TransportRule.md
@@ -13,7 +13,7 @@ title: Remove-TransportRule
 # Remove-TransportRule
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Remove-TransportRule cmdlet to remove transport rules (mail flow rules) from your organization.
 
@@ -34,7 +34,7 @@ On Mailbox servers, this cmdlet removes the rule from Active Directory. On an Ed
 
 To temporarily disable a transport rule without removing it, use the Disable-TransportRule cmdlet instead.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-UMAutoAttendant.md b/exchange/exchange-ps/ExchangePowerShell/Remove-UMAutoAttendant.md
index 0d1717b887..3fd7891ce3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-UMAutoAttendant.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-UMAutoAttendant.md
@@ -34,7 +34,7 @@ The Remove-UMAutoAttendant cmdlet deletes an existing UM auto attendant from Act
 
 After this task is completed, the UM auto attendant is removed from Active Directory.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-UMCallAnsweringRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-UMCallAnsweringRule.md
index 493243ce17..26d0991f60 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-UMCallAnsweringRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-UMCallAnsweringRule.md
@@ -31,11 +31,11 @@ Remove-UMCallAnsweringRule [-Identity] <UMCallAnsweringRuleIdParameter>
 ```
 
 ## DESCRIPTION
-The Remove-UMCallAnsweringRule cmdlet removes an existing UM call answering rule that has been created and stored in a UM-enabled user's mailbox. When you remove an existing call answering rule, all of the remaining call answering rules are still processed in order of their priority.
+The Remove-UMCallAnsweringRule cmdlet removes an existing UM call answering rule that is created and stored in a UM-enabled user's mailbox. When you remove an existing call answering rule, all of the remaining call answering rules are still processed in order of their priority.
 
 After this task is completed, the cmdlet sets the parameters and the values specified.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-UMDialPlan.md b/exchange/exchange-ps/ExchangePowerShell/Remove-UMDialPlan.md
index 9891da4d6d..8f422da9ef 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-UMDialPlan.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-UMDialPlan.md
@@ -34,7 +34,7 @@ The Remove-UMDialPlan cmdlet deletes an existing UM dial plan from Active Direct
 
 After this task is completed, the UM dial plan is removed from Active Directory.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-UMHuntGroup.md b/exchange/exchange-ps/ExchangePowerShell/Remove-UMHuntGroup.md
index 5a6e163d62..6966e94209 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-UMHuntGroup.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-UMHuntGroup.md
@@ -34,7 +34,7 @@ The Remove-UMHuntGroup cmdlet deletes an existing UM hunt group from Active Dire
 
 After this task is completed, the UM hunt group is removed from Active Directory.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-UMIPGateway.md b/exchange/exchange-ps/ExchangePowerShell/Remove-UMIPGateway.md
index f0bb270293..2eb54404fe 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-UMIPGateway.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-UMIPGateway.md
@@ -36,7 +36,7 @@ The Remove-UMIPGateway cmdlet should be run only by an administrator who fully u
 
 After this task is completed, the UM IP gateway is removed from Active Directory.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-UMMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-UMMailboxPolicy.md
index 6e1dbd4616..47622239c9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-UMMailboxPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-UMMailboxPolicy.md
@@ -34,7 +34,7 @@ The Remove-UMMailboxPolicy cmdlet deletes or removes a UM mailbox policy. If the
 
 After this task is completed, the UM mailbox policy is removed from Active Directory.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-UnifiedGroup.md b/exchange/exchange-ps/ExchangePowerShell/Remove-UnifiedGroup.md
index cbccda7b2c..28b72dc892 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-UnifiedGroup.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-UnifiedGroup.md
@@ -34,7 +34,7 @@ Remove-UnifiedGroup [-Identity] <UnifiedGroupIdParameter>
 ## DESCRIPTION
 Microsoft 365 Groups are group objects that are available across Microsoft 365 services.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-UnifiedGroupLinks.md b/exchange/exchange-ps/ExchangePowerShell/Remove-UnifiedGroupLinks.md
index afdf8598ab..494ea656fd 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-UnifiedGroupLinks.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-UnifiedGroupLinks.md
@@ -34,7 +34,7 @@ Remove-UnifiedGroupLinks [-Identity] <UnifiedGroupIdParameter> -Links <Recipient
 ## DESCRIPTION
 Microsoft 365 Groups are group objects that are available across Microsoft 365 services.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-UserPhoto.md b/exchange/exchange-ps/ExchangePowerShell/Remove-UserPhoto.md
index ab41f0e36c..7fdc01f89c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-UserPhoto.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-UserPhoto.md
@@ -50,9 +50,9 @@ Remove-UserPhoto [-Identity] <MailboxIdParameter>
 Use the Remove-UserPhoto cmdlet to delete the user photo currently associated with a user's account. This cmdlet removes the photo from user's Exchange mailbox root.
 In on-premises Exchange, it also removes the user's photo from their Active Directory account. Administrators can also use the Exchange admin center (EAC) to delete user photos by accessing the Options page in the user's mailbox in Outlook on the web.
 
-**Notes**: Changes to the user photo won't appear in SharePoint until the affected user visits their profile page (My Site) or any SharePoint page that shows their large thumbnail image.
+**Notes**: Changes to the user photo don't appear in SharePoint until the affected user visits their profile page (My Site) or any SharePoint page that shows their large thumbnail image.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-VivaModuleFeaturePolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-VivaModuleFeaturePolicy.md
index fd0cb8ce9c..fe576b5f2d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-VivaModuleFeaturePolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-VivaModuleFeaturePolicy.md
@@ -15,7 +15,7 @@ title: Remove-VivaModuleFeaturePolicy
 ## SYNOPSIS
 This cmdlet is available only in the Exchange Online PowerShell module v3.2.0 or later. For more information, see [About the Exchange Online PowerShell module](https://aka.ms/exov3-module).
 
-Use the Remove-VivaModuleFeaturePolicy cmdlet to delete an access policy for a feature in a Viva module in Viva. Once you delete a policy, the policy is permanently deleted. You cannot undo the deletion.
+Use the Remove-VivaModuleFeaturePolicy cmdlet to delete an access policy for a feature in a Viva module in Viva. Once you delete a policy, the policy is permanently deleted. You can't undo the deletion.
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-WebServicesVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Remove-WebServicesVirtualDirectory.md
index 4a2b358ce1..146c97aa5f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-WebServicesVirtualDirectory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-WebServicesVirtualDirectory.md
@@ -33,7 +33,7 @@ Remove-WebServicesVirtualDirectory [-Identity] <VirtualDirectoryIdParameter>
 ## DESCRIPTION
 You can remove the default Exchange Web Services virtual directory or another Exchange Web Services virtual directory.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-X400AuthoritativeDomain.md b/exchange/exchange-ps/ExchangePowerShell/Remove-X400AuthoritativeDomain.md
index 4e966c4f48..d15a9671e2 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-X400AuthoritativeDomain.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-X400AuthoritativeDomain.md
@@ -30,7 +30,7 @@ Remove-X400AuthoritativeDomain [-Identity] <X400AuthoritativeDomainIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Reset-ProvisioningCache.md b/exchange/exchange-ps/ExchangePowerShell/Reset-ProvisioningCache.md
index 6eda0f1f75..304b16a5f9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Reset-ProvisioningCache.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Reset-ProvisioningCache.md
@@ -47,7 +47,7 @@ The Reset-ProvisioningCache cmdlet is for diagnostic purposes only and is rarely
 
 The Reset-ProvisioningCache cmdlet clears the Windows PowerShell provisioning cache of frequently used Active Directory objects. To reduce Active Directory requests, a provisioning cache is initialized in each Windows PowerShell runspace and is used to cache common objects that are frequently used by cmdlets and provisioning handlers. During Exchange cmdlet execution, the provisioning cache loads configuration objects from Active Directory to help run a cmdlet. For example, when you create a mailbox, the New-Mailbox cmdlet obtains properties from Active Directory. When running cmdlets, configuration objects such as database containers, administrative role groups, and LegacyDNs are retrieved from Active Directory. Because these types of objects are stable and don't change for months or years after they're created, they're stored in the provisioning cache used by Windows PowerShell. This increases provisioning efficiency and significantly improves cmdlet performance.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -191,7 +191,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-The Organizations parameter specifies the organizations that the provisioning cache will be reset. This parameter is used in multi-tenant deployments.
+The Organizations parameter specifies the organizations where the provisioning cache is reset. Use this parameter in multi-tenant deployments.
 
 ```yaml
 Type: MultiValuedProperty
diff --git a/exchange/exchange-ps/ExchangePowerShell/Restore-DatabaseAvailabilityGroup.md b/exchange/exchange-ps/ExchangePowerShell/Restore-DatabaseAvailabilityGroup.md
index ae01926758..d57df551a4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Restore-DatabaseAvailabilityGroup.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Restore-DatabaseAvailabilityGroup.md
@@ -45,7 +45,7 @@ The Restore-DatabaseAvailabilityGroup cmdlet performs several operations that af
 - Forcibly evicts the servers listed on the StoppedMailboxServers list from the DAG's cluster, thereby reestablishing quorum for the cluster enabling the surviving DAG members to start and provide service.
 - Configures the DAG to use the alternate witness server if there is an even number of surviving DAG members, or a single surviving DAG member.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Restore-DetailsTemplate.md b/exchange/exchange-ps/ExchangePowerShell/Restore-DetailsTemplate.md
index bfb2fae14f..c535b125f8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Restore-DetailsTemplate.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Restore-DetailsTemplate.md
@@ -32,7 +32,7 @@ Restore-DetailsTemplate [-Identity] <DetailsTemplateIdParameter>
 ## DESCRIPTION
 Details templates can't be created or deleted, but this task restores the specified template to its default state. All user changes are lost.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Restore-Mailbox.md b/exchange/exchange-ps/ExchangePowerShell/Restore-Mailbox.md
index acdecb4511..88fdd90071 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Restore-Mailbox.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Restore-Mailbox.md
@@ -49,7 +49,7 @@ Restore-Mailbox [-Identity] <MailboxIdParameter> -RecoveryDatabase <DatabaseIdPa
 ## DESCRIPTION
 The Restore-Mailbox cmdlet copies end-user data from any server running Microsoft Exchange Server 2010 to a mailbox on an Exchange 2010 Mailbox server in the same organization that has adequate space and resources to support the mailbox. The Restore-Mailbox cmdlet can only use disconnected mailboxes on a server as a source of data, and the cmdlet can only use connected mailboxes as a target for data.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -295,7 +295,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010
 
-The EndDate parameter specifies the end date for filtering content that will be exported from the source mailbox. Only items in the mailbox whose date is prior to the end date are exported. When you enter a specific date, use the short date format defined in the Regional Options settings configured on the local computer. For example, if your computer is configured to use the short date format MM/dd/yyyy, enter 03/01/2010 to specify March 1, 2010.
+The EndDate parameter specifies the end date for filtering content to be exported from the source mailbox. Only items in the mailbox whose date is prior to the end date are exported. When you enter a specific date, use the short date format defined in the Regional Options settings configured on the local computer. For example, if your computer is configured to use the short date format MM/dd/yyyy, enter 03/01/2010 to specify March 1, 2010.
 
 ```yaml
 Type: DateTime
@@ -475,9 +475,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010
 
-The ValidateOnly switch tells the command to evaluate the conditions and requirements necessary to perform the operation, and then report whether the operation will succeed or fail. You don't need to specify a value with this switch.
-
-No changes are made when you use this switch.
+The ValidateOnly switch specifies whether to evaluate the potential success or failure of the command without making changes. You don't need to specify a value with this switch.
 
 ```yaml
 Type: SwitchParameter
diff --git a/exchange/exchange-ps/ExchangePowerShell/Restore-RecoverableItems.md b/exchange/exchange-ps/ExchangePowerShell/Restore-RecoverableItems.md
index cd4e7247c4..7dfbf5787e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Restore-RecoverableItems.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Restore-RecoverableItems.md
@@ -13,7 +13,7 @@ title: Restore-RecoverableItems
 # Restore-RecoverableItems
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Restore-RecoverableItems items cmdlet to restore deleted items in mailboxes. You use the Get-RecoverableItems cmdlet to find the deleted items to recover.
 
@@ -58,7 +58,7 @@ Restore-RecoverableItems -Identity <GeneralMailboxOrMailUserIdParameter[]>
 ## DESCRIPTION
 Items are restored to the original folder location if the information is available for the item. If the information can't be found, the item is restored to the default folder for the item type (Inbox for messages, Calendar for meetings and appointments, etc.).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -322,7 +322,7 @@ This parameter is available only in the cloud-based service.
 
 The RestoreTargetFolder parameter specifies the top-level folder in which to restore data. If you don't specify this parameter, the command restores folders to the top of the folder structure in the target mailbox or archive. Content is merged under existing folders, and new folders are created if they don't already exist in the target folder structure.
 
-This parameter is available only on primary mailboxes and is ignored on archive mailboxes. A destination folder will be created if it does not exist. Valid paths are:
+This parameter is available only on primary mailboxes and is ignored on archive mailboxes. A destination folder is created if it does not exist. Valid paths are:
 
 - `/`
 - `/folder1`
@@ -330,7 +330,7 @@ This parameter is available only on primary mailboxes and is ignored on archive
 - `folder1`
 - `folder1/folder2`
 
-The preceding or trailing `/` will be ignored. Then, it will be treated as the relative path of the IPM sub-tree: `/Top Of Information Store`.
+The preceding or trailing `/` are ignored. Then, it's treated as the relative path of the IPM sub-tree: `/Top Of Information Store`.
 
 ```yaml
 Type: String
diff --git a/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxDatabaseCopy.md b/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxDatabaseCopy.md
index 1403d54b10..645c002cfe 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxDatabaseCopy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxDatabaseCopy.md
@@ -45,7 +45,7 @@ Resume-MailboxDatabaseCopy [-Identity] <DatabaseCopyIdParameter>
 ## DESCRIPTION
 The Resume-MailboxDatabaseCopy cmdlet resumes replication and replay from a suspended state. If a database copy was suspended without administrator intervention, it's because the database copy is in a bad state. You can use the Get-MailboxDatabaseCopyStatus cmdlet to see if there are any messages indicating a failure. If the copy of the database is in a bad state, resuming the copy causes replication to fail and the mailbox database copy to return to a suspended state.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxExportRequest.md b/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxExportRequest.md
index e8b277aa9d..9dd5908f7a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxExportRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxExportRequest.md
@@ -34,7 +34,7 @@ Resume-MailboxExportRequest [-Identity] <MailboxExportRequestIdParameter>
 ## DESCRIPTION
 The Resume-MailboxExportRequest cmdlet can be pipelined with the Get-MailboxExportRequest cmdlet.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxImportRequest.md b/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxImportRequest.md
index 298495c2a6..785786b9af 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxImportRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxImportRequest.md
@@ -13,7 +13,7 @@ title: Resume-MailboxImportRequest
 # Resume-MailboxImportRequest
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Resume-MailboxImportRequest cmdlet to resume an import request that was suspended or failed.
 
@@ -36,7 +36,7 @@ Resume-MailboxImportRequest [-Identity] <MailboxImportRequestIdParameter>
 ## DESCRIPTION
 This cmdlet can be pipelined with the Get-MailboxImportRequest cmdlet.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxRestoreRequest.md b/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxRestoreRequest.md
index 83322f5be6..fad77ae856 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxRestoreRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxRestoreRequest.md
@@ -13,7 +13,7 @@ title: Resume-MailboxRestoreRequest
 # Resume-MailboxRestoreRequest
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Resume-MailboxRestoreRequest cmdlet to resume a restore request that was suspended or failed.
 
@@ -30,7 +30,7 @@ Resume-MailboxRestoreRequest [-Identity] <MailboxRestoreRequestIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Resume-Message.md b/exchange/exchange-ps/ExchangePowerShell/Resume-Message.md
index 2f95ea5a15..0e3a1e81b7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Resume-Message.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Resume-Message.md
@@ -41,7 +41,7 @@ Resume-Message [-Identity] <MessageIdentity>
 ## DESCRIPTION
 A message being sent to multiple recipients might be located in multiple queues. If you specify an Identity parameter, the message is resumed in a single queue if that identity matches only a single message. If the identity matches more than one message, you receive an error. To resume a message in more than one queue in a single operation, you must use the Filter parameter.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -54,7 +54,7 @@ This example resumes delivery of all messages in a suspended state and for which
 
 - The messages were sent by the sender kweku@contoso.com.
 - The messages are queued on the server Server1.
-- The messages will expire before 15:00 on January 5, 2018.
+- The messages expire before 15:00 on January 5, 2018.
 
 ## PARAMETERS
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Resume-MoveRequest.md b/exchange/exchange-ps/ExchangePowerShell/Resume-MoveRequest.md
index f03468c869..b1659f57e9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Resume-MoveRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Resume-MoveRequest.md
@@ -13,9 +13,9 @@ title: Resume-MoveRequest
 # Resume-MoveRequest
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
-Use the Resume-MoveRequest cmdlet to resume a move request that has been suspended or has failed.
+Use the Resume-MoveRequest cmdlet to resume a move request that is suspended or has failed.
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
@@ -32,7 +32,7 @@ Resume-MoveRequest [-Identity] <MoveRequestIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Resume-PublicFolderMigrationRequest.md b/exchange/exchange-ps/ExchangePowerShell/Resume-PublicFolderMigrationRequest.md
index 0ed306d912..bd11ab1149 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Resume-PublicFolderMigrationRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Resume-PublicFolderMigrationRequest.md
@@ -32,7 +32,7 @@ Resume-PublicFolderMigrationRequest [-Identity] <PublicFolderMigrationRequestIdP
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Resume-PublicFolderMoveRequest.md b/exchange/exchange-ps/ExchangePowerShell/Resume-PublicFolderMoveRequest.md
index 7fa861fda1..3573fecc7e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Resume-PublicFolderMoveRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Resume-PublicFolderMoveRequest.md
@@ -15,7 +15,7 @@ title: Resume-PublicFolderMoveRequest
 ## SYNOPSIS
 This cmdlet is available only in on-premises Exchange.
 
-Use the Resume-PublicFolderMoveRequest cmdlet to resume a public folder move request that has been suspended or has failed.
+Use the Resume-PublicFolderMoveRequest cmdlet to resume a public folder move request that is suspended or has failed.
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
@@ -30,7 +30,7 @@ Resume-PublicFolderMoveRequest [-Identity] <PublicFolderMoveRequestIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Resume-PublicFolderReplication.md b/exchange/exchange-ps/ExchangePowerShell/Resume-PublicFolderReplication.md
index fdedc6a3ae..a5ee4bc606 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Resume-PublicFolderReplication.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Resume-PublicFolderReplication.md
@@ -29,7 +29,7 @@ Resume-PublicFolderReplication [-Confirm]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Resume-Queue.md b/exchange/exchange-ps/ExchangePowerShell/Resume-Queue.md
index 7d18b6c74d..fcd4ceaf1c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Resume-Queue.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Resume-Queue.md
@@ -41,7 +41,7 @@ Resume-Queue [-Identity] <QueueIdentity>
 ## DESCRIPTION
 If you use the Identity parameter, the queue is resumed only if that identity matches a single queue. If the identity matches more than one queue, you receive an error. To resume more than one queue in a single operation, you must use the Filter parameter.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Retry-Queue.md b/exchange/exchange-ps/ExchangePowerShell/Retry-Queue.md
index 42164baa7f..20b8cbb918 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Retry-Queue.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Retry-Queue.md
@@ -43,7 +43,7 @@ Retry-Queue [-Identity] <QueueIdentity>
 ## DESCRIPTION
 The Retry-Queue cmdlet forces a connection attempt for a queue that has a status of Retry. The cmdlet establishes a connection to the next hop if possible. If a connection isn't established, a new retry time is set. To use this command to retry delivery of messages in the Unreachable queue, you must include the Resubmit parameter.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Rotate-DkimSigningConfig.md b/exchange/exchange-ps/ExchangePowerShell/Rotate-DkimSigningConfig.md
index 894b736a5b..14fd8444d3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Rotate-DkimSigningConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Rotate-DkimSigningConfig.md
@@ -30,7 +30,7 @@ Rotate-DkimSigningConfig [-Identity] <DkimSigningConfigIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Search-AdminAuditLog.md b/exchange/exchange-ps/ExchangePowerShell/Search-AdminAuditLog.md
index ead5224ff7..a1fe3fddee 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Search-AdminAuditLog.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Search-AdminAuditLog.md
@@ -16,7 +16,7 @@ title: Search-AdminAuditLog
 > [!NOTE]
 > This cmdlet will be deprecated in the cloud-based service. To access audit log data, use the Search-UnifiedAuditLog cmdlet. For more information, see this blog post: <https://aka.ms/AdminAuditCmdletBlog>.
 
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Search-AdminAuditLog cmdlet to search the contents of the administrator audit log. Administrator audit logging records when a user or administrator makes a change in your organization (in the Exchange admin center or by using cmdlets).
 
@@ -45,11 +45,11 @@ If you run the Search-AdminAuditLog cmdlet without any parameters, up to 1,000 l
 
 In Exchange Online PowerShell, if you don't use the StartDate or EndDate parameters, only results from the last 14 days are returned.
 
-In Exchange Online PowerShell, data is available for the last 90 days. You can enter dates older than 90 days, but only data from the last 90 days will be returned.
+In Exchange Online PowerShell, data is available for the last 90 days. You can enter dates older than 90 days, but only data from the last 90 days are returned.
 
 For more information about the structure and properties of the audit log, see [Administrator audit log structure](https://learn.microsoft.com/Exchange/policy-and-compliance/admin-audit-logging/log-structure).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -215,7 +215,7 @@ The ObjectIds parameter filters the results by the object that was modified (the
 - Canonical distinguished name (for example, contoso.com/Users/Akia Al-Zuhairi)
 - Public folder identity (for example, \\Engineering\\Customer Discussion)
 
-You'll likely need to use other filtering parameters on this cmdlet to narrow down the results and identify the types of objects that you're interested in. In the results of this cmdlet, this property is named **ObjectModified**.
+You likely need to use other filtering parameters on this cmdlet to narrow down the results and identify the types of objects that you're interested in. In the results of this cmdlet, this property is named **ObjectModified**.
 
 You can enter multiple values separated by commas. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Search-Mailbox.md b/exchange/exchange-ps/ExchangePowerShell/Search-Mailbox.md
index c2be455ddb..31efc27c8a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Search-Mailbox.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Search-Mailbox.md
@@ -348,7 +348,7 @@ The LogLevel parameter specifies the logging level for the search. It can have o
 
 The default log level is Basic.
 
-When you included this parameter, an email message is created and sent to the mailbox specified by the TargetMailbox parameter. The log file (which is a CSV-formatted file named Search Results.csv) is attached to this email message, and will be located in the folder specified by the TargetFolder parameter. The log file contains a row for each message that's included in the search results when you run the Search-Mailbox cmdlet.
+When you included this parameter, an email message is created and sent to the mailbox specified by the TargetMailbox parameter. The log file (which is a CSV-formatted file named Search Results.csv) is attached to this email message, and is located in the folder specified by the TargetFolder parameter. The log file contains a row for each message that's included in the search results when you run the Search-Mailbox cmdlet.
 
 ```yaml
 Type: LoggingLevel
diff --git a/exchange/exchange-ps/ExchangePowerShell/Search-MailboxAuditLog.md b/exchange/exchange-ps/ExchangePowerShell/Search-MailboxAuditLog.md
index ec79d9383b..8a20ce8c36 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Search-MailboxAuditLog.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Search-MailboxAuditLog.md
@@ -16,7 +16,7 @@ title: Search-MailboxAuditLog
 > [!NOTE]
 > This cmdlet will be deprecated in the cloud-based service. To access audit log data, use the Search-UnifiedAuditLog cmdlet. For more information, see this blog post: <https://aka.ms/AuditCmdletBlog>.
 
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Search-MailboxAuditLog cmdlet to search mailbox audit log entries matching the specified search terms.
 
@@ -62,7 +62,7 @@ The Search-MailboxAuditLog cmdlet performs a synchronous search of mailbox audit
 
 In multi-geo environments, when you run this cmdlet in a different region from the mailbox that you're trying to search, you might receive the error, "An error occurred while trying to access the audit log." In this scenario, you need to anchor the PowerShell session to a user in the same region as the mailbox as described in [Connect directly to a geo location using Exchange Online PowerShell](https://learn.microsoft.com/microsoft-365/enterprise/administering-exchange-online-multi-geo#connect-directly-to-a-geo-location-using-exchange-online-powershell).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -166,7 +166,7 @@ The ExternalAccess parameter specifies whether to return only audit log entries
 
 $true: Audit log entries for mailbox access by external users or Microsoft datacenter administrators are returned.
 
-$false: Audit log entries for mailbox access by external users or Microsoft datacenter administrators are ignored. This is the default value.
+$false: Audit log entries for mailbox access by external users or Microsoft datacenter administrators are ignored. This value is the default.
 
 ```yaml
 Type: Boolean
diff --git a/exchange/exchange-ps/ExchangePowerShell/Search-MessageTrackingReport.md b/exchange/exchange-ps/ExchangePowerShell/Search-MessageTrackingReport.md
index d1f91cda9d..87a469ee90 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Search-MessageTrackingReport.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Search-MessageTrackingReport.md
@@ -57,7 +57,7 @@ Search-MessageTrackingReport [-Identity] <MailboxIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -235,7 +235,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
 
-The MessageId parameter filters the results by the Message-ID header field of the message. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which may include angle brackets) and enclose the value in quotation marks (for example, "<d9683b4c-127b-413a-ae2e-fa7dfb32c69d@contoso.com>").
+The MessageId parameter filters the results by the Message-ID header field of the message. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which might include angle brackets) and enclose the value in quotation marks (for example, "<d9683b4c-127b-413a-ae2e-fa7dfb32c69d@contoso.com>").
 
 ```yaml
 Type: String
diff --git a/exchange/exchange-ps/ExchangePowerShell/Search-UnifiedAuditLog.md b/exchange/exchange-ps/ExchangePowerShell/Search-UnifiedAuditLog.md
index c468fec3d7..6c403ffeeb 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Search-UnifiedAuditLog.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Search-UnifiedAuditLog.md
@@ -48,13 +48,13 @@ The Search-UnifiedAuditLog cmdlet is available in Exchange Online PowerShell. Yo
 
 If you want to programmatically download data from the Microsoft 365 audit log, we recommend that you use the Microsoft 365 Management Activity API instead of using the Search-UnifiedAuditLog cmdlet in a PowerShell script. The Microsoft 365 Management Activity API is a REST web service that you can use to develop operations, security, and compliance monitoring solutions for your organization. For more information, see [Management Activity API reference](https://learn.microsoft.com/office/office-365-management-api/office-365-management-activity-api-reference).
 
-This cmdlet is available in Office 365 operated by 21Vianet, but it won't return any results.
+This cmdlet is available in Office 365 operated by 21Vianet, but it doesn't return any results.
 
 The OutVariable parameter accepts objects of type ArrayList. Here's an example of how to use it:
 
 `$start = (Get-Date).AddDays(-1); $end = (Get-Date).AddDays(-0.5); $auditData = New-Object System.Collections.ArrayList; Search-UnifiedAuditLog -StartDate $start -EndDate $end -OutVariable +auditData | Out-Null`
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -74,7 +74,7 @@ Search-UnifiedAuditLog -StartDate "6/1/2023 8:00 AM" -EndDate "6/1/2023 6:00 PM"
 
 This example searches the unified audit log for all Exchange admin events from 8:00 AM to 6:00 PM on June 1, 2023.
 
-**Note** If you use the same date for the StartDate and EndDate parameters, you need to include a timestamp; otherwise, no results will be returned because the date and time for the start and end dates will be the same.
+**Note** If you use the same date for the StartDate and EndDate parameters, you need to include a timestamp; otherwise, no results are returned because the date and time for the start and end dates are the same.
 
 ### Example 3
 ```powershell
@@ -335,7 +335,7 @@ Accept wildcard characters: False
 
 The SessionCommand parameter specifies how much information is returned and how it's organized. This parameter is required if you want to retrieve more than the default limit of 100 results. Valid values are:
 
-- ReturnLargeSet: This value causes the cmdlet to return unsorted data. By using paging, you can access a maximum of 50,000 results. This is the recommended value if an ordered result is not required and has been optimized for search latency.
+- ReturnLargeSet: This value causes the cmdlet to return unsorted data. By using paging, you can access a maximum of 50,000 results. This is the recommended value if an ordered result is not required and is optimized for search latency.
 - ReturnNextPreviewPage: This value causes the cmdlet to return data sorted on date. The maximum number of records returned through use of either paging or the ResultSize parameter is 5,000 records.
 
 **Note**: Always use the same SessionCommand value for a given SessionId value. Don't switch between ReturnLargeSet and ReturnNextPreviewPage for the same session ID. Otherwise, the output is limited to 10,000 results.
@@ -356,9 +356,9 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online, Exchange Online Protection
 
-The SessionId parameter specifies an ID you provide in the form of a string to identify a command (the cmdlet and its parameters) that will be run multiple times to return paged data. The SessionId can be any string value you choose.
+The SessionId parameter specifies an ID string to identify a command (the cmdlet and its parameters) that's run multiple times to return paged data. The SessionId can be any string value you choose.
 
-When the cmdlet is run sequentially with the same session ID, the cmdlet will return the data in sequential blocks of the size specified by ResultSize.
+When the cmdlet is run sequentially with the same session ID, the cmdlet returns the data in sequential blocks of the size specified by ResultSize.
 
 For a given session ID, if you use the SessionCommand value ReturnLargeSet, and then you use the SessionCommand value ReturnNextPreviewPage, the results are limited to 10,000 records. To have all 50,000 records available, always use the ReturnLargeSet value each time your run the cmdlet for the same session ID.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Send-TextMessagingVerificationCode.md b/exchange/exchange-ps/ExchangePowerShell/Send-TextMessagingVerificationCode.md
index b1af8ec2d7..af84b61d3e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Send-TextMessagingVerificationCode.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Send-TextMessagingVerificationCode.md
@@ -13,7 +13,7 @@ title: Send-TextMessagingVerificationCode
 # Send-TextMessagingVerificationCode
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Send-TextMessagingVerificationCode cmdlet to send a text messaging verification as part of configuring text message notifications on the mailbox.
 
@@ -32,7 +32,7 @@ Send-TextMessagingVerificationCode [[-Identity] <MailboxIdParameter>]
 ## DESCRIPTION
 The Send-TextMessagingVerificationCode cmdlet generates a verification code and sends it to a user's mobile phone.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 This cmdlet returns an error if the user requests a verification code more than three times within a 24-hour period.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ADServerSettings.md b/exchange/exchange-ps/ExchangePowerShell/Set-ADServerSettings.md
index 080dc688ce..537e6dd15f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ADServerSettings.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ADServerSettings.md
@@ -52,7 +52,7 @@ Set-ADServerSettings [[-PreferredServer] <Fqdn>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AcceptedDomain.md b/exchange/exchange-ps/ExchangePowerShell/Set-AcceptedDomain.md
index d4947a9cab..6c681e1ca8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-AcceptedDomain.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-AcceptedDomain.md
@@ -13,7 +13,7 @@ title: Set-AcceptedDomain
 # Set-AcceptedDomain
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-AcceptedDomain cmdlet to modify existing accepted domains in your organization. An accepted domain is any SMTP namespace for which an Exchange organization sends and receives email.
 
@@ -42,7 +42,7 @@ Set-AcceptedDomain [-Identity] <AcceptedDomainIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -166,7 +166,7 @@ Accept wildcard characters: False
 
 The DomainType parameter specifies the accepted domain type. Valid values are:
 
-- Authoritative: This is the default value. Your organization is completely responsible for delivering email to recipients in the domain, and for generating non-delivery reports (also known as an NDRs, delivery system notifications, DSNs, or bounce messages) for unresolved recipients.
+- Authoritative: This value is the default. Your organization is completely responsible for delivering email to recipients in the domain, and for generating non-delivery reports (also known as an NDRs, delivery system notifications, DSNs, or bounce messages) for unresolved recipients.
 - InternalRelay: This is a type of non-authoritative domain. Your organization receives email that's sent to recipients in the domain, but the messages are relayed to an external email system that's under your control. The external email system is responsible for generating NDRs for unresolved recipients. Use this value to treat messages that are sent to the domain as internal messages.
 - ExternalRelay: This is a type of non-authoritative domain that's available only in on-premises Exchange organizations. Your organization receives email that's sent to recipients in the domain, but the messages are relayed to an external email system that's completely outside of your control. The external email system is responsible for generating NDRs for unresolved recipients.
 
@@ -212,7 +212,7 @@ This parameter is available only in on-premises Exchange.
 
 The MakeDefault parameter specifies whether the accepted domain is the default domain. Valid values are: $true or $false.
 
-- $true: The accepted domain is the default domain. This is the default value for first accepted domain that's created in the organization.
+- $true: The accepted domain is the default domain. This value is the default for first accepted domain that's created in the organization.
 - $false: The accepted domain isn't the default domain. This the default value for subsequent accepted domains.
 
 The default accepted domain is used in sender email addresses when the senders have only non-SMTP email addresses (for example, X.400 addresses). Non-SMTP email addresses are encapsulated in SMTP email addresses by using the Internet Mail Connector Encapsulated Address (IMCEA) encapsulation method. IMCEA encapsulation uses the default domain value in the SMTP email address.
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AccessToCustomerDataRequest.md b/exchange/exchange-ps/ExchangePowerShell/Set-AccessToCustomerDataRequest.md
index 0f0c11f6da..aaedd38eb6 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-AccessToCustomerDataRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-AccessToCustomerDataRequest.md
@@ -31,7 +31,7 @@ Set-AccessToCustomerDataRequest -ApprovalDecision <AccessToCustomerDataApproverD
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncDeviceAccessRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncDeviceAccessRule.md
index f09b1a8f8a..b2dfc71570 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncDeviceAccessRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncDeviceAccessRule.md
@@ -13,7 +13,7 @@ title: Set-ActiveSyncDeviceAccessRule
 # Set-ActiveSyncDeviceAccessRule
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-ActiveSyncDeviceAccessRule cmdlet to set the level of access for the rule.
 
@@ -33,7 +33,7 @@ Set-ActiveSyncDeviceAccessRule [-Identity] <ActiveSyncDeviceAccessRuleIdParamete
 ## DESCRIPTION
 Your rule can define multiple groups of devices: allowed devices, blocked devices and quarantined devices.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncDeviceAutoblockThreshold.md b/exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncDeviceAutoblockThreshold.md
index a6b7e0af1e..8b29f977a3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncDeviceAutoblockThreshold.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncDeviceAutoblockThreshold.md
@@ -36,20 +36,20 @@ Set-ActiveSyncDeviceAutoblockThreshold [-Identity] <ActiveSyncDeviceAutoblockThr
 ## DESCRIPTION
 Microsoft Exchange and Microsoft Exchange ActiveSync can block Exchange ActiveSync mobile devices if these devices display any of a defined list of behaviors that can potentially cause issues with the server. The Set-ActiveSyncDeviceAutoblockThreshold cmdlet can modify an existing autoblock threshold rule and change a variety of settings including the duration of blocking.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
 ### Example 1
 ```powershell
-Set-ActiveSyncDeviceAutoblockThreshold -Identity "UserAgentChanges" BehaviorTypeIncidenceLimit 2 -BehaviorTypeIncidenceDuration 1440 -DeviceBlockDuration 1440 -AdminEmailInsert "<B>Your device has been blocked.</B> "]
+Set-ActiveSyncDeviceAutoblockThreshold -Identity "UserAgentChanges" BehaviorTypeIncidenceLimit 2 -BehaviorTypeIncidenceDuration 1440 -DeviceBlockDuration 1440 -AdminEmailInsert "<B>Your device is blocked.</B> "]
 ```
 
 This example sets the autoblock threshold rule UserAgentChanges with several settings. It limits the number of accepted UserAgent changes to 2, specifies that the incidence duration is 1440 minutes and blocks the mobile device for 1440 minutes. Lastly, it inserts a message into the administrative email message sent to the user.
 
 ### Example 2
 ```powershell
-Set-ActiveSyncDeviceAutoblockThreshold -Identity "RecentCommands" BehaviorTypeIncidenceLimit 5 -BehaviorTypeIncidenceDuration 720 -DeviceBlockDuration 720 -AdminEmailInsert "<B>Your device has been blocked.</B> "]
+Set-ActiveSyncDeviceAutoblockThreshold -Identity "RecentCommands" BehaviorTypeIncidenceLimit 5 -BehaviorTypeIncidenceDuration 720 -DeviceBlockDuration 720 -AdminEmailInsert "<B>Your device is blocked.</B> "]
 ```
 
 This example sets the autoblock threshold rule RecentCommands with several settings. It limits the number of accepted RecentCommands changes to 5, specifies that the incidence duration is 720 minutes and blocks the mobile device for 720 minutes. Lastly, it inserts a message into the administrative email message sent to the user.
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncMailboxPolicy.md
index c315385640..d5222a900b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncMailboxPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncMailboxPolicy.md
@@ -13,7 +13,7 @@ title: Set-ActiveSyncMailboxPolicy
 # Set-ActiveSyncMailboxPolicy
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-ActiveSyncMailboxPolicy cmdlet to apply a variety of Mobile Device mailbox policy settings to a server. You can set any of the parameters by using one command.
 
@@ -90,7 +90,7 @@ With the Set-ActiveSyncMailboxPolicy cmdlet, you can set each parameter in a mai
 
 Some Microsoft Mobile Device mailbox policy settings require the mobile device to have specific built-in features that enforce these security and device management settings. If your organization allows all devices, you must set the AllowNonProvisionableDevices parameter to $true. This applies to devices that can't enforce all policy settings.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncOrganizationSettings.md b/exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncOrganizationSettings.md
index 3e8b02bfe3..c1e59f6d4b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncOrganizationSettings.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncOrganizationSettings.md
@@ -13,7 +13,7 @@ title: Set-ActiveSyncOrganizationSettings
 # Set-ActiveSyncOrganizationSettings
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-ActiveSyncOrganizationSettings cmdlet to set the Exchange ActiveSync settings for the organization.
 
@@ -38,7 +38,7 @@ Set-ActiveSyncOrganizationSettings [[-Identity] <ActiveSyncOrganizationSettingsI
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -118,7 +118,7 @@ This parameter is functional only in the cloud-based service.
 The AllowRMSSupportForUnenlightenedApps parameter specifies whether to allow Rights Management Services (RMS) protected messages for ActiveSync clients that don't support RMS. Valid values are:
 
 - $true
-- $false (This is the default value)
+- $false (default value)
 
 ```yaml
 Type: Boolean
@@ -159,7 +159,7 @@ Accept wildcard characters: False
 
 The DefaultAccessLevel parameter specifies the access level for new and existing device partnerships. Valid values are:
 
-- Allow (This is the default value)
+- Allow (default value)
 - Block
 - Quarantine
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncVirtualDirectory.md
index a23f8983c8..676037bf7e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncVirtualDirectory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncVirtualDirectory.md
@@ -55,7 +55,7 @@ Set-ActiveSyncVirtualDirectory [-Identity] <VirtualDirectoryIdParameter>
 ## DESCRIPTION
 The Set-ActiveSyncVirtualDirectory cmdlet configures a variety of settings on the virtual directory used for Exchange ActiveSync including security, authentication, and internal and external URL settings.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -148,7 +148,7 @@ Accept wildcard characters: False
 
 The BasicAuthentication parameter specifies whether Basic authentication is enabled on the virtual directory. Valid values are:
 
-- $true: Basic authentication is enabled. This is the default value.
+- $true: Basic authentication is enabled. This value is the default.
 - $false: Basic authentication is disabled.
 
 ```yaml
@@ -248,7 +248,7 @@ The ExtendedProtectionFlags parameter specifies custom settings for Extended Pro
 - AllowDotlessSPN: Required if you want to use Service Principal Name (SPN) values that don't contain FQDNs (for example, HTTP/ContosoMail instead of HTTP/mail.contoso.com). You specify SPNs with the ExtendedProtectionSPNList parameter. This setting makes Extended Protection for Authentication less secure because dotless certificates aren't unique, so it isn't possible to ensure that the client-to-proxy connection was established over a secure channel.
 - NoServiceNameCheck: The SPN list isn't checked to validate a channel binding token. This setting makes Extended Protection for Authentication less secure. We generally don't recommend this setting.
 - Proxy: A proxy server is responsible for terminating the SSL channel. To use this setting, you need to register an SPN by using the ExtendedProtectionSPNList parameter.
-- ProxyCoHosting: HTTP and HTTPS traffic may be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server.
+- ProxyCoHosting: HTTP and HTTPS traffic might be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server.
 
 ```yaml
 Type: MultiValuedProperty
@@ -268,7 +268,7 @@ Accept wildcard characters: False
 
 The ExtendedProtectionSPNList parameter specifies a list of valid Service Principal Names (SPNs) if you're using Extended Protection for Authentication on the virtual directory. Valid values are:
 
-- $null: This is the default value.
+- $null: This value is the default.
 - Single SPN or comma delimited list of valid SPNs: The SPN value format is `Protocol\FQDN`. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter.
 
 ```yaml
@@ -289,8 +289,8 @@ Accept wildcard characters: False
 
 The ExtendedProtectionTokenChecking parameter defines how you want to use Extended Protection for Authentication on the virtual directory. Extended Protection for Authentication isn't enabled by default. Valid values are:
 
-- None: Extended Protection for Authentication isn't be used on the virtual directory. This is the default value.
-- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication will work, but may not be as secure as connections that use Extended Protection for Authentication.
+- None: Extended Protection for Authentication isn't be used on the virtual directory. This value is the default.
+- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication work, but might not be as secure as connections that use Extended Protection for Authentication.
 - Require: Extended Protection for Authentication is used for all connections between clients and the virtual directory. If either the client or server doesn't support it, the connection will fail. If you use this value, you also need to set an SPN value for the ExtendedProtectionSPNList parameter.
 
 **Note**: If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter.
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AddressBookPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-AddressBookPolicy.md
index ad5d4f2c0d..3ca49ee585 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-AddressBookPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-AddressBookPolicy.md
@@ -13,7 +13,7 @@ title: Set-AddressBookPolicy
 # Set-AddressBookPolicy
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-AddressBookPolicy cmdlet to change the settings of an address book policy.
 
@@ -37,7 +37,7 @@ Set-AddressBookPolicy [-Identity] <MailboxPolicyIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -72,7 +72,15 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
 
-The AddressLists parameter specifies the address lists that will be used by mailbox users who are assigned this address book policy. This parameter accepts multiple values, which should be separated by a comma.
+The AddressLists parameter specifies the address lists for mailbox users who are assigned this address book policy. You can use any value that uniquely identifies the address list. For example:
+
+- Name
+- Distinguished name (DN)
+- GUID
+
+You can enter multiple values separated by commas. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`.
+
+You can find the identify values of address lists by using the Get-AddressList cmdlet.
 
 ```yaml
 Type: AddressListIdParameter[]
@@ -131,7 +139,15 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
 
-The GlobalAddressList parameter specifies the identity of the global address list (GAL) that will be used by mailbox users who are assigned this address book policy. You can specify only one GAL for each address book policy.
+The GlobalAddressList parameter specifies the GAL for mailbox users who are assigned this address book policy. You can use any value that uniquely identifies the GAL. For example:
+
+- Name
+- Distinguished name (DN)
+- GUID
+
+You can find the identify values of GALs by using the Get-GlobalAddressList cmdlet.
+
+You can specify only one GAL for each address book policy.
 
 ```yaml
 Type: GlobalAddressListIdParameter
@@ -167,7 +183,15 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
 
-The OfflineAddressBook parameter specifies the identity of the offline address book (OAB) that will be used by mailbox users who are assigned this address book policy. You can specify only one OAB for each address book policy.
+The OfflineAddressBook parameter specifies the OAB for mailbox users who are assigned this address book policy. You can use any value that uniquely identifies the OAB. For example:
+
+- Name
+- Distinguished name (DN)
+- GUID
+
+You can find the identify values of OABs by using the Get-OfflineAddressBook cmdlet.
+
+You can specify only one OAB for each address book policy.
 
 ```yaml
 Type: OfflineAddressBookIdParameter
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AddressList.md b/exchange/exchange-ps/ExchangePowerShell/Set-AddressList.md
index bee9b693b5..72c8d4e3e6 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-AddressList.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-AddressList.md
@@ -13,7 +13,7 @@ title: Set-AddressList
 # Set-AddressList
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-AddressList cmdlet to modify existing address lists.
 
@@ -68,7 +68,7 @@ To create flexible filters that use any available recipient property and that ar
 
 You can't use this cmdlet to replace a precanned filter with a custom OPATH filter, or vice-versa. You can only modify the existing filter.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AdminAuditLogConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-AdminAuditLogConfig.md
index 2039a6a6de..42c5b5bdfa 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-AdminAuditLogConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-AdminAuditLogConfig.md
@@ -13,7 +13,7 @@ title: Set-AdminAuditLogConfig
 # Set-AdminAuditLogConfig
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-AdminAuditLogConfig cmdlet to configure the administrator audit logging configuration settings.
 
@@ -44,11 +44,11 @@ When audit logging is enabled, a log entry is created for each cmdlet run, exclu
 
 The Set-AdminAuditLogConfig, Enable-CmdletExtensionAgent, and Disable-CmdletExtensionAgent cmdlets are logged when they're run regardless of whether administrator audit logging is enabled or disabled.
 
-Administrator audit logging relies on Active Directory replication to replicate the configuration settings you specify to the domain controllers in your organization. Depending on your replication settings, the changes you make may not be immediately applied to all Exchange servers in your organization.
+Administrator audit logging relies on Active Directory replication to replicate the configuration settings you specify to the domain controllers in your organization. Depending on your replication settings, the changes you make might not be immediately applied to all Exchange servers in your organization.
 
-Changes to the audit log configuration may take up to 60 minutes to be applied on computers that have the Exchange Management Shell open at the time a configuration change is made. If you want to apply the changes immediately, close and reopen the Exchange Management Shell on each computer.
+Changes to the audit log configuration might take up to 60 minutes to be applied on computers that have the Exchange Management Shell open at the time a configuration change is made. If you want to apply the changes immediately, close and reopen the Exchange Management Shell on each computer.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -151,7 +151,7 @@ This parameter is available only in on-premises Exchange.
 
 The AdminAuditLogEnabled parameter specifies whether administrator audit logging is enabled. Valid values are:
 
-- $true: Administrator audit logging is enabled. This is the default value.
+- $true: Administrator audit logging is enabled. This value is the default.
 - $false: Administrator audit logging is disabled.
 
 You must specify an administrator audit log mailbox before you enable logging.
@@ -281,7 +281,7 @@ This parameter is available only in on-premises Exchange.
 
 The LogLevel parameter specifies whether additional properties should be included in the log entries. Valid values are:
 
-- None: The CmdletName, ObjectName, Parameters (values), and the Caller, Succeeded and RunDate properties are included in log entries. This is the default value.
+- None: The CmdletName, ObjectName, Parameters (values), and the Caller, Succeeded and RunDate properties are included in log entries. This value is the default.
 - Verbose: The ModifiedProperties (old and new) and ModifiedObjectResolvedName properties are also included in log entries.
 
 ```yaml
@@ -327,7 +327,7 @@ This parameter is available only in on-premises Exchange.
 The TestCmdletLoggingEnabled parameter specifies whether test cmdlets (cmdlet names that begin with the verb Test) results are included in admin audit logging. Valid values are:
 
 - $true: Test cmdlets are included in admin audit logging.
-- $false: Test cmdlets aren't included in admin audit logging. This is the default value.
+- $false: Test cmdlets aren't included in admin audit logging. This value is the default.
 
 Test cmdlets can produce a large amount of information. As such, you should only enable logging of test cmdlets for a short period of time.
 
@@ -351,7 +351,7 @@ This parameter is functional only in the cloud-based service.
 
 The UnifiedAuditLogIngestionEnabled parameter specifies whether to enable or disable the recording of user and admin activities in the Microsoft 365 audit log. Valid values are:
 
-- $true: User and admin activities are recorded in the Microsoft 365 audit log, and admins can search the Microsoft 365 audit log. This is the default value.
+- $true: User and admin activities are recorded in the Microsoft 365 audit log, and admins can search the Microsoft 365 audit log. This value is the default.
 - $false: User and admin activities aren't recorded in the Microsoft 365 audit log, and admins can't search the Microsoft 365 audit log.
 
 ```yaml

From 7bb4df1e269ea5a14f0dfc8eb9c36e1781650037 Mon Sep 17 00:00:00 2001
From: Chris Davis <chris.davis@microsoft.com>
Date: Wed, 6 Aug 2025 10:11:13 -0700
Subject: [PATCH 110/145] Acrolinx 13

---
 .../ExchangePowerShell/Set-ADSite.md          |  7 +-
 .../ExchangePowerShell/Set-ADSiteLink.md      |  4 +-
 .../Set-ATPBuiltInProtectionRule.md           |  2 +-
 .../Set-ATPProtectionPolicyRule.md            |  2 +-
 .../ExchangePowerShell/Set-AntiPhishPolicy.md | 44 ++++-----
 .../ExchangePowerShell/Set-AntiPhishRule.md   |  2 +-
 .../exchange-ps/ExchangePowerShell/Set-App.md | 14 +--
 .../Set-AppRetentionCompliancePolicy.md       |  8 +-
 .../Set-AppRetentionComplianceRule.md         |  6 +-
 .../Set-ApplicationAccessPolicy.md            |  2 +-
 .../ExchangePowerShell/Set-ArcConfig.md       |  2 +-
 .../Set-AtpPolicyForO365.md                   | 10 +--
 .../Set-AttachmentFilterListConfig.md         |  2 +-
 .../ExchangePowerShell/Set-AuthConfig.md      |  4 +-
 .../ExchangePowerShell/Set-AuthRedirect.md    |  4 +-
 .../ExchangePowerShell/Set-AuthServer.md      |  8 +-
 .../Set-AuthenticationPolicy.md               |  6 +-
 .../Set-AutoSensitivityLabelPolicy.md         | 10 +--
 .../Set-AutoSensitivityLabelRule.md           | 10 +--
 .../Set-AutodiscoverVirtualDirectory.md       | 20 ++---
 .../Set-AvailabilityConfig.md                 |  4 +-
 .../Set-AvailabilityReportOutage.md           |  2 +-
 .../ExchangePowerShell/Set-CASMailbox.md      | 68 +++++++-------
 .../ExchangePowerShell/Set-CASMailboxPlan.md  |  6 +-
 .../Set-CalendarNotification.md               | 14 +--
 .../Set-CalendarProcessing.md                 | 60 ++++++-------
 .../ExchangePowerShell/Set-CaseHoldPolicy.md  |  2 +-
 .../ExchangePowerShell/Set-CaseHoldRule.md    |  2 +-
 .../Set-ClassificationRuleCollection.md       |  4 +-
 .../Set-ClientAccessArray.md                  |  2 +-
 .../Set-ClientAccessRule.md                   |  4 +-
 .../Set-ClientAccessServer.md                 |  8 +-
 .../Set-ClientAccessService.md                |  2 +-
 .../ExchangePowerShell/Set-Clutter.md         |  4 +-
 .../Set-CmdletExtensionAgent.md               |  2 +-
 .../Set-ComplianceRetentionEventType.md       |  2 +-
 .../Set-ComplianceSearch.md                   | 14 +--
 .../Set-ComplianceSearchAction.md             |  2 +-
 .../Set-ComplianceSecurityFilter.md           |  2 +-
 .../ExchangePowerShell/Set-Contact.md         | 10 +--
 .../Set-ContentFilterConfig.md                | 18 ++--
 .../Set-DataClassification.md                 |  4 +-
 .../Set-DataEncryptionPolicy.md               |  4 +-
 .../Set-DatabaseAvailabilityGroup.md          |  8 +-
 .../Set-DatabaseAvailabilityGroupNetwork.md   |  2 +-
 .../Set-DefaultTenantBriefingConfig.md        |  2 +-
 .../Set-DeliveryAgentConnector.md             |  2 +-
 .../ExchangePowerShell/Set-DetailsTemplate.md |  2 +-
 .../Set-DeviceConditionalAccessPolicy.md      |  2 +-
 .../Set-DeviceConditionalAccessRule.md        | 90 +++++++++----------
 .../Set-DeviceConfigurationPolicy.md          |  2 +-
 .../Set-DeviceConfigurationRule.md            | 88 +++++++++---------
 .../Set-DeviceTenantPolicy.md                 |  2 +-
 .../Set-DistributionGroup.md                  | 46 +++++-----
 .../Set-DkimSigningConfig.md                  |  8 +-
 .../Set-DlpCompliancePolicy.md                |  6 +-
 .../Set-DlpComplianceRule.md                  | 22 ++---
 .../ExchangePowerShell/Set-DlpPolicy.md       |  4 +-
 .../Set-DlpSensitiveInformationType.md        |  4 +-
 .../Set-DynamicDistributionGroup.md           | 36 ++++----
 .../Set-EOPProtectionPolicyRule.md            |  2 +-
 .../Set-EcpVirtualDirectory.md                | 18 ++--
 .../Set-EdgeSyncServiceConfig.md              |  8 +-
 .../Set-EmailAddressPolicy.md                 |  6 +-
 .../Set-EmailTenantSettings.md                |  2 +-
 .../ExchangePowerShell/Set-EventLogLevel.md   |  2 +-
 .../Set-EventsFromEmailConfiguration.md       | 22 ++---
 .../Set-ExchangeAssistanceConfig.md           |  4 +-
 .../ExchangePowerShell/Set-ExchangeFeature.md |  2 +-
 .../ExchangePowerShell/Set-ExchangeServer.md  |  4 +-
 .../Set-ExchangeSettings.md                   |  2 +-
 .../Set-ExoPhishSimOverrideRule.md            |  2 +-
 .../Set-ExoSecOpsOverrideRule.md              |  2 +-
 .../Set-ExternalInOutlook.md                  |  2 +-
 .../Set-FederatedOrganizationIdentifier.md    |  4 +-
 .../ExchangePowerShell/Set-FederationTrust.md |  2 +-
 .../ExchangePowerShell/Set-FocusedInbox.md    |  4 +-
 .../Set-ForeignConnector.md                   | 12 +--
 .../Set-FrontendTransportService.md           | 30 +++----
 .../Set-GlobalAddressList.md                  |  4 +-
 .../ExchangePowerShell/Set-Group.md           |  8 +-
 .../Set-HoldCompliancePolicy.md               |  4 +-
 .../Set-HoldComplianceRule.md                 |  4 +-
 .../Set-HostedConnectionFilterPolicy.md       |  5 +-
 .../Set-HostedContentFilterPolicy.md          | 74 +++++++--------
 .../Set-HostedContentFilterRule.md            |  2 +-
 .../Set-HostedOutboundSpamFilterPolicy.md     | 14 +--
 .../Set-HostedOutboundSpamFilterRule.md       |  2 +-
 .../Set-HybridConfiguration.md                |  8 +-
 .../Set-IRMConfiguration.md                   | 32 +++----
 .../ExchangePowerShell/Set-ImapSettings.md    | 30 +++----
 .../Set-InboundConnector.md                   | 18 ++--
 .../ExchangePowerShell/Set-InboxRule.md       | 14 +--
 .../Set-IntraOrganizationConnector.md         |  8 +-
 .../ExchangePowerShell/Set-JournalRule.md     |  4 +-
 .../ExchangePowerShell/Set-Label.md           |  2 +-
 .../ExchangePowerShell/Set-LabelPolicy.md     |  2 +-
 97 files changed, 550 insertions(+), 548 deletions(-)

diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ADSite.md b/exchange/exchange-ps/ExchangePowerShell/Set-ADSite.md
index d3e770f585..03b5ba59ce 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ADSite.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ADSite.md
@@ -33,7 +33,7 @@ Set-ADSite [-Identity] <AdSiteIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -125,9 +125,10 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-The InboundMailEnabled parameter enables or disables receiving incoming messages for all the Exchange located in the Active Directory site. Typically, this parameter is used after Active Directory site failover or maintenance.
+The InboundMailEnabled parameter enables or disables receiving incoming messages for all Exchange servers located in the Active Directory site. Typically, you use this parameter after Active Directory site failover or maintenance. Valid values are:
 
-Valid input for this parameter is $true or $false. The default value is $true. If you set the value to $false, none of the Exchange servers in the Active Directory site will be able to receive incoming messages.
+- $true: All Exchange servers in the Active Directory site can receive incoming email messages. This value is the default.
+- $false: No Exchange servers in the Active Directory site can receive incoming email messages.
 
 ```yaml
 Type: Boolean
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ADSiteLink.md b/exchange/exchange-ps/ExchangePowerShell/Set-ADSiteLink.md
index 01d0e16fc3..f47a8b17c3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ADSiteLink.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ADSiteLink.md
@@ -35,7 +35,7 @@ Set-ADSiteLink [-Identity] <AdSiteLinkIdParameter>
 ## DESCRIPTION
 By default, Microsoft Exchange determines the least cost routing path by using the cost assigned to the Active Directory IP site link. You can use the Set-ADSiteLink cmdlet to assign an Exchange-specific cost to the Active Directory IP site link. The Exchange-specific cost is a separate attribute used instead of the Active Directory-assigned cost to determine the least cost routing path.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -139,7 +139,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The valid input range for this parameter is from 64 KB through Int64. To remove the message size limit on an Active Directory IP site link, enter a value of unlimited.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ATPBuiltInProtectionRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-ATPBuiltInProtectionRule.md
index 8a156797ad..d5c9dd43e2 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ATPBuiltInProtectionRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ATPBuiltInProtectionRule.md
@@ -38,7 +38,7 @@ For more information about preset security policies in PowerShell, see [Preset s
 > [!IMPORTANT]
 > Different types of recipient exceptions use OR logic (the recipient must satisfy **any** of the specified exceptions). For more information, see [Profiles in preset security policies](https://learn.microsoft.com/defender-office-365/preset-security-policies#profiles-in-preset-security-policies).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ATPProtectionPolicyRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-ATPProtectionPolicyRule.md
index ea44a4a727..b623a6b8de 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ATPProtectionPolicyRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ATPProtectionPolicyRule.md
@@ -43,7 +43,7 @@ For more information about preset security policies in PowerShell, see [Preset s
 > [!IMPORTANT]
 > Different types of recipient conditions use AND logic (the recipient must satisfy **all** specified conditions). Different types of recipient exceptions use OR logic (the recipient must satisfy **any** of the specified exceptions). For more information, see [Profiles in preset security policies](https://learn.microsoft.com/defender-office-365/preset-security-policies#profiles-in-preset-security-policies).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AntiPhishPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-AntiPhishPolicy.md
index f4a26fbb29..4cfb21fc4b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-AntiPhishPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-AntiPhishPolicy.md
@@ -65,7 +65,7 @@ Set-AntiPhishPolicy -Identity <AntiPhishPolicyIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -138,7 +138,7 @@ This setting is part of spoof protection.
 
 The AuthenticationFailAction parameter specifies the action to take when the message fails composite authentication (a mixture of traditional SPF, DKIM, and DMARC email authentication checks and proprietary backend intelligence). Valid values are:
 
-- MoveToJmf: This is the default value. Deliver the message to the Junk Email folder in the recipient's mailbox.
+- MoveToJmf: This value is the default. Deliver the message to the Junk Email folder in the recipient's mailbox.
 - Quarantine: Deliver the message to quarantine. Quarantined high confidence phishing messages are available only to admins. As of April 2020, quarantined phishing messages are available to the intended recipients.
 
 ```yaml
@@ -183,7 +183,7 @@ This setting is part of spoof protection.
 The DmarcQuarantineAction parameter specifies the action to take when a message fails DMARC checks and the sender's DMARC policy is `p=quarantine`. Valid values are:
 
 - MoveToJmf: Deliver the message to the Junk Email folder in the recipient's mailbox.
-- Quarantine: Deliver the message to quarantine. This is the default value.
+- Quarantine: Deliver the message to quarantine. This value is the default.
 
 ```yaml
 Type: SpoofDmarcQuarantineAction
@@ -206,7 +206,7 @@ This setting is part of spoof protection.
 The DmarcRejectAction parameter specifies the action to take when a message fails DMARC checks and the sender's DMARC policy is `p=reject`. Valid values are:
 
 - Quarantine: Deliver the message to quarantine.
-- Reject: Reject the message. This is the default value.
+- Reject: Reject the message. This value is the default.
 
 This parameter is meaningful only when the HonorDmarcPolicy parameter is set to the value $true.
 
@@ -253,7 +253,7 @@ Accept wildcard characters: False
 The EnableFirstContactSafetyTips parameter specifies whether to enable or disable the safety tip that's shown when recipients first receive an email from a sender or do not often receive email from a sender. Valid values are:
 
 - $true: First contact safety tips are enabled.
-- $false: First contact safety tips are disabled. This is the default value.
+- $false: First contact safety tips are disabled. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -275,7 +275,7 @@ This setting is part of impersonation protection and is available only in Micros
 
 The EnableMailboxIntelligence parameter specifies whether to enable or disable mailbox intelligence, which is artificial intelligence (AI) that determines user email patterns with their frequent contacts. Mailbox intelligence helps distinguish between messages from legitimate and impersonated senders based on a recipient's previous communication history. Valid values are:
 
-- $true: Mailbox intelligence is enabled. This is the default value.
+- $true: Mailbox intelligence is enabled. This value is the default.
 - $false: Mailbox intelligence is disabled. The values of the EnableMailboxIntelligenceProtection and MailboxIntelligenceProtectionAction parameters are ignored.
 
 ```yaml
@@ -299,7 +299,7 @@ This setting is part of impersonation protection and is available only in Micros
 The EnableMailboxIntelligenceProtection specifies whether to enable or disable taking action for impersonation detections from mailbox intelligence results. Valid values are:
 
 - $true: Take action for impersonation detections from mailbox intelligence results. Use the MailboxIntelligenceProtectionAction parameter to specify the action.
-- $false: Don't take action for impersonation detections from mailbox intelligence results. The value of the MailboxIntelligenceProtectionAction parameter is ignored. This is the default value.
+- $false: Don't take action for impersonation detections from mailbox intelligence results. The value of the MailboxIntelligenceProtectionAction parameter is ignored. This value is the default.
 
 This parameter is meaningful only if the EnableMailboxIntelligence parameter is set to the value $true.
 
@@ -326,7 +326,7 @@ This setting is part of impersonation protection and is available only in Micros
 The EnableOrganizationDomainsProtection parameter specifies whether to enable domain impersonation protection for all registered domains in the Microsoft 365 organization. Valid values are:
 
 - $true: Domain impersonation protection is enabled for all registered domains in the Microsoft 365 organization.
-- $false: Domain impersonation protection isn't enabled for all registered domains in the Microsoft 365 organization. This is the default value. You can enable protection for specific domains by using the EnableTargetedDomainsProtection and TargetedDomainsToProtect parameters.
+- $false: Domain impersonation protection isn't enabled for all registered domains in the Microsoft 365 organization. This value is the default. You can enable protection for specific domains by using the EnableTargetedDomainsProtection and TargetedDomainsToProtect parameters.
 
 ```yaml
 Type: Boolean
@@ -349,7 +349,7 @@ This setting is part of impersonation protection and is available only in Micros
 The EnableSimilarDomainsSafetyTips parameter specifies whether to enable the safety tip that's shown to recipients for domain impersonation detections. Valid values are:
 
 - $true: Safety tips for similar domains are enabled.
-- $false: Safety tips for similar domains are disabled. This is the default value.
+- $false: Safety tips for similar domains are disabled. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -372,7 +372,7 @@ This setting is part of impersonation protection and is available only in Micros
 The EnableSimilarUsersSafetyTips parameter specifies whether to enable the safety tip that's shown to recipients for user impersonation detections. Valid values are:
 
 - $true: Safety tips for similar users are enabled.
-- $false: Safety tips for similar users are disabled. This is the default value.
+- $false: Safety tips for similar users are disabled. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -418,7 +418,7 @@ This setting is part of impersonation protection and is available only in Micros
 The EnableTargetedDomainsProtection parameter specifies whether to enable domain impersonation protection for a list of specified domains. Valid values are:
 
 - $true: Domain impersonation protection is enabled for the domains specified by the TargetedDomainsToProtect parameter.
-- $false: The TargetedDomainsToProtect parameter isn't used. This is the default value.
+- $false: The TargetedDomainsToProtect parameter isn't used. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -441,7 +441,7 @@ This setting is part of impersonation protection and is available only in Micros
 The EnableTargetedUserProtection parameter specifies whether to enable user impersonation protection for a list of specified users. Valid values are:
 
 - $true: User impersonation protection is enabled for the users specified by the TargetedUsersToProtect parameter.
-- $false: The TargetedUsersToProtect parameter isn't used. This is the default value.
+- $false: The TargetedUsersToProtect parameter isn't used. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -463,7 +463,7 @@ This setting is part of spoof protection.
 
 The EnableUnauthenticatedSender parameter enables or disables unauthenticated sender identification in Outlook. Valid values are:
 
-- $true: This is the default value. A question mark (?) is applied to the sender's photo if the message does not pass SPF or DKIM checks AND the message does not pass DMARC or composite authentication.
+- $true: This value is the default. A question mark (?) is applied to the sender's photo if the message does not pass SPF or DKIM checks AND the message does not pass DMARC or composite authentication.
 - $false: A question mark is never applied to the sender's photo.
 
 To prevent these identifiers from being added to messages from specific senders, you have the following options:
@@ -492,7 +492,7 @@ This setting is part of impersonation protection and is available only in Micros
 The EnableUnusualCharactersSafetyTips parameter specifies whether to enable the safety tip that's shown to recipients for unusual characters in domain and user impersonation detections. Valid values are:
 
 - $true: Safety tips for unusual characters are enabled.
-- $false: Safety tips for unusual characters are disabled. This is the default value.
+- $false: Safety tips for unusual characters are disabled. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -514,7 +514,7 @@ This setting is part of spoof protection.
 
 The EnableViaTag parameter enables or disables adding the via tag to the From address in Outlook (chris@contso.com via fabrikam.com). Valid values are:
 
-- $true: The via tag is added to the From address (the message sender that's displayed in email clients) if the domain in the From address is different from the domain in the DKIM signature or the MAIL FROM address. This is the default value.
+- $true: The via tag is added to the From address (the message sender that's displayed in email clients) if the domain in the From address is different from the domain in the DKIM signature or the MAIL FROM address. This value is the default.
 - $false: The via tag is not added to the From address.
 
 To prevent the via tag from being added to messages from specific senders, you have the following options:
@@ -588,7 +588,7 @@ This setting is part of spoof protection.
 
 The HonorDmarcPolicy enables or disables using the sender's DMARC policy to determine what to do to messages that fail DMARC checks. Valid values are:
 
-- $true: If a message fails DMARC and the sender's DMARC policy is `p=quarantine` or `p=reject`, the DmarcQuarantineAction or DmarcRejectAction parameters specify the action to take on the message. This is the default value.
+- $true: If a message fails DMARC and the sender's DMARC policy is `p=quarantine` or `p=reject`, the DmarcQuarantineAction or DmarcRejectAction parameters specify the action to take on the message. This value is the default.
 - $false: If the message fails DMARC, ignore the action in the sender's DMARC policy. The AuthenticationFailAction parameter specifies the action to take on the message.
 
 ```yaml
@@ -611,8 +611,8 @@ This setting is part of impersonation protection and is available only in Micros
 
 The ImpersonationProtectionState parameter specifies the configuration of impersonation protection. Valid values are:
 
-- Automatic: This is the default value in the default policy named Office365 AntiPhish Policy.
-- Manual: This is the default value in custom policies that you create.
+- Automatic: This value is the default in the default policy named Office365 AntiPhish Policy.
+- Manual: This value is the default in custom policies that you create.
 - Off
 
 ```yaml
@@ -635,7 +635,7 @@ This setting is part of impersonation protection and is available only in Micros
 
 The MailboxIntelligenceProtectionAction parameter specifies what to do with messages that fail mailbox intelligence protection. Valid values are:
 
-- NoAction: This is the default value. Note that this value has the same result as setting the EnableMailboxIntelligenceProtection parameter to $false when the EnableMailboxIntelligence parameter is $true.
+- NoAction: This value is the default. This value has the same result as setting the EnableMailboxIntelligenceProtection parameter to $false when the EnableMailboxIntelligence parameter is $true.
 - BccMessage: Add the recipients specified by the MailboxIntelligenceProtectionActionRecipients parameter to the Bcc field of the message.
 - Delete: Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message.
 - MoveToJmf: Deliver the message to the Junk Email folder in the recipient's mailbox.
@@ -736,7 +736,7 @@ This setting is part of advanced settings and is available only in Microsoft Def
 
 The PhishThresholdLevel parameter specifies the tolerance level that's used by machine learning in the handling of phishing messages. Valid values are:
 
-- 1: Standard: This is the default value. The severity of the action that's taken on the message depends on the degree of confidence that the message is phishing (low, medium, high, or very high confidence). For example, messages that are identified as phishing with a very high degree of confidence have the most severe actions applied, while messages that are identified as phishing with a low degree of confidence have less severe actions applied.
+- 1: Standard: This value is the default. The severity of the action that's taken on the message depends on the degree of confidence that the message is phishing (low, medium, high, or very high confidence). For example, messages that are identified as phishing with a very high degree of confidence have the most severe actions applied, while messages that are identified as phishing with a low degree of confidence have less severe actions applied.
 - 2: Aggressive: Messages that are identified as phishing with a high degree of confidence are treated as if they were identified with a very high degree of confidence.
 - 3: More aggressive: Messages that are identified as phishing with a medium or high degree of confidence are treated as if they were identified with a very high degree of confidence.
 - 4: Most aggressive: Messages that are identified as phishing with a low, medium, or high degree of confidence are treated as if they were identified with a very high degree of confidence.
@@ -829,7 +829,7 @@ This setting is part of impersonation protection and is available only in Micros
 
 The TargetedDomainProtectionAction parameter specifies the action to take on detected domain impersonation messages. You specify the protected domains in the TargetedDomainsToProtect parameter. Valid values are:
 
-- NoAction: This is the default value.
+- NoAction: This value is the default.
 - BccMessage: Add the recipients specified by the TargetedDomainActionRecipients parameter to the Bcc field of the message, and deliver the message to the Junk Email folder of all (original + BCC-ed) recipients' mailboxes.
 - Delete: Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message.
 - MoveToJmf: Deliver the message to the Junk Email folder in the recipient's mailbox.
@@ -930,7 +930,7 @@ This setting is part of impersonation protection and is available only in Micros
 
 The TargetedUserProtectionAction parameter specifies the action to take on detected user impersonation messages. You specify the protected users in the TargetedUsersToProtect parameter. Valid values are:
 
-- NoAction: This is the default value.
+- NoAction: This value is the default.
 - BccMessage: Add the recipients specified by the TargetedDomainActionRecipients parameter to the Bcc field of the message.
 - Delete: Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message.
 - MoveToJmf: Deliver the message to the recipient's mailbox, and move the message to the Junk Email folder.
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AntiPhishRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-AntiPhishRule.md
index d3b9cfe74d..e84298092e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-AntiPhishRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-AntiPhishRule.md
@@ -42,7 +42,7 @@ Set-AntiPhishRule [-Identity] <RuleIdParameter>
 > [!IMPORTANT]
 > Different types of recipient conditions use AND logic (the recipient must satisfy **all** specified conditions). Different types of recipient exceptions use OR logic (the recipient must satisfy **any** of the specified exceptions). For more information, see [Common policy settings](https://learn.microsoft.com/defender-office-365/anti-phishing-policies-about#common-policy-settings).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-App.md b/exchange/exchange-ps/ExchangePowerShell/Set-App.md
index 5c05af8d3d..4fe9357f89 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-App.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-App.md
@@ -13,7 +13,7 @@ title: Set-App
 # Set-App
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-App cmdlet to modify the availability of organization apps.
 
@@ -36,13 +36,13 @@ Set-App [-Identity] <AppIdParameter>
 ```
 
 ## DESCRIPTION
-The Set-App cmdlet can only be used when configuring the availability of an organization app. This task requires that the specified app has already been installed (for example, that the app has been installed with the New-App cmdlet, or that it's a default app for Outlook).
+The Set-App cmdlet can only be used when configuring the availability of an organization app. This task requires that the specified app has already been installed (for example, that the app is installed with the New-App cmdlet, or that it's a default app for Outlook).
 
 Default apps in Outlook on the web and apps that you've installed for use by users in your organization are known as organization apps. Organization apps can't be removed by end users, but can be enabled or disabled. If an app is an organization app (scope default or organization), the delete control on the toolbar is disabled for end users. Administrators are able to remove organization apps. Administrators can't remove default apps, but they can disable them for the entire organization.
 
 For more information, see [Manage user access to add-ins for Outlook in Exchange Server](https://learn.microsoft.com/Exchange/manage-user-access-to-add-ins-exchange-2013-help) and [Manage deployment of add-ins in the Microsoft 365 admin center](https://learn.microsoft.com/office365/admin/manage/manage-deployment-of-add-ins).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -110,7 +110,7 @@ Accept wildcard characters: False
 The DefaultStateForUser parameter specifies the default initial state of the organization app for the specified users. Valid values are:
 
 - Enabled: The organization app is enabled.
-- Disabled: The organization app is disabled. This is the default value.
+- Disabled: The organization app is disabled. This value is the default.
 - AlwaysEnabled: The organization app is enabled, and users can't disable it.
 
 You use this parameter with the OrganizationApp switch.
@@ -153,7 +153,7 @@ Accept wildcard characters: False
 
 The Enabled parameter specifies whether the app is available to users in the organization. Valid values are:
 
-- $true: The app is enabled for the specified users. This is the default value.
+- $true: The app is enabled for the specified users. This value is the default.
 - $false: The app isn't enabled for any users in the organization. This hides the app from user view for all users.
 
 This setting overrides the ProvidedTo, UserList, and DefaultStateForUser settings. This setting doesn't prevent users from installing their own instance of the app if they have install permissions.
@@ -212,8 +212,8 @@ Accept wildcard characters: False
 
 The ProvidedTo parameter specifies the availability of the app in your organization. Valid value are:
 
-- Everyone: The app is provided to every user in the organization. This is the default value. Every user sees this app listed in the installed apps list in Outlook on the web Options. When an app in the installed apps list is enabled, users can use the features of this app in their email. All users are blocked from installing their own instances of this app, including but not limited to users with install apps permissions.
-- SpecificUsers: This app is provided to only the users specified by the UserList parameter. All other users don't see this organizational app in their management view, nor will it activate in their mail or calendar items. The specified users are also blocked from installing their own instance of this app. Unlisted users aren't blocked from installing their own instance of this app.
+- Everyone: The app is provided to every user in the organization. This value is the default. Every user sees this app listed in the installed apps list in Outlook on the web Options. When an app in the installed apps list is enabled, users can use the features of this app in their email. All users are blocked from installing their own instances of this app, including but not limited to users with install apps permissions.
+- SpecificUsers: This app is provided to only the users specified by the UserList parameter. All other users don't see this organizational app in their management view, nor does it activate in their mail or calendar items. The specified users are also blocked from installing their own instance of this app. Unlisted users aren't blocked from installing their own instance of this app.
 
 You use this parameter with the OrganizationApp switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AppRetentionCompliancePolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-AppRetentionCompliancePolicy.md
index 4830d65dc5..8d42672ef9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-AppRetentionCompliancePolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-AppRetentionCompliancePolicy.md
@@ -431,7 +431,7 @@ A valid value is a JSON string. Refer to the Examples section for syntax and usa
 
 For information about the inactive mailbox scenario, see [Learn about inactive mailboxes](https://learn.microsoft.com/purview/inactive-mailboxes-in-office-365).
 
-**CAUTION**: This parameter uses the SMTP address of the deleted mailbox or mail user, which might also be specified for other mailboxes or mail users. If you use this parameter without first taking additional steps, other mailboxes and mail users with the same SMTP address in the retention policy will also be excluded. To check for additional mailboxes or mail users with the same SMTP address, use the following command and replace `user@contoso.com` with the SMTP address to check: `Get-Recipient -IncludeSoftDeletedRecipients user@contoso.com | Select-Object DisplayName, EmailAddresses, Description, Alias, RecipientTypeDetails, WhenSoftDeleted`
+**CAUTION**: This parameter uses the SMTP address of the deleted mailbox or mail user, which might also be specified for other mailboxes or mail users. If you use this parameter without first taking additional steps, other mailboxes and mail users with the same SMTP address in the retention policy are also excluded. To check for additional mailboxes or mail users with the same SMTP address, use the following command and replace `user@contoso.com` with the SMTP address to check: `Get-Recipient -IncludeSoftDeletedRecipients user@contoso.com | Select-Object DisplayName, EmailAddresses, Description, Alias, RecipientTypeDetails, WhenSoftDeleted`
 
 To prevent active mailboxes or mail users with the same SMTP address from being excluded, put the mailbox on [Litigation Hold](https://learn.microsoft.com/purview/ediscovery-create-a-litigation-hold) before you run the command with the DeletedResources parameter.
 
@@ -453,7 +453,7 @@ Accept wildcard characters: False
 
 The Enabled parameter enables or disables the policy. Valid values are:
 
-- $true: The policy is enabled. This is the default value.
+- $true: The policy is enabled. This value is the default.
 - $false: The policy is disabled.
 
 ```yaml
@@ -655,9 +655,9 @@ Accept wildcard characters: False
 The RestrictiveRetention parameter specifies whether Preservation Lock is enabled for the policy. Valid values are:
 
 - $true: Preservation Lock is enabled for the policy. No one -- including an administrator -- can turn off the policy or make it less restrictive.
-- $false: Preservation Lock isn't enabled for the policy. This is the default value.
+- $false: Preservation Lock isn't enabled for the policy. This value is the default.
 
-After a policy has been locked, no one can turn off or disable it, or remove apps from the policy. The only ways that you can modify the policy are by adding apps to it, or extending its duration. A locked policy can be increased or extended, but it can't be reduced, disabled, or turned off.
+After a policy is locked, no one can turn off or disable it, or remove apps from the policy. The only ways that you can modify the policy are by adding apps to it, or extending its duration. A locked policy can be increased or extended, but it can't be reduced, disabled, or turned off.
 
 Therefore, before you lock a policy, it's critical that you understand your organization's compliance requirements, and that you don't lock a policy until you are certain that it's what you need.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AppRetentionComplianceRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-AppRetentionComplianceRule.md
index 94ac093cd4..1e3923865e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-AppRetentionComplianceRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-AppRetentionComplianceRule.md
@@ -195,7 +195,7 @@ Accept wildcard characters: False
 
 > Applicable: Security & Compliance
 
-The ExcludedItemClasses parameter specifies the types of messages to exclude from the rule. You can use this parameter only to exclude items from a hold policy, which excludes the specified item class from being held. Using this parameter won't exclude items from deletion policies. Typically, you use this parameter to exclude voicemail messages, IM conversations, and other Skype for Business Online content from being held by a hold policy. Common Skype for Business values include:
+The ExcludedItemClasses parameter specifies the types of messages to exclude from the rule. You can use this parameter only to exclude items from a hold policy, which excludes the specified item class from being held. Using this parameter doesn't exclude items from deletion policies. Typically, you use this parameter to exclude voicemail messages, IM conversations, and other Skype for Business Online content from being held by a hold policy. Common Skype for Business values include:
 
 - IPM.Note.Microsoft.Conversation
 - IPM.Note.Microsoft.Conversation.Voice
@@ -206,7 +206,7 @@ The ExcludedItemClasses parameter specifies the types of messages to exclude fro
 - IPM.Note.Microsoft.Voicemail.UM
 - IPM.Note.Microsoft.Voicemail.UM.CA
 
-Additionally, you can specify [message classes for Exchange items](https://learn.microsoft.com/office/vba/outlook/concepts/forms/item-types-and-message-classes) and custom or non-Microsoft message classes. Note that the values you specify aren't validated, so the parameter accepts any text value.
+Additionally, you can specify [message classes for Exchange items](https://learn.microsoft.com/office/vba/outlook/concepts/forms/item-types-and-message-classes) and custom or non-Microsoft message classes. The values you specify aren't validated, so the parameter accepts any text value.
 
 You can specify multiple item class values by using the following syntax: `"Value1","Value2",..."ValueN"`.
 
@@ -296,7 +296,7 @@ The RetentionDurationDisplayHint parameter specifies the units that are used to
 - Months
 - Years
 
-For example, if this parameter is set to the value Years, and the RetentionDuration parameter is set to the value 365, the Microsoft Purview compliance portal will display 1 year as the content hold duration.
+For example, if this parameter is set to the value Years, and the RetentionDuration parameter is set to the value 365, the Microsoft Purview compliance portal displays 1 year as the content hold duration.
 
 ```yaml
 Type: HoldDurationHint
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ApplicationAccessPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-ApplicationAccessPolicy.md
index eef7ce2879..b2e7429a58 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ApplicationAccessPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ApplicationAccessPolicy.md
@@ -32,7 +32,7 @@ Set-ApplicationAccessPolicy [-Identity] <ApplicationAccessPolicyIdParameter>
 ## DESCRIPTION
 This feature applies only to apps connecting to the Microsoft Graph API for Outlook resources.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ArcConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-ArcConfig.md
index 8b419a49ce..9bbb3811d5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ArcConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ArcConfig.md
@@ -31,7 +31,7 @@ Set-ArcConfig [-Identity] <HostedConnectionFilterPolicyIdParameter> -ArcTrustedS
 ## DESCRIPTION
 Services that modify message content in transit before delivery can invalidate DKIM email signatures and affect the authentication of the message. These services can use ARC to provide details of the original authentication before the modifications occurred. Your organization can then trust these details to help authenticate the message.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AtpPolicyForO365.md b/exchange/exchange-ps/ExchangePowerShell/Set-AtpPolicyForO365.md
index 5f93a93d5c..4b4654ecbd 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-AtpPolicyForO365.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-AtpPolicyForO365.md
@@ -42,7 +42,7 @@ Safe Documents scans documents and files that are opened in Protected View. For
 
 Safe Attachments for SharePoint, OneDrive, and Microsoft Teams prevents users from opening and downloading files that are identified as malicious. For more information, see [Safe Attachments for SharePoint, OneDrive, and Microsoft Teams](https://learn.microsoft.com/defender-office-365/safe-attachments-for-spo-odfb-teams-about).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -79,7 +79,7 @@ Accept wildcard characters: False
 
 The AllowSafeDocsOpen parameter specifies whether users can click through and bypass the Protected View container even when Safe Documents identifies a file as malicious. Valid values are:
 
-- $true: Users are allowed to exit the Protected View container even if the document has been identified as malicious.
+- $true: Users are allowed to exit the Protected View container even if the document is identified as malicious.
 - $false: Users aren't allowed to exit Protected View in case of a malicious detection.
 
 This parameter is meaningful only when the EnableSafeDocs parameter value is $true.
@@ -124,7 +124,7 @@ Accept wildcard characters: False
 The EnableATPForSPOTeamsODB parameter enables or disables Safe Attachments for SharePoint, OneDrive, and Microsoft Teams. Valid values are:
 
 - $true: Safe Attachments for SharePoint, OneDrive, and Microsoft Teams is enabled. SharePoint admins can use the DisallowInfectedFileDownload parameter on the [Set-SPOTenant](https://learn.microsoft.com/powershell/module/sharepoint-online/Set-SPOTenant) cmdlet to control whether users are allowed to download files that are found to be malicious.
-- $false: Safe Attachments for SharePoint, OneDrive, and Microsoft Teams is disabled. This is the default value.
+- $false: Safe Attachments for SharePoint, OneDrive, and Microsoft Teams is disabled. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -144,8 +144,8 @@ Accept wildcard characters: False
 
 The EnableSafeDocs parameter enables or disables Safe Documents in organizations with Microsoft 365 A5 or Microsoft 365 E5 Security licenses. Valid values are:
 
-- $true: Safe Documents is enabled and will upload user files to Microsoft Defender for Endpoint for scanning and verification.
-- $false: Safe Documents is disabled. This is the default value.
+- $true: Safe Documents is enabled and uploads user files to Microsoft Defender for Endpoint for scanning and verification.
+- $false: Safe Documents is disabled. This value is the default.
 
 For more information about Safe Documents, see [Safe Documents in Microsoft 365 A5 or E5 Security](https://learn.microsoft.com/defender-office-365/safe-documents-in-e5-plus-security-about)
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AttachmentFilterListConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-AttachmentFilterListConfig.md
index 1c317461b0..40c8190235 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-AttachmentFilterListConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-AttachmentFilterListConfig.md
@@ -55,7 +55,7 @@ This example modifies the action that the Attachment Filtering agent takes on an
 
 The Action parameter specifies how the Attachment Filtering agent handles an attachment that matches an entry on the attachment filter list. Valid values are:
 
-- Reject: This value prevents both the email message and attachment from being delivered to the recipient and issues a non-delivery report (NDR) to the sender. This is the default value.
+- Reject: This value prevents both the email message and attachment from being delivered to the recipient and issues a non-delivery report (NDR) to the sender. This value is the default.
 - Strip: This value removes the offending attachment from the email message and allows the message and other attachments that don't match an entry on the attachment filter list through. A notification that the attachment was removed is added to the email message.
 - SilentDelete: This value prevents both the email message and the attachment from being delivered to the recipient. No notification that the email message and attachment were blocked is sent to the sender.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AuthConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-AuthConfig.md
index ab3ba426ba..8bdf7d268b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-AuthConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-AuthConfig.md
@@ -70,7 +70,7 @@ Set-AuthConfig [-Realm <String>]
 ## DESCRIPTION
 The Set-AuthConfig parameter defines Microsoft Exchange as a partner application for server-to-server authentication with other partner applications such as Microsoft SharePoint 2013 and Microsoft Lync 2013 or Skype for Business Server 2015, including the certificate used for signing tokens. It's generally not required for this configuration to be modified except in some cases where you must use a different certificate instead of the self-signed certificate created by Exchange Setup or to use a new certificate after the old one has expired.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -79,7 +79,7 @@ You need to be assigned permissions before you can run this cmdlet. Although thi
 Set-AuthConfig -NewCertificateThumbprint DB821B4FCA2A5DA9593B9DE00C86BC5EA35D0FC0 -NewCertificateEffectiveDate 4/17/2014
 ```
 
-This example specifies a new certificate and a date when the certificate will become effective.
+This example specifies a new certificate and a date when the certificate is effective.
 
 ### Example 2
 ```powershell
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AuthRedirect.md b/exchange/exchange-ps/ExchangePowerShell/Set-AuthRedirect.md
index 8facbc23d1..f23fcfa6f2 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-AuthRedirect.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-AuthRedirect.md
@@ -31,7 +31,7 @@ Set-AuthRedirect [-Identity] <AuthRedirectIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -112,7 +112,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-The TargetUrl parameter specifies the FQDN of the Exchange 2013 Client Access server that will process the Oauth request.
+The TargetUrl parameter specifies the FQDN of the Exchange 2013 Client Access server that processes the Oauth request.
 
 ```yaml
 Type: String
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AuthServer.md b/exchange/exchange-ps/ExchangePowerShell/Set-AuthServer.md
index 9086e663d8..5419f5f7de 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-AuthServer.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-AuthServer.md
@@ -81,7 +81,7 @@ Partner applications authorized by Exchange can access their resources after the
 
 Use the Set-AuthServer cmdlet to enable or disable the authorization server, change the AuthMetadataUrl parameter or refresh authorization metadata.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -199,9 +199,9 @@ Accept wildcard characters: False
 
 This parameter is available only in Exchange Server 2016 (CU18 or higher) and Exchange Server 2019 (CU7 or higher).
 
-The DomainName parameter specifies the tenant domain that's linked with the AuthServer object. This parameter uses the syntax: "tenantname.onmicrosoft.com".
+The DomainName parameter links a cloud-based organization to the corresponding AuthServer object in the Multi-Tenant Exchange Hybrid. This parameter uses the syntax: "domain.onmicrosoft.com".
 
-This parameter is used to link Tenant to the corresponding authserver object in the Multi-Tenant Exchange Hybrid. For example, if DomainName is contoso.onmicrosoft.com, then the AuthServer object will be associated with the contoso tenant.
+For example, if the DomainName value is contoso.onmicrosoft.com, the AuthServer object is associated with the contoso cloud-based organization.
 
 ```yaml
 Type: MultiValuedProperty
@@ -223,7 +223,7 @@ The Enabled parameter specifies whether the authorization server is enabled. Onl
 
 The Enabled parameter specifies whether the authorization server is enabled. Valid values are:
 
-- $true: Authorization tokens that are issued by the authorization server are accepted. This is the default value
+- $true: Authorization tokens that are issued by the authorization server are accepted. This value is the default
 - $false: The authorization server does not issue or accept authorization tokens.
 
 ```yaml
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AuthenticationPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-AuthenticationPolicy.md
index 480c57c088..cf7790c298 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-AuthenticationPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-AuthenticationPolicy.md
@@ -13,7 +13,7 @@ title: Set-AuthenticationPolicy
 # Set-AuthenticationPolicy
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-AuthenticationPolicy cmdlet to modify authentication policies in your organization.
 
@@ -60,7 +60,7 @@ Set-AuthenticationPolicy [-Identity] <AuthPolicyIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -616,7 +616,7 @@ The switch applies to the entire organization. The Identity parameter is require
 - Legacy Exchange Online tokens will be turned off for all organizations from August 2025 through September 2025. Once turned off, you can't use the _AllowLegacyExchangeTokens_ switch on the **Set-AuthenticationPolicy** cmdlet to turn on these tokens. You get the warning "Legacy Exchange Online tokens are disabled" when you run the command `Get-AuthenticationPolicy -AllowLegacyExchangeTokens`. You can [contact Microsoft Support to request an exception](https://aka.ms/LegacyTokensByOctober). For more information, see [Nested app authentication and Outlook legacy tokens deprecation FAQ](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens).
 - Apart from the Identity parameter, this switch disregards other authentication policy parameters used in the same command. We recommend running separate commands for other authentication policy changes.
 - It might take up to 24 hours for the change to take effect across your entire organization.
-- Legacy Exchange tokens issued to Outlook add-ins before token blocking was implemented in your organization will remain valid until they expire.
+- Legacy Exchange tokens issued to Outlook add-ins before token blocking was implemented in your organization remain valid until they expire.
 - Blocking legacy Exchange tokens might cause some Microsoft add-ins to stop working. These add-ins are being updated to no longer use legacy tokens.
 
 ```yaml
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AutoSensitivityLabelPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-AutoSensitivityLabelPolicy.md
index 7c95423e8b..e8c95a366c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-AutoSensitivityLabelPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-AutoSensitivityLabelPolicy.md
@@ -129,7 +129,7 @@ Accept wildcard characters: False
 
 > Applicable: Security & Compliance
 
-The AddExchangeLocation parameter adds email messages to the policy if they're not already included. The valid value for this parameter is All.
+The AddExchangeLocation parameter adds email messages to the policy if they aren't already included. The valid value for this parameter is All.
 
 If the policy doesn't already include email messages (in the output of the Get-AutoSensitivityLabelPolicy cmdlet, the ExchangeLocation property value is blank), you can use this parameter in the following procedures:
 
@@ -243,7 +243,7 @@ Accept wildcard characters: False
 
 > Applicable: Security & Compliance
 
-The ApplySensitivityLabel parameter selects which label to be used for the policy. This will override the previous label on the policy.
+The ApplySensitivityLabel parameter selects the label to use for the policy. This value overrides the previous label on the policy.
 
 ```yaml
 Type: String
@@ -326,7 +326,7 @@ Accept wildcard characters: False
 
 The Enabled parameter enables or disables the policy. Valid values are:
 
-- $true: The policy is enabled. This is the default value.
+- $true: The policy is enabled. This value is the default.
 - $false: The policy is disabled.
 
 ```yaml
@@ -706,7 +706,7 @@ Accept wildcard characters: False
 The OverwriteLabel parameter specifies whether to overwrite a manual label. Valid values are:
 
 - $true: Overwrite the manual label.
-- $false: Don't overwrite the manual label. This is the default value.
+- $false: Don't overwrite the manual label. This value is the default.
 
 This parameter works only on Exchange locations.
 
@@ -974,7 +974,7 @@ Accept wildcard characters: False
 Use the StartSimulation parameter to restart the simulation for updated results. Valid values are:
 
 - $true: Restart the simulation for updated results. **Any edits to an auto-labeling policy require restarting the simulation by using this value.**
-- $false: This is the default value
+- $false: This value is the default
 
 ```yaml
 Type: Boolean
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AutoSensitivityLabelRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-AutoSensitivityLabelRule.md
index a41e2735f2..ee05901854 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-AutoSensitivityLabelRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-AutoSensitivityLabelRule.md
@@ -335,7 +335,7 @@ Accept wildcard characters: False
 The Disabled parameter specifies whether the case hold rule is enabled or disabled. Valid values are:
 
 - $true: The rule is disabled.
-- $false: The rule is enabled. This is the default value.
+- $false: The rule is enabled. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -446,7 +446,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 You can use this condition in auto-labeling policy rules that are scoped only to Exchange.
 
@@ -689,7 +689,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 You can use this exception in auto-labeling policy rules that are scoped only to Exchange.
 
@@ -1158,7 +1158,7 @@ Accept wildcard characters: False
 The ReportSeverityLevel parameter specifies the severity level of the incident report for content detections based on the rule. Valid values are:
 
 - None: You can't select this value if the rule has no actions configured.
-- Low: This is the default value.
+- Low: This value is the default.
 - Medium
 - High
 
@@ -1183,7 +1183,7 @@ The RuleErrorAction parameter specifies what to do if an error is encountered du
 
 - Ignore
 - RetryThenBlock
-- Blank (the value $null): This is the default value.
+- Blank (the value $null): This value is the default.
 
 ```yaml
 Type: PolicyRuleErrorAction
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AutodiscoverVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Set-AutodiscoverVirtualDirectory.md
index d079983959..ca01c30e74 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-AutodiscoverVirtualDirectory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-AutodiscoverVirtualDirectory.md
@@ -40,7 +40,7 @@ Set-AutodiscoverVirtualDirectory [-Identity] <VirtualDirectoryIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -97,7 +97,7 @@ Accept wildcard characters: False
 
 The BasicAuthentication parameter specifies whether Basic authentication is enabled on the virtual directory. Valid values are:
 
-- $true: Basic authentication is enabled. This is the default value.
+- $true: Basic authentication is enabled. This value is the default.
 - $false: Basic authentication is disabled.
 
 ```yaml
@@ -140,7 +140,7 @@ Accept wildcard characters: False
 The DigestAuthentication parameter specifies whether Digest authentication is enabled on the virtual directory. Valid values are:
 
 - $true: Digest authentication is enabled.
-- $false: Digest authentication is disabled. This is the default value.
+- $false: Digest authentication is disabled. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -182,7 +182,7 @@ The ExtendedProtectionFlags parameter specifies custom settings for Extended Pro
 - AllowDotlessSPN: Required if you want to use Service Principal Name (SPN) values that don't contain FQDNs (for example, HTTP/ContosoMail instead of HTTP/mail.contoso.com). You specify SPNs with the ExtendedProtectionSPNList parameter. This setting makes Extended Protection for Authentication less secure because dotless certificates aren't unique, so it isn't possible to ensure that the client-to-proxy connection was established over a secure channel.
 - NoServiceNameCheck: The SPN list isn't checked to validate a channel binding token. This setting makes Extended Protection for Authentication less secure. We generally don't recommend this setting.
 - Proxy: A proxy server is responsible for terminating the SSL channel. To use this setting, you need to register an SPN by using the ExtendedProtectionSPNList parameter.
-- ProxyCoHosting: HTTP and HTTPS traffic may be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server.
+- ProxyCoHosting: HTTP and HTTPS traffic might be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server.
 
 ```yaml
 Type: MultiValuedProperty
@@ -202,7 +202,7 @@ Accept wildcard characters: False
 
 The ExtendedProtectionSPNList parameter specifies a list of valid Service Principal Names (SPNs) if you're using Extended Protection for Authentication on the virtual directory. Valid values are:
 
-- $null: This is the default value.
+- $null: This value is the default.
 - Single SPN or comma delimited list of valid SPNs: The SPN value format is `Protocol\FQDN`. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter.
 
 ```yaml
@@ -223,8 +223,8 @@ Accept wildcard characters: False
 
 The ExtendedProtectionTokenChecking parameter defines how you want to use Extended Protection for Authentication on the virtual directory. Extended Protection for Authentication isn't enabled by default. Valid values are:
 
-- None: Extended Protection for Authentication isn't be used on the virtual directory. This is the default value.
-- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication will work, but may not be as secure as connections that use Extended Protection for Authentication.
+- None: Extended Protection for Authentication isn't be used on the virtual directory. This value is the default.
+- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication work, but might not be as secure as connections that use Extended Protection for Authentication.
 - Require: Extended Protection for Authentication is used for all connections between clients and the virtual directory. If either the client or server doesn't support it, the connection will fail. If you use this value, you also need to set an SPN value for the ExtendedProtectionSPNList parameter.
 
 **Note**: If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter.
@@ -287,7 +287,7 @@ Accept wildcard characters: False
 
 The OAuthAuthentication parameter specifies whether OAuth authentication is enabled on the virtual directory. Valid values are:
 
-- $true: OAuth authentication is enabled. This is the default value.
+- $true: OAuth authentication is enabled. This value is the default.
 - $false: OAuth authentication is disabled.
 
 ```yaml
@@ -326,7 +326,7 @@ Accept wildcard characters: False
 
 The WindowsAuthentication parameter specifies whether Integrated Windows authentication is enabled on the virtual directory. Valid values are:
 
-- $true: Integrated Windows authentication is enabled. This is the default value.
+- $true: Integrated Windows authentication is enabled. This value is the default.
 - $false: Integrated Windows authentication is disabled.
 
 ```yaml
@@ -347,7 +347,7 @@ Accept wildcard characters: False
 
 The WSSecurityAuthentication parameter specifies whether WS-Security (Web Services Security) authentication is enabled on the virtual directory. Valid values are:
 
-- $true: WS-Security authentication is enabled. This is the default value.
+- $true: WS-Security authentication is enabled. This value is the default.
 - $false: WS-Security authentication is disabled.
 
 ```yaml
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AvailabilityConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-AvailabilityConfig.md
index 2364adde75..1eb3727049 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-AvailabilityConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-AvailabilityConfig.md
@@ -13,7 +13,7 @@ title: Set-AvailabilityConfig
 # Set-AvailabilityConfig
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-AvailabilityConfig cmdlet to set the access level for free/busy information.
 
@@ -39,7 +39,7 @@ For cross-forest availability services to retrieve free/busy information in the
 
 In Exchange Online, this cmdlet lets you update the set of tenant ids that free/busy information sharing is allowed with.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AvailabilityReportOutage.md b/exchange/exchange-ps/ExchangePowerShell/Set-AvailabilityReportOutage.md
index 7ff6054fec..6920c4e782 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-AvailabilityReportOutage.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-AvailabilityReportOutage.md
@@ -46,7 +46,7 @@ Set-AvailabilityReportOutage [-Identity] <AvailabilityReportOutageIdParameter> -
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-CASMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Set-CASMailbox.md
index 9a16d536b4..e4545c1e31 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-CASMailbox.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-CASMailbox.md
@@ -13,7 +13,7 @@ title: Set-CASMailbox
 # Set-CASMailbox
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-CASMailbox cmdlet to configure client access settings on a mailbox. For example, you can configure settings for Exchange ActiveSync, Outlook, Outlook on the web, POP3, and IMAP4.
 
@@ -81,7 +81,7 @@ Set-CASMailbox [-Identity] <MailboxIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -192,7 +192,7 @@ Accept wildcard characters: False
 The ActiveSyncDebugLogging parameter enables or disables Exchange ActiveSync debug logging for the mailbox. Valid values are:
 
 - $true: ActiveSync debug logging is enabled for 48 hours in Exchange Online, and 72 hours in Exchange Server. After the time period expires, the value reverts to $false.
-- $false: ActiveSync debug logging is disabled. This is the default value
+- $false: ActiveSync debug logging is disabled. This value is the default
 
 ```yaml
 Type: Boolean
@@ -212,7 +212,7 @@ Accept wildcard characters: False
 
 The ActiveSyncEnabled parameter enables or disables access to the mailbox using Exchange ActiveSync. Valid values are:
 
-- $true: Access to the mailbox using ActiveSync is enabled. This is the default value.
+- $true: Access to the mailbox using ActiveSync is enabled. This value is the default.
 - $false. Access to the mailbox using ActiveSync is disabled. Other ActiveSync settings in this cmdlet are ignored.
 
 For more information, see [Enable or disable Exchange ActiveSync for a mailbox in Exchange Online](https://learn.microsoft.com/exchange/recipients-in-exchange-online/manage-user-mailboxes/enable-or-disable-exchange-activesync), or [Enable or disable Exchange ActiveSync access to mailboxes in Exchange Server](https://learn.microsoft.com/exchange/clients/exchange-activesync/activesync-mailbox-access).
@@ -260,7 +260,7 @@ Accept wildcard characters: False
 The ActiveSyncSuppressReadReceipt parameter controls the behavior of read receipts for Exchange ActiveSync clients that access the mailbox. Valid values are:
 
 - $true: Read receipts are not automatically returned when the user opens a message sent with a read receipt request.
-- $false: A read receipt is automatically returned when the user opens a message sent with a read receipt request. This is the default value.
+- $false: A read receipt is automatically returned when the user opens a message sent with a read receipt request. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -343,7 +343,7 @@ This parameter is available only in on-premises Exchange.
 
 The ECPEnabled parameter enables or disables access the Exchange admin center (EAC) or the Exchange Control Panel (ECP) for the specified user. Valid values are:
 
-- $true: Access to the EAC or ECP is enabled. This is the default value.
+- $true: Access to the EAC or ECP is enabled. This value is the default.
 - $false: Access to the EAC or ECP is disabled.
 
 ```yaml
@@ -403,7 +403,7 @@ Accept wildcard characters: False
 
 The EwsAllowEntourage parameter enables or disables access to the mailbox by Microsoft Entourage clients that use Exchange Web Services (for example, Entourage 2008 for Mac, Web Services Edition).
 
-- $true: Access to the mailbox using Microsoft Entourage is enabled. This is the default value.
+- $true: Access to the mailbox using Microsoft Entourage is enabled. This value is the default.
 - $false: Access to the mailbox using Microsoft Entourage is disabled.
 
 ```yaml
@@ -448,7 +448,7 @@ Accept wildcard characters: False
 
 The EwsAllowMacOutlook parameter enables or disables access to the mailbox by Outlook for Mac clients that use Exchange Web Services (for example, Outlook for Mac 2011 or later). Valid values are:
 
-- $true: Outlook for Mac clients that use EWS are allowed to access the mailbox. This is the default value.
+- $true: Outlook for Mac clients that use EWS are allowed to access the mailbox. This value is the default.
 - $false: Outlook for Mac clients that use EWS are not allowed to access the mailbox.
 
 In the cloud-based service, access for Outlook for Mac clients that use Microsoft Sync technology is controlled by the MacOutlookEnabled parameter.
@@ -541,7 +541,7 @@ Accept wildcard characters: False
 
 The EwsEnabled parameter enables or disables access to the mailbox using Exchange Web Services clients. Valid values are:
 
-- $true: Access to the mailbox using EWS is enabled. This is the default value.
+- $true: Access to the mailbox using EWS is enabled. This value is the default.
 - $false: Access to the mailbox using EWS is disabled. Other Exchange Web Services settings in this cmdlet are ignored.
 
 The value of this parameter is meaningful only if the EwsEnabled parameter on the Set-OrganizationConfig parameter isn't set to the value $false.
@@ -612,7 +612,7 @@ Accept wildcard characters: False
 
 The ImapEnabled parameter enables or disables access to the mailbox using IMAP4 clients. Valid values are:
 
-- $true: Access to the mailbox using IMAP4 is enabled. This is the default value.
+- $true: Access to the mailbox using IMAP4 is enabled. This value is the default.
 - $fale: Access to the mailbox using IMAP4 is disabled. The other IMAP4 settings in this cmdlet are ignored.
 
 For more information, see [Enable or Disable POP3 or IMAP4 access for a user in Exchange Online](https://learn.microsoft.com/exchange/clients-and-mobile-in-exchange-online/pop3-and-imap4/enable-or-disable-pop3-or-imap4-access), or [Enable or disable POP3 or IMAP4 access to mailboxes in Exchange Server](https://learn.microsoft.com/exchange/clients/pop3-and-imap4/configure-mailbox-access).
@@ -638,7 +638,7 @@ This parameter is available only in on-premises Exchange.
 The ImapEnableExactRFC822Size parameter specifies how message sizes are presented to IMAP4 clients that access the mailbox. Valid values are:
 
 - $true: Calculate the exact message size.
-- $false: Use an estimated message size. This is the default value.
+- $false: Use an estimated message size. This value is the default.
 
 We don't recommend changing this value unless you determine that the default setting causes problems for IMAP4 clients. To change the value of this parameter, you also need to set the value of the ImapUseProtocolDefaults parameter to $false.
 
@@ -661,7 +661,7 @@ Accept wildcard characters: False
 The ImapForceICalForCalendarRetrievalOption parameter specifies how meeting requests are presented to IMAP4 clients that access the mailbox. Valid values are:
 
 - $true: All meeting requests are in the iCal format.
-- $false: All meeting requests appear as Outlook on the web links. This is the default value.
+- $false: All meeting requests appear as Outlook on the web links. This value is the default.
 
 To change the value of this parameter, you also need to set the value of the ImapUseProtocolDefaults parameter to $false.
 
@@ -712,7 +712,7 @@ Accept wildcard characters: False
 The ImapSuppressReadReceipt parameter controls the behavior of read receipts for IMAP4 clients that access the mailbox. Valid values are:
 
 - $true: The user receives a read receipt when the recipient opens the message.
-- $false: The user receives two read receipts: one when the message is downloaded and another when the message is opened. This is the default value.
+- $false: The user receives two read receipts: one when the message is downloaded and another when the message is opened. This value is the default.
 
 To change the value of this parameter, you also need to set the value of the ImapUseProtocolDefaults parameter to $false.
 
@@ -734,7 +734,7 @@ Accept wildcard characters: False
 
 The ImapUseProtocolDefaults parameter specifies whether to use the IMAP4 protocol defaults for the mailbox. Valid values are:
 
-- $true: Use the protocol defaults for IMAP4 access to the mailbox. This is the default value.
+- $true: Use the protocol defaults for IMAP4 access to the mailbox. This value is the default.
 - $false: Use custom protocol settings for IMAP4 access to the mailbox.
 
 You need to set this parameter to $false when you use any of the following IMAP4 parameters:
@@ -787,7 +787,7 @@ This parameter is available only in the cloud-based service.
 
 The MacOutlookEnabled parameter enables or disables access to the mailbox using Outlook for Mac clients that use Microsoft Sync technology. Valid values are:
 
-- $true: Access to the mailbox using Outlook for Mac clients is enabled. This is the default value.
+- $true: Access to the mailbox using Outlook for Mac clients is enabled. This value is the default.
 - $false: Access to the mailbox using Outlook for Mac clients is disabled.
 
 Access for older Outlook for Mac clients that use Exchange Web Services is controlled by the EwsAllowMacOutlook parameter.
@@ -813,7 +813,7 @@ This parameter is available only in on-premises Exchange.
 The MAPIBlockOutlookNonCachedMode parameter controls access to the mailbox using Outlook in online or offline mode. Valid values are:
 
 - $true: Only Outlook clients that are configured to use Cached Exchange Mode (offline mode) are allowed to access the mailbox.
-- $false: The state of the Cached Exchange Mode setting isn't checked before Outlook clients are allowed to access the mailbox (online mode and offline mode are allowed). This is the default value.
+- $false: The state of the Cached Exchange Mode setting isn't checked before Outlook clients are allowed to access the mailbox (online mode and offline mode are allowed). This value is the default.
 
 ```yaml
 Type: Boolean
@@ -838,7 +838,7 @@ The MAPIBlockOutlookExternalConnectivity parameter enables or disables external
 - $true: External Outlook clients can't use Outlook Anywhere, MAPI over HTTP, or EWS to access the mailbox.
 - $false: External Outlook clients can use Outlook Anywhere, MAPI over HTTP, or EWS to access the mailbox.
 
-**Note**: If your organization uses the same Autodiscover URL values for internal and external clients, setting this parameter to $true won't block access for external clients.
+**Note**: If your organization uses the same Autodiscover URL values for internal and external clients, setting this parameter to $true doesn't block access for external clients.
 
 ```yaml
 Type: Boolean
@@ -861,7 +861,7 @@ This parameter is available only in on-premises Exchange.
 The MAPIBlockOutlookRpcHttp parameter enables or disables access to the mailbox in Outlook using Outlook Anywhere. Valid values are:
 
 - $true: Access to the mailbox using Outlook Anywhere is disabled.
-- $false: Access to the mailbox using Outlook Anywhere is enabled. This is the default value.
+- $false: Access to the mailbox using Outlook Anywhere is enabled. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -905,7 +905,7 @@ Accept wildcard characters: False
 
 The MAPIEnabled parameter enables or disables access to the mailbox using MAPI clients (for example, Outlook). Valid values are:
 
-- $true: Access to the mailbox using MAPI clients is enabled. This is the default value.
+- $true: Access to the mailbox using MAPI clients is enabled. This value is the default.
 - $false: Access to the mailbox using MAPI clients is disabled. The other MAPI settings in this cmdlet are ignored.
 
 For more information, see[Enable or disable MAPI for a mailbox in Exchange Online](https://learn.microsoft.com/exchange/recipients-in-exchange-online/manage-user-mailboxes/enable-or-disable-mapi), or [Enable or disable MAPI access to mailboxes in Exchange Server](https://learn.microsoft.com/exchange/clients/mapi-mailbox-access).
@@ -932,7 +932,7 @@ The MapiHttpEnabled parameter enables or disables access to the mailbox in Outlo
 
 - $true: Access to the mailbox using MAPI over HTTP is enabled.
 - $false: Access to the mailbox using MAPI over HTTP is disabled.
-- $null (blank): The setting isn't configured. The mailbox uses the organization setting for MAPI over HTTP (the MapiHttpEnabled parameter on the Set-OrganizationConfig cmdlet). This is the default value.
+- $null (blank): The setting isn't configured. The mailbox uses the organization setting for MAPI over HTTP (the MapiHttpEnabled parameter on the Set-OrganizationConfig cmdlet). This value is the default.
 
 ```yaml
 Type: Boolean
@@ -975,7 +975,7 @@ This parameter is available only in the cloud-based service.
 The OneWinNativeOutlookEnabled parameter enables or disables access to the mailbox using the new Outlook for Windows.
 Valid values are:
 
-- $true: Access to the mailbox using the new Outlook for Windows is enabled. This is the default value.
+- $true: Access to the mailbox using the new Outlook for Windows is enabled. This value is the default.
 - $false: Access to the mailbox using the new Outlook for Windows is disabled.
 
 ```yaml
@@ -998,7 +998,7 @@ This parameter is available only in the cloud-based service.
 
 The OutlookMobileEnabled parameter enables or disables access to the mailbox using Outlook for iOS and Android. Valid values are:
 
-- $true: Access to the mailbox using Outlook for iOS and Android is enabled. This is the default value.
+- $true: Access to the mailbox using Outlook for iOS and Android is enabled. This value is the default.
 - $false: Access to the mailbox using Outlook for iOS and Android is disabled.
 
 ```yaml
@@ -1019,7 +1019,7 @@ Accept wildcard characters: False
 
 The OWAEnabled parameter enables or disables access to the mailbox using Outlook on the web (formerly known as Outlook Web App or OWA) and the new Outlook for Windows. Valid values are:
 
-- $true: Access to the mailbox using Outlook on the web is enabled. This is the default value.
+- $true: Access to the mailbox using Outlook on the web is enabled. This value is the default.
 - $false: Access to the mailbox using Outlook on the web and the new Outlook for Windows is disabled. The other Outlook on the web settings in this cmdlet are ignored.
 
 For more information, see [Enable or disable Outlook on the web for a mailbox in Exchange Online](https://learn.microsoft.com/exchange/recipients-in-exchange-online/manage-user-mailboxes/enable-or-disable-outlook-web-app), or [Enable or disable Outlook on the web access to mailboxes in Exchange Server](https://learn.microsoft.com/exchange/clients/outlook-on-the-web/mailbox-access).
@@ -1042,7 +1042,7 @@ Accept wildcard characters: False
 
 The OWAforDevicesEnabled parameter enables or disables access to the mailbox using the older Outlook Web App (OWA) app on iOS and Android devices. Valid values are:
 
-- $true: Access to the mailbox using OWA for Devices is enabled. This is the default value.
+- $true: Access to the mailbox using OWA for Devices is enabled. This value is the default.
 - $false: Access to the mailbox using OWA for Devices is disabled.
 
 ```yaml
@@ -1087,7 +1087,7 @@ Accept wildcard characters: False
 
 The PopEnabled parameter enables or disables access to the mailbox using POP3 clients. Valid values are:
 
-- $true: Access to the mailbox using POP3 clients is enabled. This is the default value.
+- $true: Access to the mailbox using POP3 clients is enabled. This value is the default.
 - $false: Access to the mailbox using POP3 clients is disabled. The other POP3 settings in this cmdlet are ignored.
 
 For more information, see [Enable or Disable POP3 or IMAP4 access for a user in Exchange Online](https://learn.microsoft.com/exchange/clients-and-mobile-in-exchange-online/pop3-and-imap4/enable-or-disable-pop3-or-imap4-access), or [Enable or disable POP3 or IMAP4 access to mailboxes in Exchange Server](https://learn.microsoft.com/exchange/clients/pop3-and-imap4/configure-mailbox-access).
@@ -1113,7 +1113,7 @@ This parameter is available only in on-premises Exchange.
 The PopEnableExactRFC822Size parameter specifies how message sizes are presented to POP3 clients that access the mailbox. Valid values are:
 
 - $true: Calculate the exact message size.
-- $false: Use an estimated message size. This is the default value
+- $false: Use an estimated message size. This value is the default
 
 We don't recommend changing this value unless you determine that the default setting causes problems for POP3 clients. To change the value of this parameter, you also need to set the value of the PopUseProtocolDefaults parameter to $false.
 
@@ -1136,7 +1136,7 @@ Accept wildcard characters: False
 The PopForceICalForCalendarRetrievalOption parameter specifies how meeting requests are presented to POP3 clients that access the mailbox. Valid values are:
 
 - $true: All meeting requests are in the iCal format.
-- $false: All meeting requests appear as Outlook on the web links. This is the default value.
+- $false: All meeting requests appear as Outlook on the web links. This value is the default.
 
 To change the value of this parameter, you also need to set the value of the PopUseProtocolDefaults parameter to $false.
 
@@ -1187,7 +1187,7 @@ Accept wildcard characters: False
 The PopSuppressReadReceipt parameter controls the behavior of read receipts for POP3 clients that access the mailbox. Valid values are:
 
 - $true: The user receives a read receipt when the recipient opens the message.
-- $false: The user receives two read receipts: one when the message is downloaded and another when the message is opened. This is the default value.
+- $false: The user receives two read receipts: one when the message is downloaded and another when the message is opened. This value is the default.
 
 To change the value of this parameter, you also need to set the value of the PopUseProtocolDefaults parameter to $false.
 
@@ -1209,7 +1209,7 @@ Accept wildcard characters: False
 
 The PopUseProtocolDefaults parameter specifies whether to use the POP3 protocol defaults for the mailbox. Valid values are:
 
-- $true: Use the protocol defaults for POP3 access to the mailbox. This is the default value.
+- $true: Use the protocol defaults for POP3 access to the mailbox. This value is the default.
 - $false: Use custom protocol settings for POP3 access to the mailbox.
 
 You need to set this parameter to $false when you use any of following parameters:
@@ -1258,7 +1258,7 @@ Accept wildcard characters: False
 The PublicFolderClientAccess parameter enables or disables access to public folders in Microsoft Outlook. Valid values are:
 
 - $true: The user can access public folders in Outlook if the value of the PublicFolderShowClientControl parameter on the Set-OrganizationConfig cmdlet is $true (the default value is $false).
-- $false: The user can't access public folders in Outlook if the value of the PublicFolderShowClientControl parameter on the Set-OrganizationConfig cmdlet is $true. This is the default value.
+- $false: The user can't access public folders in Outlook if the value of the PublicFolderShowClientControl parameter on the Set-OrganizationConfig cmdlet is $true. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -1298,7 +1298,7 @@ Accept wildcard characters: False
 
 This parameter is available only in on-premises Exchange.
 
-The SamAccountName parameter (also known as the pre-Windows 2000 user account or group name) specifies an object identifier that's compatible with older versions of Microsoft Windows client and server operating systems. The value can contain letters, numbers, spaces, periods (.), and the following characters: !, #, $, %, ^, &, -, \_, {, }, and ~. The last character can't be a period. Unicode characters are allowed, but accented characters may generate collisions (for example, o and ö match). The maximum length is 20 characters.
+The SamAccountName parameter (also known as the pre-Windows 2000 user account or group name) specifies an object identifier that's compatible with older versions of Microsoft Windows client and server operating systems. The value can contain letters, numbers, spaces, periods (.), and the following characters: !, #, $, %, ^, &, -, \_, {, }, and ~. The last character can't be a period. Unicode characters are allowed, but accented characters might generate collisions (for example, o and ö match). The maximum length is 20 characters.
 
 ```yaml
 Type: String
@@ -1318,7 +1318,7 @@ Accept wildcard characters: False
 
 The ShowGalAsDefaultView parameter specifies whether the global address list (GAL) is the default recipient picker for messages. Valid values are:
 
-- $true: Use the GAL as the primary address picker. This is the default value.
+- $true: Use the GAL as the primary address picker. This value is the default.
 - $false: Don't use the GAL as the primary address picker.
 
 ```yaml
@@ -1350,7 +1350,7 @@ Valid values for this parameter are:
 
 - $true: Authenticated SMTP is disabled for the mailbox.
 - $false: Authenticated SMTP is enabled for the mailbox.
-- blank ($null): This is the default value. The authenticated SMTP setting for the mailbox is controlled by the corresponding SmtpClientAuthenticationDisabled parameter on the Set-TransportConfig cmdlet for the whole organization.
+- blank ($null): This value is the default. The authenticated SMTP setting for the mailbox is controlled by the corresponding SmtpClientAuthenticationDisabled parameter on the Set-TransportConfig cmdlet for the whole organization.
 
 To selectively enable authenticated SMTP for specific mailboxes only: disable authenticated SMTP at the organizational level ($true), enable it for the specific mailboxes ($false), and leave the rest of the mailboxes with their default value ($null).
 
@@ -1374,7 +1374,7 @@ This parameter is available only in the cloud-based service.
 
 The UniversalOutlookEnabled parameter enables or disables access to the mailbox using Windows 10 Mail and Calendar. Valid values are:
 
-- $true: Access to the mailbox using Windows 10 Mail and Calendar is enabled. This is the default value.
+- $true: Access to the mailbox using Windows 10 Mail and Calendar is enabled. This value is the default.
 - $false: Access to the mailbox using Windows 10 Mail and Calendar is disabled.
 
 ```yaml
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-CASMailboxPlan.md b/exchange/exchange-ps/ExchangePowerShell/Set-CASMailboxPlan.md
index d755e6ec94..d7570a544d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-CASMailboxPlan.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-CASMailboxPlan.md
@@ -39,7 +39,7 @@ Set-CASMailboxPlan [-Identity] <MailboxPlanIdParameter>
 ## DESCRIPTION
 A CAS mailbox plan is tied to the corresponding mailbox plan that has the same name (and display name). Like mailbox plans, CAS mailbox plans correspond to license types, and are applied to a mailbox when you license the user. The availability of a CAS mailbox plan is determined by your selections when you enroll in the service and the age of your organization.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -82,7 +82,7 @@ Accept wildcard characters: False
 
 The ActiveSyncEnabled parameter enables or disables access to the mailbox by using Exchange Active Sync (EAS). Valid values are:
 
-- $true: ActiveSync access to the mailbox is enabled. This is the default value.
+- $true: ActiveSync access to the mailbox is enabled. This value is the default.
 - $false: ActiveSync access to the mailbox is disabled.
 
 ```yaml
@@ -243,7 +243,7 @@ Accept wildcard characters: False
 
 The PopEnabled parameter enables or disables access to the mailbox by using POP3 clients. Valid values are:
 
-- $true: POP3 access to the mailbox is enabled. This is the default value.
+- $true: POP3 access to the mailbox is enabled. This value is the default.
 - $false: POP3 access to the mailbox is disabled.
 
 ```yaml
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-CalendarNotification.md b/exchange/exchange-ps/ExchangePowerShell/Set-CalendarNotification.md
index 21a621c826..c20aafc1af 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-CalendarNotification.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-CalendarNotification.md
@@ -17,7 +17,7 @@ This cmdlet is available only in on-premises Exchange.
 
 The Set-CalendarNotification cmdlet allows users to set text message notification options for calendar events in their own calendar. By default, the MyTextMessaging end-user role gives access to this cmdlet, so admins can't configure text messaging notification for calendar events in user calendars.
 
-**Note**: This cmdlet has been deprecated in Exchange Online PowerShell. The text message notification service has been discontinued in Microsoft 365.
+**Note**: This cmdlet is deprecated in Exchange Online PowerShell. The text message notification service is discontinued in Microsoft 365.
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
@@ -42,7 +42,7 @@ Set-CalendarNotification [-Identity] <MailboxIdParameter>
 ## DESCRIPTION
 Users can receive text message notifications of changes to calendar events and daily agendas.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -95,7 +95,7 @@ Accept wildcard characters: False
 The CalendarUpdateNotification parameter specifies whether calendar update text message notifications are sent to the user's mobile device. Valid values are:
 
 - $true: Calendar update text message notifications are enabled.
-- $false: Calendar update text message notifications aren't enabled. This is the default value.
+- $false: Calendar update text message notifications aren't enabled. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -116,7 +116,7 @@ Accept wildcard characters: False
 The CalendarUpdateSendDuringWorkHour parameter specifies whether calendar update text notifications are sent to the user's mobile device during working hours only. Valid values are:
 
 - $true: Calendar update text message notifications are sent during working hours only.
-- $false: Calendar update text message notifications are sent anytime. This is the default value.
+- $false: Calendar update text message notifications are sent anytime. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -158,7 +158,7 @@ Accept wildcard characters: False
 The DailyAgendaNotification parameter specifies whether daily agenda text message notifications are sent to the user's mobile device. Valid values are:
 
 - $true: Daily agenda text message notifications are sent.
-- $false: Daily agenda text message notifications aren't sent. This is the default value.
+- $false: Daily agenda text message notifications aren't sent. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -237,7 +237,7 @@ Accept wildcard characters: False
 The MeetingReminderNotification parameter specifies whether meeting reminder text message notifications are sent to the user's mobile device. Valid values are:
 
 - $true: Meeting reminder text message notifications are sent.
-- $false: Meeting reminder text message notifications aren't sent. This is the default value.
+- $false: Meeting reminder text message notifications aren't sent. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -258,7 +258,7 @@ Accept wildcard characters: False
 The MeetingReminderSendDuringWorkHour parameter specifies whether meeting reminder text message notifications are sent to the user's mobile device during working hours only. Valid values are:
 
 - $true: Meeting update notifications are sent during working hours only.
-- $false: Meeting update notifications are sent anytime. This is the default value.
+- $false: Meeting update notifications are sent anytime. This value is the default.
 
 ```yaml
 Type: Boolean
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-CalendarProcessing.md b/exchange/exchange-ps/ExchangePowerShell/Set-CalendarProcessing.md
index 6897e1410a..da0a5b0cfd 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-CalendarProcessing.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-CalendarProcessing.md
@@ -13,9 +13,9 @@ title: Set-CalendarProcessing
 # Set-CalendarProcessing
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
-Use the Set-CalendarProcessing cmdlet to modify calendar processing options for resource mailboxes, which include the Calendar Attendant, resource booking assistant, and calendar configuration. Note that this cmdlet is effective only on resource mailboxes.
+Use the Set-CalendarProcessing cmdlet to modify calendar processing options for resource mailboxes, which include the Calendar Attendant, resource booking assistant, and calendar configuration. This cmdlet is effective only on resource mailboxes.
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
@@ -69,7 +69,7 @@ Set-CalendarProcessing [-Identity] <MailboxIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -192,7 +192,7 @@ Accept wildcard characters: False
 The AddAdditionalResponse parameter specifies whether additional information (the value of the AdditionalResponse parameter) is added to meeting request responses. Valid values are:
 
 - $true: Text from the AdditionalResponse parameter is added to meeting request responses.
-- $false: No additional text is added to meeting request responses (any text in the AddAdditionalResponse parameter isn't used). This is the default value.
+- $false: No additional text is added to meeting request responses (any text in the AddAdditionalResponse parameter isn't used). This value is the default.
 
 This parameter is used only on resource mailboxes where the AutomateProcessing parameter is set to AutoAccept.
 
@@ -232,7 +232,7 @@ Accept wildcard characters: False
 
 The AddNewRequestsTentatively parameter specifies whether new meeting requests are added to the calendar as tentative. Valid values are:
 
-- $true: New calendar items are added to the calendar as tentative. This is the default value.
+- $true: New calendar items are added to the calendar as tentative. This value is the default.
 - $false: Only existing calendar items are updated by the Calendar Attendant.
 
 ```yaml
@@ -253,7 +253,7 @@ Accept wildcard characters: False
 
 The AddOrganizerToSubject parameter specifies whether the meeting organizer's name is used as the subject of the meeting request. Valid values are:
 
-- $true: The meeting organizer's name replaces any existing Subject value for the meeting request. This is the default value.
+- $true: The meeting organizer's name replaces any existing Subject value for the meeting request. This value is the default.
 - $false: The original Subject value is preserved.
 
 This parameter is used only on resource mailboxes where the AutomateProcessing parameter is set to AutoAccept.
@@ -278,7 +278,7 @@ Accept wildcard characters: False
 
 The AllBookInPolicy parameter specifies whether to automatically approve in-policy requests from all users to the resource mailbox. Valid values are:
 
-- $true: In-policy requests from all users are automatically approved. This is the default value.
+- $true: In-policy requests from all users are automatically approved. This value is the default.
 - $false: In-policy requests from all users aren't automatically approved (approval by a delegate is required).
 
 ```yaml
@@ -300,11 +300,11 @@ Accept wildcard characters: False
 The AllowConflicts parameter specifies whether to allow conflicting meeting requests. Valid values are:
 
 - $true: Conflicts are allowed. A recurring meeting series is accepted regardless of whether any occurrences conflict with existing bookings. The values of the ConflictPercentageAllowed or MaximumConflictInstances parameters are ignored.
-- $false: Conflicts aren't allowed. This is the default value. Whether an entire series is declined depends on the amount of conflicts in the series:
+- $false: Conflicts aren't allowed. This value is the default. Whether an entire series is declined depends on the amount of conflicts in the series:
 
   • The series is declined if the number or percentage of conflicts is higher than the ConflictPercentageAllowed or MaximumConflictInstances parameter values.
 
-  • The series is accepted, but conflicting occurrences are declined if the number or percentage of conflicts is lower than the ConflictPercentageAllowed or MaximumConflictInstances parameter values. If the EnableResponseDetails parameter value is $true, the organizer will receive a notification email for each declined occurrence.
+  • The series is accepted, but conflicting occurrences are declined if the number or percentage of conflicts is lower than the ConflictPercentageAllowed or MaximumConflictInstances parameter values. If the EnableResponseDetails parameter value is $true, the organizer receives a notification email for each declined occurrence.
 
 ```yaml
 Type: Boolean
@@ -324,7 +324,7 @@ Accept wildcard characters: False
 
 The AllowRecurringMeetings parameter specifies whether to allow recurring meetings in meeting requests. Valid values are:
 
-- $true: Recurring meetings are allowed. This is the default value.
+- $true: Recurring meetings are allowed. This value is the default.
 - $false: Recurring meetings aren't allowed.
 
 ```yaml
@@ -346,7 +346,7 @@ Accept wildcard characters: False
 The AllRequestInPolicy parameter specifies whether to allow all users to submit in-policy requests to the resource mailbox. Valid values are:
 
 - $true: All users are allowed to submit in-policy requests to the resource mailbox. These requests require approval by a resource mailbox delegate if the AllBookInPolicy parameter is set to $false (the default value of AllBookInPolicy is $true).
-- $false: All users can't submit in-policy requests to the resource mailbox. This is the default value.
+- $false: All users can't submit in-policy requests to the resource mailbox. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -367,7 +367,7 @@ Accept wildcard characters: False
 The AllRequestOutOfPolicy parameter specifies whether to allow all users to submit out-of-policy requests to the resource mailbox. Valid values are:
 
 - $true: All users are allowed to submit out-of-policy requests to the resource mailbox. Out-of-policy requests require approval by a resource mailbox delegate.
-- $false: All users can't submit out-of-policy requests to the resource mailbox. This is the default value.
+- $false: All users can't submit out-of-policy requests to the resource mailbox. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -417,7 +417,7 @@ This parameter is available only in the cloud-based service.
 
 The BookingType parameter specifies how reservations work on the resource mailbox. Valid values are:
 
-- Standard: The resource can be reserved based on the other settings in this cmdlet. This is the default value
+- Standard: The resource can be reserved based on the other settings in this cmdlet. This value is the default
 - Reserved: The resource can't be reserved.
 
 ```yaml
@@ -530,7 +530,7 @@ Accept wildcard characters: False
 
 The DeleteAttachments parameter specifies whether to remove attachments from all incoming messages. Valid values are:
 
-- $true: Remove any attachments in incoming messages. This is the default value.
+- $true: Remove any attachments in incoming messages. This value is the default.
 - $false: Preserve any attachments in incoming messages.
 
 This parameter is used only on resource mailboxes where the AutomateProcessing parameter is set to AutoAccept.
@@ -553,7 +553,7 @@ Accept wildcard characters: False
 
 The DeleteComments parameter specifies whether to remove or keep any text in the message body of incoming meeting requests. Valid values are:
 
-- $true: Remove any text in the message body of incoming meeting requests. This is the default value.
+- $true: Remove any text in the message body of incoming meeting requests. This value is the default.
 - $false: Preserve any text in the message body of incoming meeting requests.
 
 This parameter is used only on resource mailboxes where the AutomateProcessing parameter is set to AutoAccept.
@@ -576,7 +576,7 @@ Accept wildcard characters: False
 
 The DeleteNonCalendarItems parameter specifies whether to remove or keep all non-calendar-related messages that are received by the resource mailbox. Valid values are:
 
-- $true: Non-calendar messages are deleted. This is the default value.
+- $true: Non-calendar messages are deleted. This value is the default.
 - $false: Non-calendar messages are preserved.
 
 ```yaml
@@ -597,7 +597,7 @@ Accept wildcard characters: False
 
 The DeleteSubject parameter specifies whether to remove or keep the subject of incoming meeting requests. Valid values are:
 
-- $true: Remove the Subject value of incoming meeting requests. This is the default value.
+- $true: Remove the Subject value of incoming meeting requests. This value is the default.
 - $false: Preserve The Subject value of incoming meeting requests.
 
 This parameter is used only on resource mailboxes where the AutomateProcessing parameter is set to AutoAccept.
@@ -660,7 +660,7 @@ Accept wildcard characters: False
 
 The EnableResponseDetails parameter specifies whether to include the reasons for accepting or declining a meeting in the response email message. Valid values are:
 
-- $true: The reasons for accepting or declining a meeting are included in the response message. This is the default value.
+- $true: The reasons for accepting or declining a meeting are included in the response message. This value is the default.
 - $false: The reasons for accepting or declining a meeting aren't included in the response message.
 
 ```yaml
@@ -684,7 +684,7 @@ This parameter is available only in the cloud-based service.
 The EnforceCapacity parameter specifies whether to restrict the number of attendees to the capacity of the workspace. For example, if capacity is set to 10, then only 10 people can book the workspace. Valid values are:
 
 - $true: Capacity is enforced.
-- $false: Capacity is not enforced. This is the default value.
+- $false: Capacity is not enforced. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -704,8 +704,8 @@ Accept wildcard characters: False
 
 The EnforceSchedulingHorizon parameter controls the behavior of recurring meetings that extend beyond the date specified by the BookingWindowInDays parameter. Valid values are:
 
-- $true: A recurring meeting request is automatically declined if the meetings start on or before the date specified by the BookingWindowInDays parameter, and the meetings extend beyond the specified date. This is the default value.
-- $false: A recurring meeting request is automatically accepted if the meetings start on or before the date specified by the BookingWindowInDays parameter, and the meetings extend beyond the specified date. However, the number of meetings is automatically reduced so meetings won't occur after the specified date.
+- $true: A recurring meeting request is automatically declined if the meetings start on or before the date specified by the BookingWindowInDays parameter, and the meetings extend beyond the specified date. This value is the default.
+- $false: A recurring meeting request is automatically accepted if the meetings start on or before the date specified by the BookingWindowInDays parameter, and the meetings extend beyond the specified date. However, the number of meetings is automatically reduced so meetings don't occur after the specified date.
 
 ```yaml
 Type: Boolean
@@ -725,7 +725,7 @@ Accept wildcard characters: False
 
 The ForwardRequestsToDelegates parameter specifies whether to forward incoming meeting requests to the delegates that are configured for the resource mailbox. Valid values are:
 
-- $true: Forward incoming meeting requests to the delegates. This is the default value.
+- $true: Forward incoming meeting requests to the delegates. This value is the default.
 - $false: Don't forward incoming meeting requests to the delegates.
 
 ```yaml
@@ -833,7 +833,7 @@ Accept wildcard characters: False
 
 The OrganizerInfo parameter specifies whether the resource mailbox sends organizer information when a meeting request is declined because of conflicts. Valid values are:
 
-- $true: Organizer information is sent when a meeting request is declined because of conflicts. This is the default value.
+- $true: Organizer information is sent when a meeting request is declined because of conflicts. This value is the default.
 - $false: Organizer information isn't sent when a meeting request is declined because of conflicts.
 
 ```yaml
@@ -875,7 +875,7 @@ Accept wildcard characters: False
 The ProcessExternalMeetingMessages parameter specifies whether to process meeting requests that originate outside the Exchange organization. Valid values are:
 
 - $true: Meeting requests from external senders are processed.
-- $false: Meeting requests from external senders are rejected. This is the default value.
+- $false: Meeting requests from external senders are rejected. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -898,7 +898,7 @@ This parameter is available only in the cloud-based service.
 The RemoveCanceledMeetings parameter specifies whether to automatically delete meetings that were cancelled by the organizer from the resource mailbox's calendar. Valid values are:
 
 - $true: Canceled meetings are deleted.
-- $false: Canceled meetings aren't deleted. This is the default value.
+- $false: Canceled meetings aren't deleted. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -919,7 +919,7 @@ Accept wildcard characters: False
 The RemoveForwardedMeetingNotifications parameter specifies whether forwarded meeting notifications are moved to the Deleted Items folder after they're processed by the Calendar Attendant. Valid values are:
 
 - $true: Processed forwarded meeting notifications are deleted (moved to the Deleted Items folder).
-- $false: Processed forwarded meeting notifications aren't deleted. This is the default value.
+- $false: Processed forwarded meeting notifications aren't deleted. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -939,7 +939,7 @@ Accept wildcard characters: False
 
 The RemoveOldMeetingMessages parameter specifies whether the Calendar Attendant removes old and redundant updates and responses. Valid values are:
 
-- $true: Outdated and redundant meeting messages are deleted. This is the default value.
+- $true: Outdated and redundant meeting messages are deleted. This value is the default.
 - $false: Outdated and redundant meeting messages aren't deleted.
 
 ```yaml
@@ -960,7 +960,7 @@ Accept wildcard characters: False
 
 The RemovePrivateProperty parameter specifies whether to clear the private flag for incoming meetings that were sent by the organizer in the original requests. Valid values are:
 
-- $true: The private flag for incoming meeting requests is cleared (the meeting is no longer private). This is the default value.
+- $true: The private flag for incoming meeting requests is cleared (the meeting is no longer private). This value is the default.
 - $false: The private flag for incoming meeting requests is preserved (private meetings stay private).
 
 ```yaml
@@ -1063,7 +1063,7 @@ Accept wildcard characters: False
 The ScheduleOnlyDuringWorkHours parameter specifies whether to allow meetings to be scheduled outside of the working hours that are defined for the resource mailbox. Valid values are:
 
 - $true: Meeting requests that are outside of working hours are automatically rejected.
-- $false: Meeting requests that are outside of working hours aren't automatically rejected. This is the default value.
+- $false: Meeting requests that are outside of working hours aren't automatically rejected. This value is the default.
 
 You configure the working hours of the resource mailbox by using the WorkDays, WorkingHoursStartTime, WorkingHoursEndTime and WorkingHoursTimeZone parameters on the Set-MailboxCalendarConfiguration cmdlet.
 
@@ -1085,7 +1085,7 @@ Accept wildcard characters: False
 
 The TentativePendingApproval parameter specifies whether to mark pending requests as tentative on the calendar. Valid values are:
 
-- $true: Meeting requests that are awaiting approval from a delegate appear in the calendar as tentative. This is the default value.
+- $true: Meeting requests that are awaiting approval from a delegate appear in the calendar as tentative. This value is the default.
 - $false: Meeting requests that are awaiting approval appear in the calendar as free.
 
 ```yaml
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-CaseHoldPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-CaseHoldPolicy.md
index 68741273ad..d6849d6df6 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-CaseHoldPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-CaseHoldPolicy.md
@@ -228,7 +228,7 @@ Accept wildcard characters: False
 
 The Enabled parameter specifies whether the policy is enabled. Valid values are:
 
-- $true: The policy is enabled. This is the default value.
+- $true: The policy is enabled. This value is the default.
 - $false: The policy is disabled.
 
 ```yaml
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-CaseHoldRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-CaseHoldRule.md
index c34bc26621..b608519c55 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-CaseHoldRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-CaseHoldRule.md
@@ -133,7 +133,7 @@ Accept wildcard characters: False
 The Disabled parameter specifies whether the case hold rule is enabled or disabled. Valid values are:
 
 - $true: The rule is disabled.
-- $false: The rule is enabled. This is the default value.
+- $false: The rule is enabled. This value is the default.
 
 ```yaml
 Type: Boolean
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ClassificationRuleCollection.md b/exchange/exchange-ps/ExchangePowerShell/Set-ClassificationRuleCollection.md
index 2502056704..53a24290a9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ClassificationRuleCollection.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ClassificationRuleCollection.md
@@ -13,7 +13,7 @@ title: Set-ClassificationRuleCollection
 # Set-ClassificationRuleCollection
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-ClassificationRuleCollection cmdlet to update existing classification rule collections in your organization.
 
@@ -32,7 +32,7 @@ Set-ClassificationRuleCollection [-FileData] <Byte[]>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessArray.md b/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessArray.md
index 00eda61ee3..527bdc1924 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessArray.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessArray.md
@@ -33,7 +33,7 @@ Set-ClientAccessArray [-Identity] <ClientAccessArrayIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessRule.md
index 19c664d7a8..c608194cb5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessRule.md
@@ -16,7 +16,7 @@ title: Set-ClientAccessRule
 > [!NOTE]
 > Beginning in October 2022, client access rules were deprecated for all Exchange Online organizations that weren't using them. Client access rules will be deprecated for all remaining organizations on September 1, 2025. If you choose to turn off client access rules before the deadline, the feature will be disabled in your organization. For more information, see [Update on Client Access Rules Deprecation in Exchange Online](https://techcommunity.microsoft.com/blog/exchange/update-on-client-access-rules-deprecation-in-exchange-online/4354809).
 
-This cmdlet is functional only in Exchange Server 2019 and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is functional only in Exchange Server 2019 and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-ClientAccessRule cmdlet to modify existing client access rules. Client access rules help you control access to your organization based on the properties of the connection.
 
@@ -73,7 +73,7 @@ Protocols that don't support authentication type filters:
 - REST
 - UniversalOutlook
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessServer.md b/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessServer.md
index 485c03031d..c508f745f4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessServer.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessServer.md
@@ -60,7 +60,7 @@ Set-ClientAccessServer [-Identity] <ClientAccessServerIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -293,7 +293,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 ```yaml
 Type: Unlimited
@@ -324,7 +324,7 @@ When you enter a value, qualify the value with one of the following units:
 - MB (megabytes)
 - GB (gigabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value of this parameter must be less than or equal to the value of the ReceiveProtocolLogMaxDirectorySize parameter.
 
@@ -348,6 +348,8 @@ This parameter is available only in Exchange Server 2010.
 
 The IrmLogPath parameter specifies the location of the IRM log files. The default location is %ExchangeInstallPath%Logging\\IRMLogs.
 
+If you set the value of this parameter to $null, you effectively disable IRM logging. However, if the value of the IrmLogEnabled parameter is $true, Exchange adds errors to the Application event log. The preferred way to disable IRM logging is to set the IrmLogEnabled parameter to $false.
+
 ```yaml
 Type: LocalLongFullPath
 Parameter Sets: (All)
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessService.md b/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessService.md
index 513a753cb2..054020ca76 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessService.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessService.md
@@ -46,7 +46,7 @@ Set-ClientAccessService [-Identity] <ClientAccessServerIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-Clutter.md b/exchange/exchange-ps/ExchangePowerShell/Set-Clutter.md
index 0744a0ad2e..69a1410858 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-Clutter.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-Clutter.md
@@ -29,7 +29,7 @@ Set-Clutter -Identity <MailboxIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -77,7 +77,7 @@ Accept wildcard characters: False
 
 The Enable parameter specifies whether to enable or disable Clutter for the mailbox. Valid values are:
 
-- $true: Clutter is enabled for the mailbox. This is the default value.
+- $true: Clutter is enabled for the mailbox. This value is the default.
 - $false: Clutter is disabled for the mailbox.
 
 ```yaml
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-CmdletExtensionAgent.md b/exchange/exchange-ps/ExchangePowerShell/Set-CmdletExtensionAgent.md
index 681865354f..1076192f9a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-CmdletExtensionAgent.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-CmdletExtensionAgent.md
@@ -36,7 +36,7 @@ Cmdlet extension agents are used by Exchange cmdlets in Exchange Server 2010 and
 
 The changes that you make by using the Set-CmdletExtensionAgent cmdlet are applied to every Exchange server in the organization.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceRetentionEventType.md b/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceRetentionEventType.md
index a8987cc8b3..336c84486c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceRetentionEventType.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceRetentionEventType.md
@@ -30,7 +30,7 @@ Set-ComplianceRetentionEventType -Identity <ComplianceRuleIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceSearch.md b/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceSearch.md
index 3919717169..77914d94f0 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceSearch.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceSearch.md
@@ -13,7 +13,7 @@ title: Set-ComplianceSearch
 # Set-ComplianceSearch
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-ComplianceSearch cmdlet to modify non-running compliance searches in Exchange Server 2016 or later and in the Microsoft Purview compliance portal.
 
@@ -53,7 +53,7 @@ Set-ComplianceSearch [-Identity] <ComplianceSearchIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 In on-premises Exchange, this cmdlet is available in the Mailbox Search role. By default, this role is assigned only to the Discovery Management role group.
 
@@ -208,7 +208,7 @@ Accept wildcard characters: False
 The AllowNotFoundExchangeLocationsEnabled parameter specifies whether to include mailboxes other than regular user mailboxes in the compliance search. Valid values are:
 
 - $true: The search doesn't try to validate the existence of the mailbox before proceeding. This value is required if you want to search mailboxes that don't resolve as regular mailboxes.
-- $false: The search tries to validate the existence of the mailbox before proceeding. If you specify a mailbox that isn't a regular user mailbox, the search will fail. This is the default value.
+- $false: The search tries to validate the existence of the mailbox before proceeding. If you specify a mailbox that isn't a regular user mailbox, the search will fail. This value is the default.
 
 The mailbox types that are affected by the value of this parameter include:
 
@@ -365,11 +365,11 @@ Accept wildcard characters: False
 
 This parameter is available only in the cloud-based service.
 
-The HoldNames parameter specifies that the content locations that have been placed on hold in the eDiscovery case will be searched. You use the value All for this parameter. You can use this parameter only for compliance searches that are associated with an eDiscovery case.
+The HoldNames parameter specifies the content locations placed on hold in the specified eDiscovery case are searched. You use the value All for this parameter. You can use this parameter only for compliance searches that are associated with an eDiscovery case.
 
 If the content locations in the compliance search include mailboxes, you also need to use the ExchangeLocation parameter with the value $null. Similarly, if the compliance search includes SharePoint sites, you also need to use the SharePointLocation parameter with the value $null.
 
-Also, if a content location was placed on a query-based case hold, only items that are on hold will be searched when you restart this compliance search. For example, if a user was placed on a query-based case hold that preserves items that were sent or created before a specific date, only those items would be searched by using the search criteria specified by this compliance search.
+Also, if a content location was placed on a query-based case hold, only items that are on hold are searched when you restart this compliance search. For example, if a user was placed on a query-based case hold that preserves items that were sent or created before a specific date, only those items would be searched by using the search criteria specified by this compliance search.
 
 ```yaml
 Type: String[]
@@ -409,8 +409,8 @@ This parameter is available only in the cloud-based service.
 
 The IncludeUserAppContent parameter specifies that you want to search the cloud-based storage location for users who don't have a regular Microsoft 365 user account in your organization. These types of users include users without an Exchange Online license who use Office applications, Microsoft 365 guest users, and on-premises users whose identity is synchronized with your Microsoft 365 organization. Valid values are:
 
-- $true: The cloud-based storage location for the users specified in any of the Exchange location parameters will be included in the search. If you use the value All for the ExchangeLocation parameter, the cloud-based storage location for any guest or on-premises user will be included in the search.
-- $false: The cloud-based storage location for the users specified in the ExchangeLocation parameter won't be included in the search. This is the default value.
+- $true: The cloud-based storage location for the users specified in any of the Exchange location parameters are included in the search. If you use the value All for the ExchangeLocation parameter, the cloud-based storage location for any guest or on-premises user are included in the search.
+- $false: The cloud-based storage location for the users specified in the ExchangeLocation parameter isn't included in the search. This value is the default.
 
 ```yaml
 Type: Boolean
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceSearchAction.md b/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceSearchAction.md
index a70ca0736f..7b3b7caae8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceSearchAction.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceSearchAction.md
@@ -34,7 +34,7 @@ Set-ComplianceSearchAction [-Identity] <ComplianceSearchActionIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 This cmdlet is available in the Mailbox Search role. By default, this role is assigned only to the Discovery Management role group.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceSecurityFilter.md b/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceSecurityFilter.md
index 1717b76660..40742de678 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceSecurityFilter.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceSecurityFilter.md
@@ -210,7 +210,7 @@ The Users parameter specifies the user who gets this filter applied to their sea
 
 You can't specify distribution groups with this parameter.
 
-The values you specify will overwrite any existing entries. See the Examples section to add or remove users without affecting other existing entries.
+The values you specify overwrite any existing entries. See the Examples section to add or remove users without affecting other existing entries.
 
 ```yaml
 Type: MultiValuedProperty
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-Contact.md b/exchange/exchange-ps/ExchangePowerShell/Set-Contact.md
index 29b5f373c7..cfd2ce2f56 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-Contact.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-Contact.md
@@ -13,7 +13,7 @@ title: Set-Contact
 # Set-Contact
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-Contact cmdlet to modify contact object settings. If the contact is a mail contact, you can use the Set-MailContact cmdlet to modify other Microsoft Exchange settings that aren't available by using the Set-Contact cmdlet.
 
@@ -68,7 +68,7 @@ Set-Contact [-Identity] <ContactIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -233,7 +233,7 @@ This parameter is available only in on-premises Exchange.
 
 The CreateDTMFMap parameter specifies whether to create a dual-tone multiple-frequency (DTMF) map for the recipient. This allows the recipient to be identified by using a telephone keypad in Unified Messaging (UM) environments. Valid values are:
 
-- $true: A DTMF map is created for the recipient. This is the default value.
+- $true: A DTMF map is created for the recipient. This value is the default.
 - $false: A DTMF map isn't created for the recipient.
 
 ```yaml
@@ -682,7 +682,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
 
-The SeniorityIndex parameter specifies the order in which this contact will display in a hierarchical address book. A contact with a value of 2 will display higher in an address book than a contact with a value of 1.
+The SeniorityIndex parameter specifies the order in which this contact displays in a hierarchical address book. A contact with a value of 2 displays higher in an address book than a contact with a value of 1.
 
 ```yaml
 Type: Int32
@@ -800,7 +800,7 @@ Accept wildcard characters: False
 
 This parameter is available only in on-premises Exchange.
 
-The UMCallingLineIds parameter specifies telephone numbers or extensions that can be mapped to a Unified Messaging (UM)-enabled user. You can specify more than one telephone number for each user, separated by a comma. Values for this parameter must be less than 128 characters in length and may include an optional plus sign (+) that precedes the numbers. Each UM-enabled user must have a unique UMCallingLineIds parameter value.
+The UMCallingLineIds parameter specifies telephone numbers or extensions that can be mapped to a Unified Messaging (UM)-enabled user. You can specify more than one telephone number for each user, separated by a comma. Values for this parameter must be less than 128 characters in length and might include an optional plus sign (+) that precedes the numbers. Each UM-enabled user must have a unique UMCallingLineIds parameter value.
 
 ```yaml
 Type: MultiValuedProperty
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ContentFilterConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-ContentFilterConfig.md
index 43970e90cf..e16cf78246 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ContentFilterConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ContentFilterConfig.md
@@ -44,7 +44,7 @@ Set-ContentFilterConfig [-BypassedRecipients <MultiValuedProperty>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -66,7 +66,7 @@ It enables and configures the SCL threshold functionalities that quarantine, rej
 
 It specifies `SpamQuarantineMailbox@contoso.com` as the spam quarantine mailbox.
 
-It defines two users for whom the Content Filter won't process messages.
+It defines two users for whom the Content Filter doesn't process messages.
 
 ## PARAMETERS
 
@@ -177,7 +177,7 @@ Accept wildcard characters: False
 
 The Enabled parameter enables or disables the Content Filter agent on the computer on which you're running the command. Valid values are:
 
-- $true: The Content Filter agent is enabled. This is the default value.
+- $true: The Content Filter agent is enabled. This value is the default.
 - $false: The Content Filter agent is disabled.
 
 ```yaml
@@ -198,7 +198,7 @@ Accept wildcard characters: False
 
 The ExternalMailEnabled parameter specifies whether all messages from unauthenticated connections from sources external to your Exchange organization are processed by the Content Filter agent. Valid values are:
 
-- $true: Messages from unauthenticated connections are processed by the Content Filter agent. This is the default value.
+- $true: Messages from unauthenticated connections are processed by the Content Filter agent. This value is the default.
 - $false: Messages from unauthenticated connections aren't processed by the Content Filter agent.
 
 ```yaml
@@ -220,7 +220,7 @@ Accept wildcard characters: False
 The InternalMailEnabled parameter specifies whether all messages from authenticated connections and from authoritative domains in your enterprise are processed by the Content Filter agent. Valid values are:
 
 - $true: Messages from authenticated connections are processed by the Content Filter agent.
-- $false: Messages from authenticated connections aren't processed by the Content Filter agent. This is the default value.
+- $false: Messages from authenticated connections aren't processed by the Content Filter agent. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -246,7 +246,7 @@ The OutlookEmailPostmarkValidationEnabled parameter specifies whether Outlook Em
 Valid values are:
 
 - $true: Outlook Email Postmark validation is enabled.
-- $false: Outlook Email Postmark validation is disabled. This is the default value.
+- $false: Outlook Email Postmark validation is disabled. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -303,7 +303,7 @@ Accept wildcard characters: False
 The SCLDeleteEnabled parameter specifies whether all messages that meet or exceed the value set in the SCLDeleteThreshold parameter are deleted. Valid values are:
 
 - $true: Messages that meet or exceed the value set in the SCLDeleteThreshold parameter are deleted.
-- $false: Messages aren't deleted. This is the default value.
+- $false: Messages aren't deleted. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -342,7 +342,7 @@ Accept wildcard characters: False
 The SCLQuarantineEnabled parameter specifies whether all messages that meet or exceed the value set in the SCLQuarantineThreshold parameter are sent to the spam quarantine mailbox specified in the QuarantineMailbox parameter. Valid values are:
 
 - $true: Messages that meet or exceed the value set in the SCLQuarantineThreshold parameter are sent to the spam quarantine mailbox specified in the QuarantineMailbox parameter.
-- $false: Messages aren't quarantined. This is the default value.
+- $false: Messages aren't quarantined. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -381,7 +381,7 @@ Accept wildcard characters: False
 The SCLRejectEnabled parameter specifies whether all messages that meet or exceed the value set in the SCLRejectThreshold parameter are rejected in an NDR to the sender. Valid values are:
 
 - $true: Messages that meet or exceed the value set in the SCLRejectThreshold parameter are rejected in an NDR is to the sender.
-- $false: Messages aren't rejected. This is the default value.
+- $false: Messages aren't rejected. This value is the default.
 
 ```yaml
 Type: Boolean
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-DataClassification.md b/exchange/exchange-ps/ExchangePowerShell/Set-DataClassification.md
index adc832cfbe..96da55616a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-DataClassification.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-DataClassification.md
@@ -15,7 +15,7 @@ title: Set-DataClassification
 ## SYNOPSIS
 This cmdlet is functional only in on-premises Exchange.
 
-In Exchange Online, this cmdlet has been replaced by the [Set-DlpSensitiveInformationType](https://learn.microsoft.com/powershell/module/exchangepowershell/set-dlpsensitiveinformationtype) cmdlet in Security & Compliance PowerShell.
+In Exchange Online, this cmdlet is replaced by the [Set-DlpSensitiveInformationType](https://learn.microsoft.com/powershell/module/exchangepowershell/set-dlpsensitiveinformationtype) cmdlet in Security & Compliance PowerShell.
 
 Use the Set-DataClassification cmdlet to modify data classification rules that use document fingerprints.
 
@@ -39,7 +39,7 @@ Set-DataClassification [-Identity] <DataClassificationIdParameter>
 ## DESCRIPTION
 Classification rule packages are used by data loss prevention (DLP) to detect sensitive content in messages.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-DataEncryptionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-DataEncryptionPolicy.md
index 12b4c81f90..737d608e85 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-DataEncryptionPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-DataEncryptionPolicy.md
@@ -62,7 +62,7 @@ Set-DataEncryptionPolicy [-Identity] <DataEncryptionPolicyIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -78,7 +78,7 @@ This example disabled the data encryption policy named US Mailboxes.
 Set-DataEncryptionPolicy -Identity "Europe Mailboxes" -Refresh
 ```
 
-This example updates the data encryption policy named Europe Mailboxes after one of the associated keys has been rotated in the Azure Key Vault.
+This example updates the data encryption policy named Europe Mailboxes after one of the associated keys is rotated in the Azure Key Vault.
 
 ## PARAMETERS
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-DatabaseAvailabilityGroup.md b/exchange/exchange-ps/ExchangePowerShell/Set-DatabaseAvailabilityGroup.md
index 9d95637c81..050d159a8c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-DatabaseAvailabilityGroup.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-DatabaseAvailabilityGroup.md
@@ -69,7 +69,7 @@ DAG property values are stored in both Active Directory and the cluster database
 - NetworkEncryption
 - DiscoverNetworks
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -353,7 +353,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-The AutoDagDiskReclaimerEnabled is used to enable or disable the volume formatting functions used by Autoreseed. The default value is $true (enabled). If you set this to $false, you will need to manually format the volume before the database(s) can be reseeded.
+The AutoDagDiskReclaimerEnabled is used to enable or disable the volume formatting functions used by Autoreseed. The default value is $true (enabled). If you set this to $false, you need to manually format the volume before the database(s) can be reseeded.
 
 ```yaml
 Type: Boolean
@@ -650,7 +650,7 @@ To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = h
 
 The default value is 01:00:00 (1 hour). To disable this feature, specify the value `([System.Threading.Timeout]::InfiniteTimeSpan)`.
 
-**Important**: Don't specify a value larger than 49.7 days. A larger value will crash MSExchangeRepl.exe with an ArgumentOutOfRangeException error on all DAG members.
+**Important**: Don't specify a value larger than 49.7 days. A larger value crashes MSExchangeRepl.exe with an ArgumentOutOfRangeException error on all DAG members.
 
 ```yaml
 Type: TimeSpan
@@ -758,7 +758,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-The WitnessServer parameter specifies the name of a server that will act as a witness for the DAG. The server specified can't be a member of the DAG.
+The WitnessServer parameter specifies the name of a server that acts as a witness for the DAG. The server specified can't be a member of the DAG.
 
 ```yaml
 Type: FileShareWitnessServerName
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-DatabaseAvailabilityGroupNetwork.md b/exchange/exchange-ps/ExchangePowerShell/Set-DatabaseAvailabilityGroupNetwork.md
index 12e8a3b755..26432fbd03 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-DatabaseAvailabilityGroupNetwork.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-DatabaseAvailabilityGroupNetwork.md
@@ -37,7 +37,7 @@ Set-DatabaseAvailabilityGroupNetwork [-Identity] <DatabaseAvailabilityGroupNetwo
 ## DESCRIPTION
 You can configure a variety of network properties, such as the name for the network, a description of the network, a list of one or more subnets that comprise the network and whether the network is enabled for replication (log shipping and seeding).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-DefaultTenantBriefingConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-DefaultTenantBriefingConfig.md
index 02455e250f..624d0d94d3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-DefaultTenantBriefingConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-DefaultTenantBriefingConfig.md
@@ -59,7 +59,7 @@ This example sets the default Briefing email configuration for the organization
 The IsEnabledByDefault parameter specifies the default Briefing email configuration for the organization. Valid values are:
 
 - Opt-in: By default, all users in the organization are subscribed to receive the Briefing email.
-- Opt-out: By default, no users in the organization are subscribed to receive the Briefing email. This is the default value.
+- Opt-out: By default, no users in the organization are subscribed to receive the Briefing email. This value is the default.
 
 This setting affects the following users:
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-DeliveryAgentConnector.md b/exchange/exchange-ps/ExchangePowerShell/Set-DeliveryAgentConnector.md
index 3c06a255d6..4996845f35 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-DeliveryAgentConnector.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-DeliveryAgentConnector.md
@@ -43,7 +43,7 @@ Set-DeliveryAgentConnector [-Identity] <DeliveryAgentConnectorIdParameter>
 ## DESCRIPTION
 Delivery agent connectors are used to route messages addressed to foreign systems that don't use the SMTP protocol. When a message is routed to a delivery agent connector, the associated delivery agent performs the content conversion and message delivery. Delivery agent connectors allow queue management of foreign connectors, thereby eliminating the need for storing messages on the file system in Drop and Pickup directories. For more information, see [Delivery agents and Delivery Agent connectors](https://learn.microsoft.com/exchange/delivery-agents-and-delivery-agent-connectors-exchange-2013-help).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-DetailsTemplate.md b/exchange/exchange-ps/ExchangePowerShell/Set-DetailsTemplate.md
index 248527df63..95bb18e238 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-DetailsTemplate.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-DetailsTemplate.md
@@ -31,7 +31,7 @@ Set-DetailsTemplate [-Identity] <DetailsTemplateIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-DeviceConditionalAccessPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-DeviceConditionalAccessPolicy.md
index 5e4ae5fe94..807af383b6 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-DeviceConditionalAccessPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-DeviceConditionalAccessPolicy.md
@@ -149,7 +149,7 @@ Accept wildcard characters: False
 
 The Enabled parameter specifies whether the policy is enabled. Valid values are:
 
-- $true: The policy is enabled. This is the default value.
+- $true: The policy is enabled. This value is the default.
 - $false: The policy is disabled.
 
 ```yaml
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-DeviceConditionalAccessRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-DeviceConditionalAccessRule.md
index 2bf094221a..4f2b1cd162 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-DeviceConditionalAccessRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-DeviceConditionalAccessRule.md
@@ -145,7 +145,7 @@ Accept wildcard characters: False
 The AccountName parameter specifies the account name. Valid values for this parameter are:
 
 - A text value.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 ```yaml
 Type: String
@@ -166,7 +166,7 @@ Accept wildcard characters: False
 The AccountUserName parameter specifies the account user name. Valid values for this parameter are:
 
 - A text value.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 ```yaml
 Type: String
@@ -188,7 +188,7 @@ The AllowAppStore parameter specifies whether to allow access to the app store o
 
 - $true: Access to the app store is allowed.
 - $false: Access to the app store isn't allowed.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available on the following types of devices:
 
@@ -215,7 +215,7 @@ The AllowAssistantWhileLocked parameter specifies whether to allow the use of th
 
 - $true: The voice assistant can be used while devices are locked.
 - $false: The voice assistant can't be used while devices are locked.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available only on Apple iOS 6+ devices.
 
@@ -239,7 +239,7 @@ The AllowConvenienceLogon parameter specifies whether to allow convenience logon
 
 - $true: Convenience logons are allowed.
 - $false: Convenience logons aren't allowed.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available only on Windows 8.1 RT devices.
 
@@ -263,7 +263,7 @@ The AllowDiagnosticSubmission parameter specifies whether to allow diagnostic su
 
 - $true: Diagnostic submissions are allowed.
 - $false: Diagnostic submissions aren't allowed.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available on the following types of devices:
 
@@ -291,7 +291,7 @@ The AllowiCloudBackup parameter specifies whether to allow Apple iCloud Backup f
 
 - $true: iCloud Backup is allowed.
 - $false: iCloud Backup isn't allowed.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available on the following types of devices:
 
@@ -318,7 +318,7 @@ The AllowiCloudDocSync parameter specifies whether to allow Apple iCloud Documen
 
 - $true: iCloud Documents & Data sync is allowed.
 - $false: iCloud Documents & Data sync isn't allowed.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available on the following types of devices:
 
@@ -345,7 +345,7 @@ The AllowiCloudPhotoSync parameter specifies whether to allow Apple iCloud Photo
 
 - $true: iCloud Photos sync is allowed.
 - $false: iCloud Photo sync isn't allowed.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available on the following types of devices:
 
@@ -372,7 +372,7 @@ The AllowJailbroken parameter specifies whether to allow access to your organiza
 
 - $true: Jailbroken devices are allowed.
 - $false: Jailbroken devices aren't allowed.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available on the following types of devices:
 
@@ -399,7 +399,7 @@ The AllowPassbookWhileLocked parameter specifies whether to allow the use of App
 
 - $true: Passbook is available while devices are locked.
 - $false: Passbook isn't available while devices are locked.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available only on Apple iOS 6+ devices.
 
@@ -423,7 +423,7 @@ The AllowScreenshot parameter specifies whether to allow screenshots on devices.
 
 - $true: Screenshots are allowed.
 - $false: Screenshots aren't allowed.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available on the following types of devices:
 
@@ -450,7 +450,7 @@ The AllowSimplePassword parameter specifies whether to allow simple or non-compl
 
 - $true: Simple passwords are allowed.
 - $false: Simple passwords aren't allowed.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available on the following types of devices:
 
@@ -478,7 +478,7 @@ The AllowVideoConferencing parameter specifies whether to allow video conferenci
 
 - $true: Video conferencing is allowed.
 - $false: Video conferencing isn't allowed.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available only on Apple iOS 6+ devices.
 
@@ -502,7 +502,7 @@ The AllowVoiceAssistant parameter specifies whether to allow using the voice ass
 
 - $true: The voice assistant is allowed.
 - $false: The voice assistant isn't allowed.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available only on Apple iOS 6+ devices.
 
@@ -526,7 +526,7 @@ The AllowVoiceDialing parameter specifies whether to allow voice-activated telep
 
 - $true: Voice dialing is allowed.
 - $false: Voice dialing isn't allowed.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available only on Apple iOS 6+ devices.
 
@@ -549,7 +549,7 @@ Accept wildcard characters: False
 The AntiVirusSignatureStatus parameter specifies the antivirus signature status. Valid values for this parameter are:
 
 - An integer.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available only on Windows 8.1 RT devices.
 
@@ -572,7 +572,7 @@ Accept wildcard characters: False
 The AntiVirusStatus parameter specifies antivirus status. Valid values for this parameter are:
 
 - An integer.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available only on Windows 8.1 RT devices.
 
@@ -599,7 +599,7 @@ The AppsRating parameter species the maximum or most restrictive rating of apps
 - Rating9plus
 - Rating12plus
 - Rating17plus
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available only on Apple iOS 6+ devices.
 
@@ -626,7 +626,7 @@ The AutoUpdateStatus parameter specifies the update settings for devices. Valid
 - AutomaticUpdatesRequired
 - DeviceDefault
 - NeverCheckUpdates
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available only on Windows 8.1 RT devices.
 
@@ -650,7 +650,7 @@ The BluetoothEnabled parameter specifies whether to enable or disable Bluetooth
 
 - $true: Bluetooth is enabled.
 - $false: Bluetooth is disabled.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available only on Windows Phone 8.1 devices.
 
@@ -674,7 +674,7 @@ The CameraEnabled parameter specifies whether to enable or disable cameras on de
 
 - $true: Cameras are enabled.
 - $false: Cameras are disabled.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available on the following types of devices:
 
@@ -740,7 +740,7 @@ Accept wildcard characters: False
 The EmailAddress parameter specifies the email address. Valid values are:
 
 - An email address: For example, julia@contoso.com.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 ```yaml
 Type: String
@@ -762,7 +762,7 @@ The EnableRemovableStorage parameter specifies whether removable storage can be
 
 - $true: Removable storage can be used.
 - $false: Removable storage can't be used.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available only on Windows Phone 8.1 devices.
 
@@ -785,7 +785,7 @@ Accept wildcard characters: False
 The ExchangeActiveSyncHost parameter specifies the Exchange ActiveSync host. Valid values for this parameter are:
 
 - A text value.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 ```yaml
 Type: String
@@ -806,7 +806,7 @@ Accept wildcard characters: False
 The FirewallStatus parameter specifies the acceptable firewall status values on devices. Valid values for this parameter are:
 
 - Required
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available only on Windows 8.1 RT devices.
 
@@ -830,7 +830,7 @@ The ForceAppStorePassword parameter specifies whether to require a password to u
 
 - $true: App store passwords are required.
 - $false: App store passwords aren't required.
-- $null (blank): The feature isn't allowed or blocked by the rule. This is the default value.
+- $null (blank): The feature isn't allowed or blocked by the rule. This value is the default.
 
 This setting is available only on Apple iOS 6+ devices.
 
@@ -854,7 +854,7 @@ The ForceEncryptedBackup parameter specifies whether to force encrypted backups
 
 - $true: Encrypted backups are required.
 - $false: Encrypted backups aren't required.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available on the following types of devices:
 
@@ -880,7 +880,7 @@ Accept wildcard characters: False
 The MaxPasswordAttemptsBeforeWipe parameter specifies the number of incorrect password attempts that cause devices to be automatically wiped. Valid values for this parameter are:
 
 - An integer.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available on the following types of devices:
 
@@ -933,7 +933,7 @@ Valid values for the MoviesRating parameter are:
 
 - AllowAll: All movies are allowed, regardless of their rating.
 - DontAllow: No movies are allowed, regardless of their rating.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 Australia
 
@@ -1032,7 +1032,7 @@ Accept wildcard characters: False
 The PasswordComplexity parameter specifies the password complexity. Valid values for this parameter are:
 
 - An integer.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 ```yaml
 Type: Int64
@@ -1053,7 +1053,7 @@ Accept wildcard characters: False
 The PasswordExpirationDays parameter specifies the number of days that the same password can be used on devices before users are required to change their passwords . Valid values for this parameter are:
 
 - An integer.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available on the following types of devices:
 
@@ -1081,7 +1081,7 @@ Accept wildcard characters: False
 The PasswordHistoryCount parameter specifies the minimum number of unique new passwords that are required on devices before an old password can be reused. Valid values for this parameter are:
 
 - An integer.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available on the following types of devices:
 
@@ -1109,7 +1109,7 @@ Accept wildcard characters: False
 The PasswordMinComplexChars parameter specifies the minimum number of complex characters that are required for device passwords. A complex character isn't a letter. Valid values for this parameter are:
 
 - An integer.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 ```yaml
 Type: Int32
@@ -1130,7 +1130,7 @@ Accept wildcard characters: False
 The PasswordMinimumLength parameter specifies the minimum number of characters that are required for device passwords. Valid values for this parameter are:
 
 - An integer.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available on the following types of devices:
 
@@ -1160,7 +1160,7 @@ The PasswordQuality parameter specifies the minimum password quality rating that
 Valid values for this parameter are:
 
 - An integer.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available only on Android 4+ devices.
 
@@ -1184,7 +1184,7 @@ The PasswordRequired parameter specifies whether a password is required to acces
 
 - $true: Device passwords are required.
 - $false: Device passwords aren't required.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available on the following types of devices:
 
@@ -1239,7 +1239,7 @@ The PhoneMemoryEncrypted parameter specifies whether to encrypt the memory on de
 
 - $true: Memory is encrypted.
 - $false: Memory isn't encrypted.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available on the following types of devices:
 
@@ -1266,7 +1266,7 @@ The RegionRatings parameter specifies the rating system (country/region) to use
 
 Valid values for the RegionRating parameter are:
 
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 - au: Australia
 - ca: Canada
 - de: Germany
@@ -1299,7 +1299,7 @@ The RequireEmailProfile parameter specifies whether an email profile is required
 
 - $true: An email profile is required. This value is required for selective wipe on iOS devices.
 - $false: An email profile isn't required.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -1321,7 +1321,7 @@ The SmartScreenEnabled parameter specifies whether to requireWindows SmartScreen
 
 - $true: SmartScreen is enabled.
 - $false: SmartScreen is disabled.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available only on Windows 8.1 RT devices.
 
@@ -1345,7 +1345,7 @@ The SystemSecurityTLS parameter specifies whether TLS encryption is used on devi
 
 - $true: TLS encryption is used.
 - $false: TLS encryption isn't used.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available only on Apple iOS 6+ devices.
 
@@ -1371,7 +1371,7 @@ Valid values for the TVShowsRating parameter are:
 
 - AllowAll: All television shows are allowed, regardless of their rating.
 - DontAllow: No televisions shows are allowed, regardless of their rating.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 Australia
 
@@ -1458,7 +1458,7 @@ Accept wildcard characters: False
 
 The UserAccountControlStatus parameter specifies how User Account Control messages are presented on devices. Valid values for this parameter are:
 
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 - AlwaysNotify
 - NeverNotify
 - NotifyAppChanges
@@ -1504,7 +1504,7 @@ The WLANEnabled parameter specifies whether Wi-Fi is enabled devices. Valid valu
 
 - $true: Wi-Fi is enabled.
 - $false: Wi-Fi is disabled.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available only on Microsoft Windows Phone 8.1 devices.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-DeviceConfigurationPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-DeviceConfigurationPolicy.md
index 4f8b285283..68bf9001ec 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-DeviceConfigurationPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-DeviceConfigurationPolicy.md
@@ -149,7 +149,7 @@ Accept wildcard characters: False
 
 The Enabled parameter specifies whether the policy is enabled. Valid values are:
 
-- $true: The policy is enabled. This is the default value.
+- $true: The policy is enabled. This value is the default.
 - $false: The policy is disabled.
 
 ```yaml
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-DeviceConfigurationRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-DeviceConfigurationRule.md
index 5495fd17ec..ca87acb7a7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-DeviceConfigurationRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-DeviceConfigurationRule.md
@@ -144,7 +144,7 @@ Accept wildcard characters: False
 The AccountName parameter specifies the account name. Valid values for this parameter are:
 
 - A text value.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 ```yaml
 Type: String
@@ -165,7 +165,7 @@ Accept wildcard characters: False
 The AccountUserName parameter specifies the account user name. Valid values for this parameter are:
 
 - A text value.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 ```yaml
 Type: String
@@ -187,7 +187,7 @@ The AllowAppStore parameter specifies whether to allow access to the app store o
 
 - $true: Access to the app store is allowed.
 - $false: Access to the app store isn't allowed.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available on the following types of devices:
 
@@ -214,7 +214,7 @@ The AllowAssistantWhileLocked parameter specifies whether to allow the use of th
 
 - $true: The voice assistant can be used while devices are locked.
 - $false: The voice assistant can't be used while devices are locked.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available only on Apple iOS 6+ devices.
 
@@ -238,7 +238,7 @@ The AllowConvenienceLogon parameter specifies whether to allow convenience logon
 
 - $true: Convenience logons are allowed.
 - $false: Convenience logons aren't allowed.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available only on Windows 8.1 RT devices.
 
@@ -262,7 +262,7 @@ The AllowDiagnosticSubmission parameter specifies whether to allow diagnostic su
 
 - $true: Diagnostic submissions are allowed.
 - $false: Diagnostic submissions aren't allowed.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available on the following types of devices:
 
@@ -290,7 +290,7 @@ The AllowiCloudBackup parameter specifies whether to allow Apple iCloud Backup f
 
 - $true: iCloud Backup is allowed.
 - $false: iCloud Backup isn't allowed.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available on the following types of devices:
 
@@ -317,7 +317,7 @@ The AllowiCloudDocSync parameter specifies whether to allow Apple iCloud Documen
 
 - $true: iCloud Documents & Data sync is allowed.
 - $false: iCloud Documents & Data sync isn't allowed.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available on the following types of devices:
 
@@ -344,7 +344,7 @@ The AllowiCloudPhotoSync parameter specifies whether to allow Apple iCloud Photo
 
 - $true: iCloud Photos sync is allowed.
 - $false: iCloud Photo sync isn't allowed.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available on the following types of devices:
 
@@ -371,7 +371,7 @@ The AllowPassbookWhileLocked parameter specifies whether to allow the use of App
 
 - $true: Passbook is available while devices are locked.
 - $false: Passbook isn't available while devices are locked.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available only on Apple iOS 6+ devices.
 
@@ -395,7 +395,7 @@ The AllowScreenshot parameter specifies whether to allow screenshots on devices.
 
 - $true: Screenshots are allowed.
 - $false: Screenshots aren't allowed.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available on the following types of devices:
 
@@ -422,7 +422,7 @@ The AllowSimplePassword parameter specifies whether to allow simple or non-compl
 
 - $true: Simple passwords are allowed.
 - $false: Simple passwords aren't allowed.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available on the following types of devices:
 
@@ -450,7 +450,7 @@ The AllowVideoConferencing parameter specifies whether to allow video conferenci
 
 - $true: Video conferencing is allowed.
 - $false: Video conferencing isn't allowed.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available only on Apple iOS 6+ devices.
 
@@ -474,7 +474,7 @@ The AllowVoiceAssistant parameter specifies whether to allow using the voice ass
 
 - $true: The voice assistant is allowed.
 - $false: The voice assistant isn't allowed.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available only on Apple iOS 6+ devices.
 
@@ -498,7 +498,7 @@ The AllowVoiceDialing parameter specifies whether to allow voice-activated telep
 
 - $true: Voice dialing is allowed.
 - $false: Voice dialing isn't allowed.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available only on Apple iOS 6+ devices.
 
@@ -521,7 +521,7 @@ Accept wildcard characters: False
 The AntiVirusSignatureStatus parameter specifies the antivirus signature status. Valid values for this parameter are:
 
 - An integer.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available only on Windows 8.1 RT devices.
 
@@ -544,7 +544,7 @@ Accept wildcard characters: False
 The AntiVirusStatus parameter specifies the antivirus status. Valid values for this parameter are:
 
 - An integer.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available only on Windows 8.1 RT devices.
 
@@ -571,7 +571,7 @@ The AppsRating parameter species the maximum or most restrictive rating of apps
 - Rating9plus
 - Rating12plus
 - Rating17plus
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available only on Apple iOS 6+ devices.
 
@@ -598,7 +598,7 @@ The AutoUpdateStatus parameter specifies the update settings for devices. Valid
 - AutomaticUpdatesRequired
 - DeviceDefault
 - NeverCheckUpdates
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available only on Windows 8.1 RT devices.
 
@@ -622,7 +622,7 @@ The BluetoothEnabled parameter specifies whether to enable or disable Bluetooth
 
 - $true: Bluetooth is enabled.
 - $false: Bluetooth is disabled.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available only on Windows Phone 8.1 devices.
 
@@ -646,7 +646,7 @@ The CameraEnabled parameter specifies whether to enable or disable cameras on de
 
 - $true: Cameras are enabled.
 - $false: Cameras are disabled.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available on the following types of devices:
 
@@ -712,7 +712,7 @@ Accept wildcard characters: False
 The EmailAddress parameter specifies the email address. Valid values are:
 
 - An email address: For example, julia@contoso.com.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 ```yaml
 Type: String
@@ -734,7 +734,7 @@ The EnableRemovableStorage parameter specifies whether removable storage can be
 
 - $true: Removable storage can be used.
 - $false: Removable storage can't be used.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available only on Windows Phone 8.1 devices.
 
@@ -757,7 +757,7 @@ Accept wildcard characters: False
 The ExchangeActiveSyncHost parameter specifies the Exchange ActiveSync host. Valid values for this parameter are:
 
 - A text value.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 ```yaml
 Type: String
@@ -778,7 +778,7 @@ Accept wildcard characters: False
 The FirewallStatus parameter specifies the acceptable firewall status values on devices. Valid values for this parameter are:
 
 - Required
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available only on Windows 8.1 RT devices.
 
@@ -802,7 +802,7 @@ The ForceAppStorePassword parameter specifies whether to require a password to u
 
 - $true: App store passwords are required.
 - $false: App store passwords aren't required.
-- $null (blank): The feature isn't allowed or blocked by the rule. This is the default value.
+- $null (blank): The feature isn't allowed or blocked by the rule. This value is the default.
 
 This setting is available only on Apple iOS 6+ devices.
 
@@ -826,7 +826,7 @@ The ForceEncryptedBackup parameter specifies whether to force encrypted backups
 
 - $true: Encrypted backups are required.
 - $false: Encrypted backups aren't required.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available on the following types of devices:
 
@@ -852,7 +852,7 @@ Accept wildcard characters: False
 The MaxPasswordAttemptsBeforeWipe parameter specifies the number of incorrect password attempts that cause devices to be automatically wiped. Valid values for this parameter are:
 
 - An integer.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available on the following types of devices:
 
@@ -905,7 +905,7 @@ Valid values for the MoviesRating parameter are:
 
 - AllowAll: All movies are allowed, regardless of their rating.
 - DontAllow: No movies are allowed, regardless of their rating.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 Australia
 
@@ -1004,7 +1004,7 @@ Accept wildcard characters: False
 The PasswordComplexity parameter specifies the password complexity. Valid values for this parameter are:
 
 - An integer.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 ```yaml
 Type: Int64
@@ -1025,7 +1025,7 @@ Accept wildcard characters: False
 The PasswordExpirationDays parameter specifies the number of days that the same password can be used on devices before users are required to change their passwords . Valid values for this parameter are:
 
 - An integer.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available on the following types of devices:
 
@@ -1053,7 +1053,7 @@ Accept wildcard characters: False
 The PasswordHistoryCount parameter specifies the minimum number of unique new passwords that are required on devices before an old password can be reused. Valid values for this parameter are:
 
 - An integer.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available on the following types of devices:
 
@@ -1081,7 +1081,7 @@ Accept wildcard characters: False
 The PasswordMinComplexChars parameter specifies the minimum number of complex characters that are required for device passwords. A complex character isn't a letter. Valid values for this parameter are:
 
 - An integer.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 ```yaml
 Type: Int32
@@ -1102,7 +1102,7 @@ Accept wildcard characters: False
 The PasswordMinimumLength parameter specifies the minimum number of characters that are required for device passwords. Valid values for this parameter are:
 
 - An integer.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available on the following types of devices:
 
@@ -1132,7 +1132,7 @@ The PasswordQuality parameter specifies the minimum password quality rating that
 Valid values for this parameter are:
 
 - An integer.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available only on Android 4+ devices.
 
@@ -1156,7 +1156,7 @@ The PasswordRequired parameter specifies whether a password is required to acces
 
 - $true: Device passwords are required.
 - $false: Device passwords aren't required.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available on the following types of devices:
 
@@ -1211,7 +1211,7 @@ The PhoneMemoryEncrypted parameter specifies whether to encrypt the memory on de
 
 - $true: Memory is encrypted.
 - $false: Memory isn't encrypted.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available on the following types of devices:
 
@@ -1238,7 +1238,7 @@ The RegionRatings parameter specifies the rating system (country/region) to use
 
 Valid values for the RegionRating parameter are:
 
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 - au: Australia
 - ca: Canada
 - de: Germany
@@ -1271,7 +1271,7 @@ The RequireEmailProfile parameter specifies whether an email profile is required
 
 - $true: An email profile is required. This value is required for selective wipe on iOS devices.
 - $false: An email profile isn't required.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -1293,7 +1293,7 @@ The SmartScreenEnabled parameter specifies whether to requireWindows SmartScreen
 
 - $true: SmartScreen is enabled.
 - $false: SmartScreen is disabled.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available only on Windows 8.1 RT devices.
 
@@ -1317,7 +1317,7 @@ The SystemSecurityTLS parameter specifies whether TLS encryption is used on devi
 
 - $true: TLS encryption is used.
 - $false: TLS encryption isn't used.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available only on Apple iOS 6+ devices.
 
@@ -1343,7 +1343,7 @@ Valid values for the TVShowsRating parameter are:
 
 - AllowAll: All television shows are allowed, regardless of their rating.
 - DontAllow: No televisions shows are allowed, regardless of their rating.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 Australia
 
@@ -1430,7 +1430,7 @@ Accept wildcard characters: False
 
 The UserAccountControlStatus parameter specifies how User Account Control messages are presented on devices. Valid values for this parameter are:
 
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 - AlwaysNotify
 - NeverNotify
 - NotifyAppChanges
@@ -1476,7 +1476,7 @@ The WLANEnabled parameter specifies whether Wi-Fi is enabled devices. Valid valu
 
 - $true: Wi-Fi is enabled.
 - $false: Wi-Fi is disabled.
-- $null (blank): The setting isn't configured. This is the default value.
+- $null (blank): The setting isn't configured. This value is the default.
 
 This setting is available only on Microsoft Windows Phone 8.1 devices.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-DeviceTenantPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-DeviceTenantPolicy.md
index c5e82785ad..7882d265a4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-DeviceTenantPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-DeviceTenantPolicy.md
@@ -127,7 +127,7 @@ Accept wildcard characters: False
 
 The Enabled parameter specifies whether the policy is enabled. Valid values are:
 
-- $true: The policy is enabled. This is the default value.
+- $true: The policy is enabled. This value is the default.
 - $false: The policy is disabled.
 
 ```yaml
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-DistributionGroup.md b/exchange/exchange-ps/ExchangePowerShell/Set-DistributionGroup.md
index 0eafe6e2d8..01e017c678 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-DistributionGroup.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-DistributionGroup.md
@@ -13,7 +13,7 @@ title: Set-DistributionGroup
 # Set-DistributionGroup
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-DistributionGroup cmdlet to modify the settings of existing distribution groups or mail-enabled security groups. To add or remove group members, use the Add-DistributionGroupMember, Remove-DistributionGroupMember or Update-DistributionGroupMember cmdlets.
 
@@ -99,7 +99,7 @@ Set-DistributionGroup [-Identity] <DistributionGroupIdParameter>
 ## DESCRIPTION
 Distribution groups are used to consolidate groups of recipients into a single point of contact for email messages. Distribution groups aren't security principals, and therefore can't be assigned permissions. However, you can assign permissions to mail-enabled security groups.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -334,7 +334,7 @@ This parameter is available only in the cloud-based service.
 The BccBlocked parameter specifies whether members of the group don't receive messages if the group is used in the Bcc line. Valid values are:
 
 - $true: If the group is used in the Bcc line, members of the group don't receive the message, and the sender receives a non-delivery report (also known as an NDR or bounce message). Other recipients of the message aren't blocked. If an external sender uses the group in the Bcc line, members of the group aren't blocked. For nested groups, the message is blocked only for members of the top-level group.
-- $false: There are no restrictions for using the group in the Bcc line of messages. This is the default value.
+- $false: There are no restrictions for using the group in the Bcc line of messages. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -388,7 +388,7 @@ Accept wildcard characters: False
 The ByPassNestedModerationEnabled parameter specifies how to handle message approval when a moderated group contains other moderated groups as members. Valid values are:
 
 - $true: After a moderator approves a message sent to the group, the message is automatically approved for all other moderated groups that are members of the group.
-- $false: After a moderator approves a message sent to the group, separate approval is required for each moderated group that's a member of the group. This is the default value.
+- $false: After a moderator approves a message sent to the group, separate approval is required for each moderated group that's a member of the group. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -454,7 +454,7 @@ This parameter is available only in on-premises Exchange.
 
 The CreateDTMFMap parameter specifies whether to create a dual-tone multiple-frequency (DTMF) map for the recipient. This allows the recipient to be identified by using a telephone keypad in Unified Messaging (UM) environments. Valid values are:
 
-- $true: A DTMF map is created for the recipient. This is the default value.
+- $true: A DTMF map is created for the recipient. This value is the default.
 - $false: A DTMF map isn't created for the recipient.
 
 ```yaml
@@ -846,7 +846,7 @@ This parameter is available only in on-premises Exchange.
 
 The EmailAddressPolicyEnabled parameter specifies whether to apply email address policies to this recipient. Valid values are:
 
-- $true: Email address policies are applied to this recipient. This is the default value.
+- $true: Email address policies are applied to this recipient. This value is the default.
 - $false: Email address policies aren't applied to this recipient.
 
 ```yaml
@@ -898,7 +898,7 @@ To enter multiple values that overwrite any existing entries, use the following
 
 To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`.
 
-Although this is a multivalued property, the filter `"ExtensionCustomAttribute1 -eq 'Value'"` will return a match if the property _contains_ the specified value.
+Although this is a multivalued property, the filter `"ExtensionCustomAttribute1 -eq 'Value'"` returns a match if the property _contains_ the specified value.
 
 ```yaml
 Type: MultiValuedProperty
@@ -922,7 +922,7 @@ To enter multiple values that overwrite any existing entries, use the following
 
 To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`.
 
-Although this is a multivalued property, the filter `"ExtensionCustomAttribute2 -eq 'Value'"` will return a match if the property _contains_ the specified value.
+Although this is a multivalued property, the filter `"ExtensionCustomAttribute2 -eq 'Value'"` returns a match if the property _contains_ the specified value.
 
 ```yaml
 Type: MultiValuedProperty
@@ -946,7 +946,7 @@ To enter multiple values that overwrite any existing entries, use the following
 
 To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`.
 
-Although this is a multivalued property, the filter `"ExtensionCustomAttribute3 -eq 'Value'"` will return a match if the property _contains_ the specified value.
+Although this is a multivalued property, the filter `"ExtensionCustomAttribute3 -eq 'Value'"` returns a match if the property _contains_ the specified value.
 
 ```yaml
 Type: MultiValuedProperty
@@ -970,7 +970,7 @@ To enter multiple values that overwrite any existing entries, use the following
 
 To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`.
 
-Although this is a multivalued property, the filter `"ExtensionCustomAttribute4 -eq 'Value'"` will return a match if the property _contains_ the specified value.
+Although this is a multivalued property, the filter `"ExtensionCustomAttribute4 -eq 'Value'"` returns a match if the property _contains_ the specified value.
 
 ```yaml
 Type: MultiValuedProperty
@@ -994,7 +994,7 @@ To enter multiple values that overwrite any existing entries, use the following
 
 To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`.
 
-Although this is a multivalued property, the filter `"ExtensionCustomAttribute5 -eq 'Value'"` will return a match if the property _contains_ the specified value.
+Although this is a multivalued property, the filter `"ExtensionCustomAttribute5 -eq 'Value'"` returns a match if the property _contains_ the specified value.
 
 ```yaml
 Type: MultiValuedProperty
@@ -1070,7 +1070,7 @@ Accept wildcard characters: False
 The HiddenFromAddressListsEnabled parameter specifies whether this recipient is visible in address lists. Valid values are:
 
 - $true: The recipient isn't visible in address lists.
-- $false: The recipient is visible in address lists. This is the default value.
+- $false: The recipient is visible in address lists. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -1267,7 +1267,7 @@ When you enter a value, qualify the value with one of the following units:
 - MB (megabytes)
 - GB (gigabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 A valid value is a number up to 1.999999 gigabytes (2147483647 bytes) or the value unlimited. The default value is unlimited, which indicates the maximum size is imposed elsewhere (for example, organization, server, or connector limits).
 
@@ -1300,7 +1300,7 @@ When you enter a value, qualify the value with one of the following units:
 - MB (megabytes)
 - GB (gigabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 A valid value is a number up to 1.999999 gigabytes (2147483647 bytes) or the value unlimited. The default value is unlimited, which indicates the maximum size is imposed elsewhere (for example, organization, server, or connector limits).
 
@@ -1324,8 +1324,8 @@ Accept wildcard characters: False
 
 The MemberDepartRestriction parameter specifies the restrictions that you put on requests to leave the group. Valid values are:
 
-- Open: Members can leave the group without approval from one of the group owners. This is the default value for universal distribution groups. You can't use this value on universal security groups.
-- Closed: Members can't remove themselves from the group, and requests to leave the group are rejected automatically. Group membership is controlled by the group owners. This is the default value for universal security groups.
+- Open: Members can leave the group without approval from one of the group owners. This value is the default for universal distribution groups. You can't use this value on universal security groups.
+- Closed: Members can't remove themselves from the group, and requests to leave the group are rejected automatically. Group membership is controlled by the group owners. This value is the default for universal security groups.
 
 ```yaml
 Type: MemberUpdateType
@@ -1346,7 +1346,7 @@ Accept wildcard characters: False
 The MemberJoinRestriction parameter specifies the restrictions that you put on requests to join the group. Valid values are:
 
 - Open: Users can add themselves to the group without approval from a group owner. You can't use this value on universal security groups.
-- Closed: Users can't add themselves to the group, and requests to join the group are rejected automatically. Group membership is controlled by the group owners. This is the default value on universal security groups and universal distribution groups.
+- Closed: Users can't add themselves to the group, and requests to join the group are rejected automatically. Group membership is controlled by the group owners. This value is the default on universal security groups and universal distribution groups.
 - ApprovalRequired: Users can request to join the group. The user is added to the group after the request is approved by one of the group owners. Although you can use this value on universal security groups, user requests to join the group aren't sent to the group owners, so this setting is only effective on universal distribution groups.
 
 ```yaml
@@ -1401,7 +1401,7 @@ Accept wildcard characters: False
 The ModerationEnabled parameter specifies whether moderation is enabled for this recipient. Valid value are:
 
 - $true: Moderation is enabled for this recipient. Messages sent to this recipient must be approved by a moderator before the messages are delivered.
-- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This is the default value.
+- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This value is the default.
 
 You use the ModeratedBy parameter to specify the moderators.
 
@@ -1571,7 +1571,7 @@ Accept wildcard characters: False
 The ReportToManagerEnabled parameter specifies whether delivery status notifications (also known as DSNs, non-delivery reports, NDRs, or bounce messages) are sent to the owner (first one listed if more than one) of the group (defined by the ManagedBy property). Valid values are:
 
 - $true: Delivery status notifications are sent to the owner (first one listed if more than one) of the group.
-- $false: Delivery status notifications aren't sent to the owner (first one listed if more than one) of the group. This is the default value.
+- $false: Delivery status notifications aren't sent to the owner (first one listed if more than one) of the group. This value is the default.
 
 The ReportToManagerEnabled and ReportToOriginatorEnabled parameters affect the return path for messages sent to the group. Some email servers reject messages that don't have a return path. Therefore, you should set one parameter to $false and one to $true, but not both to $false or both to $true.
 
@@ -1593,7 +1593,7 @@ Accept wildcard characters: False
 
 The ReportToOriginatorEnabled parameter specifies whether delivery status notifications (also known as DSNs, non-delivery reports, NDRs, or bounce messages) are sent to senders who send messages to this group. Valid values are:
 
-- $true: Delivery status notifications are sent to the message senders. This is the default value.
+- $true: Delivery status notifications are sent to the message senders. This value is the default.
 - $false: Delivery status notifications aren't sent to the message senders.
 
 The ReportToManagerEnabled and ReportToOriginatorEnabled parameters affect the return path for messages sent to the group. Some email servers reject messages that don't have a return path. Therefore, you should set one parameter to $false and one to $true, but not both to $false or both to $true.
@@ -1677,7 +1677,7 @@ Accept wildcard characters: False
 
 This parameter is available only in on-premises Exchange.
 
-The SamAccountName parameter (also known as the pre-Windows 2000 user account or group name) specifies an object identifier that's compatible with older versions of Microsoft Windows client and server operating systems. The value can contain letters, numbers, spaces, periods (.), and the following characters: !, #, $, %, ^, &, -, \_, {, }, and ~. The last character can't be a period. Unicode characters are allowed, but accented characters may generate collisions (for example, o and ö match).
+The SamAccountName parameter (also known as the pre-Windows 2000 user account or group name) specifies an object identifier that's compatible with older versions of Microsoft Windows client and server operating systems. The value can contain letters, numbers, spaces, periods (.), and the following characters: !, #, $, %, ^, &, -, \_, {, }, and ~. The last character can't be a period. Unicode characters are allowed, but accented characters might generate collisions (for example, o and ö match).
 
 ```yaml
 Type: String
@@ -1697,7 +1697,7 @@ Accept wildcard characters: False
 
 The SendModerationNotifications parameter specifies when moderation notification messages are sent. Valid values are:
 
-- Always: Notify all senders when their messages aren't approved. This is the default value.
+- Always: Notify all senders when their messages aren't approved. This value is the default.
 - Internal: Notify senders in the organization when their messages aren't approved.
 - Never: Don't notify anyone when a message isn't approved.
 
@@ -1722,7 +1722,7 @@ Accept wildcard characters: False
 The SendOofMessageToOriginatorEnabled parameter specifies how to handle out of office (OOF) messages for members of the group. Valid values are:
 
 - $true: When messages are sent to the group, OOF messages for any of the group members are sent to the message sender.
-- $false: When messages are sent to the group, OOF messages for any of the group members aren't sent to the message sender. This is the default value.
+- $false: When messages are sent to the group, OOF messages for any of the group members aren't sent to the message sender. This value is the default.
 
 ```yaml
 Type: Boolean
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-DkimSigningConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-DkimSigningConfig.md
index e05a1d19ae..91d0b4e1e1 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-DkimSigningConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-DkimSigningConfig.md
@@ -34,7 +34,7 @@ Set-DkimSigningConfig [-Identity] <DkimSigningConfigIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -93,7 +93,7 @@ Accept wildcard characters: False
 
 The BodyCanonicalization parameter specifies the canonicalization algorithm that's used to create and verify the message body part of the DKIM signature. This value effectively controls the sensitivity of DKIM to changes to the message body in transit. Valid values are:
 
-- Relaxed: Changes in whitespace and changes in empty lines at the end of the message body are tolerated. This is the default value.
+- Relaxed: Changes in whitespace and changes in empty lines at the end of the message body are tolerated. This value is the default.
 - Simple: Only changes in empty lines at the end of the message body are tolerated.
 
 ```yaml
@@ -135,7 +135,7 @@ Accept wildcard characters: False
 
 The Enabled parameter specifies whether the policy is enabled. Valid values are:
 
-- $true: The policy is enabled. This is the default value.
+- $true: The policy is enabled. This value is the default.
 - $false: The policy is disabled.
 
 ```yaml
@@ -156,7 +156,7 @@ Accept wildcard characters: False
 
 The HeaderCanonicalization parameter specifies the canonicalization algorithm that's used to create and verify the message header part of the DKIM signature. This value effectively controls the sensitivity of DKIM to changes to the message headers in transit. Valid values are:
 
-- Relaxed: Common modifications to the message header are tolerated (for example, header field line rewrapping, changes in unnecessary whitespace or empty lines, and changes in case for header fields). This is the default value.
+- Relaxed: Common modifications to the message header are tolerated (for example, header field line rewrapping, changes in unnecessary whitespace or empty lines, and changes in case for header fields). This value is the default.
 - Simple: No changes to the header fields are tolerated.
 
 ```yaml
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-DlpCompliancePolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-DlpCompliancePolicy.md
index 1970809d33..4abc2dd131 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-DlpCompliancePolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-DlpCompliancePolicy.md
@@ -221,7 +221,7 @@ Accept wildcard characters: False
 
 > Applicable: Security & Compliance
 
-The AddExchangeLocation parameter adds email messages to the DLP policy if they're not already included. The valid value for this parameter is All.
+The AddExchangeLocation parameter adds email messages to the DLP policy if they aren't already included. The valid value for this parameter is All.
 
 If the policy doesn't already include email messages (in the output of the Get-DlpCompliancePolicy cmdlet, the ExchangeLocation property value is blank), you can use this parameter in the following procedures:
 
@@ -247,7 +247,7 @@ Accept wildcard characters: False
 
 > Applicable: Security & Compliance
 
-The AddOneDriveLocation parameter adds OneDrive sites to the DLP policy if they're not already included. The valid value for this parameter is All.
+The AddOneDriveLocation parameter adds OneDrive sites to the DLP policy if they aren't already included. The valid value for this parameter is All.
 
 If the policy doesn't already include OneDrive sites (in the output of the Get-DlpCompliancePolicy cmdlet, the OneDriveLocation property value is blank), you can use this parameter in the following procedures:
 
@@ -874,7 +874,7 @@ Accept wildcard characters: False
 
 The Mode parameter specifies the action and notification level of the DLP policy. Valid values are:
 
-- Enable: The policy is enabled for actions and notifications. This is the default value.
+- Enable: The policy is enabled for actions and notifications. This value is the default.
 - Disable: The policy is disabled.
 - TestWithNotifications: Simulation mode where no actions are taken, but notifications **are** sent.
 - TestWithoutNotifications: Simulation mode where no actions are taken, and no notifications are sent.
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-DlpComplianceRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-DlpComplianceRule.md
index 1843b0a257..31fbb3026c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-DlpComplianceRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-DlpComplianceRule.md
@@ -502,7 +502,7 @@ Accept wildcard characters: False
 The BlockAccess parameter specifies an action for the DLP rule that blocks access to the source item when the conditions of the rule are met. Valid values are:
 
 - $true: Blocks further access to the source item that matched the rule. The owner, author, and site owner can still access the item.
-- $false: Allows access to the source item that matched the rule. This is the default value.
+- $false: Allows access to the source item that matched the rule. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -720,7 +720,7 @@ Accept wildcard characters: False
 The Disabled parameter specifies whether the DLP rule is disabled. Valid values are:
 
 - $true: The rule is disabled.
-- $false: The rule is enabled. This is the default value.
+- $false: The rule is enabled. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -914,7 +914,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 You can use this condition in DLP policies that are scoped only to Exchange.
 
@@ -1446,7 +1446,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 You can use this exception in DLP policies that are scoped only to Exchange.
 
@@ -1652,7 +1652,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, although small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, although small values might be rounded up to the nearest kilobyte.
 
 You can use this exception in DLP policies that are scoped only to Exchange.
 
@@ -2476,7 +2476,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 You can use this condition in DLP policies that are scoped only to Exchange.
 
@@ -2835,7 +2835,7 @@ Accept wildcard characters: False
 
 The NotifyPolicyTipDialogOption parameter specifies a display option for the policy tip. Valid values are:
 
-- Tip: Displays policy tip at the top of the mail. This is the default value.
+- Tip: Displays policy tip at the top of the mail. This value is the default.
 - Dialog: Displays policy tip at the top of the mail and as a popup dialog. (exchange only)
 
 ```yaml
@@ -3239,7 +3239,7 @@ Accept wildcard characters: False
 The ReportSeverityLevel parameter specifies the severity level of the incident report for content detections based on the rule. Valid values are:
 
 - None: You can't select this value if the rule has no actions configured.
-- Low: This is the default value.
+- Low: This value is the default.
 - Medium
 - High
 
@@ -3299,7 +3299,7 @@ The RuleErrorAction parameter specifies what to do if an error is encountered du
 
 - Ignore: Ignore the failure of the rule and thereby any actions in that rule and move to the next rule.
 - RetryThenBlock: Do a maximum of 5 retries of the rule with an increasing time gap of 10 min (i.e, 1st retry happens after 10 min, 2nd retry after 20 min, etc.). After the failure of the fifth retry, the message is dropped and we send a non-delivery report (also known as an NDR or bounce messages).
-- Blank (the value $null): Defer the delivery of the message and keep retrying the rule. This is the default value.
+- Blank (the value $null): Defer the delivery of the message and keep retrying the rule. This value is the default.
 
 ```yaml
 Type: Microsoft.Office.CompliancePolicy.PolicyEvaluation.PolicyRuleErrorAction
@@ -3423,11 +3423,11 @@ Accept wildcard characters: False
 
 The SenderAddressLocation parameter specifies where to look for sender addresses in conditions and exceptions that examine sender email addresses. Valid values are:
 
-- Header: Only examine senders in the message headers (for example, the From, Sender, or Reply-To fields). This is the default value.
+- Header: Only examine senders in the message headers (for example, the From, Sender, or Reply-To fields). This value is the default.
 - Envelope: Only examine senders from the message envelope (the MAIL FROM value that was used in the SMTP transmission, which is typically stored in the Return-Path field).
 - HeaderOrEnvelope: Examine senders in the message header and the message envelope.
 
-Note that message envelope searching is available only for the following conditions and exceptions:
+Message envelope searching is available only for the following conditions and exceptions:
 
 - From and ExceptIfFrom
 - FromAddressContainsWords and ExceptIfFromAddressContainsWords
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-DlpPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-DlpPolicy.md
index 5a996fc620..5229b5b8b3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-DlpPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-DlpPolicy.md
@@ -13,7 +13,7 @@ title: Set-DlpPolicy
 # Set-DlpPolicy
 
 ## SYNOPSIS
-**Note**: This cmdlet has been retired from the cloud-based service. For more information, see [this blog post](https://techcommunity.microsoft.com/t5/exchange-team-blog/exchange-online-etrs-to-stop-supporting-dlp-policies/ba-p/3886713). Use the Set-DlpCompliancePolicy and Set-DlpComplianceRule cmdlets instead.
+**Note**: This cmdlet is retired from the cloud-based service. For more information, see [this blog post](https://techcommunity.microsoft.com/t5/exchange-team-blog/exchange-online-etrs-to-stop-supporting-dlp-policies/ba-p/3886713). Use the Set-DlpCompliancePolicy and Set-DlpComplianceRule cmdlets instead.
 
 This cmdlet is functional only in on-premises Exchange.
 
@@ -36,7 +36,7 @@ Set-DlpPolicy [-Identity] <DlpPolicyIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-DlpSensitiveInformationType.md b/exchange/exchange-ps/ExchangePowerShell/Set-DlpSensitiveInformationType.md
index 73e210f497..7b6975cbdd 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-DlpSensitiveInformationType.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-DlpSensitiveInformationType.md
@@ -13,7 +13,7 @@ title: Set-DlpSensitiveInformationType
 # Set-DlpSensitiveInformationType
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-DlpSensitiveInformationType cmdlet to modify sensitive information type rules that use document fingerprints.
 
@@ -39,7 +39,7 @@ Set-DlpSensitiveInformationType [-Identity] <SensitiveInformationTypeIdParameter
 ## DESCRIPTION
 Sensitive information type rule packages are used by data loss prevention (DLP) to detect sensitive content in messages.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-DynamicDistributionGroup.md b/exchange/exchange-ps/ExchangePowerShell/Set-DynamicDistributionGroup.md
index 65cda8e11c..66ffc8fef1 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-DynamicDistributionGroup.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-DynamicDistributionGroup.md
@@ -13,7 +13,7 @@ title: Set-DynamicDistributionGroup
 # Set-DynamicDistributionGroup
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-DynamicDistributionGroup cmdlet to modify existing dynamic distribution groups.
 
@@ -123,7 +123,7 @@ To create flexible filters that use any available recipient property and that ar
 
 You can't use this cmdlet to replace a precanned filter with a custom OPATH filter, or vice-versa. You can only modify the existing filter.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -844,7 +844,7 @@ This parameter is available only in on-premises Exchange.
 
 The CreateDTMFMap parameter specifies whether to create a dual-tone multiple-frequency (DTMF) map for the recipient. This allows the recipient to be identified by using a telephone keypad in Unified Messaging (UM) environments. Valid values are:
 
-- $true: A DTMF map is created for the recipient. This is the default value.
+- $true: A DTMF map is created for the recipient. This value is the default.
 - $false: A DTMF map isn't created for the recipient.
 
 ```yaml
@@ -1234,7 +1234,7 @@ This parameter is available only in on-premises Exchange.
 
 The EmailAddressPolicyEnabled parameter specifies whether to apply email address policies to this recipient. Valid values are:
 
-- $true: Email address policies are applied to this recipient. This is the default value.
+- $true: Email address policies are applied to this recipient. This value is the default.
 - $false: Email address policies aren't applied to this recipient.
 
 ```yaml
@@ -1286,7 +1286,7 @@ To enter multiple values that overwrite any existing entries, use the following
 
 To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`.
 
-Although this is a multivalued property, the filter `"ExtensionCustomAttribute1 -eq 'Value'"` will return a match if the property _contains_ the specified value.
+Although this is a multivalued property, the filter `"ExtensionCustomAttribute1 -eq 'Value'"` returns a match if the property _contains_ the specified value.
 
 ```yaml
 Type: MultiValuedProperty
@@ -1310,7 +1310,7 @@ To enter multiple values that overwrite any existing entries, use the following
 
 To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`.
 
-Although this is a multivalued property, the filter `"ExtensionCustomAttribute2 -eq 'Value'"` will return a match if the property _contains_ the specified value.
+Although this is a multivalued property, the filter `"ExtensionCustomAttribute2 -eq 'Value'"` returns a match if the property _contains_ the specified value.
 
 ```yaml
 Type: MultiValuedProperty
@@ -1334,7 +1334,7 @@ To enter multiple values that overwrite any existing entries, use the following
 
 To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`.
 
-Although this is a multivalued property, the filter `"ExtensionCustomAttribute3 -eq 'Value'"` will return a match if the property _contains_ the specified value.
+Although this is a multivalued property, the filter `"ExtensionCustomAttribute3 -eq 'Value'"` returns a match if the property _contains_ the specified value.
 
 ```yaml
 Type: MultiValuedProperty
@@ -1358,7 +1358,7 @@ To enter multiple values that overwrite any existing entries, use the following
 
 To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`.
 
-Although this is a multivalued property, the filter `"ExtensionCustomAttribute4 -eq 'Value'"` will return a match if the property _contains_ the specified value.
+Although this is a multivalued property, the filter `"ExtensionCustomAttribute4 -eq 'Value'"` returns a match if the property _contains_ the specified value.
 
 ```yaml
 Type: MultiValuedProperty
@@ -1382,7 +1382,7 @@ To enter multiple values that overwrite any existing entries, use the following
 
 To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`.
 
-Although this is a multivalued property, the filter `"ExtensionCustomAttribute5 -eq 'Value'"` will return a match if the property _contains_ the specified value.
+Although this is a multivalued property, the filter `"ExtensionCustomAttribute5 -eq 'Value'"` returns a match if the property _contains_ the specified value.
 
 ```yaml
 Type: MultiValuedProperty
@@ -1478,7 +1478,7 @@ Accept wildcard characters: False
 The HiddenFromAddressListsEnabled parameter specifies whether this recipient is visible in address lists. Valid values are:
 
 - $true: The recipient isn't visible in address lists.
-- $false: The recipient is visible in address lists. This is the default value.
+- $false: The recipient is visible in address lists. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -1643,7 +1643,7 @@ When you enter a value, qualify the value with one of the following units:
 - MB (megabytes)
 - GB (gigabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 A valid value is a number up to 1.999999 gigabytes (2147483647 bytes) or the value unlimited. The default value is unlimited, which indicates the maximum size is imposed elsewhere (for example, organization, server, or connector limits).
 
@@ -1676,7 +1676,7 @@ When you enter a value, qualify the value with one of the following units:
 - MB (megabytes)
 - GB (gigabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 A valid value is a number up to 1.999999 gigabytes (2147483647 bytes) or the value unlimited. The default value is unlimited, which indicates the maximum size is imposed elsewhere (for example, organization, server, or connector limits).
 
@@ -1732,7 +1732,7 @@ Accept wildcard characters: False
 The ModerationEnabled parameter specifies whether moderation is enabled for this recipient. Valid value are:
 
 - $true: Moderation is enabled for this recipient. Messages sent to this recipient must be approved by a moderator before the messages are delivered.
-- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This is the default value.
+- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This value is the default.
 
 You use the ModeratedBy parameter to specify the moderators.
 
@@ -1837,7 +1837,7 @@ The RecipientContainer parameter specifies a filter that's based on the recipien
 
 If you don't use this parameter, the default value is the OU where the object was created.
 
-Note that the RecipientContainer property can't be blank. The group is always limited to looking for recipients in a specific location (the value you specify for this parameter, or the location where the group was created).
+The RecipientContainer property can't be blank. The group is always limited to looking for recipients in a specific location (the value you specify for this parameter, or the location where the group was created).
 
 ```yaml
 Type: OrganizationalUnitIdParameter
@@ -1992,7 +1992,7 @@ Accept wildcard characters: False
 The ReportToManagerEnabled parameter specifies whether delivery status notifications (also known as DSNs, non-delivery reports, NDRs, or bounce messages) are sent to the owners of the group (defined by the ManagedBy property). Valid values are:
 
 - $true: Delivery status notifications are sent to the owners of the group.
-- $false: Delivery status notifications aren't sent to the owners of the group. This is the default value.
+- $false: Delivery status notifications aren't sent to the owners of the group. This value is the default.
 
 The ReportToManagerEnabled and ReportToOriginatorEnabled parameters affect the return path for messages sent to the group. Some email servers reject messages that don't have a return path. Therefore, you should set one parameter to $false and one to $true, but not both to $false or both to $true.
 
@@ -2014,7 +2014,7 @@ Accept wildcard characters: False
 
 The ReportToOriginatorEnabled parameter specifies whether delivery status notifications (also known as DSNs, non-delivery reports, NDRs, or bounce messages) are sent to senders who send messages to this group. Valid values are:
 
-- $true: Delivery status notifications are sent to the message senders. This is the default value.
+- $true: Delivery status notifications are sent to the message senders. This value is the default.
 - $false: Delivery status notifications aren't sent to the message senders.
 
 The ReportToManagerEnabled and ReportToOriginatorEnabled parameters affect the return path for messages sent to the group. Some email servers reject messages that don't have a return path. Therefore, you should set one parameter to $false and one to $true, but not both to $false or both to $true.
@@ -2058,7 +2058,7 @@ Accept wildcard characters: False
 
 The SendModerationNotifications parameter specifies when moderation notification messages are sent. Valid values are:
 
-- Always: Notify all senders when their messages aren't approved. This is the default value.
+- Always: Notify all senders when their messages aren't approved. This value is the default.
 - Internal: Notify senders in the organization when their messages aren't approved.
 - Never: Don't notify anyone when a message isn't approved.
 
@@ -2082,7 +2082,7 @@ Accept wildcard characters: False
 
 The SendOofMessageToOriginatorEnabled parameter specifies how to handle out of office (OOF) messages for members of the group. Valid values are:
 
-- $true: When messages are sent to the group, OOF messages for any of the group members are sent to the message sender. This is the default value.
+- $true: When messages are sent to the group, OOF messages for any of the group members are sent to the message sender. This value is the default.
 - $false: When messages are sent to the group, OOF messages for any of the group members aren't sent to the message sender.
 
 ```yaml
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-EOPProtectionPolicyRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-EOPProtectionPolicyRule.md
index 09ecc30047..158f4efa73 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-EOPProtectionPolicyRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-EOPProtectionPolicyRule.md
@@ -43,7 +43,7 @@ For more information about preset security policies in PowerShell, see [Preset s
 > [!IMPORTANT]
 > Different types of recipient conditions use AND logic (the recipient must satisfy **all** specified conditions). Different types of recipient exceptions use OR logic (the recipient must satisfy **any** of the specified exceptions). For more information, see [Profiles in preset security policies](https://learn.microsoft.com/defender-office-365/preset-security-policies#profiles-in-preset-security-policies).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-EcpVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Set-EcpVirtualDirectory.md
index 5626991ff1..dfc2e8dfb3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-EcpVirtualDirectory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-EcpVirtualDirectory.md
@@ -47,7 +47,7 @@ Set-EcpVirtualDirectory [-Identity] <VirtualDirectoryIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -137,7 +137,7 @@ Accept wildcard characters: False
 
 The BasicAuthentication parameter specifies whether Basic authentication is enabled on the virtual directory. Valid values are:
 
-- $true: Basic authentication is enabled. This is the default value.
+- $true: Basic authentication is enabled. This value is the default.
 - $false: Basic authentication is disabled.
 
 This parameter can be used with the FormsAuthentication parameter or with the DigestAuthentication and WindowsAuthentication parameters.
@@ -182,7 +182,7 @@ Accept wildcard characters: False
 The DigestAuthentication parameter specifies whether Digest authentication is enabled on the virtual directory. Valid values are:
 
 - $true: Digest authentication is enabled.
-- $false: Digest authentication is disabled. This is the default value.
+- $false: Digest authentication is disabled. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -224,7 +224,7 @@ The ExtendedProtectionFlags parameter specifies custom settings for Extended Pro
 - AllowDotlessSPN: Required if you want to use Service Principal Name (SPN) values that don't contain FQDNs (for example, HTTP/ContosoMail instead of HTTP/mail.contoso.com). You specify SPNs with the ExtendedProtectionSPNList parameter. This setting makes Extended Protection for Authentication less secure because dotless certificates aren't unique, so it isn't possible to ensure that the client-to-proxy connection was established over a secure channel.
 - NoServiceNameCheck: The SPN list isn't checked to validate a channel binding token. This setting makes Extended Protection for Authentication less secure. We generally don't recommend this setting.
 - Proxy: A proxy server is responsible for terminating the SSL channel. To use this setting, you need to register an SPN by using the ExtendedProtectionSPNList parameter.
-- ProxyCoHosting: HTTP and HTTPS traffic may be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server.
+- ProxyCoHosting: HTTP and HTTPS traffic might be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server.
 
 ```yaml
 Type: MultiValuedProperty
@@ -244,7 +244,7 @@ Accept wildcard characters: False
 
 The ExtendedProtectionSPNList parameter specifies a list of valid Service Principal Names (SPNs) if you're using Extended Protection for Authentication on the virtual directory. Valid values are:
 
-- $null: This is the default value.
+- $null: This value is the default.
 - Single SPN or comma delimited list of valid SPNs: The SPN value format is `Protocol\FQDN`. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter.
 
 ```yaml
@@ -265,8 +265,8 @@ Accept wildcard characters: False
 
 The ExtendedProtectionTokenChecking parameter defines how you want to use Extended Protection for Authentication on the virtual directory. Extended Protection for Authentication isn't enabled by default. Valid values are:
 
-- None: Extended Protection for Authentication isn't be used on the virtual directory. This is the default value.
-- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication will work, but may not be as secure as connections that use Extended Protection for Authentication.
+- None: Extended Protection for Authentication isn't be used on the virtual directory. This value is the default.
+- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication work, but might not be as secure as connections that use Extended Protection for Authentication.
 - Require: Extended Protection for Authentication is used for all connections between clients and the virtual directory. If either the client or server doesn't support it, the connection will fail. If you use this value, you also need to set an SPN value for the ExtendedProtectionSPNList parameter.
 
 **Note**: If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter.
@@ -402,7 +402,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-The OwaOptionsEnabled parameter specifies that Outlook on the web Options is enabled for end users. If this parameter is set to $false, users aren't able to access Outlook on the web Options. You may want to disable access if your organization uses non-Microsoft provider tools. This parameter accepts $true or $false.
+The OwaOptionsEnabled parameter specifies that Outlook on the web Options is enabled for end users. If this parameter is set to $false, users aren't able to access Outlook on the web Options. You might want to disable access if your organization uses non-Microsoft provider tools. This parameter accepts $true or $false.
 
 ```yaml
 Type: Boolean
@@ -440,7 +440,7 @@ Accept wildcard characters: False
 
 The WindowsAuthentication parameter specifies whether Integrated Windows authentication is enabled on the virtual directory. Valid values are:
 
-- $true: Integrated Windows authentication is enabled. This is the default value.
+- $true: Integrated Windows authentication is enabled. This value is the default.
 - $false: Integrated Windows authentication is disabled.
 
 ```yaml
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-EdgeSyncServiceConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-EdgeSyncServiceConfig.md
index 3ee57372e0..46b76be6cb 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-EdgeSyncServiceConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-EdgeSyncServiceConfig.md
@@ -44,7 +44,7 @@ Set-EdgeSyncServiceConfig [-Identity] <EdgeSyncServiceConfigIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -246,7 +246,7 @@ Accept wildcard characters: False
 
 The LogLevel parameter specifies the EdgeSync logging level. Valid values are:
 
-- None (This is the default value)
+- None (default value)
 - Low
 - Medium
 - High
@@ -297,7 +297,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value of the LogMaxFileSize parameter must be less than or equal to the value of the LogMaxDirectorySize parameter. The valid input range for either parameter is from 1 through 9223372036854775807 bytes. If you enter a value of unlimited, no size limit is imposed on the EdgeSyncLog directory.
 
@@ -327,7 +327,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value of the LogMaxFileSize parameter must be less than or equal to the value of the LogMaxDirectorySize parameter. The valid input range for either parameter is from 1 through 9223372036854775807 bytes. If you enter a value of unlimited, no size limit is imposed on the EdgeSyncLog files.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-EmailAddressPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-EmailAddressPolicy.md
index 1124b51735..1c7aeb2dd0 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-EmailAddressPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-EmailAddressPolicy.md
@@ -13,7 +13,7 @@ title: Set-EmailAddressPolicy
 # Set-EmailAddressPolicy
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-EmailAddressPolicy cmdlet to modify email address policies. In Exchange Online, email address policies are available only for Microsoft 365 Groups.
 
@@ -69,7 +69,7 @@ To create flexible filters that use any available recipient property and that ar
 
 You can't use this cmdlet to replace a precanned filter with a custom OPATH filter, or vice-versa. You can only modify the existing filter.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -617,7 +617,7 @@ The DisabledEmailAddressTemplates parameter specifies the proxy email addresses
 
 Valid syntax for this parameter is `Type:AddressFormat`:
 
-- Type: A valid email address type as described in the "Address types" section in [Email address policies in Exchange Server](https://learn.microsoft.com/Exchange/email-addresses-and-address-books/email-address-policies/email-address-policies). For example, smtp or X400. Note that you can't use SMTP to specify a disabled primary SMTP email address.
+- Type: A valid email address type as described in the "Address types" section in [Email address policies in Exchange Server](https://learn.microsoft.com/Exchange/email-addresses-and-address-books/email-address-policies/email-address-policies). For example, smtp or X400. You can't use SMTP to specify a disabled primary SMTP email address.
 - AddressFormat: For SMTP email addresses, a domain or subdomain that's configured as accepted domain (authoritative or internal relay), and valid variables and ASCII text characters as described in the "Address formats" section in [Email address policies in Exchange Server](https://learn.microsoft.com/Exchange/email-addresses-and-address-books/email-address-policies/email-address-policies). For example: alias@contoso.com requires the value `%m@contoso.com`, and firstname.lastname@contoso.com requires the value `%g.%s@contoso.com`.
 
 You can specify multiple disabled email address templates separated by commas: `"[Type1:]EmailAddress1","[Type2:]EmailAddress2",..."[TypeN:]EmailAddressN"`.
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-EmailTenantSettings.md b/exchange/exchange-ps/ExchangePowerShell/Set-EmailTenantSettings.md
index bffda0e62d..efcc915182 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-EmailTenantSettings.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-EmailTenantSettings.md
@@ -32,7 +32,7 @@ Set-EmailTenantSettings [[-Identity] <EmailTenantSettingsIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-EventLogLevel.md b/exchange/exchange-ps/ExchangePowerShell/Set-EventLogLevel.md
index 9c20bb18f4..79703e4588 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-EventLogLevel.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-EventLogLevel.md
@@ -29,7 +29,7 @@ Set-EventLogLevel [-Identity] <ECIdParameter> -Level <ECIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-EventsFromEmailConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Set-EventsFromEmailConfiguration.md
index 706bc92788..f2f9e6efff 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-EventsFromEmailConfiguration.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-EventsFromEmailConfiguration.md
@@ -44,7 +44,7 @@ Set-EventsFromEmailConfiguration [-Identity] <RecipientIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -95,7 +95,7 @@ Accept wildcard characters: False
 
 The CreateEventsFromEmailAsPrivate parameter specifies whether to create the events discovered from messages as normal or private events. Valid values are:
 
-- $true: The events are crated as private events. This is the default value.
+- $true: The events are crated as private events. This value is the default.
 - $false: The events are created as normal events.
 
 ```yaml
@@ -114,7 +114,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online
 
-This parameter has been deprecated and is no longer used.
+This parameter is deprecated and no longer used.
 
 ```yaml
 Type: String
@@ -136,9 +136,9 @@ The FlightReservationProcessingLevel parameter specifies whether flight reservat
 
 - Disabled: Do not discover flight reservations from messages.
 - Email: Discover flight reservations from messages, but don't automatically add them to the user's calendar.
-- Calendar: Discover flight reservations from messages and automatically add them to the user's calendar. This is the default value.
+- Calendar: Discover flight reservations from messages and automatically add them to the user's calendar. This value is the default.
 
-Note that these values are case sensitive.
+These values are case sensitive.
 
 ```yaml
 Type: String
@@ -156,7 +156,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online
 
-This parameter has been deprecated and is no longer used.
+This parameter is deprecated and no longer used.
 
 ```yaml
 Type: String
@@ -174,7 +174,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online
 
-This parameter has been deprecated and is no longer used.
+This parameter is deprecated and no longer used.
 
 ```yaml
 Type: String
@@ -196,7 +196,7 @@ The LodgingReservationProcessingLevel parameter specifies whether lodging reserv
 
 - Disabled: Do not discover lodging reservations from messages.
 - Email: Discover lodging reservations from messages however do not automatically add these to the user's calendar.
-- Calendar: Discover lodging reservations from messages and automatically add them to the user's calendar. This is the default value.
+- Calendar: Discover lodging reservations from messages and automatically add them to the user's calendar. This value is the default.
 
 ```yaml
 Type: String
@@ -218,7 +218,7 @@ The ParcelDeliveryProcessingLevel parameter specifies whether parcel deliveries
 
 - Disabled: Do not discover parcel deliveries from messages.
 - Email: Discover parcel deliveries from messages however do not automatically add these to the user's calendar.
-- Calendar: Discover parcel deliveries from messages and automatically add them to the user's calendar. This is the default value.
+- Calendar: Discover parcel deliveries from messages and automatically add them to the user's calendar. This value is the default.
 
 ```yaml
 Type: String
@@ -240,7 +240,7 @@ The RentalCarReservationProcessingLevel parameter specifies whether rental car r
 
 - Disabled: Do not discover rental car reservations from messages.
 - Email: Discover rental car reservations from messages, but don't automatically add them to the user's calendar.
-- Calendar: Discover rental car reservations from messages and automatically add them to the user's calendar. This is the default value.
+- Calendar: Discover rental car reservations from messages and automatically add them to the user's calendar. This value is the default.
 
 ```yaml
 Type: String
@@ -276,7 +276,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online
 
-This parameter has been deprecated and is no longer used.
+This parameter is deprecated and no longer used.
 
 ```yaml
 Type: String
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeAssistanceConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeAssistanceConfig.md
index 01ea6df375..c8d43e777b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeAssistanceConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeAssistanceConfig.md
@@ -47,7 +47,7 @@ Set-ExchangeAssistanceConfig [[-Identity] <OrganizationIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -215,7 +215,7 @@ Accept wildcard characters: False
 
 The ExchangeHelpAppOnline specifies whether your organization uses the public help that's hosted by Microsoft. Valid values are:
 
-- $true: Your organization uses the help that's hosted by Microsoft. This is the default value.
+- $true: Your organization uses the help that's hosted by Microsoft. This value is the default.
 - $false: Your organization doesn't use the help that's hosted by Microsoft. You need to use the ControlPanelHelpURL, ManagementConsoleHelpURL, OWAHelpURL, and OWALightHelpURL parameters to configure the URLs where the help files are hosted.
 
 ```yaml
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeFeature.md b/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeFeature.md
index a899325723..fd7e59be88 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeFeature.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeFeature.md
@@ -35,7 +35,7 @@ Set-ExchangeFeature [-Identity] <ServerIdParameter>
 ## DESCRIPTION
 The Set-ExchangeFeature cmdlet lets you approve or block features flighted via Feature Flighting, a service introduced in the Exchange Server 2019 CU15 (2025H1) update.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeServer.md b/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeServer.md
index 1dc0ff53dd..d57443c90a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeServer.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeServer.md
@@ -47,7 +47,7 @@ Set-ExchangeServer [-Identity] <ServerIdParameter>
 ## DESCRIPTION
 The Set-ExchangeServer cmdlet sets generic Exchange attributes in Active Directory for a specified computer. You can only use this task on one server at a time. If you want to bulk manage your servers running Microsoft Exchange, add this task to a script.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -140,7 +140,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2016, Exchange Server 2019
 
-The DataCollectionEnabled parameter specifies whether the EM Service will collect and send diagnostic data to Microsoft using OCS. Valid values are:
+The DataCollectionEnabled parameter specifies whether the EM Service collects and send diagnostic data to Microsoft using OCS. Valid values are:
 
 - $true: The EM Service collects and sends diagnostic data to Microsoft using OCS.
 - $false: Data collection is disabled.
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeSettings.md b/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeSettings.md
index 84fe110fd6..82fde1fc28 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeSettings.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeSettings.md
@@ -194,7 +194,7 @@ Set-ExchangeSettings [-Identity] <ExchangeSettingsIdParameter> -Reason <String>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ExoPhishSimOverrideRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-ExoPhishSimOverrideRule.md
index 0ff54a190c..42a575f418 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ExoPhishSimOverrideRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ExoPhishSimOverrideRule.md
@@ -35,7 +35,7 @@ Set-ExoPhishSimOverrideRule [-Identity] <ComplianceRuleIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ExoSecOpsOverrideRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-ExoSecOpsOverrideRule.md
index c289ce7162..adba6e057d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ExoSecOpsOverrideRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ExoSecOpsOverrideRule.md
@@ -33,7 +33,7 @@ Set-ExoSecOpsOverrideRule [-Identity] <ComplianceRuleIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ExternalInOutlook.md b/exchange/exchange-ps/ExchangePowerShell/Set-ExternalInOutlook.md
index 618f01f80b..682e01d1e0 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ExternalInOutlook.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ExternalInOutlook.md
@@ -31,7 +31,7 @@ Set-ExternalInOutlook [[-Identity] <OrganizationIdParameter>]
 ## DESCRIPTION
 If your organization already uses mail flow rules (also known as transport rules) to add text to the subject line of messages from external senders, you should disable those rules before you enable this feature to avoid duplication.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-FederatedOrganizationIdentifier.md b/exchange/exchange-ps/ExchangePowerShell/Set-FederatedOrganizationIdentifier.md
index c18d4a1ee1..2f88fa08ee 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-FederatedOrganizationIdentifier.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-FederatedOrganizationIdentifier.md
@@ -13,7 +13,7 @@ title: Set-FederatedOrganizationIdentifier
 # Set-FederatedOrganizationIdentifier
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-FederatedOrganizationIdentifier cmdlet to configure the federated organization identifier for the Exchange organization.
 
@@ -41,7 +41,7 @@ You must configure a federated organization identifier to create an account name
 
 You can temporarily disable federation by disabling the organization identifier.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-FederationTrust.md b/exchange/exchange-ps/ExchangePowerShell/Set-FederationTrust.md
index 932434bdf2..9906bb2479 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-FederationTrust.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-FederationTrust.md
@@ -59,7 +59,7 @@ Set-FederationTrust [-Identity] <FederationTrustIdParameter>
 ## DESCRIPTION
 You can use the Set-FederationTrust cmdlet to manage the certificates used for the federation trust. You can also use the Set-FederationTrust cmdlet to refresh the metadata document from the Microsoft Federation Gateway and download its certificate.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-FocusedInbox.md b/exchange/exchange-ps/ExchangePowerShell/Set-FocusedInbox.md
index 584d428bc6..7aca252699 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-FocusedInbox.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-FocusedInbox.md
@@ -31,7 +31,7 @@ Set-FocusedInbox -Identity <MailboxIdParameter>
 ## DESCRIPTION
 Focused Inbox is a replacement for Clutter that separates the Inbox into the Focused and Other tabs in Outlook on the web and newer versions of Outlook. Important emails are on the Focused tab while the rest are on the Other tab.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -79,7 +79,7 @@ Accept wildcard characters: False
 
 The FocusedInboxOn parameter enables or disables Focused Inbox for the mailbox. Valid values are:
 
-- $true: Focused Inbox is enabled. This is the default value.
+- $true: Focused Inbox is enabled. This value is the default.
 - $false: Focused Inbox is disabled.
 
 ```yaml
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ForeignConnector.md b/exchange/exchange-ps/ExchangePowerShell/Set-ForeignConnector.md
index 0ff39d0e21..39b7e32309 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ForeignConnector.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ForeignConnector.md
@@ -43,7 +43,7 @@ Set-ForeignConnector [-Identity] <ForeignConnectorIdParameter>
 ## DESCRIPTION
 A Foreign connector uses a Drop directory in the Transport service of a Mailbox server to send messages to a local messaging server that doesn't use SMTP as its primary transport mechanism. These messaging servers are known as foreign gateway servers. Non-Microsoft fax gateway servers are examples of foreign gateway servers. The address spaces assigned to a Foreign connector can be SMTP or non-SMTP.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -84,7 +84,7 @@ Accept wildcard characters: False
 
 The AddressSpaces parameter specifies the domain names to which the Foreign connector sends messages. The complete syntax for entering each address space is: `AddressSpaceType:AddressSpace;AddressSpaceCost`.
 
-- AddressSpaceType: The address space type may be SMTP, X400, or any other text string. If you omit the address space type, an SMTP address space type is assumed.
+- AddressSpaceType: The address space type might be SMTP, X400, or any other text string. If you omit the address space type, an SMTP address space type is assumed.
 - AddressSpace: For SMTP address space types, the address space that you enter must be RFC 1035-compliant. For example, \*, \*.com, and \*.contoso.com are permitted, but \*contoso.com isn't permitted. For X.400 address space types, the address space that you enter must be RFC 1685-compliant, such as o=MySite;p=MyOrg;a=adatum;c=us. For all other values of address type, you can enter any text for the address space.
 - AddressSpaceCost : The valid input range for the cost is from 1 through 100. A lower cost indicates a better route. If you omit the address space cost, a cost of 1 is assumed. If you enter a non-SMTP address space that contains a semicolon (;), you must specify the address space cost.
 
@@ -95,7 +95,7 @@ If you specify the address space type or the address space cost, you must enclos
 - "SMTP:contoso.com"
 - contoso.com
 
-You may specify multiple address spaces by separating the address spaces with commas, for example: `contoso.com,fabrikam.com`. If you specify the address space type or the address space cost, you must enclose the address space in quotation marks ("), for example: `"contoso.com;2","fabrikam.com;3"`.
+You might specify multiple address spaces by separating the address spaces with commas, for example: `contoso.com,fabrikam.com`. If you specify the address space type or the address space cost, you must enclose the address space in quotation marks ("), for example: `"contoso.com;2","fabrikam.com;3"`.
 
 To add or remove one or more address space values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`.
 
@@ -176,7 +176,7 @@ Accept wildcard characters: False
 
 The DropDirectory parameter specifies the name of the Drop directory used by this Foreign connector. All outbound messages sent to address spaces defined by this Foreign connector are put in the specified Drop directory. The location of the Drop directory for each Foreign connector is controlled by the following two items:
 
-- RootDropDirectoryPath parameter in the Set-TransportService cmdlet: This option is used for all Foreign connectors that exist on the Mailbox server. The value of the RootDropDirectoryPath parameter may be a local path or a Universal Naming Convention (UNC) path to a remote server.
+- RootDropDirectoryPath parameter in the Set-TransportService cmdlet: This option is used for all Foreign connectors that exist on the Mailbox server. The value of the RootDropDirectoryPath parameter might be a local path or a Universal Naming Convention (UNC) path to a remote server.
 - DropDirectory parameter in the Set-ForeignConnector cmdlet: This value is set for each Foreign Connector that exists on the server.
 
 By default, the RootDropDirectoryPath parameter is blank. This indicates the value of RootDropDirectoryPath is the Exchange 2010 installation folder. The default Exchange 2010 installation folder is C:\\Program Files\\Microsoft\\Exchange Server\\. By default, the value of the DropDirectory parameter is the name of the Foreign connector.
@@ -217,7 +217,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The valid input range for this parameter is from 1 through 2147483647 bytes. If you enter a value of unlimited, no message size limit is imposed on the Drop directory. The default value is unlimited.
 
@@ -303,7 +303,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 If you enter a value of unlimited, no message size limit is imposed on this Foreign connector. The default value is unlimited. The valid input range for this parameter is from 0 through 2147483647 kilobytes. If you set the value of the MaxMessageSize parameter to 0, you effectively disable the Foreign connector. However, if you set the value of the MaxMessageSize parameter to 0 when the value of the Enabled attribute is $true, you generate event log errors. The preferred method to disable the Foreign connector is to use the Enabled parameter.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-FrontendTransportService.md b/exchange/exchange-ps/ExchangePowerShell/Set-FrontendTransportService.md
index ae846c4f1f..d9a3a5221e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-FrontendTransportService.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-FrontendTransportService.md
@@ -72,7 +72,7 @@ Set-FrontendTransportService [-Identity] <FrontendTransportServerIdParameter>
 ## DESCRIPTION
 The Front End Transport service runs on all Mailbox servers and acts as a stateless proxy for all inbound and outbound external SMTP traffic for the Exchange organization. The Front End Transport service only communicates with the Transport service on a Mailbox server, and doesn't queue any messages locally.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -164,7 +164,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value of the AgentLogMaxFileSize parameter must be less than or equal to the value of the AgentLogMaxDirectorySize parameter. If you enter a value of unlimited, no size limit is imposed on the agent log directory.
 
@@ -194,7 +194,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value of the AgentLogMaxFileSize parameter must be less than or equal to the value of the AgentLogMaxDirectorySize parameter. If you enter a value of unlimited, no size limit is imposed on the agent log files.
 
@@ -323,7 +323,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value of the ConnectivityLogMaxFileSize parameter must be less than or equal to the value of the ConnectivityLogMaxDirectorySize parameter. The valid input range for either parameter is from 1 through 9223372036854775807 bytes. If you enter a value of unlimited, no size limit is imposed on the connectivity log directory.
 
@@ -353,7 +353,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value of the ConnectivityLogMaxFileSize parameter must be less than or equal to the value of the ConnectivityLogMaxDirectorySize parameter. The valid input range for either parameter is from 1 through 9223372036854775807 bytes. If you enter a value of unlimited, no size limit is imposed on the connectivity log files.
 
@@ -441,7 +441,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value of the DnsLogMaxFileSize parameter must be less than or equal to the value of the DnsLogMaxDirectorySize parameter. If you enter a value of unlimited, no size limit is imposed on the DNS log directory.
 
@@ -471,7 +471,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value of the DnsLogMaxFileSize parameter must be less than or equal to the value of the DnsLogMaxDirectorySize parameter. If you enter a value of unlimited, no size limit is imposed on the DNS log files.
 
@@ -545,7 +545,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-The ExternalDNSAdapterGuid parameter specifies the network adapter that has the DNS settings used for DNS lookups of destinations that exist outside the Exchange organization. The concept of an external network adapter and an internal network adapter is only applicable in a multi-homed Exchange server environment. When no particular network adapter is specified as the network adapter for external DNS lookups, the value of the ExternalDNSAdapterGuid parameter is 00000000-0000-0000-0000-000000000000, and external DNS lookups are performed by using the DNS settings of any available network adapter. You may enter the GUID of a specific network adapter to use for external DNS lookups. The default value of the ExternalDNSAdapterGuid parameter is 00000000-0000-0000-0000-000000000000.
+The ExternalDNSAdapterGuid parameter specifies the network adapter that has the DNS settings used for DNS lookups of destinations that exist outside the Exchange organization. The concept of an external network adapter and an internal network adapter is only applicable in a multi-homed Exchange server environment. When no particular network adapter is specified as the network adapter for external DNS lookups, the value of the ExternalDNSAdapterGuid parameter is 00000000-0000-0000-0000-000000000000, and external DNS lookups are performed by using the DNS settings of any available network adapter. You might enter the GUID of a specific network adapter to use for external DNS lookups. The default value of the ExternalDNSAdapterGuid parameter is 00000000-0000-0000-0000-000000000000.
 
 If the value of the ExternalDNSAdapterEnabled parameter is set to $false, the value of the ExternalDNSAdapterGuid parameter is ignored, and the list of DNS servers from the ExternalDNSServers parameter is used.
 
@@ -639,7 +639,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-The InternalDNSAdapterGuid parameter specifies the network adapter that has the DNS settings used for DNS lookups of servers that exist inside the Exchange organization. The concept of an internal network adapter and an external network adapter is only applicable in a multi-homed Exchange server environment. When no particular network adapter is specified as the network adapter for external DNS lookups, the value of the InternalDNSAdapterGuid parameter is 00000000-0000-0000-0000-000000000000, and internal DNS lookups are performed by using the DNS settings of any available network adapter. You may enter the GUID of a specific network adapter to use for internal DNS lookups. The default value of the InternalDNSAdapterGuid parameter is 00000000-0000-0000-0000-000000000000.
+The InternalDNSAdapterGuid parameter specifies the network adapter that has the DNS settings used for DNS lookups of servers that exist inside the Exchange organization. The concept of an internal network adapter and an external network adapter is only applicable in a multi-homed Exchange server environment. When no particular network adapter is specified as the network adapter for external DNS lookups, the value of the InternalDNSAdapterGuid parameter is 00000000-0000-0000-0000-000000000000, and internal DNS lookups are performed by using the DNS settings of any available network adapter. You might enter the GUID of a specific network adapter to use for internal DNS lookups. The default value of the InternalDNSAdapterGuid parameter is 00000000-0000-0000-0000-000000000000.
 
 If the value of the InternalDNSAdapterEnabled parameter is set to $false, the value of the InternalDNSAdapterGuid parameter is ignored, and the list of DNS servers from the InternalDNSServers parameter is used.
 
@@ -702,7 +702,7 @@ Accept wildcard characters: False
 The IntraOrgConnectorProtocolLoggingLevel parameter enables or disables SMTP protocol logging on the implicit and invisible intra-organization Send connector In the Front End Transport service. Valid values are:
 
 - None: Protocol logging is disabled for the intra-organization Send connector in the Front End Transport service.
-- Verbose: Protocol logging is enabled for the intra-organization Send connector in the Front End Transport service. This is the default value. The location of the log files is controlled by the SendProtocolLogPath parameter.
+- Verbose: Protocol logging is enabled for the intra-organization Send connector in the Front End Transport service. This value is the default. The location of the log files is controlled by the SendProtocolLogPath parameter.
 
 ```yaml
 Type: ProtocolLoggingLevel
@@ -774,7 +774,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value of this parameter must be greater than or equal to the value of the ReceiveProtocolLogMaxFileSize parameter.
 
@@ -808,7 +808,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value of this parameter must be less than or equal to the value of the ReceiveProtocolLogMaxDirectorySize parameter.
 
@@ -882,7 +882,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The valid input range for this parameter is from 1 through 9223372036854775807 bytes. If you enter a value of unlimited, no size limit is imposed on the routing table log directory.
 
@@ -956,7 +956,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value of this parameter must be greater than or equal to the value of the SendProtocolLogMaxDirectorySize parameter.
 
@@ -990,7 +990,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value of this parameter must be less than or equal to the value of the SendProtocolLogMaxDirectorySize parameter.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-GlobalAddressList.md b/exchange/exchange-ps/ExchangePowerShell/Set-GlobalAddressList.md
index 81ea55b283..1b6156bcc7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-GlobalAddressList.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-GlobalAddressList.md
@@ -13,7 +13,7 @@ title: Set-GlobalAddressList
 # Set-GlobalAddressList
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-GlobalAddressList cmdlet to modify an existing global address list (GAL).
 
@@ -65,7 +65,7 @@ To create flexible filters that use any available recipient property and that ar
 
 You can't use this cmdlet to replace a precanned filter with a custom OPATH filter, or vice-versa. You can only modify the existing filter.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-Group.md b/exchange/exchange-ps/ExchangePowerShell/Set-Group.md
index f585acbe6c..0d12511a23 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-Group.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-Group.md
@@ -13,7 +13,7 @@ title: Set-Group
 # Set-Group
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-Group cmdlet to modify group object settings. If the group is a mail-enabled security group or a distribution group, you can use the Set-DistributionGroup cmdlet to modify other Microsoft Exchange settings that aren't available by using the Set-Group cmdlet.
 
@@ -45,7 +45,7 @@ Set-Group [-Identity] <GroupIdParameter>
 ## DESCRIPTION
 You can't use the Set-Group cmdlet to modify dynamic distribution groups. To modify dynamic distribution groups, use the Set-DynamicDistributionGroup cmdlet.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -65,7 +65,7 @@ Add a Notes parameter value of verified.
 Set-Group -Identity "Human Resources" -IsHierarchicalGroup $true -SeniorityIndex 1
 ```
 
-This example specifies that the group Human Resources is a hierarchical group and will display last within its hierarchy because its index number is 1.
+This example specifies that the group Human Resources is a hierarchical group and displays last within its hierarchy because its index number is 1.
 
 ## PARAMETERS
 
@@ -344,7 +344,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
 
-The SeniorityIndex parameter specifies the order in which this group will display in a hierarchical address book. A group with a value of 2 will display higher in an address book than a group with a value of 1.
+The SeniorityIndex parameter specifies the order in which this group displays in a hierarchical address book. A group with a value of 2 displays higher in an address book than a group with a value of 1.
 
 ```yaml
 Type: Int32
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-HoldCompliancePolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-HoldCompliancePolicy.md
index 33d71e298c..275525196e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-HoldCompliancePolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-HoldCompliancePolicy.md
@@ -17,7 +17,7 @@ This cmdlet is available only in Security & Compliance PowerShell. For more info
 
 Use the Set-HoldCompliancePolicy cmdlet to modify existing preservation policies in the Microsoft Purview compliance portal.
 
-**Note**: The Set-HoldCompliancePolicy cmdlet has been replaced by the Set-RetentionCompliancePolicy cmdlet. If you have scripts that use Set-HoldCompliancePolicy, update them to use Set-RetentionCompliancePolicy.
+**Note**: The Set-HoldCompliancePolicy cmdlet is replaced by the Set-RetentionCompliancePolicy cmdlet. If you have scripts that use Set-HoldCompliancePolicy, update them to use Set-RetentionCompliancePolicy.
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
@@ -229,7 +229,7 @@ Accept wildcard characters: False
 
 The Enabled parameter specifies whether the policy is enabled. Valid values are:
 
-- $true: The policy is enabled. This is the default value.
+- $true: The policy is enabled. This value is the default.
 - $false: The policy is disabled.
 
 ```yaml
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-HoldComplianceRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-HoldComplianceRule.md
index fd20b54fec..bebc71dc17 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-HoldComplianceRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-HoldComplianceRule.md
@@ -17,7 +17,7 @@ This cmdlet is available only in Security & Compliance PowerShell. For more info
 
 Use the Set-HoldComplianceRule cmdlet to modify existing preservation rules in the Microsoft Purview compliance portal.
 
-**Note**: The Set-HoldComplianceRule cmdlet has been replaced by the Set-RetentionComplianceRule cmdlet. If you have scripts that use Set-HoldComplianceRule, update them to use Set-RetentionComplianceRule.
+**Note**: The Set-HoldComplianceRule cmdlet is replaced by the Set-RetentionComplianceRule cmdlet. If you have scripts that use Set-HoldComplianceRule, update them to use Set-RetentionComplianceRule.
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
@@ -221,7 +221,7 @@ The HoldDurationDisplayHint parameter specifies the units that are used to displ
 - Months
 - Years
 
-For example, if this parameter is set to the value Years, and the HoldContent parameter is set to the value 365, the Microsoft Purview compliance portal will display 1 year as the content hold duration.
+For example, if this parameter is set to the value Years, and the RetentionDuration parameter is set to the value 365, the Microsoft Purview compliance portal displays 1 year as the content hold duration.
 
 ```yaml
 Type: HoldDurationHint
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-HostedConnectionFilterPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-HostedConnectionFilterPolicy.md
index 90a43832ac..015064fe09 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-HostedConnectionFilterPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-HostedConnectionFilterPolicy.md
@@ -35,7 +35,7 @@ Set-HostedConnectionFilterPolicy [-Identity] <HostedConnectionFilterPolicyIdPara
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -161,10 +161,9 @@ Accept wildcard characters: False
 ```
 
 ### -IPAllowList
-
 > Applicable: Exchange Online, Exchange Online Protection
 
-The IPAllowList parameter specifies IP addresses from which messages are always allowed. Messages from the IP addresses you specify won't be identified as spam, despite any other spam characteristics of the messages. Valid values are:
+The IPAllowList parameter specifies IP addresses from which messages are always allowed. Messages from the IP addresses you specify aren't identified as spam, despite any other spam characteristics of the messages. Valid values are:
 
 - Single IP address: For example, 192.168.1.1.
 - IP address range: You can use an IP address range, for example, 192.168.0.1-192.168.0.254. The maximum number of addresses in the range is 256.
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-HostedContentFilterPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-HostedContentFilterPolicy.md
index ba1f227f67..65a16298ad 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-HostedContentFilterPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-HostedContentFilterPolicy.md
@@ -84,7 +84,7 @@ Set-HostedContentFilterPolicy [-Identity] <HostedContentFilterPolicyIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 For more information about the limits for allowed and blocked senders, see [Exchange Online Protection Limits](https://learn.microsoft.com/office365/servicedescriptions/exchange-online-protection-service-description/exchange-online-protection-limits).
 
@@ -141,7 +141,7 @@ For example, if you enter the value `This-is-my-custom-header`, the X-header tha
 
 If you enter a value that contains spaces or colons (:), the value is ignored, and the default X-header is added to the message (`X-This-Is-Spam: This message appears to be spam.`).
 
-Note that this setting is independent of the AddXHeader value of the TestModeAction parameter.
+This setting is independent of the AddXHeader value of the TestModeAction parameter.
 
 ```yaml
 Type: String
@@ -306,7 +306,7 @@ The BulkSpamAction parameter specifies the action to take on messages that are m
 - AddXHeader: Add the AddXHeaderValue parameter value to the message header and deliver the message.
 - Delete: Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message.
 - ModifySubject: Add the ModifySubject parameter value to the beginning of the subject line, deliver the message, and move the message to the Junk Email folder (same caveats as MoveToJmf).
-- MoveToJmf: This is the default value. Deliver the message to the Junk Email folder in the recipient's mailbox. Hybrid environments need mail flow rules in the on-premises Exchange organization. For instructions, see [Configure standalone EOP to deliver spam to the Junk Email folder in hybrid environments](https://learn.microsoft.com/exchange/standalone-eop/configure-eop-spam-protection-hybrid).
+- MoveToJmf: This value is the default. Deliver the message to the Junk Email folder in the recipient's mailbox. Hybrid environments need mail flow rules in the on-premises Exchange organization. For instructions, see [Configure standalone EOP to deliver spam to the Junk Email folder in hybrid environments](https://learn.microsoft.com/exchange/standalone-eop/configure-eop-spam-protection-hybrid).
 - NoAction
 - Quarantine: Deliver the message to quarantine. By default, messages that are quarantined as bulk email are available to the intended recipients and admins. Or, you can use the BulkQuarantineTag parameter to specify what end-users are allowed to do on quarantined messages.
 - Redirect: Redirect the message to the recipients specified by the RedirectToRecipients parameter.
@@ -327,7 +327,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online, Exchange Online Protection
 
-The BulkThreshold parameter specifies the BCL on messages that triggers the action specified by the BulkSpamAction parameter (greater than or equal to the specified BCL value). A valid value is an integer from 1 to 9. The default value is 7, which means a BCL of 7, 8, or 9 on messages will trigger the action that's specified by the BulkSpamAction parameter.
+The BulkThreshold parameter specifies the BCL on messages that triggers the action specified by the BulkSpamAction parameter (greater than or equal to the specified BCL value). A valid value is an integer from 1 to 9. The default value is 7, which means a BCL of 7, 8, or 9 on messages triggers the action specified by the BulkSpamAction parameter.
 
 A higher BCL indicates the message is more likely to generate complaints (and is therefore more likely to be spam). For more information, see [Bulk complaint level (BCL) in EOP](https://learn.microsoft.com/defender-office-365/anti-spam-bulk-complaint-level-bcl-about).
 
@@ -368,7 +368,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online, Exchange Online Protection
 
-This parameter has been deprecated and is no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters.
+This parameter is deprecated and no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters.
 
 ```yaml
 Type: Boolean
@@ -386,7 +386,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online, Exchange Online Protection
 
-This parameter has been deprecated and is no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters.
+This parameter is deprecated and no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters.
 
 ```yaml
 Type: Boolean
@@ -407,7 +407,7 @@ Accept wildcard characters: False
 The EnableLanguageBlockList parameter enables or disables marking messages that were written in specific languages as spam. Valid values are:
 
 - $true: Mark messages hat were written in the languages specified by the LanguageBlockList parameter as spam.
-- $false: Don't mark messages as spam solely based on their languages. This is the default value.
+- $false: Don't mark messages as spam solely based on their languages. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -428,7 +428,7 @@ Accept wildcard characters: False
 The EnableRegionBlockList parameter enables or disables marking messages that are sent from specific countries or regions as spam. Valid values are:
 
 - $true: Mark messages from senders in the RegionBlockList parameter as spam.
-- $false: Don't mark messages as spam solely based on the source country or region. This is the default value.
+- $false: Don't mark messages as spam solely based on the source country or region. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -446,7 +446,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online, Exchange Online Protection
 
-This parameter has been deprecated and is no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters.
+This parameter is deprecated and no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters.
 
 ```yaml
 Type: SmtpAddress
@@ -464,7 +464,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online, Exchange Online Protection
 
-This parameter has been deprecated and is no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters.
+This parameter is deprecated and no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters.
 
 ```yaml
 Type: String
@@ -482,7 +482,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online, Exchange Online Protection
 
-This parameter has been deprecated and is no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters.
+This parameter is deprecated and no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters.
 
 ```yaml
 Type: String
@@ -500,7 +500,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online, Exchange Online Protection
 
-This parameter has been deprecated and is no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters.
+This parameter is deprecated and no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters.
 ```yaml
 Type: Int32
 Parameter Sets: (All)
@@ -517,7 +517,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online, Exchange Online Protection
 
-This parameter has been deprecated and is no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters.
+This parameter is deprecated and no longer used. End-user quarantine notifications are controlled by quarantine policies as specified by the \*QuarantineTag parameters.
 
 ```yaml
 Type: EsnLanguage
@@ -657,8 +657,8 @@ Accept wildcard characters: False
 
 The IncreaseScoreWithBizOrInfoUrls parameter increases the spam score of messages that contain links to .biz or .info domains. Valid values are:
 
-- Off: The setting is disabled. This is the default value, and we recommend that you don't change it.
-- On: The setting is enabled. Messages that contain links to .biz or .info domains are given a higher spam score and therefore have a higher chance of getting marked as spam with SCL 5 or 6, and the X-header `X-CustomSpam: URL to .biz or .info websites` is added to the message. Not all messages that match this setting will be marked as spam.
+- Off: The setting is disabled. This value is the default, and we recommend that you don't change it.
+- On: The setting is enabled. Messages that contain links to .biz or .info domains are given a higher spam score and therefore have a higher chance of getting marked as spam with SCL 5 or 6, and the X-header `X-CustomSpam: URL to .biz or .info websites` is added to the message. Not all messages that match this setting are marked as spam.
 - Test: The action specified by the TestModeAction parameter is taken on the message.
 
 ```yaml
@@ -679,8 +679,8 @@ Accept wildcard characters: False
 
 The IncreaseScoreWithImageLinks parameter increases the spam score of messages that contain image links to remote websites. Valid values are:
 
-- Off: The setting is disabled. This is the default value, and we recommend that you don't change it.
-- On: The setting is enabled. Messages that contain image links to remote websites are given a higher spam score and therefore have a higher chance of getting marked as spam with SCL 5 or 6, and the X-header `X-CustomSpam: Image links to remote sites` is added to the message. Not all messages that match this setting will be marked as spam.
+- Off: The setting is disabled. This value is the default, and we recommend that you don't change it.
+- On: The setting is enabled. Messages that contain image links to remote websites are given a higher spam score and therefore have a higher chance of getting marked as spam with SCL 5 or 6, and the X-header `X-CustomSpam: Image links to remote sites` is added to the message. Not all messages that match this setting aree marked as spam.
 - Test: The action specified by the TestModeAction parameter is taken on the message.
 
 ```yaml
@@ -701,7 +701,7 @@ Accept wildcard characters: False
 
 The IncreaseScoreWithNumericIps parameter increases the spam score of messages that contain links to IP addresses. Valid values are:
 
-- Off: The setting is disabled. This is the default value, and we recommend that you don't change it.
+- Off: The setting is disabled. This value is the default, and we recommend that you don't change it.
 - On: The setting is enabled. Messages that contain links to IP addresses are given the SCL 5 or 6 (spam), and the X-header `X-CustomSpam: Numeric IP in URL` is added to the message.
 - Test: The action specified by the TestModeAction parameter is taken on the message.
 
@@ -723,7 +723,7 @@ Accept wildcard characters: False
 
 The IncreaseScoreWithRedirectToOtherPort parameter increases the spam score of messages that contain links that redirect to TCP ports other than 80 (HTTP), 8080 (alternate HTTP), or 443 (HTTPS). Valid values are:
 
-- Off: The setting is disabled. This is the default value, and we recommend that you don't change it.
+- Off: The setting is disabled. This value is the default, and we recommend that you don't change it.
 - On: The setting is enabled. Messages that contain links that redirect to other TCP ports are given the SCL 5 or 6 (spam), and the X-header `X-CustomSpam: URL redirect to other port` is added to the message.
 - Test: The action specified by the TestModeAction parameter is taken on the message.
 
@@ -745,7 +745,7 @@ Accept wildcard characters: False
 
 The InlineSafetyTipsEnabled parameter specifies whether to enable or disable safety tips that are shown to recipients in messages. Valid values are:
 
-- $true: Safety tips are enabled. This is the default value.
+- $true: Safety tips are enabled. This value is the default.
 - $false: Safety tips are disabled.
 
 ```yaml
@@ -766,7 +766,7 @@ Accept wildcard characters: False
 
 The IntraOrgFilterState parameter specifies whether to enable anti-spam filtering for messages sent between internal users (users in the same organization). The action that's configured in the policy for the specified spam filter verdicts is taken on messages sent between internal users. Valid values are:
 
-- Default: This is the default value. Currently, HighConfidencePhish.
+- Default: This value is the default. Currently, HighConfidencePhish.
 - HighConfidencePhish
 - Phish: Includes phishing and high confidence phishing.
 - HighConfidenceSpam: Includes high confidence spam, phishing, and high confidence phishing.
@@ -840,7 +840,7 @@ Accept wildcard characters: False
 The MarkAsSpamBulkMail parameter allows spam filtering to act on bulk email messages. Valid values are:
 
 - Off: The message is stamped with the BCL, but no action is taken for a bulk email filtering verdict. In effect, the values of the BulkThreshold and BulkSpamAction parameters are irrelevant.
-- On: This is the default value. A BCL that's greater than the BulkThreshold value is converted to an SCL 6 that corresponds to a filtering verdict of spam, and the BulkSpamAction value is taken on the message.
+- On: This value is the default. A BCL that's greater than the BulkThreshold value is converted to an SCL 6 that corresponds to a filtering verdict of spam, and the BulkSpamAction value is taken on the message.
 - Test: This value is available, but isn't used for this parameter.
 
 ```yaml
@@ -861,7 +861,7 @@ Accept wildcard characters: False
 
 The MarkAsSpamEmbedTagsInHtml parameter marks a message as spam when the message contains HTML \<embed\> tags. Valid values are:
 
-- Off: The setting is disabled. This is the default value, and we recommend that you don't change it.
+- Off: The setting is disabled. This value is the default, and we recommend that you don't change it.
 - On: The setting is enabled. Messages that contain HTML \<embed\> tags are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Embed tag in html` is added to the message.
 - Test: The action specified by the TestModeAction parameter is taken on the message.
 
@@ -883,7 +883,7 @@ Accept wildcard characters: False
 
 The MarkAsSpamEmptyMessages parameter marks a message as spam when the message contains no subject, no content in the message body, and no attachments. Valid values are:
 
-- Off: The setting is disabled. This is the default value, and we recommend that you don't change it.
+- Off: The setting is disabled. This value is the default, and we recommend that you don't change it.
 - On: The setting is enabled. Empty messages are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Empty Message` is added to the message.
 - Test: The action specified by the TestModeAction parameter is taken on the message.
 
@@ -905,7 +905,7 @@ Accept wildcard characters: False
 
 The MarkAsSpamFormTagsInHtml parameter marks a message as spam when the message contains HTML \<form\> tags. Valid values are:
 
-- Off: The setting is disabled. This is the default value, and we recommend that you don't change it.
+- Off: The setting is disabled. This value is the default, and we recommend that you don't change it.
 - On: The setting is enabled. Messages that contain HTML \<form\> tags are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Form tag in html` is added to the message.
 - Test: The action specified by the TestModeAction parameter is taken on the message.
 
@@ -927,7 +927,7 @@ Accept wildcard characters: False
 
 The MarkAsSpamFramesInHtml parameter marks a message as spam when the message contains HTML \<frame\> or \<iframe\> tags. Valid values are:
 
-- Off: The setting is disabled. This is the default value, and we recommend that you don't change it.
+- Off: The setting is disabled. This value is the default, and we recommend that you don't change it.
 - On: The setting is enabled. Messages that contain HTML \<frame\> or \<iframe\> tags are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: IFRAME or FRAME in HTML` is added to the message.
 - Test: The action specified by the TestModeAction parameter is taken on the message.
 
@@ -949,7 +949,7 @@ Accept wildcard characters: False
 
 The MarkAsSpamFromAddressAuthFail parameter marks a message as spam when Sender ID filtering encounters a hard fail. This setting combines an Sender Policy Framework (SPF) check with a Sender ID check to help protect against message headers that contain forged senders. Valid values are:
 
-- Off: The setting is disabled. This is the default value, and we recommend that you don't change it.
+- Off: The setting is disabled. This value is the default, and we recommend that you don't change it.
 - On: The setting is enabled. Messages where Sender ID filtering encounters a hard fail are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: SPF From Record Fail` is added to the message.
 
 ```yaml
@@ -970,7 +970,7 @@ Accept wildcard characters: False
 
 The MarkAsSpamJavaScriptInHtml parameter marks a message as spam when the message contains JavaScript or VBScript. Valid values are:
 
-- Off: The setting is disabled. This is the default value, and we recommend that you don't change it.
+- Off: The setting is disabled. This value is the default, and we recommend that you don't change it.
 - On: The setting is enabled. Messages that contain JavaScript or VBScript are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Javascript or VBscript tags in HTML` is added to the message.
 - Test: The action specified by the TestModeAction parameter is taken on the message.
 
@@ -992,7 +992,7 @@ Accept wildcard characters: False
 
 The MarkAsSpamNdrBackscatter parameter marks a message as spam when the message is a non-delivery report (also known as an NDR or bounce messages) sent to a forged sender (known as *backscatter*). Valid values are:
 
-- Off: The setting is disabled. This is the default value, and we recommend that you don't change it.
+- Off: The setting is disabled. This value is the default, and we recommend that you don't change it.
 - On: The setting is enabled. Backscatter is given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Backscatter NDR` is added to the message.
 
 ```yaml
@@ -1013,7 +1013,7 @@ Accept wildcard characters: False
 
 The MarkAsSpamObjectTagsInHtml parameter marks a message as spam when the message contains HTML \<object\> tags. Valid values are:
 
-- Off: The setting is disabled. This is the default value, and we recommend that you don't change it.
+- Off: The setting is disabled. This value is the default, and we recommend that you don't change it.
 - On: The setting is enabled. Messages that contain HTML \<object\> tags are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Object tag in html` is added to the message.
 - Test: The action specified by the TestModeAction parameter is taken on the message.
 
@@ -1035,7 +1035,7 @@ Accept wildcard characters: False
 
 The MarkAsSpamSensitiveWordList parameter marks a message as spam when the message contains words from the sensitive words list. Microsoft maintains a dynamic but non-editable list of words that are associated with potentially offensive messages. Valid values are:
 
-- Off: The setting is disabled. This is the default value, and we recommend that you don't change it.
+- Off: The setting is disabled. This value is the default, and we recommend that you don't change it.
 - On: The setting is enabled. Messages that contain words from the sensitive word list in the subject or message body are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Sensitive word in subject/body` is added to the message.
 - Test: The action specified by the TestModeAction parameter is taken on the message.
 
@@ -1057,7 +1057,7 @@ Accept wildcard characters: False
 
 The MarkAsSpamSpfRecordHardFail parameter marks a message as spam when SPF record checking encounters a hard fail. Valid values are:
 
-- Off: The setting is disabled. This is the default value, and we recommend that you don't change it.
+- Off: The setting is disabled. This value is the default, and we recommend that you don't change it.
 - On: The setting is enabled. Messages sent from an IP address that isn't specified in the SPF Sender Policy Framework (SPF) record in DNS are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: SPF Record Fail` is added to the message.
 
 ```yaml
@@ -1078,7 +1078,7 @@ Accept wildcard characters: False
 
 The MarkAsSpamWebBugsInHtml parameter marks a message as spam when the message contains web bugs (also known as web beacons). Valid values are:
 
-- Off: The setting is disabled. This is the default value, and we recommend that you don't change it.
+- Off: The setting is disabled. This value is the default, and we recommend that you don't change it.
 - On: The setting is enabled. Messages that contain web bugs are given the SCL 9 (high confidence spam), and the X-header `X-CustomSpam: Web bug` is added to the message.
 - Test: The action specified by the TestModeAction parameter is taken on the message.
 
@@ -1178,7 +1178,7 @@ Accept wildcard characters: False
 
 The PhishZapEnabled parameter enables or disables zero-hour auto purge (ZAP) to detect phishing in already delivered messages in Exchange Online mailboxes. Valid values are:
 
-- $true: ZAP for phishing messages is enabled. This is the default value. The result depends on the spam filtering verdict action for phishing messages: MoveToJmf = Read and unread phishing messages are moved to the Junk Email folder. Delete, Redirect, or Quarantine = Read and unread phishing messages are quarantined. AddXHeader or ModifySubject = no action is taken on the message.
+- $true: ZAP for phishing messages is enabled. This value is the default. The result depends on the spam filtering verdict action for phishing messages: MoveToJmf = Read and unread phishing messages are moved to the Junk Email folder. Delete, Redirect, or Quarantine = Read and unread phishing messages are quarantined. AddXHeader or ModifySubject = no action is taken on the message.
 - $false: ZAP for phishing messages is disabled.
 
 You configure ZAP for spam with the SpamZapEnabled parameter.
@@ -1285,7 +1285,7 @@ The SpamAction parameter specifies the action to take on messages that are marke
 - AddXHeader: Add the AddXHeaderValue parameter value to the message header, deliver the message, and move the message to the Junk Email folder (same caveats as MoveToJmf).
 - Delete : Delete the message during filtering. Use caution when selecting this value, because you can't recover the deleted message.
 - ModifySubject: Add the ModifySubject parameter value to the beginning of the subject line, deliver the message, and move the message to the Junk Email folder (same caveats as MoveToJmf).
-- MoveToJmf: This is the default value. Deliver the message to the Junk Email folder in the recipient's mailbox. Hybrid environments need mail flow rules in the on-premises Exchange organization. For instructions, see [Configure standalone EOP to deliver spam to the Junk Email folder in hybrid environments](https://learn.microsoft.com/exchange/standalone-eop/configure-eop-spam-protection-hybrid).
+- MoveToJmf: This value is the default. Deliver the message to the Junk Email folder in the recipient's mailbox. Hybrid environments need mail flow rules in the on-premises Exchange organization. For instructions, see [Configure standalone EOP to deliver spam to the Junk Email folder in hybrid environments](https://learn.microsoft.com/exchange/standalone-eop/configure-eop-spam-protection-hybrid).
 - Quarantine: Deliver the message to quarantine. By default, messages that are quarantined as spam are available to the intended recipients and admins. Or, you can use the SpamQuarantineTag parameter to specify what end-users are allowed to do on quarantined messages.
 - Redirect: Redirect the message to the recipients specified by the RedirectToRecipients parameter.
 
@@ -1335,7 +1335,7 @@ Accept wildcard characters: False
 
 The SpamZapEnabled parameter enables or disables zero-hour auto purge (ZAP) to detect spam in already delivered messages in Exchange Online mailboxes. Valid values are:
 
-- $true: ZAP for spam is enabled. This is the default value. The result depends on the spam filtering verdict action for spam messages: MoveToJmf = Unread spam messages are moved to the Junk Email folder. Delete, Redirect, or Quarantine = Unread spam messages are quarantined. AddXHeader or ModifySubject = no action is taken on the message.
+- $true: ZAP for spam is enabled. This value is the default. The result depends on the spam filtering verdict action for spam messages: MoveToJmf = Unread spam messages are moved to the Junk Email folder. Delete, Redirect, or Quarantine = Unread spam messages are quarantined. AddXHeader or ModifySubject = no action is taken on the message.
 - $false: ZAP for spam is disabled.
 
 You configure ZAP for phishing messages with the PhishZapEnabled parameter.
@@ -1358,7 +1358,7 @@ Accept wildcard characters: False
 
 The TestModeAction parameter specifies the additional action to take on messages when one or more IncreaseScoreWith\* or MarkAsSpam\* ASF parameters are set to the value Test. Valid values are:
 
-- None: This is the default value, and we recommend that you don't change it.
+- None: This value is the default, and we recommend that you don't change it.
 - AddXHeader: The X-header value `X-CustomSpam: This message was filtered by the custom spam filter option` is added to the message.
 - BccMessage: Redirect the message to the recipients specified by the TestModeBccToRecipients parameter.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-HostedContentFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-HostedContentFilterRule.md
index 120a069048..d2689d5311 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-HostedContentFilterRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-HostedContentFilterRule.md
@@ -42,7 +42,7 @@ Set-HostedContentFilterRule [-Identity] <RuleIdParameter>
 > [!IMPORTANT]
 > Different types of recipient conditions use AND logic (the recipient must satisfy **all** specified conditions). Different types of recipient exceptions use OR logic (the recipient must satisfy **any** of the specified exceptions). For more information, see [Use the Microsoft Defender portal to create anti-spam policies](https://learn.microsoft.com/defender-office-365/anti-spam-policies-configure#use-the-microsoft-defender-portal-to-create-anti-spam-policies).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-HostedOutboundSpamFilterPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-HostedOutboundSpamFilterPolicy.md
index fe113889c6..bc15d5b3d0 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-HostedOutboundSpamFilterPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-HostedOutboundSpamFilterPolicy.md
@@ -39,7 +39,7 @@ Set-HostedOutboundSpamFilterPolicy [-Identity] <HostedOutboundSpamFilterPolicyId
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -85,7 +85,7 @@ The ActionWhenThresholdReach parameter specifies the action to take when any of
 
 - Alert: No action, alert only.
 - BlockUser: Prevent the user from sending email messages.
-- BlockUserForToday: Prevent the user from sending email messages until the following day. This is the default value.
+- BlockUserForToday: Prevent the user from sending email messages until the following day. This value is the default.
 
 ```yaml
 Type: OutboundRecipientLimitsExceededAction
@@ -124,7 +124,7 @@ Accept wildcard characters: False
 
 The AutoForwardingMode specifies how the policy controls automatic email forwarding to external recipients. Valid values are:
 
-- Automatic: This is the default value. This value is now the same as Off. When this value was originally introduced, it was equivalent to On. Over time, thanks to the principles of [secure by default](https://learn.microsoft.com/defender-office-365/secure-by-default), the effect of this value was eventually changed to Off for all customers. For more information, see [this blog post](https://techcommunity.microsoft.com/t5/exchange-team-blog/all-you-need-to-know-about-automatic-email-forwarding-in/ba-p/2074888).
+- Automatic: This value is the default. This value is now the same as Off. When this value was originally introduced, it was equivalent to On. Over time, thanks to the principles of [secure by default](https://learn.microsoft.com/defender-office-365/secure-by-default), the effect of this value was eventually changed to Off for all customers. For more information, see [this blog post](https://techcommunity.microsoft.com/t5/exchange-team-blog/all-you-need-to-know-about-automatic-email-forwarding-in/ba-p/2074888).
 - On: Automatic external email forwarding isn't disabled by the policy.
 - Off: Automatic external email forwarding is disabled by the policy and results in a non-delivery report (also known as an NDR or bounce message) to the sender.
 
@@ -170,7 +170,7 @@ Accept wildcard characters: False
 The BccSuspiciousOutboundMail parameter specifies whether to add recipients to the Bcc field of outgoing spam messages. Valid values are:
 
 - $true: The recipients specified by the BccSuspiciousOutboundAdditionalRecipients parameter are added to outgoing spam messages.
-- $false: No additional messages are added to outgoing spam messages. This is the default value.
+- $false: No additional messages are added to outgoing spam messages. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -209,12 +209,12 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online, Exchange Online Protection
 
-**Note**: This setting has been replaced by the default alert policy named **User restricted from sending email**, which sends notification messages to admins. We recommend that you use the alert policy rather than this setting to notify admins and other users. For instructions, see [Verify the alert settings for restricted users](https://learn.microsoft.com/defender-office-365/outbound-spam-restore-restricted-users#verify-the-alert-settings-for-restricted-users).
+**Note**: This setting is replaced by the default alert policy named **User restricted from sending email**, which sends notification messages to admins. We recommend that you use the alert policy rather than this setting to notify admins and other users. For instructions, see [Verify the alert settings for restricted users](https://learn.microsoft.com/defender-office-365/outbound-spam-restore-restricted-users#verify-the-alert-settings-for-restricted-users).
 
 The NotifyOutboundSpam parameter specify whether to notify admins when outgoing spam is detected. Valid values are:
 
 - $true: Notify the admins specified by the NotifyOutboundSpamRecipients parameter.
-- $false: Don't send notifications. This is the default value.
+- $false: Don't send notifications. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -232,7 +232,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online, Exchange Online Protection
 
-**Note**: This setting has been replaced by the default alert policy named **User restricted from sending email**, which sends notification messages to admins. We recommend that you use the alert policy rather than this setting to notify admins and other users. For instructions, see [Verify the alert settings for restricted users](https://learn.microsoft.com/defender-office-365/outbound-spam-restore-restricted-users#verify-the-alert-settings-for-restricted-users).
+**Note**: This setting is replaced by the default alert policy named **User restricted from sending email**, which sends notification messages to admins. We recommend that you use the alert policy rather than this setting to notify admins and other users. For instructions, see [Verify the alert settings for restricted users](https://learn.microsoft.com/defender-office-365/outbound-spam-restore-restricted-users#verify-the-alert-settings-for-restricted-users).
 
 The NotifyOutboundSpamRecipients parameter specifies the email addresses of admins to notify when an outgoing spam is detected. You can specify multiple email addresses separated by commas.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-HostedOutboundSpamFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-HostedOutboundSpamFilterRule.md
index f404f720ce..d5d7fc9ec7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-HostedOutboundSpamFilterRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-HostedOutboundSpamFilterRule.md
@@ -39,7 +39,7 @@ Set-HostedOutboundSpamFilterRule [-Identity] <RuleIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-HybridConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Set-HybridConfiguration.md
index b9750e5e1b..6e76762288 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-HybridConfiguration.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-HybridConfiguration.md
@@ -45,7 +45,7 @@ Set-HybridConfiguration
 ## DESCRIPTION
 The Set-HybridConfiguration cmdlet modifies the hybrid configuration features, such as enabling secure mail, designating a specific Mailbox server for hybrid functionality, or enabling or disabling free/busy sharing between on-premises Exchange and Exchange Online.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -54,7 +54,7 @@ You need to be assigned permissions before you can run this cmdlet. Although thi
 Set-HybridConfiguration -SecureMailCertificateThumbprint AC00F35CBA8359953F4126E0984B5CCAFA2F4F17
 ```
 
-In Exchange Server 2010, this example specifies that the hybrid configuration will use the certificate with the thumbprint AC00F35CBA8359953F4126E0984B5CCAFA2F4F17 as the certificate for Secure Mail messaging.
+In Exchange Server 2010, this example specifies the hybrid configuration uses the certificate with the thumbprint AC00F35CBA8359953F4126E0984B5CCAFA2F4F17 as the certificate for Secure Mail messaging.
 
 ### Example 2
 ```powershell
@@ -210,7 +210,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-This parameter has been deprecated and is no longer used.
+This parameter is deprecated and no longer used.
 
 There can be only one HybridConfiguration object in an Exchange organization.
 
@@ -277,7 +277,7 @@ Accept wildcard characters: False
 
 This parameter is available only in Exchange Server 2010.
 
-The SecureMailCertificateThumbprint parameter specifies the thumbprint of the X.509 certificate to be used as the certificate for hybrid deployment secure message transport. This certificate cannot be self-signed, must be obtained from a trusted certificate authority (CA), and must be installed on all Hub Transport servers defined in the TransportServers parameter.
+The SecureMailCertificateThumbprint parameter specifies the thumbprint of the X.509 certificate to be used as the certificate for hybrid deployment secure message transport. This certificate can't be self-signed, must be obtained from a trusted certificate authority (CA), and must be installed on all Hub Transport servers defined in the TransportServers parameter.
 
 ```yaml
 Type: String
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-IRMConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Set-IRMConfiguration.md
index 84722adaa4..31c494d89b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-IRMConfiguration.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-IRMConfiguration.md
@@ -13,7 +13,7 @@ title: Set-IRMConfiguration
 # Set-IRMConfiguration
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-IRMConfiguration cmdlet to configure Information Rights Management (IRM) features on your organization.
 
@@ -54,7 +54,7 @@ Set-IRMConfiguration [-Identity <OrganizationIdParameter>]
 ## DESCRIPTION
 IRM requires the use of an on-premises AD RMS server or the ILS service. IRM features can be selectively enabled or disabled.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -109,7 +109,7 @@ This parameter is available only in the cloud-based service.
 
 The AutomaticServiceUpdateEnabled parameter specifies whether to allow the automatic addition of new features within Azure Information Protection for your cloud-based organization. Valid values are:
 
-- $true: New Azure Information Protection features announced through Microsoft 365 message center will be enabled automatically in your cloud-based organization.
+- $true: New Azure Information Protection features announced through Microsoft 365 message center are enabled automatically in your cloud-based organization.
 - $false: Prevents new Azure Information Protection features from automatically being introduced into your tenant organization.
 
 ```yaml
@@ -155,7 +155,7 @@ This parameter is available only in on-premises Exchange.
 
 The ClientAccessServerEnabled parameter specifies whether Exchange Client Access servers are allowed to authenticate clients that do not have direct access to AD RMS (for example, Outlook on the web, Exchange ActiveSync or remote Outlook Anywhere clients). Valid values are:
 
-- $true: Client Access servers are allowed to authenticate clients. This is the default value. Note that enabling IRM in Outlook on the web requires additional configuration on AD RMS servers. For more information, see [Information Rights Management in Outlook Web App](https://learn.microsoft.com/exchange/information-rights-management-in-outlook-web-app-exchange-2013-help).
+- $true: Client Access servers are allowed to authenticate clients. This value is the default. Enabling IRM in Outlook on the web requires additional configuration on AD RMS servers. For more information, see [Information Rights Management in Outlook Web App](https://learn.microsoft.com/exchange/information-rights-management-in-outlook-web-app-exchange-2013-help).
 - $false: Client Access servers aren't allowed to authenticate clients.
 
 ```yaml
@@ -199,8 +199,8 @@ This parameter is available only in the cloud-based service.
 
 The DecryptAttachmentForEncryptOnly parameter specifies whether mail recipients have unrestricted rights on the attachment or not for Encrypt-only mails sent using Microsoft Purview Message Encryption. Valid values are:
 
-- $true: The recipients will have unrestricted rights on attachments sent using Encrypt-Only policy.
-- $false: The recipients will not have unrestricted rights on attachments sent using Encrypt-Only policy.
+- $true: The recipients have unrestricted rights on attachments sent using Encrypt-Only policy.
+- $false: The recipients don't have unrestricted rights on attachments sent using Encrypt-Only policy.
 
 This parameter replaces the deprecated DecryptAttachmentFromPortal parameter.
 
@@ -313,12 +313,12 @@ Accept wildcard characters: False
 
 This parameter is available only in on-premises Exchange.
 
-The ExternalLicensingEnabled parameter specifies whether Exchange will try to acquire licenses from clusters other than the one it is configured to use. Without this setting, if Exchange receives many messages protected with a random key, the server will devote excessive resources to validating signatures and decrypting messages, even if the keys aren't valid.
+The ExternalLicensingEnabled parameter specifies whether Exchange tries to acquire licenses from clusters other than the one it is configured to use. Without this setting, if Exchange receives many messages protected with a random key, the server devotes excessive resources to validating signatures and decrypting messages, even if the keys aren't valid.
 
 Valid values are:
 
-- $true: Exchange will try to acquire licenses from clusters other than the one it is configured to use. This value can help prevent denial of service (DoS) attacks.
-- $false: Exchange will try to acquire licenses only from clusters that it is configured to use. This is the default value. The *LicensingLocation* parameter specifies the list of allowed clusters.
+- $true: Exchange tries to acquire licenses from clusters other than the one it is configured to use. This value can help prevent denial of service (DoS) attacks.
+- $false: Exchange tries to acquire licenses only from clusters that it is configured to use. This value is the default. The *LicensingLocation* parameter specifies the list of allowed clusters.
 
 ```yaml
 Type: Boolean
@@ -360,8 +360,8 @@ Accept wildcard characters: False
 
 The InternalLicensingEnabled parameter specifies whether to enable IRM features for messages that are sent to internal recipients. Valid values are:
 
-- $true: IRM features are enabled for internal messages. This is the default value in Exchange Online.
-- $false: IRM features are disabled for internal messages. This is the default value in on-premises Exchange. Note that this value causes the Get-RMSTemplate to return no AD RMS templates.
+- $true: IRM features are enabled for internal messages. This value is the default in Exchange Online.
+- $false: IRM features are disabled for internal messages. This value is the default in on-premises Exchange. This value causes the Get-RMSTemplate to return no AD RMS templates.
 
 ```yaml
 Type: Boolean
@@ -381,7 +381,7 @@ Accept wildcard characters: False
 
 The JournalReportDecryptionEnabled parameter specifies whether to enable journal report decryption. Valid values are:
 
-- $true: Journal report encryption is enabled. A decrypted copy of the IRM-protected message is attached to the journal report. This is the default value. Note that journal report decryption requires additional configuration on AD RMS servers. For more information, see [Journal report decryption](https://learn.microsoft.com/exchange/journal-report-decryption-exchange-2013-help).
+- $true: Journal report encryption is enabled. A decrypted copy of the IRM-protected message is attached to the journal report. This value is the default. Journal report decryption requires additional configuration on AD RMS servers. For more information, see [Journal report decryption](https://learn.microsoft.com/exchange/journal-report-decryption-exchange-2013-help).
 - $false: Journal report decryption is disabled.
 
 ```yaml
@@ -404,7 +404,7 @@ The LicensingLocation parameter specifies the RMS licensing URLs. You can specif
 
 Typically, in on-premises Exchange, you only need to use this parameter in cross-forest deployments of AD RMS licensing servers.
 
-**IMPORTANT**: If you specify multiple URLs, always specify the Azure RMS URL first. Otherwise, encryption services won't function properly.
+**IMPORTANT**: If you specify multiple URLs, always specify the Azure RMS URL first. Otherwise, encryption services don't function properly.
 
 ```yaml
 Type: MultiValuedProperty
@@ -486,7 +486,7 @@ Accept wildcard characters: False
 
 The SearchEnabled parameter specifies whether to enable searching of IRM-encrypted messages in Outlook on the web (formerly known as Outlook Web App). Valid values are:
 
-- $true: Searching IRM-encrypted messages in Outlook on the web is enabled. This is the default value.
+- $true: Searching IRM-encrypted messages in Outlook on the web is enabled. This value is the default.
 - $false: Searching IRM-encrypted messages in Outlook on the web is disabled.
 
 ```yaml
@@ -533,7 +533,7 @@ This parameter is available only in the cloud-based service.
 The SimplifiedClientAccessEnabled parameter specifies whether to enable the Protect button in Outlook on the web. Valid values are:
 
 - $true: The Protect button is enabled in Outlook on the web.
-- $false: The Protect button is disabled in Outlook on the web. This is the default value.
+- $false: The Protect button is disabled in Outlook on the web. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -578,7 +578,7 @@ The TransportDecryptionSetting parameter specifies the transport decryption conf
 
 - Disabled: Transport decryption is disabled for internal and external messages.
 - Mandatory: Messages that can't be decrypted are rejected with a non-delivery report (also known as an NDR or bounce message).
-- Optional: Messages are decrypted if possible, but are delivered even if decryption fails. This is the default value.
+- Optional: Messages are decrypted if possible, but are delivered even if decryption fails. This value is the default.
 
 ```yaml
 Type: TransportDecryptionSetting
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ImapSettings.md b/exchange/exchange-ps/ExchangePowerShell/Set-ImapSettings.md
index 8e5266dbf8..c596ae4a64 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ImapSettings.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ImapSettings.md
@@ -59,7 +59,7 @@ Set-ImapSettings [-AuthenticatedConnectionTimeout <EnhancedTimeSpan>]
 ## DESCRIPTION
 You can run the Set-ImapSettings cmdlet for a single Exchange server that's running the Microsoft Exchange IMAP4 service, or for all Exchange servers that are running the Microsoft Exchange IMAP4 service.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -98,7 +98,7 @@ Set-ImapSettings -X509CertificateName mail.contoso.com
 
 This example specifies the certificate that contains mail.contoso.com is used to encrypt IMAP4 client connections.
 
-**Note**: For single subject certificates or a SAN certificates, you also need to assign the certificate to the Exchange IMAP service by using the Enable-ExchangeCertificate cmdlet. For wildcard certificates, you don't need to assign the certificate to the Exchange IMAP service (you'll receive an error if you try).
+**Note**: For single subject certificates or a SAN certificates, you also need to assign the certificate to the Exchange IMAP service by using the Enable-ExchangeCertificate cmdlet. For wildcard certificates, you don't need to assign the certificate to the Exchange IMAP service (you get an error if you try).
 
 ## PARAMETERS
 
@@ -148,7 +148,7 @@ Accept wildcard characters: False
 
 The CalendarItemRetrievalOption parameter specifies how calendar items are presented to IMAP4 clients. Valid values are:
 
-- 0 or iCalendar. This is the default value.
+- 0 or iCalendar. This value is the default.
 - 1 or IntranetUrl
 - 2 or InternetUrl
 - 3 or Custom
@@ -213,7 +213,7 @@ Accept wildcard characters: False
 The EnableExactRFC822Size parameter specifies how message sizes are presented to IMAP4 clients. Valid values are:
 
 - $true: Calculate the exact message size. Because this setting can negatively affect performance, you should configure it only if it's required by your IMAP4 clients.
-- $false: Use an estimated message size. This is the default value.
+- $false: Use an estimated message size. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -233,7 +233,7 @@ Accept wildcard characters: False
 
 The EnableGSSAPIAndNTLMAuth parameter specifies whether connections can use Integrated Windows authentication (NTLM) using the Generic Security Services application programming interface (GSSAPI). This setting applies to connections where Transport Layer Security (TLS) is disabled. Valid values are:
 
-- $true: NTLM for IMAP4 connections is enabled. This is the default value.
+- $true: NTLM for IMAP4 connections is enabled. This value is the default.
 - $false: NTLM for IMAP4 connections is disabled.
 
 ```yaml
@@ -257,7 +257,7 @@ The EnforceCertificateErrors parameter specifies whether to enforce valid Secure
 The default setting is $false.
 
 - $true: If the certificate isn't valid or doesn't match the target IMAP4 server's FQDN, the connection attempt fails.
-- $false: The server doesn't deny IMAP4 connections based on certificate errors. This is the default value.
+- $false: The server doesn't deny IMAP4 connections based on certificate errors. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -277,7 +277,7 @@ Accept wildcard characters: False
 
 The ExtendedProtectionPolicy parameter specifies how Extended Protection for Authentication is used. Valid values are:
 
-- None: Extended Protection for Authentication isn't used. This is the default value.
+- None: Extended Protection for Authentication isn't used. This value is the default.
 - Allow: Extended Protection for Authentication is used only if it's supported by the incoming IMAP4 connection. If it's not, Extended Protection for Authentication isn't used.
 - Require: Extended Protection for Authentication is required for all IMAP4 connections. If the incoming IMAP4 connection doesn't support it, the connection is rejected.
 
@@ -377,8 +377,8 @@ Accept wildcard characters: False
 
 The LogFileRollOverSettings parameter specifies how frequently IMAP4 protocol logging creates a new log file. Valid values are:
 
-- 1 or Hourly. This is the default value in Exchange 2019 and Exchange 2016.
-- 2 or Daily. This is the default value in Exchange 2013 and Exchange 2010.
+- 1 or Hourly. This value is the default in Exchange 2019 and Exchange 2016.
+- 2 or Daily. This value is the default in Exchange 2013 and Exchange 2010.
 - 3 or Weekly.
 - 4 or Monthly.
 
@@ -404,7 +404,7 @@ The LoginType parameter specifies the authentication method for IMAP4 connection
 
 - 1 or PlainTextLogin.
 - 2 or PlainTextAuthentication.
-- 3 or SecureLogin. This is the default value.
+- 3 or SecureLogin. This value is the default.
 
 ```yaml
 Type: LoginOptions
@@ -432,7 +432,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The default value is 0, which means a new IMAP4 protocol log file is created at the frequency that's specified by the LogFileRollOverSettings parameter.
 
@@ -533,7 +533,7 @@ The MessageRetrievalMimeFormat parameter specifies the MIME encoding of messages
 - 2 or HtmlAndTextAlternative.
 - 3 or TextEnrichedOnly.
 - 4 or TextEnrichedAndTextAlternative.
-- 5 or BestBodyFormat. This is the default value.
+- 5 or BestBodyFormat. This value is the default.
 - 6 or Tnef.
 
 ```yaml
@@ -595,7 +595,7 @@ Accept wildcard characters: False
 The ProtocolLogEnabled parameter specifies whether to enable protocol logging for IMAP4. Valid values are:
 
 - $true: IMAP4 protocol logging is enabled.
-- $false: IMAP4 protocol logging is disabled. This is the default value.
+- $false: IMAP4 protocol logging is disabled. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -659,7 +659,7 @@ Accept wildcard characters: False
 The ShowHiddenFoldersEnabled parameter specifies whether hidden mailbox folders are visible. Valid values are:
 
 - $true: Hidden folders are visible.
-- $false: Hidden folders aren't visible. This is the default value.
+- $false: Hidden folders aren't visible. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -704,7 +704,7 @@ Accept wildcard characters: False
 The SuppressReadReceipt parameter specifies whether to stop duplicate read receipts from being sent to IMAP4 clients that have the Send read receipts for messages I send setting configured in their IMAP4 email program. Valid values are:
 
 - $true: The sender receives a read receipt only when the recipient opens the message.
-- $false: The sender receives a read receipt when the recipient downloads the message, and when the recipient opens the message. This is the default value.
+- $false: The sender receives a read receipt when the recipient downloads the message, and when the recipient opens the message. This value is the default.
 
 ```yaml
 Type: Boolean
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-InboundConnector.md b/exchange/exchange-ps/ExchangePowerShell/Set-InboundConnector.md
index ab649d275a..cd67b28eb5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-InboundConnector.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-InboundConnector.md
@@ -52,7 +52,7 @@ Set-InboundConnector [-Identity] <InboundConnectorIdParameter>
 ## DESCRIPTION
 Inbound connectors accept email messages from remote domains that require specific configuration options.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -117,7 +117,7 @@ The CloudServicesMailEnabled parameter specifies whether the connector is used f
 
 Valid values are:
 
-- $true: The connector is used for mail flow in hybrid organizations, so cross-premises headers are preserved or promoted in messages that flow through the connector. This is the default value for connectors that are created by the Hybrid Configuration wizard. Certain X-MS-Exchange-Organization-\* headers in outbound messages that are sent from one side of the hybrid organization to the other are converted to X-MS-Exchange-CrossPremises-\* headers and are thereby preserved in messages. X-MS-Exchange-CrossPremises-\* headers in inbound messages that are received on one side of the hybrid organization from the other are promoted to X-MS-Exchange-Organization-\* headers. These promoted headers replace any instances of the same X-MS-Exchange-Organization-\* headers that already exist in messages.
+- $true: The connector is used for mail flow in hybrid organizations, so cross-premises headers are preserved or promoted in messages that flow through the connector. This value is the default for connectors that are created by the Hybrid Configuration wizard. Certain X-MS-Exchange-Organization-\* headers in outbound messages that are sent from one side of the hybrid organization to the other are converted to X-MS-Exchange-CrossPremises-\* headers and are thereby preserved in messages. X-MS-Exchange-CrossPremises-\* headers in inbound messages that are received on one side of the hybrid organization from the other are promoted to X-MS-Exchange-Organization-\* headers. These promoted headers replace any instances of the same X-MS-Exchange-Organization-\* headers that already exist in messages.
 - $false: The connector isn't used for mail flow in hybrid organizations, so any cross-premises headers are removed from messages that flow through the connector.
 
 ```yaml
@@ -177,7 +177,7 @@ Accept wildcard characters: False
 
 The ConnectorSource parameter specifies how the connector is created. Valid input for this parameter includes the following values:
 
-- Default: The connector is manually created. This is the default value.
+- Default: The connector is manually created. This value is the default.
 - HybridWizard: The connector is automatically created by the Hybrid Configuration Wizard.
 - Migrated: The connector was originally created in Microsoft Forefront Online Protection for Exchange.
 
@@ -247,7 +247,7 @@ Accept wildcard characters: False
 The EFSkipIPs parameter specifies the behavior of Enhanced Filtering for Connectors. Valid values are:
 
 - $true: Only the last message source is skipped.
-- $false: Skip the source IP addresses specified by the EFSkipIPs parameter. If no IP addresses are specified, Enhanced Filtering for Connectors is disabled on the connector. This is the default value.
+- $false: Skip the source IP addresses specified by the EFSkipIPs parameter. If no IP addresses are specified, Enhanced Filtering for Connectors is disabled on the connector. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -323,7 +323,7 @@ Accept wildcard characters: False
 
 The Enabled parameter enables or disables the connector. Valid values are:
 
-- $true: The connector is enabled. This is the default value.
+- $true: The connector is enabled. This value is the default.
 - $false: The connector is disabled.
 
 ```yaml
@@ -362,7 +362,7 @@ Accept wildcard characters: False
 
 The RequireTLS parameter specifies whether to require TLS transmission for all messages that are received by a Partner type connector. Valid values are:
 
-- $true: Reject messages if they aren't sent over TLS. This is the default value
+- $true: Reject messages if they aren't sent over TLS. This value is the default
 - $false: Allow messages if they aren't sent over TLS.
 
 **Note**: This parameter applies only to Partner type connectors.
@@ -386,7 +386,7 @@ Accept wildcard characters: False
 The RestrictDomainsToCertificate parameter specifies whether the Subject value of the TLS certificate is checked before messages can use the Partner type connector. Valid values are:
 
 - $true: Mail is allowed to use the connector only if the Subject value of the TLS certificate that the source email server uses to authenticate matches the TlsSenderCertificateName parameter value.
-- $false: The Subject value of the TLS certificate that the source email server uses to authenticate doesn't control whether mail from that source uses the connector. This is the default value.
+- $false: The Subject value of the TLS certificate that the source email server uses to authenticate doesn't control whether mail from that source uses the connector. This value is the default.
 
 **Note**: This parameter applies only to Partner type connectors.
 
@@ -409,7 +409,7 @@ Accept wildcard characters: False
 The RestrictDomainsToIPAddresses parameter specifies whether to reject mail that comes from unknown source IP addresses for Partner type connectors. Valid values are:
 
 - $true: Automatically reject mail from domains that are specified by the SenderDomains parameter if the source IP address isn't also specified by the SenderIPAddress parameter.
-- $false: Don't automatically reject mail from domains that are specified by the SenderDomains parameter based on the source IP address. This is the default value.
+- $false: Don't automatically reject mail from domains that are specified by the SenderDomains parameter based on the source IP address. This value is the default.
 
 **Note**: This parameter applies only to Partner type connectors.
 
@@ -514,7 +514,7 @@ Accept wildcard characters: False
 The TreatMessagesAsInternal parameter specifies an alternative method to identify messages sent from an on-premises organization as internal messages. You should only consider using this parameter when your on-premises organization doesn't use Exchange. Valid values are:
 
 - $true: Messages are considered internal if the sender's domain matches a domain that's configured in Microsoft 365. This setting allows internal mail flow between Microsoft 365 and on-premises organizations that don't have Exchange Server 2010 or later installed. However, this setting has potential security risks (for example, internal messages bypass antispam filtering), so use caution when configuring this setting.
-- $false: Messages aren't considered internal. This is the default value.
+- $false: Messages aren't considered internal. This value is the default.
 
 In hybrid environments, you don't need to use this parameter, because the Hybrid Configuration wizard automatically configures the required settings on the Inbound connector in Microsoft 365 and the Send connector in the on-premises Exchange organization (the CloudServicesMailEnabled parameter).
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-InboxRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-InboxRule.md
index 59223edb84..a9d14c5d20 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-InboxRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-InboxRule.md
@@ -13,7 +13,7 @@ title: Set-InboxRule
 # Set-InboxRule
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-InboxRule cmdlet to modify existing Inbox rules in mailboxes. Inbox rules process messages in the Inbox based on conditions specified and take actions such as moving a message to a specified folder or deleting a message.
 
@@ -100,7 +100,7 @@ The Set-InboxRule cmdlet allows you to modify the rule conditions, exceptions, a
 
 When you create, modify, remove, enable, or disable an Inbox rule in Exchange PowerShell, any client-side rules created by Microsoft Outlook are removed.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -905,7 +905,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 You need to use this parameter with the ExceptIfWithinSizeRangeMinimum parameter, and the value of this parameter must be greater than the value of ExceptIfWithinSizeRangeMinimum.
 
@@ -937,7 +937,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 You need to use this parameter with the ExceptIfWithinSizeRangeMaximum parameter, and the value of this parameter must be less than the value of ExceptIfWithinSizeRangeMaximum.
 
@@ -1016,7 +1016,7 @@ Accept wildcard characters: False
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
-A confirmation prompt warns you if the mailbox contains rules that were created by Outlook, because any client-side rules will be removed by the actions of this cmdlet.
+A confirmation prompt warns you if the mailbox contains rules that were created by Outlook, because any client-side rules are removed by the actions of this cmdlet.
 
 ```yaml
 Type: SwitchParameter
@@ -1816,7 +1816,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 You need to use this parameter with the WithinSizeRangeMinimum parameter, and the value of this parameter must be greater than the value of WithinSizeRangeMinimum.
 
@@ -1848,7 +1848,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 You need to use this parameter with the WithinSizeRangeMaximum parameter, and the value of this parameter must be less than the value of WithinSizeRangeMaximum.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-IntraOrganizationConnector.md b/exchange/exchange-ps/ExchangePowerShell/Set-IntraOrganizationConnector.md
index fb7f1e6a95..54ac46f17a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-IntraOrganizationConnector.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-IntraOrganizationConnector.md
@@ -13,7 +13,7 @@ title: Set-IntraOrganizationConnector
 # Set-IntraOrganizationConnector
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-IntraOrganizationConnector cmdlet to modify an existing Intra-Organization connector between two on-premises Exchange forests in an organization, between an on-premises Exchange organization and an Exchange Online organization or between two Exchange Online organizations.
 
@@ -36,7 +36,7 @@ Set-IntraOrganizationConnector [-Identity] <IntraOrganizationConnectorIdParamete
 ## DESCRIPTION
 Intra-Organizational connectors enable features and services between divisions in your Exchange organization. It allows for the expansion of organizational boundaries for features and services across different hosts and network boundaries, such as between Active Directory forests, between on-premises and cloud-based organizations or between tenants hosted in the same or different datacenters.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -154,7 +154,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
 
-The TargetAddressDomains parameter specifies the domain namespaces that will be used in the Intra-Organization connector. The domains must have valid Autodiscover endpoints defined in their organizations. The domains and their associated Autodiscover endpoints are used by the Intra-Organization connector for feature and service connectivity.
+The TargetAddressDomains parameter specifies the domain namespaces to be used in the Intra-Organization connector. The domains must have valid Autodiscover endpoints defined in their organizations. The domains and their associated Autodiscover endpoints are used by the Intra-Organization connector for feature and service connectivity.
 
 ```yaml
 Type: MultiValuedProperty
@@ -174,7 +174,7 @@ Accept wildcard characters: False
 
 This parameter is available only in the cloud-based service.
 
-The TargetSharingEpr parameter specifies the URL of the target Exchange Web Services that will be used in the Intra-Organization connector.
+The TargetSharingEpr parameter specifies the URL of the target Exchange Web Services to be used in the Intra-Organization connector.
 
 ```yaml
 Type: Uri
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-JournalRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-JournalRule.md
index 7cd7eda4b9..f0a36d4384 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-JournalRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-JournalRule.md
@@ -13,7 +13,7 @@ title: Set-JournalRule
 # Set-JournalRule
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-JournalRule cmdlet to modify an existing journal rule in your organization.
 
@@ -36,7 +36,7 @@ Set-JournalRule [-Identity] <RuleIdParameter>
 ## DESCRIPTION
 The Set-JournalRule cmdlet modifies an existing journal rule used in your organization.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-Label.md b/exchange/exchange-ps/ExchangePowerShell/Set-Label.md
index fd2b100f35..9afee26214 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-Label.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-Label.md
@@ -159,7 +159,7 @@ Some of the settings that you configure with this parameter are supported only b
 
 Supported settings for built-in labeling:
 
-- **BlockContentAnalysisServices**: Specifies a privacy setting to allow or prevent content in Word, Excel, PowerPoint, and Outlook from being sent to Microsoft for content analysis. Available values are True, and False (the default). This setting impacts services such as data loss prevention policy tips, automatic and recommended labeling, and Microsoft Copilot for Microsoft 365. Example: `Set-Label -Identity Confidential -AdvancedSettings @{BlockContentAnalysisServices="True"}`. For more information, see [Prevent some connected experiences that analyze content](https://learn.microsoft.com/purview/sensitivity-labels-office-apps#prevent-some-connected-experiences-that-analyze-content).
+- **BlockContentAnalysisServices**: Specifies a privacy setting to allow or prevent content in Word, Excel, PowerPoint, and Outlook from being sent to Microsoft for content analysis. Available values are True, and False (the default). This setting affects services such as data loss prevention policy tips, automatic and recommended labeling, and Microsoft Copilot for Microsoft 365. Example: `Set-Label -Identity Confidential -AdvancedSettings @{BlockContentAnalysisServices="True"}`. For more information, see [Prevent some connected experiences that analyze content](https://learn.microsoft.com/purview/sensitivity-labels-office-apps#prevent-some-connected-experiences-that-analyze-content).
 
 - **Color**: Specifies a label color as a hex triplet code for the red, green, and blue (RGB) components of the color. Example: `Set-Label -Identity 8faca7b8-8d20-48a3-8ea2-0f96310a848e -AdvancedSettings @{color="#40e0d0"}`. For more information, see [Configuring custom colors by using PowerShell](https://learn.microsoft.com/purview/sensitivity-labels-office-apps#configuring-custom-colors-by-using-powershell).
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-LabelPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-LabelPolicy.md
index 8646340ea5..7d14426eaa 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-LabelPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-LabelPolicy.md
@@ -416,7 +416,7 @@ Supported settings for built-in labeling:
 
 - **teamworkdefaultlabelid**: Outlook and Teams apps that support this setting apply a default label, or no label for meetings. Example: `Set-LabelPolicy -Identity Global -AdvancedSettings @{teamworkdefaultlabelid="General"}`. For more information about labeling meetings, see [Use sensitivity labels to protect calendar items, Teams meetings, and chat](https://learn.microsoft.com/purview/sensitivity-labels-meetings).
 
-- **HideBarByDefault**: For Office apps that support the sensitivity bar, don't display the sensitivity label name on the window bar title so that there's more space to display long file names. Just the label icon and color (if configured) will be displayed. Users can't revert this setting in the app. Example: `Set-LabelPolicy -Identity Global -AdvancedSettings @{HideBarByDefault="True"}`
+- **HideBarByDefault**: For Office apps that support the sensitivity bar, don't display the sensitivity label name on the window bar title so that there's more space to display long file names. Just the label icon and color (if configured) are displayed. Users can't revert this setting in the app. Example: `Set-LabelPolicy -Identity Global -AdvancedSettings @{HideBarByDefault="True"}`
 
 - **DisableShowSensitiveContent**: For Office apps that highlight the sensitive content that caused a label to be recommended, turn off these highlights and corresponding indications about the sensitive content. For more information, see [Sensitivity labels are automatically applied or recommended for your files and emails in Office](https://support.microsoft.com/office/sensitivity-labels-are-automatically-applied-or-recommended-for-your-files-and-emails-in-office-622e0d9c-f38c-470a-bcdb-9e90b24d71a1). Supported apps: Word for Windows (version 2311+). Example: `Set-LabelPolicy -Identity Global -AdvancedSettings @{DisableShowSensitiveContent="True"}`
 

From e9d0bfe1a56adaa18c3d3b3e468147538ccccc73 Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Wed, 6 Aug 2025 10:12:49 -0700
Subject: [PATCH 111/145] Create Get-CsTeamsPersonalAttendantPolicy.md

---
 .../Get-CsTeamsPersonalAttendantPolicy.md     | 111 ++++++++++++++++++
 1 file changed, 111 insertions(+)
 create mode 100644 teams/teams-ps/MicrosoftTeams/Get-CsTeamsPersonalAttendantPolicy.md

diff --git a/teams/teams-ps/MicrosoftTeams/Get-CsTeamsPersonalAttendantPolicy.md b/teams/teams-ps/MicrosoftTeams/Get-CsTeamsPersonalAttendantPolicy.md
new file mode 100644
index 0000000000..01c42fa033
--- /dev/null
+++ b/teams/teams-ps/MicrosoftTeams/Get-CsTeamsPersonalAttendantPolicy.md
@@ -0,0 +1,111 @@
+---
+external help file: Microsoft.Rtc.Management.dll-Help.xml
+online version: https://learn.microsoft.com/powershell/module/teams/get-csteamspersonalattendantpolicy
+applicable: Microsoft Teams
+title: Get-CsTeamsPersonalAttendantPolicy
+schema: 2.0.0
+author: juliiva
+ms.author: juliiva
+ms.reviewer:
+manager: jomarque
+---
+
+# Get-CsTeamsPersonalAttendantPolicy
+
+## SYNOPSIS
+
+**Limited Preview:** Functionality described in this document is currently in limited preview and only authorized organizations have access.
+
+Returns information about the Teams personal attendant policies configured for use in your organization.
+Teams personal attendant policies help determine which users are able to use personal attendant and its functionalities within Microsoft Teams.
+
+## SYNTAX
+
+### Identity (Default)
+```powershell
+Get-CsTeamsPersonalAttendantPolicy [-Identity <string>] [<CommonParameters>]
+```
+
+### Filter
+```powershell
+Get-CsTeamsPersonalAttendantPolicy [-Filter <string>] [<CommonParameters>]
+```
+
+## DESCRIPTION
+
+Returns information about the Teams personal attendant policies configured for use in your organization.
+Teams personal attendant policies help determine which users are able to use personal attendant and its functionalities within Microsoft Teams.
+
+## EXAMPLES
+
+### Example 1
+```powershell
+Get-CsTeamsPersonalAttendantPolicy -Identity SalesPersonalAttendantPolicy
+```
+
+Retrieves the personal attendant policy with the Identity "SalesPersonalAttendantPolicy".
+
+### Example 2
+```powershell
+Get-CsTeamsPersonalAttendantPolicy -Filter "tag:Sales*"
+```
+
+Retrieves the personal attendant policies with Identity starting with Sales.
+
+## PARAMETERS
+
+### -Identity
+Specify the TeamsPersonalAttendantPolicy that you would like to retrieve.
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -Filter
+Enables you to use wildcard characters when indicating the policy (or policies) to be returned.
+To return a collection of all the per-user policies, use this syntax: -Filter "tag:*".
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### CommonParameters
+This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).
+
+## INPUTS
+
+### None
+
+## OUTPUTS
+
+### System.Object
+
+## NOTES
+
+The cmdlet is available in Teams PowerShell module 7.2.1-preview or later.
+
+## RELATED LINKS
+
+[New-CsTeamsPersonalAttendantPolicy](./new-csteamspersonalattendantpolicy.md)
+
+[Set-CsTeamsPersonalAttendantPolicy](./set-csteamspersonalattendantpolicy.md)
+
+[Grant-CsTeamsPersonalAttendantPolicy](./grant-csteamspersonalattendantpolicy.md)
+
+[Remove-CsTeamsPersonalAttendantPolicy](./remove-csteamspersonalattendantpolicy.md)

From 4c37695d6753aa9cbda48c45289d6b9a06299bf6 Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Wed, 6 Aug 2025 10:14:22 -0700
Subject: [PATCH 112/145] Update Get-CsPersonalAttendantSettings.md

---
 .../MicrosoftTeams/Get-CsPersonalAttendantSettings.md         | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/teams/teams-ps/MicrosoftTeams/Get-CsPersonalAttendantSettings.md b/teams/teams-ps/MicrosoftTeams/Get-CsPersonalAttendantSettings.md
index bd61deb0f6..74e0fd7e61 100644
--- a/teams/teams-ps/MicrosoftTeams/Get-CsPersonalAttendantSettings.md
+++ b/teams/teams-ps/MicrosoftTeams/Get-CsPersonalAttendantSettings.md
@@ -6,9 +6,9 @@ Locale: en-US
 manager: jomarque
 Module Name: MicrosoftTeams
 ms.author: juliiva
-online version: https://learn.microsoft.com/powershell/module/microsoftteams/get-cspersonalattendantsettings
+online version: https://learn.microsoft.com/powershell/module/microsoftteams/get-csteamspersonalattendantpolicy
 schema: 2.0.0
-title: Get-CsPersonalAttendantSettings
+title: Get-CsTeamsPersonalAttendantPolicy
 ---
 
 # Get-CsPersonalAttendantSettings

From 3a1f3ed1e8896df41068b5d836f5e3b1b5a36c96 Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Wed, 6 Aug 2025 10:16:11 -0700
Subject: [PATCH 113/145] Update Get-CsTeamsPersonalAttendantPolicy.md

---
 .../Get-CsTeamsPersonalAttendantPolicy.md            | 12 +++---------
 1 file changed, 3 insertions(+), 9 deletions(-)

diff --git a/teams/teams-ps/MicrosoftTeams/Get-CsTeamsPersonalAttendantPolicy.md b/teams/teams-ps/MicrosoftTeams/Get-CsTeamsPersonalAttendantPolicy.md
index 01c42fa033..721d583679 100644
--- a/teams/teams-ps/MicrosoftTeams/Get-CsTeamsPersonalAttendantPolicy.md
+++ b/teams/teams-ps/MicrosoftTeams/Get-CsTeamsPersonalAttendantPolicy.md
@@ -21,14 +21,8 @@ Teams personal attendant policies help determine which users are able to use per
 
 ## SYNTAX
 
-### Identity (Default)
-```powershell
-Get-CsTeamsPersonalAttendantPolicy [-Identity <string>] [<CommonParameters>]
 ```
-
-### Filter
-```powershell
-Get-CsTeamsPersonalAttendantPolicy [-Filter <string>] [<CommonParameters>]
+Get-CsTeamsPersonalAttendantPolicy [-Identity <string>] [-Filter <string>] [<CommonParameters>]
 ```
 
 ## DESCRIPTION
@@ -39,14 +33,14 @@ Teams personal attendant policies help determine which users are able to use per
 ## EXAMPLES
 
 ### Example 1
-```powershell
+```
 Get-CsTeamsPersonalAttendantPolicy -Identity SalesPersonalAttendantPolicy
 ```
 
 Retrieves the personal attendant policy with the Identity "SalesPersonalAttendantPolicy".
 
 ### Example 2
-```powershell
+```
 Get-CsTeamsPersonalAttendantPolicy -Filter "tag:Sales*"
 ```
 

From 572c49f431a6fd7d4c13ac0f9ec999225be4ef2b Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Wed, 6 Aug 2025 10:19:22 -0700
Subject: [PATCH 114/145] Create Grant-CsTeamsPersonalAttendantPolicy.md

---
 .../Grant-CsTeamsPersonalAttendantPolicy.md   | 171 ++++++++++++++++++
 1 file changed, 171 insertions(+)
 create mode 100644 teams/teams-ps/MicrosoftTeams/Grant-CsTeamsPersonalAttendantPolicy.md

diff --git a/teams/teams-ps/MicrosoftTeams/Grant-CsTeamsPersonalAttendantPolicy.md b/teams/teams-ps/MicrosoftTeams/Grant-CsTeamsPersonalAttendantPolicy.md
new file mode 100644
index 0000000000..7c28c9d8f3
--- /dev/null
+++ b/teams/teams-ps/MicrosoftTeams/Grant-CsTeamsPersonalAttendantPolicy.md
@@ -0,0 +1,171 @@
+---
+applicable: Microsoft Teams
+author: juliiva
+external help file: Microsoft.Rtc.Management.dll-Help.xml
+Locale: en-US
+manager: jomarque
+Module Name: MicrosoftTeams
+ms.author: juliiva
+online version: https://learn.microsoft.com/powershell/module/microsoftteams/grant-csteamspersonalattendantpolicy
+schema: 2.0.0
+title: Grant-CsTeamsPersonalAttendantPolicy
+---
+
+
+# Grant-CsTeamsPersonalAttendantPolicy
+
+## SYNOPSIS
+
+**Limited Preview:** Functionality described in this document is currently in limited preview and only authorized organizations have access.
+
+Assigns a specific Teams Personal Attendant Policy to a user, a group of users, or sets the Global policy instance.
+
+## SYNTAX
+
+```powershell
+Grant-CsTeamsPersonalAttendantPolicy [-Identity <string>] [-PolicyName <string>] [-PassThru] [-Global] [-Rank <int>] [<CommonParameters>]
+```
+
+## DESCRIPTION
+The Teams Personal Attendant Policies designate how users are able to use personal attendant and its functionalities within Microsoft Teams. This cmdlet allows admins to grant user level policies to individual users, to members of a group, or to set the Global policy instance.
+
+## EXAMPLES
+
+### Example 1
+```
+Grant-CsTeamsPersonalAttendantPolicy -identity user1@contoso.com -PolicyName SalesPersonalAttendantPolicy
+```
+
+Assigns the TeamsPersonalAttendantPolicy called "SalesPersonalAttendantPolicy" to user1@contoso.com
+
+### Example 2
+```
+Grant-CsTeamsPersonalAttendantPolicy -Global -PolicyName SalesPersonalAttendantPolicy
+```
+
+Assigns the TeamsPersonalAttendantPolicy called "SalesPersonalAttendantPolicy" to the Global policy instance. This sets the parameters in the Global policy instance to the values found
+in the SalesPersonalAttendantPolicy instance.
+
+### Example 3
+```
+Grant-CsTeamsPersonalAttendantPolicy -Group sales@contoso.com -Rank 10 -PolicyName SalesPersonalAttendantPolicy
+```
+
+Assigns the TeamsPersonalAttendantPolicy called "SalesPersonalAttendantPolicy" to the members of the group sales@contoso.com.
+
+## PARAMETERS
+
+### -Identity
+The user object to whom the policy is being assigned.
+
+```yaml
+Type: String
+Parameter Sets: (Identity)
+Aliases:
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -PolicyName
+The name of the policy being assigned. To remove an existing user level policy assignment, specify PolicyName as $null.
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -PassThru
+Enables you to pass a user object through the pipeline that represents the user being assigned the policy. By default, the Grant-CsTeamsPersonalAttendantPolicy cmdlet does not pass objects through the pipeline.
+
+```yaml
+Type: SwitchParameter
+Parameter Sets: (All)
+Aliases:
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -Global
+Sets the parameters of the Global policy instance to the values in the specified policy instance.
+
+```yaml
+Type: SwitchParameter
+Parameter Sets: (GrantToTenant)
+Aliases:
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -Group
+Specifies the group used for the group policy assignment.
+
+```yaml
+Type: String
+Parameter Sets: (GrantToGroup)
+Aliases:
+
+Required: True
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -Rank
+The rank of the policy assignment, relative to other group policy assignments for the same policy type.
+
+```yaml
+Type: Int32
+Parameter Sets: (GrantToGroup)
+Aliases:
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### CommonParameters
+This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).
+
+## INPUTS
+
+### None
+
+## OUTPUTS
+
+### System.Object
+
+## NOTES
+
+The cmdlet is available in Teams PowerShell module 7.2.1-preview or later.
+
+## RELATED LINKS
+
+[New-CsTeamsPersonalAttendantPolicy](./new-csteamspersonalattendantpolicy.md)
+
+[Set-CsTeamsPersonalAttendantPolicy](./set-csteamspersonalattendantpolicy.md)
+
+[Get-CsTeamsPersonalAttendantPolicy](./get-csteamspersonalattendantpolicy.md)
+
+[Remove-CsTeamsPersonalAttendantPolicy](./remove-csteamspersonalattendantpolicy.md)

From 386d36a6e636ca75e7e425c49721e9fb666732a8 Mon Sep 17 00:00:00 2001
From: Chris Davis <chris.davis@microsoft.com>
Date: Wed, 6 Aug 2025 10:21:01 -0700
Subject: [PATCH 115/145] Acrolinx 14

---
 .../ExchangePowerShell/Set-LinkedUser.md      |   2 +-
 .../Set-M365DataAtRestEncryptionPolicy.md     |   6 +-
 ...365DataAtRestEncryptionPolicyAssignment.md |   2 +-
 .../ExchangePowerShell/Set-MailContact.md     |  36 +--
 .../Set-MailPublicFolder.md                   |  28 +--
 .../ExchangePowerShell/Set-MailUser.md        |  46 ++--
 .../ExchangePowerShell/Set-Mailbox.md         | 138 ++++++------
 .../Set-MailboxAuditBypassAssociation.md      |   6 +-
 .../Set-MailboxAutoReplyConfiguration.md      |  16 +-
 .../Set-MailboxCalendarConfiguration.md       |  56 ++---
 .../Set-MailboxCalendarFolder.md              |  14 +-
 .../ExchangePowerShell/Set-MailboxDatabase.md |  50 ++--
 .../Set-MailboxDatabaseCopy.md                |   6 +-
 .../Set-MailboxExportRequest.md               |  10 +-
 .../Set-MailboxFolderPermission.md            |  14 +-
 .../Set-MailboxIRMAccess.md                   |   2 +-
 .../Set-MailboxImportRequest.md               |  12 +-
 .../Set-MailboxJunkEmailConfiguration.md      |  10 +-
 .../Set-MailboxMessageConfiguration.md        |  32 +--
 .../ExchangePowerShell/Set-MailboxPlan.md     |  24 +-
 .../Set-MailboxRegionalConfiguration.md       |   8 +-
 .../Set-MailboxRestoreRequest.md              |  12 +-
 .../ExchangePowerShell/Set-MailboxSearch.md   |  20 +-
 .../Set-MailboxSentItemsConfiguration.md      |   6 +-
 .../ExchangePowerShell/Set-MailboxServer.md   | 107 ++++-----
 .../Set-MailboxSpellingConfiguration.md       |   4 +-
 .../Set-MailboxTransportService.md            |  34 +--
 .../Set-MalwareFilterPolicy.md                |  24 +-
 .../Set-MalwareFilterRule.md                  |   4 +-
 .../Set-MalwareFilteringServer.md             |   6 +-
 .../Set-ManagedContentSettings.md             |   2 +-
 .../ExchangePowerShell/Set-ManagedFolder.md   |   4 +-
 .../Set-ManagedFolderMailboxPolicy.md         |   2 +-
 .../Set-ManagementRoleAssignment.md           |   4 +-
 .../Set-ManagementRoleEntry.md                |   6 +-
 .../ExchangePowerShell/Set-ManagementScope.md |   6 +-
 .../Set-MapiVirtualDirectory.md               |  10 +-
 .../Set-MessageClassification.md              |  12 +-
 .../ExchangePowerShell/Set-MigrationBatch.md  |  30 +--
 .../ExchangePowerShell/Set-MigrationConfig.md |   4 +-
 .../Set-MigrationEndpoint.md                  |   8 +-
 .../ExchangePowerShell/Set-MigrationUser.md   |  14 +-
 .../Set-MobileDeviceMailboxPolicy.md          |   8 +-
 .../ExchangePowerShell/Set-MoveRequest.md     |  22 +-
 .../ExchangePowerShell/Set-Notification.md    |   6 +-
 .../Set-OMEConfiguration.md                   |  12 +-
 .../Set-OMEMessageRevocation.md               |  10 +-
 .../Set-OabVirtualDirectory.md                |  16 +-
 .../Set-OfflineAddressBook.md                 |  10 +-
 .../Set-OnPremisesOrganization.md             |   6 +-
 .../Set-OrganizationConfig.md                 | 137 +++++------
 .../Set-OrganizationRelationship.md           |  26 +--
 .../Set-OutboundConnector.md                  |  28 +--
 .../ExchangePowerShell/Set-OutlookAnywhere.md |  24 +-
 .../Set-OutlookProtectionRule.md              |   4 +-
 .../ExchangePowerShell/Set-OutlookProvider.md |   4 +-
 .../Set-OwaMailboxPolicy.md                   | 213 +++++++++---------
 .../Set-OwaVirtualDirectory.md                | 188 ++++++++--------
 .../Set-PartnerApplication.md                 |   4 +-
 .../Set-PendingFederatedDomain.md             |   2 +-
 .../Set-PhishSimOverridePolicy.md             |   4 +-
 .../ExchangePowerShell/Set-Place.md           |   6 +-
 .../ExchangePowerShell/Set-PolicyConfig.md    |   8 +-
 .../ExchangePowerShell/Set-PolicyTipConfig.md |   4 +-
 .../ExchangePowerShell/Set-PopSettings.md     |  30 +--
 .../Set-PowerShellVirtualDirectory.md         |  14 +-
 .../ExchangePowerShell/Set-ProtectionAlert.md |  16 +-
 .../ExchangePowerShell/Set-PublicFolder.md    |  10 +-
 .../Set-PublicFolderDatabase.md               |  12 +-
 .../Set-PublicFolderMigrationRequest.md       |   6 +-
 .../Set-PublicFolderMoveRequest.md            |   6 +-
 .../Set-QuarantinePermissions.md              |  14 +-
 .../Set-QuarantinePolicy.md                   |   8 +-
 .../ExchangePowerShell/Set-RMSTemplate.md     |   2 +-
 .../Set-ReceiveConnector.md                   |  58 ++---
 .../Set-RecipientFilterConfig.md              |   2 +-
 ...-RecordReviewNotificationTemplateConfig.md |   4 +-
 .../Set-RegulatoryComplianceUI.md             |   2 +-
 .../ExchangePowerShell/Set-RemoteDomain.md    |  50 ++--
 .../ExchangePowerShell/Set-RemoteMailbox.md   |  32 +--
 .../Set-ReportSubmissionPolicy.md             |  10 +-
 .../Set-ReportSubmissionRule.md               |   2 +-
 .../ExchangePowerShell/Set-ResourceConfig.md  |   4 +-
 .../ExchangePowerShell/Set-ResubmitRequest.md |   2 +-
 .../Set-RetentionCompliancePolicy.md          |  12 +-
 .../Set-RetentionComplianceRule.md            |   6 +-
 .../ExchangePowerShell/Set-RetentionPolicy.md |   8 +-
 .../Set-RetentionPolicyTag.md                 |  10 +-
 .../Set-RoleAssignmentPolicy.md               |   4 +-
 .../ExchangePowerShell/Set-RoleGroup.md       |   4 +-
 .../Set-RoutingGroupConnector.md              |   2 +-
 .../ExchangePowerShell/Set-RpcClientAccess.md |   6 +-
 .../Set-SafeAttachmentPolicy.md               |   8 +-
 .../Set-SafeAttachmentRule.md                 |   2 +-
 .../ExchangePowerShell/Set-SafeLinksPolicy.md |  22 +-
 .../ExchangePowerShell/Set-SafeLinksRule.md   |   2 +-
 .../Set-SearchDocumentFormat.md               |   2 +-
 97 files changed, 977 insertions(+), 974 deletions(-)

diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-LinkedUser.md b/exchange/exchange-ps/ExchangePowerShell/Set-LinkedUser.md
index 63c3c474f2..5b19885817 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-LinkedUser.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-LinkedUser.md
@@ -32,7 +32,7 @@ Set-LinkedUser [-Identity] <UserIdParameter>
 ## DESCRIPTION
 The OLSync service account is the only linked user in your organization. By default, the account is named GALSync-ServiceAccount.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-M365DataAtRestEncryptionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-M365DataAtRestEncryptionPolicy.md
index ef3f52b177..4d44abfb09 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-M365DataAtRestEncryptionPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-M365DataAtRestEncryptionPolicy.md
@@ -46,7 +46,7 @@ Set-M365DataAtRestEncryptionPolicy [-Identity] <DataEncryptionPolicyIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -62,7 +62,7 @@ This example disabled the Microsoft 365 data-at-rest encryption policy named Ten
 Set-M365DataAtRestEncryptionPolicy -Identity "Tenant Default Policy" -Refresh
 ```
 
-This example updates the Microsoft 365 data-at-rest encryption policy named Tenant Default Policy after one of the associated keys has been rotated in the Azure Key Vault.
+This example updates the Microsoft 365 data-at-rest encryption policy named Tenant Default Policy after one of the associated keys is rotated in the Azure Key Vault.
 
 ## PARAMETERS
 
@@ -151,7 +151,7 @@ Accept wildcard characters: False
 
 The Enabled parameter specifies whether the policy is enabled or disabled. Valid values are:
 
-- $true: The policy is enabled. This is the default value.
+- $true: The policy is enabled. This value is the default.
 - $false: The policy is disabled.
 
 ```yaml
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-M365DataAtRestEncryptionPolicyAssignment.md b/exchange/exchange-ps/ExchangePowerShell/Set-M365DataAtRestEncryptionPolicyAssignment.md
index b33473efcb..321d855a48 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-M365DataAtRestEncryptionPolicyAssignment.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-M365DataAtRestEncryptionPolicyAssignment.md
@@ -26,7 +26,7 @@ Set-M365DataAtRestEncryptionPolicyAssignment -DataEncryptionPolicy <DataEncrypti
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailContact.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailContact.md
index 5d26ad05db..35488447ff 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-MailContact.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailContact.md
@@ -13,7 +13,7 @@ title: Set-MailContact
 # Set-MailContact
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-MailContact cmdlet to modify existing mail contacts.
 
@@ -93,7 +93,7 @@ Set-MailContact [-Identity] <MailContactIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -367,7 +367,7 @@ This parameter is available only in on-premises Exchange.
 
 The CreateDTMFMap parameter specifies whether to create a dual-tone multiple-frequency (DTMF) map for the recipient. This allows the recipient to be identified by using a telephone keypad in Unified Messaging (UM) environments. Valid values are:
 
-- $true: A DTMF map is created for the recipient. This is the default value.
+- $true: A DTMF map is created for the recipient. This value is the default.
 - $false: A DTMF map isn't created for the recipient.
 
 ```yaml
@@ -737,7 +737,7 @@ This parameter is available only in on-premises Exchange.
 
 The EmailAddressPolicyEnabled parameter specifies whether to apply email address policies to this recipient. Valid values are:
 
-- $true: Email address policies are applied to this recipient. This is the default value.
+- $true: Email address policies are applied to this recipient. This value is the default.
 - $false: Email address policies aren't applied to this recipient.
 
 ```yaml
@@ -762,7 +762,7 @@ To enter multiple values that overwrite any existing entries, use the following
 
 To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`.
 
-Although this is a multivalued property, the filter `"ExtensionCustomAttribute1 -eq 'Value'"` will return a match if the property _contains_ the specified value.
+Although this is a multivalued property, the filter `"ExtensionCustomAttribute1 -eq 'Value'"` returns a match if the property _contains_ the specified value.
 
 ```yaml
 Type: MultiValuedProperty
@@ -786,7 +786,7 @@ To enter multiple values that overwrite any existing entries, use the following
 
 To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`.
 
-Although this is a multivalued property, the filter `"ExtensionCustomAttribute2 -eq 'Value'"` will return a match if the property _contains_ the specified value.
+Although this is a multivalued property, the filter `"ExtensionCustomAttribute2 -eq 'Value'"` returns a match if the property _contains_ the specified value.
 
 ```yaml
 Type: MultiValuedProperty
@@ -810,7 +810,7 @@ To enter multiple values that overwrite any existing entries, use the following
 
 To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`.
 
-Although this is a multivalued property, the filter `"ExtensionCustomAttribute3 -eq 'Value'"` will return a match if the property _contains_ the specified value.
+Although this is a multivalued property, the filter `"ExtensionCustomAttribute3 -eq 'Value'"` returns a match if the property _contains_ the specified value.
 
 ```yaml
 Type: MultiValuedProperty
@@ -834,7 +834,7 @@ To enter multiple values that overwrite any existing entries, use the following
 
 To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`.
 
-Although this is a multivalued property, the filter `"ExtensionCustomAttribute4 -eq 'Value'"` will return a match if the property _contains_ the specified value.
+Although this is a multivalued property, the filter `"ExtensionCustomAttribute4 -eq 'Value'"` returns a match if the property _contains_ the specified value.
 
 ```yaml
 Type: MultiValuedProperty
@@ -858,7 +858,7 @@ To enter multiple values that overwrite any existing entries, use the following
 
 To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`.
 
-Although this is a multivalued property, the filter `"ExtensionCustomAttribute5 -eq 'Value'"` will return a match if the property _contains_ the specified value.
+Although this is a multivalued property, the filter `"ExtensionCustomAttribute5 -eq 'Value'"` returns a match if the property _contains_ the specified value.
 
 ```yaml
 Type: MultiValuedProperty
@@ -956,7 +956,7 @@ Accept wildcard characters: False
 The HiddenFromAddressListsEnabled parameter specifies whether this recipient is visible in address lists. Valid values are:
 
 - $true: The recipient isn't visible in address lists.
-- $false: The recipient is visible in address lists. This is the default value.
+- $false: The recipient is visible in address lists. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -1001,7 +1001,7 @@ Accept wildcard characters: False
 
 The MacAttachmentFormat parameter specifies the Apple Macintosh operating system attachment format to use for messages sent to the mail contact or mail user. Valid values are:
 
-- BinHex (This is the default value)
+- BinHex (default value)
 - UuEncode
 - AppleSingle
 - AppleDouble
@@ -1087,7 +1087,7 @@ When you enter a value, qualify the value with one of the following units:
 - MB (megabytes)
 - GB (gigabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 A valid value is a number up to 1.999999 gigabytes (2147483647 bytes) or the value unlimited. The default value is unlimited.
 
@@ -1146,7 +1146,7 @@ When you enter a value, qualify the value with one of the following units:
 - MB (megabytes)
 - GB (gigabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 A valid value is a number up to 1.999999 gigabytes (2147483647 bytes) or the value unlimited. The default value is unlimited.
 
@@ -1174,7 +1174,7 @@ The MessageBodyFormat parameter specifies the message body format for messages s
 
 - Text
 - Html
-- TextAndHtml (This is the default value)
+- TextAndHtml (default value)
 
 The MessageFormat and MessageBodyFormat parameters are interdependent:
 
@@ -1200,7 +1200,7 @@ Accept wildcard characters: False
 The MessageFormat parameter specifies the message format for messages sent to the mail contact or mail user. Valid values are:
 
 - Text
-- Mime (This is the default value)
+- Mime (default value)
 
 The MessageFormat and MessageBodyFormat parameters are interdependent:
 
@@ -1259,7 +1259,7 @@ Accept wildcard characters: False
 The ModerationEnabled parameter specifies whether moderation is enabled for this recipient. Valid value are:
 
 - $true: Moderation is enabled for this recipient. Messages sent to this recipient must be approved by a moderator before the messages are delivered.
-- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This is the default value.
+- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This value is the default.
 
 You use the ModeratedBy parameter to specify the moderators.
 
@@ -1537,7 +1537,7 @@ Accept wildcard characters: False
 
 The SendModerationNotifications parameter specifies when moderation notification messages are sent. Valid values are:
 
-- Always: Notify all senders when their messages aren't approved. This is the default value.
+- Always: Notify all senders when their messages aren't approved. This value is the default.
 - Internal: Notify senders in the organization when their messages aren't approved.
 - Never: Don't notify anyone when a message isn't approved.
 
@@ -1642,7 +1642,7 @@ Accept wildcard characters: False
 The UsePreferMessageFormat specifies whether the message format settings configured for the mail user or mail contact override the global settings configured for the remote domain or configured by the message sender. Valid value are:
 
 - $true: Messages sent to the mail user or mail contact use the message format that's configured for the mail user or mail contact.
-- $false: Messages sent to the mail user or mail contact use the message format that's configured for the remote domain (the default remote domain or a specific remote domain) or configured by the message sender. This is the default value.
+- $false: Messages sent to the mail user or mail contact use the message format that's configured for the remote domain (the default remote domain or a specific remote domain) or configured by the message sender. This value is the default.
 
 ```yaml
 Type: Boolean
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailPublicFolder.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailPublicFolder.md
index 7b5cf8c9e7..08ae62604e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-MailPublicFolder.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailPublicFolder.md
@@ -13,7 +13,7 @@ title: Set-MailPublicFolder
 # Set-MailPublicFolder
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-MailPublicFolder cmdlet to configure the mail-related settings of mail-enabled public folders. If you want to configure basic settings that aren't mail-related, use the Set-PublicFolder cmdlet.
 
@@ -91,7 +91,7 @@ Set-MailPublicFolder [-Identity] <MailPublicFolderIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -791,7 +791,7 @@ Accept wildcard characters: False
 
 The EmailAddressPolicyEnabled parameter specifies whether to apply email address policies to this recipient. Valid values are:
 
-- $true: Email address policies are applied to this recipient. This is the default value.
+- $true: Email address policies are applied to this recipient. This value is the default.
 - $false: Email address policies aren't applied to this recipient.
 
 ```yaml
@@ -834,7 +834,7 @@ To enter multiple values that overwrite any existing entries, use the following
 
 To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`.
 
-Although this is a multivalued property, the filter `"ExtensionCustomAttribute1 -eq 'Value'"` will return a match if the property _contains_ the specified value.
+Although this is a multivalued property, the filter `"ExtensionCustomAttribute1 -eq 'Value'"` returns a match if the property _contains_ the specified value.
 
 ```yaml
 Type: MultiValuedProperty
@@ -858,7 +858,7 @@ To enter multiple values that overwrite any existing entries, use the following
 
 To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`.
 
-Although this is a multivalued property, the filter `"ExtensionCustomAttribute2 -eq 'Value'"` will return a match if the property _contains_ the specified value.
+Although this is a multivalued property, the filter `"ExtensionCustomAttribute2 -eq 'Value'"` returns a match if the property _contains_ the specified value.
 
 ```yaml
 Type: MultiValuedProperty
@@ -882,7 +882,7 @@ To enter multiple values that overwrite any existing entries, use the following
 
 To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`.
 
-Although this is a multivalued property, the filter `"ExtensionCustomAttribute3 -eq 'Value'"` will return a match if the property _contains_ the specified value.
+Although this is a multivalued property, the filter `"ExtensionCustomAttribute3 -eq 'Value'"` returns a match if the property _contains_ the specified value.
 
 ```yaml
 Type: MultiValuedProperty
@@ -906,7 +906,7 @@ To enter multiple values that overwrite any existing entries, use the following
 
 To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`.
 
-Although this is a multivalued property, the filter `"ExtensionCustomAttribute4 -eq 'Value'"` will return a match if the property _contains_ the specified value.
+Although this is a multivalued property, the filter `"ExtensionCustomAttribute4 -eq 'Value'"` returns a match if the property _contains_ the specified value.
 
 ```yaml
 Type: MultiValuedProperty
@@ -930,7 +930,7 @@ To enter multiple values that overwrite any existing entries, use the following
 
 To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`.
 
-Although this is a multivalued property, the filter `"ExtensionCustomAttribute5 -eq 'Value'"` will return a match if the property _contains_ the specified value.
+Although this is a multivalued property, the filter `"ExtensionCustomAttribute5 -eq 'Value'"` returns a match if the property _contains_ the specified value.
 
 ```yaml
 Type: MultiValuedProperty
@@ -1038,7 +1038,7 @@ Accept wildcard characters: False
 The HiddenFromAddressListsEnabled parameter specifies whether this recipient is visible in address lists. Valid values are:
 
 - $true: The recipient isn't visible in address lists.
-- $false: The recipient is visible in address lists. This is the default value.
+- $false: The recipient is visible in address lists. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -1082,7 +1082,7 @@ Accept wildcard characters: False
 The IgnoreMissingFolderLink parameter specifies whether to exclude the mail-enabled public folder from a specific validation check that's used during a public folder migration. Valid values are:
 
 - $true: Skip the validation check. If the Active Directory object for the mail-enabled public folder doesn't have EntryId or ContentMailbox property values, the public folder is ignored, and the public folder migration can continue.
-- $false: Don't skip the validation check. If the Active Directory object for the mail-enabled public folder doesn't have EntryId or ContentMailbox property values, the entire public folder migration will fail. This is the default value.
+- $false: Don't skip the validation check. If the Active Directory object for the mail-enabled public folder doesn't have EntryId or ContentMailbox property values, the entire public folder migration will fail. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -1158,7 +1158,7 @@ When you enter a value, qualify the value with one of the following units:
 - MB (megabytes)
 - GB (gigabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 A valid value is a number up to 1.999999 gigabytes (2147483647 bytes) or the value unlimited. The default value is unlimited, which indicates the maximum size is imposed elsewhere (for example, organization, server, or connector limits).
 
@@ -1189,7 +1189,7 @@ When you enter a value, qualify the value with one of the following units:
 - MB (megabytes)
 - GB (gigabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 A valid value is a number up to 1.999999 gigabytes (2147483647 bytes) or the value unlimited. The default value is unlimited, which indicates the maximum size is imposed elsewhere (for example, organization, server, or connector limits).
 
@@ -1245,7 +1245,7 @@ Accept wildcard characters: False
 The ModerationEnabled parameter specifies whether moderation is enabled for this recipient. Valid value are:
 
 - $true: Moderation is enabled for this recipient. Messages sent to this recipient must be approved by a moderator before the messages are delivered.
-- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This is the default value.
+- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This value is the default.
 
 You use the ModeratedBy parameter to specify the moderators.
 
@@ -1494,7 +1494,7 @@ Accept wildcard characters: False
 
 The SendModerationNotifications parameter specifies when moderation notification messages are sent. Valid values are:
 
-- Always: Notify all senders when their messages aren't approved. This is the default value.
+- Always: Notify all senders when their messages aren't approved. This value is the default.
 - Internal: Notify senders in the organization when their messages aren't approved.
 - Never: Don't notify anyone when a message isn't approved.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailUser.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailUser.md
index ffe35144e9..8ecd9e7617 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-MailUser.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailUser.md
@@ -13,7 +13,7 @@ title: Set-MailUser
 # Set-MailUser
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-MailUser cmdlet to modify mail users. Mail users (also known as mail-enabled users) have email addresses and accounts in the Exchange organization, but they don't have Exchange mailboxes.
 
@@ -945,7 +945,7 @@ Set-MailUser [-Identity] <MailUserIdParameter> [-UnblockForwardSyncPostCrossTena
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -954,7 +954,7 @@ You need to be assigned permissions before you can run this cmdlet. Although thi
 Set-MailUser -Identity "John Woods" -ExternalEmailAddress john@tailspintoys.com
 ```
 
-This example modifies the external email address for the mail user named John Woods. Note that the original external email address isn't kept as a proxy address.
+This example modifies the external email address for the mail user named John Woods. The original external email address isn't kept as a proxy address.
 
 ## PARAMETERS
 
@@ -1257,7 +1257,7 @@ This parameter is available only in on-premises Exchange.
 
 The CreateDTMFMap parameter specifies whether to create a dual-tone multiple-frequency (DTMF) map for the recipient. This allows the recipient to be identified by using a telephone keypad in Unified Messaging (UM) environments. Valid values are:
 
-- $true: A DTMF map is created for the recipient. This is the default value.
+- $true: A DTMF map is created for the recipient. This value is the default.
 - $false: A DTMF map isn't created for the recipient.
 
 ```yaml
@@ -1653,7 +1653,7 @@ This parameter is available only in on-premises Exchange.
 
 The EmailAddressPolicyEnabled parameter specifies whether to apply email address policies to this recipient. Valid values are:
 
-- $true: Email address policies are applied to this recipient. This is the default value.
+- $true: Email address policies are applied to this recipient. This value is the default.
 - $false: Email address policies aren't applied to this recipient.
 
 ```yaml
@@ -1764,7 +1764,7 @@ To enter multiple values that overwrite any existing entries, use the following
 
 To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`.
 
-Although this is a multivalued property, the filter `"ExtensionCustomAttribute1 -eq 'Value'"` will return a match if the property _contains_ the specified value.
+Although this is a multivalued property, the filter `"ExtensionCustomAttribute1 -eq 'Value'"` returns a match if the property _contains_ the specified value.
 
 ```yaml
 Type: MultiValuedProperty
@@ -1788,7 +1788,7 @@ To enter multiple values that overwrite any existing entries, use the following
 
 To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`.
 
-Although this is a multivalued property, the filter `"ExtensionCustomAttribute2 -eq 'Value'"` will return a match if the property _contains_ the specified value.
+Although this is a multivalued property, the filter `"ExtensionCustomAttribute2 -eq 'Value'"` returns a match if the property _contains_ the specified value.
 
 ```yaml
 Type: MultiValuedProperty
@@ -1812,7 +1812,7 @@ To enter multiple values that overwrite any existing entries, use the following
 
 To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`.
 
-Although this is a multivalued property, the filter `"ExtensionCustomAttribute3 -eq 'Value'"` will return a match if the property _contains_ the specified value.
+Although this is a multivalued property, the filter `"ExtensionCustomAttribute3 -eq 'Value'"` returns a match if the property _contains_ the specified value.
 
 ```yaml
 Type: MultiValuedProperty
@@ -1836,7 +1836,7 @@ To enter multiple values that overwrite any existing entries, use the following
 
 To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`.
 
-Although this is a multivalued property, the filter `"ExtensionCustomAttribute4 -eq 'Value'"` will return a match if the property _contains_ the specified value.
+Although this is a multivalued property, the filter `"ExtensionCustomAttribute4 -eq 'Value'"` returns a match if the property _contains_ the specified value.
 
 ```yaml
 Type: MultiValuedProperty
@@ -1860,7 +1860,7 @@ To enter multiple values that overwrite any existing entries, use the following
 
 To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`.
 
-Although this is a multivalued property, the filter `"ExtensionCustomAttribute5 -eq 'Value'"` will return a match if the property _contains_ the specified value.
+Although this is a multivalued property, the filter `"ExtensionCustomAttribute5 -eq 'Value'"` returns a match if the property _contains_ the specified value.
 
 ```yaml
 Type: MultiValuedProperty
@@ -1978,7 +1978,7 @@ Accept wildcard characters: False
 The HiddenFromAddressListsEnabled parameter specifies whether this recipient is visible in address lists. Valid values are:
 
 - $true: The recipient isn't visible in address lists.
-- $false: The recipient is visible in address lists. This is the default value.
+- $false: The recipient is visible in address lists. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -2103,7 +2103,7 @@ Accept wildcard characters: False
 
 The MacAttachmentFormat parameter specifies the Apple Macintosh operating system attachment format to use for messages sent to the mail contact or mail user. Valid values are:
 
-- BinHex (This is the default value)
+- BinHex (default value)
 - UuEncode
 - AppleSingle
 - AppleDouble
@@ -2207,7 +2207,7 @@ When you enter a value, qualify the value with one of the following units:
 - MB (megabytes)
 - GB (gigabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 A valid value is a number up to 1.999999 gigabytes (2147483647 bytes) or the value unlimited. The default value is unlimited, which indicates the maximum size is imposed elsewhere (for example, organization, server, or connector limits).
 
@@ -2238,7 +2238,7 @@ When you enter a value, qualify the value with one of the following units:
 - MB (megabytes)
 - GB (gigabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 A valid value is a number up to 1.999999 gigabytes (2147483647 bytes) or the value unlimited. The default value is unlimited, which indicates the maximum size is imposed elsewhere (for example, organization, server, or connector limits).
 
@@ -2264,7 +2264,7 @@ The MessageBodyFormat parameter specifies the message body format for messages s
 
 - Text
 - Html
-- TextAndHtml (This is the default value)
+- TextAndHtml (default value)
 
 The MessageFormat and MessageBodyFormat parameters are interdependent:
 
@@ -2290,7 +2290,7 @@ Accept wildcard characters: False
 The MessageFormat parameter specifies the message format for messages sent to the mail contact or mail user. Valid values are:
 
 - Text
-- Mime (This is the default value)
+- Mime (default value)
 
 The MessageFormat and MessageBodyFormat parameters are interdependent:
 
@@ -2369,7 +2369,7 @@ Accept wildcard characters: False
 The ModerationEnabled parameter specifies whether moderation is enabled for this recipient. Valid value are:
 
 - $true: Moderation is enabled for this recipient. Messages sent to this recipient must be approved by a moderator before the messages are delivered.
-- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This is the default value.
+- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This value is the default.
 
 You use the ModeratedBy parameter to specify the moderators.
 
@@ -2515,7 +2515,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 A valid value is number up to 1.999999999 terabytes (2199023254528 bytes) or the value unlimited. The default value is 30 gigabytes (32212254720 bytes).
 
@@ -2549,7 +2549,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 A valid value is number up to 1.999999999 terabytes (2199023254528 bytes) or the value unlimited. The default value is 20 gigabytes (21474836480 bytes).
 
@@ -2890,7 +2890,7 @@ This parameter is available only in the cloud-based service.
 The ResetPasswordOnNextLogon parameter allows users to require themselves to change their password the next time they log on. Valid values are:
 
 - $true: The user is required to change their password then next time they successfully log on.
-- $false: The user isn't required to change their password then next time they successfully log on. This is the default value.
+- $false: The user isn't required to change their password then next time they successfully log on. This value is the default.
 
 You can't use this parameter to require another user to change their password (the parameter is available only via the MyBaseOptions user role). You need to use the ForceChangePasswordNextSignIn value in the PasswordProfile parameter on the [Update-MgUser](https://learn.microsoft.com/powershell/module/microsoft.graph.users/update-mguser) cmdlet in Microsoft Graph PowerShell.
 
@@ -2912,7 +2912,7 @@ Accept wildcard characters: False
 
 This parameter is available only in on-premises Exchange.
 
-The SamAccountName parameter (also known as the pre-Windows 2000 user account or group name) specifies an object identifier that's compatible with older versions of Microsoft Windows client and server operating systems. The value can contain letters, numbers, spaces, periods (.), and the following characters: !, #, $, %, ^, &, -, \_, {, }, and ~. The last character can't be a period. Unicode characters are allowed, but accented characters may generate collisions (for example, o and ö match). The maximum length is 20 characters.
+The SamAccountName parameter (also known as the pre-Windows 2000 user account or group name) specifies an object identifier that's compatible with older versions of Microsoft Windows client and server operating systems. The value can contain letters, numbers, spaces, periods (.), and the following characters: !, #, $, %, ^, &, -, \_, {, }, and ~. The last character can't be a period. Unicode characters are allowed, but accented characters might generate collisions (for example, o and ö match). The maximum length is 20 characters.
 
 ```yaml
 Type: String
@@ -2972,7 +2972,7 @@ Accept wildcard characters: False
 
 The SendModerationNotifications parameter specifies when moderation notification messages are sent. Valid values are:
 
-- Always: Notify all senders when their messages aren't approved. This is the default value.
+- Always: Notify all senders when their messages aren't approved. This value is the default.
 - Internal: Notify senders in the organization when their messages aren't approved.
 - Never: Don't notify anyone when a message isn't approved.
 
@@ -3117,7 +3117,7 @@ Accept wildcard characters: False
 The UsePreferMessageFormat specifies whether the message format settings configured for the mail user or mail contact override the global settings configured for the remote domain or configured by the message sender. Valid value are:
 
 - $true: Messages sent to the mail user or mail contact use the message format that's configured for the mail user or mail contact.
-- $false: Messages sent to the mail user or mail contact use the message format that's configured for the remote domain (the default remote domain or a specific remote domain) or configured by the message sender. This is the default value.
+- $false: Messages sent to the mail user or mail contact use the message format that's configured for the remote domain (the default remote domain or a specific remote domain) or configured by the message sender. This value is the default.
 
 ```yaml
 Type: Boolean
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-Mailbox.md b/exchange/exchange-ps/ExchangePowerShell/Set-Mailbox.md
index b4a48bfc93..0af9d1bc47 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-Mailbox.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-Mailbox.md
@@ -13,7 +13,7 @@ title: Set-Mailbox
 # Set-Mailbox
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-Mailbox cmdlet to modify the settings of existing mailboxes.
 
@@ -1124,7 +1124,7 @@ Set-Mailbox [-Identity] <MailboxIdParameter>
 ## DESCRIPTION
 You can use this cmdlet for one mailbox at a time. To perform bulk management, you can pipeline the output of various Get- cmdlets (for example, the Get-Mailbox or Get-User cmdlets) and configure several mailboxes in a single-line command. You can also use the Set-Mailbox cmdlet in scripts.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -1418,7 +1418,7 @@ This parameter is available only in on-premises Exchange.
 The AntispamBypassEnabled parameter specifies whether to skip anti-spam processing on the mailbox. Valid values are:
 
 - $true: Anti-spam processing is skipped on the mailbox.
-- $false: Anti-spam processing occurs on the mailbox. This is the default value
+- $false: Anti-spam processing occurs on the mailbox. This value is the default
 
 ```yaml
 Type: Boolean
@@ -1597,7 +1597,7 @@ A valid value is a number up to 1.999999999 terabytes (2199023254528 bytes) or t
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The ArchiveQuota value must be greater than or equal to the ArchiveWarningQuota value.
 
@@ -1649,7 +1649,7 @@ A valid value is a number up to 1.999999999 terabytes (2199023254528 bytes) or t
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The ArchiveWarningQuota value must be less than or equal to the ArchiveQuota value.
 
@@ -1698,7 +1698,7 @@ The AuditAdmin parameter specifies the mailbox operations to log for administrat
 - Create (Enabled by default.)
 - FolderBind (Enabled by default in on-premises Exchange 2010 or later.)
 - HardDelete (Enabled by default.)
-- MessageBind (This has been deprecated in the cloud-based service.)
+- MessageBind (This is deprecated in the cloud-based service.)
 - ModifyFolderPermissions (Available only in Exchange 2019 and the cloud-based service.)
 - Move (Enabled by default in on-premises Exchange 2010 or later.)
 - MoveToDeletedItems (Enabled by default.)
@@ -1779,7 +1779,7 @@ Accept wildcard characters: False
 The AuditEnabled parameter specifies whether to enable or disable mailbox audit logging for the mailbox. If auditing is enabled, actions specified in the AuditAdmin, AuditDelegate, and AuditOwner parameters are logged. Valid values are:
 
 - $true: Mailbox audit logging is enabled.
-- $false: Mailbox audit logging is disabled. This is the default value.
+- $false: Mailbox audit logging is disabled. This value is the default.
 
 **Note**: In Exchange Online, mailbox auditing on by default was enabled for all organizations in January, 2019. For more information, see [Manage mailbox auditing](https://learn.microsoft.com/purview/audit-mailboxes).
 
@@ -1847,7 +1847,7 @@ Accept wildcard characters: False
 
 The AuditOwner parameter specifies the mailbox operations to log for mailbox owners as part of mailbox audit logging. Valid values include:
 
-- None (This is the default value in Exchange 2010, Exchange 2013, and Exchange 2016.)
+- None (This value is the default in Exchange 2010, Exchange 2013, and Exchange 2016.)
 - AddFolderPermissions (Available only in Exchange 2019 and the cloud-based service.)
 - ApplyRecord (Available only in the cloud-based service.)
 - Create
@@ -1959,7 +1959,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value of this parameter must be less than or equal to the value of the RecoverableItemsQuota parameter.
 
@@ -1984,7 +1984,7 @@ Accept wildcard characters: False
 The CalendarRepairDisabled parameter specifies whether to prevent calendar items in the mailbox from being repaired by the Calendar Repair Assistant. Valid values are:
 
 - $true: The Calendar Repair Assistant doesn't repair calendar items in the mailbox.
-- $false: The Calendar Repair Assistant repairs calendars items in the mailbox. This is the default value.
+- $false: The Calendar Repair Assistant repairs calendars items in the mailbox. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -2005,7 +2005,7 @@ Accept wildcard characters: False
 The CalendarVersionStoreDisabled parameter specifies whether to prevent calendar changes in the mailbox from being logged. Valid values are:
 
 - $true: Changes to a calendar item aren't recorded.
-- $false: Changes to a calendar item are recorded. This keeps older versions of meetings and appointments. This is the default value.
+- $false: Changes to a calendar item are recorded. This keeps older versions of meetings and appointments. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -2047,7 +2047,7 @@ Accept wildcard characters: False
 
 This parameter is available only in on-premises Exchange.
 
-The ClientExtensions parameter specifies whether the organization-wide client extensions (also called Apps for Outlook) will be installed in the arbitration mailbox (also called the organization mailbox). Only one arbitration mailbox in the organization can be configured to store client extensions. You can use this parameter only on an arbitration mailbox.
+The ClientExtensions parameter specifies whether the organization-wide client extensions (also called Apps for Outlook) are installed in the arbitration mailbox (also called the organization mailbox). Only one arbitration mailbox in the organization can be configured to store client extensions. You can use this parameter only on an arbitration mailbox.
 
 Valid values are $true or $false.
 
@@ -2092,7 +2092,7 @@ This parameter is available only in on-premises Exchange.
 
 The CreateDTMFMap parameter specifies whether to create a dual-tone multiple-frequency (DTMF) map for the recipient. This allows the recipient to be identified by using a telephone keypad in Unified Messaging (UM) environments. Valid values are:
 
-- $true: A DTMF map is created for the recipient. This is the default value.
+- $true: A DTMF map is created for the recipient. This value is the default.
 - $false: A DTMF map isn't created for the recipient.
 
 ```yaml
@@ -2441,7 +2441,7 @@ The DefaultAuditSet parameter specifies whether to revert the mailbox operations
 - Delegate: Reverts the mailbox operations to log for delegate users back to the default list of operations.
 - Owner: Reverts the mailbox operations to log for mailbox owners back to the default list of operations.
 
-With on-by-default mailbox auditing in the cloud-based service, a set of mailbox operations are logged by default for each logon type. This list of operations is managed by Microsoft, who will automatically add new operations to be audited when they are released. If you change the list of mailbox operations for any logon type (by using the AuditAdmin, AuditDelegate, or AuditOwner parameters), any new mailbox operation released by Microsoft will not be audited; you'll need to explicitly add new mailbox operations to the list of operations for a logon type. Use this parameter to revert the mailbox back to the Microsoft-managed list of mailbox operations that are audited for a logon type. For more information about on-by-default mailbox auditing, see [Manage mailbox auditing](https://learn.microsoft.com/purview/audit-mailboxes).
+With on-by-default mailbox auditing in the cloud-based service, a set of mailbox operations are logged by default for each logon type. This list of operations is managed by Microsoft, and new mailbox operations are automatically added to auditing as they're released. If you change the list of mailbox operations for any logon type (by using the AuditAdmin, AuditDelegate, or AuditOwner parameters), any new mailbox operation released by Microsoft aren't audited. You need to explicitly add new mailbox operations to the list of operations for a logon type. Use this parameter to revert the mailbox back to the Microsoft-managed list of mailbox operations that are audited for a logon type. For more information about on-by-default mailbox auditing, see [Manage mailbox auditing](https://learn.microsoft.com/purview/audit-mailboxes).
 
 ```yaml
 Type: MultiValuedProperty
@@ -2513,8 +2513,8 @@ This parameter is available only in on-premises Exchange.
 
 The DisableThrottling parameter enables or disables sender rate throttling for the mailbox. Valid values are:
 
-- $true: Messages sent by this mailbox will not be throttled by Sender Rate Control. We only recommend this value for moderation mailboxes.
-- $false: Messages will be throttled after the threshold is exceeded. This is the default value.
+- $true: Messages sent by this mailbox aren't throttled by Sender Rate Control. We only recommend this value for moderation mailboxes.
+- $false: Messages are throttled after the threshold is exceeded. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -2575,7 +2575,7 @@ This parameter is available only in on-premises Exchange.
 The DowngradeHighPriorityMessagesEnabled parameter specifies whether to prevent the mailbox from sending high priority messages to an X.400 mail system. Valid values are:
 
 - $true: High priority messages sent to X.400 recipients are changed to normal priority.
-- $false: High priority messages set to X.400 recipients remain high priority. This is the default value.
+- $false: High priority messages set to X.400 recipients remain high priority. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -2641,8 +2641,8 @@ This parameter is available only in the cloud-based service.
 
 The ElcProcessingDisabled parameter specifies whether to prevent the Managed Folder Assistant from processing the mailbox. Valid values are:
 
-- $true: The Managed Folder Assistant isn't allowed to process the mailbox. Note that this setting will be ignored if a retention policy that has Preservation Lock enabled is applied to the mailbox.
-- $false: The Managed Folder Assistant is allowed to process the mailbox. This is the default value.
+- $true: The Managed Folder Assistant isn't allowed to process the mailbox. This setting is ignored if a retention policy that has Preservation Lock enabled is applied to the mailbox.
+- $false: The Managed Folder Assistant is allowed to process the mailbox. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -2723,7 +2723,7 @@ This parameter is available only in on-premises Exchange.
 
 The EmailAddressPolicyEnabled parameter specifies whether to apply email address policies to this recipient. Valid values are:
 
-- $true: Email address policies are applied to this recipient. This is the default value.
+- $true: Email address policies are applied to this recipient. This value is the default.
 - $false: Email address policies aren't applied to this recipient.
 
 ```yaml
@@ -2771,7 +2771,7 @@ Accept wildcard characters: False
 
 The EndDateForRetentionHold parameter specifies the end date for retention hold for messaging records management (MRM). To use this parameter, you need to set the RetentionHoldEnabled parameter to the value $true.
 
-**Important**: Using this parameter does not change the _RetentionHoldEnabled_ value to $false after the specified date. The _RentionHoldEnabled_ will still be $true on the mailbox after the specified date, but MRM will start processing mailbox items as normal.
+**Important**: Using this parameter does not change the _RetentionHoldEnabled_ value to $false after the specified date. The _RetentionHoldEnabled_ is still $true on the mailbox after the specified date, but MRM starts processing mailbox items as normal.
 
 Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
 
@@ -2835,7 +2835,7 @@ Accept wildcard characters: False
 
 This parameter is available only in Exchange Online.
 
-The ExcludeFromOrgHolds parameter excludes the mailbox from one or more organization-wide Microsoft 365 retention policies. This parameter can only be used for inactive mailboxes. A valid value for this parameter is the GUID of the organization-wide Microsoft 365 retention policy that the inactive mailbox is excluded from. To find the GUID values of organization-wide Microsoft 365 retention policies, run the command Get-OrganizationConfig | Format-List InplaceHolds. Note that retention policies assigned to mailboxes are prefaced by 'mbx'.
+The ExcludeFromOrgHolds parameter excludes the mailbox from one or more organization-wide Microsoft 365 retention policies. This parameter can only be used for inactive mailboxes. A valid value for this parameter is the GUID of the organization-wide Microsoft 365 retention policy that the inactive mailbox is excluded from. To find the GUID values of organization-wide Microsoft 365 retention policies, run the command Get-OrganizationConfig | Format-List InplaceHolds. Retention policies assigned to mailboxes are prefaced by 'mbx'.
 
 You can specify multiple values by using the syntax: "GUID1","GUID2",..."GUIDX".
 
@@ -2883,7 +2883,7 @@ To enter multiple values that overwrite any existing entries, use the following
 
 To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`.
 
-Although this is a multivalued property, the filter `"ExtensionCustomAttribute1 -eq 'Value'"` will return a match if the property _contains_ the specified value.
+Although this is a multivalued property, the filter `"ExtensionCustomAttribute1 -eq 'Value'"` returns a match if the property _contains_ the specified value.
 
 ```yaml
 Type: MultiValuedProperty
@@ -2907,7 +2907,7 @@ To enter multiple values that overwrite any existing entries, use the following
 
 To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`.
 
-Although this is a multivalued property, the filter `"ExtensionCustomAttribute2 -eq 'Value'"` will return a match if the property _contains_ the specified value.
+Although this is a multivalued property, the filter `"ExtensionCustomAttribute2 -eq 'Value'"` returns a match if the property _contains_ the specified value.
 
 ```yaml
 Type: MultiValuedProperty
@@ -2931,7 +2931,7 @@ To enter multiple values that overwrite any existing entries, use the following
 
 To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`.
 
-Although this is a multivalued property, the filter `"ExtensionCustomAttribute3 -eq 'Value'"` will return a match if the property _contains_ the specified value.
+Although this is a multivalued property, the filter `"ExtensionCustomAttribute3 -eq 'Value'"` returns a match if the property _contains_ the specified value.
 
 ```yaml
 Type: MultiValuedProperty
@@ -2955,7 +2955,7 @@ To enter multiple values that overwrite any existing entries, use the following
 
 To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`.
 
-Although this is a multivalued property, the filter `"ExtensionCustomAttribute4 -eq 'Value'"` will return a match if the property _contains_ the specified value.
+Although this is a multivalued property, the filter `"ExtensionCustomAttribute4 -eq 'Value'"` returns a match if the property _contains_ the specified value.
 
 ```yaml
 Type: MultiValuedProperty
@@ -2979,7 +2979,7 @@ To enter multiple values that overwrite any existing entries, use the following
 
 To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`.
 
-Although this is a multivalued property, the filter `"ExtensionCustomAttribute5 -eq 'Value'"` will return a match if the property _contains_ the specified value.
+Although this is a multivalued property, the filter `"ExtensionCustomAttribute5 -eq 'Value'"` returns a match if the property _contains_ the specified value.
 
 ```yaml
 Type: MultiValuedProperty
@@ -2999,7 +2999,7 @@ Accept wildcard characters: False
 
 The ExternalOofOptions parameter specifies the automatic replies or Out of Office (also known OOF) message options that are available for the mailbox. Valid values are:
 
-- External: Automatic replies can be configured for external senders. This is the default value.
+- External: Automatic replies can be configured for external senders. This value is the default.
 - InternalOnly: Automatic replies can be configured only for internal senders.
 
 ```yaml
@@ -3020,7 +3020,7 @@ Accept wildcard characters: False
 
 This parameter is available only in on-premises Exchange.
 
-The FolderHierarchyChildrenCountReceiveQuota parameter specifies the maximum number of subfolders that can be created in a mailbox folder. The mailbox owner won't be able to create a new subfolder when this limit is reached.
+The FolderHierarchyChildrenCountReceiveQuota parameter specifies the maximum number of subfolders that can be created in a mailbox folder. The mailbox owner can't create a new subfolder when this limit is reached.
 
 To see the current value of this property, run the command `Get-MailboxStatistics <MailboxIdentity> | Format-List FolderHierarchyChildrenCountReceiveQuota`.
 
@@ -3064,7 +3064,7 @@ Accept wildcard characters: False
 
 This parameter is available only in on-premises Exchange.
 
-The FolderHierarchyDepthReceiveQuota parameter specifies the maximum number of levels in the folder hierarchy of a mailbox folder. The mailbox owner won't be able to create another level in the folder hierarchy of the mailbox folder when this limit is reached.
+The FolderHierarchyDepthReceiveQuota parameter specifies the maximum number of levels in the folder hierarchy of a mailbox folder. The mailbox owner can't create another level in the folder hierarchy of the mailbox folder when this limit is reached.
 
 To see the current value of this property, run the command `Get-MailboxStatistics <MailboxIdentity> | Format-List FolderHierarchyDepthReceiveQuota`.
 
@@ -3108,7 +3108,7 @@ Accept wildcard characters: False
 
 This parameter is available only in on-premises Exchange.
 
-The FoldersCountReceiveQuota parameter is used to specify a maximum number of folders within a mailbox, typically a public folder mailbox. If this value is configured and the limit is reached, no new folders will be able to be created.
+The FoldersCountReceiveQuota parameter is used to specify a maximum number of folders within a mailbox, typically a public folder mailbox. If this value is configured and the limit is reached, you can't create new folders in the mailbox.
 
 To see the current value of this property, run the command `Get-MailboxStatistics <MailboxIdentity> | Format-List FoldersCountReceiveQuota`.
 
@@ -3313,7 +3313,7 @@ Accept wildcard characters: False
 The HiddenFromAddressListsEnabled parameter specifies whether this recipient is visible in address lists. Valid values are:
 
 - $true: The recipient isn't visible in address lists.
-- $false: The recipient is visible in address lists. This is the default value.
+- $false: The recipient is visible in address lists. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -3363,11 +3363,11 @@ The ImListMigrationCompleted parameter specifies whether a user's Lync or Skype
 Valid values are:
 
 - $true: The user's Lync or Skype for Business contact list is stored in their Exchange 2016 mailbox. This prevents you from migrating the mailbox back to an Exchange 2010 server.
-- $false: The user's Lync or Skype for Business contact list is stored on a Lync or Skype for Business server. This doesn't prevent you from migrating the mailbox back to an Exchange 2010 server. This is the default value.
+- $false: The user's Lync or Skype for Business contact list is stored on a Lync or Skype for Business server. This doesn't prevent you from migrating the mailbox back to an Exchange 2010 server. This value is the default.
 
 Lync Server 2013 and Skype for Business Server 2015 support storing the user's contact list in their Exchange 2016 mailbox. This feature is known as the unified contact store (UCS), and it allows applications to show a consistent, up-to-date contact list. However, Exchange 2010 doesn't support the unified contact store. Therefore, before you migrate a user's Exchange 2016 mailbox back to Exchange 2010, you need to move the user's Lync or Skype for Business contact list from the unified contact store back to a Lync 2013 or Skype for Business server. For more information, see [Configuring Microsoft Lync Server 2013 to use the unified contact store](https://learn.microsoft.com/lyncserver/lync-server-2013-configuring-lync-server-to-use-the-unified-contact-store).
 
-If you migrate an Exchange 2013 mailbox back to Exchange 2010 while the user's Lync or Skype for Business contact list is stored in the unified contact store, the user could permanently lose access to those contacts. After you verify the user's Lync or Skype for Business contact list has been moved back to a Lync 2013 or Skype for Business server, you should be able to complete the mailbox migration. If you need to migrate the mailbox despite the potential for data loss, you can manually set the ImListMigrationCompleted parameter to $false.
+If you migrate an Exchange 2013 mailbox back to Exchange 2010 while the user's Lync or Skype for Business contact list is stored in the unified contact store, the user could permanently lose access to those contacts. After you verify the user's Lync or Skype for Business contact list is moved back to a Lync 2013 or Skype for Business server, you should be able to complete the mailbox migration. If you need to migrate the mailbox despite the potential for data loss, you can manually set the ImListMigrationCompleted parameter to $false.
 
 ```yaml
 Type: Boolean
@@ -3433,7 +3433,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
 
-The IsExcludedFromServingHierarchy parameter prevents users from accessing the public folder hierarchy on this public folder mailbox. For load-balancing purposes, users are equally distributed across public folder mailboxes by default. When this parameter is set on a public folder mailbox, that mailbox isn't included in this automatic load-balancing and won't be accessed by users to retrieve the public folder hierarchy. However, if an administrator has set the DefaultPublicFolderMailbox property on a user mailbox to a specific public folder mailbox, the user will still access the specified public folder mailbox even if the IsExcludedFromServingHierarchy parameter is set for that public folder mailbox.
+The IsExcludedFromServingHierarchy parameter prevents users from accessing the public folder hierarchy on this public folder mailbox. For load-balancing purposes, users are equally distributed across public folder mailboxes by default. When this parameter is set on a public folder mailbox, that mailbox isn't included in this automatic load-balancing and can't be accessed by users to retrieve the public folder hierarchy. However, if an administrator has set the DefaultPublicFolderMailbox property on a user mailbox to a specific public folder mailbox, the user can still access the specified public folder mailbox even if the IsExcludedFromServingHierarchy parameter is set for that public folder mailbox.
 
 You should use this parameter only during public folder migrations. Don't use this parameter once the initial migration validation is complete.
 
@@ -3503,11 +3503,11 @@ A valid value is a number up to 1.999999999 terabytes (2199023254528 bytes) or t
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The IssueWarningQuota value must be less than or equal to the ProhibitSendReceiveQuota value.
 
-In Exchange Online, the quota value is determined by the subscriptions and licenses that administrators purchase and assign in the Microsoft 365 admin center. You can lower the quota value, and you may be able to raise the quota, but you can't exceed the maximum value that's allowed by the subscription or license. In Exchange Online, you can't use this parameter on public folder mailboxes.
+In Exchange Online, the quota value is determined by the subscriptions and licenses that administrators purchase and assign in the Microsoft 365 admin center. You can lower the quota value, and you might be able to raise the quota, but you can't exceed the maximum value that's allowed by the subscription or license. In Exchange Online, you can't use this parameter on public folder mailboxes.
 
 In on-premises Exchange, the default value of this parameter is unlimited. When the UseDatabaseQuotaDefaults parameter on the mailbox is set to $true (the default value), the value of the this parameter is ignored, and the mailbox uses the IssueWarningQuota value from the mailbox database. To use this parameter to enforce a specific quota value for the mailbox, you need to set the UseDatabaseQuotaDefaults parameter to the value $false.
 
@@ -3681,7 +3681,7 @@ Accept wildcard characters: False
 The LitigationHoldEnabled parameter specifies whether to place the mailbox on litigation hold. Valid values are:
 
 - $true: The mailbox is on litigation hold.
-- $false: The mailbox isn't on litigation hold. This is the default value.
+- $false: The mailbox isn't on litigation hold. This value is the default.
 
 After a mailbox is placed on litigation hold, messages can't be deleted from the mailbox. Deleted items and all versions of changed items are retained in the Recoverable Items folder. Items that are purged from the dumpster are also retained and the items are held indefinitely. If you enable litigation hold, single-item recovery quotas aren't applied.
 
@@ -3937,11 +3937,11 @@ When you enter a value, qualify the value with one of the following units:
 - MB (megabytes)
 - GB (gigabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 A valid value is a number up to 1.999999 gigabytes (2147483647 bytes) or the value unlimited.
 
-In Exchange Online, the value is determined by the subscriptions and licenses that administrators purchase and assign in the Microsoft 365 admin center. You can lower the value, and you may be able to raise the value, but you can't exceed the maximum value that's allowed by the subscription or license.
+In Exchange Online, the value is determined by the subscriptions and licenses that administrators purchase and assign in the Microsoft 365 admin center. You can lower the value, and you might be able to raise the value, but you can't exceed the maximum value that's allowed by the subscription or license.
 
 In Exchange Online, you use this parameter to configure the MaxReceiveSize value on existing mailboxes. Use the Set-MailboxPlan cmdlet to change the MaxReceiveSize value for all new mailboxes that you create in the future.
 
@@ -3994,11 +3994,11 @@ When you enter a value, qualify the value with one of the following units:
 - MB (megabytes)
 - GB (gigabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 A valid value is a number up to 1.999999 gigabytes (2147483647 bytes) or the value unlimited.
 
-In Exchange Online, the value is determined by the subscriptions and licenses that administrators purchase and assign in the Microsoft 365 admin center. You can lower the value, and you may be able to raise the value, but you can't exceed the maximum value that's allowed by the subscription or license.
+In Exchange Online, the value is determined by the subscriptions and licenses that administrators purchase and assign in the Microsoft 365 admin center. You can lower the value, and you might be able to raise the value, but you can't exceed the maximum value that's allowed by the subscription or license.
 
 In Exchange Online, you use this parameter to configure the MaxSendSize value on existing mailboxes. Use the Set-MailboxPlan cmdlet to change the MaxSendSize value for all new mailboxes that you create in the future.
 
@@ -4027,7 +4027,7 @@ Accept wildcard characters: False
 The MessageCopyForSendOnBehalfEnabled parameter specifies whether to copy the sender for messages that are sent from a mailbox by users that have the "send on behalf of" permission. Valid values are:
 
 - $true: When a user sends a message from the mailbox by using the "send on behalf of" permission, a copy of the message is sent to the sender's mailbox.
-- $false: When a user sends a message from the mailbox by using the "send on behalf of" permission, a copy of the message isn't sent to the sender's mailbox. This is the default value.
+- $false: When a user sends a message from the mailbox by using the "send on behalf of" permission, a copy of the message isn't sent to the sender's mailbox. This value is the default.
 
 You give users permission to send on behalf of a mailbox by using the GrantSendOnBehalfTo parameter on the mailbox.
 
@@ -4052,7 +4052,7 @@ Accept wildcard characters: False
 The MessageCopyForSentAsEnabled parameter specifies whether to copy the sender for messages that are sent from a mailbox by users that have the "send as" permission. Valid values are:
 
 - $true: When a user sends a message from the mailbox by using the "send as" permission, a copy of the message is sent to the sender's mailbox.
-- $false: When a user sends a message from the mailbox by using the "send as" permission, a copy of the message isn't sent to the sender's mailbox. This is the default value.
+- $false: When a user sends a message from the mailbox by using the "send as" permission, a copy of the message isn't sent to the sender's mailbox. This value is the default.
 
 In Exchange Online, you give a user permission to send as a mailbox by running this command: `Add-RecipientPermission <Mailbox> -AccessRights SendAs -Trustee <User>`.
 
@@ -4078,7 +4078,7 @@ This parameter is available only in the cloud-based service.
 
 The MessageCopyForSMTPClientSubmissionEnabled parameter specifies whether to copy the sender for messages that are sent using SMTP client submission (SMTP AUTH). Valid values are:
 
-- $true: When the user's account sends messages using SMTP AUTH, a copy of the message is sent to the users's mailbox. This is the default value.
+- $true: When the user's account sends messages using SMTP AUTH, a copy of the message is sent to the users's mailbox. This value is the default.
 - $false: When the user's account sends messages using SMTP AUTH, a copy of the message isn't sent to the users's mailbox.
 
 ```yaml
@@ -4121,7 +4121,7 @@ Accept wildcard characters: False
 
 The MessageTrackingReadStatusEnabled parameter specifies whether to include detailed information in delivery reports for messages sent to the mailbox. Valid values are:
 
-- $true: The read status of the message and the date-time that the message was delivered is shown in the delivery report for messages sent to this mailbox. This is the default value.
+- $true: The read status of the message and the date-time that the message was delivered is shown in the delivery report for messages sent to this mailbox. This value is the default.
 - $false: The read status of the message isn't displayed in the delivery report for messages sent to this mailbox. Only the date-time that the message was delivered is shown in the delivery report.
 
 ```yaml
@@ -4214,7 +4214,7 @@ Accept wildcard characters: False
 The ModerationEnabled parameter specifies whether moderation is enabled for this recipient. Valid value are:
 
 - $true: Moderation is enabled for this recipient. Messages sent to this recipient must be approved by a moderator before the messages are delivered.
-- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This is the default value.
+- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This value is the default.
 
 You use the ModeratedBy parameter to specify the moderators.
 
@@ -4493,11 +4493,11 @@ A valid value is a number up to 1.999999999 terabytes (2199023254528 bytes) or t
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The ProhibitSendQuota value must be less than or equal to the ProhibitSendReceiveQuota value.
 
-In Exchange Online, the quota value is determined by the subscriptions and licenses that administrators purchase and assign in the Microsoft 365 admin center. You can lower the quota value, and you may be able to raise the quota, but you can't exceed the maximum value that's allowed by the subscription or license. In Exchange Online, you can't use this parameter on public folder mailboxes.
+In Exchange Online, the quota value is determined by the subscriptions and licenses that administrators purchase and assign in the Microsoft 365 admin center. You can lower the quota value, and you might be able to raise the quota, but you can't exceed the maximum value that's allowed by the subscription or license. In Exchange Online, you can't use this parameter on public folder mailboxes.
 
 In on-premises Exchange, the default value of this parameter is unlimited. When the UseDatabaseQuotaDefaults parameter on the mailbox is set to the value $true (the default value), the value of the this parameter is ignored, and the mailbox uses the ProhibitSendQuota value from the mailbox database. To use this parameter to enforce a specific quota value for the mailbox, you need to set the UseDatabaseQuotaDefaults parameter to the value $false.
 
@@ -4527,7 +4527,7 @@ A valid value is a number up to 1.999999999 terabytes (2199023254528 bytes) or t
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value must be greater than or equal to the ProhibitSendQuota or IssueWarningQuota values.
 
@@ -4691,7 +4691,7 @@ When you enter a number, you can qualify it with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The RecoverableItemsQuota value must be greater than or equal to the RecoverableItemsWarningQuota value.
 
@@ -4727,7 +4727,7 @@ When you enter a number, you can qualify it with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The RecoverableItemsWarningQuota value must be less than or equal to the RecoverableItemsQuota value.
 
@@ -4991,9 +4991,9 @@ This parameter is available only in the cloud-based service.
 
 The RemoveOrphanedHolds parameter is used to remove the mailbox (typically, an inactive mailbox) from In-Place Holds that no longer exist, but are still applied to the mailbox. You identify the In-Place Hold by using its GUID value. You can specify multiple GUID values separated by commas.
 
-If you use the GUID value of an In-Place Hold that still exists as a value for this parameter, the command will return an error. If that happens, you'll need to remove the mailbox (or inactive mailbox) from the In-Place Hold.
+If you use the GUID value of an In-Place Hold that still exists as a value for this parameter, the command returns an error. If that happens, you need to remove the mailbox (or inactive mailbox) from the In-Place Hold.
 
-In an Exchange hybrid deployment, In-Place Holds that are created in the on-premises organization can be applied to cloud-based mailboxes. In this scenario, it's possible that the hold object hasn't been synced to the cloud-based organization, and using this parameter will remove the specified hold from the cloud-based mailbox even though the hold may still exist. To prevent this from happening, make sure the hold doesn't exist in the on-premises organization before you use this parameter.
+In an Exchange hybrid deployment, In-Place Holds that are created in the on-premises organization can be applied to cloud-based mailboxes. In this scenario, it's possible that the hold object hasn't been synced to the cloud-based organization, and using this parameter removes the specified hold from the cloud-based mailbox even though the hold might still exist. To prevent this from happening, make sure the hold doesn't exist in the on-premises organization before you use this parameter.
 
 ```yaml
 Type: String[]
@@ -5081,7 +5081,7 @@ This parameter is available only in on-premises Exchange.
 The ResetPasswordOnNextLogon parameter specifies whether the user is required to change their password the next time they log on to their mailbox. Valid values are:
 
 - $true: The user is required to change their password the next time they log on to their mailbox.
-- $false: The user isn't required to change their password the next time they log on to their mailbox. This is the default value.
+- $false: The user isn't required to change their password the next time they log on to their mailbox. This value is the default.
 
 In Exchange Online, administrators can require users to reset their password the next time they log on by using the ResetPasswordOnNextLogon parameter on the Set-User cmdlet.
 
@@ -5184,7 +5184,7 @@ This parameter is available only in on-premises Exchange.
 The RetainDeletedItemsUntilBackup parameter specifies whether to keep items in the Recoverable Items\\Deletions folder of the mailbox until the next database backup occurs. Valid values are:
 
 - $true: Deleted items are kept until the next mailbox database backup. This value could effectively override the DeletedItemRetention and RecoverableItemsQuota parameter values.
-- $false: This is the default value. Retention of deleted items in mailboxes is controlled by the DeletedItemRetention and RecoverableItemsQuota parameter values.
+- $false: This value is the default. Retention of deleted items in mailboxes is controlled by the DeletedItemRetention and RecoverableItemsQuota parameter values.
 
 When the UseDatabaseRetentionDefaults parameter on the mailbox is set to the value $true (the default value), the value of the this parameter is ignored, and the mailbox uses the RetainDeletedItemsUntilBackup parameter value from the mailbox database. To use the RetainDeletedItemsUntilBackup parameter on the mailbox, you need to set the UseDatabaseRetentionDefaults parameter to the value $false.
 
@@ -5233,7 +5233,7 @@ Accept wildcard characters: False
 The RetentionHoldEnabled parameter specifies whether the mailbox is placed on retention hold. Placing the mailbox on retention hold temporarily suspends the processing of retention policies or managed folder mailbox policies for the mailbox (for example, when the user is on vacation). Valid values are:
 
 - $true: The mailbox is placed on retention hold. Retention policies and managed folder policies are suspended for the mailbox, and purging items from the mailbox isn't possible (even using MFCMapi).
-- $false: The retention hold is removed from the mailbox. The mailbox is subject to retention policies and managed folder policies. This is the default value.
+- $false: The retention hold is removed from the mailbox. The mailbox is subject to retention policies and managed folder policies. This value is the default.
 
 To set the start date for retention hold, use the StartDateForRetentionHold parameter.
 
@@ -5368,7 +5368,7 @@ A valid value is a number from 32 to 256 kilobytes (32768 to 262144 bytes). When
 - B (bytes)
 - KB (kilobytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 In Exchange Online, Exchange 2019, Exchange 2016, and Exchange 2013, the default value is 256 kilobytes (262,144 bytes).
 
@@ -5394,7 +5394,7 @@ Accept wildcard characters: False
 
 This parameter is available only in on-premises Exchange.
 
-The SamAccountName parameter (also known as the pre-Windows 2000 user account or group name) specifies an object identifier that's compatible with older versions of Microsoft Windows client and server operating systems. The value can contain letters, numbers, spaces, periods (.), and the following characters: !, #, $, %, ^, &, -, \_, {, }, and ~. The last character can't be a period. Unicode characters are allowed, but accented characters may generate collisions (for example, o and ö match). The maximum length is 20 characters.
+The SamAccountName parameter (also known as the pre-Windows 2000 user account or group name) specifies an object identifier that's compatible with older versions of Microsoft Windows client and server operating systems. The value can contain letters, numbers, spaces, periods (.), and the following characters: !, #, $, %, ^, &, -, \_, {, }, and ~. The last character can't be a period. Unicode characters are allowed, but accented characters might generate collisions (for example, o and ö match). The maximum length is 20 characters.
 
 ```yaml
 Type: String
@@ -5438,7 +5438,7 @@ The SCLDeleteEnabled parameter specifies whether to silently delete messages tha
 
 - $true: Messages that meet or exceed the SCLDeleteThreshold value are silently deleted without sending a non-delivery report (NDR).
 - $false: Messages that meet or exceed the SCLDeleteThreshold value aren't deleted.
-- $null (blank): The value isn't configured. This is the default value.
+- $null (blank): The value isn't configured. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -5484,7 +5484,7 @@ The SCLJunkEnabled parameter specifies whether messages that exceed(not meet) th
 
 - $true: Messages that exceed the SCLJunkThreshold value are moved to the Junk Email folder. Messages that meet the SCLJunkThreshold value aren't moved to the Junk Email folder.
 - $false: Messages that meet or exceed the SCLJunkThreshold value aren't moved to the Junk Email folder.
-- $null (blank): The value isn't configured. This is the default value.
+- $null (blank): The value isn't configured. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -5530,7 +5530,7 @@ The SCLQuarantineEnabled parameter specifies whether messages that meet or excee
 
 - $true: Messages that meet or exceed the SCLQuarantineThreshold value are sent to the quarantine mailbox.
 - $false: Messages that meet or exceed the SCLQuarantineThreshold value aren't sent to the quarantine mailbox.
-- $null (blank): The value isn't configured. This is the default value.
+- $null (blank): The value isn't configured. This value is the default.
 
 To configure the quarantine mailbox, see [Configure a spam quarantine mailbox](https://learn.microsoft.com/Exchange/antispam-and-antimalware/antispam-protection/configure-quarantine-mailboxes).
 
@@ -5578,7 +5578,7 @@ The SCLRejectEnabled parameter specifies whether messages that meet or exceed th
 
 - $true: Messages that meet or exceed the SCLRejectThreshold value are rejected, and an NDR is sent to the sender.
 - $false: Messages that meet or exceed the SCLRejectThreshold value aren't rejected.
-- $null (blank): The value isn't configured. This is the default value.
+- $null (blank): The value isn't configured. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -5660,7 +5660,7 @@ Accept wildcard characters: False
 
 The SendModerationNotifications parameter specifies when moderation notification messages are sent. Valid values are:
 
-- Always: Notify all senders when their messages aren't approved. This is the default value.
+- Always: Notify all senders when their messages aren't approved. This value is the default.
 - Internal: Notify senders in the organization when their messages aren't approved.
 - Never: Don't notify anyone when a message isn't approved.
 
@@ -5732,8 +5732,8 @@ Accept wildcard characters: False
 
 The SingleItemRecoveryEnabled parameter specifies whether to prevent the Recoverable Items folder from being purged. Valid values are:
 
-- $true: Single item recovery is enabled. The Recoverable Items folder can't be purged, and deleted or edited items can't be removed. This is the default value in Exchange Online. For more information, see [Enable or disable single item recovery for a mailbox in Exchange Online](https://learn.microsoft.com/exchange/recipients-in-exchange-online/manage-user-mailboxes/enable-or-disable-single-item-recovery).
-- $false: Single item recovery isn't enabled. The Recoverable Items folder can be purged, and deleted or edited items can be removed. This is the default value in Exchange Server. For more information, see [Enable or disable single item recovery for a mailbox](https://learn.microsoft.com/exchange/recipients/user-mailboxes/single-item-recovery).
+- $true: Single item recovery is enabled. The Recoverable Items folder can't be purged, and deleted or edited items can't be removed. This value is the default in Exchange Online. For more information, see [Enable or disable single item recovery for a mailbox in Exchange Online](https://learn.microsoft.com/exchange/recipients-in-exchange-online/manage-user-mailboxes/enable-or-disable-single-item-recovery).
+- $false: Single item recovery isn't enabled. The Recoverable Items folder can be purged, and deleted or edited items can be removed. This value is the default in Exchange Server. For more information, see [Enable or disable single item recovery for a mailbox](https://learn.microsoft.com/exchange/recipients/user-mailboxes/single-item-recovery).
 
 ```yaml
 Type: Boolean
@@ -5958,7 +5958,7 @@ Accept wildcard characters: False
 
 This parameter is available only in on-premises Exchange.
 
-The UMGrammar parameter specifies whether the arbitration mailbox (also called an organization mailbox) is used for UM directory speech grammar generation for the organization. UM directory speech grammars will be generated and used on the Mailbox server of this arbitration mailbox. UM directory speech grammars are used in speech-enabled directory search features, such as UM auto attendants. You can use this parameter only on an arbitration mailbox.
+The UMGrammar parameter specifies whether the arbitration mailbox (also called an organization mailbox) is used for UM directory speech grammar generation for the organization. UM directory speech grammars are generated and used on the Mailbox server of this arbitration mailbox. UM directory speech grammars are used in speech-enabled directory search features, such as UM auto attendants. You can use this parameter only on an arbitration mailbox.
 
 Valid values are $true or $false.
 
@@ -6032,7 +6032,7 @@ This parameter is functional only in on-premises Exchange.
 
 The UseDatabaseRetentionDefaults parameter specifies whether the retention settings for items in the Recoverable Items folder in the mailbox are determined by the settings on the mailbox or the corresponding settings on the mailbox database. Valid values are:
 
-- $true: The mailbox uses the applicable retention settings that are configured on the mailbox database. Any corresponding settings that are configured on the mailbox are ignored. This is the default value.
+- $true: The mailbox uses the applicable retention settings that are configured on the mailbox database. Any corresponding settings that are configured on the mailbox are ignored. This value is the default.
 - $false: The mailbox uses its own values for the applicable retention settings. Any corresponding settings that are configured on the mailbox database are ignored.
 
 The following retention settings are affected by this parameter:
@@ -6040,7 +6040,7 @@ The following retention settings are affected by this parameter:
 - DeletedItemRetention
 - RetainDeletedItemsUntilBackup
 
-**Note**: If you set the RetainDeletedItemsUntilBackup parameter on the mailbox database to the value $true when the value of the UseDatabaseRetentionDefaults parameter on a mailbox is also $true (the default value), the value of the UseDatabaseRetentionDefaults property in the output of the Get-Mailbox cmdlet will erroneously appear as False. To verify the value of the UseDatabaseRetentionDefaults property on the mailbox, do the following steps in the Exchange Management Shell:
+**Note**: If you set the RetainDeletedItemsUntilBackup parameter on the mailbox database to the value $true when the value of the UseDatabaseRetentionDefaults parameter on a mailbox is also $true (the default value), the value of the UseDatabaseRetentionDefaults property in the output of the Get-Mailbox cmdlet erroneously appears as False. To verify the value of the UseDatabaseRetentionDefaults property on the mailbox, do the following steps in the Exchange Management Shell:
 
 - Run the following command: `Import-Module ActiveDirectory`.
 - Replace \<Alias\> with the Alias value of the mailbox, and run the following command: `Get-ADUser <Alias> -Properties mDBUseDefaults | Format-List mDBUseDefaults`.
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxAuditBypassAssociation.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxAuditBypassAssociation.md
index 2ea3be04e4..727665ecc5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxAuditBypassAssociation.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxAuditBypassAssociation.md
@@ -13,7 +13,7 @@ title: Set-MailboxAuditBypassAssociation
 # Set-MailboxAuditBypassAssociation
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-MailboxAuditBypassAssociation cmdlet to configure mailbox audit logging bypass for user or computer accounts such as service accounts for applications that access mailboxes frequently.
 
@@ -32,9 +32,9 @@ Set-MailboxAuditBypassAssociation [-Identity] <MailboxAuditBypassAssociationIdPa
 ## DESCRIPTION
 When you configure a user or computer account to bypass mailbox audit logging, access or actions taken by the user or computer account to any mailbox isn't logged. By bypassing trusted user or computer accounts that need to access mailboxes frequently, you can reduce the noise in mailbox audit logs.
 
-If you use mailbox audit logging to audit mailbox access and actions, you must monitor mailbox audit bypass associations at regular intervals. If a mailbox audit bypass association is added for an account, the account can access any mailbox in the organization to which it has been assigned access permissions, without any mailbox audit logging entries being generated for such access, or any actions taken such as message deletions.
+If you use mailbox audit logging to audit mailbox access and actions, you must monitor mailbox audit bypass associations at regular intervals. If a mailbox audit bypass association is added for an account, the account can access any mailbox in the organization to which it is assigned access permissions, without any mailbox audit logging entries being generated for such access, or any actions taken such as message deletions.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxAutoReplyConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxAutoReplyConfiguration.md
index 5ca39110ff..8e5570733c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxAutoReplyConfiguration.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxAutoReplyConfiguration.md
@@ -14,7 +14,7 @@ title: Set-MailboxAutoReplyConfiguration
 # Set-MailboxAutoReplyConfiguration
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-MailboxAutoReplyConfiguration cmdlet to configure Automatic Replies settings for a specific mailbox.
 
@@ -47,7 +47,7 @@ Set-MailboxAutoReplyConfiguration [-Identity] <MailboxIdParameter>
 ## DESCRIPTION
 You can disable Automatic Replies for a specified mailbox or organization.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -105,7 +105,7 @@ This parameter is functional only in the cloud-based service.
 The AutoDeclineFutureRequestsWhenOOF parameter specifies whether to automatically decline new meeting requests that are sent to the mailbox during the scheduled time period when Automatic Replies are being sent. Valid values are:
 
 - $true: New meeting requests that are received during the scheduled time period are automatically declined.
-- $false: Meeting requests received during the scheduled time period aren't automatically declined. This is the default value.
+- $false: Meeting requests received during the scheduled time period aren't automatically declined. This value is the default.
 
 You can use this parameter only when the AutoReplyState parameter is set to Scheduled.
 
@@ -128,7 +128,7 @@ Accept wildcard characters: False
 The AutoReplyState parameter specifies whether the mailbox is enabled for Automatic Replies. Valid values are:
 
 - Enabled: Automatic Replies are sent for the mailbox.
-- Disabled: Automatic Replies aren't sent for the mailbox. This is the default value.
+- Disabled: Automatic Replies aren't sent for the mailbox. This value is the default.
 - Scheduled: Automatic Replies are sent for the mailbox during the time period that's specified by the StartTime and EndTime parameters.
 
 The Enabled and Scheduled values require these additional settings:
@@ -178,7 +178,7 @@ This parameter is functional only in the cloud-based service.
 The CreateOOFEvent parameter specifies whether to create a calendar event that corresponds to the scheduled time period when Automatic Replies are being sent for the mailbox. Valid values are:
 
 - $true: When you configure a scheduled time period for Automatic Replies by using the value Scheduled for the AutoReplyState parameter, a calendar event is created in the mailbox for those dates. You can specify the subject for the event by using the OOFEventSubject parameter.
-- $false: When you configure a scheduled time period for Automatic Replies by using the value Scheduled for the AutoReplyState parameter, no calendar event is created for those dates. This is the default value.
+- $false: When you configure a scheduled time period for Automatic Replies by using the value Scheduled for the AutoReplyState parameter, no calendar event is created for those dates. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -201,7 +201,7 @@ This parameter is functional only in the cloud-based service.
 The DeclineAllEventsForScheduledOOF parameter specifies whether to decline all existing calendar events in the mailbox during the scheduled time period when Automatic Replies are being sent. Valid values are:
 
 - $true: Existing calendar events in the mailbox that occur during the scheduled time period are declined and removed from the calendar. If the mailbox is the meeting organizer, the events are cancelled for all other attendees.
-- $false: Existing calendar events in the mailbox that occur during the scheduled time period remain in the calendar. This is the default value.
+- $false: Existing calendar events in the mailbox that occur during the scheduled time period remain in the calendar. This value is the default.
 
 You can use this parameter only when the DeclineEventsForScheduledOOF parameter is set to $true.
 
@@ -231,7 +231,7 @@ The DeclineEventsForScheduledOOF parameter specifies whether it's possible to de
 
   To decline specific events during the scheduled time period, use the EventsToDeleteIDs parameter. To decline all events during the scheduled time period, use the DeclineAllEventsForScheduledOOF parameter.
 
-- $false: Existing calendar events in the mailbox that occur during the scheduled time period remain in the calendar. This is the default value.
+- $false: Existing calendar events in the mailbox that occur during the scheduled time period remain in the calendar. This value is the default.
 
 You can use this parameter only when the AutoReplyState parameter is set to Scheduled.
 
@@ -346,7 +346,7 @@ The ExternalAudience parameter specifies whether Automatic Replies are sent to e
 
 - None: Automatic Replies aren't sent to any external senders.
 - Known: Automatic Replies are sent only to external senders that are specified in the Contact list of the mailbox.
-- All: Automatic Replies are sent to all external senders. This is the default value.
+- All: Automatic Replies are sent to all external senders. This value is the default.
 
 The value of this parameter is meaningful only when the AutoReplyState parameter is set to Enabled or Scheduled.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxCalendarConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxCalendarConfiguration.md
index 72fd48a291..d0f4c94bb5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxCalendarConfiguration.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxCalendarConfiguration.md
@@ -13,7 +13,7 @@ title: Set-MailboxCalendarConfiguration
 # Set-MailboxCalendarConfiguration
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-MailboxCalendarConfiguration cmdlet to modify mailbox calendar settings for Outlook on the web. This affects how the user's calendar looks and how reminders work in Outlook on the web. This also affects settings that define how meeting invitations, responses, and notifications are sent to the user.
 
@@ -158,7 +158,7 @@ Set-MailboxCalendarConfiguration [-MailboxLocation <MailboxLocationIdParameter>]
 ## DESCRIPTION
 The Set-MailboxCalendarConfiguration cmdlet primarily allows users to manage their own calendar settings in Outlook on the web Options. However, administrators who are members of the Organization Management or Recipient Management role groups can configure the calendar settings for users by using this cmdlet.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -381,7 +381,7 @@ Accept wildcard characters: False
 
 The ConversationalSchedulingEnabled parameter specifies whether to enable or disable conversational scheduling. Valid values are:
 
-- $true: Conversational scheduling is enabled. This is the default value.
+- $true: Conversational scheduling is enabled. This value is the default.
 - $false: Conversational scheduling is disabled.
 
 ```yaml
@@ -404,7 +404,7 @@ This parameter is available only in the cloud-based service.
 
 The CreateEventsFromEmailAsPrivate parameter specifies whether to create events from email messages as Normal or Private. Valid values are:
 
-- $true: Events from email are created as Private. This is the default value.
+- $true: Events from email are created as Private. This value is the default.
 - $false: Events from email are created as Normal (public).
 
 ```yaml
@@ -516,7 +516,7 @@ The DefaultOnlineMeetingProvider parameter specifies the default provider for on
 - RingCentral
 - SkypeForBusiness
 - SkypeForConsumer
-- TeamsForBusiness (This is the default value.)
+- TeamsForBusiness (This value is the default.)
 - Webex
 - Zoom
 
@@ -540,12 +540,12 @@ The DefaultReminderTime parameter specifies the length of time before a meeting
 
 To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds.
 
-Note that the value can't contain seconds. Valid values are:
+The value can't contain seconds. Valid values are:
 
 - 00:00:00
 - 00:05:00 (5 minutes)
 - 00:10:00 (10 minutes)
-- 00:15:00 (15 minutes) This is the default value.
+- 00:15:00 (15 minutes) This value is the default.
 - 00:30:00 (30 minutes)
 - 01:00:00 (1 hour)
 - 02:00:00 (2 hours)
@@ -601,7 +601,7 @@ This parameter is available only in the cloud-based service.
 
 The DiningEventsFromEmailEnabled parameter specifies whether to create dining reservation events from email messages. Valid values are:
 
-- $true: Create dining reservation events from email messages. This is the default value.
+- $true: Create dining reservation events from email messages. This value is the default.
 - $false: Don't create dining reservation events from email messages.
 
 This parameter is meaningful only when the EventsFromEmailEnabled parameter is set to $true (which is the default value).
@@ -646,7 +646,7 @@ This parameter is available only in the cloud-based service.
 
 The EntertainmentEventsFromEmailEnabled parameter specifies whether to create entertainment reservation events from email messages. Valid values are:
 
-- $true: Create entertainment reservation events from email messages. This is the default value.
+- $true: Create entertainment reservation events from email messages. This value is the default.
 - $false: Don't create entertainment reservation events from email messages.
 
 This parameter is meaningful only when the EventsFromEmailEnabled parameter is set to $true (which is the default value).
@@ -671,7 +671,7 @@ This parameter is available only in the cloud-based service.
 
 The EventsFromEmailEnabled parameter specifies whether to enable events to be created from email messages. Valid values are:
 
-- $true: Creating events from email messages is enabled. This is the default value.
+- $true: Creating events from email messages is enabled. This value is the default.
 - $false: Creating events from email messages is disabled.
 
 When this setting is enabled, you can enable or disable creating specific types of events from email messages by using the following parameters:
@@ -701,10 +701,10 @@ Accept wildcard characters: False
 
 The FirstWeekOfYear parameter specifies the first week of the year. Valid values are:
 
-- FirstDay: Week numbers start on the first day of the year. This is the default value.
+- FirstDay: Week numbers start on the first day of the year. This value is the default.
 - FirstFourDayWeek: Week numbers start on the first week that has at least four days.
 - FirstFullWeek: Week numbers start on the first week that has seven days.
-- LegacyNotSet: You can't set this value. This is a null value that appears only when the mailbox has been moved from an earlier version of Exchange.
+- LegacyNotSet: You can't set this value. This is a null value that appears only when the mailbox is moved from an earlier version of Exchange.
 
 You configure the first day of the week by using the WeekStartDay parameter.
 
@@ -728,7 +728,7 @@ This parameter is available only in the cloud-based service.
 
 The FlightEventsFromEmailEnabled parameter specifies whether to create flight reservation events from email messages. Valid values are:
 
-- $true: Create flight reservation events from email messages. This is the default value.
+- $true: Create flight reservation events from email messages. This value is the default.
 - $false: Don't create flight reservation events from email messages.
 
 This parameter is meaningful only when the EventsFromEmailEnabled parameter is set to $true (which is the default value).
@@ -753,7 +753,7 @@ This parameter is available only in the cloud-based service.
 
 The HotelEventsFromEmailEnabled parameter specifies whether to create hotel reservation events from email messages. Valid values are:
 
-- $true: Create hotel reservation events from email messages. This is the default value.
+- $true: Create hotel reservation events from email messages. This value is the default.
 - $false: Don't create hotel reservation events from email messages.
 
 This parameter is meaningful only when the EventsFromEmailEnabled parameter is set to $true (which is the default value).
@@ -778,7 +778,7 @@ This parameter is available only in the cloud-based service.
 
 The InvoiceEventsFromEmailEnabled parameter specifies whether to allow creating invoices from email messages. Valid values are:
 
-- $true: Creating invoices from messages is enabled. This is the default value.
+- $true: Creating invoices from messages is enabled. This value is the default.
 - $false: Creating invoices from messages is disabled.
 
 ```yaml
@@ -803,7 +803,7 @@ The LocationDetailsInFreeBusy parameter specifies the level of work location inf
 
 - None: No location information is returned.
 - Building: Only Office or Remote are returned as work location information, if provided.
-- Desk: All work location information is returned, including Building and Desk, if provided. This is the default value.
+- Desk: All work location information is returned, including Building and Desk, if provided. This value is the default.
 
 ```yaml
 Type: LocationDetailsPermissionInFreeBusy
@@ -843,7 +843,7 @@ Accept wildcard characters: False
 
 This parameter is available only in the cloud-based service.
 
-The OnlineMeetingsByDefaultEnabled parameter specifies whether to set all meetings as Teams or Skype for Business by default during meeting creation. Currently, this parameter sets the default value, so if the user has already directly interacted with this setting from an Outlook client, this default value will be ignored. Eventually, this parameter will override the Outlook-configured setting.
+The OnlineMeetingsByDefaultEnabled parameter specifies whether to set all meetings as Teams or Skype for Business by default during meeting creation. Currently, this parameter sets the default value, so if the user has already directly interacted with this setting from an Outlook client, this default value is ignored. Eventually, this parameter will override the Outlook-configured setting.
 
 Valid values are:
 
@@ -874,7 +874,7 @@ This parameter is available only in the cloud-based service.
 The PackageDeliveryEventsFromEmailEnabled parameter specifies whether to create package delivery events from email messages. Valid values are:
 
 - $true: Create package delivery events from email messages.
-- $false: Don't create package delivery events from email messages. This is the default value.
+- $false: Don't create package delivery events from email messages. This value is the default.
 
 This parameter is meaningful only when the EventsFromEmailEnabled parameter is set to $true (which is the default value).
 
@@ -916,7 +916,7 @@ Accept wildcard characters: False
 
 The RemindersEnabled parameter enables or disables reminders for calendar items. Valid values are:
 
-- $true: Reminders are enabled. This is the default value.
+- $true: Reminders are enabled. This value is the default.
 - $false: Reminders are disabled.
 
 When the reminder is first displayed is controlled by the DefaultReminderTime parameter.
@@ -939,7 +939,7 @@ Accept wildcard characters: False
 
 The ReminderSoundEnabled parameter specifies whether a sound is played along with the reminder. Valid values are:
 
-- $true: A sound is played with the reminder. This is the default value.
+- $true: A sound is played with the reminder. This value is the default.
 - $false: No sound is played with the reminder.
 
 This parameter is ignored when the RemindersEnabled parameter is set to $false.
@@ -964,7 +964,7 @@ This parameter is available only in the cloud-based service.
 
 The RentalCarEventsFromEmailEnabled parameter specifies whether to create rental car reservation events from email messages. Valid values are:
 
-- $true: Create rental car reservation events from email messages. This is the default value.
+- $true: Create rental car reservation events from email messages. This value is the default.
 - $false: Don't create rental car reservation events from email messages.
 
 This parameter is meaningful only when the EventsFromEmailEnabled parameter is set to $true (which is the default value).
@@ -1028,7 +1028,7 @@ Accept wildcard characters: False
 The ShowWeekNumbers parameter specifies whether the week number is displayed in the Outlook on the web calendar. Valid values are:
 
 - $true: The week number is displayed.
-- $false: The week number isn't displayed. This is the default value.
+- $false: The week number isn't displayed. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -1067,7 +1067,7 @@ Accept wildcard characters: False
 The TimeIncrement parameter specifies the scale that the Outlook on the web calendar uses to show time. Valid values are:
 
 - FifteenMinutes
-- ThirtyMinutes (This is the default value)
+- ThirtyMinutes (default value)
 
 ```yaml
 Type: HourIncrement
@@ -1088,7 +1088,7 @@ Accept wildcard characters: False
 The UseBrightCalendarColorThemeInOwa parameter specifies whether to use light colors or bright colors for the calendar in Outlook on the web. Valid values are:
 
 - $true: Use bright colors in the calendar.
-- $false: Use light colors in the calendar. This is the default value.
+- $false: Use light colors in the calendar. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -1110,7 +1110,7 @@ This parameter is available only in the cloud-based service.
 
 The WeatherEnabled specifies whether weather is displayed in the calendar in Outlook on the web. Valid values are:
 
-- FirstRun (This is the default value)
+- FirstRun (default value)
 - Disabled: Hide weather on the calendar.
 - Enabled: Show weather on the calendar.
 
@@ -1186,7 +1186,7 @@ This parameter is available only in the cloud-based service.
 
 The WeatherUnit parameter specifies the temperature scale that's used to display the weather in the calendar in Outlook on the web. Valid values are:
 
-- Default (This is the default value)
+- Default (default value)
 - Celsius
 - Fahrenheit
 
@@ -1208,7 +1208,7 @@ Accept wildcard characters: False
 
 The WeekStartDay parameter specifies the first day of the week. Valid values are:
 
-- Sunday (This is the default value)
+- Sunday (default value)
 - Monday
 - Tuesday
 - Wednesday
@@ -1254,7 +1254,7 @@ The WorkDays parameter specifies the work days in the calendar. Valid values are
 
 - None
 - AllDays
-- Weekdays (This is the default value)
+- Weekdays (default value)
 - WeekEndDays
 - Sunday
 - Monday
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxCalendarFolder.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxCalendarFolder.md
index d2fe92983d..7ad33e450c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxCalendarFolder.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxCalendarFolder.md
@@ -13,7 +13,7 @@ title: Set-MailboxCalendarFolder
 # Set-MailboxCalendarFolder
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-MailboxCalendarFolder cmdlet to configure calendar publishing or sharing settings on a mailbox for the visibility of calendar information to external users. To add or modify the permissions so internal users can access the calendar, use the Add-MailboxFolderPermission or Set-MailboxFolderPermission cmdlets.
 
@@ -46,7 +46,7 @@ The Set-MailboxCalendarFolder cmdlet configures calendar publishing information.
 - Level of detail to publish for the calendar
 - Whether the published URL of the calendar is enabled for search on the web
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -174,7 +174,7 @@ The PublishDateRangeFrom parameter specifies the start date of calendar informat
 - ThreeDays
 - OneWeek
 - OneMonth
-- ThreeMonths (This is the default value)
+- ThreeMonths (default value)
 - SixMonths
 - OneYear
 
@@ -202,7 +202,7 @@ The PublishDateRangeTo parameter specifies the end date of calendar information
 - ThreeDays
 - OneWeek
 - OneMonth
-- ThreeMonths (This is the default value)
+- ThreeMonths (default value)
 - SixMonths
 - OneYear
 
@@ -227,7 +227,7 @@ Accept wildcard characters: False
 The PublishEnabled parameter specifies whether to publish the specified calendar information. Valid values are:
 
 - $true: The calendar information is published.
-- $false: The calendar information is not published. This is the default value.
+- $false: The calendar information is not published. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -245,7 +245,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
 
-The ResetUrl switch replaces the existing non-public URL with a new URL for a calendar that has been published without being publicly searchable. You don't need to specify a value with this switch.
+The ResetUrl switch replaces the existing non-public URL with a new URL for a calendar that is published without being publicly searchable. You don't need to specify a value with this switch.
 
 ```yaml
 Type: SwitchParameter
@@ -266,7 +266,7 @@ Accept wildcard characters: False
 The SearchableUrlEnabled parameter specifies whether the published calendar URL is discoverable on the web.
 
 - $true: The published calendar URL is discoverable on the web.
-- $false: The published calendar URL is not discoverable on the web. This is the default value.
+- $false: The published calendar URL is not discoverable on the web. This value is the default.
 
 This parameter is meaningful only when the PublishEnabled parameter value is $true.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxDatabase.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxDatabase.md
index 8678125dd0..e700a98c53 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxDatabase.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxDatabase.md
@@ -63,7 +63,7 @@ Set-MailboxDatabase [-Identity] <DatabaseIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -114,7 +114,7 @@ Accept wildcard characters: False
 The AllowFileRestore parameter specifies whether to allow a database to be restored from a backup. Valid values are:
 
 - $true: You can replace an existing database with a newly-created database. You can mount a database that doesn't match the database entry in Active Directory.
-- $false: You can't replace an existing database with a newly-created database. You can't mount a database that doesn't match the database entry in Active Directory. This is the default value.
+- $false: You can't replace an existing database with a newly-created database. You can't mount a database that doesn't match the database entry in Active Directory. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -135,7 +135,7 @@ Accept wildcard characters: False
 The AutoDagExcludedFromMonitoring parameter specifies whether to exclude the mailbox database from the ServerOneCopyMonitor, which alerts an administrator when a replicated database has only one healthy copy available. Valid values are:
 
 - $true: No alert is issued when there's only one healthy copy of the replicated database.
-- $false: An alert is issued when there's only one healthy copy of the replicated database. This is the default value.
+- $false: An alert is issued when there's only one healthy copy of the replicated database. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -173,7 +173,7 @@ Accept wildcard characters: False
 
 The BackgroundDatabaseMaintenance parameter specifies whether the Extensible Storage Engine (ESE) performs database maintenance. Valid values are:
 
-- $true: The mailbox database reads the object during database mount and initializes the database to perform background maintenance. This is the default value.
+- $true: The mailbox database reads the object during database mount and initializes the database to perform background maintenance. This value is the default.
 - $false: The mailbox database reads the object during database mount and initializes the database without the option to perform background maintenance.
 
 ```yaml
@@ -204,7 +204,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value of this parameter must be less than or equal to the value of the RecoverableItemsQuota parameter.
 
@@ -229,7 +229,7 @@ Accept wildcard characters: False
 The CircularLoggingEnabled parameter specifies whether circular logging is enabled for the database. Valid values are:
 
 - $true: Circular logging is enabled.
-- $false: Circular logging is disabled. This is the default value.
+- $false: Circular logging is disabled. This value is the default.
 
 For more information about circular logging, see [Exchange Native Data Protection](https://learn.microsoft.com/exchange/backup-restore-and-disaster-recovery-exchange-2013-help#exchange-native-data-protection).
 
@@ -296,7 +296,7 @@ The DataMoveReplicationConstraint parameter specifies the throttling behavior fo
 - CINoReplication (Exchange 2013 or later): Moves shouldn't be throttled to ensure high availability, but the content indexing service must be up to date.
 - CISecondCopy (Exchange 2013 or later): At least one passive mailbox database copy must have the most recent changes synchronized, and the content indexing service must be up to date. Use this setting to indicate that the database is replicated to one or more mailbox database copies.
 - CISecondDatacenter (Exchange 2013 or later): At least one passive mailbox database copy in another Active Directory site must have the most recent changes replicated, and the content indexing service must be up to date. Use this setting to indicate that the database is replicated to database copies in multiple Active Directory sites.
-- SecondCopy: At least one passive mailbox database copy must have the most recent changes synchronized. This is the default value. Use this setting to indicate that the database is replicated to one or more mailbox database copies.
+- SecondCopy: At least one passive mailbox database copy must have the most recent changes synchronized. This value is the default. Use this setting to indicate that the database is replicated to one or more mailbox database copies.
 - SecondDatacenter: At least one passive mailbox database copy in another Active Directory site must have the most recent changes replicated. Use this setting to indicate that the database is replicated to database copies in multiple Active Directory sites.
 
 Any value other than None enables the Microsoft Exchange Mailbox Replication service to coordinate with Active Manager. For more information, see [Active Manager](https://learn.microsoft.com/Exchange/high-availability/database-availability-groups/active-manager).
@@ -387,7 +387,7 @@ This parameter is functional only in Exchange 2016 or earlier.
 
 The IndexEnabled parameter specifies whether Exchange Search indexes the mailbox database. Valid values are:
 
-- $true: Exchange Search indexes the mailbox database. This is the default value.
+- $true: Exchange Search indexes the mailbox database. This value is the default.
 - $false: Exchange Search doesn't index the mailbox database.
 
 ```yaml
@@ -427,7 +427,7 @@ Accept wildcard characters: False
 The IsExcludedFromProvisioning parameter specifies whether to exclude the database from the mailbox provisioning load balancer that distributes new mailboxes randomly and evenly across the available databases. Valid values are:
 
 - $true: The database is excluded from new or move mailbox operations when you don't specify the target mailbox database.
-- $false: The database can be used in new or move mailbox operations when you don't specify the target mailbox database. This is the default value.
+- $false: The database can be used in new or move mailbox operations when you don't specify the target mailbox database. This value is the default.
 
 The value is automatically set to $true when you set the IsExcludedFromProvisioningDueToLogicalCorruption parameter to $true, and isn't changed back to $false when you set the IsExcludedFromProvisioningDueToLogicalCorruption parameter back to $false. In the case of database corruption, you should set the IsExcludedFromProvisioning parameter back to $false only after you fix the corruption issue or recreate the database.
 
@@ -452,9 +452,9 @@ The IIsExcludedFromProvisioningByOperator parameter specifies whether to exclude
 Valid values are:
 
 - $true: Indicates that you manually excluded the database. The database is excluded from new or move mailbox operations when you don't specify the target mailbox database.
-- $false: The database can be used in new or move mailbox operations when you don't specify the target mailbox database. This is the default value.
+- $false: The database can be used in new or move mailbox operations when you don't specify the target mailbox database. This value is the default.
 
-Note that setting this parameter to the value $true has these additional effects on the database:
+Setting this parameter to the value $true has these additional effects on the database:
 
 - The IsExcludedFromProvisioningReason parameter requires a value if it doesn't already have one.
 - The unmodifiable IsExcludedFromProvisioningBy property is populated with your user account.
@@ -480,9 +480,9 @@ The IsExcludedFromProvisioningDueToLogicalCorruption parameter specifies whether
 Valid values are:
 
 - $true: Indicates that you excluded the database due to database corruption. The database is excluded from new or move mailbox operations when you don't specify the target mailbox database.
-- $false: This is the default value. The database can be used in new or move mailbox operations when you don't specify the target mailbox database. You should manually configure this value only after the database corruption is fixed, or after the database is recreated.
+- $false: This value is the default. The database can be used in new or move mailbox operations when you don't specify the target mailbox database. You should manually configure this value only after the database corruption is fixed, or after the database is recreated.
 
-Note that setting this parameter to the value $true has these additional effects on the database:
+Setting this parameter to the value $true has these additional effects on the database:
 
 - The IsExcludedFromProvisioningReason parameter requires a value if it doesn't already have one.
 - The unmodifiable IsExcludedFromProvisioningBy property is populated with your user account.
@@ -538,7 +538,7 @@ A valid value is a number up to 1.999999999 terabytes (2199023254528 bytes) or t
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The IssueWarningQuota value must be less than or equal to the ProhibitSendReceiveQuota value.
 
@@ -563,9 +563,9 @@ Accept wildcard characters: False
 The IsSuspendedFromProvisioning parameter specifies whether to exclude the database from the mailbox provisioning load balancer that distributes new mailboxes randomly and evenly across the available databases. Valid values are:
 
 - $true: Indicates that you don't want the exclusion to be permanent. The database is excluded from new or move mailbox operations when you don't specify the target mailbox database.
-- $false: The database can be used in new or move mailbox operations when you don't specify the target mailbox database. This is the default value.
+- $false: The database can be used in new or move mailbox operations when you don't specify the target mailbox database. This value is the default.
 
-Note that setting this parameter to the value $true has these additional effects on the database:
+Setting this parameter to the value $true has these additional effects on the database:
 
 - The IsExcludedFromProvisioningReason parameter requires a value if it doesn't already have one.
 - The unmodifiable IsExcludedFromProvisioningBy property is populated with your user account.
@@ -635,7 +635,7 @@ Accept wildcard characters: False
 
 This parameter is functional only in Exchange Server 2010.
 
-The MaintenanceSchedule parameter specifies when maintenance will be performed on the mailbox database. Maintenance includes online defragmentation, removing items that have passed their retention period, removing unused indexes and other cleanup tasks.
+The MaintenanceSchedule parameter specifies when maintenance is performed on the mailbox database. Maintenance includes online defragmentation, removing items that have passed their retention period, removing unused indexes and other cleanup tasks.
 
 The syntax for this parameter is: `StartDay.Hour:Minute [AM | PM]-EndDay.Hour:Minute [AM | PM]`.
 
@@ -695,7 +695,7 @@ Accept wildcard characters: False
 
 The MountAtStartup parameter specifies whether to mount the mailbox database when the Microsoft Exchange Information Store service starts. Valid values are:
 
-- $true: The database is mounted when the service starts. This is the default value.
+- $true: The database is mounted when the service starts. This value is the default.
 - $false: The database isn't mounted when the service starts.
 
 ```yaml
@@ -766,7 +766,7 @@ A valid value is a number up to 1.999999999 terabytes (2199023254528 bytes) or t
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The ProhibitSendQuota value must be less than or equal to the ProhibitSendReceiveQuota value.
 
@@ -798,7 +798,7 @@ A valid value is a number up to 1.999999999 terabytes (2199023254528 bytes) or t
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value must be greater than or equal to the ProhibitSendQuota or IssueWarningQuota values.
 
@@ -896,7 +896,7 @@ When you enter a number, you can qualify it with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The RecoverableItemsQuota value must be greater than or equal to the RecoverableItemsWarningQuota value.
 
@@ -930,7 +930,7 @@ When you enter a number, you can qualify it with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The RecoverableItemsWarningQuota value must be less than or equal to the RecoverableItemsQuota value.
 
@@ -955,13 +955,13 @@ Accept wildcard characters: False
 The RetainDeletedItemsUntilBackup parameter specifies whether to keep items in the Recoverable Items\\Deletions folder of the mailbox until the next database backup occurs. Valid values are:
 
 - $true: Deleted items in mailboxes are kept until the next mailbox database backup. This value could effectively override the deleted DeletedItemRetention and RecoverableItemsQuota parameter values.
-- $false: This is the default value. Retention of deleted items in mailboxes is controlled by the DeletedItemRetention and RecoverableItemsQuota parameters.
+- $false: This value is the default. Retention of deleted items in mailboxes is controlled by the DeletedItemRetention and RecoverableItemsQuota parameters.
 
 This settings applies to all mailboxes in the database that don't have their own RetainDeletedItemsUntilBackup value configured.
 
 For more information, see [Recoverable Items folder in Exchange Server](https://learn.microsoft.com/Exchange/policy-and-compliance/recoverable-items-folder/recoverable-items-folder).
 
-**Note**: If you set the value of this parameter to $true when the value of the UseDatabaseRetentionDefaults parameter on a specific mailbox is also $true (the default value), the value of the UseDatabaseRetentionDefaults property in the output of the Get-Mailbox cmdlet will erroneously appear as False. To verify the value of the UseDatabaseRetentionDefaults property on the mailbox, do the following steps in the Exchange Management Shell:
+**Note**: If you set the value of this parameter to $true when the value of the UseDatabaseRetentionDefaults parameter on a specific mailbox is also $true (the default value), the value of the UseDatabaseRetentionDefaults property in the output of the Get-Mailbox cmdlet erroneously appears as False. To verify the value of the UseDatabaseRetentionDefaults property on the mailbox, do the following steps in the Exchange Management Shell:
 
 - Run the following command: `Import-Module ActiveDirectory`.
 - Replace \<Alias\> with the Alias value of the mailbox, and run the following command: `Get-ADUser <Alias> -Properties mDBUseDefaults | Format-List mDBUseDefaults`.
@@ -986,7 +986,7 @@ This parameter is functional only in Exchange Server 2010.
 
 The RpcClientAccessServer parameter specifies the Client Access server or Client Access server array through which RPC clients (for example, Microsoft Office Outlook 2007 clients) access their mailboxes. This feature is supported for all versions of Outlook.
 
-When connecting with Outlook 2003 clients, RPC encryption is disabled by default. Unless RPC encryption is enabled on Outlook 2003 or disabled on the server, Outlook 2003 clients won't be able to connect. For more information, see [Understanding RPC Client Access](https://learn.microsoft.com/previous-versions/office/exchange-server-2010/ee332317(v=exchg.141)).
+When connecting with Outlook 2003 clients, RPC encryption is disabled by default. Unless RPC encryption is enabled on Outlook 2003 or disabled on the server, Outlook 2003 clients can't connect. For more information, see [Understanding RPC Client Access](https://learn.microsoft.com/previous-versions/office/exchange-server-2010/ee332317(v=exchg.141)).
 
 ```yaml
 Type: ClientAccessServerOrArrayIdParameter
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxDatabaseCopy.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxDatabaseCopy.md
index f8ef8e0bf2..91532aaab8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxDatabaseCopy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxDatabaseCopy.md
@@ -37,7 +37,7 @@ Set-MailboxDatabaseCopy [-Identity] <DatabaseCopyIdParameter>
 ## DESCRIPTION
 With this cmdlet, you can configure the replay lag time, truncation lag time, and activation preference value for a mailbox database copy.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -160,7 +160,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-The TruncationLagTime parameter specifies the amount of time that the Microsoft Exchange Replication service should wait before truncating log files that have replayed into the passive copy of the database. The time period begins after the log has been successfully replayed into the copy of the database.
+The TruncationLagTime parameter specifies the amount of time that the Microsoft Exchange Replication service should wait before truncating log files that have replayed into the passive copy of the database. The time period begins after the log is successfully replayed into the copy of the database.
 
 To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds.
 
@@ -224,7 +224,7 @@ To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = h
 
 The default value is 24:00:00 (24 hours). To disable deferred lagged copy play down, specify the value ([TimeSpan]::Zero).
 
-Note that when the disk is running out of space, the value of this parameter is ignored, and lagged copy play down occurs without delay.
+When the disk is running out of space, the value of this parameter is ignored, and lagged copy play down occurs without delay.
 
 ```yaml
 Type: EnhancedTimeSpan
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxExportRequest.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxExportRequest.md
index 9800ba7cc0..b81f0286db 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxExportRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxExportRequest.md
@@ -15,7 +15,7 @@ title: Set-MailboxExportRequest
 ## SYNOPSIS
 This cmdlet is available only in on-premises Exchange.
 
-Use the Set-MailboxExportRequest cmdlet to change export request options after the request has been created. You can use the Set-MailboxExportRequest cmdlet to recover from failed export requests.
+Use the Set-MailboxExportRequest cmdlet to change export request options after the request is created. You can use the Set-MailboxExportRequest cmdlet to recover from failed export requests.
 
 This cmdlet is available only in the Mailbox Import Export role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Mailbox Import Export role to a role group (for example, to the Organization Management role group). For more information, see [Add a role to a role group](https://learn.microsoft.com/Exchange/permissions/role-groups#add-a-role-to-a-role-group).
 
@@ -57,7 +57,7 @@ Set-MailboxExportRequest [-Identity] <MailboxExportRequestIdParameter>
 ## DESCRIPTION
 You can pipeline the Set-MailboxExportRequest cmdlet from the Get-MailboxExportRequest cmdlet.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -175,7 +175,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-The CompletedRequestAgeLimit parameter specifies how long the request will be kept after it has completed before being automatically removed. The default value is 30 days.
+The CompletedRequestAgeLimit parameter specifies how long the request is kept after it has completed before being automatically removed. The default value is 30 days.
 
 ```yaml
 Type: Unlimited
@@ -236,7 +236,7 @@ For more information about maximum message size values, see the following topics
 - Exchange 2016: [Message size limits in Exchange Server](https://learn.microsoft.com/Exchange/mail-flow/message-size-limits)
 - Exchange Online: [Exchange Online Limits](https://learn.microsoft.com/office365/servicedescriptions/exchange-online-service-description/exchange-online-limits)
 
-Valid input for this parameter is an integer or the value unlimited. The default value is 0, which means the request will fail if any large items are detected. If you are OK with leaving a few large items behind, you can set this parameter to a reasonable value (we recommend 10 or lower) so the request can proceed.
+Valid input for this parameter is an integer or the value unlimited. The default value is 0, which means the request fails if any large items are detected. If you are OK with leaving a few large items behind, you can set this parameter to a reasonable value (we recommend 10 or lower) so the request can proceed.
 
 If you set this value to 51 or higher, you also need to use the AcceptLargeDataLoss switch. Otherwise, the command will fail.
 
@@ -261,7 +261,7 @@ The Priority parameter specifies the order in which the request should be proces
 - Lowest
 - Lower
 - Low
-- Normal: This is the default value.
+- Normal: This value is the default.
 - High
 - Higher
 - Highest
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxFolderPermission.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxFolderPermission.md
index a49cfbab41..223ac5f5c3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxFolderPermission.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxFolderPermission.md
@@ -13,7 +13,7 @@ title: Set-MailboxFolderPermission
 # Set-MailboxFolderPermission
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-MailboxFolderPermission cmdlet to modify folder-level permissions for users in mailboxes. This cmdlet differs from the Add-MailboxFolderPermission cmdlet in that it modifies existing permission entries. To configure calendar publishing or sharing settings for a mailbox so calendar information is visible to external users, use the Set-MailboxCalendarFolder cmdlet.
 
@@ -32,9 +32,9 @@ Set-MailboxFolderPermission [-Identity] <MailboxFolderIdParameter> -AccessRights
 ```
 
 ## DESCRIPTION
-In Exchange Online PowerShell, if you don't use the SendNotificationToUser or SharingPermissionFlags parameters, there are no changes to the functionality of the cmdlet. For example, if the user is an existing delegate, and you change their permissions to Editor without using the SendNotificationToUser or SharingPermissionFlags parameters, the user remains a delegate. But, if you use the SendNotificationToUser parameter ($true or $false), the SharingPermissionFlags parameter has the default value None, which can affect delegate access for existing users. For example, you change an existing delegate's permission to Editor, and you use SendNotificationToUser with the value $true. The user will no longer be a delegate and will only have Editor permissions to the folder.
+In Exchange Online PowerShell, if you don't use the SendNotificationToUser or SharingPermissionFlags parameters, there are no changes to the functionality of the cmdlet. For example, if the user is an existing delegate, and you change their permissions to Editor without using the SendNotificationToUser or SharingPermissionFlags parameters, the user remains a delegate. But, if you use the SendNotificationToUser parameter ($true or $false), the SharingPermissionFlags parameter has the default value None, which can affect delegate access for existing users. For example, you change an existing delegate's permission to Editor, and you use SendNotificationToUser with the value $true. The user is no longer a delegate and has only Editor permissions to the folder.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -246,10 +246,10 @@ Accept wildcard characters: False
 
 This parameter is available only in the cloud-based service.
 
-The SendNotificationToUser parameter specifies whether to send a sharing invitation to the user when you modify their calendar permissions. The message will be a normal calendar sharing invitation that can be accepted by the recipient. Valid values are:
+The SendNotificationToUser parameter specifies whether to send a sharing invitation to the user when you modify their calendar permissions. The message is a normal calendar sharing invitation that can be accepted by the recipient. Valid values are:
 
 - $true: A sharing invitation is sent.
-- $false: No sharing invitation is sent. This is the default value.
+- $false: No sharing invitation is sent. This value is the default.
 
 This parameter only applies to calendar folders and can only be used with the following AccessRights parameter values:
 
@@ -278,8 +278,8 @@ This parameter is available only in the cloud-based service.
 
 The SharingPermissionFlags parameter assigns calendar delegate permissions. This parameter only applies to calendar folders and can only be used when the AccessRights parameter value is Editor. Valid values are:
 
-- None: Removes delegate permissions and updates the meeting message rule so the user stops receiving meeting invites and responses for the mailbox. This is the default value when you use the SendNotificationToUser parameter without specifying a value for the SharingPermissionFlags parameter.
-- Delegate: The user is made a calendar delegate, which includes receiving meeting invites and responses. If there are no other delegates, this value will create the meeting message rule. If there are existing delegates, the user is added to the meeting message rule without changing how delegate messages are sent.
+- None: Removes delegate permissions and updates the meeting message rule so the user stops receiving meeting invites and responses for the mailbox. This value is the default when you use the SendNotificationToUser parameter without specifying a value for the SharingPermissionFlags parameter.
+- Delegate: The user is made a calendar delegate, which includes receiving meeting invites and responses. If there are no other delegates, this value creates the meeting message rule. If there are existing delegates, the user is added to the meeting message rule without changing how delegate messages are sent.
 - CanViewPrivateItems: The user can access private items on the calendar. You must use this value with the Delegate value.
 
 You can specify multiple values separated by commas.
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxIRMAccess.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxIRMAccess.md
index 4d967f1dc5..f4f0e60e87 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxIRMAccess.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxIRMAccess.md
@@ -29,7 +29,7 @@ Set-MailboxIRMAccess -AccessLevel <IRMAccessLevel> [-Identity] <MailboxIdParamet
 > [!NOTE]
 > This cmdlet works only for delegates who already have Full Access permission to the mailbox. For more information, see [Manage permissions for recipients in Exchange Online](https://learn.microsoft.com/exchange/recipients-in-exchange-online/manage-permissions-for-recipients).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxImportRequest.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxImportRequest.md
index 2bcc2e87e1..86bba500cd 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxImportRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxImportRequest.md
@@ -13,9 +13,9 @@ title: Set-MailboxImportRequest
 # Set-MailboxImportRequest
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
-Use the Set-MailboxImportRequest cmdlet to change import request options after the request has been created. You can use the Set-MailboxImportRequest cmdlet to recover from failed import requests.
+Use the Set-MailboxImportRequest cmdlet to change import request options after the request is created. You can use the Set-MailboxImportRequest cmdlet to recover from failed import requests.
 
 This cmdlet is available only in the Mailbox Import Export role, and by default, the role isn't assigned to any role groups. To use this cmdlet, you need to add the Mailbox Import Export role to a role group (for example, to the Organization Management role group). For more information, see [Add a role to a role group](https://learn.microsoft.com/Exchange/permissions/role-groups#add-a-role-to-a-role-group).
 
@@ -58,7 +58,7 @@ Set-MailboxImportRequest [-Identity] <MailboxImportRequestIdParameter> [-RehomeR
 ## DESCRIPTION
 You can pipeline the Set-MailboxImportRequest cmdlet from the Get-MailboxImportRequest cmdlet.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -148,7 +148,7 @@ Valid input for this parameter is an integer or the value unlimited. The default
 
 In Exchange 2010, if you set this value to 51 or higher, you also need to use the AcceptLargeDataLoss switch. Otherwise, the command will fail.
 
-**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics will be used instead.
+**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics are used instead.
 
 ```yaml
 Type: Unlimited
@@ -274,7 +274,7 @@ Valid input for this parameter is an integer or the value unlimited. The default
 
 If you set this value to 51 or higher, you also need to use the AcceptLargeDataLoss switch. Otherwise, the command will fail.
 
-**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics will be used instead.
+**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics are used instead.
 
 ```yaml
 Type: Unlimited
@@ -299,7 +299,7 @@ The Priority parameter specifies the order in which the request should be proces
 - Lowest
 - Lower
 - Low
-- Normal: This is the default value.
+- Normal: This value is the default.
 - High
 - Higher
 - Highest
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxJunkEmailConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxJunkEmailConfiguration.md
index 5dde63a4e1..7c763e94da 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxJunkEmailConfiguration.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxJunkEmailConfiguration.md
@@ -13,7 +13,7 @@ title: Set-MailboxJunkEmailConfiguration
 # Set-MailboxJunkEmailConfiguration
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-MailboxJunkEmailConfiguration cmdlet to configure the junk email settings on mailboxes.
 
@@ -51,7 +51,7 @@ This cmdlet controls the following junk email settings on the mailbox:
 
 For more information, see [Configure Exchange antispam settings on mailboxes](https://learn.microsoft.com/Exchange/antispam-and-antimalware/antispam-protection/configure-antispam-settings).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -160,7 +160,7 @@ Accept wildcard characters: False
 The ContactsTrusted parameter specifies whether the contacts in the Contacts folder are treated as trusted senders. This parameter corresponds to the Outlook on the web setting: Trust email from my contacts. Valid values are:
 
 - $true: Messages from contacts in the Contacts folder that reach the mailbox are never delivered to the Junk Email folder, regardless of the content.
-- $false: Messages from contacts in the Contacts folder aren't treated as trusted senders. The email address is a trusted sender only if it's defined in the Safe Senders list. This is the default value.
+- $false: Messages from contacts in the Contacts folder aren't treated as trusted senders. The email address is a trusted sender only if it's defined in the Safe Senders list. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -200,7 +200,7 @@ Accept wildcard characters: False
 
 The Enabled parameter enables or disables the junk email rule on the mailbox (a hidden Inbox rule named Junk E-mail Rule). Valid values are:
 
-- $true: The junk email rule is enabled in the mailbox. This value corresponds to the Outlook on the web setting: Automatically filter junk email. This is the default value.
+- $true: The junk email rule is enabled in the mailbox. This value corresponds to the Outlook on the web setting: Automatically filter junk email. This value is the default.
 
   In on-premises Exchange, the safelist collection of the mailbox (the Safe Senders list, Safe Recipients list, and Blocked Senders list), and the SCL Junk Email folder threshold (for the organization or the mailbox) delivers messages to the Inbox or the Junk Email folder.
 
@@ -301,7 +301,7 @@ Accept wildcard characters: False
 The TrustedListsOnly parameter specifies that only messages from senders in the Safe Senders list are delivered to the Inbox. All other messages are treated as junk email. This parameter corresponds to the Outlook on the web setting: Don't trust email unless it comes from someone in my Safe Senders and Recipients list. Valid values are:
 
 - $true: Only messages from email address or domain entries in the Safe Senders list and the Safe Recipients list are delivered to the Inbox. All other messages are automatically delivered to the Junk Email folder.
-- $false: Messages from other senders, recipients, and domains aren't automatically treated as junk email, and are evaluated individually. This is the default value.
+- $false: Messages from other senders, recipients, and domains aren't automatically treated as junk email, and are evaluated individually. This value is the default.
 
 ```yaml
 Type: Boolean
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxMessageConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxMessageConfiguration.md
index eb2d6eb0aa..40134436a3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxMessageConfiguration.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxMessageConfiguration.md
@@ -13,7 +13,7 @@ title: Set-MailboxMessageConfiguration
 # Set-MailboxMessageConfiguration
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-MailboxMessageConfiguration cmdlet to configure the Outlook on the web settings that are applied to specific mailboxes.
 
@@ -94,7 +94,7 @@ Set-MailboxMessageConfiguration [-Identity] <MailboxIdParameter>
 ## DESCRIPTION
 The Set-MailboxMessageConfiguration cmdlet configures Outlook on the web settings for the specified mailbox. These settings include email signature, message format, message options, read receipts, reading pane, and conversations. These settings are not used in Outlook, Exchange ActiveSync, or other email clients. These settings are applied in Outlook on the web only. Some settings also apply to the new Outlook client. Settings that contain the word Mobile are applied in Outlook on the web for devices only.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -581,7 +581,7 @@ This parameter is available only in the cloud-based service.
 The EchoGroupMessageBackToSubscribedSender parameter controls whether subscribed members of Microsoft 365 Groups receive copies of messages that they send to those Groups. Valid values are:
 
 - $true: If a subscribed member of a Microsoft 365 Group sends a message to that Group, they'll receive a copy of the message in their Inbox.
-- $false: Subscribed members of a Microsoft 365 Group don't receive their own copies of messages that they send to the Group. This is the default value.
+- $false: Subscribed members of a Microsoft 365 Group don't receive their own copies of messages that they send to the Group. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -603,7 +603,7 @@ This parameter is functional only in on-premises Exchange.
 
 The EmailComposeMode parameter specifies how the user creates messages in Outlook on the web. You can use the following values:
 
-- Inline: New messages and replies are created in the preview pane. This is the default value.
+- Inline: New messages and replies are created in the preview pane. This value is the default.
 - SeparateForm: New messages and replies are created in a new browser window.
 
 ```yaml
@@ -668,7 +668,7 @@ The GlobalReadingPanePosition specifies the default location of the reading pane
 
 - Off
 - Bottom
-- Right (This is the default value)
+- Right (default value)
 
 ```yaml
 Type: MailReadingPanePosition
@@ -752,7 +752,7 @@ Accept wildcard characters: False
 The IsFavoritesFolderTreeCollapsed parameter specifies whether to collapse the Favorites folder tree by default in Outlook on the web. Valid values are:
 
 - $true: The Favorites folder tree is collapsed by default.
-- $false: The Favorites folder tree isn't collapsed by default. This is the default value
+- $false: The Favorites folder tree isn't collapsed by default. This value is the default
 
 ```yaml
 Type: Boolean
@@ -793,7 +793,7 @@ Accept wildcard characters: False
 The IsMailRootFolderTreeCollapsed parameter specifies whether to collapse the Mail root folder tree by default in Outlook on the web. Valid values are:
 
 - $true: The Mail root folder tree is collapsed by default.
-- $false: The Mail root folder tree isn't collapsed by default. This is the default value
+- $false: The Mail root folder tree isn't collapsed by default. This value is the default
 
 ```yaml
 Type: Boolean
@@ -813,7 +813,7 @@ Accept wildcard characters: False
 
 The IsReplyAllTheDefaultResponse parameter specifies whether Reply All is the default response for messages in Outlook on the web. Valid values are:
 
-- $true: Reply All is the default response option for messages in the reading pane. This is the default value.
+- $true: Reply All is the default response option for messages in the reading pane. This value is the default.
 - $false: Reply All isn't the default response option for messages in the reading pane.
 
 ```yaml
@@ -834,7 +834,7 @@ Accept wildcard characters: False
 
 The LinkPreviewEnabled parameter specifies whether link preview of URLs in email messages is enabled for the user in Outlook on the web. Valid values are:
 
-- $true: Link preview of URLs in email messages is enabled for the user. This is the default value.
+- $true: Link preview of URLs in email messages is enabled for the user. This value is the default.
 - $false: Link preview of URLs in email messages is disabled for the user.
 
 This parameter depends on the value of the LinkPreviewEnabled parameter on the Set-OrganizationConfig cmdlet, which controls the link preview behavior in Outlook on the web for the entire organization. If link preview is disabled for the organization, users can't enable it for themselves.
@@ -857,7 +857,7 @@ Accept wildcard characters: False
 
 The MailFolderPaneExpanded parameter specifies whether the Mail folder pane is expanded by default in Outlook on the web. Valid values are:
 
-- $true: The Mail folder pane is expanded by default. This is the default value.
+- $true: The Mail folder pane is expanded by default. This value is the default.
 - $false: The Mail folder pane isn't expanded by default.
 
 ```yaml
@@ -938,7 +938,7 @@ Accept wildcard characters: False
 
 The NavigationPaneViewOption parameter specifies the default navigation pane view in Outlook on the web. Valid values are:
 
-- Default: This is the default value
+- Default: This value is the default
 - MailFolders
 - PeopleFolders
 - Groups
@@ -1010,7 +1010,7 @@ Accept wildcard characters: False
 The PreferAccessibleContent parameter specifies whether to prefer accessible content in Outlook on the web. Valid values are:
 
 - $true: Prefer accessible content.
-- $false: Don't prefer accessible content. This is the default value.
+- $false: Don't prefer accessible content. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -1213,7 +1213,7 @@ Accept wildcard characters: False
 
 The ShowPreviewTextInListView parameter specifies whether to show preview text for messages in list view in Outlook on the web. Valid values are:
 
-- $true: Show preview text for messages in list view. This is the default value.
+- $true: Show preview text for messages in list view. This value is the default.
 - $false: Don't show preview text for messages in list view.
 
 ```yaml
@@ -1235,7 +1235,7 @@ Accept wildcard characters: False
 The ShowReadingPaneOnFirstLoad parameter specifies whether to show the reading pane when the user opens in Outlook on the web for the first time. Valid values are:
 
 - $true: Show the reading pane when the user opens Outlook on the web for the first time.
-- $false: Don't show the reading pane when the user opens Outlook on the web for the first time. This is the default value.
+- $false: Don't show the reading pane when the user opens Outlook on the web for the first time. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -1255,7 +1255,7 @@ Accept wildcard characters: False
 
 The ShowSenderOnTopInListView parameter specifies whether to show the message sender on top in list view in Outlook on the web. Valid values are:
 
-- $true: Show the message sender on top in list view. This is the default value.
+- $true: Show the message sender on top in list view. This value is the default.
 - $false: Don't show the message sender on top in list view.
 
 ```yaml
@@ -1276,7 +1276,7 @@ Accept wildcard characters: False
 
 The ShowUpNext parameter specifies whether the next upcoming event should be shown above the mail list view in Outlook on the web. Valid values are:
 
-- $true: Show the next upcoming event above the mail list view. This is the default value.
+- $true: Show the next upcoming event above the mail list view. This value is the default.
 - $false: Don't show the next upcoming event above the mail list view.
 
 ```yaml
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxPlan.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxPlan.md
index 0edf3ce269..746b24f47e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxPlan.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxPlan.md
@@ -42,11 +42,11 @@ Set-MailboxPlan [-Identity] <MailboxPlanIdParameter>
 ## DESCRIPTION
 A mailbox plan is a template that automatically configures mailbox properties. Mailbox plans correspond to license types, and are applied when you license the user. The availability of a mailbox plan is determined by your selections when you enroll in the service and the age of your organization.
 
-Modifying the settings in a mailbox plan doesn't affect existing mailboxes that were created using the mailbox plan. The only way to use a mailbox plan to modify the settings on an existing mailbox is to assign a different license to the user, which will apply the corresponding mailbox plan to the mailbox.
+Modifying the settings in a mailbox plan doesn't affect existing mailboxes that were created using the mailbox plan. The only way to use a mailbox plan to modify the settings on an existing mailbox is to assign a different license to the user, which applies the corresponding mailbox plan to the mailbox.
 
 Each mailbox plan has a corresponding Client Access services (CAS) mailbox plan with the same name and display name value. You can use the Set-CasMailboxPlan cmdlet to enable or disable POP3, IMAP4 or Exchange ActiveSync (EAS) access to new or newly-enabled mailboxes, and you can specify the Outlook on the web (formerly known as Outlook Web App) mailbox policy for the mailboxes.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -158,11 +158,11 @@ A valid value is a number up to 1.999999999 terabytes (2199023254528 bytes) or t
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The IssueWarningQuota value must be less than or equal to the ProhibitSendReceiveQuota value.
 
-The maximum value is determined by the mailbox plan. You can lower the value, and you may be able to raise the value, but you can't exceed the maximum value that's specified by the subscription or license that corresponds to the mailbox plan.
+The maximum value is determined by the mailbox plan. You can lower the value, and you might be able to raise the value, but you can't exceed the maximum value that's specified by the subscription or license that corresponds to the mailbox plan.
 
 ```yaml
 Type: Unlimited
@@ -188,11 +188,11 @@ When you enter a value, qualify the value with one of the following units:
 - KB (kilobytes)
 - MB (megabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 A valid value is a number up to 150 MB. The default value is 36 MB.
 
-The maximum value is determined by the mailbox plan (subscriptions and licenses). You can lower the value, and you may be able to raise the value, but you can't exceed the maximum value that's specified by the subscription or license that corresponds to the mailbox plan.
+The maximum value is determined by the mailbox plan (subscriptions and licenses). You can lower the value, and you might be able to raise the value, but you can't exceed the maximum value that's specified by the subscription or license that corresponds to the mailbox plan.
 
 Use this parameter to change the MaxReceiveSize value for new mailboxes that you create. Use the MaxReceiveSize parameter on the Set-Mailbox cmdlet to configure the value on existing mailboxes.
 
@@ -222,11 +222,11 @@ When you enter a value, qualify the value with one of the following units:
 - KB (kilobytes)
 - MB (megabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 A valid value is a number up to 150 MB. The default value is 35 MB.
 
-The maximum value is determined by the mailbox plan (subscriptions and licenses). You can lower the value, and you may be able to raise the value, but you can't exceed the maximum value that's specified by the subscription or license that corresponds to the mailbox plan.
+The maximum value is determined by the mailbox plan (subscriptions and licenses). You can lower the value, and you might be able to raise the value, but you can't exceed the maximum value that's specified by the subscription or license that corresponds to the mailbox plan.
 
 Use this parameter to change the MaxSendSize value for new mailboxes that you create. Use the MaxSendSize parameter on the Set-Mailbox cmdlet to configure the value on existing mailboxes.
 
@@ -258,11 +258,11 @@ A valid value is a number up to 1.999999999 terabytes (2199023254528 bytes) or t
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The ProhibitSendQuota value must be less than or equal to the ProhibitSendReceiveQuota value.
 
-The maximum value is determined by the mailbox plan. You can lower the value, and you may be able to raise the value, but you can't exceed the maximum value that's specified by the subscription or license that corresponds to the mailbox plan.
+The maximum value is determined by the mailbox plan. You can lower the value, and you might be able to raise the value, but you can't exceed the maximum value that's specified by the subscription or license that corresponds to the mailbox plan.
 
 ```yaml
 Type: Unlimited
@@ -290,7 +290,7 @@ A valid value is a number up to 1.999999999 terabytes (2199023254528 bytes) or t
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value must be greater than or equal to the ProhibitSendQuota or IssueWarningQuota values.
 
@@ -375,7 +375,7 @@ If you don't set a value for this parameter, existing mailboxes are also updated
 **Note**: Specifying a value for this parameter has the following potential issues:
 
 - If the value of this parameter is not blank ($null), then the specified retention policy must be the default Exchange retention policy that's configured for the organization. Otherwise, the experience might be inconsistent when creating new mailboxes, enabling disabled mailboxes, and changing licenses.
-- If a mailbox is assigned an Exchange retention policy that's not the default policy, the RetentionPolicy value of the mailbox will be overwritten when changing licenses and will need to be manually reset to the original value.
+- If a mailbox is assigned an Exchange retention policy that's not the default policy, the RetentionPolicy value of the mailbox is overwritten when changing licenses. You need to manually reset the RetentionPolicy to the original value.
 - Changes to the default retention policy that affect existing mailboxes can potentially saturate the network if there are hundreds or thousands of mailboxes that require updates.
 
 For more information, see [Mailbox plans in Exchange Online](https://learn.microsoft.com/exchange/recipients-in-exchange-online/manage-user-mailboxes/mailbox-plans).
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxRegionalConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxRegionalConfiguration.md
index 3349fad8d4..d9fdf8c9c0 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxRegionalConfiguration.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxRegionalConfiguration.md
@@ -13,7 +13,7 @@ title: Set-MailboxRegionalConfiguration
 # Set-MailboxRegionalConfiguration
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-MailboxRegionalConfiguration cmdlet to modify the regional settings of a mailbox. You can modify the date format, time format, time zone and language of the mailbox.
 
@@ -63,7 +63,7 @@ Set-MailboxRegionalConfiguration [-MailboxLocation <MailboxLocationIdParameter>]
 ## DESCRIPTION
 As shown in Example 5, you might need to set the DateFormat and TimeFormat parameter values to $null when you change the Language parameter value and you receive an error about invalid DateFormat values.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -180,7 +180,7 @@ Accept wildcard characters: False
 
 The DateFormat parameter specifies a valid date format based on the current or specified language for the mailbox. For example, if the language is set to en-US, valid DateFormat parameter values include:
 
-- M/d/yyyy: This is the default value for en-US.
+- M/d/yyyy: This value is the default for en-US.
 - M/d/yy
 - MM/dd/yy
 - MM/dd/yyyy
@@ -286,7 +286,7 @@ Accept wildcard characters: False
 
 The TimeFormat parameter specifies a valid time format based on the current or specified language value for the mailbox. For example, if the language is set to en-us, valid TimeFormat parameter values include:
 
-- h:mm tt: This is the default value for en-US.
+- h:mm tt: This value is the default for en-US.
 - hh:mm tt
 - H:mm
 - HH:mm
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxRestoreRequest.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxRestoreRequest.md
index 31a09c45f0..fc864e68e8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxRestoreRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxRestoreRequest.md
@@ -13,9 +13,9 @@ title: Set-MailboxRestoreRequest
 # Set-MailboxRestoreRequest
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
-Use the Set-MailboxRestoreRequest cmdlet to change restore request options after the request has been created. You can use this cmdlet to recover from failed restore requests.
+Use the Set-MailboxRestoreRequest cmdlet to change restore request options after the request is created. You can use this cmdlet to recover from failed restore requests.
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
@@ -61,7 +61,7 @@ Set-MailboxRestoreRequest [-Identity] <MailboxRestoreRequestIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -133,7 +133,7 @@ Valid input for this parameter is an integer or the value unlimited. The default
 
 In Exchange 2010, if you set this value to 51 or higher, you also need to use the AcceptLargeDataLoss switch. Otherwise, the command will fail.
 
-**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics will be used instead.
+**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics are used instead.
 
 ```yaml
 Type: Unlimited
@@ -261,7 +261,7 @@ Valid input for this parameter is an integer or the value unlimited. The default
 
 If you set this value to 51 or higher, you also need to use the AcceptLargeDataLoss switch. Otherwise, the command will fail.
 
-**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics will be used instead.
+**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics are used instead.
 
 ```yaml
 Type: Unlimited
@@ -286,7 +286,7 @@ The Priority parameter specifies the order in which the request should be proces
 - Lowest
 - Lower
 - Low
-- Normal: This is the default value.
+- Normal: This value is the default.
 - High
 - Higher
 - Highest
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxSearch.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxSearch.md
index 87fa9b177c..0e5035c4d9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxSearch.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxSearch.md
@@ -13,7 +13,7 @@ title: Set-MailboxSearch
 # Set-MailboxSearch
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-MailboxSearch cmdlet to modify an existing mailbox search.
 
@@ -65,7 +65,7 @@ If the In-Place eDiscovery search you want to modify is running, stop it before
 
 For more information, see [In-Place eDiscovery in Exchange Server](https://learn.microsoft.com/Exchange/policy-and-compliance/ediscovery/ediscovery) and [In-Place Hold and Litigation Hold in Exchange Server](https://learn.microsoft.com/Exchange/policy-and-compliance/holds/holds).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -112,7 +112,7 @@ Accept wildcard characters: False
 The AllPublicFolderSources parameter specifies whether to include all public folders in the organization in the search. Valid values are:
 
 - $true: All public folders are included in the search. This value is required when the value of the AllSourceMailboxes parameter is $falseand you don't specify one or more source mailboxes by using the SourceMailboxes parameter (the parameter value is blank [$null]).
-- $false: No public folders are included in the search. This is the default value. You can use this value when the value of the AllSourceMailboxes parameter is $trueor you specify one or more source mailboxes by using the SourceMailboxes parameter (the parameter value isn't blank [$null]).
+- $false: No public folders are included in the search. This value is the default. You can use this value when the value of the AllSourceMailboxes parameter is $trueor you specify one or more source mailboxes by using the SourceMailboxes parameter (the parameter value isn't blank [$null]).
 
 ```yaml
 Type: Boolean
@@ -133,7 +133,7 @@ Accept wildcard characters: False
 The AllSourceMailboxes parameter specifies whether to include all mailboxes in the search. Valid values are:
 
 - $true: All mailboxes are included in the search. This value is required when the value of the AllPublicFolderSources parameter is $falseand you don't specify one or more source mailboxes by using the SourceMailboxes parameter (the parameter value is blank [$null]).
-- $false: All mailboxes aren't included in the search. This is the default value. You can use this value when the value of the AllPublicFolderSources parameter is $trueor you specify one or more source mailboxes by using the SourceMailboxes parameter (the parameter value isn't blank [$null]).
+- $false: All mailboxes aren't included in the search. This value is the default. You can use this value when the value of the AllPublicFolderSources parameter is $trueor you specify one or more source mailboxes by using the SourceMailboxes parameter (the parameter value isn't blank [$null]).
 
 ```yaml
 Type: Boolean
@@ -274,7 +274,7 @@ Accept wildcard characters: False
 
 The ExcludeDuplicateMessages parameter eliminates duplication of messages across mailboxes in an In-Place eDiscovery search. Valid values are:
 
-- $true: Copy a single instance of a message if the same message exists in multiple folders or mailboxes. This is the default value.
+- $true: Copy a single instance of a message if the same message exists in multiple folders or mailboxes. This value is the default.
 - $false: Copy all instances of a message if the same message exists in multiple folders or mailboxes.
 
 ```yaml
@@ -334,7 +334,7 @@ Accept wildcard characters: False
 The IncludeUnsearchableItems parameter specifies whether items that couldn't be indexed by Exchange Search should be included in the results. Valid values are:
 
 - $true: Unsearchable items are included in the results.
-- $false: Unsearchable items aren't included in the results. This is the default value.
+- $false: Unsearchable items aren't included in the results. This value is the default.
 
 Unsearchable items aren't placed on hold for a query-based In-Place Hold. If you need to place unsearchable items on hold, you need to create an indefinite hold (a hold without specifying any search parameters, which provides functionality similar to Litigation Hold.
 
@@ -357,11 +357,11 @@ Accept wildcard characters: False
 The InPlaceHoldEnabled parameter specifies whether to set an In-Place Hold on items in the search results. Valid values are:
 
 - $true: In-Place Hold is enabled on the search results.
-- $false: In-Place Hold isn't enabled on the search results. This is the default value.
+- $false: In-Place Hold isn't enabled on the search results. This value is the default.
 
 You can't set an In-Place Hold on the search results when the AllSourceMailboxes parameter is $true.
 
-If you attempt to place a hold but don't specify mailboxes using the SourceMailboxes parameter, the command may succeed but the mailboxes are not placed on In-Place Hold.
+If you attempt to place a hold but don't specify mailboxes using the SourceMailboxes parameter, the command might succeed but the mailboxes are not placed on In-Place Hold.
 
 ```yaml
 Type: Boolean
@@ -382,7 +382,7 @@ Accept wildcard characters: False
 The ItemHoldPeriod parameter specifies the number of days for the In-Place Hold onthe mailbox items (all items or the mailbox items that are returned in the search query results). You use this parameter with the InPlaceHoldEnabled parameter to set an In-Place Hold. The duration is calculated from the time the item is received or created in the mailbox. Valid values are:
 
 - An integer.
-- The value unlimited. This is the default value. Items are held until you remove the In-Place Hold by removing the search by using the Remove-MailboxSearch cmdlet, removing the source mailbox from the search by using the Set-MailboxSearch cmdlet and the SourceMailboxes parameter, or in on-premises Exchange, you remove all public folders from the search by using the Set-MailboxSearch cmdlet to change the AllPublicFolderSources parameter from $true to $false.
+- The value unlimited. This value is the default. Items are held until you remove the In-Place Hold by removing the search by using the Remove-MailboxSearch cmdlet, removing the source mailbox from the search by using the Set-MailboxSearch cmdlet and the SourceMailboxes parameter, or in on-premises Exchange, you remove all public folders from the search by using the Set-MailboxSearch cmdlet to change the AllPublicFolderSources parameter from $true to $false.
 
 ```yaml
 Type: Unlimited
@@ -422,7 +422,7 @@ Accept wildcard characters: False
 
 The LogLevel parameter specifies a logging level for the mailbox search. Valid values are:
 
-- Basic: Basic details of the search are kept. This is the default value.
+- Basic: Basic details of the search are kept. This value is the default.
 - Full: In addition to details in the Basic logging level, a full list of all messages returned is included.
 - Suppress: Logging is suppressed. No logs are kept.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxSentItemsConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxSentItemsConfiguration.md
index 144b54ea09..7a2d21ab4e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxSentItemsConfiguration.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxSentItemsConfiguration.md
@@ -34,7 +34,7 @@ Set-MailboxSentItemsConfiguration [-Confirm]
 ## DESCRIPTION
 By default, when you use Send As or Send On Behalf Of to send a message from another mailbox, the message is saved in your Sent Items folder (not in the Sent Items folder of the source mailbox). In Microsoft Exchange Server 2010 Service Pack 3 (SP3), you can save copies messages in the Sent Items folder of the sender and the source mailbox. For example, consider a shared mailbox that receives customer feedback and is monitored by multiple users. When someone responds to a message in the shared mailbox, you can save the message in the Sent Items folder of the shared mailbox and the sender's mailbox.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -121,7 +121,7 @@ Accept wildcard characters: False
 
 The SendAsItemsCopiedTo parameter specifies where messages that are sent from the mailbox using Send As permission are saved. Valid values are:
 
-- Sender: Messages sent from the mailbox are saved in the Sent Items folder of the user who sent the message. This is the default value.
+- Sender: Messages sent from the mailbox are saved in the Sent Items folder of the user who sent the message. This value is the default.
 - SenderAndFrom: Messages sent from the mailbox are saved in the Sent Items folder of the user who sent the message, and in the Sent Items folder of the mailbox.
 
 ```yaml
@@ -142,7 +142,7 @@ Accept wildcard characters: False
 
 The SendOnBehalfOfItemsCopiedTo parameter specifies where messages that are sent from the mailbox using Send On Behalf Of permission are saved. Valid values are:
 
-- Sender: Messages sent from the mailbox are saved in the Sent Items folder of the user who sent the message. This is the default value.
+- Sender: Messages sent from the mailbox are saved in the Sent Items folder of the user who sent the message. This value is the default.
 - SenderAndFrom: Messages sent from the mailbox are saved in the Sent Items folder of the user who sent the message, and in the Sent Items folder of the mailbox.
 
 ```yaml
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxServer.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxServer.md
index bed67ec315..7748bd0a40 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxServer.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxServer.md
@@ -131,7 +131,7 @@ Set-MailboxServer [-Identity] <MailboxServerIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -140,7 +140,7 @@ You need to be assigned permissions before you can run this cmdlet. Although thi
 Set-MailboxServer -Identity MBX02 -CalendarRepairWorkCycle 7.00:00:00 -CalendarRepairWorkCycleCheckpoint 7.00:00:00
 ```
 
-In Exchange 2013, this example throttles the Calendar Repair Assistant to detect and repair calendar inconsistencies for the Mailbox server MBX02 in a 7-day period. During that 7-day period, all mailboxes will be scanned, and at the end of the period, the process will start over.
+In Exchange 2013, this example throttles the Calendar Repair Assistant to detect and repair calendar inconsistencies for the Mailbox server MBX02 in a 7-day period. During that 7-day period, all mailboxes are scanned, and at the end of the period, the process starts over.
 
 ### Example 2
 ```powershell
@@ -154,42 +154,42 @@ This example changes some of the default settings of the Calendar Repair Assista
 Set-MailboxServer -Identity MBX02 -CalendarRepairWorkCycle 7.00:00:00 -CalendarRepairWorkCycleCheckpoint 7.00:00:00
 ```
 
-In Exchange 2010, this example throttles the Calendar Repair Assistant to detect and repair calendar inconsistencies for the Mailbox server MBX02 in a 7-day period. During that 7-day period, all mailboxes will be scanned, and at the end of the period, the process will start over.
+In Exchange 2010, this example throttles the Calendar Repair Assistant to detect and repair calendar inconsistencies for the Mailbox server MBX02 in a 7-day period. During that 7-day period, all mailboxes are scanned, and at the end of the period, the process starts over.
 
 ### Example 4
 ```powershell
 Set-MailboxServer -Identity MBX02 -ManagedFolderWorkCycle 10.00:00:00 -ManagedFolderWorkCycleCheckpoint 10.00:00:00
 ```
 
-In Exchange 2013, this example throttles the Managed Folder Assistant, which applies message retention settings to all mailboxes for the Mailbox server MBX02 in a 10-day period. During that 10-day period, all mailboxes will be scanned, and at the end of the period, the process will start over.
+In Exchange 2013, this example throttles the Managed Folder Assistant, which applies message retention settings to all mailboxes for the Mailbox server MBX02 in a 10-day period. During that 10-day period, all mailboxes are scanned, and at the end of the period, the process starts over.
 
 ### Example 5
 ```powershell
 Set-MailboxServer -Identity MBX02 -ManagedFolderWorkCycle 10.00:00:00 -ManagedFolderWorkCycleCheckpoint 10.00:00:00
 ```
 
-In Exchange 2010, this example throttles the Managed Folder Assistant, which applies message retention settings to all mailboxes for the Mailbox server MBX02 in a 10-day period. During that 10-day period, all mailboxes will be scanned, and at the end of the period, the process will start over.
+In Exchange 2010, this example throttles the Managed Folder Assistant, which applies message retention settings to all mailboxes for the Mailbox server MBX02 in a 10-day period. During that 10-day period, all mailboxes are scanned, and at the end of the period, the process starts over.
 
 ### Example 6
 ```powershell
 Set-MailboxServer -Identity MBX02 -SharingPolicyWorkCycle 7.00:00:00 -SharingPolicyWorkCycleCheckpoint 7.00:00:00 -SharingSyncWorkCycle 7.00:00:00 -SharingSyncWorkCycleCheckpoint 7.00:00:00
 ```
 
-In Exchange 2013, this example throttles the Sharing Policy and Sharing Sync Assistants to apply sharing policies, sync shared calendars, and free/busy information for the mailboxes on server MBX02 in a 7-day period. During that 7-day period, all mailboxes will be scanned, and at the end of the period, the process will start over.
+In Exchange 2013, this example throttles the Sharing Policy and Sharing Sync Assistants to apply sharing policies, sync shared calendars, and free/busy information for the mailboxes on server MBX02 in a 7-day period. During that 7-day period, all mailboxes are scanned, and at the end of the period, the process starts over.
 
 ### Example 7
 ```powershell
 Set-MailboxServer -Identity MBX02 -SharingPolicyWorkCycle 7.00:00:00 -SharingPolicyWorkCycleCheckpoint 7.00:00:00 -SharingSyncWorkCycle 7.00:00:00 -SharingSyncWorkCycleCheckpoint 7.00:00:00
 ```
 
-In Exchange 2010, this example throttles the Sharing Policy and Sharing Sync Assistants to apply sharing policies, sync shared calendars, and free/busy information for the mailboxes on server MBX02 in a 7-day period. During that 7-day period, all mailboxes will be scanned, and at the end of the period, the process will start over.
+In Exchange 2010, this example throttles the Sharing Policy and Sharing Sync Assistants to apply sharing policies, sync shared calendars, and free/busy information for the mailboxes on server MBX02 in a 7-day period. During that 7-day period, all mailboxes are scanned, and at the end of the period, the process starts over.
 
 ### Example 8
 ```powershell
 Set-MailboxServer -Identity MBX02 -TopNWorkCycle 10.00:00:00 -TopNWorkCycleCheckpoint 10.00:00:00 -UMReportingWorkCycle 10.00:00:00 -UMReportingWorkCycleCheckpoint 10.00:00:00
 ```
 
-In Exchange 2010, this example throttles the TopN Words Assistant and the Unified Messaging Reporting Assistant for mailboxes that reside on the Mailbox server MBX02 in a 10-day period. During that 10-day period, all mailboxes that have Unified Messaging enabled will be scanned, and at the end of the period, the process will start over.
+In Exchange 2010, this example throttles the TopN Words Assistant and the Unified Messaging Reporting Assistant for mailboxes that reside on the Mailbox server MBX02 in a 10-day period. During that 10-day period, all mailboxes that have Unified Messaging enabled are scanned, and at the end of the period, the process starts over.
 
 ## PARAMETERS
 
@@ -243,7 +243,7 @@ The AutoDatabaseMountDial parameter specifies the automatic database mount behav
 - GoodAvailability: The database automatically mounts immediately after a failover if the copy queue length is less than or equal to six. The copy queue length is the number of logs recognized by the passive copy that needs to be replicated. If the copy queue length is more than six, the database doesn't automatically mount. When the copy queue length is less than or equal to six, Exchange attempts to replicate the remaining logs to the passive copy and mounts the database.
 - Lossless: The database doesn't automatically mount until all logs that were generated on the active copy have been copied to the passive copy. This setting also causes Active Manager's best copy selection algorithm to sort potential candidates for activation based on the database copy's activation preference value and not its copy queue length.
 
-The default value is GoodAvailability. If you specify either BestAvailability or GoodAvailability, and all of the logs from the active copy haven't been replicated to the passive copy, you may lose some mailbox data. However, the Safety Net feature, (which is enabled by default) helps protect against data loss by resubmitting messages that are in Safety Net.
+The default value is GoodAvailability. If you specify either BestAvailability or GoodAvailability, and all of the logs from the active copy haven't been replicated to the passive copy, you might lose some mailbox data. However, the Safety Net feature, (which is enabled by default) helps protect against data loss by resubmitting messages that are in Safety Net.
 
 ```yaml
 Type: AutoDatabaseMountDial
@@ -297,7 +297,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 If you enter the value unlimited, no size limit is imposed on the calendar repair log directory.
 
@@ -402,7 +402,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-The CalendarRepairMissingItemFixDisabled parameter specifies whether the Calendar Repair Assistant won't fix missing calendar items in mailboxes on the Mailbox server.Valid input for this parameter is $true or $false. The default value is $false.
+The CalendarRepairMissingItemFixDisabled parameter specifies whether the Calendar Repair Assistant fixes missing calendar items in mailboxes on the Mailbox server.Valid input for this parameter is $true or $false. The default value is $false.
 
 ```yaml
 Type: Boolean
@@ -481,13 +481,13 @@ Accept wildcard characters: False
 
 This parameter is available only in Exchange Server 2010 or Exchange Server 2013.
 
-The CalendarRepairWorkCycle parameter specifies the time span in which all mailboxes on the Mailbox server will be scanned by the Calendar Repair Assistant. The default value is 1 day.
+The CalendarRepairWorkCycle parameter specifies the time span in which all mailboxes on the Mailbox server are scanned by the Calendar Repair Assistant. The default value is 1 day.
 
-Calendars that have inconsistencies will be flagged and repaired according to the interval specified by the CalendarRepairWorkCycleCheckpoint parameter.
+Calendars that have inconsistencies are flagged and repaired according to the interval specified by the CalendarRepairWorkCycleCheckpoint parameter.
 
 To specify a value, enter it as a time span: dd.hh:mm:ss where d = days, h = hours, m = minutes, and s = seconds.
 
-For example, to specify 2 days for this parameter, use 2.00:00:00. The Calendar Repair Assistant will then process all mailboxes on this server every 2 days.
+For example, to specify 2 days for this parameter, use 2.00:00:00. The Calendar Repair Assistant then processes all mailboxes on this server every 2 days.
 
 ```yaml
 Type: EnhancedTimeSpan
@@ -507,11 +507,11 @@ Accept wildcard characters: False
 
 This parameter is available only in Exchange Server 2010 or Exchange Server 2013.
 
-The CalendarRepairWorkCycleCheckpoint parameter specifies the time span at which all mailboxes on the Mailbox server will be identified as needing work completed on them. The default value is 1 day.
+The CalendarRepairWorkCycleCheckpoint parameter specifies the time span at which all mailboxes on the Mailbox server are identified as needing work completed on them. The default value is 1 day.
 
 To specify a value, enter it as a time span: dd.hh:mm:ss where d = days, h = hours, m = minutes and s = seconds.
 
-For example, to specify 2 days for this parameter, use 2.00:00:00. The Calendar Repair Assistant will then process all mailboxes on this server every 2 days.
+For example, to specify 2 days for this parameter, use 2.00:00:00. The Calendar Repair Assistant then processes all mailboxes on this server every 2 days.
 
 ```yaml
 Type: EnhancedTimeSpan
@@ -590,11 +590,11 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-The DatabaseCopyActivationDisabledAndMoveNow parameter specifies whether to prevent databases from being mounted on this Mailbox server if there are other healthy copies of the databases on other Mailbox servers. It will also immediately move any mounted databases on the server to other servers if copies exist and are healthy.
+The DatabaseCopyActivationDisabledAndMoveNow parameter specifies whether to prevent databases from being mounted on this Mailbox server if there are other healthy copies of the databases on other Mailbox servers. It also immediately moves any mounted databases on the server to other servers if copies exist and are healthy.
 
 Valid input for this parameter is $true or $false. The default value is $false.
 
-Setting this parameter to $true won't cause databases to move to a server that has the DatabaseCopyAutoActivationPolicy parameter set to Blocked.
+Setting this parameter to $true doesn't cause databases to move to a server that has the DatabaseCopyAutoActivationPolicy parameter set to Blocked.
 
 ```yaml
 Type: Boolean
@@ -614,9 +614,9 @@ Accept wildcard characters: False
 
 The DatabaseCopyAutoActivationPolicy parameter specifies the type of automatic activation available for mailbox database copies on the specified Mailbox server. Valid values for this parameter are:
 
-- Blocked: Databases can't be automatically activated on the specified Mailbox server. In Exchange 2013 prior to Cumulative Update 7 (CU7), this setting stops server locator requests to the specified server, which prevents all client access to manually activated databases on the server if all DAG members are configured with a value of Blocked. In Exchange 2013 CU7 or later versions of Exchange, server locator requests are sent to a blocked server if no other Mailbox servers are available, thus client access is not impacted.
+- Blocked: Databases can't be automatically activated on the specified Mailbox server. In Exchange 2013 prior to Cumulative Update 7 (CU7), this setting stops server locator requests to the specified server, which prevents all client access to manually activated databases on the server if all DAG members are configured with a value of Blocked. In Exchange 2013 CU7 or later versions of Exchange, server locator requests are sent to a blocked server if no other Mailbox servers are available, thus client access isn't affected.
 - IntrasiteOnly: The database copy is allowed to be activated only on Mailbox servers in the same Active Directory site. This prevents cross-site failover and activation.
-- Unrestricted: There are no special restrictions on activating mailbox database copies on the specified Mailbox server. This is the default value.
+- Unrestricted: There are no special restrictions on activating mailbox database copies on the specified Mailbox server. This value is the default.
 
 ```yaml
 Type: DatabaseCopyAutoActivationPolicyType
@@ -1009,9 +1009,9 @@ Accept wildcard characters: False
 
 This parameter is available only in Exchange Server 2010.
 
-The IrmLogPath parameter specifies the default IRM log directory location. The default value is C:\\Program Files\\Microsoft\\Exchange Server\\ v14\\Logging\\IRMLogs.
+The IrmLogPath parameter specifies the default IRM log directory location. The default value is %ExchangeInstallPath%Logging\\IRMLogs.
 
-If you set the value of the IrmLogPath parameter to $null, you effectively disable IRM logging. However, if you set the value of the IrmLogPath parameter to $null when the value of the IrmLogEnabled parameter is $true, Exchange will log errors in the Application event log. The preferred way for disabling IRM logging is to set the IrmLogEnabled parameter to $false.
+If you set the value of this parameter to $null, you effectively disable IRM logging. However, if the value of the IrmLogEnabled parameter is $true, Exchange adds errors to the Application event log. The preferred way to disable IRM logging is to set the IrmLogEnabled parameter to $false.
 
 ```yaml
 Type: LocalLongFullPath
@@ -1029,9 +1029,10 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-The IsExcludedFromProvisioning parameter specifies that the Mailbox server isn't considered by the OAB provisioning load balancer. Valid input for this parameter is $true or $false. The default value is $false.
+The IsExcludedFromProvisioning parameter specifies that the Mailbox server isn't considered by the OAB provisioning load balancer. Valid values are:
 
-If you specify$true, the server won't be used for provisioning a new OAB or for moving existing OABs.
+- $true: The server isn't used for provisioning new OABs or for moving existing OABs.
+- $false: The server can be used for provisioning new OABs or for moving existing OABs. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -1131,7 +1132,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The default value is unlimited, which means no size limit is imposed on the managed folder log directory.
 
@@ -1187,7 +1188,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 If you enter the value unlimited, no size limit is imposed on a managed folder log file.
 
@@ -1334,13 +1335,13 @@ Accept wildcard characters: False
 
 This parameter is available only in Exchange Server 2010 or Exchange Server 2013.
 
-The ManagedFolderWorkCycle parameter specifies the time span in which all mailboxes on the Mailbox server will be processed by the Managed Folder Assistant. The default value is 1 day.
+The ManagedFolderWorkCycle parameter specifies the time span in which all mailboxes on the Mailbox server are processed by the Managed Folder Assistant. The default value is 1 day.
 
 The Managed Folder Assistant applies retention policies according to the ManagedFolderWorkCycleCheckpoint interval.
 
 To specify a value, enter it as a time span: dd.hh:mm:ss where d = days, h = hours, m = minutes and s = seconds.
 
-For example, to specify 2 days for this parameter, use 2.00:00:00. The Managed Folder Assistant will then process all mailboxes on this server every 2 days.
+For example, to specify 2 days for this parameter, use 2.00:00:00. The Managed Folder Assistant then processes all mailboxes on this server every 2 days.
 
 ```yaml
 Type: EnhancedTimeSpan
@@ -1360,9 +1361,9 @@ Accept wildcard characters: False
 
 This parameter is available only in Exchange Server 2010 or Exchange Server 2013.
 
-The ManagedFolderWorkCycleCheckpoint parameter specifies the time span at which to refresh the list of mailboxes on the Mailbox server so that new mailboxes that have been created or moved will be part of the work queue. The default value is 1 day.
+The ManagedFolderWorkCycleCheckpoint parameter specifies the time span at which to refresh the list of mailboxes on the Mailbox server so that new mailboxes that have been created or moved are part of the work queue. The default value is 1 day.
 
-Also, as mailboxes are prioritized, existing mailboxes that haven't been successfully processed for a long time will be placed higher in the queue and will have a greater chance of being processed again in the same work cycle.
+Also, as mailboxes are prioritized, existing mailboxes that haven't been successfully processed for a long time are placed higher in the queue and have a greater chance of being processed again in the same work cycle.
 
 To specify a value, enter it as a time span: dd.hh:mm:ss where d = days, h = hours, m = minutes and s = seconds.
 
@@ -1404,7 +1405,7 @@ Accept wildcard characters: False
 
 The MaximumActiveDatabases parameter specifies the maximum number of databases that can be mounted on the Mailbox server.
 
-When the maximum number is reached, the database copies on the server won't be activated if a failover or switchover occurs. If the copies are already active on a server, the Information Store on the server won't allow databases to be mounted.
+When the maximum number is reached, the database copies on the server isn't activated if a failover or switchover occurs. If the copies are already active on a server, the Information Store on the server doesn't allow databases to be mounted.
 
 The default value is blank ($null), which means no maximum value is configured.
 
@@ -1681,7 +1682,7 @@ Accept wildcard characters: False
 
 This parameter is available only in Exchange Server 2013.
 
-The OABGeneratorWorkCycle parameter specifies the time span in which the OAB generation on the Mailbox server will be processed. The default value is 8 hours.
+The OABGeneratorWorkCycle parameter specifies the time span in which the OAB generation on the Mailbox server are processed. The default value is 8 hours.
 
 To specify a value, enter it as a time span: dd.hh:mm:ss where d = days, h = hours, m = minutes and s = seconds.
 
@@ -2034,13 +2035,13 @@ Accept wildcard characters: False
 
 This parameter is available only in Exchange Server 2010 or Exchange Server 2013.
 
-The SharingPolicyWorkCycle parameter specifies the time span in which all mailboxes on the Mailbox server will be scanned by the Sharing Policy Assistant. The default value is 1 day.
+The SharingPolicyWorkCycle parameter specifies the time span in which all mailboxes on the Mailbox server are scanned by the Sharing Policy Assistant. The default value is 1 day.
 
 The Sharing Policy Assistant scans all mailboxes and enables or disables sharing policies according to the interval specified by the SharingPolicyWorkCycle.
 
 To specify a value, enter it as a time span: dd.hh:mm:ss where d = days, h = hours, m = minutes and s = seconds.
 
-For example, to specify 2 days for this parameter, use 2.00:00:00. The Sharing Policy Assistant will then process all mailboxes on this server every 2 days.
+For example, to specify 2 days for this parameter, use 2.00:00:00. The Sharing Policy Assistant then processes all mailboxes on this server every 2 days.
 
 ```yaml
 Type: EnhancedTimeSpan
@@ -2060,13 +2061,13 @@ Accept wildcard characters: False
 
 This parameter is available only in Exchange Server 2010 or Exchange Server 2013.
 
-The SharingPolicyWorkCycleCheckpoint parameter specifies the time span at which to refresh the list of mailboxes on the Mailbox server so that new mailboxes that have been created or moved will be part of the work queue. The default value is 1 day.
+The SharingPolicyWorkCycleCheckpoint parameter specifies the time span at which to refresh the list of mailboxes on the Mailbox server so that new mailboxes that have been created or moved are part of the work queue. The default value is 1 day.
 
-Also, as mailboxes are prioritized, existing mailboxes that haven't been successfully processed for a long time will be placed higher in the queue and will have a greater chance of being processed again in the same work cycle.
+Also, as mailboxes are prioritized, existing mailboxes that haven't been successfully processed for a long time are placed higher in the queue and have a greater chance of being processed again in the same work cycle.
 
 To specify a value, enter it as a time span: dd.hh:mm:ss where d = days, h = hours, m = minutes and s = seconds.
 
-For example, to specify 2 days for this parameter, use 2.00:00:00. The Sharing Policy Assistant will then process all mailboxes on this server every 2 days.
+For example, to specify 2 days for this parameter, use 2.00:00:00. The Sharing Policy Assistant then processes all mailboxes on this server every 2 days.
 
 ```yaml
 Type: EnhancedTimeSpan
@@ -2086,13 +2087,13 @@ Accept wildcard characters: False
 
 This parameter is available only in Exchange Server 2010 or Exchange Server 2013.
 
-The SharingSyncWorkCycle parameter specifies the time span in which all mailboxes on the Mailbox server will be synced to the cloud-based service by the Sharing Sync Assistant. The default value is 3 hours.
+The SharingSyncWorkCycle parameter specifies the time span in which all mailboxes on the Mailbox server are synced to the cloud-based service by the Sharing Sync Assistant. The default value is 3 hours.
 
-Mailboxes that require syncing will be synced according to the interval specified by the SharingSyncWorkCycleCheckpoint parameter.
+Mailboxes that require syncing are synced according to the interval specified by the SharingSyncWorkCycleCheckpoint parameter.
 
 To specify a value, enter it as a time span: dd.hh:mm:ss where d = days, h = hours, m = minutes and s = seconds.
 
-For example, to specify 8 hours for this parameter, use 08:00:00. The Sharing Sync Assistant will then process all mailboxes on this server every 8 hours.
+For example, to specify 8 hours for this parameter, use 08:00:00. The Sharing Sync Assistant then processes all mailboxes on this server every 8 hours.
 
 ```yaml
 Type: EnhancedTimeSpan
@@ -2112,13 +2113,13 @@ Accept wildcard characters: False
 
 This parameter is available only in Exchange Server 2010 or Exchange Server 2013.
 
-The SharingSyncWorkCycleCheckpoint parameter specifies the time span at which to refresh the list of mailboxes on the Mailbox server so that new mailboxes that have been created or moved will be part of the work queue. The default value is 3 hours.
+The SharingSyncWorkCycleCheckpoint parameter specifies the time span at which to refresh the list of mailboxes on the Mailbox server so that new mailboxes that have been created or moved are part of the work queue. The default value is 3 hours.
 
-Also, as mailboxes are prioritized, existing mailboxes that haven't been successfully processed for a long time will be placed higher in the queue and will have a greater chance of being processed again in the same work cycle.
+Also, as mailboxes are prioritized, existing mailboxes that haven't been successfully processed for a long time are placed higher in the queue and have a greater chance of being processed again in the same work cycle.
 
 To specify a value, enter it as a time span: dd.hh:mm:ss where d = days, h = hours, m = minutes, and s = seconds.
 
-For example, to specify 8 hours for this parameter, use 08:00:00. The Sharing Sync Assistant will then process all mailboxes on this server every 8 hours.
+For example, to specify 8 hours for this parameter, use 08:00:00. The Sharing Sync Assistant then processes all mailboxes on this server every 8 hours.
 
 ```yaml
 Type: EnhancedTimeSpan
@@ -2138,7 +2139,7 @@ Accept wildcard characters: False
 
 This parameter is available only in Exchange Server 2013.
 
-The SiteMailboxWorkCycle parameter specifies the time span in which the site mailbox information on the Mailbox server will be processed. The default value is 6 hours.
+The SiteMailboxWorkCycle parameter specifies the time span in which the site mailbox information on the Mailbox server are processed. The default value is 6 hours.
 
 To specify a value, enter it as a time span: dd.hh:mm:ss where d = days, h = hours, m = minutes and s = seconds.
 
@@ -2426,13 +2427,13 @@ Accept wildcard characters: False
 
 This parameter is available only in Exchange Server 2010 or Exchange Server 2013.
 
-The TopNWorkCycle parameter specifies the time span in which all mailboxes that have Unified Messaging on the Mailbox server will be scanned by the TopN Words Assistant. The default value is 7 days.
+The TopNWorkCycle parameter specifies the time span in which all mailboxes that have Unified Messaging on the Mailbox server are scanned by the TopN Words Assistant. The default value is 7 days.
 
 To specify a value, enter it as a time span: dd.hh:mm:ss where d = days, h = hours, m = minutes and s = seconds.
 
 The TopN Words Assistant scans voice mail for the most frequently used words to aid in transcription. The most common words are then indexed according to the interval specified by the TopNWorkCycleCheckpoint parameter.
 
-For example, to specify 10 days for this parameter, use 10.00:00:00. The TopN Words Assistant will then process all mailboxes on which Unified Messaging is enabled on this server every 10 days.
+For example, to specify 10 days for this parameter, use 10.00:00:00. The TopN Words Assistant then processes all mailboxes on which Unified Messaging is enabled on this server every 10 days.
 
 ```yaml
 Type: EnhancedTimeSpan
@@ -2452,13 +2453,13 @@ Accept wildcard characters: False
 
 This parameter is available only in Exchange Server 2010 or Exchange Server 2013.
 
-The TopNWorkCycleCheckpoint parameter specifies the time span at which to refresh the list of mailboxes on the Mailbox server so that new mailboxes that have been created or moved will be part of the work queue. The default value is 1 day.
+The TopNWorkCycleCheckpoint parameter specifies the time span at which to refresh the list of mailboxes on the Mailbox server so that new mailboxes that have been created or moved are part of the work queue. The default value is 1 day.
 
-Also, as mailboxes are prioritized, existing mailboxes that haven't been successfully processed for a long time will be placed higher in the queue and will have a greater chance of being processed again in the same work cycle.
+Also, as mailboxes are prioritized, existing mailboxes that haven't been successfully processed for a long time are placed higher in the queue and have a greater chance of being processed again in the same work cycle.
 
 To specify a value, enter it as a time span: dd.hh:mm:ss where d = days, h = hours, m = minutes and s = seconds.
 
-For example, to specify 2 days for this parameter, use 2.00:00:00. The TopN Words Assistant will then process all mailboxes on this server every 2 days.
+For example, to specify 2 days for this parameter, use 2.00:00:00. The TopN Words Assistant then processes all mailboxes on this server every 2 days.
 
 ```yaml
 Type: EnhancedTimeSpan
@@ -2478,15 +2479,15 @@ Accept wildcard characters: False
 
 This parameter is available only in Exchange Server 2010 or Exchange Server 2013.
 
-The UMReportingWorkCycle parameter specifies the time span in which the arbitration mailbox named SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9} on the Mailbox server will be scanned by the Unified Messaging Reporting Assistant. The default value is 1 day.
+The UMReportingWorkCycle parameter specifies the time span in which the arbitration mailbox named SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9} on the Mailbox server are scanned by the Unified Messaging Reporting Assistant. The default value is 1 day.
 
 The Unified Messaging Reporting Assistant updates the Call Statistics reports by reading Unified Messaging call data records for an organization on a regular basis.
 
 To specify a value, enter it as a time span: dd.hh:mm:ss where d = days, h = hours, m = minutes, and s = seconds.
 
-For example, to specify 2 days for this parameter, use 2.00:00:00. The Unified Messaging Reporting Assistant will then process all mailboxes that have Unified Messaging enabled on this server every 2 days.
+For example, to specify 2 days for this parameter, use 2.00:00:00. The Unified Messaging Reporting Assistant then processes all mailboxes that have Unified Messaging enabled on this server every 2 days.
 
-Changing the default work cycle for this assistant might impact the performance of the Mailbox server.
+Changing the default work cycle for this assistant might affect the performance of the Mailbox server.
 
 ```yaml
 Type: EnhancedTimeSpan
@@ -2506,7 +2507,7 @@ Accept wildcard characters: False
 
 This parameter is available only in Exchange Server 2010 or Exchange Server 2013.
 
-The UMReportingWorkCycleCheckpoint parameter specifies the time span at which the arbitration mailbox named SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9} on the Mailbox server will be marked by processing. The default value is 1 day.
+The UMReportingWorkCycleCheckpoint parameter specifies the time span at which the arbitration mailbox named SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9} on the Mailbox server are marked by processing. The default value is 1 day.
 
 To specify a value, enter it as a time span: dd.hh:mm:ss where d = days, h = hours, m = minutes, and s = seconds.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxSpellingConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxSpellingConfiguration.md
index 5dc0433512..ad74531f90 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxSpellingConfiguration.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxSpellingConfiguration.md
@@ -13,7 +13,7 @@ title: Set-MailboxSpellingConfiguration
 # Set-MailboxSpellingConfiguration
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-MailboxSpellingConfiguration cmdlet to modify Outlook on the web spelling checker options for a specified user. For example, you can set the dictionary language and configure the spelling checker to ignore mixed digits or words in all uppercase.
 
@@ -34,7 +34,7 @@ Set-MailboxSpellingConfiguration [-Identity] <MailboxIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxTransportService.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxTransportService.md
index 1cd0ab0e6a..98eb1644f0 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxTransportService.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxTransportService.md
@@ -72,7 +72,7 @@ Set-MailboxTransportService [-Identity] <MailboxTransportServerIdParameter>
 ## DESCRIPTION
 The Mailbox Transport service runs on all Mailbox servers and is responsible for delivering messages to and accepting messages from local mailbox databases using a remote procedure call (RPC). The Mailbox Transport service also uses SMTP to send messages to and from the Transport service that runs on all Mailbox servers for routing messages to their ultimate destinations.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -178,7 +178,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value of the ConnectivityLogMaxFileSize parameter must be less than or equal to the value of the ConnectivityLogMaxDirectorySize parameter. The valid input range for either parameter is from 1 through 9223372036854775807 bytes. If you enter a value of unlimited, no size limit is imposed on the connectivity log directory.
 
@@ -208,7 +208,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value of the ConnectivityLogMaxFileSize parameter must be less than or equal to the value of the ConnectivityLogMaxDirectorySize parameter. The valid input range for either parameter is from 1 through 9223372036854775807 bytes. If you enter a value of unlimited, no size limit is imposed on the connectivity log files.
 
@@ -336,7 +336,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value of the MailboxDeliveryAgentLogMaxFileSize parameter must be less than or equal to the value of the MailboxDeliveryAgentLogMaxDirectorySize parameter. If you enter a value of unlimited, no size limit is imposed on the agent log directory.
 
@@ -366,7 +366,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value of the MailboxDeliveryAgentLogMaxFileSize parameter must be less than or equal to the value of the MailboxDeliveryAgentLogMaxDirectorySize parameter. If you enter a value of unlimited, no size limit is imposed on the agent log files.
 
@@ -424,7 +424,7 @@ Accept wildcard characters: False
 
 The MailboxDeliveryConnectorProtocolLoggingLevel parameter enables or disables SMTP protocol logging for the implicit and invisible mailbox delivery Receive connector in the Mailbox Transport Delivery service. Valid values are:
 
-- None: Protocol logging is disabled for the mailbox delivery Receive connector. This is the default value.
+- None: Protocol logging is disabled for the mailbox delivery Receive connector. This value is the default.
 - Verbose: Protocol logging is enabled for the mailbox delivery Receive connector. The location of the log files is controlled by the ReceiveProtocolLogPath parameter.
 
 ```yaml
@@ -445,7 +445,7 @@ Accept wildcard characters: False
 
 The MailboxDeliveryConnectorSmtpUtf8Enabled parameters or disables email address internationalization (EAI) support for the implicit and invisible mailbox delivery Receive connector in the Mailbox Transport Delivery service. Valid values are:
 
-- $true: Mail can be delivered to local mailboxes that have international characters in email addresses. This is the default value
+- $true: Mail can be delivered to local mailboxes that have international characters in email addresses. This value is the default
 - $false: Mail can't be delivered to local mailboxes that have international characters in email addresses.
 
 ```yaml
@@ -514,7 +514,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value of the MailboxDeliveryThrottlingLogMaxFileSize parameter must be less than or equal to the value of the MailboxDeliveryThrottlingLogMaxDirectorySize parameter. If you enter a value of unlimited, no size limit is imposed on the mailbox delivery throttling log directory.
 
@@ -544,7 +544,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value of the MailboxDeliveryThrottlingLogMaxFileSize parameter must be less than or equal to the value of the MailboxDeliveryThrottlingLogMaxDirectorySize parameter. If you enter a value of unlimited, no size limit is imposed on the mailbox delivery throttling log files.
 
@@ -632,7 +632,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value of the MailboxSubmissionAgentLogMaxFileSize parameter must be less than or equal to the value of the MailboxSubmissionAgentLogMaxDirectorySize parameter. If you enter a value of unlimited, no size limit is imposed on the agent log directory.
 
@@ -662,7 +662,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value of the MailboxSubmissionAgentLogMaxFileSize parameter must be less than or equal to the value of the MailboxSubmissionAgentLogMaxDirectorySize parameter. If you enter a value of unlimited, no size limit is imposed on the agent log files.
 
@@ -780,7 +780,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-The PipelineTracingSenderAddress parameter specifies the sender email address that invokes pipeline tracing. Only messages from this address generate pipeline tracing output. The address can be either inside or outside the Exchange organization. Depending on your requirements, you may have to set this parameter to different sender addresses and send new messages to start the transport agents or routes that you want to test. The default value of this parameter is $null.
+The PipelineTracingSenderAddress parameter specifies the sender email address that invokes pipeline tracing. Only messages from this address generate pipeline tracing output. The address can be either inside or outside the Exchange organization. Depending on your requirements, you might have to set this parameter to different sender addresses and send new messages to start the transport agents or routes that you want to test. The default value of this parameter is $null.
 
 ```yaml
 Type: SmtpAddress
@@ -836,7 +836,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value of this parameter must be greater than or equal to the value of the ReceiveProtocolLogMaxFileSize parameter.
 
@@ -870,7 +870,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value of this parameter must be less than or equal to the value of the ReceiveProtocolLogMaxDirectorySize parameter.
 
@@ -944,7 +944,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The valid input range for this parameter is from 1 through 9223372036854775807 bytes. If you enter a value of unlimited, no size limit is imposed on the routing table log directory.
 
@@ -1018,7 +1018,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value of this parameter must be less than or equal to the value of the SendProtocolLogMaxDirectorySize parameter.
 
@@ -1052,7 +1052,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value this parameter must be less than or equal to the value of the SendProtocolLogMaxDirectorySize parameter.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MalwareFilterPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-MalwareFilterPolicy.md
index 9dc6e6811f..d697405ee3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-MalwareFilterPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-MalwareFilterPolicy.md
@@ -13,7 +13,7 @@ title: Set-MalwareFilterPolicy
 # Set-MalwareFilterPolicy
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-MalwareFilterPolicy cmdlet to modify malware filter policies in your organization.
 
@@ -55,7 +55,7 @@ Set-MalwareFilterPolicy [-Identity] <MalwareFilterPolicyIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -132,7 +132,7 @@ This parameter is available only in on-premises Exchange.
 
 The Action parameter specifies the action to take when malware is detected in a message. Valid values are:
 
-- DeleteMessage: Handles the message without notifying the recipients. This is the default value.
+- DeleteMessage: Handles the message without notifying the recipients. This value is the default.
 - DeleteAttachmentAndUseDefaultAlert: Delivers the message, but replaces all attachments with a file named Malware Alert Text.txt that contains the default alert text.
 - DeleteAttachmentAndUseCustomAlert: Delivers the message, but replaces all attachments with a file named Malware Alert Text.txt that contains the custom alert text specified by the CustomAlertText parameter.
 
@@ -175,7 +175,7 @@ This parameter is available only in on-premises Exchange.
 The BypassInboundMessages parameter enables or disables malware filtering on incoming messages (messages entering the organization). Valid values are:
 
 - $true: Malware filtering is disabled on inbound messages.
-- $false: Malware filtering is enabled on inbound messages. This is the default value.
+- $false: Malware filtering is enabled on inbound messages. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -198,7 +198,7 @@ This parameter is available only in on-premises Exchange.
 The BypassOutboundMessages parameter enables or disables malware filtering on outgoing messages (messages leaving the organization). Valid values are:
 
 - $true: Malware filtering is disabled on outbound messages.
-- $false: Malware filtering is enabled on outbound messages. This is the default value.
+- $false: Malware filtering is enabled on outbound messages. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -452,7 +452,7 @@ Accept wildcard characters: False
 The EnableExternalSenderAdminNotifications parameter enables or disables sending notification messages to an administrator for malware detections in messages from internal senders. Valid values are:
 
 - $true: When malware attachments are detected in messages from external senders, a notification messages is sent to the email address that's specified by the ExternalSenderAdminAddress parameter.
-- $false: Notifications aren't sent for malware attachment detections in messages from external senders. This is the default value.
+- $false: Notifications aren't sent for malware attachment detections in messages from external senders. This value is the default.
 
 **Note**: Admin notifications are sent only for _attachments_ that are classified as malware.
 
@@ -477,7 +477,7 @@ This parameter is available only in on-premises Exchange.
 The EnableExternalSenderNotifications parameter enables or disables sending notification messages to external senders for malware detections in their messages. Valid values are:
 
 - $true: When malware is detected in a message from an external sender, send them a notification message.
-- $false: Don't send malware detection notification messages to external message senders. This is the default value.
+- $false: Don't send malware detection notification messages to external message senders. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -499,7 +499,7 @@ This parameter is available only in the cloud-based service.
 
 The EnableFileFilter parameter enables or disables the common attachments filter (also known as common attachment blocking). Valid values are:
 
-- $true: The common attachments filter is enabled. This is the default value.
+- $true: The common attachments filter is enabled. This value is the default.
 - $false: The common attachments filter is disabled.
 
 You specify the file types using the FileTypes parameter.
@@ -525,7 +525,7 @@ Accept wildcard characters: False
 The EnableInternalSenderAdminNotifications parameter enables or disables sending notification messages to an administrator for malware detections in messages from internal senders. Valid values are:
 
 - $true: When malware attachments are detected in messages from internal senders, a notification messages is sent to the email address that's specified by the InternalSenderAdminAddress parameter.
-- $false: Notifications aren't sent for malware attachment detections in messages from internal senders. This is the default value.
+- $false: Notifications aren't sent for malware attachment detections in messages from internal senders. This value is the default.
 
 **Note**: Admin notifications are sent only for _attachments_ that are classified as malware.
 
@@ -550,7 +550,7 @@ This parameter is available only in on-premises Exchange.
 The EnableInternalSenderNotifications parameter enables or disables sending notification messages to internal senders for malware detections in their messages. Valid values are:
 
 - $true: When malware is detected in a message from an internal sender, send them a notification message.
-- $false: Don't send malware detection notification messages to internal message senders. This is the default value.
+- $false: Don't send malware detection notification messages to internal message senders. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -593,7 +593,7 @@ This parameter is available only in the cloud-based service.
 The FileTypeAction parameter specifies what happens to messages that contain one or more attachments where the file extension is included in the FileTypes parameter (the common attachments filter). Valid values are:
 
 - Quarantine: Quarantine the message. Whether or not the recipient is notified depends on the quarantine notification settings in the quarantine policy that's selected for the malware filter policy by the QuarantineTag parameter.
-- Reject: The message is rejected in a non-delivery report (also known as an NDR or bounce message) to the sender. The message is not available in quarantine. This is the default value.
+- Reject: The message is rejected in a non-delivery report (also known as an NDR or bounce message) to the sender. The message is not available in quarantine. This value is the default.
 
 This parameter is meaningful only when the value of the EnableFileFilter parameter is $true.
 
@@ -753,7 +753,7 @@ This parameter is available only in the cloud-based service.
 
 The ZapEnabled parameter enables or disables zero-hour auto purge (ZAP) for malware in cloud mailboxes. ZAP detects malware in unread messages that have already been delivered to the user's Inbox. Valid values are:
 
-- $true: ZAP for malware is enabled. This is the default value. In Exchange Server, unread messages in the user's Inbox that contain malware are moved to the Junk Email folder. In the cloud-based service, the messages are quarantined.
+- $true: ZAP for malware is enabled. This value is the default. In Exchange Server, unread messages in the user's Inbox that contain malware are moved to the Junk Email folder. In the cloud-based service, the messages are quarantined.
 - $false: ZAP for malware is disabled.
 
 ```yaml
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MalwareFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-MalwareFilterRule.md
index 92dce6658f..c9a8199c78 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-MalwareFilterRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-MalwareFilterRule.md
@@ -13,7 +13,7 @@ title: Set-MalwareFilterRule
 # Set-MalwareFilterRule
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-MalwareFilterRule cmdlet to modify malware filter rules in your organization.
 
@@ -43,7 +43,7 @@ Set-MalwareFilterRule [-Identity] <RuleIdParameter>
 > [!IMPORTANT]
 > Different types of recipient conditions use AND logic (the recipient must satisfy **all** specified conditions). Different types of recipient exceptions use OR logic (the recipient must satisfy **any** of the specified exceptions). For more information, see [Anti-malware policies](https://learn.microsoft.com/defender-office-365/anti-malware-protection-about#anti-malware-policies).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MalwareFilteringServer.md b/exchange/exchange-ps/ExchangePowerShell/Set-MalwareFilteringServer.md
index dc4dd0fd54..3f204ae47a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-MalwareFilteringServer.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-MalwareFilteringServer.md
@@ -41,7 +41,7 @@ Set-MalwareFilteringServer [-Identity] <MalwareFilteringServerIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -125,7 +125,7 @@ Accept wildcard characters: False
 
 The DeferAttempts parameter specifies the maximum number of times to defer a message that can't be scanned by the Malware agent. Valid input for this parameter is an integer between 1 and 5. The default value is 3.
 
-After the maximum number of deferrals is reached, the action taken by the Malware agent depends on the error. For scan timeouts and engine errors, the action is to fail the message and return a non-delivery report (NDR) to the sender immediately after the last defer attempt. For all other errors, the message is retried for up to 48 hours, with each retry attempt taking place one hour longer than the last one. For example, starting after the last defer attempt, the first retry attempt will occur in 1 hour, the next retry attempt will occur 2 hours after that, the next retry attempt will occur 3 hours after the second retry attempt, and so on for up to 48 hours. After 48 hours have elapsed, the action is to fail the message and return a non-delivery report (NDR) to the sender.
+After the maximum number of deferrals is reached, the action taken by the Malware agent depends on the error. For scan timeouts and engine errors, the action is to fail the message and return a non-delivery report (NDR) to the sender immediately after the last defer attempt. For all other errors, the message is retried for up to 48 hours, with each retry attempt taking place one hour longer than the last one. For example, starting after the last defer attempt, the first retry attempt occurs in 1 hour, the next retry attempt occurs 2 hours after that, the next retry attempt occurs 3 hours after the second retry attempt, and so on for up to 48 hours. After 48 hours have elapsed, the action is to fail the message and return a non-delivery report (NDR) to the sender.
 
 ```yaml
 Type: Int32
@@ -188,7 +188,7 @@ Accept wildcard characters: False
 The ForceRescan parameter specifies that messages should be scanned by the malware agent, even if the message was already scanned by cloud-based protection. Valid values are:
 
 - $true: Messages from cloud-based organizations are scanned by the malware agent.
-- $false: Messages from cloud-based organizations aren't scanned by the malware agent. This is the default value.
+- $false: Messages from cloud-based organizations aren't scanned by the malware agent. This value is the default.
 
 ```yaml
 Type: Boolean
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ManagedContentSettings.md b/exchange/exchange-ps/ExchangePowerShell/Set-ManagedContentSettings.md
index ddf16e2394..575e6d948f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ManagedContentSettings.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ManagedContentSettings.md
@@ -44,7 +44,7 @@ Managed content settings are settings that you apply to managed folders to contr
 
 Although the New-ManagedContentSettings cmdlet has the MessageClass parameter, the Set-ManagedContentSettings cmdlet doesn't. If you want to change the message type to which content settings apply, you must delete and then re-create the content settings. For more information about the MessageClass parameter, see [New-ManagedContentSettings](https://learn.microsoft.com/powershell/module/exchangepowershell/new-managedcontentsettings).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ManagedFolder.md b/exchange/exchange-ps/ExchangePowerShell/Set-ManagedFolder.md
index a5a7ff9c53..a184b0b51e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ManagedFolder.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ManagedFolder.md
@@ -42,7 +42,7 @@ The Set-ManagedFolder cmdlet modifies the specified parameters of a managed fold
 
 The Set-ManagedFolder cmdlet accepts a managed custom folder or an identity string as pipelined input.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -242,7 +242,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010
 
-The StorageQuota parameter specifies the storage size limit for the mailbox folder. When the folder size exceeds this limit, no additional items may be added. Mailbox sizes can be specified in kilobytes (KB) or megabytes (MB), for example, as 100KB or 5MB. The StorageQuota parameter is valid for managed custom folders in Outlook 2007.
+The StorageQuota parameter specifies the storage size limit for the mailbox folder. When the folder size exceeds this limit, no additional items might be added. Mailbox sizes can be specified in kilobytes (KB) or megabytes (MB), for example, as 100KB or 5MB. The StorageQuota parameter is valid for managed custom folders in Outlook 2007.
 
 ```yaml
 Type: Unlimited
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ManagedFolderMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-ManagedFolderMailboxPolicy.md
index ab10d066e9..e42e17a347 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ManagedFolderMailboxPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ManagedFolderMailboxPolicy.md
@@ -32,7 +32,7 @@ Set-ManagedFolderMailboxPolicy [-Identity] <MailboxPolicyIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ManagementRoleAssignment.md b/exchange/exchange-ps/ExchangePowerShell/Set-ManagementRoleAssignment.md
index 0c8c86b88c..a0c404aed0 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ManagementRoleAssignment.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ManagementRoleAssignment.md
@@ -13,7 +13,7 @@ title: Set-ManagementRoleAssignment
 # Set-ManagementRoleAssignment
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-ManagementRoleAssignment cmdlet to modify existing management role assignments.
 
@@ -106,7 +106,7 @@ You can create custom management scopes using the New-ManagementScope cmdlet and
 
 For more information about management role assignments, see [Understanding management role assignments](https://learn.microsoft.com/exchange/understanding-management-role-assignments-exchange-2013-help).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ManagementRoleEntry.md b/exchange/exchange-ps/ExchangePowerShell/Set-ManagementRoleEntry.md
index de99ac0cc4..5ab67ee695 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ManagementRoleEntry.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ManagementRoleEntry.md
@@ -13,7 +13,7 @@ title: Set-ManagementRoleEntry
 # Set-ManagementRoleEntry
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-ManagementRoleEntry cmdlet to change the available parameters on an existing management role entry.
 
@@ -39,7 +39,7 @@ The Set-ManagementRoleEntry cmdlet changes the available parameters on an existi
 
 For more information about management role entries, see [Understanding management roles](https://learn.microsoft.com/exchange/understanding-management-roles-exchange-2013-help).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -69,7 +69,7 @@ This example adds the DisplayName and ForwardingAddress parameters to the Set-Ma
 Set-ManagementRoleEntry "IT Scripts\MailboxAudit" -Parameters Location -AddParameter -UnScopedTopLevel
 ```
 
-In on-premises Exchange, this example adds the Location parameter to the MailboxAudit custom script on the IT Scripts unscoped top level role. Note that the UnScopedTopLevel switch requires the UnScoped Role Management role, which isn't assigned to any role groups by default.
+In on-premises Exchange, this example adds the Location parameter to the MailboxAudit custom script on the IT Scripts unscoped top level role. The UnScopedTopLevel switch requires the UnScoped Role Management role, which isn't assigned to any role groups by default.
 
 ## PARAMETERS
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ManagementScope.md b/exchange/exchange-ps/ExchangePowerShell/Set-ManagementScope.md
index 30b702cd34..8b671cdcef 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ManagementScope.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ManagementScope.md
@@ -13,7 +13,7 @@ title: Set-ManagementScope
 # Set-ManagementScope
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-ManagementScope cmdlet to change an existing management scope.
 
@@ -57,11 +57,11 @@ Set-ManagementScope [-Identity] <ManagementScopeIdParameter>
 ```
 
 ## DESCRIPTION
-If you change a scope that has been associated with management role assignments using the New-ManagementRoleAssignment cmdlet, the updated scope applies to all the associated role assignments. For more information about changing scopes, see [Change a role scope](https://learn.microsoft.com/exchange/change-a-role-scope-exchange-2013-help).
+If you change a scope that is associated with management role assignments using the New-ManagementRoleAssignment cmdlet, the updated scope applies to all the associated role assignments. For more information about changing scopes, see [Change a role scope](https://learn.microsoft.com/exchange/change-a-role-scope-exchange-2013-help).
 
 For more information about regular and exclusive scopes, see [Understanding management role scopes](https://learn.microsoft.com/exchange/understanding-management-role-scopes-exchange-2013-help).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MapiVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Set-MapiVirtualDirectory.md
index 0b55d95639..bd261af787 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-MapiVirtualDirectory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-MapiVirtualDirectory.md
@@ -37,7 +37,7 @@ Set-MapiVirtualDirectory [-Identity] <VirtualDirectoryIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -146,7 +146,7 @@ The ExtendedProtectionFlags parameter specifies custom settings for Extended Pro
 - AllowDotlessSPN: Required if you want to use Service Principal Name (SPN) values that don't contain FQDNs (for example, HTTP/ContosoMail instead of HTTP/mail.contoso.com). You specify SPNs with the ExtendedProtectionSPNList parameter. This setting makes Extended Protection for Authentication less secure because dotless certificates aren't unique, so it isn't possible to ensure that the client-to-proxy connection was established over a secure channel.
 - NoServiceNameCheck: The SPN list isn't checked to validate a channel binding token. This setting makes Extended Protection for Authentication less secure. We generally don't recommend this setting.
 - Proxy: A proxy server is responsible for terminating the SSL channel. To use this setting, you need to register an SPN by using the ExtendedProtectionSPNList parameter.
-- ProxyCoHosting: HTTP and HTTPS traffic may be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server.
+- ProxyCoHosting: HTTP and HTTPS traffic might be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server.
 
 ```yaml
 Type: MultiValuedProperty
@@ -166,7 +166,7 @@ Accept wildcard characters: False
 
 The ExtendedProtectionSPNList parameter specifies a list of valid Service Principal Names (SPNs) if you're using Extended Protection for Authentication on the virtual directory. Valid values are:
 
-- $null: This is the default value.
+- $null: This value is the default.
 - Single SPN or comma delimited list of valid SPNs: The SPN value format is `Protocol\FQDN`. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter.
 
 ```yaml
@@ -187,8 +187,8 @@ Accept wildcard characters: False
 
 The ExtendedProtectionTokenChecking parameter defines how you want to use Extended Protection for Authentication on the virtual directory. Extended Protection for Authentication isn't enabled by default. Valid values are:
 
-- None: Extended Protection for Authentication isn't be used on the virtual directory. This is the default value.
-- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication will work, but may not be as secure as connections that use Extended Protection for Authentication.
+- None: Extended Protection for Authentication isn't be used on the virtual directory. This value is the default.
+- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication work, but might not be as secure as connections that use Extended Protection for Authentication.
 - Require: Extended Protection for Authentication is used for all connections between clients and the virtual directory. If either the client or server doesn't support it, the connection will fail. If you use this value, you also need to set an SPN value for the ExtendedProtectionSPNList parameter.
 
 **Note**: If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter.
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MessageClassification.md b/exchange/exchange-ps/ExchangePowerShell/Set-MessageClassification.md
index 6c39983580..c5de61e4a9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-MessageClassification.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-MessageClassification.md
@@ -13,7 +13,7 @@ title: Set-MessageClassification
 # Set-MessageClassification
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-MessageClassification cmdlet to configure an existing message classification instance in your organization.
 
@@ -38,7 +38,7 @@ Set-MessageClassification [-Identity] <MessageClassificationIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -141,19 +141,19 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
 
-The DisplayPrecedence parameter specifies the relative precedence of the message classification to other message classifications that may be applied to a specified message. Valid values are:
+The DisplayPrecedence parameter specifies the relative precedence of the message classification to other message classifications that might be applied to a specified message. Valid values are:
 
 - Highest
 - Higher
 - High
 - MediumHigh
-- Medium (This is the default value)
+- Medium (default value)
 - MediumLow
 - Low
 - Lower
 - Lowest
 
-Although Outlook only lets a user specify a single classification for a message, transport rules may apply other classifications to a message. The classification with the highest precedence is shown first and the subsequent classifications, which are those with lesser precedence as defined by this parameter, are appended in the appropriate order thereafter.
+Although Outlook only lets a user specify a single classification for a message, transport rules might apply other classifications to a message. The classification with the highest precedence is shown first and the subsequent classifications, which are those with lesser precedence as defined by this parameter, are appended in the appropriate order thereafter.
 
 ```yaml
 Type: ClassificationDisplayPrecedenceLevel
@@ -213,7 +213,7 @@ Accept wildcard characters: False
 
 The PermissionMenuVisible parameter specifies whether the values that you entered for the DisplayName and RecipientDescription parameters are displayed in Outlook as the user composes a message. Valid values are:
 
-- $true: Users can assign the message classification to messages before they're sent, and the classification information is displayed. This is the default value.
+- $true: Users can assign the message classification to messages before they're sent, and the classification information is displayed. This value is the default.
 - $false: Users can't assign the message classification to messages before they're sent, However, messages received with this message classification still display the classification information.
 
 ```yaml
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MigrationBatch.md b/exchange/exchange-ps/ExchangePowerShell/Set-MigrationBatch.md
index 9c8fc8ac44..f6ae4c00ee 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-MigrationBatch.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-MigrationBatch.md
@@ -13,7 +13,7 @@ title: Set-MigrationBatch
 # Set-MigrationBatch
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-MigrationBatch cmdlet to update a migration request for a batch of users. For more information, see [New-MigrationBatch](https://learn.microsoft.com/powershell/module/exchangepowershell/new-migrationbatch).
 
@@ -60,9 +60,9 @@ The Set-MigrationBatch cmdlet configures your existing migration batches to migr
 - IMAP migration
 - Google Workspace (formerly G Suite) migration
 
-Some settings can be applied both to the batch as well as to individual users within the batch. It is important to note that when a setting is applied to a user it will override any corresponding setting on the batch.
+Some settings can be applied both to the batch as well as to individual users within the batch. A setting applied to a user overrides any corresponding setting on the batch.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -125,7 +125,7 @@ This parameter is available only in on-premises Exchange.
 The AllowIncrementalSyncs parameter specifies whether to enable or disable incremental synchronization. Valid values are:
 
 - $true: Incremental synchronization is enabled. Any new messages that are sent to the source mailbox are copied to the corresponding target mailbox once every 24 hours.
-- $false: Incremental synchronization is disabled. The migration batch will go into the Stopped state after the initial synchronization is complete. To complete a migration batch for local moves, cross-forest moves, or remote move migrations, you need to enable incremental synchronization.
+- $false: Incremental synchronization is disabled. The migration batch enters the Stopped state after the initial synchronization is complete. To complete a migration batch for local moves, cross-forest moves, or remote move migrations, you need to enable incremental synchronization.
 
 ```yaml
 Type: Boolean
@@ -146,7 +146,7 @@ Accept wildcard characters: False
 The AllowUnknownColumnsInCsv parameter specifies whether to allow extra columns in the CSV file that aren't used by migration. Valid values are:
 
 - $true: The migration ignores (silently skips) unknown columns in the CSV file (including optional columns with misspelled column headers). All unknown columns are treated like extra columns that aren't used by migration.
-- $false: The migration fails if there are any unknown columns in the CSV file. This setting protects against spelling errors in column headers. This is the default value.
+- $false: The migration fails if there are any unknown columns in the CSV file. This setting protects against spelling errors in column headers. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -168,7 +168,7 @@ This parameter is available only in the cloud-based service.
 
 The ApproveSkippedItems switch marks all of the skipped items that were discovered prior to the current time as approved. You don't need to specify a value with this switch.
 
-If the data loss that was detected during this migration is significant, the migration will not be able to complete without approving skipped items. Items may have been skipped because they are corrupted in the source mailbox and can't be copied to the target mailbox, they are larger than the max allowable message size configured for the tenant, or they were detected as missing from the target mailbox when the migration is ready to complete.
+If the data loss that was detected during this migration is significant, the migration can't complete without approving skipped items. Items might have been skipped because they are corrupted in the source mailbox and can't be copied to the target mailbox, they are larger than the max allowable message size configured for the tenant, or they were detected as missing from the target mailbox when the migration is ready to complete.
 
 For more information about maximum message size values, see the following topic [Exchange Online Limits](https://learn.microsoft.com/office365/servicedescriptions/exchange-online-service-description/exchange-online-limits).
 
@@ -210,9 +210,9 @@ Accept wildcard characters: False
 
 The BadItemLimit parameter specifies the maximum number of bad items that are allowed before the migration request fails. A bad item is a corrupt item in the source mailbox that can't be copied to the target mailbox. Also included in the bad item limit are missing items. Missing items are items in the source mailbox that can't be found in the target mailbox when the migration request is ready to complete.
 
-Valid input for this parameter is an integer or the value unlimited. The default value is 0, which means the migration request will fail if any bad items are detected. If you are OK with leaving a few bad items behind, you can set this parameter to a reasonable value (we recommend 10 or lower) so the migration request can proceed. If too many bad items are detected, consider using the New-MailboxRepairRequest cmdlet to attempt to fix corrupted items in the source mailbox, and try the migration request again.
+Valid input for this parameter is an integer or the value unlimited. The default value is 0, which means the migration request fails if any bad items are detected. If you are OK with leaving a few bad items behind, you can set this parameter to a reasonable value (we recommend 10 or lower) so the migration request can proceed. If too many bad items are detected, consider using the New-MailboxRepairRequest cmdlet to attempt to fix corrupted items in the source mailbox, and try the migration request again.
 
-**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics will be used instead.
+**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics are used instead.
 
 ```yaml
 Type: Unlimited
@@ -232,14 +232,14 @@ Accept wildcard characters: False
 
 This parameter is functional only in the cloud-based service.
 
-The CompleteAfter parameter specifies a delay before the batch is completed. Data migration for the batch will start, but completion won't start until the date/time you specify with this parameter.
+The CompleteAfter parameter specifies a delay before the batch is completed. Data migration for the batch starts, but completion doesn't start until the date/time you specify with this parameter.
 
 Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
 
 In Exchange Online PowerShell, if you specify a date/time value without a time zone, the value is in Coordinated Universal Time (UTC). To specify a value, use either of the following options:
 
 - Specify the date/time value in UTC: For example, `"7/30/2020 9:00PM Z"`.
-- Specify the date/time value in your local time zone. For example, `"7/30/2020 9:00PM -700"`. The value will be converted to UTC if you don't use the TimeZone parameter.
+- Specify the date/time value in your local time zone. For example, `"7/30/2020 9:00PM -700"`. The value is converted to UTC if you don't use the TimeZone parameter.
 
 ```yaml
 Type: DateTime
@@ -282,7 +282,7 @@ The CSVData parameter specifies the CSV file that contains information about the
 
 A valid value for this parameter requires you to read the file to a byte-encoded object using the following syntax: `([System.IO.File]::ReadAllBytes('<Path>\<FileName>'))`. You can use this command as the parameter value, or you can write the output to a variable (`$data = [System.IO.File]::ReadAllBytes('<Path>\<FileName>')`) and use the variable as the parameter value (`$data`).
 
-**Note**: This parameter doesn't validate the availability of the mailboxes based on RBAC scope. All mailboxes that are specified in the CSV file will be migrated, even if they are outside of the RBAC scope (for example, an OU) that gives the admin permissions to migrate mailboxes.
+**Note**: This parameter doesn't validate the availability of the mailboxes based on RBAC scope. All mailboxes specified in the CSV file are migrated, even if they're outside of the RBAC scope (for example, an OU) that gives the admin permissions to migrate mailboxes.
 
 ```yaml
 Type: Byte[]
@@ -329,7 +329,7 @@ For more information about maximum message size values, see the following topics
 
 Valid input for this parameter is an integer or the value unlimited. The default value is 0, which means the migration request will fail if any large items are detected. If you are OK with leaving a few large items behind, you can set this parameter to a reasonable value (we recommend 10 or lower) so the migration request can proceed.
 
-**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics will be used instead.
+**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics are used instead.
 
 ```yaml
 Type: Unlimited
@@ -449,7 +449,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
 
-This parameter has been replaced by the MoveOptions parameter.
+This parameter is replaced by the MoveOptions parameter.
 
 The SkipMoving parameter specifies the stages of the migration that you want to skip for debugging purposes. Don't use this parameter unless you're directed to do so by Microsoft Customer Service and Support or specific documentation.
 
@@ -511,14 +511,14 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
 
-The StartAfter parameter specifies a delay before the data migration for the users within the batch is started. The migration will be prepared, but the actual data migration for users within the batch won't start until the date/time you specify with this parameter.
+The StartAfter parameter specifies a delay before the data migration for the users within the batch is started. The migration is prepared, but the actual data migration for users within the batch doesn't start until the date/time you specify with this parameter.
 
 Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
 
 In Exchange Online PowerShell, if you specify a date/time value without a time zone, the value is in Coordinated Universal Time (UTC). To specify a value, use either of the following options:
 
 - Specify the date/time value in UTC: For example, `"7/30/2020 9:00PM Z"`.
-- Specify the date/time value in your local time zone. For example, `"7/30/2020 9:00PM -700"`. The value will be converted to UTC if you don't use the TimeZone parameter.
+- Specify the date/time value in your local time zone. For example, `"7/30/2020 9:00PM -700"`. The value is converted to UTC if you don't use the TimeZone parameter.
 
 ```yaml
 Type: DateTime
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MigrationConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-MigrationConfig.md
index 0c567f3657..605b6fd87b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-MigrationConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-MigrationConfig.md
@@ -13,7 +13,7 @@ title: Set-MigrationConfig
 # Set-MigrationConfig
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-MigrationConfig cmdlet to edit migration configurations on Exchange servers.
 
@@ -34,7 +34,7 @@ Set-MigrationConfig
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MigrationEndpoint.md b/exchange/exchange-ps/ExchangePowerShell/Set-MigrationEndpoint.md
index 219d487254..ff7cf2b290 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-MigrationEndpoint.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-MigrationEndpoint.md
@@ -13,7 +13,7 @@ title: Set-MigrationEndpoint
 # Set-MigrationEndpoint
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-MigrationEndpoint cmdlet to edit settings for cutover or staged Exchange migrations, IMAP migrations, Google Workspace (formerly G Suite) migrations, and remote moves.
 
@@ -67,7 +67,7 @@ For more information about the different move and migration scenarios, see:
 
 Changes made to an endpoint that affect the individual users within the batch are applied starting at the next time that the batch is processed. If you are running this cmdlet in the cloud-based service and wish to speed up the application of these settings, consider running the Set-MigrationBatch cmdlet with the -Update parameter.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -313,7 +313,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
 
-The MaxConcurrentMigrations parameter specifies the maximum number of mailboxes that will be migrated for this endpoint at a specified time. This parameter is applicable for all migration types.
+The MaxConcurrentMigrations parameter specifies the maximum number of migrated mailboxes for this endpoint at a specified time. This parameter is applicable for all migration types.
 
 ```yaml
 Type: Unlimited
@@ -474,7 +474,7 @@ Accept wildcard characters: False
 
 This parameter is available only in the cloud-based service.
 
-The ServiceAccountKeyFileData parameter is used to specify information needed to authenticate as a service account. The data should come from the JSON key file that is downloaded when the service account that has been granted access to your remote tenant is created.
+The ServiceAccountKeyFileData parameter is used to specify information needed to authenticate as a service account. The data should come from the JSON key file that is downloaded when the service account that is granted access to your remote tenant is created.
 
 A valid value for this parameter requires you to read the file to a byte-encoded object using the following syntax: `([System.IO.File]::ReadAllBytes('<Path>\<FileName>'))`. You can use this command as the parameter value, or you can write the output to a variable (`$data = [System.IO.File]::ReadAllBytes('<Path>\<FileName>')`) and use the variable as the parameter value (`$data`).
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MigrationUser.md b/exchange/exchange-ps/ExchangePowerShell/Set-MigrationUser.md
index 06f2e1d789..9e26ca12a5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-MigrationUser.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-MigrationUser.md
@@ -37,9 +37,9 @@ Set-MigrationUser [-Identity] <MigrationUserIdParameter>
 ```
 
 ## DESCRIPTION
-Some settings can be applied both to the batch as well as to individual users within the batch. It is important to note that when a setting is applied to a user it will override any corresponding setting on the batch.
+Some settings can be applied both to the batch as well as to individual users within the batch. A setting applied to a user overrides any corresponding setting on the batch.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -87,7 +87,7 @@ This parameter is available only in the cloud-based service.
 
 The ApproveSkippedItems switch marks all of the skipped items that were discovered prior to the current time as approved. You don't need to specify a value with this switch.
 
-If the data loss that was detected during this migration is significant, the migration will not be able to complete without approving skipped items. Items may have been skipped because they are corrupted in the source mailbox and can't be copied to the target mailbox, they are larger than the max allowable message size configured for the tenant, or they were detected as missing from the target mailbox when the migration is ready to complete.
+If the data loss that was detected during this migration is significant, the migration can't complete without approving skipped items. Items might have been skipped because they are corrupted in the source mailbox and can't be copied to the target mailbox, they are larger than the max allowable message size configured for the tenant, or they were detected as missing from the target mailbox when the migration is ready to complete.
 
 For more information about maximum message size values, see the following topic [Exchange Online Limits](https://learn.microsoft.com/office365/servicedescriptions/exchange-online-service-description/exchange-online-limits).
 
@@ -113,7 +113,7 @@ The BadItemLimit parameter specifies the maximum number of bad items that are al
 
 Valid input for this parameter is an integer or the value unlimited. The default value is 0, which means the migration request will fail if any bad items are detected. If you are OK with leaving a few bad items behind, you can set this parameter to a reasonable value (we recommend 10 or lower) so the migration request can proceed. If too many bad items are detected, consider using the New-MailboxRepairRequest cmdlet to attempt to fix corrupted items in the source mailbox, and try the migration request again.
 
-**Note**: This parameter is being deprecated. In the future, if you don't use this parameter, Skipped Item approval semantics will be used instead.
+**Note**: This parameter is being deprecated. In the future, if you don't use this parameter, Skipped Item approval semantics are used instead.
 
 ```yaml
 Type: Unlimited
@@ -133,7 +133,7 @@ Accept wildcard characters: False
 
 This parameter is available only in the cloud-based service.
 
-The CompleteAfter parameter specifies a delay before the user is completed. Data migration for the user will start, but won't complete until the date/time you specify with this parameter.
+The CompleteAfter parameter specifies a delay before the user is completed. Data migration for the user starts but doesn't complete until the date/time you specify with this parameter.
 
 Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
 
@@ -210,7 +210,7 @@ For more information about maximum message size values, see the following topics
 
 Valid input for this parameter is an integer or the value unlimited. The default value is 0, which means the migration request will fail if any large items are detected. If you are OK with leaving a few large items behind, you can set this parameter to a reasonable value (we recommend 10 or lower) so the migration request can proceed.
 
-**Note**: This parameter is being deprecated. In the future, if you don't use this parameter, Skipped Item approval semantics will be used instead.
+**Note**: This parameter is being deprecated. In the future, if you don't use this parameter, Skipped Item approval semantics are used instead.
 
 ```yaml
 Type: Unlimited
@@ -250,7 +250,7 @@ Accept wildcard characters: False
 
 This parameter is available only in the cloud-based service.
 
-The StartAfter parameter specifies a delay before the data migration for the user is started. The migration will be prepared, but the actual data migration for the user won't start until the date/time you specify with this parameter.
+The StartAfter parameter specifies a delay before the data migration for the user is started. The migration is prepared, but the actual data migration for the user doesn't start until the date/time you specify with this parameter.
 
 Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MobileDeviceMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-MobileDeviceMailboxPolicy.md
index 8cb8193e53..1418931139 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-MobileDeviceMailboxPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-MobileDeviceMailboxPolicy.md
@@ -13,7 +13,7 @@ title: Set-MobileDeviceMailboxPolicy
 # Set-MobileDeviceMailboxPolicy
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-MobileDeviceMailboxPolicy cmdlet to modify mobile device mailbox policies.
 
@@ -91,7 +91,7 @@ Some mobile device mailbox policy settings require the mobile device to have spe
 
 Some settings in this cmdlet are supported by Outlook for iOS and Android. For more information, see [Leveraging Exchange Online mobile device policies](https://learn.microsoft.com/exchange/clients-and-mobile-in-exchange-online/outlook-for-ios-and-android/secure-outlook-for-ios-and-android#leveraging-exchange-online-mobile-device-policies).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -901,7 +901,7 @@ Accept wildcard characters: False
 The MaxInactivityTimeLock parameter specifies the length of time that the mobile device can be inactive before the password is required to reactivate it. Valid values are:
 
 - A timespan: hh:mm:ss, where hh = hours, mm = minutes and ss= seconds. The valid input range is 00:01:00 to 01:00:00 (one minute to one hour).
-- The value Unlimited. This is the default value.
+- The value Unlimited. This value is the default.
 
 ```yaml
 Type: Unlimited
@@ -1036,7 +1036,7 @@ Accept wildcard characters: False
 The PasswordExpiration parameter specifies how long a password can be used on a mobile device before the user is forced to change the password. Valid values are:
 
 - A timespan: ddd.hh:mm:ss, where ddd = days, hh = hours, mm = minutes and ss= seconds. The valid input range is 1.00:00:00 to 730.00:00:00 (one day to two years).
-- The value Unlimited. This is the default value
+- The value Unlimited. This value is the default
 
 ```yaml
 Type: Unlimited
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MoveRequest.md b/exchange/exchange-ps/ExchangePowerShell/Set-MoveRequest.md
index 1c119aad16..ea5a7779aa 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-MoveRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-MoveRequest.md
@@ -13,9 +13,9 @@ title: Set-MoveRequest
 # Set-MoveRequest
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
-Use the Set-MoveRequest cmdlet to change move request options after the move request has been created. You can use the Set-MoveRequest cmdlet to recover from failed move requests.
+Use the Set-MoveRequest cmdlet to change move request options after the move request is created. You can use the Set-MoveRequest cmdlet to recover from failed move requests.
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
@@ -57,7 +57,7 @@ Set-MoveRequest [-Identity] <MoveRequestIdParameter>
 ## DESCRIPTION
 You can pipeline the Set-MoveRequest cmdlet from the Get-MoveRequestStatistics, Get-MoveRequest, or Get-Mailbox cmdlets.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -161,7 +161,7 @@ Valid input for this parameter is an integer or the value unlimited. The default
 
 In Exchange 2010, if you set this value to 51 or higher, you also need to use the AcceptLargeDataLoss switch. Otherwise, the command will fail.
 
-**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics will be used instead.
+**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics are used instead.
 
 ```yaml
 Type: Unlimited
@@ -283,7 +283,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013
 
-The IgnoreRuleLimitErrors parameter specifies that the command won't move the user's rules to the target server running Microsoft Exchange.
+The IgnoreRuleLimitErrors parameter specifies whether the command moves the user's rules to the target server running Microsoft Exchange.
 
 ```yaml
 Type: Boolean
@@ -301,7 +301,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
 
-The IncrementalSyncInterval parameter specifies the wait time between incremental syncs. This parameter is used together with the CompleteAfter parameter to create a move request that will do periodic incremental syncs after the initial sync is complete.
+The IncrementalSyncInterval parameter specifies the wait time between incremental syncs. Use this parameter with the CompleteAfter parameter to create a move request that does periodic incremental syncs after the initial sync is complete.
 
 To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds.
 
@@ -354,7 +354,7 @@ Valid input for this parameter is an integer or the value unlimited. The default
 
 If you set this value to 51 or higher, you also need to use the AcceptLargeDataLoss switch. Otherwise, the command will fail.
 
-**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics will be used instead.
+**Note**: This parameter is being deprecated in the cloud-based service. In the future, if you don't use this parameter, Skipped Item approval semantics are used instead.
 
 ```yaml
 Type: Unlimited
@@ -395,7 +395,7 @@ Accept wildcard characters: False
 The PreventCompletion parameter specifies whether to run the move request, but not allow it to complete. Valid values are:
 
 - $true: The move request is run, but is not allowed to complete. Instead of this value, we recommend using the CompleteAfter parameter.
-- $false: This is the default value. The move request is run and allowed to complete. If you created the move request with the SuspendWhenReadyToComplete or PreventCompletion switches, set this parameter to $false before you run the Resume-MoveRequest cmdlet to complete the move request.
+- $false: This value is the default. The move request is run and allowed to complete. If you created the move request with the SuspendWhenReadyToComplete or PreventCompletion switches, set this parameter to $false before you run the Resume-MoveRequest cmdlet to complete the move request.
 
 ```yaml
 Type: Boolean
@@ -420,7 +420,7 @@ The Priority parameter specifies the order in which the request should be proces
 - Lowest
 - Lower
 - Low
-- Normal: This is the default value.
+- Normal: This value is the default.
 - High
 - Higher
 - Highest
@@ -574,7 +574,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
 
-This parameter has been replaced by the MoveOptions parameter.
+This parameter is replaced by the MoveOptions parameter.
 
 The SkipMoving parameter specifies the stages of the move that you want to skip for debugging purposes. Don't use this parameter unless you're directed to do so by Microsoft Customer Service and Support or specific documentation.
 
@@ -643,7 +643,7 @@ Accept wildcard characters: False
 
 This parameter is available only in the cloud-based service.
 
-The SkippedItemApprovalTime parameter marks all of the skipped items discovered prior to the specified time as approved. If the data loss that was detected during this migration is significant, the migration will not be able to complete without approving skipped items. Items may have been skipped because they are corrupted in the source mailbox and can't be copied to the target mailbox, they are larger than the max allowable message size configured for the tenant, or they were detected as missing from the target mailbox when the migration is ready to complete.
+The SkippedItemApprovalTime parameter marks all of the skipped items discovered prior to the specified time as approved. If the data loss that was detected during this migration is significant, the migration can't complete without approving skipped items. Items might have been skipped because they are corrupted in the source mailbox and can't be copied to the target mailbox, they are larger than the max allowable message size configured for the tenant, or they were detected as missing from the target mailbox when the migration is ready to complete.
 
 For more information about maximum message size values, see the following topic [Exchange Online Limits](https://learn.microsoft.com/office365/servicedescriptions/exchange-online-service-description/exchange-online-limits).
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-Notification.md b/exchange/exchange-ps/ExchangePowerShell/Set-Notification.md
index a253128a9d..55cdd0e679 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-Notification.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-Notification.md
@@ -13,7 +13,7 @@ title: Set-Notification
 # Set-Notification
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 > [!NOTE]
 > This cmdlet will be deprecated in the cloud-based service. The classic Exchange admin center was deprecated in the cloud-based service in 2023.
@@ -49,7 +49,7 @@ Set-Notification -NotificationEmails <MultiValuedProperty> -ProcessType <AsyncOp
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -75,7 +75,7 @@ This example configures the specified notification event to send notification em
 
 The Identity parameter specifies the notification event that you want to modify. You identify the notification event by its AlternativeID property value (a GUID). You can find this value by running the command: `Get-Notification | Format-List DisplayName,AlternativeID,StartTime,Status,Type`.
 
-Typically, it only makes sense to modify notification recipients for events that haven't completed (if the event has completed, no more notification messages will be sent).
+Typically, it only makes sense to modify notification recipients for events that haven't completed (if the event has completed, no more notification messages are sent).
 
 You can't use this parameter with the ProcessType parameter.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-OMEConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Set-OMEConfiguration.md
index 233c454fd2..90b01174f8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-OMEConfiguration.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-OMEConfiguration.md
@@ -40,7 +40,7 @@ Set-OMEConfiguration [-Identity] <OMEConfigurationIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -79,7 +79,7 @@ The BackgroundColor parameter specifies the background color. Valid values are:
 
 - An HTML hexadecimal color code value (#RRGGBB) enclosed in quotation marks. For example, `"#FFFFFF"` is white.
 - A valid color name value. For example, `yellow` is #ffff00. For a list of the valid color names, see [Background color reference](https://learn.microsoft.com/purview/add-your-organization-brand-to-encrypted-messages#background-color-reference).
-- $null (blank). This is the default value.
+- $null (blank). This value is the default.
 
 ```yaml
 Type: String
@@ -160,7 +160,7 @@ Accept wildcard characters: False
 
 This parameter is available only with a Microsoft 365 Advanced Message Encryption subscription.
 
-The ExternalMailExpiryInDays parameter specifies the number of days that the encrypted message is available to external recipients in the Microsoft 365 portal. A valid value is an integer from 0 to 730. The value 0 means the messages will never expire. The default value is 0.
+The ExternalMailExpiryInDays parameter specifies the number of days that the encrypted message is available to external recipients in the Microsoft 365 portal. A valid value is an integer from 0 to 730. The value 0 means the messages never expire. The default value is 0.
 
 You can't update the value of this parameter in the default OME configuration. You can only modify this value in a customized configuration.
 
@@ -182,7 +182,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online, Exchange Online Protection
 
-The Image parameter identifies and uploads an image that will be displayed in the email message and in the Microsoft 365 admin center.
+The Image parameter identifies and uploads an image to be displayed in the email message and in the Microsoft 365 admin center.
 
 A valid value for this parameter requires you to read the file to a byte-encoded object using the following syntax: `([System.IO.File]::ReadAllBytes('<Path>\<FileName>'))`. You can use this command as the parameter value, or you can write the output to a variable (`$data = [System.IO.File]::ReadAllBytes('<Path>\<FileName>')`) and use the variable as the parameter value (`$data`).
 
@@ -230,7 +230,7 @@ Accept wildcard characters: False
 
 The OTPEnabled parameter specifies whether to allow recipients to use a one-time passcode to view encrypted messages. Valid values are:
 
-- $true: Recipients can use a one-time passcode to view encrypted messages. This is the default value.
+- $true: Recipients can use a one-time passcode to view encrypted messages. This value is the default.
 - $false: Recipients can't use a one-time passcode to view encrypted messages. The recipient is required to sign in using a Microsoft 365 work or school account.
 
 ```yaml
@@ -311,7 +311,7 @@ Accept wildcard characters: False
 
 The SocialIdSignIn parameter specifies whether a user is allowed to view an encrypted message in the Microsoft 365 admin center using their own social network id (Google, Yahoo, and Microsoft account). Valid values are:
 
-- $true: Social network ID sign in is allowed. This is the default value.
+- $true: Social network ID sign in is allowed. This value is the default.
 - $false: Social network ID sign in is not allowed. Whether the recipient can use a one-time passcode or their Microsoft 365 work or school account is controlled by the OTPEnabled parameter.
 
 ```yaml
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-OMEMessageRevocation.md b/exchange/exchange-ps/ExchangePowerShell/Set-OMEMessageRevocation.md
index 2372c45de6..7b7c845e23 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-OMEMessageRevocation.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-OMEMessageRevocation.md
@@ -27,11 +27,11 @@ Set-OMEMessageRevocation -MessageId <String> -Revoke <Boolean>
 ```
 
 ## DESCRIPTION
-When an email has been revoked, the recipient will get the following error when they try to view the encrypted message in the OME portal: "The message has been revoked by the sender".
+When an email is revoked, the recipient gets the following error when they try to view the encrypted message in the OME portal: "The message is revoked by the sender".
 
 You can revoke encrypted messages if the recipient received a link-based, branded encrypted email message. If the recipient received a native inline experience in a supported Outlook client, then you can't revoke encryption for the message.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -48,7 +48,7 @@ This example revokes encryption for the specified message.
 
 > Applicable: Exchange Online
 
-The MessageId parameter specifies the message based on the value the Message-ID header field. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which may include angle brackets) and enclose the value in quotation marks (for example, "<d9683b4c-127b-413a-ae2e-fa7dfb32c69d@DM3NAM06BG401.Eop-nam06.prod.protection.outlook.com>").
+The MessageId parameter specifies the message based on the value the Message-ID header field. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which might include angle brackets) and enclose the value in quotation marks (for example, "<d9683b4c-127b-413a-ae2e-fa7dfb32c69d@DM3NAM06BG401.Eop-nam06.prod.protection.outlook.com>").
 
 You can find the Message ID for a message in Message Trace or the Message Encryption Report in the Microsoft Purview compliance portal.
 
@@ -70,8 +70,8 @@ Accept wildcard characters: False
 
 The Revoke parameter specifies whether to revoke encryption for the message. Valid values are:
 
-- $true: Encryption for the specified message is revoked. The recipient will get an error when they try to view the encrypted message in the OME portal
-- $false: Encryption for the specified message isn't revoked. This is the default value.
+- $true: Encryption for the specified message is revoked. The recipient gets an error when they try to view the encrypted message in the OME portal
+- $false: Encryption for the specified message isn't revoked. This value is the default.
 
 ```yaml
 Type: Boolean
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-OabVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Set-OabVirtualDirectory.md
index 5ec25ce2cb..b5baa5d5b7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-OabVirtualDirectory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-OabVirtualDirectory.md
@@ -40,7 +40,7 @@ Set-OabVirtualDirectory [-Identity] <VirtualDirectoryIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -83,7 +83,7 @@ Accept wildcard characters: False
 
 The BasicAuthentication parameter specifies whether Basic authentication is enabled on the virtual directory. Valid values are:
 
-- $true: Basic authentication is enabled. This is the default value.
+- $true: Basic authentication is enabled. This value is the default.
 - $false: Basic authentication is disabled.
 
 You can use this parameter with the WindowsAuthentication parameter.
@@ -149,7 +149,7 @@ The ExtendedProtectionFlags parameter specifies custom settings for Extended Pro
 - AllowDotlessSPN: Required if you want to use Service Principal Name (SPN) values that don't contain FQDNs (for example, HTTP/ContosoMail instead of HTTP/mail.contoso.com). You specify SPNs with the ExtendedProtectionSPNList parameter. This setting makes Extended Protection for Authentication less secure because dotless certificates aren't unique, so it isn't possible to ensure that the client-to-proxy connection was established over a secure channel.
 - NoServiceNameCheck: The SPN list isn't checked to validate a channel binding token. This setting makes Extended Protection for Authentication less secure. We generally don't recommend this setting.
 - Proxy: A proxy server is responsible for terminating the SSL channel. To use this setting, you need to register an SPN by using the ExtendedProtectionSPNList parameter.
-- ProxyCoHosting: HTTP and HTTPS traffic may be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server.
+- ProxyCoHosting: HTTP and HTTPS traffic might be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server.
 
 ```yaml
 Type: MultiValuedProperty
@@ -169,7 +169,7 @@ Accept wildcard characters: False
 
 The ExtendedProtectionSPNList parameter specifies a list of valid Service Principal Names (SPNs) if you're using Extended Protection for Authentication on the virtual directory. Valid values are:
 
-- $null: This is the default value.
+- $null: This value is the default.
 - Single SPN or comma delimited list of valid SPNs: The SPN value format is `Protocol\FQDN`. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter.
 
 ```yaml
@@ -190,8 +190,8 @@ Accept wildcard characters: False
 
 The ExtendedProtectionTokenChecking parameter defines how you want to use Extended Protection for Authentication on the virtual directory. Extended Protection for Authentication isn't enabled by default. Valid values are:
 
-- None: Extended Protection for Authentication isn't be used on the virtual directory. This is the default value.
-- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication will work, but may not be as secure as connections that use Extended Protection for Authentication.
+- None: Extended Protection for Authentication isn't be used on the virtual directory. This value is the default.
+- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication work, but might not be as secure as connections that use Extended Protection for Authentication.
 - Require: Extended Protection for Authentication is used for all connections between clients and the virtual directory. If either the client or server doesn't support it, the connection will fail. If you use this value, you also need to set an SPN value for the ExtendedProtectionSPNList parameter.
 
 **Note**: If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter.
@@ -288,7 +288,7 @@ Accept wildcard characters: False
 
 The RequireSSL parameter specifies whether the client connection to the virtual directory requires Secure Sockets Layer (SSL) encryption. Valid values are:
 
-- $true: SSL encryption is required to connect to the virtual directory. This is the default value.
+- $true: SSL encryption is required to connect to the virtual directory. This value is the default.
 - $false: SSL encryption isn't required to connect to the virtual directory.
 
 ```yaml
@@ -327,7 +327,7 @@ Accept wildcard characters: False
 
 The WindowsAuthentication parameter specifies whether Integrated Windows authentication is enabled on the virtual directory. Valid values are:
 
-- $true: Integrated Windows authentication is enabled. This is the default value.
+- $true: Integrated Windows authentication is enabled. This value is the default.
 - $false: Integrated Windows authentication is disabled.
 
 You can use this parameter with the BasicAuthentication parameter.
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-OfflineAddressBook.md b/exchange/exchange-ps/ExchangePowerShell/Set-OfflineAddressBook.md
index e7ba1533af..9aa1ab5a32 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-OfflineAddressBook.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-OfflineAddressBook.md
@@ -13,7 +13,7 @@ title: Set-OfflineAddressBook
 # Set-OfflineAddressBook
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-OfflineAddressBook cmdlet to modify offline address book (OAB) settings.
 
@@ -53,7 +53,7 @@ Set-OfflineAddressBook [-Identity] <OfflineAddressBookIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -282,7 +282,7 @@ This parameter is available only in on-premises Exchange.
 The GlobalWebDistributionEnabled parameter specifies whether all OAB virtual directories in the organization can accept requests to download the OAB. These locations are advertised by the Autodiscover service. Valid values are:
 
 - $true: Any OAB virtual directory in the organization can accept requests to download the OAB. You can't use this setting with the VirtualDirectories parameter.
-- $false: Only the OAB virtual directories that are specified by the VirtualDirectories parameter accept requests to download the OAB. This is the default value.
+- $false: Only the OAB virtual directories that are specified by the VirtualDirectories parameter accept requests to download the OAB. This value is the default.
 
 In Exchange 2013 CU7 or later, we recommend that you use the value $true for this parameter. The Client Access services on any Mailbox server can proxy incoming OAB download requests to the correct location.
 
@@ -490,7 +490,7 @@ This parameter is available only in on-premises Exchange.
 The ShadowMailboxDistributionEnabled parameter specifies whether a read only copy of the OAB (also known as a shadow copy) is distributed to all other OAB generation mailboxes (also known as organization mailboxes). This allows additional Mailbox servers to be endpoints for requests to download the OAB, which can help prevent users from downloading the OAB across slow WAN links. Valid values are:
 
 - $true: The OAB is distributed to all other organization mailboxes.
-- $false: The OAB is isn't distributed to other organization mailboxes. This is the default value.
+- $false: The OAB is isn't distributed to other organization mailboxes. This value is the default.
 
 The value of this parameter is only meaningful if you have multiple organization mailboxes, and is only beneficial in Exchange organizations that have multiple Active Directory sites.
 
@@ -625,7 +625,7 @@ Accept wildcard characters: False
 The ZipOabFilesBeforeUploading specifies whether to use ZIP file compression on the OAB files before uploading them to the server. Valid values are:
 
 - $true: ZIP the OAB files.
-- $false: Don't ZIP the OAB files. This is the default value.
+- $false: Don't ZIP the OAB files. This value is the default.
 
 ```yaml
 Type: Boolean
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-OnPremisesOrganization.md b/exchange/exchange-ps/ExchangePowerShell/Set-OnPremisesOrganization.md
index aa0d233348..a6c3d1ea65 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-OnPremisesOrganization.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-OnPremisesOrganization.md
@@ -35,9 +35,9 @@ Set-OnPremisesOrganization [-Identity] <OnPremisesOrganizationIdParameter>
 ```
 
 ## DESCRIPTION
-The OnPremisesOrganization object represents an on-premises Exchange organization configured for hybrid deployment with a Microsoft 365 organization. Typically, this object is only modified and updated by the Hybrid Configuration wizard. Manual modification of this object may result in hybrid deployment misconfiguration; therefore, we strongly recommend that you use the Hybrid Configuration wizard to update this object in the Microsoft 365 organization.
+The OnPremisesOrganization object represents an on-premises Exchange organization configured for hybrid deployment with a Microsoft 365 organization. Typically, this object is only modified and updated by the Hybrid Configuration wizard. Manual modification of this object might result in hybrid deployment misconfiguration; therefore, we strongly recommend that you use the Hybrid Configuration wizard to update this object in the Microsoft 365 organization.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -115,7 +115,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online
 
-The HybridDomains parameter specifies the domains that are configured in the hybrid deployment between a Microsoft 365 organization and an on-premises Exchange organization. The domains specified in this parameter must match the domains listed in the HybridConfiguration Active Directory object for the on-premises Exchange organization configured by the Hybrid Configuration wizard. Multiple domains may be listed and must be separated by a comma, for example, "contoso.com, sales.contoso.com".
+The HybridDomains parameter specifies the domains that are configured in the hybrid deployment between a Microsoft 365 organization and an on-premises Exchange organization. The domains specified in this parameter must match the domains listed in the HybridConfiguration Active Directory object for the on-premises Exchange organization configured by the Hybrid Configuration wizard. Multiple domains might be listed and must be separated by a comma, for example, "contoso.com, sales.contoso.com".
 
 ```yaml
 Type: MultiValuedProperty
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-OrganizationConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-OrganizationConfig.md
index 763ab36230..35f5f42bd8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-OrganizationConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-OrganizationConfig.md
@@ -13,7 +13,7 @@ title: Set-OrganizationConfig
 # Set-OrganizationConfig
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-OrganizationConfig cmdlet to configure various settings of an Exchange organization.
 
@@ -505,7 +505,7 @@ Set-OrganizationConfig
 > [!TIP]
 > The output of the **Get-OrganizationConfig** cmdlet often shows curly braces or `{}` around properties values that accept multiple comma-separated values. Don't use those extra characters in values for the corresponding parameters on this cmdlet. Use the syntax as explained in the parameter descriptions.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -516,11 +516,11 @@ Set-OrganizationConfig -DistributionGroupDefaultOU Users\Groups -DistributionGro
 
 This example creates a distribution group naming policy using the following configuration:
 
-Distribution groups will be created in the Users\\Groups container.
+Distribution groups are created in the Users\\Groups container.
 
-The words curse, bad, and offensive will be blocked from being used in distribution group names.
+The words curse, bad, and offensive are blocked from being used in distribution group names.
 
-All distribution groups will be prefixed with `DL_` and suffixed with an underscore (\_\) and the user's department and country code.
+All distribution groups are prefixed with `DL_` and suffixed with an underscore (\_\) and the user's department and country code.
 
 ### Example 2
 ```powershell
@@ -567,7 +567,7 @@ This parameter is available only in the cloud-based service.
 
 The ShortenEventScopeDefault parameter specifies whether calendar events start late or end early in the organization. Valid values are:
 
-- 0 or None: Calendar events in the organization don't automatically start late or end early. This is the default value.
+- 0 or None: Calendar events in the organization don't automatically start late or end early. This value is the default.
 - 1 or EndEarly: By default, the end time of all calendar events is reduced by the number of minutes as specified by the values of the DefaultMinutesToReduceLongEventsBy and DefaultMinutesToReduceShortEventsBy parameters.
 - 2 or StartLate: By default, the start time of all calendar events is delayed by the number of minutes as specified by the values of the DefaultMinutesToReduceLongEventsBy and DefaultMinutesToReduceShortEventsBy parameters.
 
@@ -649,7 +649,7 @@ Accept wildcard characters: False
 
 The ActivityBasedAuthenticationTimeoutEnabled parameter enables or disables the inactivity interval for automatic logoff in Outlook on the web (formerly known as Outlook Web App). Valid values are:
 
-- $true: The ActivityBasedAuthenticationTimeoutInterval parameter specifies the period of inactivity that causes logoff in Outlook on the web. This is the default value.
+- $true: The ActivityBasedAuthenticationTimeoutInterval parameter specifies the period of inactivity that causes logoff in Outlook on the web. This value is the default.
 - $false: Automatic logoff based on a period of inactivity in Outlook on the web is disabled.
 
 If you're using single sign-on, use the ActivityBasedAuthenticationTimeoutWithSingleSignOnEnabled parameter.
@@ -698,7 +698,7 @@ Accept wildcard characters: False
 
 The ActivityBasedAuthenticationTimeoutWithSingleSignOnEnabled parameter enables or disables the inactivity interval for automatic logoff for single sign-on in Outlook on the Web. Valid values are:
 
-- $true: The ActivityBasedAuthenticationTimeoutInterval parameter specifies the period of inactivity in Outlook on the web that causes logoff for single sign-on. This is the default value.
+- $true: The ActivityBasedAuthenticationTimeoutInterval parameter specifies the period of inactivity in Outlook on the web that causes logoff for single sign-on. This value is the default.
 - $false: Automatic logoff based on a period of inactivity in Outlook on the web is disabled for single sign-on.
 
 If you aren't using single sign-on, use the ActivityBasedAuthenticationTimeoutEnabled parameter.
@@ -853,7 +853,7 @@ Accept wildcard characters: False
 
 The AsyncSendEnabled parameter specifies whether to enable or disable async send in Outlook on the web. Valid values are:
 
-- $true: Async send is enabled. This is the default value.
+- $true: Async send is enabled. This value is the default.
 - $false: Async send is disabled.
 
 ```yaml
@@ -877,7 +877,7 @@ This parameter is available only in the cloud-based service.
 The AuditDisabled parameter specifies whether to disable or enable mailbox auditing for the organization. Valid values are:
 
 - $true: Mailbox auditing is disabled for the organization.
-- $false: Allow mailbox auditing in the organization. This is the default value.
+- $false: Allow mailbox auditing in the organization. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -897,9 +897,14 @@ Accept wildcard characters: False
 
 This parameter is available only in the cloud-based service.
 
-The AutodiscoverPartialDirSync parameter is for scenarios where tenants have Directory Synced some of their Active Directory users into the cloud, but still have on-premises Exchange users that are not Directory Synced. Setting this parameter to $true will cause unknown users to be redirected to the on-premises endpoint and will allow on-premises users to discover their mailbox automatically. Online email addresses will be susceptible to enumeration. We recommend full Directory Sync for all Active Directory users and leaving this parameter with the default $false.
+The AutodiscoverPartialDirSync parameter is for scenarios where tenants have Directory Synced some of their Active Directory users into the cloud, but still have on-premises Exchange users that are not Directory Synced. Valid values are:
 
-After you enable AutodiscoverPartialDirSync, it will take approximately 3 hours to fully saturate across the cloud.
+- $true: Unknown users are redirected to the on-premises endpoint and on-premises users are allowed to discover their mailbox automatically.
+- $false: This value is the default.
+
+We recommend full Directory Sync for all Active Directory users and leaving this parameter with the default value $false.
+
+After you enable AutodiscoverPartialDirSync, it takes approximately 3 hours to fully saturate across the cloud.
 
 ```yaml
 Type: Boolean
@@ -944,7 +949,7 @@ This parameter is available only in the cloud-based service.
 
 The AutoExpandingArchive switch enables the auto-expanding archiving feature in an Exchange Online organization. You don't need to specify a value with this switch.
 
-After you enable auto-expanding archiving, additional storage space is automatically added to a user's archive mailbox when it approaches the storage limit. Note that a user's archive mailbox has to be enabled before auto-expanding archiving can take effect. Also note that after you enable auto-expanding archiving for your organization, it can't be disabled.
+After you enable auto-expanding archiving, additional storage space is automatically added to a user's archive mailbox when it approaches the storage limit. A user's archive mailbox has to be enabled before auto-expanding archiving can take effect. Also note that after you enable auto-expanding archiving for your organization, it can't be disabled.
 
 ```yaml
 Type: SwitchParameter
@@ -987,7 +992,7 @@ This parameter is available only in the cloud-based service.
 The BlockMoveMessagesForGroupFolders parameter specifies whether to prevent group owners or group members from moving messages between folders in Microsoft 365 Groups. Valid values are:
 
 - $true: Group owners or group members can't move messages between folders in Microsoft 365 groups (manually or vial Inbox rules).
-- $false: Group owners or group members can move messages between folders in Microsoft 365 groups. This is the default value.
+- $false: Group owners or group members can move messages between folders in Microsoft 365 groups. This value is the default.
 
 The value of this parameter is meaningful only when the value of the IsGroupFoldersAndRulesEnabled parameter is $true.
 
@@ -1108,7 +1113,7 @@ This parameter is available only in the cloud-based service.
 The BookingsEnabled parameter specifies whether to enable Microsoft Bookings in an organization. Valid values are:
 
 - $true: Bookings is enabled.
-- $false: Bookings is disabled. This is the default value.
+- $false: Bookings is disabled. This value is the default.
 
 Microsoft Bookings is an online and mobile app for small businesses who provide appointment services to customers.
 
@@ -1302,7 +1307,7 @@ This parameter is available only in the cloud-based service.
 The BookingsPaymentsEnabled parameter specifies whether to enable the online payment node inside Bookings. Valid values are:
 
 - $true: Online payments are enabled.
-- $false: Online payments are disabled. This is the default value.
+- $false: Online payments are disabled. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -1388,7 +1393,7 @@ This parameter is available only in the cloud-based service.
 The BookingsSocialSharingRestricted parameter specifies whether users can see the social sharing options inside Bookings. Valid values are:
 
 - $true: Social sharing options are restricted.
-- $false: Users can see social sharing options inside Bookings. This is the default value.
+- $false: Users can see social sharing options inside Bookings. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -1497,7 +1502,7 @@ Accept wildcard characters: False
 
 The ConnectorsActionableMessagesEnabled parameter specifies whether to enable or disable actionable buttons in messages (connector cards) from connected apps on Outlook on the web. Valid values are:
 
-- $true: Action buttons in connector cards are enabled, which allows you to take quick actions directly from Outlook on the web (for example, Like or Comment). This is the default value.
+- $true: Action buttons in connector cards are enabled, which allows you to take quick actions directly from Outlook on the web (for example, Like or Comment). This value is the default.
 - $false: Action buttons in connector cards are disabled.
 
 For more information about actionable messages in connected apps, see [Connect apps to your inbox in Outlook on the web](https://support.microsoft.com/office/3d41b99c-bf8d-47d4-bc7a-97758b74689d).
@@ -1520,7 +1525,7 @@ Accept wildcard characters: False
 
 The ConnectorsEnabled parameter specifies whether to enable or disable all connected apps in organization. Valid values are:
 
-- $true: Connectors are enabled. This is the default value.
+- $true: Connectors are enabled. This value is the default.
 - $false: Connectors are disabled.
 
 The workloads that are affected by this parameter are Outlook, SharePoint, Teams, and Viva Engage.
@@ -1545,7 +1550,7 @@ This parameter is available only in the cloud-based service.
 
 The ConnectorsEnabledForOutlook parameter specifies whether to enable or disable connected apps in Outlook on the web. Valid values are:
 
-- $true: Connectors are enabled. This is the default value.
+- $true: Connectors are enabled. This value is the default.
 - $false: Connectors are disabled.
 
 To enable and disable the ability to use connectors on specific Microsoft 365 Groups, set the value of this parameter to $true, and then use the ConnectorsEnabled switch on the Set-UnifiedGroup cmdlet.
@@ -1572,7 +1577,7 @@ This parameter is available only in the cloud-based service.
 
 The ConnectorsEnabledForSharepoint parameter specifies whether to enable or disable connected apps on SharePoint. Valid values are:
 
-- $true: Connectors are enabled. This is the default value.
+- $true: Connectors are enabled. This value is the default.
 - $false: Connectors are disabled.
 
 ```yaml
@@ -1595,7 +1600,7 @@ This parameter is available only in the cloud-based service.
 
 The ConnectorsEnabledForTeams parameter specifies whether to enable or disable connected apps on Teams. Valid values are:
 
-- $true: Connectors are enabled. This is the default value.
+- $true: Connectors are enabled. This value is the default.
 - $false: Connectors are disabled.
 
 ```yaml
@@ -1618,7 +1623,7 @@ This parameter is available only in the cloud-based service.
 
 The ConnectorsEnabledForYammer parameter specifies whether to enable or disable connected apps on Viva Engage. Valid values are:
 
-- $true: Connectors are enabled. This is the default value.
+- $true: Connectors are enabled. This value is the default.
 - $false: Connectors are disabled.
 
 ```yaml
@@ -1840,7 +1845,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The valid input range for this parameter is from 0 through 2199023254529 bytes(2 TB). If you enter a value of unlimited, no size limit is imposed on the public folder.
 
@@ -1870,7 +1875,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The valid input range for this parameter is from 0 through 2199023254529 bytes (2 TB). If you enter a value of unlimited, no size limit is imposed on the public folder.
 
@@ -1920,7 +1925,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The valid input range for this parameter is from 0 through 2199023254529 bytes (2 TB). If you enter a value of unlimited, no size limit is imposed on the public folder.
 
@@ -1945,7 +1950,7 @@ This parameter is available only in the cloud-based service.
 The DelayedDelicensingEnabled parameter enables or disables a 30 day grace period for Exchange Online license removals from mailboxes. Valid values are:
 
 - $true: Exchange Online license removals from mailboxes are delayed by 30 days. Admins can use the delay to identify potential mistakes and avoid disruptions for affected users.
-- $false: Exchange Online license removals from mailboxes aren't delayed. This is the default value.
+- $false: Exchange Online license removals from mailboxes aren't delayed. This value is the default.
 
 Use the TenantAdminNotificationForDelayedDelicensingEnabled parameter to turn on weekly Service Health advisory notifications for admins about the number of Exchange Online delicensed users who are in the 30 day grace period during the specified 8 day interval. For more information about Service Health, see [How to check Microsoft 365 service health](https://learn.microsoft.com/microsoft-365/enterprise/view-service-health).
 
@@ -1980,7 +1985,7 @@ This parameter is available only in the cloud-based service.
 The DirectReportsGroupAutoCreationEnabled parameter specifies whether to enable or disable the automatic creation of direct report Microsoft 365 Groups. Valid values are:
 
 - $true: The automatic creation of direct report Microsoft 365 Groups is enabled.
-- $false: The automatic creation of direct report Microsoft 365 Groups is disabled. This is the default value.
+- $false: The automatic creation of direct report Microsoft 365 Groups is disabled. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -2120,8 +2125,8 @@ This parameter is available only in the cloud-based service.
 
 The ElcProcessingDisabled parameter specifies whether to enable or disable the processing of mailboxes by the Managed Folder Assistant. Valid values are:
 
-- $true: The Managed Folder Assistant isn't allowed to process mailboxes in the organization. Note that this setting will be ignored on a mailbox if a retention policy that has Preservation Lock enabled is applied to that mailbox.
-- $false: The Managed Folder Assistant is allowed to process mailboxes in the organization. This is the default value.
+- $true: The Managed Folder Assistant isn't allowed to process mailboxes in the organization. This setting is ignored on a mailbox if a retention policy that has Preservation Lock enabled is applied to that mailbox.
+- $false: The Managed Folder Assistant is allowed to process mailboxes in the organization. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -2184,7 +2189,7 @@ This parameter is available only in on-premises Exchange.
 The EnableDownloadDomains parameter specifies that Outlook on the web downloads inline images from a different domain than the rest of Outlook on the web. Valid values are:
 
 - $true: Outlook on the web uses a different download domain for inline images (for example, downloads.contoso.com). Before you enable this setting, you need to create a CNAME record and certificate for this domain, and add the domain to the ExternalDownloadHostName and InternalDownloadHostName parameters on the Set-OwaVirtualDirectory cmdlet.
-- $false: The setting is disabled. This is the default value.
+- $false: The setting is disabled. This value is the default.
 
 For more information about the security vulnerability that's addressed by this parameter, and for detailed configuration instructions, see [CVE 2021 1730](https://msrc.microsoft.com/update-guide/vulnerability/CVE-2021-1730).
 
@@ -2249,7 +2254,7 @@ This parameter is available only in the cloud-based service.
 The EnableOutlookEvents parameter specifies whether Outlook or Outlook on the web (formerly known as Outlook Web App) automatically discovers events from email messages and adds them to user calendars. Valid values are:
 
 - $true: Discovery of events from email messages is enabled.
-- $false: Discovery of events from email messages is disabled. This is the default value.
+- $false: Discovery of events from email messages is disabled. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -2272,7 +2277,7 @@ This parameter is available only in the cloud-based service.
 The EndUserDLUpgradeFlowsDisabled parameter specifies whether to prevent users from upgrading their own distribution groups to Microsoft 365 Groups in an Exchange Online organization. Valid values are:
 
 - $true: Users can upgrade distribution groups that they own to Microsoft 365 Groups.
-- $false: Users can't upgrade distribution groups that they own to Microsoft 365 Groups. This is the default value.
+- $false: Users can't upgrade distribution groups that they own to Microsoft 365 Groups. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -2295,7 +2300,7 @@ This parameter is available only in the cloud-based service.
 The EndUserMailNotificationForDelayedDelicensingEnabled parameter enables or disables periodic email warnings to affected users that have pending Exchange Online license removal requests on their mailboxes. Valid values are:
 
 - $true: Affected users receive periodic email notifications about losing access to their mailbox starting ~18 days after the Exchange Online license was removed.
-- $false: Affected users don't receive periodic email notifications about losing access to their mailbox. This is the default value.
+- $false: Affected users don't receive periodic email notifications about losing access to their mailbox. This value is the default.
 
 The value of this parameter is meaningful on when the value of the DelayedDelicensingEnabled parameter is $true.
 
@@ -2400,7 +2405,7 @@ The EwsApplicationAccessPolicy parameter specifies the client applications that
 - EnforceAllowList: Only applications specified by the EwsAllowList parameter are allowed to access EWS and REST. Access by other applications is blocked.
 - EnforceBlockList: All applications are allowed to access EWS and REST, except for the applications specified by the EwsBlockList parameter.
 
-Note that if the EwsAllowEntourage, EwsAllowMacOutlook or EwsAllowOutlook parameters are set to a true or false value, they take precedence for access to EWS by Entourage, Mac Outlook, or Outlook, respectively.
+If the EwsAllowEntourage, EwsAllowMacOutlook or EwsAllowOutlook parameters are set to a true or false value, they take precedence for access to EWS by Entourage, Mac Outlook, or Outlook, respectively.
 
 ```yaml
 Type: EwsApplicationAccessPolicy
@@ -2444,7 +2449,7 @@ The EwsEnabled parameter specifies whether to globally enable or disable EWS acc
 
 - $true: All EWS access is enabled.
 - $false: All EWS access is disabled.
-- $null (blank): The setting isn't configured. Access to EWS is controlled individually by the related EWS parameters (for example EwsAllowEntourage). This is the default value.
+- $null (blank): The setting isn't configured. Access to EWS is controlled individually by the related EWS parameters (for example EwsAllowEntourage). This value is the default.
 
 This parameter has no affect on access to REST.
 
@@ -2562,7 +2567,7 @@ This parameter is available only in the cloud-based service.
 
 The FindTimeLockPollForAttendeesEnabled controls whether the **Lock poll for attendees** setting is managed by the organization. Valid values are:
 
-- $true: **Lock poll for attendees** is on. Attendees will not be able to suggest new times or edit other attendees. The meeting organizer can't turn off this setting (always on).
+- $true: **Lock poll for attendees** is on. Attendees can't suggest new times or edit other attendees. The meeting organizer can't turn off this setting (always on).
 - $false: By default, **Lock poll for attendees** is off (initial default) or on (the user saved settings from last poll), but the meeting organizer is allowed to turn the setting off or on to allow or prevent attendees from suggesting new times or editing attendees.
 
 This setting overrides individual user settings.
@@ -2848,7 +2853,7 @@ This parameter is available only in the cloud-based service.
 The IsGroupFoldersAndRulesEnabled specifies whether group owners (by default) can create folders and move messages (manually or by using Inbox rules) in Microsoft 365 Groups. Valid values are:
 
 - $true: Group owners can create folders and move messages between folders in Microsoft 365 Groups.
-- $false: Group owners can't create folders or move messages between folders in Microsoft 365 Groups. This is the default value.
+- $false: Group owners can't create folders or move messages between folders in Microsoft 365 Groups. This value is the default.
 
 To allow group owners to allow group users to create folders and moved messages in Microsoft 365 Groups, use the IsGroupMemberAllowedToEditContent parameter.
 
@@ -2882,7 +2887,7 @@ The IsGroupMemberAllowedToEditContent parameter specifies whether group owners c
 
   • Create, edit, copy, and delete Inbox rules.
 
-- $false: Group owners can't use the **All members will be able to create, edit, move, copy, and delete mail folders and rules within the group** setting in the group properties in Outlook on the web to allow group members to manage folders and messages in Microsoft 365 Groups. Only group owners can manage folders and messages in Microsoft 365 Groups. This is the default value.
+- $false: Group owners can't use the **All members will be able to create, edit, move, copy, and delete mail folders and rules within the group** setting in the group properties in Outlook on the web to allow group members to manage folders and messages in Microsoft 365 Groups. Only group owners can manage folders and messages in Microsoft 365 Groups. This value is the default.
 
 The value of this parameter is meaningful only when the value of the IsGroupFoldersAndRulesEnabled parameter is $true.
 
@@ -2909,7 +2914,7 @@ Accept wildcard characters: False
 The LeanPopoutEnabled parameter specifies whether to enable faster loading of pop-out messages in Outlook on the web for Internet Explorer and Microsoft Edge. Valid values are:
 
 - $true: Lean pop-outs are enabled.
-- $false: Lean pop-outs are disabled. This is the default value.
+- $false: Lean pop-outs are disabled. This value is the default.
 
 **Notes**:
 
@@ -2934,7 +2939,7 @@ Accept wildcard characters: False
 
 The LinkPreviewEnabled parameter specifies whether link preview of URLs in email messages is allowed for the organization. Valid values are:
 
-- $true: Link preview of URLs in email messages is allowed. Users can enable or disable link preview in their Outlook on the web settings. This is the default value.
+- $true: Link preview of URLs in email messages is allowed. Users can enable or disable link preview in their Outlook on the web settings. This value is the default.
 - $false: Link preview of URLs in email messages is not allowed. Users can't enable link preview in their Outlook on the web settings.
 
 ```yaml
@@ -3087,7 +3092,7 @@ This parameter is available only in on-premises Exchange.
 
 The MapiHttpEnabled parameter enables or disables access to mailboxes in Outlook by using MAPI over HTTP. Valid values are:
 
-- $true: Access to mailboxes by using MAPI over HTTP is enabled. This is the default value.
+- $true: Access to mailboxes by using MAPI over HTTP is enabled. This value is the default.
 - $false: Access to mailboxes by using MAPI over HTTP is disabled.
 
 You can use the MapiHttpEnabled parameter on the Set-CASMailbox cmdlet to override the global MAPI over HTTP settings for individual users.
@@ -3291,7 +3296,7 @@ Accept wildcard characters: False
 
 This parameter is available only in on-premises Exchange.
 
-The MicrosoftExchangeRecipientEmailAddresses parameter specifies one or more email addresses for the recipient. All valid Microsoft Exchange email address types may be used. You can specify multiple values for this parameter as a comma-delimited list. If the MicrosoftExchangeRecipientEmailAddressPolicyEnabled parameter is set to $true, the email addresses are automatically generated by the default email address policy. This means you can't use the MicrosoftExchangeRecipientEmailAddresses parameter.
+The MicrosoftExchangeRecipientEmailAddresses parameter specifies one or more email addresses for the recipient. All valid Microsoft Exchange email address types might be used. You can specify multiple values for this parameter as a comma-delimited list. If the MicrosoftExchangeRecipientEmailAddressPolicyEnabled parameter is set to $true, the email addresses are automatically generated by the default email address policy. This means you can't use the MicrosoftExchangeRecipientEmailAddresses parameter.
 
 Email addresses that you specify by using the MicrosoftExchangeRecipientEmailAddresses parameter replace any existing email addresses already configured.
 
@@ -3413,11 +3418,9 @@ This parameter is available only in the cloud-based service.
 
 The MobileAppEducationEnabled specifies whether to show or hide the Outlook for iOS and Android education reminder in Outlook on the web (formerly known as Outlook Web App). Valid values are:
 
-- $true: Outlook on the web and Outlook desktop will show the education reminder to users who aren't using Outlook for iOS and Android to check their company email and calendar events. This is the default value.
+- $true: Outlook on the web and Outlook desktop show the education reminder to users who aren't using Outlook for iOS and Android to check their company email and calendar events. This value is the default.
 - $false: The Outlook for iOS and Android education reminder is disabled.
 
-This setting will affect Outlook desktop at some point in the future.
-
 ```yaml
 Type: Boolean
 Parameter Sets: ShortenEventScopeParameter, DelayedDelicensingParameterSet
@@ -3487,7 +3490,7 @@ The OnlineMeetingsByDefaultEnabled parameter specifies whether to set all meetin
 - $false: All meetings are not online by default.
 - $null: If the organization value has not been specified, the default behavior is for meetings to be online.
 
-If a user has already directly interacted with this setting in Outlook or Outlook on the web (formerly known as Outlook Web App or OWA), the value of this parameter is ignored. Eventually, this parameter will override the Outlook-configured setting.
+If a user has already directly interacted with this setting in Outlook or Outlook on the web (formerly known as Outlook Web App or OWA), the value of this parameter is ignored.
 
 ```yaml
 Type: Boolean
@@ -3530,7 +3533,7 @@ This parameter is available only in the cloud-based service.
 The OutlookGifPickerDisabled parameter disables the GIF Search (powered by Bing) feature that's built into the Compose page in Outlook on the web. Valid values are:
 
 - $true: GIF Search in Outlook on the web is disabled.
-- $false: GIF Search in Outlook on the web is enabled. This is the default value.
+- $false: GIF Search in Outlook on the web is enabled. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -3552,7 +3555,7 @@ This parameter is available only in the cloud-based service.
 
 The OutlookMobileGCCRestrictionsEnabled parameter specifies whether to enable or disable features within Outlook for iOS and Android that are not FedRAMP compliant for Microsoft 365 US Government Community Cloud (GCC) customers. Valid values are:
 
-- $true: Disable features that aren't FedRAMP compliant for GCC customers. This is the default value for all GCC customers.
+- $true: Disable features that aren't FedRAMP compliant for GCC customers. This value is the default for all GCC customers.
 - $false: Enable features that aren't FedRAMP compliant for GCC customers.
 
 The Outlook for iOS and Android feature and services that are not FedRAMP compliant for Microsoft 365 US Government customers include:
@@ -3667,8 +3670,8 @@ This parameter is available only in Exchange Server 2010.
 
 The PermanentlyDeleteDisabled parameter specifies whether to disable the PermanentlyDelete retention action for messaging records management (MRM). Valid values are:
 
-- $true The PermanentlyDelete retention action is disabled. This setting only prevents items from being permanently deleted. It doesn't modify existing policies, block the creation of policies with the PermanentlyDelete action or notify users that thePermanentlyDelete action won't actually take effect.
-- $false The PermanentlyDelete retention action is enabled. This is the default value.
+- $true The PermanentlyDelete retention action is disabled. This setting only prevents items from being permanently deleted. It doesn't modify existing policies, block the creation of policies with the PermanentlyDelete action, or notify users that thePermanentlyDelete action doesn't actually take effect.
+- $false The PermanentlyDelete retention action is enabled. This value is the default.
 
 A message that's permanently deleted can't be recovered by using the Recoverable Items folder. Additionally, permanently deleted messages aren't returned by a Discovery search, unless litigation hold or single item recovery is enabled for the mailbox.
 
@@ -3690,7 +3693,7 @@ Accept wildcard characters: False
 
 This parameter is available only in the cloud-based service.
 
-This parameter has been deprecated and is no longer used.
+This parameter is deprecated and no longer used.
 
 ```yaml
 Type: Boolean
@@ -3716,7 +3719,7 @@ The PostponeRoamingSignaturesUntilLater parameter controls whether roaming signa
 
   Previously, the only way to disable roaming signatures in Outlook on the web was to open a support ticket. With the introduction of this parameter and value, admins can disable roaming signatures themselves.
 
-- $false: Roaming signatures are enabled for Outlook on the web and the new Outlook for Windows. This is the default value.
+- $false: Roaming signatures are enabled for Outlook on the web and the new Outlook for Windows. This value is the default.
 
 We recommend that independent software vendors (ISVs) onboard to the [signature API](https://learn.microsoft.com/javascript/api/outlook/office.body#outlook-office-body-setsignatureasync-member(1)) based on [event-based hooks
 ](https://learn.microsoft.com/office/dev/add-ins/outlook/autolaunch).
@@ -3757,7 +3760,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
 
-The PublicComputersDetectionEnabled parameter specifies whether Outlook on the web will detect when a user signs from a public or private computer or network, and then enforces the attachment handling settings from public networks. The default is $false. However, if you set this parameter to $true, Outlook on the web will determine if the user is signing in from a public computer, and all public attachment handling rules will be applied and enforced.
+The PublicComputersDetectionEnabled parameter specifies whether Outlook on the web detects when a user signs from a public or private computer or network, and then enforces the attachment handling settings from public networks. The default is $false. However, if you set this parameter to $true, Outlook on the web determines if the user is signing in from a public computer, and all public attachment handling rules are applied and enforced.
 
 ```yaml
 Type: Boolean
@@ -3800,7 +3803,7 @@ This parameter is available only in on-premises Exchange.
 The PublicFolderMailboxesLockedForNewConnections parameter specifies whether users are allowed to make new connections to public folder mailboxes. Valid values are:
 
 - $true: Users aren't allowed to make new connections to public folder mailboxes. You use this setting during the final stages of public folder migrations.
-- $false: Users are allowed to make new connections to public folder mailboxes. This is the default value.
+- $false: Users are allowed to make new connections to public folder mailboxes. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -3823,7 +3826,7 @@ This parameter is available only in on-premises Exchange.
 The PublicFolderMailboxesMigrationComplete parameter is used during public folder migration.
 
 - $true: Queued messages are rerouted to the new destination.
-- $false (This is the default value)
+- $false (default value)
 
 ```yaml
 Type: Boolean
@@ -3886,7 +3889,7 @@ Accept wildcard characters: False
 The PublicFolderShowClientControl parameter enables or disables the control access feature for public folders in Microsoft Outlook. Valid values are:
 
 - $true: User access to public folders in Outlook is controlled by the value of the PublicFolderClientAccess parameter on the Set-CASMailbox cmdlet (the default value is $false).
-- $false: This is the default value. User access to public folders in Outlook is enabled (the control access feature is disabled). The value of the PublicFolderClientAccess parameter on the Set-CASMailbox cmdlet is meaningless.
+- $false: This value is the default. User access to public folders in Outlook is enabled (the control access feature is disabled). The value of the PublicFolderClientAccess parameter on the Set-CASMailbox cmdlet is meaningless.
 
 ```yaml
 Type: Boolean
@@ -4060,8 +4063,8 @@ This parameter is available only in the cloud-based service.
 
 The SendFromAliasEnabled parameter allows mailbox users to send messages using aliases (proxy addresses). Valid values are:
 
-- $true: Aliases on messages will no longer be rewritten to their primary SMTP addresses. Compatible Outlook clients will allow sending from aliases and replying to aliases. Even without an updated Outlook client, users might see changes in behavior because the setting affects all messages sent and received by a mailbox.
-- $false: Aliases on messages sent or received will be rewritten to their primary email address. This is the default value.
+- $true: Aliases on messages are no longer rewritten to their primary SMTP addresses. Compatible Outlook clients allow sending from aliases and replying to aliases. Even without an updated Outlook client, users might see changes in behavior because the setting affects all messages sent and received by a mailbox.
+- $false: Aliases on messages sent or received are rewritten to their primary email address. This value is the default.
 
 For more information about the availability of the feature in Outlook on the web, see the [Microsoft 365 roadmap item](https://www.microsoft.com/microsoft-365/roadmap?filters=Exchange&searchterms=59437). For Outlook for Windows, see this [Microsoft 365 roadmap item](https://www.microsoft.com/microsoft-365/roadmap?filters=Outlook&searchterms=64123).
 
@@ -4121,7 +4124,7 @@ Accept wildcard characters: False
 
 The SmtpActionableMessagesEnabled parameter specifies whether to enable or disable action buttons in email messages in Outlook on the web. Valid values are:
 
-- $true: Action buttons in email messages are enabled. This is the default value.
+- $true: Action buttons in email messages are enabled. This value is the default.
 - $false: Action buttons in email messages are disabled.
 
 ```yaml
@@ -4145,7 +4148,7 @@ This parameter is available only in the cloud-based service.
 The TenantAdminNotificationForDelayedDelicensingEnabled parameter enables or disables weekly admin Service Health advisory notifications that are sent to admins. Valid values are:
 
 - $true: Weekly Service Health advisory notifications are sent to admins about the number of Exchange Online delicensed users who are in the 30 day grace period during the specified 8 day interval.
-- $false: Disable weekly Service Health advisory notifications about the number of Exchange Online delicensed users. This is the default value.
+- $false: Disable weekly Service Health advisory notifications about the number of Exchange Online delicensed users. This value is the default.
 
 For more information about Service Health, see [How to check Microsoft 365 service health](https://learn.microsoft.com/microsoft-365/enterprise/view-service-health).
 
@@ -4191,7 +4194,7 @@ Accept wildcard characters: False
 
 This parameter is available only in on-premises Exchange.
 
-This parameter has been deprecated and is no longer used.
+This parameter is deprecated and no longer used.
 
 ```yaml
 Type: MultiValuedProperty
@@ -4249,7 +4252,7 @@ Accept wildcard characters: False
 
 This parameter is available only in the cloud-based service.
 
-The VisibleMeetingUpdateProperties parameter specifies whether meeting message updates will be auto-processed on behalf of attendees. Auto-processed updates are applied to the attendee's calendar item, and then the meeting message is moved to the deleted items. The attendee never sees the update in their inbox, but their calendar is updated.
+The VisibleMeetingUpdateProperties parameter specifies whether meeting message updates are auto-processed on behalf of attendees. Auto-processed updates are applied to the attendee's calendar item, and then the meeting message is moved to the deleted items. The attendee never sees the update in their inbox, but their calendar is updated.
 
 This parameter uses the syntax: `"MeetingProperty1:MeetingStartTimeWithinXMinutes1,MeetingProperty2:MeetingStartTimeWithinXMinutes2,...MeetingPropertyN:MeetingStartTimeWithinXMinutesN"`.
 
@@ -4267,11 +4270,11 @@ The valid meeting properties to monitor for updates are:
 - Reminder: The reminder time.
 - AllProperties: Any meeting change.
 
-If you don't specify a MeetingStartTimeWithinXMinutes value for the meeting property, any change to the meeting property will result in visible meeting update messages (regardless of how soon or how far away the meeting is). For updates to recurring meetings, the meeting start time is the start time of the next occurrence in the series.
+If you don't specify a MeetingStartTimeWithinXMinutes value for the meeting property, any change to the meeting property results in visible meeting update messages (regardless of how soon or how far away the meeting is). For updates to recurring meetings, the meeting start time is the start time of the next occurrence in the series.
 
 The default value is `"Location,AllProperties:15"`: changes to the meeting location at any time, or changes to other meeting properties within 15 minutes of the meeting start time results in visible meeting update messages.
 
-In the following scenarios, meeting update messages are not auto-processed, regardless of the values specified in this parameter. In these scenarios, attendees will always see meeting update messages in their Inbox:
+In the following scenarios, meeting update messages are not auto-processed, regardless of the values specified in this parameter. In these scenarios, attendees always see meeting update messages in their Inbox:
 
 - The update contains a change to the meeting date, time, or recurrence pattern.
 - The meeting message is received for a delegated shared calendar.
@@ -4321,7 +4324,7 @@ This parameter is available only in the cloud-based service.
 The WebPushNotificationsDisabled parameter specifies whether to enable or disable Web Push Notifications in Outlook on the Web. This feature provides web push notifications which appear on a user's desktop while the user is not using Outlook on the Web. This brings awareness of incoming messages while they are working elsewhere on their computer. Valid values are:
 
 - $true: Web Push Notifications are disabled.
-- $false: Web Push Notifications are enabled. This is the default value.
+- $false: Web Push Notifications are enabled. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -4344,7 +4347,7 @@ This parameter is available only in the cloud-based service.
 The WebSuggestedRepliesDisabled parameter specifies whether to enable or disable Suggested Replies in Outlook on the web. This feature provides suggested replies to emails so users can easily and quickly respond to messages. Valid values are:
 
 - $true: Suggested Replies are disabled.
-- $false: Suggested Replies are enabled. This is the default value.
+- $false: Suggested Replies are enabled. This value is the default.
 
 ```yaml
 Type: Boolean
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-OrganizationRelationship.md b/exchange/exchange-ps/ExchangePowerShell/Set-OrganizationRelationship.md
index 32e1291fcb..2e0b8862f8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-OrganizationRelationship.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-OrganizationRelationship.md
@@ -13,7 +13,7 @@ title: Set-OrganizationRelationship
 # Set-OrganizationRelationship
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-OrganizationRelationship cmdlet to modify existing organization relationships. Organization relationships define the settings that are used with external Exchange organizations to access calendar free/busy information or to move mailboxes between on-premises Exchange servers and Exchange Online as part of hybrid deployments.
 
@@ -52,7 +52,7 @@ Set-OrganizationRelationship [-Identity] <OrganizationRelationshipIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -98,10 +98,10 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
 
-The ArchiveAccessEnabled parameter specifies whether the organization relationship has been configured to provide remote archive access. Valid values are:
+The ArchiveAccessEnabled parameter specifies whether the organization relationship is configured to provide remote archive access. Valid values are:
 
 - $true: The external organization provides remote access to mailbox archives.
-- $false: The external organization doesn't provide remote access to mailbox archives. This is the default value
+- $false: The external organization doesn't provide remote access to mailbox archives. This value is the default
 
 ```yaml
 Type: Boolean
@@ -143,9 +143,9 @@ Accept wildcard characters: False
 The DeliveryReportEnabled parameter specifies whether Delivery Reports should be shared over the organization relationship. Valid values are:
 
 - $true: Delivery Reports should be shared over the organization relationship. This value means the organization has agreed to share all Delivery Reports with the external organization, and the organization relationship should be used to retrieve Delivery Report information from the external organization.
-- $false: Delivery Reports shouldn't be shared over the organization relationship. This is the default value
+- $false: Delivery Reports shouldn't be shared over the organization relationship. This value is the default
 
-For message tracking to work in a cross-premises Exchange scenario, this parameter must be set to $true on both sides of the organization relationship. If the value of this parameter is set to $false on one or both sides of the organization relationship, message tracking between the organizations won't work in either direction.
+For message tracking to work in a cross-premises Exchange scenario, this parameter must be set to $true on both sides of the organization relationship. If the value of this parameter is set to $false on one or both sides of the organization relationship, message tracking between the organizations doesn't work in either direction.
 
 ```yaml
 Type: Boolean
@@ -203,7 +203,7 @@ Accept wildcard characters: False
 
 The Enabled parameter specifies whether to enable the organization relationship. Valid values are:
 
-- $true: The organization relationship is enabled. This is the default value.
+- $true: The organization relationship is enabled. This value is the default.
 - $false: The organization relationship is disabled. This value completely stops sharing for the organization relationship.
 
 ```yaml
@@ -245,7 +245,7 @@ Accept wildcard characters: False
 The FreeBusyAccessEnabled parameter specifies whether the organization relationship should be used to retrieve free/busy information from the external organization. Valid values are:
 
 - $true: Free/busy information is retrieved from the external organization.
-- $false: Free/busy information isn't retrieved from the external organization. This is the default value.
+- $false: Free/busy information isn't retrieved from the external organization. This value is the default.
 
 You control the free/busy access level and scope by using the FreeBusyAccessLevel and FreeBusyAccessScope parameters.
 
@@ -344,7 +344,7 @@ Accept wildcard characters: False
 The MailboxMoveEnabled parameter specifies whether the organization relationship enables moving mailboxes to or from the external organization. Valid values are:
 
 - $true: Mailbox moves to or from the external organization are allowed.
-- $false: Mailbox moves to from the external organization aren't allowed. This is the default value.
+- $false: Mailbox moves to from the external organization aren't allowed. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -396,7 +396,7 @@ Accept wildcard characters: False
 The MailTipsAccessEnabled parameter specifies whether MailTips for users in this organization are returned over this organization relationship. Valid values are:
 
 - $true: MailTips for users in this organization are returned over the organization relationship.
-- $false: MailTips for users in this organization aren't returned over the organization relationship. This is the default value.
+- $false: MailTips for users in this organization aren't returned over the organization relationship. This value is the default.
 
 You control the MailTips access level by using the MailTipsAccessLevel parameter.
 
@@ -419,8 +419,8 @@ Accept wildcard characters: False
 The MailTipsAccessLevel parameter specifies the level of MailTips data externally shared over this organization relationship. This parameter can have the following values:
 
 - All: All MailTips are returned, but the recipients in the remote organization are considered external. For the Auto Reply MailTip, the external Auto Reply message is returned.
-- Limited: Only those MailTips that could prevent a non-delivery report (NDR) or an Auto Reply are returned. Custom MailTips, the Large Audience MailTip, and Moderated Recipient MailTips won't be returned.
-- None: No MailTips are returned to the remote organization. This is the default value.
+- Limited: Only those MailTips that could prevent a non-delivery report (NDR) or an Auto Reply are returned. Custom MailTips, the Large Audience MailTip, and Moderated Recipient MailTips aren't returned.
+- None: No MailTips are returned to the remote organization. This value is the default.
 
 This parameter is only meaningful when the MailTipsAccessEnabled parameter value is $true.
 
@@ -534,7 +534,7 @@ Accept wildcard characters: False
 The PhotosEnabled parameter specifies whether photos for users in the internal organization are returned over the organization relationship. Valid values are:
 
 - $true: Photos for users in this organization are returned over the organization relationship.
-- $false: Photos for users in this organization aren't returned over the organization relationship. This is the default value.
+- $false: Photos for users in this organization aren't returned over the organization relationship. This value is the default.
 
 ```yaml
 Type: Boolean
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-OutboundConnector.md b/exchange/exchange-ps/ExchangePowerShell/Set-OutboundConnector.md
index b270f10022..aa46e84863 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-OutboundConnector.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-OutboundConnector.md
@@ -50,7 +50,7 @@ Set-OutboundConnector [-Identity] <OutboundConnectorIdParameter>
 ## DESCRIPTION
 Outbound connectors send email messages to remote domains that require specific configuration options.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -92,7 +92,7 @@ Accept wildcard characters: False
 The AllAcceptedDomains parameter specifies whether the Outbound connector is used in hybrid organizations where message recipients are in accepted domains of the cloud-based organization. Valid values are:
 
 - $true: The Outbound connector is used in hybrid organizations when message recipients are in an accepted domain of the cloud-based organization. This setting requires OnPremises for the ConnectorType value.
-- $false: The Outbound connector isn't used in hybrid organizations. This is the default value.
+- $false: The Outbound connector isn't used in hybrid organizations. This value is the default.
 
 This parameter is effective only for OnPremises connectors.
 
@@ -118,7 +118,7 @@ The CloudServicesMailEnabled parameter specifies whether the connector is used f
 
 Valid values are:
 
-- $true: The connector is used for mail flow in hybrid organizations, so cross-premises headers are preserved or promoted in messages that flow through the connector. This is the default value for connectors that are created by the Hybrid Configuration wizard. Certain X-MS-Exchange-Organization-\* headers in outbound messages that are sent from one side of the hybrid organization to the other are converted to X-MS-Exchange-CrossPremises-\* headers and are thereby preserved in messages. X-MS-Exchange-CrossPremises-\* headers in inbound messages that are received on one side of the hybrid organization from the other are promoted to X-MS-Exchange-Organization-\* headers. These promoted headers replace any instances of the same X-MS-Exchange-Organization-\* headers that already exist in messages.
+- $true: The connector is used for mail flow in hybrid organizations, so cross-premises headers are preserved or promoted in messages that flow through the connector. This value is the default for connectors that are created by the Hybrid Configuration wizard. Certain X-MS-Exchange-Organization-\* headers in outbound messages that are sent from one side of the hybrid organization to the other are converted to X-MS-Exchange-CrossPremises-\* headers and are thereby preserved in messages. X-MS-Exchange-CrossPremises-\* headers in inbound messages that are received on one side of the hybrid organization from the other are promoted to X-MS-Exchange-Organization-\* headers. These promoted headers replace any instances of the same X-MS-Exchange-Organization-\* headers that already exist in messages.
 - $false: The connector isn't used for mail flow in hybrid organizations, so any cross-premises headers are removed from messages that flow through the connector.
 
 ```yaml
@@ -178,7 +178,7 @@ Accept wildcard characters: False
 
 The ConnectorSource parameter specifies how the connector is created. Valid values are:
 
-- Default: The connector is manually created. This is the default value for manually created connectors, and we recommend that you don't change this value.
+- Default: The connector is manually created. This value is the default for manually created connectors, and we recommend that you don't change this value.
 - HybridWizard: The connector is automatically created by the Hybrid Configuration Wizard.
 - Migrated: The connector was originally created in Microsoft Forefront Online Protection for Exchange.
 
@@ -221,7 +221,7 @@ Accept wildcard characters: False
 
 The Enabled parameter specifies whether to enable or disable the Outbound connector. Valid values are:
 
-- $true: The connector is enabled. This is the default value.
+- $true: The connector is enabled. This value is the default.
 - $false: The connector is disabled.
 
 ```yaml
@@ -243,7 +243,7 @@ Accept wildcard characters: False
 The IsTransportRuleScoped parameter specifies whether the Outbound connector is associated with a transport rule (also known as a mail flow rule). Valid values are:
 
 - $true: The connector is associated with a transport rule.
-- $false: The connector isn't associated with a transport rule. This is the default value.
+- $false: The connector isn't associated with a transport rule. This value is the default.
 
 You scope a transport rule to an Outbound connector by using the RouteMessageOutboundConnector parameter on the New-TransportRule or Set-TransportRule cmdlets. Messages that match the conditions of the transport rule are routed to their destinations by using the specified Outbound connector.
 
@@ -263,10 +263,10 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online, Exchange Online Protection
 
-The IsValidated parameter specifies whether the Outbound connector has been validated. Valid values are:
+The IsValidated parameter specifies whether the Outbound connector is validated. Valid values are:
 
-- $true: The connector has been validated,
-- $false: The connector hasn't been validated. This is the default value.
+- $true: The connector is validated,
+- $false: The connector hasn't been validated. This value is the default.
 
 Use the Validate-OutboundConnector cmdlet to validate the connector.
 
@@ -352,7 +352,7 @@ Accept wildcard characters: False
 The RouteAllMessagesViaOnPremises parameter specifies that all messages serviced by this connector are first routed through the on-premises email system. Valid values are:
 
 - $true: Messages are routed through the on-premises email system. This setting requires OnPremises for the ConnectorType value.
-- $false: Messages aren't routed through the on-premises email system. This is the default value.
+- $false: Messages aren't routed through the on-premises email system. This value is the default.
 
 This parameter is effective only for OnPremises connectors.
 
@@ -375,7 +375,7 @@ Accept wildcard characters: False
 The SenderRewritingEnabled parameter specifies that all messages that normally qualify for SRS rewriting are rewritten for routing through the on-premises email system. Valid values are:
 
 - $true: Messages are rewritten by SRS as needed before being routed through the on-premises email system. This setting requires OnPremises for the ConnectorType value.
-- $false: Messages aren't rewritten by SRS before being routed through the on-premises email system. This is the default value.
+- $false: Messages aren't rewritten by SRS before being routed through the on-premises email system. This value is the default.
 
 This parameter is effective only for OnPremises connectors.
 
@@ -424,7 +424,7 @@ Accept wildcard characters: False
 The TestMode parameter specifies whether you want to enabled or disable test mode for the Outbound connector. Valid values are:
 
 - $true: Test mode is enabled.
-- $false: Test mode is disabled. This is the default value.
+- $false: Test mode is disabled. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -469,7 +469,7 @@ The TlsSettings parameter specifies the TLS authentication level that's used for
 - EncryptionOnly: TLS is used only to encrypt the communication channel. No certificate authentication is performed.
 - CertificateValidation: TLS is used to encrypt the channel and certificate chain validation and revocation lists checks are performed.
 - DomainValidation: In addition to channel encryption and certificate validation, the Outbound connector also verifies that the FQDN of the target certificate matches the domain specified in the TlsDomain parameter.
-- $null (blank): This is the default value.
+- $null (blank): This value is the default.
 
 ```yaml
 Type: TlsAuthLevel
@@ -489,7 +489,7 @@ Accept wildcard characters: False
 
 The UseMXRecord parameter enables or disables DNS routing for the connector. Valid values are:
 
-- $true: The connector uses DNS routing (MX records in DNS) to deliver email. This is the default value.
+- $true: The connector uses DNS routing (MX records in DNS) to deliver email. This value is the default.
 - $false: The connector delivers email to one or more smart hosts. This setting requires one or more smart hosts for the SmartHosts value.
 
 ```yaml
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-OutlookAnywhere.md b/exchange/exchange-ps/ExchangePowerShell/Set-OutlookAnywhere.md
index 17d58eac0e..ac591d7859 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-OutlookAnywhere.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-OutlookAnywhere.md
@@ -46,7 +46,7 @@ Set-OutlookAnywhere [-Identity] <VirtualDirectoryIdParameter>
 ## DESCRIPTION
 For more information about the different authentication methods that you can see in this article, see [Understanding HTTP Authentication](https://learn.microsoft.com/dotnet/framework/wcf/feature-details/understanding-http-authentication).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -122,7 +122,7 @@ The ClientAuthenticationMethod parameter specifies the authentication method tha
 - Basic
 - Ntlm
 
-Although you can use this parameter to set only one authentication method, the command won't return an error if you include multiple values.
+Although you can use this parameter to set only one authentication method, the command doesn't return an error if you include multiple values.
 
 ```yaml
 Type: AuthenticationMethod
@@ -209,7 +209,7 @@ The ExtendedProtectionFlags parameter specifies custom settings for Extended Pro
 - AllowDotlessSPN: Required if you want to use Service Principal Name (SPN) values that don't contain FQDNs (for example, HTTP/ContosoMail instead of HTTP/mail.contoso.com). You specify SPNs with the ExtendedProtectionSPNList parameter. This setting makes Extended Protection for Authentication less secure because dotless certificates aren't unique, so it isn't possible to ensure that the client-to-proxy connection was established over a secure channel.
 - NoServiceNameCheck: The SPN list isn't checked to validate a channel binding token. This setting makes Extended Protection for Authentication less secure. We generally don't recommend this setting.
 - Proxy: A proxy server is responsible for terminating the SSL channel. To use this setting, you need to register an SPN by using the ExtendedProtectionSPNList parameter.
-- ProxyCoHosting: HTTP and HTTPS traffic may be accessing the virtual directory and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server.
+- ProxyCoHosting: HTTP and HTTPS traffic might be accessing the virtual directory and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server.
 
 ```yaml
 Type: MultiValuedProperty
@@ -229,7 +229,7 @@ Accept wildcard characters: False
 
 The ExtendedProtectionSPNList parameter specifies a list of valid Service Principal Names (SPNs) if you're using Extended Protection for Authentication on the virtual directory. Valid values are:
 
-- $null: This is the default value.
+- $null: This value is the default.
 - Single SPN or comma delimited list of valid SPNs: The SPN value format is `Protocol\FQDN`. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter.
 
 ```yaml
@@ -250,8 +250,8 @@ Accept wildcard characters: False
 
 The ExtendedProtectionTokenChecking parameter defines how you want to use Extended Protection for Authentication on the virtual directory. Extended Protection for Authentication isn't enabled by default. Valid values are:
 
-- None: Extended Protection for Authentication isn't be used on the virtual directory. This is the default value.
-- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication will work, but may not be as secure as connections that use Extended Protection for Authentication.
+- None: Extended Protection for Authentication isn't be used on the virtual directory. This value is the default.
+- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication work, but might not be as secure as connections that use Extended Protection for Authentication.
 - Require: Extended Protection for Authentication is used for all connections between clients and the virtual directory. If either the client or server doesn't support it, the connection will fail. If you use this value, you also need to set an SPN value for the ExtendedProtectionSPNList parameter.
 
 **Note**: If you use the value Allow or Require and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter.
@@ -276,7 +276,7 @@ The ExternalClientAuthenticationMethod parameter specifies the authentication me
 
 - Basic
 - Ntlm
-- Negotiate (This is the default value)
+- Negotiate (default value)
 
 You can't use this parameter with the DefaultAuthenticationMethods parameter.
 
@@ -299,7 +299,7 @@ Accept wildcard characters: False
 The ExternalClientsRequireSsl parameter specifies whether external Outlook Anywhere clients are required to use Secure Sockets Layer (SSL). Valid values are:
 
 - $true: Clients connecting via Outlook Anywhere from outside the organization are required to use SSL.
-- $false: Clients connecting via Outlook Anywhere from outside the organization aren't required to use SSL. This is the default value.
+- $false: Clients connecting via Outlook Anywhere from outside the organization aren't required to use SSL. This value is the default.
 
 The value of this parameter is related to the value of the SSLOffloading parameter.
 
@@ -366,7 +366,7 @@ Accept wildcard characters: False
 The InternalClientAuthenticationMethod parameter specifies the authentication method that's used to authenticate internal Outlook Anywhere clients. Valid values are:
 
 - Basic
-- Ntlm (This is the default value)
+- Ntlm (default value)
 - Negotiate
 
 You can't use this parameter with the DefaultAuthenticationMethods parameter.
@@ -390,7 +390,7 @@ Accept wildcard characters: False
 The InternalClientsRequireSsl parameter specifies whether internal Outlook Anywhere clients are required to use SSL. Valid values are:
 
 - $true: Clients connecting via Outlook Anywhere from inside the organization are required to use SSL.
-- $false: Clients connecting via Outlook Anywhere from inside the organization aren't required to use SSL. This is the default value.
+- $false: Clients connecting via Outlook Anywhere from inside the organization aren't required to use SSL. This value is the default.
 
 The value of this parameter is related to the value of the SSLOffloading parameter.
 
@@ -448,10 +448,10 @@ Accept wildcard characters: False
 
 The SSLOffloading parameter specifies whether a network device accepts SSL connections and decrypts them before proxying the connections to the Outlook Anywhere virtual directory on the Exchange server. Valid values are:
 
-- $true: Outlook Anywhere clients using SSL don't maintain an SSL connection along the entire network path to the Exchange server. A network device in front of the server decrypts the SSL connections and proxies the unencrypted (HTTP) client connections to the Outlook Anywhere virtual directory. The network segment where HTTP is used should be a secured network. This is the default value.
+- $true: Outlook Anywhere clients using SSL don't maintain an SSL connection along the entire network path to the Exchange server. A network device in front of the server decrypts the SSL connections and proxies the unencrypted (HTTP) client connections to the Outlook Anywhere virtual directory. The network segment where HTTP is used should be a secured network. This value is the default.
 - $false: Outlook Anywhere clients using SSL maintain an SSL connection along the entire network path to the Exchange server. Only SSL connections are allowed to the Outlook Anywhere virtual directory.
 
-This parameter configures the Require SSL value on the Outlook Anywhere virtual directory. When you set this parameter to $true, Require SSL is disabled. When you set this parameter to $fase, Require SSL is enabled. However, it may take several minutes before the change is visible in IIS Manager.
+This parameter configures the Require SSL value on the Outlook Anywhere virtual directory. When you set this parameter to $true, Require SSL is disabled. When you set this parameter to $fase, Require SSL is enabled. However, it might take several minutes before the change is visible in IIS Manager.
 
 You need to use the value $true for this parameter if you don't require SSL connections for internal or external Outlook Anywhere clients.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-OutlookProtectionRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-OutlookProtectionRule.md
index 595590c4a5..e7bc6acefb 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-OutlookProtectionRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-OutlookProtectionRule.md
@@ -15,7 +15,7 @@ title: Set-OutlookProtectionRule
 ## SYNOPSIS
 **Note**: This cmdlet is no longer supported in the cloud-based service.
 
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-OutlookProtectionRule cmdlet to modify an existing Microsoft Outlook protection rule.
 
@@ -44,7 +44,7 @@ Outlook protection rules are used to automatically rights-protect email messages
 
 Not specifying any conditions results in an Outlook protection rule being applied to all messages.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-OutlookProvider.md b/exchange/exchange-ps/ExchangePowerShell/Set-OutlookProvider.md
index aca9ccddb2..aa50953b25 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-OutlookProvider.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-OutlookProvider.md
@@ -38,7 +38,7 @@ Set-OutlookProvider [-Identity] <OutlookProviderIdParameter>
 ## DESCRIPTION
 The Set-OutlookProvider cmdlet creates the global settings for the Autodiscover service. It sets the AutoDiscoverConfig object under the Global Settings object in Active Directory and sets the attributes specified in the parameters listed in the Parameters section.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -172,7 +172,7 @@ The RequiredClientVersions parameter specifies the minimum version of Microsoft
 
 MinimumVersion is the version of Outlook in the format xx.x.xxxx.xxxx. For example, to specify Outlook 2010 Service Pack 2 (SP2), use the value 14.0.7012.1000.
 
-ExpirationDate is the UTC date-time when connections by older versions of Outlook will be blocked. The UTC date-time is represented in the ISO 8601 date-time format: yyyy-MM-ddThh:mm:ss.fffZ, where yyyy = year, MM = month, dd = day, T indicates the beginning of the time component, hh = hour, mm = minute, ss = second, fff = fractions of a second and Z signifies Zulu, which is another way to denote UTC.
+ExpirationDate is the UTC date-time when connections by older versions of Outlook are blocked. The UTC date-time is represented in the ISO 8601 date-time format: yyyy-MM-ddThh:mm:ss.fffZ, where yyyy = year, MM = month, dd = day, T indicates the beginning of the time component, hh = hour, mm = minute, ss = second, fff = fractions of a second and Z signifies Zulu, which is another way to denote UTC.
 
 An example of a valid value for this parameter is `"14.0.7012.1000, 2020-01-01T12:00:00Z"`.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-OwaMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-OwaMailboxPolicy.md
index 4379af8950..fa861191a0 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-OwaMailboxPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-OwaMailboxPolicy.md
@@ -13,7 +13,7 @@ title: Set-OwaMailboxPolicy
 # Set-OwaMailboxPolicy
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-OwaMailboxPolicy cmdlet to configure existing Outlook on the web mailbox policies.
 
@@ -163,9 +163,9 @@ Set-OwaMailboxPolicy [-Identity] <MailboxPolicyIdParameter>
 ## DESCRIPTION
 In on-premises Exchange, the default Outlook on the web mailbox policy is named Default. In Exchange Online, the default Outlook on the web mailbox policy is named OwaMailboxPolicy-Default.
 
-Changes to Outlook on the web mailbox policies may take up to 60 minutes to take effect. In on-premises Exchange, you can force an update by restarting IIS (`Stop-Service WAS -Force` and `Start-Service W3SVC`).
+Changes to Outlook on the web mailbox policies might take up to 60 minutes to take effect. In on-premises Exchange, you can force an update by restarting IIS (`Stop-Service WAS -Force` and `Start-Service W3SVC`).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -247,7 +247,7 @@ Accept wildcard characters: False
 
 The ActionForUnknownFileAndMIMETypes parameter specifies how to handle file types that aren't specified in the Allow, Block, and Force Save lists for file types and MIME types. Valid values are:
 
-- Allow (This is the default value.)
+- Allow (This value is the default.)
 - ForceSave
 - Block
 
@@ -271,7 +271,7 @@ This parameter is available only in the cloud-based service.
 
 The AdditionalStorageProvidersAvailable parameter specifies whether to allow additional storage providers (for example, Box, Dropbox, Facebook, Google Drive, Egnyte, personal OneDrive) attachments in Outlook on the web. Valid values are:
 
-- $true: Additional storage providers are enabled in Outlook on the web. Users can connect their additional storage providers and share files over email. This is the default value.
+- $true: Additional storage providers are enabled in Outlook on the web. Users can connect their additional storage providers and share files over email. This value is the default.
 - $false: Additional storage providers are disabled in Outlook on the web. Users can't connect their additional storage providers or share files over email.
 
 ```yaml
@@ -292,7 +292,7 @@ Accept wildcard characters: False
 
 The ActiveSyncIntegrationEnabled parameter specifies whether to enable or disable Exchange ActiveSync settings in Outlook on the web. Valid values are:
 
-- $true: ActiveSync is available in Outlook on the web. This is the default value.
+- $true: ActiveSync is available in Outlook on the web. This value is the default.
 - $false: ActiveSync isn't available in Outlook on the web.
 
 ```yaml
@@ -313,7 +313,7 @@ Accept wildcard characters: False
 
 This parameter is available only in the cloud-based service.
 
-This parameter has been deprecated and is no longer used.
+This parameter is deprecated and no longer used.
 
 To enable or disable personal accounts in the new Outlook for Windows, use the PersonalAccountsEnabled parameter.
 
@@ -335,7 +335,7 @@ Accept wildcard characters: False
 
 The AllAddressListsEnabled parameter specifies which address lists are available in Outlook on the web. Valid values are:
 
-- $true: All address lists are visible in Outlook on the web. This is the default value.
+- $true: All address lists are visible in Outlook on the web. This value is the default.
 - $false: Only the global address list is visible in Outlook on the web.
 
 ```yaml
@@ -356,7 +356,7 @@ Accept wildcard characters: False
 
 The AllowCopyContactsToDeviceAddressBook parameter specifies whether users can copy the contents of their Contacts folder to a mobile device's native address book when using Outlook on the web for devices. Valid values are:
 
-- $true: Contacts can be copied to the device's address book in Outlook on the web for devices. This is the default value.
+- $true: Contacts can be copied to the device's address book in Outlook on the web for devices. This value is the default.
 - $false: Contacts can't be copied to the device's address book in Outlook on the web for devices.
 
 ```yaml
@@ -462,7 +462,7 @@ The AllowOfflineOn parameter specifies when Outlook Web App in offline mode is a
 
 - PrivateComputersOnly: Offline mode is available in private computer sessions. By default in Exchange 2013 or later and Exchange Online, all Outlook on the web sessions are considered to be on private computers. In Exchange 2013 or later, users can only specify public computer sessions if you've enabled the private/public selection on the sign in page (the LogonPagePublicPrivateSelectionEnabled parameter value is $true on the Set-OwaVirtualDirectory cmdlet).
 - NoComputers: Offline mode is disabled.
-- AllComputers: Offline mode is available for public and private computer sessions. This is the default value.
+- AllComputers: Offline mode is available for public and private computer sessions. This value is the default.
 
 When offline mode is available, users can turn offline mode on or off themselves in Outlook Web App. For more information, see [Use offline settings in Outlook on the web](https://support.microsoft.com/office/a34c9d9d-16ac-4020-b730-ffa7c7540ae7).
 
@@ -631,7 +631,7 @@ This parameter is functional only in on-premises Exchange.
 
 The CalendarEnabled parameter specifies whether to enable or disable the calendar in Outlook Web App. Valid values are:
 
-- $true: The Calendar is available in Outlook Web App. This is the default value.
+- $true: The Calendar is available in Outlook Web App. This value is the default.
 - $false: The Calendar isn't available in Outlook Web App.
 
 ```yaml
@@ -654,7 +654,7 @@ This parameter is functional only in on-premises Exchange.
 
 The ChangePasswordEnabled parameter specifies whether users can change their passwords from inside Outlook on the web. Valid values are:
 
-- $true: The Change password option is available in Outlook on the web. This is the default value in on-premises Exchange.
+- $true: The Change password option is available in Outlook on the web. This value is the default in on-premises Exchange.
 - $false: The Change password option isn't available in Outlook on the web.
 
 ```yaml
@@ -677,7 +677,7 @@ This parameter is available only in the cloud-based service.
 
 The ChangeSettingsAccountEnabled parameter specifies whether users can change the email account where app-wide settings (for example, theme and privacy settings) are associated in the new Outlook for Windows. Valid values are:
 
-- $true: Users can change their settings account in the new Outlook for Windows. This is the default value.
+- $true: Users can change their settings account in the new Outlook for Windows. This value is the default.
 - $false: Users can't change their settings account in the new Outlook for Windows.
 
 **Note**: The settings account is referred to as the primary account in the new Outlook for Windows setting at Settings \> Accounts \> Email accounts \> Manage.
@@ -700,7 +700,7 @@ Accept wildcard characters: False
 
 The ClassicAttachmentsEnabled parameter specifies whether users can attach local files as regular email attachments in Outlook on the web. Valid values are:
 
-- $true: Users can attach local files to email messages in Outlook on the web. This is the default value.
+- $true: Users can attach local files to email messages in Outlook on the web. This value is the default.
 - $false: Users can't attach local files to email messages in Outlook on the web.
 
 ```yaml
@@ -723,11 +723,11 @@ This parameter is available only in the cloud-based service.
 
 The ConditionalAccessPolicy parameter specifies the Outlook on the Web Policy for limited access. For this feature to work properly, you also need to configure a Conditional Access policy in the Microsoft Entra admin center.
 
-**Note**: When you enable a Conditional Access policy, users will no longer be able to access the light version of Outlook on the web. An error message will direct them to use the default premium experience.
+**Note**: When you enable a Conditional Access policy, users can no longer access the light version of Outlook on the web. An error message directs them to use the default premium experience.
 
 Valid values are:
 
-- Off: No conditional access policy is applied to Outlook on the web. This is the default value.
+- Off: No conditional access policy is applied to Outlook on the web. This value is the default.
 - ReadOnly: Users can't download attachments to their local computer, and can't enable Offline Mode on non-compliant computers. They can still view attachments in the browser. This doesn't apply to in-line images.
 - ReadOnlyPlusAttachmentsBlocked: All restrictions from ReadOnly apply, but users can't view attachments in the browser. This doesn't apply to in-line images.
 
@@ -772,7 +772,7 @@ This parameter is functional only in on-premises Exchange.
 
 The ContactsEnabled parameter specifies whether to enable or disable Contacts in Outlook Web App. Valid values are:
 
-- $true: Contacts are available in Outlook Web App. This is the default value.
+- $true: Contacts are available in Outlook Web App. This value is the default.
 - $false: Contacts aren't available in Outlook Web App.
 
 ```yaml
@@ -791,7 +791,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
 
-This parameter has been deprecated and is no longer used.
+This parameter is deprecated and no longer used.
 
 ```yaml
 Type: Int32
@@ -811,7 +811,7 @@ Accept wildcard characters: False
 
 The DefaultTheme parameter specifies the default theme that's used in Outlook on the web when the user hasn't selected a theme. The default value is blank ($null). For more information about the built-in themes that are available in Outlook on the web, see [Default Outlook on the web themes in Exchange](https://learn.microsoft.com/Exchange/clients/outlook-on-the-web/themes#default-outlook-on-the-web-themes-in-exchange-2016).
 
-Note that this parameter is a text string, and the value you specify isn't validated against the list of available themes.
+This parameter is a text string, and the value you specify isn't validated against the list of available themes.
 
 ```yaml
 Type: String
@@ -833,7 +833,7 @@ This parameter is functional only in on-premises Exchange.
 
 The DelegateAccessEnabled parameter specifies whether delegates can use Outlook on the web or Outlook Web App to open folders that they have delegate access to. Valid values are:
 
-- $true: Delegates can open the mailbox in Outlook on the web. This is the default value.
+- $true: Delegates can open the mailbox in Outlook on the web. This value is the default.
 - $false: Delegates can't open the mailbox in Outlook on the web.
 
 ```yaml
@@ -854,8 +854,8 @@ Accept wildcard characters: False
 
 The DirectFileAccessOnPrivateComputersEnabled parameter specifies the left-click options for attachments in Outlook on the web for private computer sessions. Valid values are:
 
-- $true: Open is available for attachments in Outlook on the web for private computer sessions. This is the default value.
-- $false: Open isn't available for attachments in Outlook on the web for private computer sessions. Note that Office and .pdf documents can still be previewed in Outlook on the web.
+- $true: Open is available for attachments in Outlook on the web for private computer sessions. This value is the default.
+- $false: Open isn't available for attachments in Outlook on the web for private computer sessions. Office and .pdf documents can still be previewed in Outlook on the web.
 
 By default in Exchange 2013 or later and Exchange Online, all Outlook on the web sessions are considered to be on private computers.
 
@@ -877,8 +877,8 @@ Accept wildcard characters: False
 
 The DirectFileAccessOnPublicComputersEnabled parameter specifies the left-click options for attachments in Outlook on the web for public computer sessions. Valid values are:
 
-- $true: Open is available for attachments in Outlook on the web for public computer sessions. This is the default value.
-- $false: Open isn't available for attachments in Outlook on the web for public computer sessions. Note that Office and .pdf documents can still be previewed in Outlook on the web.
+- $true: Open is available for attachments in Outlook on the web for public computer sessions. This value is the default.
+- $false: Open isn't available for attachments in Outlook on the web for public computer sessions. Office and .pdf documents can still be previewed in Outlook on the web.
 
 In Exchange 2013 or later, users can only specify public computer sessions if you've enabled the private/public selection on the sign in page (the LogonPagePublicPrivateSelectionEnabled parameter value is $true on the Set-OwaVirtualDirectory cmdlet).
 
@@ -927,7 +927,7 @@ Accept wildcard characters: False
 
 The DisplayPhotosEnabled parameter specifies whether users see sender photos in Outlook on the web. Valid values are:
 
-- $true: Users see sender photos in Outlook on the web. This is the default value.
+- $true: Users see sender photos in Outlook on the web. This value is the default.
 - $false: Users don't see sender photos in Outlook on the web.
 
 ```yaml
@@ -1010,7 +1010,7 @@ This parameter is functional only in on-premises Exchange.
 
 The ExplicitLogonEnabled parameter specifies whether to allow a user to open someone else's mailbox in Outlook on the web (provided that user has permissions to the mailbox). Valid values are:
 
-- $true: A user with the required permissions is able to open someone else's mailbox in Outlook on the web. This is the default value.
+- $true: A user with the required permissions is able to open someone else's mailbox in Outlook on the web. This value is the default.
 - $false: A user with the required permissions isn't able to open someone else's mailbox in Outlook on the web.
 
 ```yaml
@@ -1033,7 +1033,7 @@ This parameter is available only in the cloud-based service.
 
 The ExternalImageProxyEnabled parameter specifies whether to load all external images through the Outlook external image proxy. Valid values are:
 
-- $true: All external images are loaded through the Outlook external image proxy. This is the default value.
+- $true: All external images are loaded through the Outlook external image proxy. This value is the default.
 - $false: All external images are loaded through the web browser. This is potentially unsafe, as the images could have mixed content or malformed images that ask for user credentials.
 
 ```yaml
@@ -1076,7 +1076,7 @@ This cmdlet is available only in the cloud-based service.
 
 The FeedbackEnabled parameter specifies whether to enable or disable inline feedback surveys in Outlook on the web. Valid values are:
 
-- $true: Inline feedback surveys are enabled. This is the default value.
+- $true: Inline feedback surveys are enabled. This value is the default.
 - $false: Inline feedback surveys are disabled.
 
  Surveys allow users to provide feedback on specific features. For example, for the text predictions feature, the inline feedback "Are the above autocomplete suggestions helpful (yes/no)?" is shown. If a user chooses "no" they can provide specific feedback.
@@ -1100,7 +1100,7 @@ Accept wildcard characters: False
 The ForceSaveAttachmentFilteringEnabled parameter specifies whether files are filtered before they can be saved from Outlook on the web. Valid values are:
 
 - $true: The attachments specified by the ForceSaveFileTypes parameter are filtered before they can be saved from Outlook on the web.
-- $false: The attachments aren't filtered before they're saved. This is the default value.
+- $false: The attachments aren't filtered before they're saved. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -1183,7 +1183,7 @@ Accept wildcard characters: False
 The ForceWacViewingFirstOnPrivateComputers parameter specifies whether private computers must first preview an Office file as a web page in Office Online Server (formerly known as Office Web Apps Server and Web Access Companion Server) before opening the file in the local application. Valid values are:
 
 - $true: Private computers must first preview an Office file as a web page in Office Online Server before opening the file.
-- $false: Private computers aren't required to preview an Office file as a web page in Office Online Server before opening the file. This is the default value.
+- $false: Private computers aren't required to preview an Office file as a web page in Office Online Server before opening the file. This value is the default.
 
 By default in Exchange 2013 or later and Exchange Online, all Outlook on the web sessions are considered to be on private computers.
 
@@ -1206,7 +1206,7 @@ Accept wildcard characters: False
 The ForceWacViewingFirstOnPublicComputers parameter specifies whether public computers must first preview an Office file as a web page in Office Online Server before opening the file in the local application. Valid values are:
 
 - $true: Public computers must first preview an Office file as a web page in Office Online Server before opening the file.
-- $false: Public computers aren't required to preview an Office file as a web page in Office Online Server before opening the file. This is the default value.
+- $false: Public computers aren't required to preview an Office file as a web page in Office Online Server before opening the file. This value is the default.
 
 In Exchange 2013 or later, users can only specify public computer sessions if you've enabled the private/public selection on the sign in page (the LogonPagePublicPrivateSelectionEnabled parameter value is $true on the Set-OwaVirtualDirectory cmdlet).
 
@@ -1231,7 +1231,7 @@ This parameter is available only in Exchange Server 2010 or Exchange Server 2013
 The ForceWebReadyDocumentViewingFirstOnPrivateComputers parameter specifies whether private computers must first preview an Office file as a web page in WebReady Document Viewing before opening the file from Outlook Web App. Valid values are:
 
 - $true: Private computers must first preview an Office file as a web page in WebReady Document Viewing before opening the file.
-- $false: Private computers aren't required to preview an Office file as a web page in WebReady Document Viewing before opening the file. This is the default value.
+- $false: Private computers aren't required to preview an Office file as a web page in WebReady Document Viewing before opening the file. This value is the default.
 
 By default in Exchange 2013 or later and Exchange Online, all Outlook on the web sessions are considered to be on private computers.
 
@@ -1256,7 +1256,7 @@ This parameter is available only in Exchange Server 2010 or Exchange Server 2013
 The ForceWebReadyDocumentViewingFirstOnPublicComputers parameter specifies whether Public computers must first preview an Office file as a web page in WebReady Document Viewing before opening the file from Outlook Web App. Valid values are:
 
 - $true: Public computers must first preview an Office file as a web page in WebReady Document Viewing before opening the file.
-- $false: Public computers aren't required to preview an Office file as a web page in WebReady Document Viewing before opening the file. This is the default value.
+- $false: Public computers aren't required to preview an Office file as a web page in WebReady Document Viewing before opening the file. This value is the default.
 
 In Exchange 2013 or later, users can only specify public computer sessions if you've enabled the private/public selection on the sign in page (the LogonPagePublicPrivateSelectionEnabled parameter value is $true on the Set-OwaVirtualDirectory cmdlet).
 
@@ -1298,7 +1298,7 @@ Accept wildcard characters: False
 
 The GlobalAddressListEnabled parameter specifies whether the global address list is available in Outlook on the web. Valid values are:
 
-- $true: The global address list is visible in Outlook on the web. This is the default value.
+- $true: The global address list is visible in Outlook on the web. This value is the default.
 - $false: The global address list isn't visible in Outlook on the web.
 
 ```yaml
@@ -1341,7 +1341,7 @@ This parameter is functional only in the cloud-based service.
 
 The GroupCreationEnabled parameter specifies whether Microsoft 365 Group creation is available in Outlook and Outlook on the web. Valid values are:
 
-- $true: Users can create Microsoft 365 Groups in Outlook and Outlook on the web. This is the default value.
+- $true: Users can create Microsoft 365 Groups in Outlook and Outlook on the web. This value is the default.
 - $false: Users can't create Microsoft 365 Groups in Outlook and Outlook on the web.
 
 ```yaml
@@ -1365,7 +1365,7 @@ This parameter is available only in the cloud-based service.
 The HideClassicOutlookToggleOut parameter specifies whether to enable or disable hiding the toggle in new Outlook that allows users to switch back to classic Outlook. Valid values are:
 
 - $true: The toggle to switch back to classic Outlook is hidden in new Outlook for Windows.
-- $false: The toggle to switch back to classic Outlook isn't hidden in new Outlook for Windows. This is the default value.
+- $false: The toggle to switch back to classic Outlook isn't hidden in new Outlook for Windows. This value is the default.
 
 ```yaml
 Type: System.Boolean
@@ -1385,7 +1385,7 @@ Accept wildcard characters: False
 
 The InstantMessagingEnabled parameter specifies whether instant messaging is available in Outlook on the web. This does not affect chat capabilities provided by Skype for Business or Teams. Valid values are:
 
-- $true: Instant messaging is available in Outlook on the web. This is the default value.
+- $true: Instant messaging is available in Outlook on the web. This value is the default.
 - $false: Instant messaging isn't available in Outlook on the web.
 
 ```yaml
@@ -1406,8 +1406,8 @@ Accept wildcard characters: False
 
 The InstantMessagingType parameter specifies the type of instant messaging provider in Outlook on the web. Valid values are:
 
-- None: This is the default value in on-premises Exchange.
-- Ocs: Lync or Skype (formerly known as Office Communication Server). This is the default value in Exchange Online.
+- None: This value is the default in on-premises Exchange.
+- Ocs: Lync or Skype (formerly known as Office Communication Server). This value is the default in Exchange Online.
 
 ```yaml
 Type: InstantMessagingTypeOptions
@@ -1429,7 +1429,7 @@ This parameter is available only in the cloud-based service.
 
 The InterestingCalendarsEnabled parameter specifies whether interesting calendars are available in Outlook on the web. Valid values are:
 
-- $true: Interesting calendars are available in Outlook on thew web. This is the default value.
+- $true: Interesting calendars are available in Outlook on thew web. This value is the default.
 - $false: Interesting calendars aren't available in Outlook on the web.
 
 ```yaml
@@ -1470,7 +1470,7 @@ Accept wildcard characters: False
 
 The IRMEnabled parameter specifies whether Information Rights Management (IRM) features are available in Outlook on the web. Valid values are:
 
-- $true: IRM is available in Outlook on the web. This is the default value.
+- $true: IRM is available in Outlook on the web. This value is the default.
 - $false: IRM isn't available in Outlook on the web.
 
 ```yaml
@@ -1493,7 +1493,7 @@ The IsDefault switch specifies whether the Outlook on the web policy is the defa
 
 If another policy is currently set as the default, this switch replaces the old default policy with this policy.
 
-**Note**: In Exchange Online - and excluding resource mailboxes - this value will be superseded by the **OwaMailboxPolicy** parameter in each organization's [CASMailboxPlan](https://learn.microsoft.com/powershell/module/exchangepowershell/set-casmailboxplan). That value will instead be applied per each mailbox's SKU.
+**Note**: In Exchange Online - and excluding resource mailboxes - this value is superseded by the _OwaMailboxPolicy_ parameter on the [Set- CASMailboxPlan](https://learn.microsoft.com/powershell/module/exchangepowershell/set-casmailboxplan) cmdlet. That value is applied instead per each mailbox's license.
 
 ```yaml
 Type: SwitchParameter
@@ -1516,7 +1516,7 @@ This parameter is available only in the cloud-based service.
 The ItemsToOtherAccountsEnabled parameter specifies whether users can move or copy email messages between accounts. Valid values are:
 
 - $true: Users can move and copy messages to and from external accounts.
-- $false: Users can't move or copy messages to and from external accounts. This is the default value.
+- $false: Users can't move or copy messages to and from external accounts. This value is the default.
 
 **Note:** This policy doesn't affect moving or copying messages between Microsoft 365 Groups and shared mailboxes within the organization.
 
@@ -1538,7 +1538,7 @@ Accept wildcard characters: False
 
 The JournalEnabled parameter specifies whether the Journal folder is available in Outlook on the web. Valid values are:
 
-- $true: The Journal folder is visible in Outlook on the web. This is the default value.
+- $true: The Journal folder is visible in Outlook on the web. This value is the default.
 - $false: The Journal folder isn't visible in Outlook on the web.
 
 ```yaml
@@ -1561,7 +1561,7 @@ This parameter is available only in on-premises Exchange.
 
 The JunkEmailEnabled parameter specifies whether the Junk Email folder and junk email management are available in Outlook on the web. Valid values are:
 
-- $true: The Junk Email folder and junk email management are available in Outlook on the web. This is the default value.
+- $true: The Junk Email folder and junk email management are available in Outlook on the web. This value is the default.
 - $false: The Junk Email folder and junk email management aren't available in Outlook on the web.
 
 ```yaml
@@ -1605,7 +1605,7 @@ This parameter is available only in the cloud-based service.
 The LocalEventsEnabled parameter specifies whether local events calendars are available in Outlook on the web. Valid values are:
 
 - $true: Local events are available in Outlook on the web.
-- $false: Local events aren't available in Outlook on the web. This is the default value.
+- $false: Local events aren't available in Outlook on the web. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -1705,7 +1705,7 @@ Accept wildcard characters: False
 
 The NotesEnabled parameter specifies whether the Notes folder is available in Outlook on the web. Valid values are:
 
-- $true: The Notes folder is visible in Outlook on the web. This is the default value.
+- $true: The Notes folder is visible in Outlook on the web. This value is the default.
 - $false: The Notes folder isn't visible in Outlook on the web.
 
 ```yaml
@@ -1728,7 +1728,7 @@ This parameter is available only in the cloud-based service.
 
 The NpsSurveysEnabled parameter specifies whether to enable or disable the Net Promoter Score (NPS) survey in Outlook on the web. The survey allows users to rate Outlook on the web on a scale of 1 to 5, and to provide feedback and suggested improvements in free text. Valid values are:
 
-- $true: The NPS survey is available in Outlook on the web. This is the default value.
+- $true: The NPS survey is available in Outlook on the web. This value is the default.
 - $false: The NPS survey isn't available in Outlook on the web.
 
 ```yaml
@@ -1751,7 +1751,7 @@ This parameter is available only in the cloud-based service.
 
 The OfflineEnabledWeb parameter specifies whether offline capabilities are available in Outlook on the web, including saving items to the local device (view items without an internet connection). Valid values are:
 
-- $true: Users can manage offline capabilities in Outlook on the web. This is the default value.
+- $true: Users can manage offline capabilities in Outlook on the web. This value is the default.
 - $false: Users can't manage offline capabilities in Outlook on the web. No items are saved to the user's device. Previously save items are deleted.
 
 When offline capabilities are available, users can turn offline capabilities on or off themselves in Outlook on the web at Settings \> General \> Offline.
@@ -1776,7 +1776,7 @@ This parameter is available only in the cloud-based service.
 
 The OfflineEnabledWin parameter specifies whether offline capabilities are available in the new Outlook for Windows, including saving items to the local device (view items without an internet connection). Valid values are:
 
-- $true: Users can manage offline capabilities in the new Outlook for Windows. This is the default value.
+- $true: Users can manage offline capabilities in the new Outlook for Windows. This value is the default.
 - $false: Users can't manage offline capabilities in the new Outlook for Windows. No items are saved to the user's device. Previously save items are deleted.
 
 When offline capabilities are available, users can turn offline capabilities on or off themselves in the New Outlook for Windows at Settings \> General \> Offline. By default, offline capabilities are turned on.
@@ -1797,7 +1797,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
 
-This parameter has been deprecated and is no longer used.
+This parameter is deprecated and no longer used.
 
 To enable or disable personal OneDrive in Outlook on the web, use the AdditionalStorageProvidersAvailable parameter.
 
@@ -1821,7 +1821,7 @@ This parameter is available only in the cloud-based service.
 
 The OneWinNativeOutlookEnabled parameter controls the availability of the new Outlook for Windows App. Valid values are:
 
-- $true: The New Outlook for Windows App is available. This is the default value.
+- $true: The New Outlook for Windows App is available. This value is the default.
 - $false: The new Outlook for Windows App isn't available.
 
 ```yaml
@@ -1841,8 +1841,8 @@ Accept wildcard characters: False
 
 The OnSendAddinsEnabled parameter specifies whether a mail item can be edited while an on-send add-in is processing it in Outlook on the web or the new Outlook on Windows. Valid values are:
 
-- $true: A user can't edit a mail item while an on-send add-in is processing the item.
-- $false: A user can edit a mail item while an on-send add-in is processing the item. This is the default value.
+- $true: On send add-ins are enabled.
+- $false: On send add-ins are disabled. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -1880,7 +1880,7 @@ Accept wildcard characters: False
 
 The OutboundCharset parameter specifies the character set that's used for outgoing messages in Outlook on the web. Valid values are:
 
-- AutoDetect: Examine the first 2 kilobytes (KB) of text in the message to determine the character set that's used in outgoing messages. This is the default value.
+- AutoDetect: Examine the first 2 kilobytes (KB) of text in the message to determine the character set that's used in outgoing messages. This value is the default.
 - AlwaysUTF8: Always use UTF-8 encoded Unicode characters in outgoing messages, regardless of the detected text in the message, or the user's language choice in Outlook on the web. Use this value if replies to UTF-8 encoded messages aren't being encoded in UTF-8.
 - UserLanguageChoice: Use the user's language choice in Outlook on the web to encode outgoing messages.
 
@@ -1904,7 +1904,7 @@ This parameter is available only in the cloud-based service.
 
 The OutlookBetaToggleEnabled parameter specifies whether to enable or disable the Outlook on the web Preview toggle. The Preview toggle allows users to try the new Outlook on the web experience. Valid values are:
 
-- $true: The Outlook on the web Preview toggle is enabled. Users can easily switch back and forth between both experiences. This is the default value.
+- $true: The Outlook on the web Preview toggle is enabled. Users can easily switch back and forth between both experiences. This value is the default.
 - $false: Outlook on the web Preview is disabled.
 
 ```yaml
@@ -1930,7 +1930,7 @@ The OutlookNewslettersAccessLevelAccess parameter specifies the access level in
 - NoAccess: No access to Outlook Newsletters in the New Outlook for Windows or Outlook on the web. Users can still read email messages sent or forwarded to them.
 - ReadOnly: Read newsletters and browse pages in Outlook Newsletters.
 - ReadWrite: Full authoring permissions to create pages and newsletters in Outlook Newsletters.
-- Undefined: This is the default value. Currently, this value is equivalent to NoAccess.
+- Undefined: This value is the default. Currently, this value is equivalent to NoAccess.
 
 ```yaml
 Type: OutlookNewslettersAccessLevel
@@ -1982,7 +1982,7 @@ The OutlookNewslettersReactions parameter specifies whether reactions are enable
 - DefaultOff: The controls are turned off.
 - DefaultOn: The controls are turned on.
 - Disabled: The controls are disabled for users.
-- Undefined: This is the default value.
+- Undefined: This value is the default.
 
 ```yaml
 Type: OutlookNewslettersFeatureState
@@ -2007,7 +2007,7 @@ The OutlookNewslettersShowMore parameter specifies whether recommendations to ot
 - DefaultOff: Recommendations are turned off.
 - DefaultOn: Recommendations are turned on.
 - Disabled: Recommendations are disabled for users.
-- Undefined: This is the default value.
+- Undefined: This value is the default.
 
 Authors can disable these recommendations for each individual newsletter edition, or admins can use this parameter to globally disable these recommendations.
 
@@ -2029,7 +2029,7 @@ Accept wildcard characters: False
 
 The OWALightEnabled parameter controls the availability of the light version of Outlook on the web. Valid values are:
 
-- $true: The light version of Outlook on the web is available. This is the default value.
+- $true: The light version of Outlook on the web is available. This value is the default.
 - $false: The light version of Outlook on the web isn't available. This setting prevents access to Outlook on the web for unsupported browsers that can only use the light version of Outlook on the web.
 
 ```yaml
@@ -2052,7 +2052,7 @@ This parameter is available only in Exchange Server 2010.
 
 The OWAMiniEnabled parameter controls the availability of the mini version of Outlook Web App. Valid values are:
 
-- $true: The mini version of Outlook Web App is available. This is the default value.
+- $true: The mini version of Outlook Web App is available. This value is the default.
 - $false: The mini version of Outlook Web App isn't available.
 
 ```yaml
@@ -2075,7 +2075,7 @@ This parameter is available only in the cloud-based service.
 
 The PersonalAccountCalendarsEnabled parameter specifies whether to allow users to connect to their personal Outlook.com or Google Calendar in Outlook on the web. Valid values are:
 
-- $true: Users can connect to their Outlook.com or Google Calendar to see those events in their Outlook on the web calendar. This is the default value.
+- $true: Users can connect to their Outlook.com or Google Calendar to see those events in their Outlook on the web calendar. This value is the default.
 - $false: Users can't connect to their Outlook.com or Google Calendar in Outlook on the web.
 
 ```yaml
@@ -2098,7 +2098,7 @@ This parameter is available only in the cloud-based service.
 
 The PersonalAccountsEnabled parameter specifies whether to allow users to add their personal accounts (for example, Outlook.com, Gmail, or Yahoo!) in the new Outlook for Windows. Valid values are:
 
-- $true: Users can add their personal accounts in the new Outlook for Windows. This is the default value.
+- $true: Users can add their personal accounts in the new Outlook for Windows. This value is the default.
 - $false: Users can't add their personal accounts in the new Outlook for Windows.
 
 ```yaml
@@ -2139,7 +2139,7 @@ This parameter is available only in the cloud-based service.
 
 The PlacesEnabled parameter specifies whether to enable or disable Places in Outlook on the web. Places lets users search, share, and map location details by using Bing. Valid values are:
 
-- $true: Places is enabled. This is the default value.
+- $true: Places is enabled. This value is the default.
 - $false: Places is disabled.
 
 ```yaml
@@ -2160,7 +2160,7 @@ Accept wildcard characters: False
 
 The PremiumClientEnabled parameter controls the availability of the full version of Outlook Web App. Valid values are:
 
-- $true: The full version of Outlook Web App is available for supported browsers. This is the default value.
+- $true: The full version of Outlook Web App is available for supported browsers. This value is the default.
 - $false: The full version of Outlook Web App isn't available.
 
 ```yaml
@@ -2183,7 +2183,7 @@ This parameter is available only in the cloud-based service.
 
 The PrintWithoutDownloadEnabled specifies whether to allow printing of supported files without downloading the attachment in Outlook on the web. Valid values are:
 
-- $true: Supported files can be printed without being downloaded in Outlook on the web. This is the default value.
+- $true: Supported files can be printed without being downloaded in Outlook on the web. This value is the default.
 - $false: Supported files must be downloaded before they can be printed in Outlook on the web.
 
 ```yaml
@@ -2209,7 +2209,7 @@ This parameter is available only in the cloud-based service.
 The ProjectMocaEnabled parameter enables or disables access to Project Moca in Outlook on the web. Valid values are:
 
 - $true: Access to Project Moca is enabled in Outlook on the web.
-- $false: Access to Project Moca is disabled in Outlook on the web. This is the default value.
+- $false: Access to Project Moca is disabled in Outlook on the web. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -2231,7 +2231,7 @@ This parameter is functional only in Exchange Server 2010.
 
 The PublicFoldersEnabled parameter specifies whether a user can browse or read items in public folders in Outlook Web App. Valid values are:
 
-- $true: Public folders are available in Outlook Web App. This is the default value.
+- $true: Public folders are available in Outlook Web App. This value is the default.
 - $false: Public folders aren't available in Outlook Web App.
 
 ```yaml
@@ -2254,7 +2254,7 @@ This parameter is functional only in Exchange Server 2010.
 
 The RecoverDeletedItemsEnabled parameter specifies whether a user can use Outlook Web App to view, recover, or delete permanently items that have been deleted from the Deleted Items folder. Valid values are:
 
-- $true: Users can view, recover, or permanently delete items in Outlook Web App. This is the default value.
+- $true: Users can view, recover, or permanently delete items in Outlook Web App. This value is the default.
 - $false: Users can't view, recover, or permanently delete items in Outlook Web App. Items deleted from the Deleted Items folder in Outlook Web App are still retained.
 
 ```yaml
@@ -2275,7 +2275,7 @@ Accept wildcard characters: False
 
 The ReferenceAttachmentsEnabled parameter specifies whether users can attach files from the cloud as linked attachments in Outlook on the web. Valid values are:
 
-- $true: Users can attach files that are stored in the cloud as linked attachments. If the file hasn't been uploaded to the cloud yet, the users can attach and upload the file in the same step. This is the default value.
+- $true: Users can attach files that are stored in the cloud as linked attachments. If the file hasn't been uploaded to the cloud yet, the users can attach and upload the file in the same step. This value is the default.
 - $false: Users can't share files in the cloud as linked attachments. They need to download a local copy of the file before attaching the file to the email message.
 
 ```yaml
@@ -2296,7 +2296,7 @@ Accept wildcard characters: False
 
 The RemindersAndNotificationsEnabled parameter specifies whether notifications and reminders are enabled in Outlook on the web. Valid values are:
 
-- $true: Notifications and reminders are enabled in Outlook on the web. This is the default value.
+- $true: Notifications and reminders are enabled in Outlook on the web. This value is the default.
 - $false: Notifications and reminders are disabled in Outlook on the web.
 
 This parameter doesn't apply to the light version of Outlook Web App.
@@ -2321,7 +2321,7 @@ Accept wildcard characters: False
 
 The ReportJunkEmailEnabled parameter specifies whether users can report messages as junk or not junk to Microsoft in Outlook on the web. Valid values are:
 
-- $true: This is the default value. Selecting a message in the Junk Email folder and clicking **Not junk** \> **Not junk** moves the message back into the Inbox and gives users the option to report the message to Microsoft. Selecting a message in any other email folder and clicking **Junk** \> **Junk folder** moves the message to the Junk Email folder and gives users the option to report the message to Microsoft. Selecting a message and clicking **Not junk** \> **Phishing** (in the Junk Email folder) and **Junk** \> **Phishing** (everywhere else) are available to report phishing messages to Microsoft.
+- $true: This value is the default. Selecting a message in the Junk Email folder and clicking **Not junk** \> **Not junk** moves the message back into the Inbox and gives users the option to report the message to Microsoft. Selecting a message in any other email folder and clicking **Junk** \> **Junk folder** moves the message to the Junk Email folder and gives users the option to report the message to Microsoft. Selecting a message and clicking **Not junk** \> **Phishing** (in the Junk Email folder) and **Junk** \> **Phishing** (everywhere else) are available to report phishing messages to Microsoft.
 - $false: Selecting a message in the Junk Email folder and clicking **Not junk** \> **Not junk** moves the message back into the Inbox with no option to report the message to Microsoft. Selecting a message in any other email folder and clicking **Junk** \> **Junk** moves the message to the Junk Email folder with no option to report the message to Microsoft. Selecting a message and clicking **Not junk** \> **Phishing** (in the Junk Email folder) and **Junk** \> **Phishing** (everywhere else) are available to report phishing messages to Microsoft.
 
 This parameter is meaningful only when the JunkEmailEnabled parameter is set to $true.
@@ -2344,7 +2344,7 @@ Accept wildcard characters: False
 
 The RulesEnabled parameter specifies whether a user can view, create, or modify server-side rules in Outlook on the web. Valid values are:
 
-- $true: Users can view, create, or modify server-side rules in Outlook on the web. This is the default value.
+- $true: Users can view, create, or modify server-side rules in Outlook on the web. This value is the default.
 - $false: Users can't view, create, or modify server-side rules in Outlook on the web.
 
 ```yaml
@@ -2365,7 +2365,7 @@ Accept wildcard characters: False
 
 The SatisfactionEnabled parameter specifies whether to enable or disable the satisfaction survey. Valid values are:
 
-- $true: The satisfaction survey is enabled. This is the default value.
+- $true: The satisfaction survey is enabled. This value is the default.
 - $false: The satisfaction survey is disabled.
 
 ```yaml
@@ -2386,7 +2386,7 @@ Accept wildcard characters: False
 
 The SaveAttachmentsToCloudEnabled parameter specifies whether users can save regular email attachments to the cloud. Valid values are:
 
-- $true: Users can save regular email attachments to the cloud. This is the default value.
+- $true: Users can save regular email attachments to the cloud. This value is the default.
 - $false: Users can only save regular email attachments locally.
 
 ```yaml
@@ -2407,7 +2407,7 @@ Accept wildcard characters: False
 
 The SearchFoldersEnabled parameter specifies whether Search Folders are available in Outlook on the web. Valid values are:
 
-- $true: Search Folders are visible in Outlook on the Web. This is the default value.
+- $true: Search Folders are visible in Outlook on the Web. This value is the default.
 - $false: Search Folders aren't visible in Outlook on the Web.
 
 ```yaml
@@ -2428,7 +2428,7 @@ Accept wildcard characters: False
 
 The SetPhotoEnabled parameter specifies whether users can add, change, and remove their sender photo in Outlook on the web. Valid values are:
 
-- $true: Users can manage their photos in Outlook on the web. This is the default value.
+- $true: Users can manage their photos in Outlook on the web. This value is the default.
 - $false: Users can't manage their user photo in Outlook on the web.
 
 **Note**: To control whether users can update photos for Exchange Online, see [Configure User Administrator support for profile photo updates](https://learn.microsoft.com/graph/profilephoto-configure-settings#configure-user-administrator-support-for-profile-photo-updates).
@@ -2449,7 +2449,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
 
-The SetPhotoURL parameter controls where users go to select their photo. Note that you can't specify a URL that contains one or more picture files, as there is no mechanism to copy a URL photo to the properties of the users' Exchange Online mailboxes.
+The SetPhotoURL parameter controls where users go to select their photo. You can't specify a URL that contains one or more picture files, as there's no mechanism to copy a URL photo to the properties of Exchange Online mailboxes.
 
 ```yaml
 Type: String
@@ -2489,7 +2489,7 @@ Accept wildcard characters: False
 
 The SignaturesEnabled parameter specifies whether to enable or disable the use of signatures in Outlook on the web. Valid values are:
 
-- $true: Signatures are available in Outlook on the web. This is the default value.
+- $true: Signatures are available in Outlook on the web. This value is the default.
 - $false: Signatures aren't available in Outlook on the web.
 
 ```yaml
@@ -2512,7 +2512,7 @@ This parameter is functional only in Exchange Server 2010.
 
 The SilverlightEnabled parameter specifies whether a user can use Microsoft Silverlight features in Outlook Web App. Valid values are:
 
-- $true: Silverlight features are available in Outlook Web App. This is the default value.
+- $true: Silverlight features are available in Outlook Web App. This value is the default.
 - $false: Silverlight features aren't available in Outlook Web App.
 
 ```yaml
@@ -2535,7 +2535,7 @@ This parameter is functional only in the cloud-based service.
 
 The SkipCreateUnifiedGroupCustomSharepointClassification parameter specifies whether to skip a custom SharePoint page during the creation of Microsoft 365 Groups in Outlook on the web. Valid values are:
 
-- $true: The custom SharePoint page is skipped when a user creates a Microsoft 365 Group in Outlook on the web. This is the default value.
+- $true: The custom SharePoint page is skipped when a user creates a Microsoft 365 Group in Outlook on the web. This value is the default.
 - $false: The custom SharePoint page is shown when a user creates a Microsoft 365 Group in Outlook on the web.
 
 ```yaml
@@ -2558,7 +2558,7 @@ This parameter is functional only in Exchange Server 2010.
 
 The SMimeEnabled parameter specifies whether users can download the S/MIME control for Outlook Web App and use it to read and compose signed and encrypted messages. Valid values are:
 
-- $true: Users can read and compose S/MIME signed and encrypted messages in Outlook Web App. This is the default value.
+- $true: Users can read and compose S/MIME signed and encrypted messages in Outlook Web App. This value is the default.
 - $false: Users can't read or compose messages in Outlook Web App that are opaque-signed or encrypted by using S/MIME. Messages that are clear-signed can be read but not composed, and their signatures aren't validated.
 
 **Note**: In Exchange 2013 or later, use the Get-SmimeConfig and Set-SmimeConfig cmdlets to configure the S/MIME settings in Outlook on the web. For more information, see [S/MIME for message signing and encryption](https://learn.microsoft.com/Exchange/policy-and-compliance/smime).
@@ -2603,7 +2603,7 @@ This parameter is functional only in Exchange Server 2010.
 
 The SpellCheckerEnabled parameter specifies whether to enable or disable the built-in Outlook Web App spell checker in the full version of Outlook Web App. Valid values are:
 
-- $true: Spell checking is available in Outlook Web App. This is the default value.
+- $true: Spell checking is available in Outlook Web App. This value is the default.
 - $false: Spell checking isn't available in Outlook Web App.
 
 This parameter doesn't apply to the light version of Outlook Web App.
@@ -2628,7 +2628,7 @@ This parameter is functional only in on-premises Exchange.
 
 The TasksEnabled parameter specifies whether Tasks folder is available in Outlook Web App. Valid values are:
 
-- $true: The Tasks folder is available in Outlook Web App. This is the default value.
+- $true: The Tasks folder is available in Outlook Web App. This value is the default.
 - $false: The Tasks folder isn't available in Outlook Web App.
 
 This parameter doesn't apply to the light version of Outlook Web App.
@@ -2653,7 +2653,7 @@ This parameter is available only in the cloud-based service.
 
 The TeamSnapCalendarsEnabled parameter specifies whether to allow users to connect to their personal TeamSnap calendars in Outlook on the web. Valid values are:
 
-- $true: Users can connect to their TeamSnap calendars to see those events in their Outlook on the web calendar. This is the default value.
+- $true: Users can connect to their TeamSnap calendars to see those events in their Outlook on the web calendar. This value is the default.
 - $false: Users can't connect to their TeamSnap calendars in Outlook on the web.
 
 ```yaml
@@ -2674,7 +2674,7 @@ Accept wildcard characters: False
 
 The TextMessagingEnabled parameter specifies whether users can send and receive text messages in Outlook on the web. Valid values are:
 
-- $true: Text messaging is available in Outlook on the web. This is the default value.
+- $true: Text messaging is available in Outlook on the web. This value is the default.
 - $false: Text messaging isn't available in Outlook on the web.
 
 This parameter doesn't apply to the light version of Outlook on the web.
@@ -2697,7 +2697,7 @@ Accept wildcard characters: False
 
 The ThemeSelectionEnabled parameter specifies whether users can change the theme in Outlook on the web. Valid values are:
 
-- $true: Users can specify the theme in Outlook on the web. This is the default value.
+- $true: Users can specify the theme in Outlook on the web. This value is the default.
 - $false: Users can't specify or change the theme in Outlook on the web.
 
 ```yaml
@@ -2738,10 +2738,10 @@ Accept wildcard characters: False
 
 The UMIntegrationEnabled parameter specifies whether Unified Messaging (UM) integration is enabled in Outlook on the web. Valid values are:
 
-- $true: UM integration is enabled in Outlook on the web. This is the default value.
+- $true: UM integration is enabled in Outlook on the web. This value is the default.
 - $false: UM integration is disabled in Outlook on the web.
 
-This setting applies only if Unified Messaging has been enabled for a user (for example, bu using the Enable-UMMailbox cmdlet).
+This setting applies only if Unified Messaging is enabled for a user (for example, bu using the Enable-UMMailbox cmdlet).
 
 This parameter doesn't apply to the light version of Outlook on the web.
 
@@ -2763,7 +2763,7 @@ Accept wildcard characters: False
 
 This parameter is available only in on-premises Exchange.
 
-This parameter has been deprecated and is no longer used.
+This parameter is deprecated and no longer used.
 
 ```yaml
 Type: Boolean
@@ -2783,7 +2783,7 @@ Accept wildcard characters: False
 
 This parameter is available only in on-premises Exchange.
 
-This parameter has been deprecated and is no longer used.
+This parameter is deprecated and no longer used.
 
 ```yaml
 Type: Boolean
@@ -2804,7 +2804,7 @@ Accept wildcard characters: False
 The UseGB18030 parameter specifies whether to use the GB18030 character set instead of GB2312 in Outlook on the web. Valid values are:
 
 - $true: GB18030 is used wherever GB2312 would have been used in Outlook on the web.
-- $false: GB2312 isn't replaced by GB18030 in Outlook on the web. This is the default value.
+- $false: GB2312 isn't replaced by GB18030 in Outlook on the web. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -2825,7 +2825,7 @@ Accept wildcard characters: False
 The UseISO885915 parameter specifies whether to use the character set ISO8859-15 instead of ISO8859-1 in Outlook on the web. Valid values are:
 
 - $true: ISO8859-15 is used wherever ISO8859-1 would have been used in Outlook on the web.
-- $false: ISO8859-1 isn't replaced by GB18030 in Outlook on the web. This is the default value.
+- $false: ISO8859-1 isn't replaced by GB18030 in Outlook on the web. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -2847,7 +2847,7 @@ This parameter is functional only in the cloud-based service.
 
 The UserVoiceEnabled parameter specifies whether to enable or disable Outlook UserVoice in Outlook on the web. Outlook UserVoice is a customer feedback area that's available in Microsoft 365. Valid values are:
 
-- $true: Outlook UserVoice is enabled. This is the default value.
+- $true: Outlook UserVoice is enabled. This value is the default.
 - $false: Outlook UserVoice is disabled.
 
 ```yaml
@@ -2868,7 +2868,7 @@ Accept wildcard characters: False
 
 The WacEditingEnabled parameter specifies whether to enable or disable editing documents in Outlook on the web by using Office Online Server (formerly known as Office Web Apps Server and Web Access Companion Server). Valid values are:
 
-- $true: Users can edit supported documents in Outlook on the web. This is the default value.
+- $true: Users can edit supported documents in Outlook on the web. This value is the default.
 - $false: Users can't edit supported documents in Outlook on the web.
 
 ```yaml
@@ -2889,7 +2889,7 @@ Accept wildcard characters: False
 
 The WacExternalServicesEnabled parameter specifies whether to enable or disable external services when viewing documents in Outlook on the web (for example, machine translation) by using Office Online Server. Valid values are:
 
-- $true: External services are enabled when viewing supported documents in Outlook on the web. This is the default value.
+- $true: External services are enabled when viewing supported documents in Outlook on the web. This value is the default.
 - $false: External services are disabled when viewing supported documents in Outlook on the web.
 
 ```yaml
@@ -2911,7 +2911,7 @@ Accept wildcard characters: False
 The WacOMEXEnabled parameter specifies whether to enable or disable apps for Outlook in Outlook on the web in Office Online Server. Valid values are:
 
 - $true: apps for Outlook are enabled in Outlook on the web.
-- $false: apps for Outlook are disabled in Outlook on the web. This is the default value.
+- $false: apps for Outlook are disabled in Outlook on the web. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -2931,7 +2931,7 @@ Accept wildcard characters: False
 
 The WacViewingOnPrivateComputersEnabled parameter specifies whether to enable or disable web viewing of supported Office documents private computer sessions in Office Online Server (formerly known as Office Web Apps Server and Web Access Companion Server). By default, all Outlook on the web sessions are considered to be on private computers. Valid values are:
 
-- $true: In private computer sessions, users can view supported Office documents in the web browser. This is the default value.
+- $true: In private computer sessions, users can view supported Office documents in the web browser. This value is the default.
 - $false: In private computer sessions, users can't view supported Office documents in the web browser. Users can still open the file in a supported application or save the file locally.
 
 By default in Exchange 2013 or later and Exchange Online, all Outlook on the web sessions are considered to be on private computers.
@@ -2954,7 +2954,7 @@ Accept wildcard characters: False
 
 The WacViewingOnPublicComputersEnabled parameter specifies whether to enable or disable web viewing of supported Office documents in public computer sessions in Office Online Server. Valid values are:
 
-- $true: In public computer sessions, users can view supported Office documents in the web browser. This is the default value.
+- $true: In public computer sessions, users can view supported Office documents in the web browser. This value is the default.
 - $false: In public computer sessions, users can't view supported Office documents in the web browser. Users can still open the file in a supported application or save the file locally.
 
 In Exchange 2013 or later, users can only specify public computer sessions if you've enabled the private/public selection on the sign in page (the LogonPagePublicPrivateSelectionEnabled parameter value is $true on the Set-OwaVirtualDirectory cmdlet).
@@ -2979,7 +2979,7 @@ This parameter is available only in the cloud-based service.
 
 The WeatherEnabled parameter specifies whether to enable or disable weather information in the calendar in Outlook on the web. Valid values are:
 
-- $true: Weather is enabled. This is the default value.
+- $true: Weather is enabled. This value is the default.
 - $false: Weather is disabled.
 
 ```yaml
@@ -3001,7 +3001,7 @@ Accept wildcard characters: False
 The WebPartsFrameOptionsType parameter specifies what sources can access web parts in IFRAME or FRAME elements in Outlook on the web. Valid values are:
 
 - None: There are no restrictions on displaying Outlook on the web content in a frame.
-- SameOrigin: This is the default value and the recommended value. Display Outlook on the web content only in a frame that has the same origin as the content.
+- SameOrigin: This value is the default and the recommended value. Display Outlook on the web content only in a frame that has the same origin as the content.
 - Deny: Blocks display of Outlook on the web content in a frame, regardless of the origin of the site attempting to access it.
 
 ```yaml
@@ -3024,7 +3024,7 @@ This parameter is available only in Exchange Server 2010 and Exchange Server 201
 
 The WebReadyDocumentViewingForAllSupportedTypes parameter specifies whether to enable WebReady Document Viewing for all supported file and MIME types. Valid values are:
 
-- $true: All supported attachment types are available for WebReady Document Viewing. This is the default value.
+- $true: All supported attachment types are available for WebReady Document Viewing. This value is the default.
 - $false: Only the attachment types that are specified by the WebReadyFileTypes and WebReadyMimeTypes parameters are available for WebReady Document Viewing (you can remove values from the lists).
 
 ```yaml
@@ -3047,7 +3047,7 @@ This parameter is available only in Exchange Server 2010 and Exchange Server 201
 
 The WebReadyDocumentViewingOnPrivateComputersEnabled parameter specifies whether WebReady Document Viewing is available in private computer sessions. Valid values are:
 
-- $true: WebReady Document Viewing is available in private computer sessions. This is the default value.
+- $true: WebReady Document Viewing is available in private computer sessions. This value is the default.
 - $false: WebReady Document Viewing isn't available in private computer sessions.
 
 By default in Exchange 2013, all Outlook on the web sessions are considered to be on private computers.
@@ -3072,7 +3072,7 @@ This parameter is available only in Exchange Server 2010 and Exchange Server 201
 
 The WebReadyDocumentViewingOnPublicComputersEnabled parameter specifies whether WebReady Document Viewing is in public computer sessions. Valid values are:
 
-- $true: WebReady Document Viewing is available for public computer sessions. This is the default value.
+- $true: WebReady Document Viewing is available for public computer sessions. This value is the default.
 - $false: WebReady Document Viewing isn't available for public computer sessions.
 
 In Exchange 2013 or later, users can only specify public computer sessions if you've enabled the private/public selection on the sign in page (the LogonPagePublicPrivateSelectionEnabled parameter value is $true on the Set-OwaVirtualDirectory cmdlet).
@@ -3225,10 +3225,9 @@ Accept wildcard characters: False
 ```
 
 ### -WSSAccessOnPrivateComputersEnabled
-
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
 
-This parameter has been deprecated and is no longer used.
+This parameter is deprecated and no longer used.
 
 ```yaml
 Type: Boolean
@@ -3246,7 +3245,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
 
-This parameter has been deprecated and is no longer used.
+This parameter is deprecated and no longer used.
 
 ```yaml
 Type: Boolean
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-OwaVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Set-OwaVirtualDirectory.md
index bb19fab87e..f60879da83 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-OwaVirtualDirectory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-OwaVirtualDirectory.md
@@ -156,13 +156,13 @@ Before you run the Set-OwaVirtualDirectory cmdlet, consider the following items:
 
 - You must have Write access to virtual directory objects in Active Directory. If you don't have the necessary permissions and you try to run the Set-OwaVirtualDirectory cmdlet on the Active Directory virtual directory object, the cmdlet fails.
 - You must have Write access to virtual directory objects in the metabase for some properties, such as Authentication and GZip. If you don't have the necessary permissions to run the Set-OwaVirtualDirectory cmdlet on a metabase virtual directory object or on a parameter that writes to the metabase, the cmdlet fails.
-- Verify that the data source can be read. Depending on the properties that you want to set on an Outlook on the web virtual directory, you may want to run the cmdlet in a test environment on the Outlook on the web virtual directory object in Active Directory, the metabase, or both.
+- Verify that the data source can be read. Depending on the properties that you want to set on an Outlook on the web virtual directory, you might want to run the cmdlet in a test environment on the Outlook on the web virtual directory object in Active Directory, the metabase, or both.
 - You can run the Set-OwaVirtualDirectory cmdlet on any server that has the Exchange Server administration tools installed.
 - Several parameters for the Set-OwaVirtualDirectory cmdlet can contain more than one value. These are known as multivalued properties. Make sure that you modify multivalued properties correctly. For information, see [Modifying multivalued properties](https://learn.microsoft.com/exchange/modifying-multivalued-properties-exchange-2013-help).
 - Many of the Outlook on the web virtual directory settings require you to restart IIS (Stop-Service WAS -Force and Start-Service W3SVC) before the change takes effect. For example, when you enable or disable forms-based authentication, or when you enable or disable the Private computer option on the sign-in page.
 - To switch from forms-based authentication to Basic authentication, you must first disable forms-based authentication, and then as a separate task, enable Basic authentication. You can't disable forms-based authentication and enable Basic authentication in a single task.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -212,7 +212,7 @@ Accept wildcard characters: False
 
 The ActionForUnknownFileAndMIMETypes parameter specifies how to handle file types that aren't specified in the Allow, Block, and Force Save lists for file types and MIME types. Valid values are:
 
-- Allow (This is the default value.)
+- Allow (This value is the default.)
 - ForceSave
 - Block
 
@@ -234,7 +234,7 @@ Accept wildcard characters: False
 
 The ActiveSyncIntegrationEnabled parameter specifies whether to enable or disable Exchange ActiveSync settings in Outlook on the web. Valid values are:
 
-- $true: ActiveSync is available in Outlook on the web. This is the default value.
+- $true: ActiveSync is available in Outlook on the web. This value is the default.
 - $false: ActiveSync isn't available in Outlook on the web
 
 ```yaml
@@ -256,7 +256,7 @@ Accept wildcard characters: False
 The AdfsAuthentication parameter enables or disables Active Directory Federation Services (ADFS) authentication on the Outlook on the web virtual directory. Valid values are:
 
 - $true: ADFS authentication is enabled. You need to set the AdfsAuthentication parameter on Set-EcpVirtualDirectory to $true before you can use this value.
-- $false: ADFS authentication is disabled. This is the default value. You need to set the AdfsAuthentication parameter on Set-EcpVirtualDirectory to $false before you can use this value.
+- $false: ADFS authentication is disabled. This value is the default. You need to set the AdfsAuthentication parameter on Set-EcpVirtualDirectory to $false before you can use this value.
 
 ```yaml
 Type: Boolean
@@ -276,7 +276,7 @@ Accept wildcard characters: False
 
 The AllAddressListsEnabled parameter specifies which address lists are available in Outlook on the web. Valid values are:
 
-- $true: All address lists are visible in Outlook on the web. This is the default value.
+- $true: All address lists are visible in Outlook on the web. This value is the default.
 - $false: Only the global address list is visible in Outlook on the web.
 
 ```yaml
@@ -297,7 +297,7 @@ Accept wildcard characters: False
 
 The AllowCopyContactsToDeviceAddressBook parameter specifies whether users can copy the contents of their Contacts folder to a mobile device's native address book when using Outlook on the web for devices. Valid values are:
 
-- $true: Contacts can be copied to the device's address book in Outlook on the web for devices. This is the default value.
+- $true: Contacts can be copied to the device's address book in Outlook on the web for devices. This value is the default.
 - $false: Contacts can't be copied to the device's address book in Outlook on the web for devices.
 
 ```yaml
@@ -381,7 +381,7 @@ The AllowOfflineOn parameter specifies when Outlook on the web in offline mode i
 
 - PrivateComputersOnly: Offline mode is available in private computer sessions. By default in Exchange 2013 or later, all Outlook on the web sessions are considered to be on private computers. In Exchange 2013 or later, users can only specify public computer sessions if you've enabled the private/public selection on the sign in page (the LogonPagePublicPrivateSelectionEnabled parameter value is $true).
 - NoComputers: Offline mode is disabled.
-- AllComputers: Offline mode is available for public and private computer sessions. This is the default value.
+- AllComputers: Offline mode is available for public and private computer sessions. This value is the default.
 
 When offline mode is available, users can turn offline mode on or off themselves in Outlook on the web. For more information, see [Use offline settings in Outlook on the web](https://support.microsoft.com/office/a34c9d9d-16ac-4020-b730-ffa7c7540ae7).
 
@@ -403,7 +403,7 @@ Accept wildcard characters: False
 
 The AnonymousFeaturesEnabled parameter specifies whether you want to allow Outlook on the web users that are logged on anonymously to access specific features. Valid values are:
 
-- $true: Features are enabled for anonymous users. For example, anonymous users can view and change meeting content. This is the default value.
+- $true: Features are enabled for anonymous users. For example, anonymous users can view and change meeting content. This value is the default.
 - $false: Features are disabled for anonymous users.
 
 ```yaml
@@ -424,7 +424,7 @@ Accept wildcard characters: False
 
 The BasicAuthentication parameter specifies whether Basic authentication is enabled on the virtual directory. Valid values are:
 
-- $true: Basic authentication is enabled. This is the default value.
+- $true: Basic authentication is enabled. This value is the default.
 - $false: Basic authentication is disabled.
 
 This parameter can be used with the FormsAuthentication parameter or with the DigestAuthentication and WindowsAuthentication parameters.
@@ -530,7 +530,7 @@ Accept wildcard characters: False
 
 The CalendarEnabled parameter specifies whether to enable or disable the calendar in Outlook on the web. Valid values are:
 
-- $true: The Calendar is available in Outlook on the web. This is the default value.
+- $true: The Calendar is available in Outlook on the web. This value is the default.
 - $false: The Calendar isn't available in Outlook on the web.
 
 ```yaml
@@ -553,7 +553,7 @@ This parameter is available only in Exchange Server 2010.
 
 The CalendarPublishingEnabled parameter specifies whether users can publish their calendar from Outlook Web App. Valid values are:
 
-- $true: Calendar publishing is enabled. This is the default value.
+- $true: Calendar publishing is enabled. This value is the default.
 - $false: Calendar publishing is disabled.
 
 ```yaml
@@ -574,7 +574,7 @@ Accept wildcard characters: False
 
 The ChangePasswordEnabled parameter specifies whether users can change their passwords from inside Outlook on the web. Valid values are:
 
-- $true: The Change password option is available in Outlook on the web. This is the default value in on-premises Exchange.
+- $true: The Change password option is available in Outlook on the web. This value is the default in on-premises Exchange.
 - $false: The Change password option isn't available in Outlook on the web.
 
 ```yaml
@@ -595,7 +595,7 @@ Accept wildcard characters: False
 
 The ClassicAttachmentsEnabled parameter specifies whether users can attach local files as regular email attachments in Outlook on the web. Valid values are:
 
-- $true: Users can attach local files to email messages in Outlook on the web. This is the default value.
+- $true: Users can attach local files to email messages in Outlook on the web. This value is the default.
 - $false: Users can't attach local files to email messages in Outlook on the web.
 
 ```yaml
@@ -617,7 +617,7 @@ Accept wildcard characters: False
 The ClientAuthCleanupLevel parameter specifies how much of the cache is cleared when the user logs off from Outlook on the web. Valid values are:
 
 - Low
-- High (This is the default value)
+- High (default value)
 
 This parameter doesn't apply to the light version of Outlook on the web.
 
@@ -660,7 +660,7 @@ Accept wildcard characters: False
 
 The ContactsEnabled parameter specifies whether to enable or disable Contacts in Outlook on the web. Valid values are:
 
-- $true: Contacts are available in Outlook on the web. This is the default value.
+- $true: Contacts are available in Outlook on the web. This value is the default.
 - $false: Contacts aren't available in Outlook on the web.
 
 ```yaml
@@ -704,7 +704,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-This parameter has been deprecated and is no longer used.
+This parameter is deprecated and no longer used.
 
 ```yaml
 Type: Int32
@@ -742,7 +742,7 @@ Accept wildcard characters: False
 
 The DefaultTheme parameter specifies the default theme that's used in Outlook on the web when the user hasn't selected a theme. The default value is blank ($null). For more information about the built-in themes that are available in Outlook on the web, see [Default Outlook on the web themes in Exchange](https://learn.microsoft.com/Exchange/clients/outlook-on-the-web/themes#default-outlook-on-the-web-themes-in-exchange-2016).
 
-Note that this parameter is a text string, and the value you specify isn't validated against the list of available themes.
+This parameter is a text string, and the value you specify isn't validated against the list of available themes.
 
 ```yaml
 Type: String
@@ -764,7 +764,7 @@ This parameter is functional only in Exchange Server 2010.
 
 The DelegateAccessEnabled parameter specifies whether delegates can use Outlook Web App to open folders that they have delegate access to. Valid values are:
 
-- $true: Delegates can open the mailbox in Outlook Web App. This is the default value.
+- $true: Delegates can open the mailbox in Outlook Web App. This value is the default.
 - $false: Delegates can't open the mailbox in Outlook Web App.
 
 ```yaml
@@ -786,7 +786,7 @@ Accept wildcard characters: False
 The DigestAuthentication parameter specifies whether Digest authentication is enabled on the virtual directory. Valid values are:
 
 - $true: Digest authentication is enabled.
-- $false: Digest authentication is disabled. This is the default value.
+- $false: Digest authentication is disabled. This value is the default.
 
 You can use this parameter with the FormsAuthentication parameter.
 
@@ -808,8 +808,8 @@ Accept wildcard characters: False
 
 The DirectFileAccessOnPrivateComputersEnabled parameter specifies the left-click options for attachments in Outlook on the web for private computer sessions. Valid values are:
 
-- $true: Open is available for attachments in Outlook on the web for private computer sessions. This is the default value.
-- $false: Open isn't available for attachments in Outlook on the web for private computer sessions. Note that Office and .pdf documents can still be previewed in Outlook on the web.
+- $true: Open is available for attachments in Outlook on the web for private computer sessions. This value is the default.
+- $false: Open isn't available for attachments in Outlook on the web for private computer sessions. Office and .pdf documents can still be previewed in Outlook on the web.
 
 By default in Exchange 2013 or later, all Outlook on the web sessions are considered to be on private computers.
 
@@ -831,8 +831,8 @@ Accept wildcard characters: False
 
 The DirectFileAccessOnPrivateComputersEnabled parameter specifies the left-click options for attachments in Outlook on the web for public computer sessions. Valid values are:
 
-- $true: Open is available for attachments in Outlook on the web for public computer sessions. This is the default value.
-- $false: Open isn't available for attachments in Outlook on the web for public computer sessions. Note that Office and .pdf documents can still be previewed in Outlook on the web.
+- $true: Open is available for attachments in Outlook on the web for public computer sessions. This value is the default.
+- $false: Open isn't available for attachments in Outlook on the web for public computer sessions. Office and .pdf documents can still be previewed in Outlook on the web.
 
 In Exchange 2013 or later, users can only specify public computer sessions if you've enabled the private/public selection on the sign in page (the LogonPagePublicPrivateSelectionEnabled parameter value is $true).
 
@@ -854,7 +854,7 @@ Accept wildcard characters: False
 
 The DisplayPhotosEnabled parameter specifies whether users see sender photos in Outlook on the web. Valid values are:
 
-- $true: Users see sender photos in Outlook on the web. This is the default value.
+- $true: Users see sender photos in Outlook on the web. This value is the default.
 - $false: Users don't see sender photos in Outlook on the web.
 
 ```yaml
@@ -929,7 +929,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-This parameter has been deprecated and is no longer used.
+This parameter is deprecated and no longer used.
 
 ```yaml
 Type: ExchwebProxyDestinations
@@ -949,7 +949,7 @@ Accept wildcard characters: False
 
 The ExplicitLogonEnabled parameter specifies whether to allow a user to open someone else's mailbox in Outlook on the web (provided that user has permissions to the mailbox). Valid values are:
 
-- $true: A user with the required permissions is able to open someone else's mailbox in Outlook on the web. This is the default value.
+- $true: A user with the required permissions is able to open someone else's mailbox in Outlook on the web. This value is the default.
 - $false: A user with the required permissions isn't able to open someone else's mailbox in Outlook on the web.
 
 ```yaml
@@ -974,7 +974,7 @@ The ExtendedProtectionFlags parameter specifies custom settings for Extended Pro
 - AllowDotlessSPN: Required if you want to use Service Principal Name (SPN) values that don't contain FQDNs (for example, HTTP/ContosoMail instead of HTTP/mail.contoso.com). You specify SPNs with the ExtendedProtectionSPNList parameter. This setting makes Extended Protection for Authentication less secure because dotless certificates aren't unique, so it isn't possible to ensure that the client-to-proxy connection was established over a secure channel.
 - NoServiceNameCheck: The SPN list isn't checked to validate a channel binding token. This setting makes Extended Protection for Authentication less secure. We generally don't recommend this setting.
 - Proxy: A proxy server is responsible for terminating the SSL channel. To use this setting, you need to register an SPN by using the ExtendedProtectionSPNList parameter.
-- ProxyCoHosting: HTTP and HTTPS traffic may be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server.
+- ProxyCoHosting: HTTP and HTTPS traffic might be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server.
 
 To enter multiple values and overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`.
 
@@ -998,7 +998,7 @@ Accept wildcard characters: False
 
 The ExtendedProtectionSPNList parameter specifies a list of valid Service Principal Names (SPNs) if you're using Extended Protection for Authentication on the virtual directory. Valid values are:
 
-- $null (blank): This is the default value.
+- $null (blank): This value is the default.
 - Single SPN or comma delimited list of valid SPNs: The SPN value format is `Protocol\FQDN`. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter.
 
 To enter multiple values and overwrite any existing entries, use the following syntax: `Value1,Value2,...ValueN`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`.
@@ -1023,8 +1023,8 @@ Accept wildcard characters: False
 
 The ExtendedProtectionTokenChecking parameter defines how you want to use Extended Protection for Authentication on the virtual directory. Extended Protection for Authentication isn't enabled by default. Valid values are:
 
-- None: Extended Protection for Authentication isn't be used on the virtual directory. This is the default value.
-- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication will work, but may not be as secure as connections that use Extended Protection for Authentication.
+- None: Extended Protection for Authentication isn't be used on the virtual directory. This value is the default.
+- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication work, but might not be as secure as connections that use Extended Protection for Authentication.
 - Require: Extended Protection for Authentication is used for all connections between clients and the virtual directory. If either the client or server doesn't support it, the connection will fail. If you use this value, you also need to set an SPN value for the ExtendedProtectionSPNList parameter.
 
 **Note**: If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter.
@@ -1166,7 +1166,7 @@ Accept wildcard characters: False
 
 The FilterWebBeaconsAndHtmlForms parameter specifies how web beacons are handled in Outlook on the web. Valid values are:
 
-- UserFilterChoice (This is the default value)
+- UserFilterChoice (default value)
 - ForceFilter
 - DisableFilter
 
@@ -1189,7 +1189,7 @@ Accept wildcard characters: False
 The ForceSaveAttachmentFilteringEnabled parameter specifies whether files are filtered before they can be saved from Outlook on the web. Valid values are:
 
 - $true: The attachments specified by the ForceSaveFileTypes parameter are filtered before they can be saved from Outlook on the web.
-- $false: The attachments aren't filtered before they're saved. This is the default value.
+- $false: The attachments aren't filtered before they're saved. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -1272,7 +1272,7 @@ Accept wildcard characters: False
 The ForceWacViewingFirstOnPrivateComputers parameter specifies whether private computers must first preview an Office file as a web page in Office Online Server (formerly known as Office Web Apps Server and Web Access Companion Server) before opening the file in the local application. Valid values are:
 
 - $true: Private computers must first preview an Office file as a web page in Office Online Server before opening the file.
-- $false: Private computers aren't required to preview an Office file as a web page in Office Online Server before opening the file. This is the default value.
+- $false: Private computers aren't required to preview an Office file as a web page in Office Online Server before opening the file. This value is the default.
 
 By default in Exchange 2013 or later, all Outlook on the web sessions are considered to be on private computers.
 
@@ -1295,7 +1295,7 @@ Accept wildcard characters: False
 The ForceWacViewingFirstOnPublicComputers parameter specifies whether public computers must first preview an Office file as a web page in Office Online Server before opening the file in the local application. Valid values are:
 
 - $true: Public computers must first preview an Office file as a web page in Office Online Server before opening the file.
-- $false: Public computers aren't required to preview an Office file as a web page in Office Online Server before opening the file. This is the default value.
+- $false: Public computers aren't required to preview an Office file as a web page in Office Online Server before opening the file. This value is the default.
 
 In Exchange 2013 or later, users can only specify public computer sessions if you've enabled the private/public selection on the sign in page (the LogonPagePublicPrivateSelectionEnabled parameter value is $true).
 
@@ -1320,7 +1320,7 @@ This parameter is available only in Exchange Server 2010 or Exchange Server 2013
 The ForceWebReadyDocumentViewingFirstOnPrivateComputers parameter specifies whether private computers must first preview an Office file as a web page in WebReady Document Viewing before opening the file from Outlook Web App. Valid values are:
 
 - $true: Private computers must first preview an Office file as a web page in WebReady Document Viewing before opening the file.
-- $false: Private computers aren't required to preview an Office file as a web page in WebReady Document Viewing before opening the file. This is the default value.
+- $false: Private computers aren't required to preview an Office file as a web page in WebReady Document Viewing before opening the file. This value is the default.
 
 By default in Exchange 2013 or later, all Outlook on the web sessions are considered to be on private computers.
 
@@ -1345,7 +1345,7 @@ This parameter is available only in Exchange Server 2010 or Exchange Server 2013
 The ForceWebReadyDocumentViewingFirstOnPublicComputers parameter specifies whether Public computers must first preview an Office file as a web page in WebReady Document Viewing before opening the file from Outlook Web App. Valid values are:
 
 - $true: Public computers must first preview an Office file as a web page in WebReady Document Viewing before opening the file.
-- $false: Public computers aren't required to preview an Office file as a web page in WebReady Document Viewing before opening the file. This is the default value.
+- $false: Public computers aren't required to preview an Office file as a web page in WebReady Document Viewing before opening the file. This value is the default.
 
 In Exchange 2013 or later, users can only specify public computer sessions if you've enabled the private/public selection on the sign in page (the LogonPagePublicPrivateSelectionEnabled parameter value is $true).
 
@@ -1367,7 +1367,7 @@ Accept wildcard characters: False
 
 The FormsAuthentication parameter enables or disables forms-based authentication on the Outlook on the web virtual directory. Valid values are:
 
-- $true: Forms-based authentication is enabled in Outlook on the web. This is the default value. The BasicAuthentication parameter is also set to $true, and the DigestAuthentication and WindowsAuthentication parameters are set to $false.
+- $true: Forms-based authentication is enabled in Outlook on the web. This value is the default. The BasicAuthentication parameter is also set to $true, and the DigestAuthentication and WindowsAuthentication parameters are set to $false.
 - $false: Forms-based authentication is disabled in Outlook on the web.
 
 ```yaml
@@ -1406,7 +1406,7 @@ Accept wildcard characters: False
 
 The GlobalAddressListEnabled parameter specifies whether the global address list is available in Outlook on the web. Valid values are:
 
-- $true: The global address list is visible in Outlook on the web. This is the default value.
+- $true: The global address list is visible in Outlook on the web. This value is the default.
 - $false: The global address list isn't visible in Outlook on the web.
 
 ```yaml
@@ -1446,7 +1446,7 @@ Accept wildcard characters: False
 The GzipLevel parameter sets Gzip configuration information for the Outlook on the web virtual directory. Valid values are:
 
 - Off
-- Low (This is the default value)
+- Low (default value)
 - High
 - Error
 
@@ -1486,7 +1486,7 @@ Accept wildcard characters: False
 
 The InstantMessagingEnabled parameter specifies whether instant messaging is available in Outlook on the web. This does not affect chat capabilities provided by Skype for Business or Teams. Valid values are:
 
-- $true: Instant messaging is available in Outlook on the web. This is the default value.
+- $true: Instant messaging is available in Outlook on the web. This value is the default.
 - $false: Instant messaging isn't available in Outlook on the web.
 
 ```yaml
@@ -1525,7 +1525,7 @@ Accept wildcard characters: False
 
 The InstantMessagingType parameter specifies the type of instant messaging provider in Outlook on the web. Valid values are:
 
-- None: This is the default value.
+- None: This value is the default.
 - Ocs: Lync or Skype (formerly known as Office Communication Server).
 
 ```yaml
@@ -1546,7 +1546,7 @@ Accept wildcard characters: False
 
 The IntegratedFeaturesEnabled parameter specifies whether to allow Outlook on the web users who are logged on using Integrated Windows authentication to access specific features. Valid values are:
 
-- $true: Integrated features are enabled. For example, users logged on using Integrated Windows authentication can view and change meeting content. This is the default value.
+- $true: Integrated features are enabled. For example, users logged on using Integrated Windows authentication can view and change meeting content. This value is the default.
 - $false: Integrated features are disabled.
 
 ```yaml
@@ -1625,7 +1625,7 @@ Accept wildcard characters: False
 
 The IRMEnabled parameter specifies whether Information Rights Management (IRM) features are available in Outlook on the web. Valid values are:
 
-- $true: IRM is available in Outlook on the web. This is the default value.
+- $true: IRM is available in Outlook on the web. This value is the default.
 - $false: IRM isn't available in Outlook on the web.
 
 ```yaml
@@ -1647,7 +1647,7 @@ Accept wildcard characters: False
 The IsPublic parameter specifies whether external users use the virtual directory for Outlook on the web in multiple virtual directory environments (you've configured separate virtual directories on the same server for internal vs. external Outlook on the web connections). Valid values are:
 
 - $true: External users use the virtual directory for Outlook on the web.
-- $false: External users don't use the virtual directory for Outlook on the web. This is the default value.
+- $false: External users don't use the virtual directory for Outlook on the web. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -1667,7 +1667,7 @@ Accept wildcard characters: False
 
 The JournalEnabled parameter specifies whether the Journal folder is available in Outlook on the web. Valid values are:
 
-- $true: The Journal folder is visible in Outlook on the web. This is the default value.
+- $true: The Journal folder is visible in Outlook on the web. This value is the default.
 - $false: The Journal folder isn't visible in Outlook on the web.
 
 ```yaml
@@ -1688,7 +1688,7 @@ Accept wildcard characters: False
 
 The JunkEmailEnabled parameter specifies whether the Junk Email folder and junk email management are available in Outlook on the web. Valid values are:
 
-- $true: The Junk Email folder and junk email management are available in Outlook on the web. This is the default value.
+- $true: The Junk Email folder and junk email management are available in Outlook on the web. This value is the default.
 - $false: The Junk Email folder and junk email management aren't available in Outlook on the web.
 
 ```yaml
@@ -1711,7 +1711,7 @@ This parameter is available only in Exchange Server 2010.
 
 The LegacyRedirectType parameter specifies the type of redirect that Outlook Web App uses to a legacy Client Access server or Front End server when forms-based authentication isn't used on the Exchange 2010 Outlook Web App virtual directory. Valid values are:
 
-- Silent: A standard redirect is used. This is the default value.
+- Silent: A standard redirect is used. This value is the default.
 - Manual: An intermediate page is displayed to show the legacy URL so that users can change their bookmarks.
 
 ```yaml
@@ -1754,7 +1754,7 @@ Accept wildcard characters: False
 
 The LogonFormat parameter specifies the type of logon format that's required for forms-based authentication on the Outlook on the web sign-in page. Valid values are:
 
-- FullDomain: Requires the format domain\\username. This is the default value.
+- FullDomain: Requires the format domain\\username. This value is the default.
 - UserName: Requires only the username, but you also need to specify a value for the DefaultDomain parameter.
 - PrincipalName: Requires the user principal name (UPN) (for example, user@contoso.com). This sign-in method works only for users whose UPN name is the same as their email address.
 
@@ -1776,7 +1776,7 @@ Accept wildcard characters: False
 
 The LogonPageLightSelectionEnabled parameter specifies whether the Outlook on the web sign-in page includes the option to sign in to the light version of Outlook on the web. Valid values are:
 
-- $true: The option to use the light version of Outlook on the web is available on the sign-in page. This is the default value.
+- $true: The option to use the light version of Outlook on the web is available on the sign-in page. This value is the default.
 - $false: The option to use the light version of Outlook on the web is available on the sign-in page.
 
 This parameter is meaningful only for browsers that support the full version of Outlook on the web; unsupported browsers are always required to use the light version of Outlook on the web.
@@ -1800,7 +1800,7 @@ Accept wildcard characters: False
 The LogonPagePublicPrivateSelectionEnabled parameter specifies whether the Outlook on the web sign-in page includes the public/private computer session option at sign-in. Valid values are:
 
 - $true: The public/private computer session selection is available on the Outlook on the web sign-in page.
-- $false: The public/private computer session selection isn't available on the Outlook on the web sign-in page. All sessions are considered to be on private computers. This is the default value.
+- $false: The public/private computer session selection isn't available on the Outlook on the web sign-in page. All sessions are considered to be on private computers. This value is the default.
 
 By default in Exchange 2013 or later, all Outlook on the web sessions are considered to be on private computers. Users can only specify public computer sessions if you've set this parameter value to $true.
 
@@ -1824,7 +1824,7 @@ Accept wildcard characters: False
 
 The NotesEnabled parameter specifies whether the Notes folder is available in Outlook on the web. Valid values are:
 
-- $true: The Notes folder is visible in Outlook on the web. This is the default value.
+- $true: The Notes folder is visible in Outlook on the web. This value is the default.
 - $false: The Notes folder isn't visible in Outlook on the web.
 
 ```yaml
@@ -1923,7 +1923,7 @@ Accept wildcard characters: False
 
 The OutboundCharset parameter specifies the character set that's used for outgoing messages in Outlook on the web. Valid values are:
 
-- AutoDetect: Examine the first 2 kilobytes (KB) of text in the message to determine the character set that's used in outgoing messages. This is the default value.
+- AutoDetect: Examine the first 2 kilobytes (KB) of text in the message to determine the character set that's used in outgoing messages. This value is the default.
 - AlwaysUTF8: Always use UTF-8 encoded Unicode characters in outgoing messages, regardless of the detected text in the message, or the user's language choice in Outlook on the web. Use this value if replies to UTF-8 encoded messages aren't being encoded in UTF-8.
 - UserLanguageChoice: Use the user's language choice in Outlook on the web to encode outgoing messages.
 
@@ -1945,7 +1945,7 @@ Accept wildcard characters: False
 
 The OWALightEnabled parameter controls the availability of the light version of Outlook on the web. Valid values are:
 
-- $true: The light version of Outlook on the web is available. This is the default value.
+- $true: The light version of Outlook on the web is available. This value is the default.
 - $false: The light version of Outlook on the web is isn't available. This setting prevents access to Outlook on the web for unsupported browsers that can only use the light version of Outlook on the web.
 
 ```yaml
@@ -1968,7 +1968,7 @@ This parameter is available only in Exchange Server 2010.
 
 The OWAMiniEnabled parameter controls the availability of the mini version of Outlook Web App. Valid values are:
 
-- $true: The mini version of Outlook Web App is available. This is the default value.
+- $true: The mini version of Outlook Web App is available. This value is the default.
 - $false: The mini version of Outlook Web App isn't available.
 
 ```yaml
@@ -1989,7 +1989,7 @@ Accept wildcard characters: False
 
 The PremiumClientEnabled parameter controls the availability of the full version of Outlook Web App. Valid values are:
 
-- $true: The full version of Outlook Web App is available for supported browsers. This is the default value.
+- $true: The full version of Outlook Web App is available for supported browsers. This value is the default.
 - $false: The full version of Outlook Web App isn't available.
 
 ```yaml
@@ -2012,7 +2012,7 @@ This parameter is functional only in Exchange Server 2010.
 
 The PublicFoldersEnabled parameter specifies whether a user can browse or read items in public folders in Outlook Web App. Valid values are:
 
-- $true: Public folders are available in Outlook Web App. This is the default value.
+- $true: Public folders are available in Outlook Web App. This value is the default.
 - $false: Public folders aren't available in Outlook Web App.
 
 ```yaml
@@ -2035,7 +2035,7 @@ This parameter is functional only in Exchange Server 2010.
 
 The RecoverDeletedItemsEnabled parameter specifies whether a user can use Outlook Web App to view, recover, or delete permanently items that have been deleted from the Deleted Items folder. Valid values are:
 
-- $true: Users can view, recover, or permanently delete items in Outlook Web App. This is the default value.
+- $true: Users can view, recover, or permanently delete items in Outlook Web App. This value is the default.
 - $false: Users can't view, recover, or permanently delete items in Outlook Web App. Items deleted from the Deleted Items folder in Outlook Web App are still retained.
 
 ```yaml
@@ -2056,7 +2056,7 @@ Accept wildcard characters: False
 
 The RedirectToOptimalOWAServer parameter specifies whether to find the optimal server for Outlook on the web. Valid values are:
 
-- $true: Outlook on the web uses service discovery to find the best Mailbox server to use after a user authenticates. This is the default value.
+- $true: Outlook on the web uses service discovery to find the best Mailbox server to use after a user authenticates. This value is the default.
 - $false: Outlook on the web doesn't redirect clients to the optimal Mailbox server.
 
 ```yaml
@@ -2077,7 +2077,7 @@ Accept wildcard characters: False
 
 The ReferenceAttachmentsEnabled parameter specifies whether users can attach files from the cloud as linked attachments in Outlook on the web. Valid values are:
 
-- $true: Users can attach files that are stored in the cloud as linked attachments. If the file hasn't been uploaded to the cloud yet, the users can attach and upload the file in the same step. This is the default value.
+- $true: Users can attach files that are stored in the cloud as linked attachments. If the file hasn't been uploaded to the cloud yet, the users can attach and upload the file in the same step. This value is the default.
 - $false: Users can't share files in the cloud as linked attachments. They need to download a local copy of the file before attaching the file to the email message.
 
 ```yaml
@@ -2098,7 +2098,7 @@ Accept wildcard characters: False
 
 The RemindersAndNotificationsEnabled parameter specifies whether notifications and reminders are enabled in Outlook on the web. Valid values are:
 
-- $true: Notifications and reminders are enabled in Outlook on the web. This is the default value.
+- $true: Notifications and reminders are enabled in Outlook on the web. This value is the default.
 - $false: Notifications and reminders are disabled in Outlook on the web.
 
 This parameter doesn't apply to the light version of Outlook Web App.
@@ -2121,7 +2121,7 @@ Accept wildcard characters: False
 
 This parameter is functional only in Exchange Server 2010.
 
-This parameter has been deprecated and is no longer used.
+This parameter is deprecated and no longer used.
 
 ```yaml
 Type: RemoteDocumentsActions
@@ -2141,7 +2141,7 @@ Accept wildcard characters: False
 
 This parameter is functional only in Exchange Server 2010.
 
-This parameter has been deprecated and is no longer used.
+This parameter is deprecated and no longer used.
 
 ```yaml
 Type: MultiValuedProperty
@@ -2161,7 +2161,7 @@ Accept wildcard characters: False
 
 This parameter is functional only in Exchange Server 2010.
 
-This parameter has been deprecated and is no longer used.
+This parameter is deprecated and no longer used.
 
 ```yaml
 Type: MultiValuedProperty
@@ -2181,7 +2181,7 @@ Accept wildcard characters: False
 
 This parameter is functional only in Exchange Server 2010.
 
-This parameter has been deprecated and is no longer used.
+This parameter is deprecated and no longer used.
 
 ```yaml
 Type: MultiValuedProperty
@@ -2201,7 +2201,7 @@ Accept wildcard characters: False
 
 The ReportJunkEmailEnabled parameter specifies whether users can report messages as junk or not junk to Microsoft in Outlook on the web. Valid values are:
 
-- $true: This is the default value. Selecting a message in the Junk Email folder and clicking **Not junk** \> **Not junk** moves the message back into the Inbox and gives users the option to report the message to Microsoft. Selecting a message in any other email folder and clicking **Junk** \> **Junk folder** moves the message to the Junk Email folder and gives users the option to report the message to Microsoft. Selecting a message and clicking **Not junk** \> **Phishing** (in the Junk Email folder) and **Junk** \> **Phishing** (everywhere else) are available to report phishing messages to Microsoft.
+- $true: This value is the default. Selecting a message in the Junk Email folder and clicking **Not junk** \> **Not junk** moves the message back into the Inbox and gives users the option to report the message to Microsoft. Selecting a message in any other email folder and clicking **Junk** \> **Junk folder** moves the message to the Junk Email folder and gives users the option to report the message to Microsoft. Selecting a message and clicking **Not junk** \> **Phishing** (in the Junk Email folder) and **Junk** \> **Phishing** (everywhere else) are available to report phishing messages to Microsoft.
 - $false: Selecting a message in the Junk Email folder and clicking **Not junk** \> **Not junk** moves the message back into the Inbox with no option to report the message to Microsoft. Selecting a message in any other email folder and clicking **Junk** \> **Junk** moves the message to the Junk Email folder with no option to report the message to Microsoft. Selecting a message and clicking **Not junk** \> **Phishing** (in the Junk Email folder) and **Junk** \> **Phishing** (everywhere else) are available to report phishing messages to Microsoft.
 
 This parameter is meaningful only when the JunkEmailEnabled parameter is set to $true.
@@ -2224,7 +2224,7 @@ Accept wildcard characters: False
 
 The RulesEnabled parameter specifies whether a user can view, create, or modify server-side rules in Outlook on the web. Valid values are:
 
-- $true: Users can view, create, or modify server-side rules in Outlook on the web. This is the default value.
+- $true: Users can view, create, or modify server-side rules in Outlook on the web. This value is the default.
 - $false: Users can't view, create, or modify server-side rules in Outlook on the web.
 
 ```yaml
@@ -2245,7 +2245,7 @@ Accept wildcard characters: False
 
 The SaveAttachmentsToCloudEnabled parameter specifies whether users can save regular email attachments to the cloud. Valid values are:
 
-- $true: Users can save regular email attachments to the cloud. This is the default value.
+- $true: Users can save regular email attachments to the cloud. This value is the default.
 - $false: Users can only save regular email attachments locally.
 
 ```yaml
@@ -2268,7 +2268,7 @@ This parameter is functional only in Exchange Server 2010.
 
 The SearchFoldersEnabled parameter specifies whether Search Folders are available in Outlook on the web. Valid values are:
 
-- $true: Search Folders are visible in Outlook on the Web. This is the default value.
+- $true: Search Folders are visible in Outlook on the Web. This value is the default.
 - $false: Search Folders aren't visible in Outlook on the Web.
 
 ```yaml
@@ -2289,7 +2289,7 @@ Accept wildcard characters: False
 
 The SetPhotoEnabled parameter specifies whether users can add, change, and remove their sender photo in Outlook on the web. Valid values are:
 
-- $true: Users can manage their photos in Outlook on the web. This is the default value.
+- $true: Users can manage their photos in Outlook on the web. This value is the default.
 - $false: Users can't manage their user photo in Outlook on the web.
 
 ```yaml
@@ -2328,7 +2328,7 @@ Accept wildcard characters: False
 
 The SignaturesEnabled parameter specifies whether to enable or disable the use of signatures in Outlook on the web. Valid values are:
 
-- $true: Signatures are available in Outlook on the web. This is the default value.
+- $true: Signatures are available in Outlook on the web. This value is the default.
 - $false: Signatures aren't available in Outlook on the web.
 
 ```yaml
@@ -2351,7 +2351,7 @@ This parameter is functional only in Exchange Server 2010.
 
 The SilverlightEnabled parameter specifies whether a user can use Microsoft Silverlight features in Outlook Web App. Valid values are:
 
-- $true: Silverlight features are available in Outlook Web App. This is the default value.
+- $true: Silverlight features are available in Outlook Web App. This value is the default.
 - $false: Silverlight features aren't available in Outlook Web App.
 
 ```yaml
@@ -2374,7 +2374,7 @@ This parameter is functional only in Exchange Server 2010.
 
 The SMimeEnabled parameter specifies whether users can download the S/MIME control for Outlook Web App and use it to read and compose signed and encrypted messages. Valid values are:
 
-- $true: Users can read and compose S/MIME signed and encrypted messages in Outlook Web App. This is the default value.
+- $true: Users can read and compose S/MIME signed and encrypted messages in Outlook Web App. This value is the default.
 - $false: Users can't read or compose messages in Outlook Web App that are opaque-signed or encrypted by using S/MIME. Messages that are clear-signed can be read but not composed, and their signatures aren't validated.
 
 **Note**: In Exchange 2013 or later, use the Get-SmimeConfig and Set-SmimeConfig cmdlets to configure the S/MIME settings in Outlook on the web. For more information, see [S/MIME for message signing and encryption](https://learn.microsoft.com/Exchange/policy-and-compliance/smime).
@@ -2399,7 +2399,7 @@ This parameter is functional only in Exchange Server 2010.
 
 The SpellCheckerEnabled parameter specifies whether to enable or disable the built-in Outlook Web App spell checker in the full version of Outlook Web App. Valid values are:
 
-- $true: Spell checking is available in Outlook Web App. This is the default value.
+- $true: Spell checking is available in Outlook Web App. This value is the default.
 - $false: Spell checking isn't available in Outlook Web App.
 
 This parameter doesn't apply to the light version of Outlook Web App.
@@ -2422,7 +2422,7 @@ Accept wildcard characters: False
 
 The TasksEnabled parameter specifies whether Tasks folder is available in Outlook on the web. Valid values are:
 
-- $true: The Tasks folder is available in Outlook on the web. This is the default value.
+- $true: The Tasks folder is available in Outlook on the web. This value is the default.
 - $false: The Tasks folder isn't available in Outlook on the web.
 
 This parameter doesn't apply to the light version of Outlook on the web.
@@ -2445,7 +2445,7 @@ Accept wildcard characters: False
 
 The TextMessagingEnabled parameter specifies whether users can send and receive text messages in Outlook on the web. Valid values are:
 
-- $true: Text messaging is available in Outlook on the web. This is the default value.
+- $true: Text messaging is available in Outlook on the web. This value is the default.
 - $false: Text messaging isn't available in Outlook on the web.
 
 This parameter doesn't apply to the light version of Outlook on the web.
@@ -2468,7 +2468,7 @@ Accept wildcard characters: False
 
 The ThemeSelectionEnabled parameter specifies whether users can change the theme in Outlook on the web. Valid values are:
 
-- $true: Users can specify the theme in Outlook on the web. This is the default value.
+- $true: Users can specify the theme in Outlook on the web. This value is the default.
 - $false: Users can't specify or change the theme in Outlook on the web.
 
 ```yaml
@@ -2489,10 +2489,10 @@ Accept wildcard characters: False
 
 The UMIntegrationEnabled parameter specifies whether Unified Messaging (UM) integration is enabled in Outlook on the web. Valid values are:
 
-- $true: UM integration is enabled in Outlook on the web. This is the default value.
+- $true: UM integration is enabled in Outlook on the web. This value is the default.
 - $false: UM integration is disabled in Outlook on the web.
 
-This setting applies only if Unified Messaging has been enabled for a user (for example, bu using the Enable-UMMailbox cmdlet).
+This setting applies only if Unified Messaging is enabled for a user (for example, bu using the Enable-UMMailbox cmdlet).
 
 This parameter doesn't apply to the light version of Outlook on the web.
 
@@ -2512,7 +2512,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-This parameter has been deprecated and is no longer used.
+This parameter is deprecated and no longer used.
 
 ```yaml
 Type: Boolean
@@ -2530,7 +2530,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-This parameter has been deprecated and is no longer used.
+This parameter is deprecated and no longer used.
 
 ```yaml
 Type: Boolean
@@ -2551,7 +2551,7 @@ Accept wildcard characters: False
 The UseGB18030 parameter specifies whether to use the GB18030 character set instead of GB2312 in Outlook on the web. Valid values are:
 
 - $true: GB18030 is used wherever GB2312 would have been used in Outlook on the web.
-- $false: GB2312 isn't replaced by GB18030 in Outlook on the web. This is the default value.
+- $false: GB2312 isn't replaced by GB18030 in Outlook on the web. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -2572,7 +2572,7 @@ Accept wildcard characters: False
 The UseISO885915 parameter specifies whether to use the character set ISO8859-15 instead of ISO8859-1 in Outlook on the web. Valid values are:
 
 - $true: ISO8859-15 is used wherever ISO8859-1 would have been used in Outlook on the web.
-- $false: ISO8859-1 isn't replaced by GB18030 in Outlook on the web. This is the default value.
+- $false: ISO8859-1 isn't replaced by GB18030 in Outlook on the web. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -2610,7 +2610,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-This parameter has been deprecated and is no longer used.
+This parameter is deprecated and no longer used.
 
 ```yaml
 Type: VirtualDirectoryTypes
@@ -2630,7 +2630,7 @@ Accept wildcard characters: False
 
 The WacEditingEnabled parameter specifies whether to enable or disable editing documents in Outlook on the web by using Office Online Server (formerly known as Office Web Apps Server and Web Access Companion Server). Valid values are:
 
-- $true: Users can edit supported documents in Outlook on the web. This is the default value.
+- $true: Users can edit supported documents in Outlook on the web. This value is the default.
 - $false: Users can't edit supported documents in Outlook on the web.
 
 ```yaml
@@ -2651,7 +2651,7 @@ Accept wildcard characters: False
 
 The WacViewingOnPrivateComputersEnabled parameter specifies whether to enable or disable web viewing of supported Office documents private computer sessions in Office Online Server (formerly known as Office Web Apps Server and Web Access Companion Server). By default, all Outlook on the web sessions are considered to be on private computers. Valid values are:
 
-- $true: In private computer sessions, users can view supported Office documents in the web browser. This is the default value.
+- $true: In private computer sessions, users can view supported Office documents in the web browser. This value is the default.
 - $false: In private computer sessions, users can't view supported Office documents in the web browser. Users can still open the file in a supported application or save the file locally.
 
 By default in Exchange 2013 or later, all Outlook on the web sessions are considered to be on private computers.
@@ -2674,7 +2674,7 @@ Accept wildcard characters: False
 
 The WacViewingOnPublicComputersEnabled parameter specifies whether to enable or disable web viewing of supported Office documents in public computer sessions in Office Online Server. Valid values are:
 
-- $true: In public computer sessions, users can view supported Office documents in the web browser. This is the default value.
+- $true: In public computer sessions, users can view supported Office documents in the web browser. This value is the default.
 - $false: In public computer sessions, users can't view supported Office documents in the web browser. Users can still open the file in a supported application or save the file locally.
 
 In Exchange 2013 or later, users can only specify public computer sessions if you've enabled the private/public selection on the sign in page (the LogonPagePublicPrivateSelectionEnabled parameter value is $true).
@@ -2698,7 +2698,7 @@ Accept wildcard characters: False
 The WebPartsFrameOptionsType parameter specifies what sources can access web parts in IFRAME or FRAME elements in Outlook on the web. Valid values are:
 
 - None: There are no restrictions on displaying Outlook on the web content in a frame.
-- SameOrigin: This is the default value and the recommended value. Display Outlook on the web content only in a frame that has the same origin as the content.
+- SameOrigin: This value is the default and the recommended value. Display Outlook on the web content only in a frame that has the same origin as the content.
 - Deny: Blocks display of Outlook on the web content in a frame, regardless of the origin of the site attempting to access it.
 
 ```yaml
@@ -2721,7 +2721,7 @@ This parameter is available only in Exchange Server 2010 and Exchange Server 201
 
 The WebReadyDocumentViewingForAllSupportedTypes parameter specifies whether to enable WebReady Document Viewing for all supported file and MIME types. Valid values are:
 
-- $true: All supported attachment types are available for WebReady Document Viewing. This is the default value.
+- $true: All supported attachment types are available for WebReady Document Viewing. This value is the default.
 - $false: Only the attachment types that are specified by the WebReadyFileTypes and WebReadyMimeTypes parameters are available for WebReady Document Viewing (you can remove values from the lists).
 
 ```yaml
@@ -2744,7 +2744,7 @@ This parameter is available only in Exchange Server 2010 and Exchange Server 201
 
 The WebReadyDocumentViewingOnPrivateComputersEnabled parameter specifies whether WebReady Document Viewing is available in private computer sessions. Valid values are:
 
-- $true: WebReady Document Viewing is available in private computer sessions. This is the default value.
+- $true: WebReady Document Viewing is available in private computer sessions. This value is the default.
 - $false: WebReady Document Viewing isn't available in private computer sessions.
 
 By default in Exchange 2013, all Outlook on the web sessions are considered to be on private computers.
@@ -2769,7 +2769,7 @@ This parameter is available only in Exchange Server 2010 and Exchange Server 201
 
 The WebReadyDocumentViewingOnPublicComputersEnabled parameter specifies whether WebReady Document Viewing is in public computer sessions. Valid values are:
 
-- $true: WebReady Document Viewing is available for public computer sessions. This is the default value.
+- $true: WebReady Document Viewing is available for public computer sessions. This value is the default.
 - $false: WebReady Document Viewing isn't available for public computer sessions.
 
 In Exchange 2013, users can only specify public computer sessions if you've enabled the private/public selection on the sign in page (the LogonPagePublicPrivateSelectionEnabled parameter value is $true).
@@ -2928,7 +2928,7 @@ Accept wildcard characters: False
 The WindowsAuthentication parameter enables or disables Integrated Windows authentication on the virtual directory. Valid values are:
 
 - $true: Integrated Windows authentication is enabled on the Outlook on the web virtual directory.
-- $false: Integrated Windows authentication is disabled on the Outlook on the web virtual directory. This is the default value.
+- $false: Integrated Windows authentication is disabled on the Outlook on the web virtual directory. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -2946,7 +2946,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-This parameter has been deprecated and is no longer used.
+This parameter is deprecated and no longer used.
 
 ```yaml
 Type: Boolean
@@ -2964,7 +2964,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-This parameter has been deprecated and is no longer used.
+This parameter is deprecated and no longer used.
 
 ```yaml
 Type: Boolean
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-PartnerApplication.md b/exchange/exchange-ps/ExchangePowerShell/Set-PartnerApplication.md
index 7d756ac636..5be97a4965 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-PartnerApplication.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-PartnerApplication.md
@@ -80,7 +80,7 @@ Set-PartnerApplication [-Identity] <PartnerApplicationIdParameter>
 ## DESCRIPTION
 You can configure partner applications such as SharePoint to access Exchange resources. Use the New-PartnerApplication cmdlet to create a partner application configuration for an application that needs to access Exchange resources. For details, see [Plan Exchange 2016 integration with SharePoint and Skype for Business](https://learn.microsoft.com/Exchange/plan-and-deploy/integration-with-sharepoint-and-skype/integration-with-sharepoint-and-skype). We recommend that you use the Configure-EnterprisePartnerApplication.ps1 script in the %ExchangeInstallPath%Scripts folder to configure partner applications.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -140,7 +140,7 @@ Accept wildcard characters: False
 
 The AccountType parameter specifies the type of Microsoft account that's required for the partner application. Valid values are:
 
-- OrganizationalAccount: This is the default value
+- OrganizationalAccount: This value is the default
 - ConsumerAccount
 
 ```yaml
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-PendingFederatedDomain.md b/exchange/exchange-ps/ExchangePowerShell/Set-PendingFederatedDomain.md
index 406c4a2b4c..2024688f5a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-PendingFederatedDomain.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-PendingFederatedDomain.md
@@ -36,7 +36,7 @@ Set-PendingFederatedDomain [[-Identity] <OrganizationIdParameter>]
 ## DESCRIPTION
 This cmdlet allows the Exchange admin center to save domains selected as the FederatedOrganizationIdentifier or federated domains when proof of domain ownership hasn't been completed.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-PhishSimOverridePolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-PhishSimOverridePolicy.md
index 49519a0178..b4bb856629 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-PhishSimOverridePolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-PhishSimOverridePolicy.md
@@ -33,7 +33,7 @@ Set-PhishSimOverridePolicy [-Identity] <PolicyIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -132,7 +132,7 @@ Accept wildcard characters: False
 
 The Enabled parameter specifies whether the policy is enabled. Valid values are:
 
-- $true: The policy is enabled. This is the default value.
+- $true: The policy is enabled. This value is the default.
 - $false: The policy is disabled.
 
 ```yaml
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-Place.md b/exchange/exchange-ps/ExchangePowerShell/Set-Place.md
index 0fdf11de3f..8cade9febb 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-Place.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-Place.md
@@ -53,7 +53,7 @@ Set-Place [-Identity] <RecipientIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -298,7 +298,7 @@ Accept wildcard characters: False
 The IsWheelChairAccessible parameter specifies whether the room is wheelchair accessible. Valid values are:
 
 - $true: The room is wheelchair accessible.
-- $false: The room is not wheelchair accessible. This is the default value.
+- $false: The room is not wheelchair accessible. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -339,7 +339,7 @@ Accept wildcard characters: False
 The MTREnabled parameter identifies the room as configured with a Microsoft Teams room system. You can add Teams room systems as audio sources in Teams meetings that involve the room. Valid values are:
 
 - $true: The room is has a Teams room system. You can add the Teams room system to Microsoft Teams meetings when selecting to join a meeting with room audio.
-- $false: The room is does not have a Teams room system. Users will join Teams meetings using their PC or mobile device audio instead of using room audio. This is the default value.
+- $false: The room is does not have a Teams room system. Users join Teams meetings using their PC or mobile device audio instead of using room audio. This value is the default.
 
 For more information about Microsoft Teams Rooms, see [Microsoft Teams Rooms](https://learn.microsoft.com/microsoftteams/rooms/).
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-PolicyConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-PolicyConfig.md
index 6fac58c159..a5938c4bcd 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-PolicyConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-PolicyConfig.md
@@ -321,7 +321,7 @@ The EnableLabelCoauth parameter enables or disables co-authoring support in Offi
 Disabling co-authoring support in Office desktop apps in the organization has the following consequences:
 
 - For apps and services that support the new labeling metadata, they now revert to the original metadata format and location when labels are read or saved.
-- The new metadata format and location for Office documents that was used while the setting was enabled will not be copied to the original format and location. As a result, this labeling information for unencrypted Word, Excel, and PowerPoint files will be lost.
+- The new metadata format and location for Office documents used while the setting was enabled isn't copied to the original format and location. As a result, this labeling information for unencrypted Word, Excel, and PowerPoint files is lost.
 - Co-authoring and AutoSave no longer work in your organization for labeled and encrypted documents.
 - Sensitivity labels remain enabled for Office files in OneDrive and SharePoint.
 
@@ -343,7 +343,7 @@ Accept wildcard characters: False
 
 The EnableSpoAipMigration parameter enables or disables built-in labeling for supported Office files in SharePoint and OneDrive. Valid values are:
 
-- $true: Users can apply your sensitivity labels in Office for the web. Users will see the Sensitivity button on the ribbon so they can apply labels, and see any applied label name on the status bar.
+- $true: Users can apply your sensitivity labels in Office for the web. Users see the Sensitivity button on the ribbon so they can apply labels, and see any applied label name on the status bar.
 - $false: Users can't apply your sensitivity labels in Office for the web.
 
 ```yaml
@@ -589,7 +589,7 @@ Accept wildcard characters: False
 The RuleErrorAction parameter specifies what to do if an error is encountered during the evaluation of the rule. Valid values are:
 
 - Ignore
-- RetryThenBlock (This is the default value)
+- RetryThenBlock (default value)
 
 ```yaml
 Type: PolicyRuleErrorAction
@@ -610,7 +610,7 @@ Accept wildcard characters: False
 
 The SenderAddressLocation parameter specifies where to look for sender addresses in conditions and exceptions that examine sender email addresses. Valid values are:
 
-- Header: Only examine senders in the message headers (for example, the From, Sender, or Reply-To fields). This is the default value.
+- Header: Only examine senders in the message headers (for example, the From, Sender, or Reply-To fields). This value is the default.
 - Envelope: Only examine senders from the message envelope (the MAIL FROM value that was used in the SMTP transmission, which is typically stored in the Return-Path field).
 - HeaderOrEnvelope: Examine senders in the message header and the message envelope.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-PolicyTipConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-PolicyTipConfig.md
index 3cd1fde963..75a9554dd4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-PolicyTipConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-PolicyTipConfig.md
@@ -13,7 +13,7 @@ title: Set-PolicyTipConfig
 # Set-PolicyTipConfig
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-PolicyTipConfig cmdlet to modify custom Policy Tips in your organization. You can't modify built-in Policy Tips.
 
@@ -31,7 +31,7 @@ Set-PolicyTipConfig [-Identity] <PolicyTipConfigIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-PopSettings.md b/exchange/exchange-ps/ExchangePowerShell/Set-PopSettings.md
index 47d9968636..0f07bd405a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-PopSettings.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-PopSettings.md
@@ -57,7 +57,7 @@ Set-PopSettings [-AuthenticatedConnectionTimeout <EnhancedTimeSpan>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -96,7 +96,7 @@ Set-PopSettings -X509CertificateName mail.contoso.com
 
 This example specifies the certificate that contains mail.contoso.com is used to encrypt POP3 client connections.
 
-**Note**: For single subject certificates or a SAN certificates, you also need to assign the certificate to the Exchange POP service by using the Enable-ExchangeCertificate cmdlet. For wildcard certificates, you don't need to assign the certificate to the Exchange POP service (you'll receive an error if you try).
+**Note**: For single subject certificates or a SAN certificates, you also need to assign the certificate to the Exchange POP service by using the Enable-ExchangeCertificate cmdlet. For wildcard certificates, you don't need to assign the certificate to the Exchange POP service (you get an error if you try).
 
 ## PARAMETERS
 
@@ -146,7 +146,7 @@ Accept wildcard characters: False
 
 The CalendarItemRetrievalOption parameter specifies how calendar items are presented to POP3 clients. Valid values are:
 
-- 0 or iCalendar. This is the default value.
+- 0 or iCalendar. This value is the default.
 - 1 or IntranetUrl.
 - 2 or InternetUrl.
 - 3 or Custom.
@@ -211,7 +211,7 @@ Accept wildcard characters: False
 The EnableExactRFC822Size parameter specifies how message sizes are presented to POP3 clients. Valid values are:
 
 - $true: Calculate the exact message size. Because this setting can negatively affect performance, you should configure it only if it's required by your POP3 clients.
-- $false: Use an estimated message size. This is the default value.
+- $false: Use an estimated message size. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -231,7 +231,7 @@ Accept wildcard characters: False
 
 The EnableGSSAPIAndNTLMAuth parameter specifies whether connections can use Integrated Windows authentication (NTLM) by using the Generic Security Services application programming interface (GSSAPI). This setting applies to connections where Transport Layer Security (TLS) is disabled. Valid values are:
 
-- $true: NTLM for POP3 connections is enabled. This is the default value.
+- $true: NTLM for POP3 connections is enabled. This value is the default.
 - $false: NTLM for POP3 connections is disabled.
 
 ```yaml
@@ -253,7 +253,7 @@ Accept wildcard characters: False
 The EnforceCertificateErrors parameter specifies whether to enforce Secure Sockets Layer (SSL) certificate validation failures. Valid values are:
 
 - $true: If the certificate isn't valid or doesn't match the target POP3 server's FQDN, the connection attempt fails.
-- $false: The server doesn't deny POP3 connections based on certificate errors. This is the default value.
+- $false: The server doesn't deny POP3 connections based on certificate errors. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -273,7 +273,7 @@ Accept wildcard characters: False
 
 The ExtendedProtectionPolicy parameter specifies how Extended Protection for Authentication is used for POP3 connections. Valid values are:
 
-- None: Extended Protection for Authentication isn't used. This is the default value.
+- None: Extended Protection for Authentication isn't used. This value is the default.
 - Allow: Extended Protection for Authentication is used only if it's supported by the incoming POP3 connection. If it's not, Extended Protection for Authentication isn't used.
 - Require: Extended Protection for Authentication is required for all POP3 connections. If the incoming POP3 connection doesn't support it, the connection is rejected.
 
@@ -373,8 +373,8 @@ Accept wildcard characters: False
 
 The LogFileRollOverSettings parameter defines how frequently POP3 protocol logging creates a new log file. Valid values are:
 
-- 1 or Hourly. This is the default value in Exchange 2019 and Exchange 2016.
-- 2 or Daily. This is the default value in Exchange 2013 and Exchange 2010.
+- 1 or Hourly. This value is the default in Exchange 2019 and Exchange 2016.
+- 2 or Daily. This value is the default in Exchange 2013 and Exchange 2010.
 - 3 or Weekly.
 - 4 or Monthly.
 
@@ -400,7 +400,7 @@ The LoginType parameter specifies the authentication method for POP3 connections
 
 - 1 or PlainTextLogin.
 - 2 or PlainTextAuthentication.
-- 3 or SecureLogin. This is the default value.
+- 3 or SecureLogin. This value is the default.
 
 ```yaml
 Type: LoginOptions
@@ -428,7 +428,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The default value is 0, which means a new POP3 protocol log file is created at the frequency that's specified by the LogFileRollOverSettings parameter.
 
@@ -529,7 +529,7 @@ The MessageRetrievalMimeFormat parameter specifies the MIME encoding of messages
 - 2 or HtmlAndTextAlternative.
 - 3 or TextEnrichedOnly.
 - 4 or TextEnrichedAndTextAlternative.
-- 5 or BestBodyFormat. This is the default value.
+- 5 or BestBodyFormat. This value is the default.
 - 6 or Tnef.
 
 ```yaml
@@ -550,7 +550,7 @@ Accept wildcard characters: False
 
 The MessageRetrievalSortOrder parameter specifies how retrieved messages are sorted. Valid values are:
 
-- 0 or Ascending. This is the default value.
+- 0 or Ascending. This value is the default.
 - 1 or Descending.
 
 ```yaml
@@ -612,7 +612,7 @@ Accept wildcard characters: False
 The ProtocolLogEnabled parameter specifies whether to enable protocol logging for POP3. Valid values are:
 
 - $true: POP3 protocol logging is enabled.
-- $false: POP3 protocol logging is disabled. This is the default value.
+- $false: POP3 protocol logging is disabled. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -700,7 +700,7 @@ Accept wildcard characters: False
 The SuppressReadReceipt parameter specifies whether to stop duplicate read receipts from being sent to POP3 clients that have the Send read receipts for messages I send setting configured in their POP3 email program. Valid values are:
 
 - $true: The sender receives a read receipt only when the recipient opens the message.
-- $false: The sender receives a read receipt when the recipient downloads the message, and when the recipient opens the message. This is the default value.
+- $false: The sender receives a read receipt when the recipient downloads the message, and when the recipient opens the message. This value is the default.
 
 ```yaml
 Type: Boolean
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-PowerShellVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Set-PowerShellVirtualDirectory.md
index 552dbc3950..955bf80c98 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-PowerShellVirtualDirectory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-PowerShellVirtualDirectory.md
@@ -41,7 +41,7 @@ Set-PowerShellVirtualDirectory [-Identity] <VirtualDirectoryIdParameter>
 ## DESCRIPTION
 Although it's possible to modify a Windows PowerShell virtual directory, we recommend that you only do so at the request of Microsoft Customer Service and Support.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -84,7 +84,7 @@ Accept wildcard characters: False
 
 The BasicAuthentication parameter specifies whether Basic authentication is enabled on the virtual directory. Valid values are:
 
-- $true: Basic authentication is enabled. This is the default value.
+- $true: Basic authentication is enabled. This value is the default.
 - $false: Basic authentication is disabled.
 
 ```yaml
@@ -166,7 +166,7 @@ The ExtendedProtectionFlags parameter specifies custom settings for Extended Pro
 - AllowDotlessSPN: Required if you want to use Service Principal Name (SPN) values that don't contain FQDNs (for example, HTTP/ContosoMail instead of HTTP/mail.contoso.com). You specify SPNs with the ExtendedProtectionSPNList parameter. This setting makes Extended Protection for Authentication less secure because dotless certificates aren't unique, so it isn't possible to ensure that the client-to-proxy connection was established over a secure channel.
 - NoServiceNameCheck: The SPN list isn't checked to validate a channel binding token. This setting makes Extended Protection for Authentication less secure. We generally don't recommend this setting.
 - Proxy: A proxy server is responsible for terminating the SSL channel. To use this setting, you need to register an SPN by using the ExtendedProtectionSPNList parameter.
-- ProxyCoHosting: HTTP and HTTPS traffic may be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server.
+- ProxyCoHosting: HTTP and HTTPS traffic might be accessing the virtual directory, and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server.
 
 ```yaml
 Type: MultiValuedProperty
@@ -186,7 +186,7 @@ Accept wildcard characters: False
 
 The ExtendedProtectionSPNList parameter specifies a list of valid Service Principal Names (SPNs) if you're using Extended Protection for Authentication on the virtual directory. Valid values are:
 
-- $null: This is the default value.
+- $null: This value is the default.
 - Single SPN or comma delimited list of valid SPNs: The SPN value format is `Protocol\FQDN`. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter.
 
 ```yaml
@@ -207,8 +207,8 @@ Accept wildcard characters: False
 
 The ExtendedProtectionTokenChecking parameter defines how you want to use Extended Protection for Authentication on the virtual directory. Extended Protection for Authentication isn't enabled by default. Valid values are:
 
-- None: Extended Protection for Authentication isn't be used on the virtual directory. This is the default value.
-- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication will work, but may not be as secure as connections that use Extended Protection for Authentication.
+- None: Extended Protection for Authentication isn't be used on the virtual directory. This value is the default.
+- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication work, but might not be as secure as connections that use Extended Protection for Authentication.
 - Require: Extended Protection for Authentication is used for all connections between clients and the virtual directory. If either the client or server doesn't support it, the connection will fail. If you use this value, you also need to set an SPN value for the ExtendedProtectionSPNList parameter.
 
 **Note**: If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter.
@@ -303,7 +303,7 @@ Accept wildcard characters: False
 
 The WindowsAuthentication parameter specifies whether Integrated Windows authentication is enabled on the virtual directory. Valid values are:
 
-- $true: Integrated Windows authentication is enabled. This is the default value.
+- $true: Integrated Windows authentication is enabled. This value is the default.
 - $false: Integrated Windows authentication is disabled.
 
 ```yaml
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ProtectionAlert.md b/exchange/exchange-ps/ExchangePowerShell/Set-ProtectionAlert.md
index 5ed5a8d14e..7df4ae0f1e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ProtectionAlert.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ProtectionAlert.md
@@ -103,8 +103,8 @@ Accept wildcard characters: False
 The AggregationType parameter specifies the how the alert policy triggers alerts for multiple occurrences of monitored activity. Valid values are:
 
 - None: Alerts are triggered for every occurrence of the activity.
-- SimpleAggregation: Alerts are triggered based on the volume of activity in a given time window (the values of the Threshold and TimeWindow parameters). This is the default value.
-- AnomalousAggregation: Alerts are triggered when the volume of activity reaches unusual levels (greatly exceeds the normal baseline that's established for the activity). Note that it can take up to 7 days for Microsoft 365 to establish the baseline. During the baseline calculation period, no alerts are generated for the activity.
+- SimpleAggregation: Alerts are triggered based on the volume of activity in a given time window (the values of the Threshold and TimeWindow parameters). This value is the default.
+- AnomalousAggregation: Alerts are triggered when the volume of activity reaches unusual levels (greatly exceeds the normal baseline that's established for the activity). It can take up to 7 days for Microsoft 365 to establish the baseline. During the baseline calculation period, no alerts are generated for the activity.
 
 ```yaml
 Type: AlertAggregationType
@@ -254,7 +254,7 @@ Accept wildcard characters: False
 The Disabled parameter enables or disables the alert policy. Valid values are:
 
 - $true: The alert policy is disabled.
-- $false: The alert policy is enabled. This is the default value.
+- $false: The alert policy is enabled. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -403,7 +403,7 @@ Accept wildcard characters: False
 The NotifyUserOnFilterMatch parameter specifies whether to trigger an alert for a single event when the alert policy is configured for aggregated activity. Valid values are:
 
 - $true: Even though the alert is configured for aggregated activity, a notification is triggered during a match for the activity (basically, an early warning).
-- $false: Alerts are triggered according to the specified aggregation type. This is the default value.
+- $false: Alerts are triggered according to the specified aggregation type. This value is the default.
 
 You can't use this parameter when the AggregationType parameter value is None (alerts are triggered for every occurrence of the activity).
 
@@ -443,10 +443,10 @@ Accept wildcard characters: False
 
 > Applicable: Security & Compliance
 
-The NotifyUserThrottleThreshold parameter specifies the maximum number of notifications for the alert policy within the time period specified by the NotifyUserThrottleWindow parameter. Once the maximum number of notifications has been reached in the time period, no more notifications are sent for the alert. Valid values are:
+The NotifyUserThrottleThreshold parameter specifies the maximum number of notifications for the alert policy within the time period specified by the NotifyUserThrottleWindow parameter. Once the maximum number of notifications is reached in the time period, no more notifications are sent for the alert. Valid values are:
 
 - An integer.
-- The value $null. This is the default value (no maximum number of notifications for an alert).
+- The value $null. This value is the default (no maximum number of notifications for an alert).
 
 ```yaml
 Type: Int32
@@ -467,7 +467,7 @@ Accept wildcard characters: False
 The NotifyUserThrottleWindow parameter specifies the time interval in minutes that's used by the NotifyUserThrottleThreshold parameter. Valid values are:
 
 - An integer.
-- The value $null. This is the default value (no interval for notification throttling).
+- The value $null. This value is the default (no interval for notification throttling).
 
 ```yaml
 Type: Int32
@@ -563,7 +563,7 @@ Accept wildcard characters: False
 
 The Severity parameter specifies the severity of the detection. Valid values are:
 
-- Low (This is the default value)
+- Low (default value)
 - Medium
 - High
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-PublicFolder.md b/exchange/exchange-ps/ExchangePowerShell/Set-PublicFolder.md
index 1e20ef8860..1482cb835f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-PublicFolder.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-PublicFolder.md
@@ -13,7 +13,7 @@ title: Set-PublicFolder
 # Set-PublicFolder
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-PublicFolder cmdlet to set the attributes of public folders.
 
@@ -52,7 +52,7 @@ Set-PublicFolder [-Identity] <PublicFolderIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -232,7 +232,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The valid input range for this parameter is from 1 through 2TB.
 
@@ -322,7 +322,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The valid input range for this parameter is from 1 through 2GB.
 
@@ -437,7 +437,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The valid input range for this parameter is from 1 through 2TB.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-PublicFolderDatabase.md b/exchange/exchange-ps/ExchangePowerShell/Set-PublicFolderDatabase.md
index fd89adf4ff..a1407b777f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-PublicFolderDatabase.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-PublicFolderDatabase.md
@@ -49,7 +49,7 @@ Set-PublicFolderDatabase [-Identity] <DatabaseIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -72,7 +72,7 @@ This example sets the database maintenance schedule on PFDB01 to run daily from
 Set-PublicFolderDatabase -RetainDeletedItemsUntilBackup $true -Identity 'PFDB01'
 ```
 
-This example prevents the deleted items in the public folder database PFDB01 from being permanently deleted until after the database has been backed up.
+This example prevents the deleted items in the public folder database PFDB01 from being permanently deleted until after the database is backed up.
 
 ## PARAMETERS
 
@@ -433,7 +433,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010
 
-The ReplicationMessageSize parameter specifies the size of replication messages. Small items may be aggregated into a single replication message that can be as large as this setting, but items larger than this setting are replicated with messages larger than this size.
+The ReplicationMessageSize parameter specifies the size of replication messages. Small items might be aggregated into a single replication message that can be as large as this setting, but items larger than this setting are replicated with messages larger than this size.
 
 A valid value is a number up to 2 gigabytes (2147482624 bytes). The default value is 300 kilobytes (307200 bytes).
 
@@ -444,7 +444,7 @@ When you enter a value, qualify the value with one of the following units:
 - MB (megabytes)
 - GB (gigabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 ```yaml
 Type: ByteQuantifiedSize
@@ -462,7 +462,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010
 
-The ReplicationPeriod parameter specifies the interval at which replication of public folders or content updates may occur.
+The ReplicationPeriod parameter specifies the interval at which replication of public folders or content updates might occur.
 
 ```yaml
 Type: UInt32
@@ -480,7 +480,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010
 
-The ReplicationSchedule parameter specifies the time intervals during which replication of public folders or contents may occur.
+The ReplicationSchedule parameter specifies the time intervals during which replication of public folders or contents might occur.
 
 The syntax for this parameter is: `StartDay.Hour:Minute [AM | PM]-EndDay.Hour:Minute [AM | PM]`.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-PublicFolderMigrationRequest.md b/exchange/exchange-ps/ExchangePowerShell/Set-PublicFolderMigrationRequest.md
index d90b6c55ed..a2c4eedfb8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-PublicFolderMigrationRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-PublicFolderMigrationRequest.md
@@ -56,7 +56,7 @@ Set-PublicFolderMigrationRequest [-Identity] <PublicFolderMigrationRequestIdPara
 ## DESCRIPTION
 You can pipe output of Get-PublicFolderMigrationRequestStatistics, Get-PublicFolderMigrationRequest, or Get-PublicFolder to this cmdlet.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -277,7 +277,7 @@ Accept wildcard characters: False
 The PreventCompletion parameter specifies whether to run the migration request, but not allow it to complete. Valid values are:
 
 - $true: The migration request is run, but is not allowed to complete. To complete the migration request, set this parameter to $false before you run the Resume-PublicFolderMigrationRequest cmdlet.
-- $false: The migration request is run and allowed to complete. This is the default value.
+- $false: The migration request is run and allowed to complete. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -300,7 +300,7 @@ The Priority parameter specifies the order in which the request should be proces
 - Lowest
 - Lower
 - Low
-- Normal: This is the default value.
+- Normal: This value is the default.
 - High
 - Higher
 - Highest
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-PublicFolderMoveRequest.md b/exchange/exchange-ps/ExchangePowerShell/Set-PublicFolderMoveRequest.md
index 9926e55de1..d1e95ab4b5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-PublicFolderMoveRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-PublicFolderMoveRequest.md
@@ -15,7 +15,7 @@ title: Set-PublicFolderMoveRequest
 ## SYNOPSIS
 This cmdlet is available only in on-premises Exchange.
 
-Use the Set-PublicFolderMoveRequest cmdlet to change a public folder move request after the move request has been created. You can use the Set-PublicFolderMoveRequest cmdlet to recover from a failed move request.
+Use the Set-PublicFolderMoveRequest cmdlet to change a public folder move request after the move request is created. You can use the Set-PublicFolderMoveRequest cmdlet to recover from a failed move request.
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
@@ -40,7 +40,7 @@ Set-PublicFolderMoveRequest [-Identity] <PublicFolderMoveRequestIdParameter>
 ## DESCRIPTION
 You can pipeline the Set-PublicFolderMoveRequest cmdlet from the Get-PublicFolderMoveRequestStatistics or Get-PublicFolderMoveRequest cmdlet.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -222,7 +222,7 @@ The Priority parameter specifies the order in which the request should be proces
 - Lowest
 - Lower
 - Low
-- Normal: This is the default value.
+- Normal: This value is the default.
 - High
 - Higher
 - Highest
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-QuarantinePermissions.md b/exchange/exchange-ps/ExchangePowerShell/Set-QuarantinePermissions.md
index 3a2ffa3548..bc66a72143 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-QuarantinePermissions.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-QuarantinePermissions.md
@@ -39,7 +39,7 @@ Set-QuarantinePermissions -QuarantinePermissionsObject <QuarantinePermissions>
 ## DESCRIPTION
 To see the current value of the permissions object that you want to modify, run the variable name as a command. For example, run the command `$Perms` to see the quarantine policy permissions stored in the `$Perms` variable.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -79,7 +79,7 @@ Accept wildcard characters: False
 The PermissionToBlockSender parameter specifies whether users are allowed to add the quarantined message sender to their Safe Senders list. Valid values are:
 
 - $true: Allow sender is available for affected messages in quarantine.
-- $false: Allow sender isn't available for affected messages in quarantine. This is the default value.
+- $false: Allow sender isn't available for affected messages in quarantine. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -100,7 +100,7 @@ Accept wildcard characters: False
 The PermissionToBlockSender parameter specifies whether users are allowed to add the quarantined message sender to their Blocked Senders list. Valid values are:
 
 - $true: Block sender is available in quarantine notifications for affected messages, and Block sender is available for affected messages in quarantine.
-- $false: Block sender isn't available in quarantine notifications for affected messages, and Block sender isn't available for affected messages in quarantine. This is the default value.
+- $false: Block sender isn't available in quarantine notifications for affected messages, and Block sender isn't available for affected messages in quarantine. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -121,7 +121,7 @@ Accept wildcard characters: False
 The PermissionToDelete parameter specifies whether users are allowed to delete messages from quarantine. Valid values are:
 
 - $true: Delete messages and Delete from quarantine are available for affected messages in quarantine.
-- $false: Delete messages and Delete from quarantine aren't available for affected messages in quarantine. This is the default value.
+- $false: Delete messages and Delete from quarantine aren't available for affected messages in quarantine. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -142,7 +142,7 @@ Accept wildcard characters: False
 The PermissionToDownload parameter specifies whether users are allowed to download messages from quarantine. Valid values are:
 
 - $true: The permission is enabled.
-- $false: The permission is disabled. This is the default value.
+- $false: The permission is disabled. This value is the default.
 
 Currently, this value has no effect on the available actions in quarantine notifications or quarantine for affected messages. End-users can't download quarantined messages.
 
@@ -165,7 +165,7 @@ Accept wildcard characters: False
 The PermissionToPreview parameter specifies whether users are allowed to preview quarantined messages. Valid values are:
 
 - $true: Preview message is available for affected messages in quarantine.
-- $false: Preview message isn't available for affected messages in quarantine. This is the default value.
+- $false: Preview message isn't available for affected messages in quarantine. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -232,7 +232,7 @@ Accept wildcard characters: False
 The PermissionToViewHeader parameter specifies whether users are allowed to view the message headers of quarantined messages. Valid values are:
 
 - $true: The permission is enabled.
-- $false: The permission is disabled. This is the default value.
+- $false: The permission is disabled. This value is the default.
 
 Currently, this value has no effect on available actions in quarantine notifications or quarantine for affected messages. View message header is always available for affected messages in quarantine.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-QuarantinePolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-QuarantinePolicy.md
index 20659f9134..a80cbc375e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-QuarantinePolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-QuarantinePolicy.md
@@ -52,7 +52,7 @@ Set-QuarantinePolicy [-Identity] <QuarantineTagIdParameter>
 ## DESCRIPTION
 You can't modify the built-in quarantine policies named AdminOnlyAccessPolicy, DefaultFullAccessPolicy, or DefaultFullAccessWithNotificationPolicy.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -398,7 +398,7 @@ Accept wildcard characters: False
 The ESNEnabled parameter specifies whether to enable quarantine notifications (formerly known as end-user spam notifications) for the policy. Valid values are:
 
 - $true: Quarantine notifications are enabled.
-- $false: Quarantine notifications are disabled. User can only access quarantined messages in quarantine, not in email notifications. This is the default value.
+- $false: Quarantine notifications are disabled. User can only access quarantined messages in quarantine, not in email notifications. This value is the default.
 
 **Note**: If the value of this parameter is $true and the value of the EndUserQuarantinePermissionsValue parameter is 0 (No access where all permissions are turned off), users can view their messages in quarantine, but the only available action for the messages is **View message header**.
 
@@ -439,7 +439,7 @@ Accept wildcard characters: False
 The IncludeMessagesFromBlockedSenderAddress parameter specifies whether to send quarantine notifications for quarantined messages from blocked sender addresses. Valid values are:
 
 - $true: Recipients get quarantine notifications for affected messages from blocked senders.
-- $false: Recipients don't get quarantine notifications for affected messages from blocked senders. This is the default value.
+- $false: Recipients don't get quarantine notifications for affected messages from blocked senders. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -536,7 +536,7 @@ Accept wildcard characters: False
 The OrganizationBrandingEnabled parameter enables or disables organization branding in the end-user quarantine notification messages. Valid values are:
 
 - $true: Organization branding is enabled. The default Microsoft logo that's used in quarantine notifications is replaced by your custom logo. Before you do this, you need to follow the instructions in [Customize the Microsoft 365 theme for your organization](https://learn.microsoft.com/microsoft-365/admin/setup/customize-your-organization-theme) to upload your custom logo.
-- $false: Organization branding is disabled. The default Microsoft logo is used in quarantine notifications. This is the default value.
+- $false: Organization branding is disabled. The default Microsoft logo is used in quarantine notifications. This value is the default.
 
 This setting is available only in the built-in quarantine policy named DefaultGlobalTag that controls global settings. To access this quarantine policy, start your command with the following syntax: `Get-QuarantinePolicy -QuarantinePolicyType GlobalQuarantinePolicy | Set-QuarantinePolicy ...`.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-RMSTemplate.md b/exchange/exchange-ps/ExchangePowerShell/Set-RMSTemplate.md
index 26d5d4ef44..27c19d4d2b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-RMSTemplate.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-RMSTemplate.md
@@ -16,7 +16,7 @@ title: Set-RMSTemplate
 This cmdlet is available only in the cloud-based service.
 
 > [!NOTE]
-> This cmdlet has been deprecated. If you use AD RMS with Exchange Online, you need to migrate to Azure Information Protection before you can use message encryption. For more information, see [Verify that Azure Rights Management is active](https://learn.microsoft.com/purview/set-up-new-message-encryption-capabilities#verify-that-azure-rights-management-is-active).
+> This cmdlet is deprecated. If you use AD RMS with Exchange Online, you need to migrate to Azure Information Protection before you can use message encryption. For more information, see [Verify that Azure Rights Management is active](https://learn.microsoft.com/purview/set-up-new-message-encryption-capabilities#verify-that-azure-rights-management-is-active).
 
 Use the Set-RMSTemplate cmdlet to modify the properties of an existing Active Directory Rights Management Services (AD RMS) template in your organization.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ReceiveConnector.md b/exchange/exchange-ps/ExchangePowerShell/Set-ReceiveConnector.md
index 4e14c8daab..c84552f4b2 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ReceiveConnector.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ReceiveConnector.md
@@ -83,7 +83,7 @@ Set-ReceiveConnector [-Identity] <ReceiveConnectorIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -130,7 +130,7 @@ Accept wildcard characters: False
 The AdvertiseClientSettings parameter specifies whether the SMTP server name, port number, and authentication settings for the Receive connector are displayed to users in the options of Outlook on the web. Valid values are:
 
 - $true: The SMTP values are displayed in Outlook on the web. Typically, you would only use this setting for a Receive connector with the usage type Client (authenticated SMTP connections on TCP port 587 for POP3 and IMAP4 clients).
-- $false: The SMTP values are displayed in Outlook on the web. This is the default value.
+- $false: The SMTP values are displayed in Outlook on the web. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -182,7 +182,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2016, Exchange Server 2019
 
-The AuthTarpitInterval parameter specifies the period of time to delay responses to failed authentication attempts from remote servers that may be abusing the connection. The default value is 5 seconds.
+The AuthTarpitInterval parameter specifies the period of time to delay responses to failed authentication attempts from remote servers that might be abusing the connection. The default value is 5 seconds.
 
 To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes and ss = seconds.
 
@@ -231,7 +231,7 @@ Accept wildcard characters: False
 The BareLinefeedRejectionEnabled parameter specifies whether this Receive connector rejects messages that contain line feed (LF) characters without immediately preceding carriage return characters (CR) in the SMTP DATA stream. This condition is known as bare line feeds. Valid values are:
 
 - $true: Messages that contain bare line feeds are rejected.
-- $false: Messages that contain bare line feeds aren't rejected. This is the default value.
+- $false: Messages that contain bare line feeds aren't rejected. This value is the default.
 
 Although message that contain bare line feeds might be delivered successfully, these messages don't follow SMTP protocol standards and might cause problems on messaging servers.
 
@@ -253,7 +253,7 @@ Accept wildcard characters: False
 
 The BinaryMimeEnabled parameter specifies whether the BINARYMIME Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are:
 
-- $true: BINARYMIME is enabled and is advertised in the EHLO response. This setting requires that the ChunkingEnabled parameter is also set to the value $true. This is the default value.
+- $true: BINARYMIME is enabled and is advertised in the EHLO response. This setting requires that the ChunkingEnabled parameter is also set to the value $true. This value is the default.
 - $false: BINARYMIME is disabled and isn't advertised in the EHLO response.
 
 The binary MIME extension is defined in RFC 3030.
@@ -301,7 +301,7 @@ Accept wildcard characters: False
 
 The ChunkingEnabled parameter specifies whether the CHUNKING Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are:
 
-- $true: CHUNKING is enabled and is advertised in the EHLO response. This is the default value.
+- $true: CHUNKING is enabled and is advertised in the EHLO response. This value is the default.
 - $false: CHUNKING is disabled and isn't advertised in the EHLO response.
 
 Chunking is defined in RFC 3030.
@@ -443,7 +443,7 @@ Accept wildcard characters: False
 
 The DeliveryStatusNotificationEnabled parameter specifies whether the DSN (delivery status notification) Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are:
 
-- $true: DSN is enabled and is advertised in the EHLO response. This is the default value.
+- $true: DSN is enabled and is advertised in the EHLO response. This value is the default.
 - $false: DSN is disabled and isn't advertised in the EHLO response.
 
 Delivery status notifications are defined in RFC 3461.
@@ -489,7 +489,7 @@ The DomainSecureEnabled parameter specifies whether to enable or disable mutual
 - $true: Mutual TLS authentication is enabled.
 - $false: Mutual TLS authentication is disabled.
 
-Note that setting this parameter to the value $true is only part of the requirements for enabling mutual TLS authentication:
+Setting this parameter to the value $true is only part of the requirements for enabling mutual TLS authentication:
 
 - The AuthMechanism parameter must contain the value Tls, and can't contain the value ExternalAuthoritative.
 - The domain that's used for mutual TLS authentication must be configured in the following locations:
@@ -515,7 +515,7 @@ Accept wildcard characters: False
 
 The EightBitMimeEnabled parameter specifies whether the 8BITMIME Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are:
 
-- $true: 8BITMIME is enabled and is advertised in the EHLO response. This is the default value.
+- $true: 8BITMIME is enabled and is advertised in the EHLO response. This value is the default.
 - $false: 8BITMIME is disabled and isn't advertised in the EHLO response.
 
 8-bit data transmission is defined in RFC 6152.
@@ -561,7 +561,7 @@ Accept wildcard characters: False
 
 The Enabled parameter specifies whether to enable or disable the Receive connector. Valid values are:
 
-- $true: The Receive connector is enabled. This is the default value.
+- $true: The Receive connector is enabled. This value is the default.
 - $false: The Receive connector is disabled.
 
 ```yaml
@@ -582,7 +582,7 @@ Accept wildcard characters: False
 
 The EnhancedStatusCodesEnabled parameter specifies whether the ENHANCEDSTATUSCODES Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are:
 
-- $true: ENHANCEDSTATUSCODES is enabled and is advertised in the EHLO response. This is the default value.
+- $true: ENHANCEDSTATUSCODES is enabled and is advertised in the EHLO response. This value is the default.
 - $false: ENHANCEDSTATUSCODES is disabled and isn't advertised in the EHLO response.
 
 Enhanced status codes are defined in RFC 2034.
@@ -605,9 +605,9 @@ Accept wildcard characters: False
 
 The ExtendedProtectionPolicy parameter specifies how you want to use Extended Protection for Authentication on the Receive connector.Valid values are:
 
-- None: Extended Protection for Authentication won't be used. This is the default value.
-- Allow: Extended Protection for Authentication will be used only if the connecting host supports it. Otherwise, the connections will be established without Extended Protection for Authentication.
-- Require: Extended Protection for Authentication will be required for all incoming connections to this Receive connector. If the connecting host doesn't support Extended Protection for Authentication, the connection will be rejected.
+- None: Extended Protection for Authentication aren't used. This value is the default.
+- Allow: Extended Protection for Authentication are used only if the connecting host supports it. Otherwise, the connections are established without Extended Protection for Authentication.
+- Require: Extended Protection for Authentication is required for all incoming connections to this Receive connector. If the connecting host doesn't support Extended Protection for Authentication, the connection is rejected.
 
 Extended Protection for Authentication enhances the protection and handling of credentials when authenticating network connections using Integrated Windows authentication. Integrated Windows authentication is also known as NTLM. We strongly recommend that you use Extended Protection for Authentication if you are using Integrated Windows authentication.
 
@@ -657,7 +657,7 @@ Accept wildcard characters: False
 The LongAddressesEnabled parameter specifies whether the Receive connector accepts long X.400 email addresses. The X.400 email addresses are encapsulated in SMTP email addresses by using the Internet Mail Connector Encapsulated Address (IMCEA) encapsulation method. Valid values are:
 
 - $true: X.400 email addresses can be up to 1,860 characters long after IMCEA encapsulation.
-- $false: The maximum length of a complete SMTP email address is 571 characters. This is the default value.
+- $false: The maximum length of a complete SMTP email address is 571 characters. This value is the default.
 
 When you set this parameter to the value $true the following changes are made to the Receive connector:
 
@@ -685,7 +685,7 @@ Accept wildcard characters: False
 
 This parameter isn't used by Exchange Server 2016. It's used only by Exchange 2010 servers in coexistence environments.
 
-The MaxAcknowledgementDelay parameter specifies the period the transport server delays acknowledgement when receiving messages from a host that doesn't support shadow redundancy. When receiving messages from a host that doesn't support shadow redundancy, a Microsoft Exchange Server 2010 transport server delays issuing an acknowledgement until it verifies that the message has been successfully delivered to all recipients. However, if it takes too long to verify successful delivery, the transport server times out and issues an acknowledgement anyway. The default value is 30 seconds.
+The MaxAcknowledgementDelay parameter specifies the period the transport server delays acknowledgement when receiving messages from a host that doesn't support shadow redundancy. When receiving messages from a host that doesn't support shadow redundancy, a Microsoft Exchange Server 2010 transport server delays issuing an acknowledgement until it verifies that the message is successfully delivered to all recipients. However, if it takes too long to verify successful delivery, the transport server times out and issues an acknowledgement anyway. The default value is 30 seconds.
 
 To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds.
 
@@ -714,7 +714,7 @@ When you enter a value, qualify the value with one of the following units:
 - MB (megabytes)
 - GB (gigabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 A valid value is from 1 to 2147483647 bytes.
 
@@ -872,7 +872,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 A valid value for this parameter is from 65536 to 2147483647 bytes.
 
@@ -1004,7 +1004,7 @@ Accept wildcard characters: False
 The OrarEnabled parameter enables or disables Originator Requested Alternate Recipient (ORAR) on the Receive connector. Valid values are:
 
 - $true: ORAR is enabled and is advertised in the XORAR keyword in the EHLO response. The actual ORAR information is transmitted in the RCPT TO SMTP command.
-- $false: ORAR is disabled and is isn't advertised in the EHLO response. This is the default value.
+- $false: ORAR is disabled and is isn't advertised in the EHLO response. This value is the default.
 
 If the email address specified in the ORAR information is a long X.400 email address, you need to set the LongAddressesEnabled parameter to the value $true.
 
@@ -1058,7 +1058,7 @@ Accept wildcard characters: False
 
 The PipeliningEnabled parameter specifies whether the PIPELINING Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are:
 
-- $true: PIPELINING is enabled and is advertised in the EHLO response. This is the default value.
+- $true: PIPELINING is enabled and is advertised in the EHLO response. This value is the default.
 - $false: PIPELINING is disabled and isn't advertised in the EHLO response.
 
 Pipelining is defined in RFC 2920.
@@ -1081,7 +1081,7 @@ Accept wildcard characters: False
 
 The ProtocolLoggingLevel parameter specifies whether to enable or disable protocol logging for the Receive connector. Valid values are:
 
-- None: Protocol logging is disabled on the Receive connector. This is the default value.
+- None: Protocol logging is disabled on the Receive connector. This value is the default.
 - Verbose: Protocol logging is enabled on the Receive connector.
 
 For more information about protocol logging, see [Protocol logging](https://learn.microsoft.com/Exchange/mail-flow/connectors/protocol-logging).
@@ -1105,7 +1105,7 @@ Accept wildcard characters: False
 The RejectReservedSecondLevelRecipientDomains parameter specifies whether to reject connections that contain recipients in reserved second-level domains as specified in RFC 2606 (example.com, example.net, or example.org). Valid value are:
 
 - $true: RCPT TO commands that contain reserved second-level domains are rejected.
-- $false: RCPT TO commands that contain reserved second-level domains aren't rejected. This is the default value.
+- $false: RCPT TO commands that contain reserved second-level domains aren't rejected. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -1126,7 +1126,7 @@ Accept wildcard characters: False
 The RejectReservedTopLevelRecipientDomains parameter specifies whether to reject connections that contain recipients in reserved top-level domains (TLDs) as specified in RFC 2606 (.test, .example, .invalid, or .localhost). Valid value are:
 
 - $true: RCPT TO commands that contain reserved TLDs are rejected.
-- $false: RCPT TO commands that contain reserved TLDs aren't rejected. This is the default value.
+- $false: RCPT TO commands that contain reserved TLDs aren't rejected. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -1147,7 +1147,7 @@ Accept wildcard characters: False
 The RejectSingleLabelRecipientDomains parameter specifies whether to reject connections that contain recipients in single-label domains (for example, chris@contoso instead of chris@contoso.com). Valid values are:
 
 - $true: RCPT TO commands that contain single-label domains are rejected.
-- $false: RCPT TO commands that contain single-label domains aren't rejected. This is the default value.
+- $false: RCPT TO commands that contain single-label domains aren't rejected. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -1200,7 +1200,7 @@ Accept wildcard characters: False
 The RequireEHLODomain parameter specifies whether the client must provide a domain name in the EHLO handshake after the SMTP connection is established. Valid values are:
 
 - $true: The client must provide a domain name in the EHLO handshake. If it doesn't, the SMTP connection is closed.
-- $false: The client isn't required to provide a domain name in the EHLO handshake. This is the default value.
+- $false: The client isn't required to provide a domain name in the EHLO handshake. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -1221,7 +1221,7 @@ Accept wildcard characters: False
 The RequireTLS parameter specifies whether to require TLS transmission for inbound messages on the Receive connector. Valid values are:
 
 - $true: Inbound messages on the Receive connector require TLS transmission.
-- $false: Inbound messages on the Receive connector don't require TLS transmission. This is the default value.
+- $false: Inbound messages on the Receive connector don't require TLS transmission. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -1259,7 +1259,7 @@ Accept wildcard characters: False
 
 The SizeEnabled parameter specifies how the SIZE Extended SMTP extension is used on the Receive connector. Valid values are:
 
-- Enabled: SIZE is enabled and is advertised in the EHLO response along with the value of the MaxMessageSize parameter. If the size of the inbound message exceeds the specified value, the Receive connector closes the connection with an error code. This is the default value.
+- Enabled: SIZE is enabled and is advertised in the EHLO response along with the value of the MaxMessageSize parameter. If the size of the inbound message exceeds the specified value, the Receive connector closes the connection with an error code. This value is the default.
 - Disabled: SIZE is disabled and isn't advertised in the EHLO response.
 - EnabledwithoutValue: SIZE is enabled and is advertised in the EHLO response, but the value of the MaxMessageSize parameter isn't disclosed in the EHLO response. This setting allows messages to bypass message size checks for authenticated connections between Mailbox servers.
 
@@ -1302,7 +1302,7 @@ Accept wildcard characters: False
 The SuppressXAnonymousTls parameter specifies whether the X-ANONYMOUSTLS Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are:
 
 - $true: X-ANONYMOUSTLS is disabled and isn't advertised in the EHLO response. This setting also requires that you set the UseDownGradedExchangeServerAuth parameter to the value $true on the Set-TransportService cmdlet on the server.
-- $false: X-ANONYMOUSTLS is enabled and is advertised in the EHLO response. This is the default value.
+- $false: X-ANONYMOUSTLS is enabled and is advertised in the EHLO response. This value is the default.
 
 The X-ANONYMOUSTLS extension is important when the AuthMechanism parameter contains the value ExchangeServer.
 
@@ -1322,7 +1322,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-The TarpitInterval parameter specifies the period of time to delay an SMTP response to a remote server that may be abusing the connection. The default value is 00:00:05 (5 seconds).
+The TarpitInterval parameter specifies the period of time to delay an SMTP response to a remote server that might be abusing the connection. The default value is 00:00:05 (5 seconds).
 
 To specify a value, enter it as a time span: dd.hh:mm:ss where dd = days, hh = hours, mm = minutes, and ss = seconds.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-RecipientFilterConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-RecipientFilterConfig.md
index 74a5aae2c5..a2b2f7d24f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-RecipientFilterConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-RecipientFilterConfig.md
@@ -35,7 +35,7 @@ Set-RecipientFilterConfig [-BlockedRecipients <MultiValuedProperty>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-RecordReviewNotificationTemplateConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-RecordReviewNotificationTemplateConfig.md
index 862f6a7ab6..fedde7df9c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-RecordReviewNotificationTemplateConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-RecordReviewNotificationTemplateConfig.md
@@ -49,7 +49,7 @@ This example configures customized review notification text and review reminder
 The IsCustomizedNotificationTemplate switch specifies whether to use a customized review notification instead of the system default notification. Valid values are:
 
 - $true: Use a customized review notification. You specify the notification text using the CustomizedNotificationDataString parameter.
-- $false: Use the default system notification. This is the default value.
+- $false: Use the default system notification. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -70,7 +70,7 @@ Accept wildcard characters: False
 The IsCustomizedReminderTemplate switch specifies whether to use a customized review reminder instead of the system default reminder:
 
 - $true: Use a customized review reminder. You specify the reminder text using the CustomizedReminderDataString parameter.
-- $false: Use the default system reminder. This is the default value.
+- $false: Use the default system reminder. This value is the default.
 
 ```yaml
 Type: Boolean
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-RegulatoryComplianceUI.md b/exchange/exchange-ps/ExchangePowerShell/Set-RegulatoryComplianceUI.md
index 4379121dc8..1450683bf3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-RegulatoryComplianceUI.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-RegulatoryComplianceUI.md
@@ -47,7 +47,7 @@ The Enabled parameter specifies whether to show or hide the UI option in retenti
 
 $true: The option to mark content as a regulatory record is visible in the UI for retention label settings.
 
-$false: The option to mark content as a regulatory record is not visible in the UI for retention label settings. This is the default value.
+$false: The option to mark content as a regulatory record is not visible in the UI for retention label settings. This value is the default.
 
 ```yaml
 Type: Boolean
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-RemoteDomain.md b/exchange/exchange-ps/ExchangePowerShell/Set-RemoteDomain.md
index 278351fb3b..ed3e25485e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-RemoteDomain.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-RemoteDomain.md
@@ -13,7 +13,7 @@ title: Set-RemoteDomain
 # Set-RemoteDomain
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-RemoteDomain cmdlet to configure a managed connection for a remote domain.
 
@@ -57,7 +57,7 @@ Set-RemoteDomain [-Identity] <RemoteDomainIdParameter>
 ## DESCRIPTION
 When you set a remote domain, you can control mail flow with more precision, specify message formatting and policy and specify acceptable character sets for messages sent to or received from the remote domain.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -109,7 +109,7 @@ Accept wildcard characters: False
 
 The AllowedOOFType parameter specifies the type of automatic replies or out-of-office (also known as OOF) notifications than can be sent to recipients in the remote domain. Valid values are:
 
-- External: Only automatic replies that are designated as external are sent to recipients in the remote domain. This is the default value.
+- External: Only automatic replies that are designated as external are sent to recipients in the remote domain. This value is the default.
 - ExternalLegacy: Only external automatic replies or automatic replies that aren't designated as internal or external are sent to recipients in the remote domain.
 - InternalLegacy: Only internal automatic replies or automatic replies that aren't designated as internal or external are sent to recipients in the remote domain.
 - None: No automatic replies are sent to recipients in the remote domain.
@@ -137,8 +137,8 @@ Accept wildcard characters: False
 
 The AutoForwardEnabled parameter specifies whether to allow messages that are auto-forwarded by client email programs in your organization. Valid values are:
 
-- $true: Auto-forwarded messages are delivered to recipients in the remote domain. This is the default value for new remote domains that you create and the built-in remote domain named Default in Exchange Online.
-- $false: Auto-forwarded messages aren't delivered to recipients in the remote domain. This is the default value for the built-in remote domain named Default in on-premises Exchange.
+- $true: Auto-forwarded messages are delivered to recipients in the remote domain. This value is the default for new remote domains that you create and the built-in remote domain named Default in Exchange Online.
+- $false: Auto-forwarded messages aren't delivered to recipients in the remote domain. This value is the default for the built-in remote domain named Default in on-premises Exchange.
 
 ```yaml
 Type: Boolean
@@ -158,8 +158,8 @@ Accept wildcard characters: False
 
 The AutoReplyEnabled parameter specifies whether to allow messages that are automatic replies from client email programs in your organization (for example, automatic reply messages that are generated by rules in Outlook). Valid values are:
 
-- $true: Automatic replies are delivered to recipients in the remote domain. This is the default value for new remote domains that you create and the built-in remote domain named Default in Exchange Online.
-- $false: Automatic replies aren't delivered to recipients in the remote domain. This is the default value for the built-in remote domain named Default in on-premises Exchange.
+- $true: Automatic replies are delivered to recipients in the remote domain. This value is the default for new remote domains that you create and the built-in remote domain named Default in Exchange Online.
+- $false: Automatic replies aren't delivered to recipients in the remote domain. This value is the default for the built-in remote domain named Default in on-premises Exchange.
 
 ```yaml
 Type: Boolean
@@ -186,7 +186,7 @@ The ByteEncoderTypeFor7BitCharsets parameter specifies the 7-bit transfer encodi
 - UseBase64HtmlDetectTextPlain: Use Base64 encoding for HTML and for plain text, unless line wrapping is enabled in plain text. If line wrapping is enabled in plain text, use Base64 encoding for HTML, and use 7-bit encoding for plain text.
 - UseQPHtml7BitTextPlain: Always use QP encoding for HTML. Always use 7-bit encoding for plain text.
 - UseBase64Html7BitTextPlain: Always use Base64 encoding for HTML. Always use 7-bit encoding for plain text.
-- Undefined: Always use QP encoding for HTML and plain text. This is the default value.
+- Undefined: Always use QP encoding for HTML and plain text. This value is the default.
 
 ```yaml
 Type: ByteEncoderTypeFor7BitCharsetsEnum
@@ -251,7 +251,7 @@ Accept wildcard characters: False
 
 The ContentType parameter specifies the outbound message content type and formatting. Valid values are:
 
-- MimeHtmlText: Converts messages to MIME messages that use HTML formatting, unless the original message is a text message. If the original message is a text message, the outbound message is a MIME message that uses text formatting. This is the default value.
+- MimeHtmlText: Converts messages to MIME messages that use HTML formatting, unless the original message is a text message. If the original message is a text message, the outbound message is a MIME message that uses text formatting. This value is the default.
 - MimeText: Converts all messages to MIME messages that use text formatting.
 - MimeHtml: Converts all messages to MIME messages that use HTML formatting.
 
@@ -273,7 +273,7 @@ Accept wildcard characters: False
 
 The DeliveryReportEnabled parameter specifies whether to allow delivery reports from client software in your organization to recipients in the remote domain. Valid values are:
 
-- $true: Delivery reports are delivered to recipients in the remote domain. This is the default value.
+- $true: Delivery reports are delivered to recipients in the remote domain. This value is the default.
 - $false: Delivery reports aren't delivered to recipients in the remote domain.
 
 ```yaml
@@ -296,7 +296,7 @@ Accept wildcard characters: False
 
 The DisplaySenderName parameter specifies whether to show the sender's Display Name in the From email address for messages sent to recipients in the remote domain. Valid values are:
 
-- $true: Sender names are displayed in messages sent to recipients in the remote domain. This is the default value.
+- $true: Sender names are displayed in messages sent to recipients in the remote domain. This value is the default.
 - $false. Sender names aren't displayed in messages sent to recipients in the remote domain.
 
 ```yaml
@@ -342,7 +342,7 @@ This parameter is available only in Exchange Server 2010.
 The IsCoexistenceDomain parameter specifies whether this remote domain is used to represent your Exchange Online organization. Valid values are:
 
 - $true: The remote domain represents your Exchange Online organization.
-- $false: The remote domain doesn't represent your Exchange Online organization. This is the default value.
+- $false: The remote domain doesn't represent your Exchange Online organization. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -363,7 +363,7 @@ Accept wildcard characters: False
 The IsInternal parameter specifies whether the recipients in the remote domain are considered to be internal recipients. Valid values are:
 
 - $true: All transport components (for example, transport rules) treat recipients in the remote domain as internal recipients. Typically, you use this value in cross-forest deployments.
-- $false: Recipients in the remote domain are treated as external recipients. This is the default value.
+- $false: Recipients in the remote domain are treated as external recipients. This value is the default.
 
 The value of this parameter is affected by the value of the AllowedOOFType parameter, and vice-versa:
 
@@ -406,7 +406,7 @@ Accept wildcard characters: False
 
 The MeetingForwardNotificationEnabled parameter specifies whether to enable meeting forward notifications for recipients in the remote domain. Valid values are:
 
-- $true: Meeting requests forwarded to recipients in the remote domain generate a meeting forward notification to the meeting organizer. This is the default value.
+- $true: Meeting requests forwarded to recipients in the remote domain generate a meeting forward notification to the meeting organizer. This value is the default.
 - $false: Meeting requests forwarded to recipients in the remote domain don't generate a meeting forward notification to the meeting organizer.
 
 ```yaml
@@ -469,7 +469,7 @@ This parameter is functional only in on-premises Exchange.
 
 The NDRDiagnosticInfoEnabled parameter specifies whether diagnostic information is included in non-delivery reports (also known NDRs or bounce messages) that are sent to recipients the remote domain. Valid values are:
 
-- $true: The diagnostic information of an NDR includes details that help administrators troubleshoot delivery problems. This detailed information includes internal server names. This is the default value.
+- $true: The diagnostic information of an NDR includes details that help administrators troubleshoot delivery problems. This detailed information includes internal server names. This value is the default.
 - $false: The diagnostic information section in the NDR body as well as internal server headers from the attached original message headers are removed from the NDR.
 
 This parameter is meaningful only when the value of the NDREnabled parameter is $true.
@@ -492,7 +492,7 @@ Accept wildcard characters: False
 
 The NDREnabled parameter specifies whether to allow non-delivery reports (also known NDRs or bounce messages) from your organization to recipients in the remote domain. Valid values are:
 
-- $true: NDRs from your organization are sent to recipients in the remote domain. This is the default value.
+- $true: NDRs from your organization are sent to recipients in the remote domain. This value is the default.
 - $false: NDRs from your organization aren't sent to recipients in the remote domain.
 
 ```yaml
@@ -540,7 +540,7 @@ The PreferredInternetCodePageForShiftJis parameter specifies the specific code p
 - 50220: Use ISO-2022-JP codepage.
 - 50221: Use ESC-2022-JP codepage.
 - 50222: Use SIO-2022-JP codepage.
-- Undefined: No codepage is defined. This is the default value.
+- Undefined: No codepage is defined. This value is the default.
 
 ```yaml
 Type: PreferredInternetCodePageForShiftJisEnum
@@ -560,7 +560,7 @@ Accept wildcard characters: False
 
 The RequiredCharsetCoverage parameter specifies a percentage threshold for characters in a message that must match to apply your organization's preferred character set before switching to automatic character set detection.
 
-For example, if you set this parameter to 60, the preferred character sets will still be used during content conversion for messages that contain characters from non-preferred character sets as long as the percentage of those characters is 40 percent or less. If the percentage of characters in a message doesn't belong to preferred character sets, Exchange analyzes the Unicode characters and automatically determines the best matching character set to use.
+For example, if you set this parameter to 60, the preferred character sets are still used during content conversion for messages that contain characters from non-preferred character sets as long as the percentage of those characters is 40 percent or less. If the percentage of characters in a message doesn't belong to preferred character sets, Exchange analyzes the Unicode characters and automatically determines the best matching character set to use.
 
 If recipients in the remote domain use characters that span character sets, you might want to specify a lower percentage to ensure that your organization's preferred character set is used during content conversion.
 
@@ -603,7 +603,7 @@ Accept wildcard characters: False
 The TargetDeliveryDomain parameter specifies whether the remote domain is used in cross-forest deployments to generate target email addresses for new mail users that represent users in the other organization (for example, all mailboxes hosted on Exchange Online are represented as mail users in your on-premises organization). Valid values are:
 
 - $true: The remote domain is used for the target email address of mail users that represent the users in the other forest.
-- $false: The remote domain isn't used for the target email address of mail users that represent the users in the other forest. This is the default value.
+- $false: The remote domain isn't used for the target email address of mail users that represent the users in the other forest. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -625,7 +625,7 @@ The TNEFEnabled parameter specifies whether Transport Neutral Encapsulation Form
 
 - $true: TNEF encoding is used on all messages sent to the remote domain.
 - $false: TNEF encoding isn't used on any messages sent to the remote domain.
-- $null (blank): TNEF encoding isn't specified for the remote domain. This is the default value. TNEF encoding for recipients in the remote domain is controlled by the value of the UseMapiRichTextFormat parameter for any mail user or mail contact objects, the sender's per-recipient settings in Outlook, or the sender's default internet message settings in Outlook
+- $null (blank): TNEF encoding isn't specified for the remote domain. This value is the default. TNEF encoding for recipients in the remote domain is controlled by the value of the UseMapiRichTextFormat parameter for any mail user or mail contact objects, the sender's per-recipient settings in Outlook, or the sender's default internet message settings in Outlook
 
 ```yaml
 Type: Boolean
@@ -645,8 +645,8 @@ Accept wildcard characters: False
 
 The TrustedMailInboundEnabled parameter specifies whether messages from senders in the remote domain are treated as trusted messages. Valid values are:
 
-- $true: Inbound messages from senders in the remote domain are considered safe and will bypass content filtering and recipient filtering.
-- $false: Inbound messages from senders in the remote domain won't bypass content filtering and recipient filtering. This is the default value.
+- $true: Inbound messages from senders in the remote domain are considered safe and skip content filtering and recipient filtering.
+- $false: Inbound messages from senders in the remote domain don't bypass content filtering and recipient filtering. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -666,8 +666,8 @@ Accept wildcard characters: False
 
 The TrustedMailOutboundEnabled parameter specifies whether messages sent to recipients in the remote domain are treated as trusted messages. Valid values are:
 
-- $true: Outbound messages to recipients in the remote domain are considered safe and will bypass content filtering and recipient filtering. We recommend that you use this value in cross-forest deployments.
-- $false: Outbound messages to recipients in the remote domain won't bypass content filtering and recipient filtering. This is the default value.
+- $true: Outbound messages to recipients in the remote domain are considered safe and skip content filtering and recipient filtering. We recommend that you use this value in cross-forest deployments.
+- $false: Outbound messages to recipients in the remote domain don't bypass content filtering and recipient filtering. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -688,7 +688,7 @@ Accept wildcard characters: False
 The UseSimpleDisplayName parameter specifies whether the sender's simple display name is used for the From email address in messages sent to recipients in the remote domain. Valid values are:
 
 - $true: Simple display names are used in messages sent to recipients in the remote domain. If the sender doesn't have a simple display name configured, the From email address is `EmailAddress <EmailAddress>`.
-- $false: Simple display names aren't used in messages sent to recipients in the remote domain. This is the default value.
+- $false: Simple display names aren't used in messages sent to recipients in the remote domain. This value is the default.
 
 ```yaml
 Type: Boolean
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-RemoteMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Set-RemoteMailbox.md
index 9ddb71e508..c561807539 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-RemoteMailbox.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-RemoteMailbox.md
@@ -93,7 +93,7 @@ Some attributes on mailboxes in the service can only be configured by connecting
 
 Directory synchronization must be configured correctly for changes made to an on-premises mail user to be applied to a mailbox in the service. Changing the configuration of the mailbox in the service isn't immediate and depends on the directory synchronization schedule.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -102,14 +102,14 @@ You need to be assigned permissions before you can run this cmdlet. Although thi
 Set-RemoteMailbox -Identity davids -Type Room
 ```
 
-This example configures the mailbox in the service that's associated with the specified mail user as a room resource mailbox. This example assumes that directory synchronization has been configured.
+This example configures the mailbox in the service that's associated with the specified mail user as a room resource mailbox. This example assumes that directory synchronization is configured.
 
 ### Example 2
 ```powershell
 Set-RemoteMailbox -Identity kima -AcceptMessagesOnlyFrom davids,"Executive Team",bill@contoso.com
 ```
 
-This example configures delivery restrictions for the mailbox in the service that's associated with the specified mail user. This example assumes that directory synchronization has been configured.
+This example configures delivery restrictions for the mailbox in the service that's associated with the specified mail user. This example assumes that directory synchronization is configured.
 
 ## PARAMETERS
 
@@ -753,7 +753,7 @@ Accept wildcard characters: False
 
 The EmailAddressPolicyEnabled parameter specifies whether to apply email address policies to this recipient. Valid values are:
 
-- $true: Email address policies are applied to this recipient. This is the default value.
+- $true: Email address policies are applied to this recipient. This value is the default.
 - $false: Email address policies aren't applied to this recipient.
 
 ```yaml
@@ -798,7 +798,7 @@ To enter multiple values that overwrite any existing entries, use the following
 
 To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`.
 
-Although this is a multivalued property, the filter `"ExtensionCustomAttribute1 -eq 'Value'"` will return a match if the property _contains_ the specified value.
+Although this is a multivalued property, the filter `"ExtensionCustomAttribute1 -eq 'Value'"` returns a match if the property _contains_ the specified value.
 
 ```yaml
 Type: MultiValuedProperty
@@ -822,7 +822,7 @@ To enter multiple values that overwrite any existing entries, use the following
 
 To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`.
 
-Although this is a multivalued property, the filter `"ExtensionCustomAttribute2 -eq 'Value'"` will return a match if the property _contains_ the specified value.
+Although this is a multivalued property, the filter `"ExtensionCustomAttribute2 -eq 'Value'"` returns a match if the property _contains_ the specified value.
 
 ```yaml
 Type: MultiValuedProperty
@@ -846,7 +846,7 @@ To enter multiple values that overwrite any existing entries, use the following
 
 To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`.
 
-Although this is a multivalued property, the filter `"ExtensionCustomAttribute3 -eq 'Value'"` will return a match if the property _contains_ the specified value.
+Although this is a multivalued property, the filter `"ExtensionCustomAttribute3 -eq 'Value'"` returns a match if the property _contains_ the specified value.
 
 ```yaml
 Type: MultiValuedProperty
@@ -870,7 +870,7 @@ To enter multiple values that overwrite any existing entries, use the following
 
 To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`.
 
-Although this is a multivalued property, the filter `"ExtensionCustomAttribute4 -eq 'Value'"` will return a match if the property _contains_ the specified value.
+Although this is a multivalued property, the filter `"ExtensionCustomAttribute4 -eq 'Value'"` returns a match if the property _contains_ the specified value.
 
 ```yaml
 Type: MultiValuedProperty
@@ -894,7 +894,7 @@ To enter multiple values that overwrite any existing entries, use the following
 
 To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`.
 
-Although this is a multivalued property, the filter `"ExtensionCustomAttribute5 -eq 'Value'"` will return a match if the property _contains_ the specified value.
+Although this is a multivalued property, the filter `"ExtensionCustomAttribute5 -eq 'Value'"` returns a match if the property _contains_ the specified value.
 
 ```yaml
 Type: MultiValuedProperty
@@ -933,7 +933,7 @@ Accept wildcard characters: False
 The HiddenFromAddressListsEnabled parameter specifies whether this recipient is visible in address lists. Valid values are:
 
 - $true: The recipient isn't visible in address lists.
-- $false: The recipient is visible in address lists. This is the default value.
+- $false: The recipient is visible in address lists. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -1077,7 +1077,7 @@ Accept wildcard characters: False
 The ModerationEnabled parameter specifies whether moderation is enabled for this recipient. Valid value are:
 
 - $true: Moderation is enabled for this recipient. Messages sent to this recipient must be approved by a moderator before the messages are delivered.
-- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This is the default value.
+- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This value is the default.
 
 You use the ModeratedBy parameter to specify the moderators.
 
@@ -1149,7 +1149,7 @@ When you enter a number, you can qualify it with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The RecoverableItemsQuota value must be greater than or equal to the RecoverableItemsWarningQuota value.
 
@@ -1181,7 +1181,7 @@ When you enter a number, you can qualify it with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The RecoverableItemsWarningQuota value must be less than or equal to the RecoverableItemsQuota value.
 
@@ -1394,7 +1394,7 @@ Accept wildcard characters: False
 The ResetPasswordOnNextLogon parameter specifies whether the user must change their password the next time they log on. Valid values are:
 
 - $true: The user is required to change their password the next time they log on.
-- $false: The user isn't required to change their password the next time they log on. This is the default value.
+- $false: The user isn't required to change their password the next time they log on. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -1412,7 +1412,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-The SamAccountName parameter (also known as the pre-Windows 2000 user account or group name) specifies an object identifier that's compatible with older versions of Microsoft Windows client and server operating systems. The value can contain letters, numbers, spaces, periods (.), and the following characters: !, #, $, %, ^, &, -, \_, {, }, and ~. The last character can't be a period. Unicode characters are allowed, but accented characters may generate collisions (for example, o and ö match). The maximum length is 20 characters.
+The SamAccountName parameter (also known as the pre-Windows 2000 user account or group name) specifies an object identifier that's compatible with older versions of Microsoft Windows client and server operating systems. The value can contain letters, numbers, spaces, periods (.), and the following characters: !, #, $, %, ^, &, -, \_, {, }, and ~. The last character can't be a period. Unicode characters are allowed, but accented characters might generate collisions (for example, o and ö match). The maximum length is 20 characters.
 
 ```yaml
 Type: String
@@ -1432,7 +1432,7 @@ Accept wildcard characters: False
 
 The SendModerationNotifications parameter specifies when moderation notification messages are sent. Valid values are:
 
-- Always: Notify all senders when their messages aren't approved. This is the default value.
+- Always: Notify all senders when their messages aren't approved. This value is the default.
 - Internal: Notify senders in the organization when their messages aren't approved.
 - Never: Don't notify anyone when a message isn't approved.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ReportSubmissionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-ReportSubmissionPolicy.md
index 6b3d62ea2d..355d745fa1 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ReportSubmissionPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ReportSubmissionPolicy.md
@@ -87,7 +87,7 @@ When you set the email address of the reporting mailbox in the Microsoft Defende
 
 Although it's not absolutely required, it makes sense to keep the email address consistent in the related parameters in the \*-ReportSubmissionPolicy and \*-ReportSubmissionRule cmdlets.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -212,7 +212,7 @@ Accept wildcard characters: False
 The DisableQuarantineReportingOption parameter allows or prevents users from reporting messages in quarantine. Valid values are:
 
 - $true: Users can't report quarantined messages from quarantine.
-- $false: Users can report quarantined messages from quarantine. This is the default value.
+- $false: Users can report quarantined messages from quarantine. This value is the default.
 
 This parameter is meaningful only reporting in Outlook is enabled as described in the EnableReportToMicrosoft parameter.
 
@@ -271,7 +271,7 @@ Accept wildcard characters: False
 The EnableCustomNotificationSender parameter specifies whether a custom sender email address is used for result messages after an admin reviews and marks the reported messages as junk, not junk, or phishing. Valid values are:
 
 - $true: Use a custom Microsoft 365 sender email address.
-- $false: Use the default sender email address. This is the default value.
+- $false: Use the default sender email address. This value is the default.
 
 You specify the sender email address using the NotificationSenderAddress parameter.
 
@@ -623,7 +623,7 @@ Accept wildcard characters: False
 
 The PostSubmitMessageEnabled parameter enables or disables the pop-up Outlook notifications that users see after they report messages using Microsoft reporting tools. Valid values are:
 
-- $true: Users receive pop-up notifications in Outlook after they report messages. This is the default value.
+- $true: Users receive pop-up notifications in Outlook after they report messages. This value is the default.
 - $false: Users don't receive pop-up notifications in Outlook after they report messages.
 
 ```yaml
@@ -796,7 +796,7 @@ Accept wildcard characters: False
 
 The PreSubmitMessageEnabled parameter enables or disables the pop-up Outlook notifications that users see before they report messages using Microsoft reporting tools. Valid values are:
 
-- $true: Users receive pop-up notifications in Outlook before they report messages. This is the default value.
+- $true: Users receive pop-up notifications in Outlook before they report messages. This value is the default.
 - $false: Users don't receive pop-up notifications in Outlook before they report messages.
 
 ```yaml
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ReportSubmissionRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-ReportSubmissionRule.md
index 68ff5bd5f9..16493b60d8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ReportSubmissionRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ReportSubmissionRule.md
@@ -42,7 +42,7 @@ If you set the email address of the reporting mailbox in the Microsoft Defender
 
 When you use this cmdlet to set the email address of the reporting mailbox, the corresponding parameters in the *\-ReportSubmissionPolicy cmdlets are not updated.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ResourceConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-ResourceConfig.md
index 2dd5ae09c4..5c934191af 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ResourceConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ResourceConfig.md
@@ -13,7 +13,7 @@ title: Set-ResourceConfig
 # Set-ResourceConfig
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-ResourceConfig cmdlet to create custom resource properties that you can add to room and equipment mailboxes.
 
@@ -32,7 +32,7 @@ Set-ResourceConfig [-Confirm]
 ## DESCRIPTION
 After you use this cmdlet to create custom resource properties, you use the ResourceCustom parameter on the Set-Mailbox cmdlet to add one or more of those properties to a room or equipment mailbox. For more information, see the ResourceCustom parameter description in Set-Mailbox.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ResubmitRequest.md b/exchange/exchange-ps/ExchangePowerShell/Set-ResubmitRequest.md
index 1f7c69fdab..ac27df96d6 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ResubmitRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ResubmitRequest.md
@@ -30,7 +30,7 @@ Set-ResubmitRequest [-Identity] <ResubmitRequestIdentityParameter> -Enabled <Boo
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-RetentionCompliancePolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-RetentionCompliancePolicy.md
index 2ec06971fb..5e04592e5a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-RetentionCompliancePolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-RetentionCompliancePolicy.md
@@ -659,7 +659,7 @@ The Applications parameter specifies the target when Microsoft 365 Groups are in
 - `Group:Exchange` for the mailbox that's connected to the Microsoft 365 Group.
 - `Group:SharePoint` for the SharePoint site that's connected to the Microsoft 365 Group.
 - `"Group:Exchange,SharePoint"` for both the mailbox and the SharePoint site that are connected to the Microsoft 365 Group.
-- blank (`$null`): This is the default value, and is functionally equivalent to the value `"Group:Exchange,SharePoint"`. To return to the default value of both the mailbox and SharePoint site for the selected Microsoft 365 groups, specify `"Group:Exchange,SharePoint"`.
+- blank (`$null`): This value is the default, and is functionally equivalent to the value `"Group:Exchange,SharePoint"`. To return to the default value of both the mailbox and SharePoint site for the selected Microsoft 365 groups, specify `"Group:Exchange,SharePoint"`.
 
 ```yaml
 Type: MultiValuedProperty
@@ -746,7 +746,7 @@ Accept wildcard characters: False
 
 The Enabled parameter specifies whether the policy is enabled. Valid values are:
 
-- $true: The policy is enabled. This is the default value.
+- $true: The policy is enabled. This value is the default.
 - $false: The policy is disabled.
 
 ```yaml
@@ -768,7 +768,7 @@ Accept wildcard characters: False
 The EnforceSimulationPolicy parameter specifies whether to enforce a simulation policy as an active policy. Valid values are:
 
 - $true: Enforce the simulation policy as an active policy.
-- $false: Don't enforce the simulation policy as an active policy. This is the default value.
+- $false: Don't enforce the simulation policy as an active policy. This value is the default.
 
 For more information about simulation mode, see [Learn about simulation mode](https://learn.microsoft.com/purview/apply-retention-labels-automatically#learn-about-simulation-mo).
 
@@ -1146,9 +1146,9 @@ Accept wildcard characters: False
 The RestrictiveRetention parameter specifies whether Preservation Lock is enabled for a retention policy or retention label policy. Valid values are:
 
 - $true: Preservation Lock is enabled for the policy. No one (including an administrator) can turn off the policy or make it less restrictive.
-- $false: Preservation Lock isn't enabled for the policy. This is the default value.
+- $false: Preservation Lock isn't enabled for the policy. This value is the default.
 
-After a policy has been locked, no one can turn off or disable it, or remove content from the policy. And it's not possible to modify or delete content that's subject to the policy during the retention period. The only way that you can modify the retention policy are by adding content to it, or extending its duration. A locked policy can be increased or extended, but it can't be reduced, disabled, or turned off.
+After a policy is locked, no one can turn off or disable it, or remove content from the policy. And it's not possible to modify or delete content that's subject to the policy during the retention period. The only way that you can modify the retention policy are by adding content to it, or extending its duration. A locked policy can be increased or extended, but it can't be reduced, disabled, or turned off.
 
 Therefore, before you lock a policy for retention, it's critical that you understand your organization's compliance requirements, and that you don't lock a policy until you are certain that it's what you need.
 
@@ -1272,7 +1272,7 @@ Accept wildcard characters: False
 The StartSimulation parameter specifies whether to start the simulation for a policy that was created in simulation mode. Valid values are:
 
 - $true: Start the simulation.
-- $false: Don't start the simulation. This is the default value.
+- $false: Don't start the simulation. This value is the default.
 
 For more information about simulation mode, see [Learn about simulation mode](https://learn.microsoft.com/purview/apply-retention-labels-automatically#learn-about-simulation-mo).
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-RetentionComplianceRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-RetentionComplianceRule.md
index 64bb9f4c85..ff567dd1a3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-RetentionComplianceRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-RetentionComplianceRule.md
@@ -230,7 +230,7 @@ Accept wildcard characters: False
 
 > Applicable: Security & Compliance
 
-The ExcludedItemClasses parameter specifies the types of messages to exclude from the rule. You can use this parameter only to exclude items from a hold policy, which excludes the specified item class from being held. Using this parameter won't exclude items from deletion policies. Typically, you use this parameter to exclude voicemail messages, IM conversations, and other Skype for Business Online content from being held by a hold policy. Common Skype for Business values include:
+The ExcludedItemClasses parameter specifies the types of messages to exclude from the rule. You can use this parameter only to exclude items from a hold policy, which excludes the specified item class from being held. This parameter doesn't exclude items from deletion policies. Typically, you use this parameter to exclude voicemail messages, IM conversations, and other Skype for Business Online content from being held by a hold policy. Common Skype for Business values include:
 
 - IPM.Note.Microsoft.Conversation
 - IPM.Note.Microsoft.Conversation.Voice
@@ -241,7 +241,7 @@ The ExcludedItemClasses parameter specifies the types of messages to exclude fro
 - IPM.Note.Microsoft.Voicemail.UM
 - IPM.Note.Microsoft.Voicemail.UM.CA
 
-Additionally, you can specify [message classes for Exchange items](https://learn.microsoft.com/office/vba/outlook/concepts/forms/item-types-and-message-classes) and custom or non-Microsoft message classes. Note that the values you specify aren't validated, so the parameter accepts any text value.
+Additionally, you can specify [message classes for Exchange items](https://learn.microsoft.com/office/vba/outlook/concepts/forms/item-types-and-message-classes) and custom or non-Microsoft message classes. The values you specify aren't validated, so the parameter accepts any text value.
 
 You can specify multiple item class values by using the following syntax: `"Value1","Value2",..."ValueN"`.
 
@@ -373,7 +373,7 @@ The RetentionDurationDisplayHint parameter specifies the units that are used to
 - Months
 - Years
 
-For example, if this parameter is set to the value Years, and the RetentionDuration parameter is set to the value 365, the Microsoft Purview compliance portal will display 1 year as the content hold duration.
+For example, if this parameter is set to the value Years, and the RetentionDuration parameter is set to the value 365, the Microsoft Purview compliance portal displays 1 year as the content hold duration.
 
 You can't use this parameter for Teams retention rules.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-RetentionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-RetentionPolicy.md
index 161fa3536c..be27958761 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-RetentionPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-RetentionPolicy.md
@@ -13,7 +13,7 @@ title: Set-RetentionPolicy
 # Set-RetentionPolicy
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-RetentionPolicy cmdlet to change the properties of an existing retention policy.
 
@@ -36,7 +36,7 @@ Set-RetentionPolicy [-Identity] <MailboxPolicyIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -138,14 +138,14 @@ This parameter is available only in the cloud-based service.
 
 The IsDefault switch specifies that this retention policy is the default retention policy. You don't need to specify a value with this switch.
 
-When you use this switch, you'll get a warning that this retention policy will replace the current default retention policy (the policy where the IsDefault property value is currently True) as the default. By default, the default retention policy is named Default MRM Policy.
+When you use this switch, you get a warning that this retention policy replaces the current default retention policy (the policy where the IsDefault property value is currently True) as the default. By default, the default retention policy is named Default MRM Policy.
 
 **Note**: Changing which retention policy is the default might or might not affect new and existing mailboxes based on the value of the RetentionPolicy parameter on all mailbox plans:
 
 - $null (blank): Changes to which retention policy is the default are continually reflected in new and existing mailboxes.
 - A retention policy is specified: The value of the RetentionPolicy parameter for all mailbox plans should be $null (blank) or match the Exchange retention policy that's configured as the default policy for the organization. Otherwise, the experience might be inconsistent when creating new mailboxes, enabling disabled mailboxes, and changing licenses. For more information see [Mailbox plans in Exchange Online](https://learn.microsoft.com/exchange/recipients-in-exchange-online/manage-user-mailboxes/mailbox-plans).
 
-If a mailbox is assigned an Exchange retention policy that's not the default policy, the RetentionPolicy value of the mailbox will be overwritten when changing licenses and will need to be manually reset to the original value.
+If a mailbox is assigned an Exchange retention policy that's not the default policy, the RetentionPolicy value of the mailbox is overwritten when changing licenses. You need to manually reset the RetentionPolicy to the original value.
 
 Changes to the default retention policy that affect existing mailboxes can potentially saturate the network if there are hundreds or thousands of mailboxes that require updates.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-RetentionPolicyTag.md b/exchange/exchange-ps/ExchangePowerShell/Set-RetentionPolicyTag.md
index 5ded99737c..cb2e87b762 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-RetentionPolicyTag.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-RetentionPolicyTag.md
@@ -13,7 +13,7 @@ title: Set-RetentionPolicyTag
 # Set-RetentionPolicyTag
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-RetentionPolicyTag cmdlet to modify the properties of a retention tag.
 
@@ -71,13 +71,13 @@ Set-RetentionPolicyTag -Mailbox <MailboxIdParameter>
 ## DESCRIPTION
 Retention tags are used to apply message retention settings to folders and items in a mailbox.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
 ### Example 1
 ```powershell
-Set-RetentionPolicyTag "AllUsers-DeletedItems" -Comment "Items in the Deleted Items folder will be automatically deleted in 120 days"
+Set-RetentionPolicyTag "AllUsers-DeletedItems" -Comment "Items in the Deleted Items folder are automatically deleted in 120 days"
 ```
 
 This example changes the comment for the AllUsers-DeletedItems retention policy tag.
@@ -458,7 +458,7 @@ The RetentionAction parameter specifies the action for the retention policy. Val
 - DeleteAndAllowRecovery: Deletes a message and allows recovery from the Recoverable Items folder.
 - MarkAsPastRetentionLimit: Messages are marked as past the retention limit.
 - MoveToArchive: Moves a message to the user's archive mailbox. You can use this action for retention tags of type All, Personal, and RecoverableItems.
-- PermanentlyDelete: Permanently deletes a message. A message that has been permanently deleted can't be recovered using the Recoverable Items folder. Permanently deleted messages aren't returned in a Discovery search, unless litigation hold is enabled for the mailbox.
+- PermanentlyDelete: Permanently deletes a message. A message that is permanently deleted can't be recovered using the Recoverable Items folder. Permanently deleted messages aren't returned in a Discovery search, unless litigation hold is enabled for the mailbox.
 
 The MoveToDeletedItems and MoveToFolder actions are available, but don't work. These actions are available for upgrades from messaging records management (MRM) 1.0 (managed folders) to MRM 2.0 (retention policies). MRM 2.0 was introduced in Exchange 2010 Service Pack 1 (SP1).
 
@@ -484,7 +484,7 @@ The RetentionEnabled parameter specifies whether the tag is enabled. When set to
 
 Messages with a disabled tag are still considered tagged, so any default policy tags in the user's retention policy aren't applied to such messages.
 
-When you set the RetentionEnabled parameter to $false, the retention period for the tag is shown as Never. Users may apply this tag to items that they want to indicate should never be deleted or should never be moved to the archive. Enabling the tag later may result in unintentional deletion or archiving of items. To avoid this situation, if a retention policy is disabled temporarily, it may be advisable to change the name of that tag so that users are discouraged from using it, such as `DISABLED_<Original Name>`.
+When you set the RetentionEnabled parameter to $false, the retention period for the tag is shown as Never. Users might apply this tag to items that they want to indicate should never be deleted or should never be moved to the archive. Enabling the tag later might result in unintentional deletion or archiving of items. To avoid this situation, if a retention policy is disabled temporarily, it might be advisable to change the name of that tag so that users are discouraged from using it, such as `DISABLED_<Original Name>`.
 
 ```yaml
 Type: Boolean
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-RoleAssignmentPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-RoleAssignmentPolicy.md
index a21a561bda..c7e9c8a83c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-RoleAssignmentPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-RoleAssignmentPolicy.md
@@ -13,7 +13,7 @@ title: Set-RoleAssignmentPolicy
 # Set-RoleAssignmentPolicy
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-RoleAssignmentPolicy cmdlet to modify existing management role assignment policies in your organization.
 
@@ -37,7 +37,7 @@ You can use the Set-RoleAssignmentPolicy cmdlet to change the name of an assignm
 
 For more information about assignment policies, see [Understanding management role assignment policies](https://learn.microsoft.com/exchange/understanding-management-role-assignment-policies-exchange-2013-help).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-RoleGroup.md b/exchange/exchange-ps/ExchangePowerShell/Set-RoleGroup.md
index 8f7420c130..085ea64b34 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-RoleGroup.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-RoleGroup.md
@@ -13,7 +13,7 @@ title: Set-RoleGroup
 # Set-RoleGroup
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-RoleGroup cmdlet to modify who can add or remove members to or from management role groups or change the name of the role group.
 
@@ -58,7 +58,7 @@ If the ManagedBy property is populated with role group managers, the user config
 
 For more information about role groups, see [Understanding management role groups](https://learn.microsoft.com/exchange/understanding-management-role-groups-exchange-2013-help).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-RoutingGroupConnector.md b/exchange/exchange-ps/ExchangePowerShell/Set-RoutingGroupConnector.md
index 51433e0ed4..da642097c4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-RoutingGroupConnector.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-RoutingGroupConnector.md
@@ -40,7 +40,7 @@ The Set-RoutingGroupConnector cmdlet modifies the properties of an existing rout
 
 The Exchange 2003 source servers specified in this cmdlet are automatically added to the ExchangeLegacyInterop universal security group. By default, the Exchange 2010 system grants Send to and Receive from permissions on the Hub Transport servers to members of this group. The source and target servers must be computers that have the Exchange 2010 Hub Transport server role installed, or Exchange 2003 bridgehead servers.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-RpcClientAccess.md b/exchange/exchange-ps/ExchangePowerShell/Set-RpcClientAccess.md
index e421b16986..0a9bafb950 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-RpcClientAccess.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-RpcClientAccess.md
@@ -38,7 +38,7 @@ Outlook 2007 isn't supported in Exchange 2016 or later, so you shouldn't see Out
 
 To block Outlook versions for specific mailboxes, use the Set-CASMailbox cmdlet.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -99,7 +99,7 @@ You can specify ranges. For example, -13.32767.65535, 14.0.0-14.32767.65535, or
 
 You can specify multiple individual values or range values separated by semicolons (;).
 
-Be careful when you restrict client access, because Exchange server components might also use RPC to log on. Some components may report their client version as a text string, while others may report the Exchange build number. Monitor the RPC Client Access log to see the client versions that are connecting to your Exchange server before you block any client versions.
+Be careful when you restrict client access, because Exchange server components might also use RPC to log on. Some components might report their client version as a text string, while others might report the Exchange build number. Monitor the RPC Client Access log to see the client versions that are connecting to your Exchange server before you block any client versions.
 
 ```yaml
 Type: String
@@ -158,7 +158,7 @@ Accept wildcard characters: False
 
 The EncryptionRequired parameter specifies whether encryption is required for RPC client connections. Valid values are:
 
-- $true: Unencrypted RPC client connections are rejected. This is the default value.
+- $true: Unencrypted RPC client connections are rejected. This value is the default.
 - $false: Unencrypted RPC client connections are allowed.
 
 ```yaml
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-SafeAttachmentPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-SafeAttachmentPolicy.md
index 8ad4ecd46d..a68c77dc14 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-SafeAttachmentPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-SafeAttachmentPolicy.md
@@ -39,7 +39,7 @@ Safe Attachments is a feature in Microsoft Defender for Office 365 that opens em
 
 A safe attachment policy can be assigned to only one safe attachment rule by using the SafeAttachmentPolicy parameter on the New-SafeAttachmentRule or Set-SafeAttachmentRule cmdlets.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -83,7 +83,7 @@ Accept wildcard characters: False
 The Action parameter specifies the action for the safe attachment policy. Valid values are:
 
 - Allow: Deliver the message if malware is detected in the attachment and track scanning results. This value corresponds to **Monitor** for the **Safe Attachments unknown malware response** property of the policy in the Microsoft Defender portal.
-- Block: Block the email message that contains the malware attachment. This is the default value.
+- Block: Block the email message that contains the malware attachment. This value is the default.
 - DynamicDelivery: Deliver the email message with a placeholder for each email attachment. The placeholder remains until a copy of the attachment is scanned and determined to be safe. For more information, see [Dynamic Delivery in Safe Attachments policies](https://learn.microsoft.com/defender-office-365/safe-attachments-about#dynamic-delivery-in-safe-attachments-policies).
 
 The value of this parameter is meaningful only when the value of the Enable parameter is $true (the default value is $false).
@@ -150,7 +150,7 @@ Accept wildcard characters: False
 The Enable parameter works with the Action parameter to specify the action for the safe attachment policy. Valid values are:
 
 - $true: The Action parameter specifies the action for the safe attachment policy.
-- $false: This is the default value. Attachments are not scanned by Safe Attachments, regardless of the value of the Action parameter. $false corresponds to the value **Off** for the **Safe Attachments unknown malware response** setting of the complete Safe Attachments policy in the Microsoft Defender portal (the combination of the rule and the corresponding associated policy in PowerShell).
+- $false: This value is the default. Attachments are not scanned by Safe Attachments, regardless of the value of the Action parameter. $false corresponds to the value **Off** for the **Safe Attachments unknown malware response** setting of the complete Safe Attachments policy in the Microsoft Defender portal (the combination of the rule and the corresponding associated policy in PowerShell).
 
 To enable or disable an existing Safe Attachments policy, use the Enable-SafeAttachmentRule or Disable-SafeAttachmentRule cmdlets.
 
@@ -201,7 +201,7 @@ Accept wildcard characters: False
 The Redirect parameter specifies whether to deliver messages to an alternate email address if malware is detected in an attachment. Valid values are:
 
 - $true: Messages that contain malware attachments are delivered to the email address specified by the RedirectAddress parameter. This value is meaningful only when the value of the Action parameter is Allow.
-- $false: Messages that contain malware attachments aren't delivered to another email address. This is the default value.
+- $false: Messages that contain malware attachments aren't delivered to another email address. This value is the default.
 
 ```yaml
 Type: Boolean
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-SafeAttachmentRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-SafeAttachmentRule.md
index 20758a7322..593ee7140c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-SafeAttachmentRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-SafeAttachmentRule.md
@@ -46,7 +46,7 @@ A safe attachment policy can be assigned only to one safe attachment rule.
 > [!IMPORTANT]
 > Different types of recipient conditions use AND logic (the recipient must satisfy **all** specified conditions). Different types of recipient exceptions use OR logic (the recipient must satisfy **any** of the specified exceptions). For more information, see [Safe Attachments policy settings](https://learn.microsoft.com/defender-office-365/safe-attachments-about#safe-attachments-policy-settings).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-SafeLinksPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-SafeLinksPolicy.md
index da0d2e61a6..828b4ef04b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-SafeLinksPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-SafeLinksPolicy.md
@@ -45,7 +45,7 @@ Set-SafeLinksPolicy [-Identity] <SafeLinksPolicyIdParameter>
 ## DESCRIPTION
 Safe Links is a feature in Microsoft Defender for Office 365 that checks links to see if they lead to malicious web sites. When a user clicks a link, the URL is temporarily rewritten and checked against a list of known, malicious web sites. Safe Links includes the URL trace reporting feature to help determine who has clicked through to a malicious web site.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -166,7 +166,7 @@ Accept wildcard characters: False
 
 The DeliverMessageAfterScan parameter specifies whether to deliver email messages only after Safe Links scanning is complete. Valid values are:
 
-- $true: Wait until Safe Links scanning is complete before delivering the message. This is the default value. Messages that contain malicious links are not delivered.
+- $true: Wait until Safe Links scanning is complete before delivering the message. This value is the default. Messages that contain malicious links are not delivered.
 - $false: If Safe Links scanning can't complete, deliver the message anyway.
 
 ```yaml
@@ -232,7 +232,7 @@ Accept wildcard characters: False
 
 The EnableForInternalSenders parameter specifies whether the Safe Links policy is applied to messages sent between internal senders and internal recipients within the same Exchange Online organization. Valid values are:
 
-- $true: The policy is applied to internal and external senders. This is the default value.
+- $true: The policy is applied to internal and external senders. This value is the default.
 - $false: The policy is applied only to external senders.
 
 ```yaml
@@ -254,7 +254,7 @@ Accept wildcard characters: False
 The EnableOrganizationBranding parameter specifies whether your organization's logo is displayed on Safe Links warning and notification pages. Valid values are:
 
 - $true: Organization branding is displayed on Safe Links warning and notification pages. Before you configure this value, you need to follow the instructions in [Customize the Microsoft 365 theme for your organization](https://learn.microsoft.com/microsoft-365/admin/setup/customize-your-organization-theme) to upload your company logo.
-- $false: Organization branding is not displayed on Safe Links warning and notification pages. This is the default value.
+- $false: Organization branding is not displayed on Safe Links warning and notification pages. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -274,7 +274,7 @@ Accept wildcard characters: False
 
 The EnableSafeLinksForEmail parameter specifies whether to enable Safe Links protection for email messages. Valid values are:
 
-- $true: Safe Links is enabled for email. This is the default value. When a user clicks a link in an email, the link will be checked by Safe Links. If the link is found to be malicious, a warning page appears in the default web browser.
+- $true: Safe Links is enabled for email. This value is the default. When a user clicks a link in an email, the link is checked by Safe Links. If the link is found to be malicious, a warning page appears in the default web browser.
 - $false: Safe Links isn't enabled for email.
 
 ```yaml
@@ -295,10 +295,10 @@ Accept wildcard characters: False
 
 The EnableSafeLinksForOffice parameter specifies whether to enable Safe Links protection for supported Office desktop, mobile, or web apps. Valid values are:
 
-- $true: Safe Links scanning is enabled in Office apps. This is the default value. When a user opens a file in a supported Office app and clicks a link in the file, the link is checked by Safe Links. If the link is found to be malicious, a warning page appears in the default web browser.
+- $true: Safe Links scanning is enabled in Office apps. This value is the default. When a user opens a file in a supported Office app and clicks a link in the file, the link is checked by Safe Links. If the link is found to be malicious, a warning page appears in the default web browser.
 - $false: Safe Links isn't enabled for Office apps.
 
-Note that this protection applies to links in Office documents, not links in email messages.
+This protection applies to links in Office documents, not links in email messages.
 
 ```yaml
 Type: Boolean
@@ -318,7 +318,7 @@ Accept wildcard characters: False
 
 The EnableSafeLinksForTeams parameter specifies whether Safe Links is enabled for Microsoft Teams. Valid values are:
 
-- $true: Safe Links is enabled for Teams. This is the default value. When a user clicks a link in a Teams conversation, group chat, or from channels, the link is checked by Safe Links. If the link is found to be malicious, a warning page appears in the default web browser.
+- $true: Safe Links is enabled for Teams. This value is the default. When a user clicks a link in a Teams conversation, group chat, or from channels, the link is checked by Safe Links. If the link is found to be malicious, a warning page appears in the default web browser.
 - $false: Safe Links isn't enabled for Teams.
 
 ```yaml
@@ -339,7 +339,7 @@ Accept wildcard characters: False
 
 The ScanUrls parameter specifies whether to enable or disable real-time scanning of clicked links in email messages. Valid values are:
 
-- $true: Real-time scanning of clicked links, including links that point to files, is enabled. This is the default value.
+- $true: Real-time scanning of clicked links, including links that point to files, is enabled. This value is the default.
 - $false: Real-time scanning of clicked links, including links that point to files, is disabled.
 
 ```yaml
@@ -360,7 +360,7 @@ Accept wildcard characters: False
 
 The TrackClicks parameter specifies whether to track user clicks related to Safe Links protection of links. Valid values are:
 
-- $true: User clicks are tracked. This is the default value.
+- $true: User clicks are tracked. This value is the default.
 - $false: User clicks aren't tracked.
 
 ```yaml
@@ -382,7 +382,7 @@ Accept wildcard characters: False
 The UseTranslatedNotificationText specifies whether to use Microsoft Translator to automatically localize the custom notification text that you specified with the CustomNotificationText parameter. Valid values are:
 
 - $true: Translate custom notification text to the user's language.
-- $false: Don't translate custom notification text to the user's language. This is the default value.
+- $false: Don't translate custom notification text to the user's language. This value is the default.
 
 ```yaml
 Type: Boolean
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-SafeLinksRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-SafeLinksRule.md
index 44a150694c..99b959c1d1 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-SafeLinksRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-SafeLinksRule.md
@@ -44,7 +44,7 @@ Safe Links is a feature in Microsoft Defender for Office 365 that checks links i
 > [!IMPORTANT]
 > Different types of recipient conditions use AND logic (the recipient must satisfy **all** specified conditions). Different types of recipient exceptions use OR logic (the recipient must satisfy **any** of the specified exceptions). For more information, see [Recipient filters in Safe Links policies](https://learn.microsoft.com/defender-office-365/safe-links-about#recipient-filters-in-safe-links-policies).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-SearchDocumentFormat.md b/exchange/exchange-ps/ExchangePowerShell/Set-SearchDocumentFormat.md
index 66cb53e178..71bbfc94b9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-SearchDocumentFormat.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-SearchDocumentFormat.md
@@ -34,7 +34,7 @@ Set-SearchDocumentFormat [-Identity] <SearchDocumentFormatId> -Enabled <Boolean>
 ## DESCRIPTION
 Exchange Search includes built-in support for indexing many file formats. If you disable indexing for a supported file format, items containing an attachment of that file type aren't considered unsearchable. When you perform an [In-Place eDiscovery search in Exchange Server](https://learn.microsoft.com/Exchange/policy-and-compliance/ediscovery/ediscovery) and you select the option to include unsearchable items, only items that are actually unsearchable are returned. Items that weren't searched because the associated file format is set as unsearchable aren't returned.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 

From 7d3dc123158f4ba7b0cc3e06642e9db46223e323 Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Wed, 6 Aug 2025 10:23:09 -0700
Subject: [PATCH 116/145] Create New-CsTeamsPersonalAttendantPolicy.md

---
 .../New-CsTeamsPersonalAttendantPolicy.md     | 295 ++++++++++++++++++
 1 file changed, 295 insertions(+)
 create mode 100644 teams/teams-ps/MicrosoftTeams/New-CsTeamsPersonalAttendantPolicy.md

diff --git a/teams/teams-ps/MicrosoftTeams/New-CsTeamsPersonalAttendantPolicy.md b/teams/teams-ps/MicrosoftTeams/New-CsTeamsPersonalAttendantPolicy.md
new file mode 100644
index 0000000000..a2a437a166
--- /dev/null
+++ b/teams/teams-ps/MicrosoftTeams/New-CsTeamsPersonalAttendantPolicy.md
@@ -0,0 +1,295 @@
+---
+applicable: Microsoft Teams
+author: juliiva
+external help file: Microsoft.Rtc.Management.dll-Help.xml
+Locale: en-US
+manager: jomarque
+Module Name: MicrosoftTeams
+ms.author: juliiva
+online version: https://learn.microsoft.com/powershell/module/microsoftteams/new-csteamspersonalattendantpolicy
+schema: 2.0.0
+title: New-CsTeamsPersonalAttendantPolicy
+---
+
+# New-CsTeamsPersonalAttendantPolicy
+
+## SYNOPSIS
+
+**Limited Preview:** Functionality described in this document is currently in limited preview and only authorized organizations have access.
+
+Use this cmdlet to create a new instance of a Teams Personal Attendant Policy.
+
+## SYNTAX
+
+```
+New-CsTeamsPersonalAttendantPolicy [-Identity <string>] [-PersonalAttendant <string>] [-CallScreening <string>] [-CalendarBookings <string>] [-InboundInternalCalls <string>] [-InboundFederatedCalls <string>] [-InboundPSTNCalls <string>] [-AutomaticTranscription <string>] [-AutomaticRecording <string>] [-Confirm] [-Force] [-WhatIf] [<CommonParameters>]
+```
+
+## DESCRIPTION
+The Teams Personal Attendant Policy controls personal attendant and its functionalities available to users in Microsoft Teams. This cmdlet allows admins to create new policy instances.
+
+## EXAMPLES
+
+### Example 1
+```
+New-CsTeamsPersonalAttendantPolicy -Identity SalesPersonalAttendantPolicy -CallScreening Enabled
+```
+
+The cmdlet create the policy instance SalesPersonalAttendantPolicy and sets the value of the parameter CallScreening to Enabled. The rest of the parameters are set to the corresponding
+values in the Global policy instance.
+
+## PARAMETERS
+
+### -Identity
+Name of the policy instance being created.
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -PersonalAttendant
+Enables the user to use the personal attendant
+
+Possible values:
+
+- EnabledUserOverride: Users can set their preferences from personal attendant settings in the Teams app.
+- Enabled: Enables the user to use this functionality.
+- Disabled: The user is not enabled to use this functionality.
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+
+Required: False
+Position: Named
+Default value: EnabledUserOverride
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -CallScreening
+Enables the user to use the personal attendant call context evaluation features
+
+Possible values:
+
+- EnabledUserOverride: Users can set their preferences from personal attendant settings in the Teams app.
+- Enabled: Enables the user to use this functionality.
+- Disabled: The user is not enabled to use this functionality.
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+
+Required: False
+Position: Named
+Default value: EnabledUserOverride
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -CalendarBookings
+Enables the user to use the personal attendant calendar related features
+
+Possible values:
+
+- EnabledUserOverride: Users can set their preferences from personal attendant settings in the Teams app.
+- Enabled: Enables the user to use this functionality.
+- Disabled: The user is not enabled to use this functionality.
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+
+Required: False
+Position: Named
+Default value: EnabledUserOverride
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -InboundInternalCalls
+Enables the user to use the personal attendant for incoming domain calls
+
+Possible values:
+
+- EnabledUserOverride: Users can set their preferences from personal attendant settings in the Teams app.
+- Enabled: Enables the user to use this functionality.
+- Disabled: The user is not enabled to use this functionality.
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+
+Required: False
+Position: Named
+Default value: EnabledUserOverride
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -InboundFederatedCalls
+Enables the user to use the personal attendant for incoming calls from other domains
+
+Possible values:
+
+- EnabledUserOverride: Users can set their preferences from personal attendant settings in the Teams app.
+- Enabled: Enables the user to use this functionality.
+- Disabled: The user is not enabled to use this functionality.
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+
+Required: False
+Position: Named
+Default value: EnabledUserOverride
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -InboundPSTNCalls
+Enables the user to use the personal attendant for incoming PSTN calls
+
+Possible values:
+
+- EnabledUserOverride: Users can set their preferences from personal attendant settings in the Teams app.
+- Enabled: Enables the user to use this functionality.
+- Disabled: The user is not enabled to use this functionality.
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+
+Required: False
+Position: Named
+Default value: EnabledUserOverride
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -AutomaticTranscription
+Enables the user to use the automatic storing of personal attendant call transcriptions
+
+Possible values:
+
+- EnabledUserOverride: Users can set their preferences from personal attendant settings in the Teams app.
+- Enabled: Enables the user to use this functionality.
+- Disabled: The user is not enabled to use this functionality.
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+
+Required: False
+Position: Named
+Default value: EnabledUserOverride
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -AutomaticRecording
+Enables the user to use the automatic storing of personal attendant call recordings
+
+Possible values:
+
+- EnabledUserOverride: Users can set their preferences from personal attendant settings in the Teams app.
+- Enabled: Enables the user to use this functionality.
+- Disabled: The user is not enabled to use this functionality.
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+
+Required: False
+Position: Named
+Default value: EnabledUserOverride
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -Confirm
+Prompts you for confirmation before running the cmdlet.
+
+```yaml
+Type: SwitchParameter
+Parameter Sets: (All)
+Aliases: cf
+
+Required: False
+Position: Named
+Default value: False
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -Force
+Suppresses any confirmation prompts that would otherwise be displayed before making changes.
+
+```yaml
+Type: SwitchParameter
+Parameter Sets: (All)
+Aliases: wi
+
+Required: False
+Position: Named
+Default value: False
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -WhatIf
+Shows what would happen if the cmdlet runs.
+The cmdlet is not run.
+
+```yaml
+Type: SwitchParameter
+Parameter Sets: (All)
+Aliases: wi
+
+Required: False
+Position: Named
+Default value: False
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### CommonParameters
+This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).
+
+## INPUTS
+
+### System.Management.Automation.PSObject
+
+## OUTPUTS
+
+### System.Object
+
+## NOTES
+
+The cmdlet is available in Teams PowerShell module 7.2.1-preview or later.
+
+## RELATED LINKS
+
+[Get-CsTeamsPersonalAttendantPolicy](./get-csteamspersonalattendantpolicy.md)
+
+[Set-CsTeamsPersonalAttendantPolicy](./set-csteamspersonalattendantpolicy.md)
+
+[Grant-CsTeamsPersonalAttendantPolicy](./grant-csteamspersonalattendantpolicy.md)
+
+[Remove-CsTeamsPersonalAttendantPolicy](./remove-csteamspersonalattendantpolicy.md)

From c999e497beed65d6b8607c1ca9790d4b8b3ea357 Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Wed, 6 Aug 2025 10:25:17 -0700
Subject: [PATCH 117/145] Create Remove-CsTeamsPersonalAttendantPolicy.md

---
 .../Remove-CsTeamsPersonalAttendantPolicy.md  | 118 ++++++++++++++++++
 1 file changed, 118 insertions(+)
 create mode 100644 teams/teams-ps/MicrosoftTeams/Remove-CsTeamsPersonalAttendantPolicy.md

diff --git a/teams/teams-ps/MicrosoftTeams/Remove-CsTeamsPersonalAttendantPolicy.md b/teams/teams-ps/MicrosoftTeams/Remove-CsTeamsPersonalAttendantPolicy.md
new file mode 100644
index 0000000000..a472467b17
--- /dev/null
+++ b/teams/teams-ps/MicrosoftTeams/Remove-CsTeamsPersonalAttendantPolicy.md
@@ -0,0 +1,118 @@
+---
+applicable: Microsoft Teams
+author: juliiva
+external help file: Microsoft.Rtc.Management.dll-Help.xml
+Locale: en-US
+manager: jomarque
+Module Name: MicrosoftTeams
+ms.author: juliiva
+online version: https://learn.microsoft.com/powershell/module/microsoftteams/remove-csteamspersonalattendantpolicy
+schema: 2.0.0
+title: Remove-CsTeamsPersonalAttendantPolicy
+---
+
+# Remove-CsTeamsPersonalAttendantPolicy
+
+## SYNOPSIS
+
+**Limited Preview:** Functionality described in this document is currently in limited preview and only authorized organizations have access.
+
+Use this cmdlet to remove an existing instance of a Teams Personal Attendant Policy or reset the Global policy instance to the default values.
+
+## SYNTAX
+
+```
+Remove-CsTeamsPersonalAttendantPolicy -Identity <string> [-WhatIf] [-Confirm] [<CommonParameters>]
+```
+
+## DESCRIPTION
+This cmdlet removes an existing Teams Personal Attendant Policy instance or resets the Global policy instance to the default values.
+
+## EXAMPLES
+
+### Example 1
+```
+Remove-CsTeamsPersonalAttendantPolicy -Identity SalesPersonalAttendantPolicy
+```
+
+This example removes the Teams Personal Attendant Policy with identity SalesPersonalAttendantPolicy
+
+### Example 2
+```
+Remove-CsTeamsPersonalAttendantPolicy -Identity Global
+```
+
+This example resets the Global Personal Attendant Policy instance to the default values.
+
+## PARAMETERS
+
+### -Identity
+ The Identity parameter is the unique identifier of the Teams Personal Attendant Policy instance to remove or reset.
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+
+Required: True
+Position: Named
+Default value: None
+Accept pipeline input: True (ByPropertyName)
+Accept wildcard characters: False
+```
+
+### -WhatIf
+Shows what would happen if the cmdlet runs.
+The cmdlet is not run.
+
+```yaml
+Type: SwitchParameter
+Parameter Sets: (All)
+Aliases: wi
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -Confirm
+Prompts you for confirmation before running the cmdlet.
+
+```yaml
+Type: SwitchParameter
+Parameter Sets: (All)
+Aliases: cf
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### CommonParameters
+This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).
+
+## INPUTS
+
+### None
+
+## OUTPUTS
+
+### System.Object
+
+## NOTES
+
+The cmdlet is available in Teams PowerShell module 7.2.1-preview or later.
+
+## RELATED LINKS
+
+[New-CsTeamsPersonalAttendantPolicy](./new-csteamspersonalattendantpolicy.md)
+
+[Get-CsTeamsPersonalAttendantPolicy](./get-csteamspersonalattendantpolicy.md)
+
+[Set-CsTeamsPersonalAttendantPolicy](./set-csteamspersonalattendantpolicy.md)
+
+[Grant-CsTeamsPersonalAttendantPolicy](./grant-csteamspersonalattendantpolicy.md)

From e54b77dd8be88f4920ee6fab15f0b47d503b4c4c Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Wed, 6 Aug 2025 10:28:20 -0700
Subject: [PATCH 118/145] Create Set-CsTeamsPersonalAttendantPolicy.md

---
 .../Set-CsTeamsPersonalAttendantPolicy.md     | 304 ++++++++++++++++++
 1 file changed, 304 insertions(+)
 create mode 100644 teams/teams-ps/MicrosoftTeams/Set-CsTeamsPersonalAttendantPolicy.md

diff --git a/teams/teams-ps/MicrosoftTeams/Set-CsTeamsPersonalAttendantPolicy.md b/teams/teams-ps/MicrosoftTeams/Set-CsTeamsPersonalAttendantPolicy.md
new file mode 100644
index 0000000000..615ec54416
--- /dev/null
+++ b/teams/teams-ps/MicrosoftTeams/Set-CsTeamsPersonalAttendantPolicy.md
@@ -0,0 +1,304 @@
+---
+applicable: Microsoft Teams
+author: juliiva
+external help file: Microsoft.Rtc.Management.dll-Help.xml
+Locale: en-US
+manager: jomarque
+Module Name: MicrosoftTeams
+ms.author: juliiva
+online version: https://learn.microsoft.com/powershell/module/microsoftteams/set-csteamspersonalattendantpolicy
+schema: 2.0.0
+title: Set-CsTeamsPersonalAttendantPolicy
+---
+
+# Set-CsTeamsPersonalAttendantPolicy
+
+## SYNOPSIS
+
+**Limited Preview:** Functionality described in this document is currently in limited preview and only authorized organizations have access.
+
+Use this cmdlet to update values in existing Teams Personal Attendant Policies.
+
+## SYNTAX
+
+```
+Set-CsTeamsPersonalAttendantPolicy [-Identity <string>] [-PersonalAttendant <string>] [-CallScreening <string>] [-CalendarBookings <string>] [-InboundInternalCalls <string>] [-InboundFederatedCalls <string>] [-InboundPSTNCalls <string>] [-AutomaticTranscription <string>] [-AutomaticRecording <string>] [-Confirm] [-Force] [-WhatIf] [<CommonParameters>]
+```
+
+## DESCRIPTION
+The Teams Personal Attendant Policy controls personal attendant and its functionalities available to users in Microsoft Teams. This cmdlet allows admins to set values in
+a given Personal Attendant Policy instance.
+
+Only the parameters specified are changed. Other parameters keep their existing values.
+
+## EXAMPLES
+
+### Example 1
+```
+Set-CsTeamsPersonalAttendantPolicy -Identity Global -CallScreening Disabled
+```
+
+Sets the value of the parameter CallScreening in the Global (default) Teams Personal Attendant Policy instance.
+
+### Example 2
+```
+Set-CsTeamsPersonalAttendantPolicy -Identity SalesPersonalAttendantPolicy -CalendarBookings Disabled
+```
+
+Sets the value of the parameter CalendarBookings to Disabled in the Teams Personal Attendant Policy instance called SalesPersonalAttendantPolicy.
+
+## PARAMETERS
+
+### -Identity
+Name of the policy instance being created.
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -PersonalAttendant
+Enables the user to use the personal attendant
+
+Possible values:
+
+- EnabledUserOverride: Users can set their preferences from personal attendant settings in the Teams app.
+- Enabled: Enables the user to use this functionality.
+- Disabled: The user is not enabled to use this functionality.
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+
+Required: False
+Position: Named
+Default value: EnabledUserOverride
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -CallScreening
+Enables the user to use the personal attendant call context evaluation features
+
+Possible values:
+
+- EnabledUserOverride: Users can set their preferences from personal attendant settings in the Teams app.
+- Enabled: Enables the user to use this functionality.
+- Disabled: The user is not enabled to use this functionality.
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+
+Required: False
+Position: Named
+Default value: EnabledUserOverride
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -CalendarBookings
+Enables the user to use the personal attendant calendar related features
+
+Possible values:
+
+- EnabledUserOverride: Users can set their preferences from personal attendant settings in the Teams app.
+- Enabled: Enables the user to use this functionality.
+- Disabled: The user is not enabled to use this functionality.
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+
+Required: False
+Position: Named
+Default value: EnabledUserOverride
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -InboundInternalCalls
+Enables the user to use the personal attendant for incoming domain calls
+
+Possible values:
+
+- EnabledUserOverride: Users can set their preferences from personal attendant settings in the Teams app.
+- Enabled: Enables the user to use this functionality.
+- Disabled: The user is not enabled to use this functionality.
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+
+Required: False
+Position: Named
+Default value: EnabledUserOverride
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -InboundFederatedCalls
+Enables the user to use the personal attendant for incoming calls from other domains
+
+Possible values:
+
+- EnabledUserOverride: Users can set their preferences from personal attendant settings in the Teams app.
+- Enabled: Enables the user to use this functionality.
+- Disabled: The user is not enabled to use this functionality.
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+
+Required: False
+Position: Named
+Default value: EnabledUserOverride
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -InboundPSTNCalls
+Enables the user to use the personal attendant for incoming PSTN calls
+
+Possible values:
+
+- EnabledUserOverride: Users can set their preferences from personal attendant settings in the Teams app.
+- Enabled: Enables the user to use this functionality.
+- Disabled: The user is not enabled to use this functionality.
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+
+Required: False
+Position: Named
+Default value: EnabledUserOverride
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -AutomaticTranscription
+Enables the user to use the automatic storing of personal attendant call transcriptions
+
+Possible values:
+
+- EnabledUserOverride: Users can set their preferences from personal attendant settings in the Teams app.
+- Enabled: Enables the user to use this functionality.
+- Disabled: The user is not enabled to use this functionality.
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+
+Required: False
+Position: Named
+Default value: EnabledUserOverride
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -AutomaticRecording
+Enables the user to use the automatic storing of personal attendant call recordings
+
+Possible values:
+
+- EnabledUserOverride: Users can set their preferences from personal attendant settings in the Teams app.
+- Enabled: Enables the user to use this functionality.
+- Disabled: The user is not enabled to use this functionality.
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+
+Required: False
+Position: Named
+Default value: EnabledUserOverride
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -Confirm
+Prompts you for confirmation before running the cmdlet.
+
+```yaml
+Type: SwitchParameter
+Parameter Sets: (All)
+Aliases: cf
+
+Required: False
+Position: Named
+Default value: False
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -Force
+Suppresses any confirmation prompts that would otherwise be displayed before making changes.
+
+```yaml
+Type: SwitchParameter
+Parameter Sets: (All)
+Aliases: 
+
+Required: False
+Position: Named
+Default value: False
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -WhatIf
+Shows what would happen if the cmdlet runs.
+The cmdlet is not run.
+
+```yaml
+Type: SwitchParameter
+Parameter Sets: (All)
+Aliases: wi
+
+Required: False
+Position: Named
+Default value: False
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### CommonParameters
+This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).
+
+## INPUTS
+
+### System.Management.Automation.PSObject
+
+## OUTPUTS
+
+### System.Object
+
+## NOTES
+
+The cmdlet is available in Teams PowerShell module 7.2.1-preview or later.
+
+## RELATED LINKS
+
+[New-CsTeamsPersonalAttendantPolicy](./new-csteamspersonalattendantpolicy.md)
+
+[Get-CsTeamsPersonalAttendantPolicy](./get-csteamspersonalattendantpolicy.md)
+
+[Grant-CsTeamsPersonalAttendantPolicy](./grant-csteamspersonalattendantpolicy.md)
+
+[Remove-CsTeamsPersonalAttendantPolicy](./remove-csteamspersonalattendantpolicy.md)

From 6b9901ea0db5f4db3c5d08cbfa6a418b36360a76 Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Wed, 6 Aug 2025 10:35:18 -0700
Subject: [PATCH 119/145] Update Get-CsTeamsPersonalAttendantPolicy.md

---
 .../MicrosoftTeams/Get-CsTeamsPersonalAttendantPolicy.md        | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/teams/teams-ps/MicrosoftTeams/Get-CsTeamsPersonalAttendantPolicy.md b/teams/teams-ps/MicrosoftTeams/Get-CsTeamsPersonalAttendantPolicy.md
index 721d583679..5791585650 100644
--- a/teams/teams-ps/MicrosoftTeams/Get-CsTeamsPersonalAttendantPolicy.md
+++ b/teams/teams-ps/MicrosoftTeams/Get-CsTeamsPersonalAttendantPolicy.md
@@ -1,6 +1,6 @@
 ---
 external help file: Microsoft.Rtc.Management.dll-Help.xml
-online version: https://learn.microsoft.com/powershell/module/teams/get-csteamspersonalattendantpolicy
+online version: https://learn.microsoft.com/powershell/module/micrososftteams/get-csteamspersonalattendantpolicy
 applicable: Microsoft Teams
 title: Get-CsTeamsPersonalAttendantPolicy
 schema: 2.0.0

From d246de24f9ee9c2056646ec10a0c41158971d18d Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Wed, 6 Aug 2025 10:41:52 -0700
Subject: [PATCH 120/145] Update Get-CsTeamsPersonalAttendantPolicy.md

---
 .../MicrosoftTeams/Get-CsTeamsPersonalAttendantPolicy.md        | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/teams/teams-ps/MicrosoftTeams/Get-CsTeamsPersonalAttendantPolicy.md b/teams/teams-ps/MicrosoftTeams/Get-CsTeamsPersonalAttendantPolicy.md
index 5791585650..7c200d7327 100644
--- a/teams/teams-ps/MicrosoftTeams/Get-CsTeamsPersonalAttendantPolicy.md
+++ b/teams/teams-ps/MicrosoftTeams/Get-CsTeamsPersonalAttendantPolicy.md
@@ -1,6 +1,6 @@
 ---
 external help file: Microsoft.Rtc.Management.dll-Help.xml
-online version: https://learn.microsoft.com/powershell/module/micrososftteams/get-csteamspersonalattendantpolicy
+online version: https://learn.microsoft.com/powershell/module/microsoftteams/get-csteamspersonalattendantpolicy
 applicable: Microsoft Teams
 title: Get-CsTeamsPersonalAttendantPolicy
 schema: 2.0.0

From a5bf99df108f8910e6e8b0048b799afde84dde64 Mon Sep 17 00:00:00 2001
From: Chris Davis <chris.davis@microsoft.com>
Date: Wed, 6 Aug 2025 10:42:33 -0700
Subject: [PATCH 121/145] Acrolinx 14

---
 .../Set-SecOpsOverridePolicy.md               |  4 +-
 .../ExchangePowerShell/Set-SendConnector.md   | 12 ++--
 .../Set-SenderFilterConfig.md                 |  2 +-
 .../ExchangePowerShell/Set-SenderIdConfig.md  |  2 +-
 .../Set-SenderReputationConfig.md             | 18 +++---
 .../Set-ServerComponentState.md               |  2 +-
 .../ExchangePowerShell/Set-ServerMonitor.md   |  2 +-
 .../Set-ServicePrincipal.md                   |  2 +-
 .../ExchangePowerShell/Set-SettingOverride.md |  2 +-
 .../ExchangePowerShell/Set-SharingPolicy.md   |  8 +--
 .../ExchangePowerShell/Set-SiteMailbox.md     |  6 +-
 .../Set-SiteMailboxProvisioningPolicy.md      | 12 ++--
 .../ExchangePowerShell/Set-SmimeConfig.md     | 32 +++++-----
 .../Set-SupervisoryReviewPolicyV2.md          |  2 +-
 .../ExchangePowerShell/Set-SweepRule.md       |  4 +-
 .../ExchangePowerShell/Set-SystemMessage.md   |  4 +-
 .../Set-TeamsProtectionPolicy.md              |  4 +-
 .../Set-TeamsProtectionPolicyRule.md          |  2 +-
 .../Set-TenantAllowBlockListItems.md          |  4 +-
 .../Set-TenantAllowBlockListSpoofItems.md     |  2 +-
 .../Set-TextMessagingAccount.md               |  4 +-
 .../Set-ThrottlingPolicy.md                   | 14 ++---
 .../Set-ThrottlingPolicyAssociation.md        |  2 +-
 .../ExchangePowerShell/Set-TransportAgent.md  |  2 +-
 .../ExchangePowerShell/Set-TransportConfig.md | 38 ++++++------
 .../ExchangePowerShell/Set-TransportRule.md   | 58 +++++++++----------
 .../ExchangePowerShell/Set-TransportServer.md | 56 +++++++++---------
 .../Set-TransportService.md                   | 58 ++++++++++---------
 .../ExchangePowerShell/Set-UMAutoAttendant.md |  2 +-
 .../Set-UMCallAnsweringRule.md                | 12 ++--
 .../Set-UMCallRouterSettings.md               | 10 +++-
 .../ExchangePowerShell/Set-UMDialPlan.md      |  4 +-
 .../ExchangePowerShell/Set-UMIPGateway.md     | 14 ++---
 .../ExchangePowerShell/Set-UMMailbox.md       | 10 ++--
 .../ExchangePowerShell/Set-UMMailboxPIN.md    | 17 +++---
 .../ExchangePowerShell/Set-UMMailboxPolicy.md | 12 ++--
 .../ExchangePowerShell/Set-UMServer.md        | 18 ++++--
 .../ExchangePowerShell/Set-UMService.md       | 20 +++----
 .../Set-UnifiedAuditLogRetentionPolicy.md     |  8 +--
 .../ExchangePowerShell/Set-UnifiedGroup.md    | 18 +++---
 .../ExchangePowerShell/Set-User.md            | 16 ++---
 .../Set-UserBriefingConfig.md                 |  2 +-
 .../ExchangePowerShell/Set-UserPhoto.md       | 16 ++---
 .../Set-WebServicesVirtualDirectory.md        | 24 ++++----
 .../Set-X400AuthoritativeDomain.md            |  2 +-
 .../Start-ComplianceSearch.md                 |  4 +-
 .../Start-DatabaseAvailabilityGroup.md        |  2 +-
 .../Start-EdgeSynchronization.md              |  4 +-
 .../Start-HistoricalSearch.md                 |  8 +--
 .../Start-MailboxAssistant.md                 |  2 +-
 .../ExchangePowerShell/Start-MailboxSearch.md |  4 +-
 .../Start-ManagedFolderAssistant.md           | 12 ++--
 .../Start-MigrationBatch.md                   |  6 +-
 .../ExchangePowerShell/Start-MigrationUser.md |  2 +-
 .../Start-RetentionAutoTagLearning.md         |  2 +-
 .../Stop-ComplianceSearch.md                  |  4 +-
 .../Stop-DatabaseAvailabilityGroup.md         |  2 +-
 .../Stop-HistoricalSearch.md                  |  2 +-
 .../ExchangePowerShell/Stop-MailboxSearch.md  |  4 +-
 .../Stop-ManagedFolderAssistant.md            |  2 +-
 .../ExchangePowerShell/Stop-MigrationBatch.md |  6 +-
 .../ExchangePowerShell/Stop-MigrationUser.md  |  2 +-
 .../Suspend-MailboxDatabaseCopy.md            |  2 +-
 .../Suspend-MailboxExportRequest.md           |  2 +-
 .../Suspend-MailboxImportRequest.md           |  4 +-
 .../Suspend-MailboxRestoreRequest.md          |  4 +-
 .../ExchangePowerShell/Suspend-Message.md     |  4 +-
 .../ExchangePowerShell/Suspend-MoveRequest.md |  4 +-
 ...end-PublicFolderMailboxMigrationRequest.md |  4 +-
 .../Suspend-PublicFolderMigrationRequest.md   |  2 +-
 .../Suspend-PublicFolderMoveRequest.md        |  2 +-
 .../Suspend-PublicFolderReplication.md        |  2 +-
 .../ExchangePowerShell/Suspend-Queue.md       |  2 +-
 .../Test-ActiveSyncConnectivity.md            |  6 +-
 .../Test-ApplicationAccessPolicy.md           |  2 +-
 .../Test-ArchiveConnectivity.md               |  2 +-
 .../Test-AssistantHealth.md                   |  4 +-
 .../Test-CalendarConnectivity.md              |  4 +-
 .../Test-ClientAccessRule.md                  |  4 +-
 .../Test-DataClassification.md                |  4 +-
 .../Test-EcpConnectivity.md                   |  4 +-
 .../Test-EdgeSynchronization.md               |  8 +--
 .../ExchangePowerShell/Test-ExchangeSearch.md |  2 +-
 .../Test-FederationTrust.md                   |  4 +-
 .../Test-FederationTrustCertificate.md        |  2 +-
 .../Test-IRMConfiguration.md                  |  4 +-
 .../Test-ImapConnectivity.md                  |  4 +-
 .../Test-M365DataAtRestEncryptionPolicy.md    |  2 +-
 .../Test-MAPIConnectivity.md                  |  8 +--
 .../ExchangePowerShell/Test-MRSHealth.md      |  4 +-
 .../ExchangePowerShell/Test-Mailflow.md       |  8 +--
 .../ExchangePowerShell/Test-Message.md        |  4 +-
 .../Test-MigrationServerAvailability.md       | 14 ++---
 .../Test-OAuthConnectivity.md                 |  8 +--
 .../Test-OrganizationRelationship.md          |  6 +-
 .../Test-OutlookConnectivity.md               | 24 ++++----
 .../Test-OutlookWebServices.md                |  4 +-
 97 files changed, 412 insertions(+), 387 deletions(-)

diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-SecOpsOverridePolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-SecOpsOverridePolicy.md
index 8757a73749..35300359af 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-SecOpsOverridePolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-SecOpsOverridePolicy.md
@@ -35,7 +35,7 @@ Set-SecOpsOverridePolicy [-Identity] <PolicyIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -154,7 +154,7 @@ Accept wildcard characters: False
 
 The Enabled parameter specifies whether the policy is enabled. Valid values are:
 
-- $true: The policy is enabled. This is the default value.
+- $true: The policy is enabled. This value is the default.
 - $false: The policy is disabled.
 
 ```yaml
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-SendConnector.md b/exchange/exchange-ps/ExchangePowerShell/Set-SendConnector.md
index e368fba06a..0bf6785c3c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-SendConnector.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-SendConnector.md
@@ -63,7 +63,7 @@ Set-SendConnector [-Identity] <SendConnectorIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -103,7 +103,7 @@ Accept wildcard characters: False
 
 The AddressSpaces parameter specifies the domain names to which the Send connector routes mail. The complete syntax for entering each address space is: `AddressSpaceType:AddressSpace;AddressSpaceCost`.
 
-- AddressSpaceType: On an Edge server, the address space type must be SMTP. In the Transport service on a Mailbox server, the address space type may be SMTP, X400, or any other text string. If you omit the address space type, SMTP is assumed.
+- AddressSpaceType: On an Edge server, the address space type must be SMTP. In the Transport service on a Mailbox server, the address space type might be SMTP, X400, or any other text string. If you omit the address space type, SMTP is assumed.
 - AddressSpace: For SMTP address space types, the address space that you enter must be RFC 1035-compliant. For example, \*, \*.com, and \*.contoso.com are permitted, but \*contoso.com is not. For X.400 address space types, the address space that you enter must be RFC 1685-compliant, such as o=MySite;p=MyOrg;a=adatum;c=us. For all other values of address space type, you can enter any text for the address space.
 - AddressSpaceCost: The valid input range for the cost is from 1 through 100. A lower cost indicates a better route. This parameter is optional. If you omit the address space cost, a cost of 1 is assumed. If you enter a non-SMTP address space that contains the semicolon character (;), you must specify the address space cost.
 
@@ -114,7 +114,7 @@ If you specify the address space type or the address space cost, you must enclos
 - "SMTP:contoso.com"
 - contoso.com
 
-You may specify multiple address spaces by separating the address spaces with commas, for example: contoso.com,fabrikam.com. If you specify the address space type or the address space cost, enclose the address space in quotation marks ("), for example: "contoso.com;2","fabrikam.com;3".
+You might specify multiple address spaces by separating the address spaces with commas, for example: contoso.com,fabrikam.com. If you specify the address space type or the address space cost, enclose the address space in quotation marks ("), for example: "contoso.com;2","fabrikam.com;3".
 
 If you specify a non-SMTP address space type on a Send connector configured in the Transport service on a Mailbox server, you must configure the following parameters:
 
@@ -165,7 +165,7 @@ The CloudServicesMailEnabled parameter specifies whether the connector is used f
 
 Valid values are:
 
-- $true: The connector is used for mail flow in hybrid organizations, so cross-premises headers are preserved or promoted in messages that flow through the connector. This is the default value for connectors that are created by the Hybrid Configuration wizard. Certain X-MS-Exchange-Organization-\* headers in outbound messages that are sent from one side of the hybrid organization to the other are converted to X-MS-Exchange-CrossPremises-\* headers and are thereby preserved in messages. X-MS-Exchange-CrossPremises-\* headers in inbound messages that are received on one side of the hybrid organization from the other are promoted to X-MS-Exchange-Organization-\* headers. These promoted headers replace any instances of the same X-MS-Exchange-Organization-\* headers that already exist in messages.
+- $true: The connector is used for mail flow in hybrid organizations, so cross-premises headers are preserved or promoted in messages that flow through the connector. This value is the default for connectors that are created by the Hybrid Configuration wizard. Certain X-MS-Exchange-Organization-\* headers in outbound messages that are sent from one side of the hybrid organization to the other are converted to X-MS-Exchange-CrossPremises-\* headers and are thereby preserved in messages. X-MS-Exchange-CrossPremises-\* headers in inbound messages that are received on one side of the hybrid organization from the other are promoted to X-MS-Exchange-Organization-\* headers. These promoted headers replace any instances of the same X-MS-Exchange-Organization-\* headers that already exist in messages.
 - $false: The connector isn't used for mail flow in hybrid organizations, so any cross-premises headers are removed from messages that flow through the connector.
 
 ```yaml
@@ -225,7 +225,7 @@ Accept wildcard characters: False
 
 The ConnectorType parameter specifies whether the connector is used in hybrid deployments to send messages to Microsoft 365. Valid values are:
 
-- Default: The connector isn't used to send messages to Microsoft 365. This is the default value.
+- Default: The connector isn't used to send messages to Microsoft 365. This value is the default.
 - XPremises: The connector is used to send messages to Microsoft 365.
 
 ```yaml
@@ -558,7 +558,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The valid input range for this parameter is 0 to 2147483647 bytes. To remove the message size limit on a Send connector, enter a value of unlimited.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-SenderFilterConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-SenderFilterConfig.md
index 01304c3b59..dd199ee3db 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-SenderFilterConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-SenderFilterConfig.md
@@ -38,7 +38,7 @@ Set-SenderFilterConfig [-Action <BlockedSenderAction>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-SenderIdConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-SenderIdConfig.md
index 21ea80d26a..92263d316d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-SenderIdConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-SenderIdConfig.md
@@ -37,7 +37,7 @@ Set-SenderIdConfig
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-SenderReputationConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-SenderReputationConfig.md
index 5497aa6189..676c164d8d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-SenderReputationConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-SenderReputationConfig.md
@@ -39,7 +39,7 @@ Set-SenderReputationConfig [-Confirm]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -103,7 +103,7 @@ Accept wildcard characters: False
 
 The Enabled parameter enables or disables sender reputation on the Exchange server. Valid values are:
 
-- $true: Sender reputation is enabled. This is the default value.
+- $true: Sender reputation is enabled. This value is the default.
 - $false: Sender reputation is disabled.
 
 ```yaml
@@ -124,7 +124,7 @@ Accept wildcard characters: False
 
 The ExternalMailEnabled parameter allows or prevents sender reputation from processing messages from unauthenticated connections that are external to your Exchange organization. Valid values are:
 
-- $true: Sender reputation is enabled on mail from external sources. This is the default value.
+- $true: Sender reputation is enabled on mail from external sources. This value is the default.
 - $false: Sender reputation is disabled on mail from external sources.
 
 ```yaml
@@ -146,7 +146,7 @@ Accept wildcard characters: False
 The InternalMailEnabled parameter allows or prevents sender reputation from processing messages from authenticated sender domains that are authoritative domains in your Exchange organization. Valid values are:
 
 - $true: Sender reputation is enabled on mail from internal sources.
-- $false: Sender reputation is disabled on mail from internal sources. This is the default value.
+- $false: Sender reputation is disabled on mail from internal sources. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -166,14 +166,14 @@ Accept wildcard characters: False
 
 The OpenProxyDetectionEnabled parameter allows or prevents sender reputation from attempting to connect to the message's source IP address to send a test message back to the Exchange server. This test determines if the sender is an open proxy server. Valid values are:
 
-- $true: Open proxy server detection is enabled. This is the default value.
+- $true: Open proxy server detection is enabled. This value is the default.
 - $false: Open proxy server detection is disabled.
 
 Open proxy server detection requires the following open outbound TCP ports in your firewall: 23, 80, 1080, 1081, 3128, and 6588.
 
 If your organization uses a proxy server for outbound Internet access, you also need to define the properties of the proxy server by using the ProxyServerName, ProxyServerPort, and ProxyServerType parameters.
 
-The values of the OpenProxyDetectionEnabled and SenderBlockingEnabled parameters can both be set to $true, but they both can't be set to $false. If one value is $true and the other is $false, and you change the $true value to $false, the parameter that was previously $false will automatically change to $true.
+The values of the OpenProxyDetectionEnabled and SenderBlockingEnabled parameters can both be set to $true, but they both can't be set to $false. If one value is $true and the other is $false, and you change the $true value to $false, the parameter that was previously $false is automatically changed to $true.
 
 ```yaml
 Type: Boolean
@@ -233,7 +233,7 @@ Accept wildcard characters: False
 
 The ProxyServerType parameter specifies the type of your organization's proxy server. Sender reputation uses this value to connect to the Internet for open proxy server detection. Valid values are:
 
-- None: This is the default value.
+- None: This value is the default.
 - Cisco
 - HttpConnect
 - HttpPost
@@ -260,12 +260,12 @@ Accept wildcard characters: False
 
 The SenderBlockingEnabled parameter allows or prevents sender reputation from blocking senders when their sender reputation level (SRL) meets or exceeds the value of the SrlBlockThreshold parameter. Valid values are:
 
-- $true: Sender blocking is enabled. This is the default value.
+- $true: Sender blocking is enabled. This value is the default.
 - $false: Sender blocking is disabled.
 
 You can temporarily block senders for up to 48 hours when you use the SenderBlockingPeriod parameter.
 
-The values of the OpenProxyDetectionEnabled and SenderBlockingEnabled parameters can both be set to $true, but they both can't be set to $false. If one value is $true and the other is $false, and you change the $true value to $false, the parameter that was previously $false will automatically change to $true.
+The values of the OpenProxyDetectionEnabled and SenderBlockingEnabled parameters can both be set to $true, but they both can't be set to $false. If one value is $true and the other is $false, and you change the $true value to $false, the parameter that was previously $false is automatically changed to $true.
 
 ```yaml
 Type: Boolean
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ServerComponentState.md b/exchange/exchange-ps/ExchangePowerShell/Set-ServerComponentState.md
index cfda020fc9..c0fc8e35b1 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ServerComponentState.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ServerComponentState.md
@@ -33,7 +33,7 @@ Set-ServerComponentState [-Identity] <ServerIdParameter> -Component <String> -Re
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ServerMonitor.md b/exchange/exchange-ps/ExchangePowerShell/Set-ServerMonitor.md
index b5498bb8a4..987756400a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ServerMonitor.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ServerMonitor.md
@@ -30,7 +30,7 @@ Set-ServerMonitor [-Server] <ServerIdParameter> -Name <String> -Repairing <Boole
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ServicePrincipal.md b/exchange/exchange-ps/ExchangePowerShell/Set-ServicePrincipal.md
index cbd2bddb7e..7b86a39d4c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ServicePrincipal.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ServicePrincipal.md
@@ -33,7 +33,7 @@ Set-ServicePrincipal [-Identity] <ServicePrincipalIdParameter>
 ## DESCRIPTION
 You can use this cmdlet to change the DisplayName only. If AppId/ObjectId is wrong, delete the service principal and create a new one.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-SettingOverride.md b/exchange/exchange-ps/ExchangePowerShell/Set-SettingOverride.md
index 7c0e64848e..99ff89a1af 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-SettingOverride.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-SettingOverride.md
@@ -40,7 +40,7 @@ Set-SettingOverride [-Identity] <SettingOverrideIdParameter>
 ## DESCRIPTION
 Setting overrides configure and store Exchange server customizations in Active Directory. The settings can be organization-wide or server-specific, and they persist in Active Directory across Exchange Cumulative Updates (CUs). Exchange customizations in web.config or exe.config XML application configuration files are server-specific, and they're lost when you install the next Exchange CU.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-SharingPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-SharingPolicy.md
index 3434cf584b..029d5a0bd5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-SharingPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-SharingPolicy.md
@@ -13,7 +13,7 @@ title: Set-SharingPolicy
 # Set-SharingPolicy
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-SharingPolicy cmdlet to modify existing sharing policies that control how users inside your organization can share free/busy and contact information with users outside your organization.
 
@@ -34,9 +34,9 @@ Set-SharingPolicy [-Identity] <SharingPolicyIdParameter>
 ```
 
 ## DESCRIPTION
-Users can only share free/busy and contact information after federation has been configured between Exchange organizations. After that, users can send sharing invitations to the external recipients as long as those invitations comply with the sharing policy. A sharing policy needs to be assigned to a mailbox to be effective. If a mailbox doesn't have a specific sharing policy assigned, a default policy enforces the sharing options for the mailbox.
+Users can only share free/busy and contact information after federation is configured between Exchange organizations. After that, users can send sharing invitations to the external recipients as long as those invitations comply with the sharing policy. A sharing policy needs to be assigned to a mailbox to be effective. If a mailbox doesn't have a specific sharing policy assigned, a default policy enforces the sharing options for the mailbox.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -113,7 +113,7 @@ Accept wildcard characters: False
 
 The Default switch specifies that the sharing policy is the default sharing policy for all mailboxes. You don't need to specify a value with this switch.
 
-If no sharing policy has been applied to a mailbox, the default policy is automatically applied. If you want to disable sharing across your organization, you disable the default policy.
+If no sharing policy is applied to a mailbox, the default policy is automatically applied. If you want to disable sharing across your organization, you disable the default policy.
 
 ```yaml
 Type: SwitchParameter
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-SiteMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Set-SiteMailbox.md
index 748990da42..a75022387e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-SiteMailbox.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-SiteMailbox.md
@@ -41,7 +41,7 @@ Set-SiteMailbox [-Identity] <RecipientIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -247,7 +247,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-The RemoveDuplicateMessages parameter specifies that when users post messages to a site mailbox, duplicate messages will be deleted. This parameter accepts the values of $true or $false. The default value is $false.
+The RemoveDuplicateMessages parameter specifies that when users post messages to a site mailbox, duplicate messages are deleted. This parameter accepts the values of $true or $false. The default value is $false.
 
 ```yaml
 Type: Boolean
@@ -285,7 +285,7 @@ Accept wildcard characters: False
 
 This parameter is intended for use only by the user interface. We recommend that you don't use this parameter.
 
-The ShowInMyClient parameter specifies that the site mailbox folder will show in your email client.
+The ShowInMyClient parameter specifies that the site mailbox folder appears in your email client.
 
 ```yaml
 Type: Boolean
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-SiteMailboxProvisioningPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-SiteMailboxProvisioningPolicy.md
index 3c639b2c78..5ff1502eb6 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-SiteMailboxProvisioningPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-SiteMailboxProvisioningPolicy.md
@@ -41,7 +41,7 @@ Set-SiteMailboxProvisioningPolicy [-Identity] <MailboxPolicyIdParameter>
 ## DESCRIPTION
 Site mailbox provisioning policies apply settings to new site mailboxes that you create. You can create multiple site mailbox provisioning policies, but only the default policy is followed when users create site mailboxes. The default site mailbox provisioning policy is named Default.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -97,7 +97,7 @@ Accept wildcard characters: False
 The AliasPrefix parameter specifies the custom text prefix to add to the aliases of new site mailboxes. Valid values are:
 
 - A text string that's 8 characters or less. When you specify a text value, the value of the DefaultAliasPrefixEnabled parameter ignored and aliases get the text prefix you specified.
-- The value $null. This is the default value. The results of this value depend on the DefaultAliasPrefixEnabled parameter value. When it's $true, aliases get the default prefix text. When it's $false, aliases don't get any prefix text.
+- The value $null. This value is the default. The results of this value depend on the DefaultAliasPrefixEnabled parameter value. When it's $true, aliases get the default prefix text. When it's $false, aliases don't get any prefix text.
 
 ```yaml
 Type: String
@@ -138,7 +138,7 @@ Accept wildcard characters: False
 
 The DefaultAliasPrefixEnabled parameter specifies whether new site mailboxes have the default prefix text added to the alias. Valid values are:
 
-- $true: Aliases get the default prefix text. This is the default value. In Microsoft 365, the default prefix text is `SMO-` (for example, the alias value `BugBash_2016` becomes `SMO-BugBash_2016`). In on-premises Exchange, the default prefix text is `SM-` (for example, the alias value `BugBash_2016` becomes `SM-BugBash_2016`).
+- $true: Aliases get the default prefix text. This value is the default. In Microsoft 365, the default prefix text is `SMO-` (for example, the alias value `BugBash_2016` becomes `SMO-BugBash_2016`). In on-premises Exchange, the default prefix text is `SM-` (for example, the alias value `BugBash_2016` becomes `SM-BugBash_2016`).
 - $false: Aliases don't get the default prefix text.
 
 The value of this parameter is related to the value of the AliasPrefix parameter. If you specify a text string for AliasPrefix, the DefaultAliasPrefixEnabled value is ignored. Specifying a text value for AliasPrefix automatically sets the value to $false, but even if you set it to $true, the default alias prefix text isn't used.
@@ -207,7 +207,7 @@ A valid value is a number up to 1.999999999 terabytes (2199023254528 bytes) or t
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The IssueWarningQuota value must be less than or equal to the ProhibitSendReceiveQuota value.
 
@@ -238,7 +238,7 @@ When you enter a value, qualify the value with one of the following units:
 - MB (megabytes)
 - GB (gigabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 A valid value is a number up to 1.999999 gigabytes (2147482624 bytes) or the value unlimited. The default value is 36 MB.
 
@@ -286,7 +286,7 @@ A valid value is a number up to 1.999999999 terabytes (2199023254528 bytes) or t
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value must be greater than or equal to the ProhibitSendQuota or IssueWarningQuota values.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-SmimeConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-SmimeConfig.md
index 1c2308992e..a86aa867c9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-SmimeConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-SmimeConfig.md
@@ -13,7 +13,7 @@ title: Set-SmimeConfig
 # Set-SmimeConfig
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-SmimeConfig cmdlet to modify the S/MIME configuration for Outlook on the web (formerly known as Outlook Web App or OWA) and new Outlook for Windows.
 
@@ -57,7 +57,7 @@ Set-SmimeConfig [[-Identity] <OrganizationIdParameter>]
 ## DESCRIPTION
 The Set-SmimeConfig cmdlet can change several important parameters than can reduce the overall level of message security. Review your organization's security policy before you make any changes.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -172,7 +172,7 @@ Accept wildcard characters: False
 
 The OWABCCEncryptedEmailForking parameter specifies how Bcc messages are encrypted in Outlook on the web. Valid values are:
 
-- 0: One encrypted message per Bcc recipient. This is the default value.
+- 0: One encrypted message per Bcc recipient. This value is the default.
 - 1: One single encrypted message for all Bcc recipients.
 - 2: One encrypted message without Bcc forking.
 
@@ -197,7 +197,7 @@ Accept wildcard characters: False
 The OWACheckCRLOnSend parameter specifies how the certificate revocation list (CRL) check is enforced when an email message is sent in Outlook on the web. Valid values are:
 
 - $true: When the CRL distribution point is inaccessible, Outlook on the web displays a warning dialog box and prevents signed or encrypted messages from being sent.
-- $false: When the CRL distribution point is inaccessible, Outlook on the web allows signed or encrypted messages to be sent. This is the default value.
+- $false: When the CRL distribution point is inaccessible, Outlook on the web allows signed or encrypted messages to be sent. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -217,7 +217,7 @@ Accept wildcard characters: False
 
 The OWAClearSign parameter specifies how email messages are signed in Outlook on the web. Valid values are:
 
-- $true: Digitally signed messages are clear-signed. This is the default value.
+- $true: Digitally signed messages are clear-signed. This value is the default.
 - $false: digitally signed messages are opaque-signed.
 
 Clear-signed messages are larger than opaque-signed messages, but clear-signed messages can be read in most email clients, including clients that don't support S/MIME.
@@ -303,7 +303,7 @@ Accept wildcard characters: False
 The OWADisableCRLCheck parameter enables or disables CRL checking in Outlook on the web. Valid values are:
 
 - $true: CRL checks are disabled when validating certificates.
-- $false: CRL checks are enabled when validating certificates.This is the default value.
+- $false: CRL checks are enabled when validating certificates.This value is the default.
 
 Disabling CRL checking can decrease the time that's required to validate the signatures of signed email messages, but it also validates email messages that are signed with revoked certificates.
 
@@ -354,7 +354,7 @@ The OWAEncryptionAlgorithms parameter specifies a list of symmetric encryption a
 - 6603: 3DES (168-bit)
 - 660E: AES128
 - 660F: AES192
-- 6610: AES256 (This is the default value)
+- 6610: AES256 (default value)
 
 If you use a non-Microsoft cryptographic service provider (CSP), you need to specify the object identifier (OID) together with an algorithm ID (Outlook on the web needs an algorithm ID to infer how the algorithm should be used). For example, to provide a custom replacement for the 3DES algorithm, use the value `6603,<CustomOID>`.
 
@@ -380,7 +380,7 @@ Accept wildcard characters: False
 
 The OWAEncryptTemporaryBuffers parameter specifies whether the Outlook on the web client-side temporary message storage buffers are encrypted. Valid values are:
 
-- $true: All client-side temporary buffers that store message data are encrypted using an ephemeral key and the 3DES algorithm. This is the default value.
+- $true: All client-side temporary buffers that store message data are encrypted using an ephemeral key and the 3DES algorithm. This value is the default.
 - $false: Temporary buffer encryption is disabled.
 
 Disabling encryption of the buffers can increase performance of the Outlook on the web client but also leaves information unencrypted in the client's buffer. Consult your organization's security policy before you disable this feature.
@@ -403,7 +403,7 @@ Accept wildcard characters: False
 
 The OWAForceSMIMEClientUpgrade parameter specifies whether or not users are forced to upgrade an S/MIME control that's older than their current version in Outlook on the web.
 
-- $true: Users need to download and install the new control before they can use S/MIME. This is the default value.
+- $true: Users need to download and install the new control before they can use S/MIME. This value is the default.
 - $false: Users receive a warning if the S/MIME control on their computer is not current, but they can still use S/MIME without updating the control.
 
 ```yaml
@@ -445,7 +445,7 @@ Accept wildcard characters: False
 The OWAIncludeCertificateChainWithoutRootCertificate parameter specifies whether the certificate chains of the signing or encryption certificates are included in messages in Outlook on the web. Valid values are:
 
 - $true: Signed or encrypted messages include the full certificate chain, but not the root certificate.
-- $false: Signed or encrypted messages include only the signing and encrypting certificates, not their corresponding certificate chains. This is the default value.
+- $false: Signed or encrypted messages include only the signing and encrypting certificates, not their corresponding certificate chains. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -467,7 +467,7 @@ The OWAIncludeSMIMECapabilitiesInMessage parameter specifies whether signed and
 
 Valid input for this parameter is $true or $false. The default is $false.
 
-Enabling this option increases the size of messages, but may make it easier for some email clients to interact with encrypted messages in Outlook on the web.
+Enabling this option increases the size of messages, but might make it easier for some email clients to interact with encrypted messages in Outlook on the web.
 
 ```yaml
 Type: Boolean
@@ -489,7 +489,7 @@ The OWAOnlyUseSmartCard parameter specifies whether smartcard-based certificates
 
 $true: Smartcard-based certificates for signing and decryption are required when you use Outlook on the web and the S/MIME control.
 
-$false: Smartcard-based certificates for signing and decryption aren't required when you use Outlook on the web and the S/MIME control. This is the default value.
+$false: Smartcard-based certificates for signing and decryption aren't required when you use Outlook on the web and the S/MIME control. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -529,7 +529,7 @@ Accept wildcard characters: False
 
 The OWASignedEmailCertificateInclusion parameter specifies whether the sender's encryption certificate is excluded from a signed email message in Outlook on the web. Valid values are:
 
-- $true: Outlook on the web and the S/MIME control include both signing and encrypting certificates with signed email messages. This is the default value.
+- $true: Outlook on the web and the S/MIME control include both signing and encrypting certificates with signed email messages. This value is the default.
 - $false: Outlook on the web and the S/MIME control do not include signing and encrypting certificates with signed email messages.
 
 When you don't include the certificates with signed email messages, the size of encrypted messages is reduced. However, recipients don't have access to the sender's encryption certificate in the message. Recipients need to retrieve the certificate from a directory, or from the sender.
@@ -556,7 +556,7 @@ The OWASigningAlgorithms parameter specifies the list of symmetric encryption si
 - 800E: CALG\_SHA\_512 or 512-bit Secure Hash Algorithm (SHA)
 - 800D: CALG\_SHA\_384 or 384-bit SHA
 - 800C: CALG\_SHA\_256 or 256-bit SHA
-- 8004: SHA1 or 160-bit SHA-1 (This is the default value)
+- 8004: SHA1 or 160-bit SHA-1 (default value)
 
 If you use a non-Microsoft cryptographic service provider (CSP), you need to specify the object identifier (OID) together with an algorithm ID (Outlook on the web needs an algorithm ID to infer how the algorithm should be used). For example, to provide a custom replacement for the SHA1 algorithm, use the value `8804,<CustomOID>`.
 
@@ -585,7 +585,7 @@ Accept wildcard characters: False
 The OWATripleWrapSignedEncryptedMail parameter specifies whether signed and encrypted email messages in Outlook on the web are triple-wrapped. Valid values are:
 
 - $true: A signed message is encrypted, and then the encrypted message is signed (signed-encrypted-signed).
-- $false: A signed message is encrypted only (there is no additional signing of the encrypted message). This is the default value.
+- $false: A signed message is encrypted only (there is no additional signing of the encrypted message). This value is the default.
 
 Triple-wrapped messages offer the highest level of security for messages under the S/MIME standard, but are larger in size.
 
@@ -633,7 +633,7 @@ The OWAUseSecondaryProxiesWhenFindingCertificates parameter specifies whether al
 
 Valid input for this parameter is $true or $false. The default is $true.
 
-Outlook on the web attempts to find the correct certificate for a recipient when sending encrypted messages. The certificate subject or subject alternative name values can each contain an email address. Because a recipient can have multiple proxy addresses, the certificate's subject or subject alternative name values may not match the recipient's primary SMTP address. When this parameter is set to $true, and the certificate subject or subject alternative name values do not match the recipient's primary SMTP address, Outlook on the web tries to match the certificate's subject to one of the recipient's proxy addresses.
+Outlook on the web attempts to find the correct certificate for a recipient when sending encrypted messages. The certificate subject or subject alternative name values can each contain an email address. Because a recipient can have multiple proxy addresses, the certificate's subject or subject alternative name values might not match the recipient's primary SMTP address. When this parameter is set to $true, and the certificate subject or subject alternative name values do not match the recipient's primary SMTP address, Outlook on the web tries to match the certificate's subject to one of the recipient's proxy addresses.
 
 ```yaml
 Type: Boolean
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-SupervisoryReviewPolicyV2.md b/exchange/exchange-ps/ExchangePowerShell/Set-SupervisoryReviewPolicyV2.md
index dbc7f85428..36033766e8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-SupervisoryReviewPolicyV2.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-SupervisoryReviewPolicyV2.md
@@ -246,7 +246,7 @@ Accept wildcard characters: False
 
 > Applicable: Security & Compliance
 
-The RetentionPeriodInDays parameter specifies the number of days that the messages will be retained for review.
+The RetentionPeriodInDays parameter specifies the number of days that the messages are retained for review.
 
 ```yaml
 Type: Int32
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-SweepRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-SweepRule.md
index 429110e014..444b193a61 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-SweepRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-SweepRule.md
@@ -13,7 +13,7 @@ title: Set-SweepRule
 # Set-SweepRule
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-SweepRule cmdlet to modify Sweep rules in mailboxes.
 
@@ -42,7 +42,7 @@ Set-SweepRule [-Identity] <SweepRuleIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-SystemMessage.md b/exchange/exchange-ps/ExchangePowerShell/Set-SystemMessage.md
index 55f6201f0f..77c85b47e4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-SystemMessage.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-SystemMessage.md
@@ -33,7 +33,7 @@ Set-SystemMessage [-Identity] <SystemMessageIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -215,7 +215,7 @@ The following HTML tags are available:
 - `<EM>` and `</EM>` (italic)
 - `<BR>` (line break)
 - `<P>` and `</P>` (paragraph)
-- `<A HREF="url">` and `</A>` (hyperlink). **Note**: You need to use single quotation marks (not double quotation marks) around the complete text string if you use this tag. Otherwise, you'll receive an error (because of the double quotation marks in the tag).
+- `<A HREF="url">` and `</A>` (hyperlink). **Note**: You need to use single quotation marks (not double quotation marks) around the complete text string if you use this tag. Otherwise, you get an error (because of the double quotation marks in the tag).
 
 Use the following escape codes for these special characters:
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-TeamsProtectionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-TeamsProtectionPolicy.md
index c191f04b4c..ce6a7a824e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-TeamsProtectionPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-TeamsProtectionPolicy.md
@@ -33,7 +33,7 @@ Set-TeamsProtectionPolicy [-Identity] <TeamsProtectionPolicyIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -182,7 +182,7 @@ Accept wildcard characters: False
 
 The ZapEnabled parameter specifies whether to enable zero-hour auto purge (ZAP) for malware and high confidence phishing messages in Teams messages. Valid values are:
 
-- $true: ZAP for malware and high confidence phishing messages in Teams is enabled. This is the default value.
+- $true: ZAP for malware and high confidence phishing messages in Teams is enabled. This value is the default.
 - $false: ZAP for malware and high confidence phishing messages in Teams is disabled.
 
 ```yaml
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-TeamsProtectionPolicyRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-TeamsProtectionPolicyRule.md
index b01e926fd1..42a45386d8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-TeamsProtectionPolicyRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-TeamsProtectionPolicyRule.md
@@ -36,7 +36,7 @@ Set-TeamsProtectionPolicyRule [-Identity] <RuleIdParameter>
 > [!IMPORTANT]
 > Different types of recipient exceptions use OR logic (the recipient must satisfy **any** of the specified exceptions). For more information, see [Configure ZAP for Teams protection in Defender for Office 365 Plan 2](https://learn.microsoft.com/defender-office-365/mdo-support-teams-about#configure-zap-for-teams-protection-in-defender-for-office-365-plan-2).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-TenantAllowBlockListItems.md b/exchange/exchange-ps/ExchangePowerShell/Set-TenantAllowBlockListItems.md
index b42888f270..0c4b286a6b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-TenantAllowBlockListItems.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-TenantAllowBlockListItems.md
@@ -52,7 +52,7 @@ Set-TenantAllowBlockListItems -Entries <String[]> -ListType <ListType>
 ## DESCRIPTION
 In most cases, you can't modify the sender, URL, file, or IP address values after you create the entry. The only exception is URL allow entries for phishing simulations (ListType = URL, ListSubType = AdvancedDelivery). For more information about allowing URLs for phishing simulations, see [Configure the advanced delivery policy for non-Microsoft phishing simulations and email delivery to SecOps mailboxes](https://learn.microsoft.com/defender-office-365/advanced-delivery-policy-configure).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -241,7 +241,7 @@ Accept wildcard characters: False
 The ListSubType parameter further specifies the entry that you want to modify. Valid values are:
 
 - AdvancedDelivery: Use this value for phishing simulation URLs. For more information, see [Configure the advanced delivery policy for non-Microsoft phishing simulations and email delivery to SecOps mailboxes](https://learn.microsoft.com/defender-office-365/advanced-delivery-policy-configure).
-- Tenant: This is the default value.
+- Tenant: This value is the default.
 
 ```yaml
 Type: ListSubType
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-TenantAllowBlockListSpoofItems.md b/exchange/exchange-ps/ExchangePowerShell/Set-TenantAllowBlockListSpoofItems.md
index c2e954de94..def6278fd4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-TenantAllowBlockListSpoofItems.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-TenantAllowBlockListSpoofItems.md
@@ -31,7 +31,7 @@ Set-TenantAllowBlockListSpoofItems [-Identity] <HostedConnectionFilterPolicyIdPa
 ## DESCRIPTION
 This cmdlet allows or blocks spoof pairs (the combination of the spoofed user and the sending infrastructure) in the Tenant Allow/Block List.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-TextMessagingAccount.md b/exchange/exchange-ps/ExchangePowerShell/Set-TextMessagingAccount.md
index 5947abf7b4..ee1c667d6f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-TextMessagingAccount.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-TextMessagingAccount.md
@@ -13,7 +13,7 @@ title: Set-TextMessagingAccount
 # Set-TextMessagingAccount
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 The Set-TextMessagingAccount cmdlet allows a user to configure the text messaging settings on their own mailbox. An administrator can't use this cmdlet to configure the text messaging settings on another user's mailbox.
 
@@ -38,7 +38,7 @@ When text messaging notifications are enabled on a mailbox, you can configure ca
 
 To clear the text messaging settings from your own mailbox, use the Clear-TextMessagingAccount parameter.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ThrottlingPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-ThrottlingPolicy.md
index 6756049cb7..de0f211360 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ThrottlingPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ThrottlingPolicy.md
@@ -178,7 +178,7 @@ By default, there is one default user throttling policy named GlobalThrottlingPo
 
 For more information about how to control the resources consumed by individual users, see [User workload management in Exchange Server](https://learn.microsoft.com/Exchange/server-health/workload-management).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -782,7 +782,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-This parameter isn't used and will be removed.
+This parameter is reserved for internal Microsoft use.
 
 ```yaml
 Type: Unlimited
@@ -854,7 +854,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-The DiscoverySearchTimeoutPeriod parameter specifies the number of minutes that a discovery search will run before it times out.
+The DiscoverySearchTimeoutPeriod parameter specifies the number of minutes that a discovery search runs before it times out.
 
 ```yaml
 Type: Unlimited
@@ -982,7 +982,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-The EasMaxInactivityForDeviceCleanup parameter specifies the length of time that a user's device partnerships will remain active. By default, there is no limit to the number of days that a user's device partnerships will remain active. Use this value if you want to minimize the amount of inactive device partnerships in your organization. To use this setting, specify a value in days since the user's last sync time to cause the device partnership to be removed.
+The EasMaxInactivityForDeviceCleanup parameter specifies the length of time that a user's device partnerships remain active. By default, there is no limit to the number of days that a user's device partnerships remain active. Use this value if you want to minimize the amount of inactive device partnerships in your organization. To use this setting, specify a value in days since the user's last sync time to cause the device partnership to be removed.
 
 ```yaml
 Type: Unlimited
@@ -2180,7 +2180,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-The PowerShellMaxCmdletQueueDepth parameter specifies the number of operations allowed to be executed by the user. This value directly affects the behavior of the PowerShellMaxCmdlets and PowerShellMaxConcurrency parameters. For example, the PowerShellMaxConcurrency parameter consumes at least two operations defined by the PowerShellMaxCmdletQueueDepth parameter but additional operations are also consumed per cmdlet execution. The number of operations depends on the cmdlets executed. We recommend that the value for the PowerShellMaxCmdletQueueDepth parameter be at least three times larger than the value of the PowerShellMaxConcurrency parameter. This parameter won't affect Exchange admin center operations or Exchange Web Services operations.
+The PowerShellMaxCmdletQueueDepth parameter specifies the number of operations allowed to be executed by the user. This value directly affects the behavior of the PowerShellMaxCmdlets and PowerShellMaxConcurrency parameters. For example, the PowerShellMaxConcurrency parameter consumes at least two operations defined by the PowerShellMaxCmdletQueueDepth parameter but additional operations are also consumed per cmdlet execution. The number of operations depends on the cmdlets executed. We recommend that the value for the PowerShellMaxCmdletQueueDepth parameter be at least three times larger than the value of the PowerShellMaxConcurrency parameter. This parameter doesn't affect Exchange admin center operations or Exchange Web Services operations.
 
 ```yaml
 Type: UInt32
@@ -2257,7 +2257,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-The PowerShellMaxDestructiveCmdlets parameter specifies the number of destructive cmdlets that can be executed within a specific time period before their execution is stopped. Destructive cmdlets are cmdlets that can make significant changes to user data and configuration settings in your Exchange organization. Throttling these cmdlets may help prevent accidental data loss. The following cmdlets are designated as destructive:
+The PowerShellMaxDestructiveCmdlets parameter specifies the number of destructive cmdlets that can be executed within a specific time period before their execution is stopped. Destructive cmdlets are cmdlets that can make significant changes to user data and configuration settings in your Exchange organization. Throttling these cmdlets might help prevent accidental data loss. The following cmdlets are designated as destructive:
 
 - Disable-Mailbox
 - Move-ActiveMailboxDatabase
@@ -2305,7 +2305,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-The PowerShellMaxOperations parameter specifies the protocol-level operations that are used to send and receive data. If the execution of a cmdlet results in a significant number of operations (for example, if there is a lot of input/output occurring), throttling may occur. The default setting is Unlimited.
+The PowerShellMaxOperations parameter specifies the protocol-level operations that are used to send and receive data. If the execution of a cmdlet results in a significant number of operations (for example, if there is a lot of input/output occurring), throttling might occur. The default setting is Unlimited.
 
 ```yaml
 Type: Unlimited
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ThrottlingPolicyAssociation.md b/exchange/exchange-ps/ExchangePowerShell/Set-ThrottlingPolicyAssociation.md
index 68a4521905..9c9408f002 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ThrottlingPolicyAssociation.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ThrottlingPolicyAssociation.md
@@ -39,7 +39,7 @@ In data center deployments, the object referred to by the Identity and Throttlin
 
 For more information about how to control the resources consumed by individual users, see [User workload management in Exchange Server](https://learn.microsoft.com/Exchange/server-health/workload-management).
 
-You need to be assigned permissions before you can run the Set-ThrottlingPolicyAssociation cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run the Set-ThrottlingPolicyAssociation cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-TransportAgent.md b/exchange/exchange-ps/ExchangePowerShell/Set-TransportAgent.md
index 590f84d5a2..d41b3a6694 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-TransportAgent.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-TransportAgent.md
@@ -32,7 +32,7 @@ Set-TransportAgent [-Identity] <TransportAgentObjectId>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-TransportConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-TransportConfig.md
index 9f53fa6bc2..b4837dae87 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-TransportConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-TransportConfig.md
@@ -13,7 +13,7 @@ title: Set-TransportConfig
 # Set-TransportConfig
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-TransportConfig cmdlet to modify the transport configuration settings for the whole Exchange organization.
 
@@ -92,7 +92,7 @@ Set-TransportConfig [[-Identity] <OrganizationIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -140,7 +140,7 @@ Accept wildcard characters: False
 
 The AddressBookPolicyRoutingEnabled parameter controls how recipients are resolved in an organization that uses address book policies to create separate virtual organizations within the same Exchange organization. Specifically, the global address list (GAL) that's specified in the user's address book policy controls how recipients are resolved. When the value of this parameter is $true, users that are assigned different GALs appear as external recipients. When the value of this parameter is $false, users that are assigned different GALs appear as internal recipients.
 
-The default value is $false. Note that this parameter has no effect if your organization doesn't use address book policies, or if the address book policy routing agent isn't installed and enabled. Also note that changing the value of this parameter may take up to 30 minutes to take effect. For more information about address book policies, see [Address book policies in Exchange Server](https://learn.microsoft.com/Exchange/email-addresses-and-address-books/address-book-policies/address-book-policies).
+The default value is $false. This parameter has no effect if your organization doesn't use address book policies, or if the address book policy routing agent isn't installed and enabled. Also note that changing the value of this parameter might take up to 30 minutes to take effect. For more information about address book policies, see [Address book policies in Exchange Server](https://learn.microsoft.com/Exchange/email-addresses-and-address-books/address-book-policies/address-book-policies).
 
 ```yaml
 Type: Boolean
@@ -265,7 +265,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
 
-The ConvertDisclaimerWrapperToEml parameter specifies whether the original message will be added as a TNEF attachment or a regular EML attachment to a disclaimer when all of the following are true:
+The ConvertDisclaimerWrapperToEml parameter specifies whether the original message is added as a TNEF attachment or a regular EML attachment to a disclaimer when all of the following are true:
 
 - Message is sent to an external user.
 - The sender has signed the message.
@@ -423,7 +423,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The valid input range for this parameter is from 0 through 2147483647 bytes. If you specify a value of 0, only the original message headers are included in the external DSN message.
 
@@ -463,7 +463,7 @@ Accept wildcard characters: False
 
 The ExternalDsnSendHtml parameter specifies whether external DSN messages should be HTML or plain text. Valid values are:
 
-- $true: External DSNs are HTML. This is the default value.
+- $true: External DSNs are HTML. This value is the default.
 - $false: External DSNs are plain text.
 
 ```yaml
@@ -573,7 +573,7 @@ The HeaderPromotionModeSetting parameter specifies whether named properties are
 
 - MustCreate: Exchange creates a named property for each new custom X-header.
 - MayCreate: Exchange creates a named property for each new custom X-header on messages received from authenticated senders. No named properties are created for custom X-headers on messages received from unauthenticated senders.
-- NoCreate: Exchange won't create any named properties based on custom X-headers on incoming messages. This is the default value.
+- NoCreate: Exchange doesn't create any named properties based on custom X-headers on incoming messages. This value is the default.
 
 ```yaml
 Type: HeaderPromotionMode
@@ -656,7 +656,7 @@ When you enter a value, qualify the value with one of the following units:
 - MB (megabytes)
 - GB (gigabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The valid input range for this parameter is from 0 through 2147483647 bytes. If you specify a value of 0, only the original message headers are included in the internal DSN message.
 
@@ -696,7 +696,7 @@ Accept wildcard characters: False
 
 The InternalDsnSendHtml parameter specifies whether internal DSN messages should be HTML or plain text. Valid values are:
 
-- $true: Internal DSNs are HTML. This is the default value.
+- $true: Internal DSNs are HTML. This value is the default.
 - $false: Internal DSNs are plain text.
 
 ```yaml
@@ -779,7 +779,7 @@ Accept wildcard characters: False
 
 This parameter is available only in Exchange Server 2010.
 
-The LegacyJournalingMigrationEnabled parameter specifies whether journal messages generated in Microsoft Exchange Server 2003 will be reformatted by Exchange 2010.
+The LegacyJournalingMigrationEnabled parameter specifies whether journal messages generated in Microsoft Exchange Server 2003 is reformatted by Exchange 2010.
 
 The default value is $false.
 
@@ -855,7 +855,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 To enable the transport dumpster, the value of the MaxDumpsterSizePerDatabase parameter must be greater than 0, and the value of the MaxDumpsterTime parameter must be greater than 00:00:00.
 
@@ -918,7 +918,7 @@ When you enter a value, qualify the value with one of the following units:
 - MB (megabytes)
 - GB (gigabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 A valid value is a number up to 1.999999 gigabytes (2147482624 bytes) or the value unlimited.
 
@@ -1027,7 +1027,7 @@ When you enter a value, qualify the value with one of the following units:
 - MB (megabytes)
 - GB (gigabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 A valid value is a number up to 1.999999 gigabytes (2147482624 bytes) or the value unlimited.
 
@@ -1061,7 +1061,7 @@ The default value is 1.00:00:00 or 1 day.
 
 A valid value is from 12 hours (0.12:00:00) to 24 hours (1.00:00:00).
 
-Queued messages typically expire after 24 hours, resulting in an NDR for failed delivery. If you change this value, the NDR will be sent at the new applicable time.
+Queued messages typically expire after 24 hours, resulting in an NDR for failed delivery. If you change this value, the NDR is sent at the new applicable time.
 
 ```yaml
 Type: EnhancedTimeSpan
@@ -1084,7 +1084,7 @@ This parameter is available only in the cloud-based service.
 The PreventDuplicateJournalingEnabled parameter prevents duplicate journaling reports that can occur when messages are processed by both on-premises and cloud journaling agents. Valid values are:
 
 - $true: Ensure that journaling messages aren't duplicated in hybrid environments.
-- $false: Journaling messages might be duplicated in hybrid environments. This is the default value.
+- $false: Journaling messages might be duplicated in hybrid environments. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -1129,7 +1129,7 @@ This parameter is available only in on-premises Exchange.
 The RejectMessageOnShadowFailure parameter specifies whether to accept or reject messages when shadow copies of the messages can't be created. Valid values are:
 
 - $true: Messages are rejected with the SMTP code 450 4.5.1. Use this value only if you have multiple Mailbox servers in a database availability group (DAG) or in an Active Directory site where shadow copies of the messages can be created.
-- $false: Messages are accepted without making shadow copies. This is the default value.
+- $false: Messages are accepted without making shadow copies. This value is the default.
 
 The number of attempts to make a shadow copy of the message and where to make the shadow copy are controlled by the MaxRetriesForLocalSiteShadow, MaxRetriesForRemoteSiteShadow, and ShadowMessagePreferenceSetting parameter settings.
 
@@ -1454,7 +1454,7 @@ The SmtpClientAuthenticationDisabled parameter specifies whether to disable auth
 
 Valid values for this parameter are:
 
-- $true: Authenticated SMTP is disabled. This is the default value for organizations created after January 2020.
+- $true: Authenticated SMTP is disabled. This value is the default for organizations created after January 2020.
 - $false: Authenticated SMTP is enabled.
 
 The corresponding parameter that controls authenticated SMTP on individual mailboxes is the SmtpClientAuthenticationDisabled parameter on the Set-CASMailbox cmdlet. The default mailbox value is blank ($null), which means the mailbox setting is controlled by this organizational setting.
@@ -1541,7 +1541,7 @@ To enter multiple values and overwrite any existing entries, use the following s
 
 To add or remove one or more values without affecting any existing entries, use the following syntax: `@{Add="Value1","Value2"...; Remove="Value3","Value4"...}`.
 
-Multiple domains may be separated by commas. The wildcard character (\*) isn't supported in the domains listed in the TLSSendDomainSecureList parameter or in the TLSReceiveSecureList parameter. The default values for both parameters are an empty list ({}).
+Multiple domains might be separated by commas. The wildcard character (\*) isn't supported in the domains listed in the TLSSendDomainSecureList parameter or in the TLSReceiveSecureList parameter. The default values for both parameters are an empty list ({}).
 
 ```yaml
 Type: MultiValuedProperty
@@ -1570,7 +1570,7 @@ When you enter a value, qualify the value with one of the following units:
 - MB (megabytes)
 - GB (gigabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 In Exchange Online, Exchange 2019, and Exchange 2016, the default value is 1 MB (1,048,576 bytes). In Exchange 2013, the default value is 150 KB (153,600 bytes).
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-TransportRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-TransportRule.md
index 4f707e0ab4..51b8d54495 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-TransportRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-TransportRule.md
@@ -13,7 +13,7 @@ title: Set-TransportRule
 # Set-TransportRule
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-TransportRule cmdlet to modify existing transport rules (mail flow rules) in your organization.
 
@@ -210,9 +210,9 @@ Set-TransportRule [-Identity] <RuleIdParameter>
 ## DESCRIPTION
 In on-premises Exchange organizations, rules created on Mailbox servers are stored in Active Directory. All Mailbox servers in the organization have access to the same set of rules. On Edge Transport servers, rules are saved in the local copy of Active Directory Lightweight Directory Services (AD LDS). Rules aren't shared or replicated between Edge Transport servers or between Mailbox servers and Edge Transport servers. Also, some conditions and actions are exclusive to each server role.
 
-The search for words or text patterns in the subject or other header fields in the message occurs after the message has been decoded from the MIME content transfer encoding method that was used to transmit the binary message between SMTP servers in ASCII text. You can't use conditions or exceptions to search for the raw (typically, Base64) encoded values of the subject or other header fields in messages.
+The search for words or text patterns in the subject or other header fields in the message occurs after the message is decoded from the MIME content transfer encoding method that was used to transmit the binary message between SMTP servers in ASCII text. You can't use conditions or exceptions to search for the raw (typically, Base64) encoded values of the subject or other header fields in messages.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -251,7 +251,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
 
-The ActivationDate parameter specifies when the rule starts processing messages. The rule won't take any action on messages until the specified date/time.
+The ActivationDate parameter specifies when the rule starts processing messages. The rule doesn't take any action on messages until the specified date/time.
 
 Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
 
@@ -331,7 +331,7 @@ In on-premises Exchange, this condition is available only on Mailbox servers.
 
 The ADComparisonOperator parameter specifies the comparison operator for the ADComparisonAttribute parameter. Valid values are:
 
-- Equal (This is the default value)
+- Equal (default value)
 - NotEqual
 
 ```yaml
@@ -702,7 +702,7 @@ In on-premises Exchange, this action is available only on Mailbox servers.
 
 The ApplyHtmlDisclaimerFallbackAction parameter specifies what to do if the HTML disclaimer can't be applied to a message (for example, encrypted or signed messages where the contents can't be altered). Valid values are:
 
-- Wrap: This is the default value. A new message is created and the original message is added to it as an attachment. The disclaimer text is added to the new message, which is delivered to the recipients.
+- Wrap: This value is the default. A new message is created and the original message is added to it as an attachment. The disclaimer text is added to the new message, which is delivered to the recipients.
 
   If you want other rules to examine and act on the original message (which is now an attachment in the new message), make sure those rules are applied _before_ the disclaimer rule by using a lower priority for the disclaimer rule and higher priority for other rules.
 
@@ -737,7 +737,7 @@ In on-premises Exchange, this action is available only on Mailbox servers.
 
 The ApplyHtmlDisclaimerLocation parameter specifies where to insert the HTML disclaimer text in the body of messages. Valid values are:
 
-- Append: The disclaimer is added to the end of the message body. This is the default value.
+- Append: The disclaimer is added to the end of the message body. This value is the default.
 - Prepend: The disclaimer is inserted at the beginning of the message body.
 
 If you don't use this parameter with the ApplyHtmlDisclaimerText parameter, the default value Append is used.
@@ -1146,9 +1146,9 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
-The embedded images are treated as attachments (for example, messages with a picture in the signature); for this reason, we do not recommend using a very small value since unexpected messages will be blocked.
+The embedded images are treated as attachments (for example, messages with a picture in the signature). For this reason, we don't recommend using a very small value, since unexpected messages are blocked.
 
 ```yaml
 Type: ByteQuantifiedSize
@@ -1505,7 +1505,7 @@ In on-premises Exchange, this exception is available only on Mailbox servers.
 
 The ExceptIfADComparisonOperator parameter specifies the comparison operator for the ExceptIfADComparisonAttribute parameter. Valid values are:
 
-- Equal (This is the default value)
+- Equal (default value)
 - NotEqual
 
 ```yaml
@@ -2047,7 +2047,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 ```yaml
 Type: ByteQuantifiedSize
@@ -2568,7 +2568,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 ```yaml
 Type: ByteQuantifiedSize
@@ -2593,7 +2593,7 @@ In on-premises Exchange, this exception is available only on Mailbox servers.
 The ExceptIfMessageTypeMatches parameter specifies an exception that looks for messages of the specified type. Valid values are:
 
 - OOF: Auto-reply messages configured by the user.
-- AutoForward: Messages automatically forwarded to an alternative recipient. In Exchange Online, if the message has been forwarded using [mailbox forwarding](https://learn.microsoft.com/exchange/recipients-in-exchange-online/manage-user-mailboxes/configure-email-forwarding) (also known as SMTP forwarding), this exception **will not** match during mail flow rule evaluation.
+- AutoForward: Messages automatically forwarded to an alternative recipient. In Exchange Online, if the message is forwarded using [mailbox forwarding](https://learn.microsoft.com/exchange/recipients-in-exchange-online/manage-user-mailboxes/configure-email-forwarding) (also known as SMTP forwarding), this exception **does not** match during mail flow rule evaluation.
 - Encrypted: S/MIME encrypted messages. In thin clients like Outlook on the web, encryption as a message type is currently not supported.
 - Calendaring: Meeting requests and responses.
 - PermissionControlled: Messages that have specific permissions configured using Office 365 Message Encryption (OME), Rights Management, and sensitivity labels (with encryption).
@@ -3275,7 +3275,7 @@ Accept wildcard characters: False
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
-The ExpiryDate parameter specifies when this rule will stop processing messages. The rule won't take any action on messages after the specified date/time.
+The ExpiryDate parameter specifies when this rule stops processing messages. The rule doesn't take any action on messages after the specified date/time.
 
 Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM".
 
@@ -3681,10 +3681,10 @@ In on-premises Exchange, this action is available only on Mailbox servers.
 The IncidentReportContent parameter specifies the message properties that are included in the incident report. Valid values are:
 
 - Sender: The sender of the message.
-- Recipients: The recipients in the To field of the message. Only the first 10 recipients are displayed in the incident report. If there are more than 10 recipients, the remaining number of recipients will be displayed.
+- Recipients: The recipients in the To field of the message. Only the first 10 recipients are displayed in the incident report. If there are more than 10 recipients, the remaining number of recipients is displayed.
 - Subject: The Subject field of the message.
-- CC: The recipients in the Cc field of the message. Only the first 10 recipients are displayed in the incident report. If there are more than 10 recipients, the remaining number of recipients will be displayed.
-- BCC: The recipients in the Bcc field of the message. Only the first 10 recipients are displayed in the incident report. If there are more than 10 recipients, the remaining number of recipients will be displayed.
+- CC: The recipients in the Cc field of the message. Only the first 10 recipients are displayed in the incident report. If there are more than 10 recipients, the remaining number of recipients is displayed.
+- BCC: The recipients in the Bcc field of the message. Only the first 10 recipients are displayed in the incident report. If there are more than 10 recipients, the remaining number of recipients is displayed.
 - Severity: The audit severity of the rule that was triggered. If the message was processed by more than one rule, the highest severity is displayed.
 - RuleDetections: The list of rules that the message triggered.
 - FalsePositive: The false positive if the sender marked the message as a false positive for a PolicyTip.
@@ -3715,13 +3715,13 @@ Accept wildcard characters: False
 
 This parameter is available only in Exchange Server 2013.
 
-This parameter has been deprecated and is no longer used. Use the IncidentReportContent parameter instead. The value AttachOriginalMail on the IncidentReportContent parameter is equivalent to setting this parameter to the value IncludeOriginalMail.
+This parameter is deprecated and no longer used. Use the IncidentReportContent parameter instead. The value AttachOriginalMail on the IncidentReportContent parameter is equivalent to setting this parameter to the value IncludeOriginalMail.
 
 This parameter specifies an action or part of an action for the rule.
 
 In on-premises Exchange, this action is available only on Mailbox servers.
 
-The IncidentReportOriginalMail parameter specifies whether to include the original message with the incident report. This parameter is used together with the GenerateIncidentReport parameter. Valid values are:
+The IncidentReportOriginalMail parameter specifies whether to include the original message with the incident report. Use this parameter with the GenerateIncidentReport parameter. Valid values are:
 
 - IncludeOriginalMail
 - DoNotIncludeOriginalMail (this is the default value)
@@ -3876,7 +3876,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 ```yaml
 Type: ByteQuantifiedSize
@@ -3901,7 +3901,7 @@ In on-premises Exchange, this condition is available only on Mailbox servers.
 The MessageTypeMatches parameter specifies a condition that looks for messages of the specified type. Valid values are:
 
 - OOF: Auto-reply messages configured by the user.
-- AutoForward: Messages automatically forwarded to an alternative recipient. In Exchange Online, if the message has been forwarded using [mailbox forwarding](https://learn.microsoft.com/exchange/recipients-in-exchange-online/manage-user-mailboxes/configure-email-forwarding) (also known as SMTP forwarding), this condition **will not** match during mail flow rule evaluation.
+- AutoForward: Messages automatically forwarded to an alternative recipient. In Exchange Online, if the message is forwarded using [mailbox forwarding](https://learn.microsoft.com/exchange/recipients-in-exchange-online/manage-user-mailboxes/configure-email-forwarding) (also known as SMTP forwarding), this condition **does not** match during mail flow rule evaluation.
 - Encrypted: S/MIME encrypted messages. In thin clients like Outlook on the web, encryption as a message type is currently not supported.
 - Calendaring: Meeting requests and responses.
 - PermissionControlled: Messages that have specific permissions configured using Office 365 Message Encryption (OME), Rights Management, and sensitivity labels (with encryption).
@@ -3928,9 +3928,9 @@ Accept wildcard characters: False
 
 The Mode parameter specifies how the rule operates. Valid values are:
 
-- Audit: The actions that the rule would have taken are written to the message tracking log, but no action that impacts message delivery is taken on the message. The GenerateIncidentReport action occurs.
-- AuditAndNotify: The actions that the rule would have taken are written to the message tracking log, but no action that impacts message delivery is taken on the message. The GenerateIncidentReport and GenerateNotification actions occur.
-- Enforce: All actions specified in the rule are taken. This is the default value.
+- Audit: The actions that the rule would have taken are written to the message tracking log, but no action that affects message delivery is taken on the message. The GenerateIncidentReport action occurs.
+- AuditAndNotify: The actions that the rule would have taken are written to the message tracking log, but no action that affects message delivery is taken on the message. The GenerateIncidentReport and GenerateNotification actions occur.
+- Enforce: All actions specified in the rule are taken. This value is the default.
 
 ```yaml
 Type: RuleMode
@@ -4044,7 +4044,7 @@ For all values except NotifyOnly, you can specify an enhanced status code and a
 
 If you use this parameter, you also need to specify a condition that looks for sensitive information types in messages by using the MessageContainsDataClassifications parameter.
 
-This action is applicable to messages sent by internal users only. External senders will not receive notifications.
+This action applies to messages sent by internal users only. External senders don't receive notifications.
 
 ```yaml
 Type: NotifySenderType
@@ -4304,7 +4304,7 @@ This parameter is available only in the cloud-based service.
 The RecipientAddressType parameter specifies how conditions and exceptions check recipient email addresses. Valid values are:
 
 - Original: The rule checks the original address in the To field of the message.
-- Resolved: The rule checks the recipient's primary SMTP email address without checking any proxy addresses. This is the default value.
+- Resolved: The rule checks the recipient's primary SMTP email address without checking any proxy addresses. This value is the default.
 
 ```yaml
 Type: RecipientAddressType
@@ -4609,7 +4609,7 @@ Accept wildcard characters: False
 
 The RuleErrorAction parameter specifies what to do if rule processing can't be completed on messages. Valid values are:
 
-- Ignore: The message is sent anyway. This is the default value.
+- Ignore: The message is sent anyway. This value is the default.
 - Defer: The message is deferred so the rules engine can attempt to process the message again.
 
 ```yaml
@@ -4631,7 +4631,7 @@ Accept wildcard characters: False
 The RuleSubType parameter specifies the rule type. Valid values are:
 
 - Dlp: The rule is associated with a DLP policy. This value is meaningful only in on-premises Exchange.
-- None: The rule is a regular transport rule. This is the default value.
+- None: The rule is a regular transport rule. This value is the default.
 
 ```yaml
 Type: RuleSubType
@@ -4792,7 +4792,7 @@ Accept wildcard characters: False
 
 The SenderAddressLocation parameter specifies where to look for sender addresses in conditions and exceptions that examine sender email addresses. Valid values are:
 
-- Header: Only examine senders in the message headers. For example, in on-premises Exchange the the From, Sender, or Reply-To fields. In Exchange Online, the From field only. This is the default value, and is the way rules worked before Exchange 2013 Cumulative Update 1 (CU1).
+- Header: Only examine senders in the message headers. For example, in on-premises Exchange the the From, Sender, or Reply-To fields. In Exchange Online, the From field only. This value is the default, and is the way rules worked before Exchange 2013 Cumulative Update 1 (CU1).
 - Envelope: Only examine senders from the message envelope (the MAIL FROM value that was used in the SMTP transmission, which is typically stored in the Return-Path field).
 - HeaderOrEnvelope: Examine senders in the message header and the message envelope.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-TransportServer.md b/exchange/exchange-ps/ExchangePowerShell/Set-TransportServer.md
index b433ad22ca..73dbb0b6d9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-TransportServer.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-TransportServer.md
@@ -123,7 +123,7 @@ Set-TransportServer [-Identity] <ServerIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -209,7 +209,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value of the ActiveUserStatisticsLogMaxFileSize parameter must be less than or equal to the value of the ActiveUserStatisticsLogMaxDirectorySize parameter. The valid input range for either parameter is from 1 through 9223372036854775807 bytes. If you enter a value of unlimited, no size limit is imposed on the server statistics log directory.
 
@@ -239,7 +239,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value of the ActiveUserStatisticsLogMaxFileSize parameter must be less than or equal to the value of the ActiveUserStatisticsLogMaxDirectorySize parameter. The valid input range for either parameter is from 1 through 9223372036854775807 bytes. If you enter a value of unlimited, no size limit is imposed on the server statistics log files.
 
@@ -332,7 +332,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value of the AgentLogMaxFileSize parameter must be less than or equal to the value of the AgentLogMaxDirectorySize parameter. If you enter a value of unlimited, no size limit is imposed on the agent log directory.
 
@@ -362,7 +362,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value of the AgentLogMaxFileSize parameter must be less than or equal to the value of the AgentLogMaxDirectorySize parameter. If you enter a value of unlimited, no size limit is imposed on the agent log files.
 
@@ -491,7 +491,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value of the ConnectivityLogMaxFileSize parameter must be less than or equal to the value of the ConnectivityLogMaxDirectorySize parameter. The valid input range for either parameter is from 1 through 9223372036854775807 bytes. If you enter a value of unlimited, no size limit is imposed on the connectivity log directory.
 
@@ -521,7 +521,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value of the ConnectivityLogMaxFileSize parameter must be less than or equal to the value of the ConnectivityLogMaxDirectorySize parameter. The valid input range for either parameter is from 1 through 9223372036854775807 bytes. If you enter a value of unlimited, no size limit is imposed on the connectivity log files.
 
@@ -658,7 +658,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value of the DnsLogMaxFileSize parameter must be less than or equal to the value of the DnsLogMaxDirectorySize parameter. If you enter a value of unlimited, no size limit is imposed on the DNS log directory.
 
@@ -688,7 +688,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value of the DnsLogMaxFileSize parameter must be less than or equal to the value of the DnsLogMaxDirectorySize parameter. If you enter a value of unlimited, no size limit is imposed on the DNS log files.
 
@@ -764,7 +764,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-The ExternalDNSAdapterGuid parameter specifies the network adapter that has the DNS settings used for DNS lookups of destinations that exist outside the Exchange organization. The concept of an external network adapter and an internal network adapter is only applicable in a multi-homed Exchange server environment. When no particular network adapter is specified as the network adapter for external DNS lookups, the value of the ExternalDNSAdapterGuid parameter is 00000000-0000-0000-0000-000000000000, and external DNS lookups are performed by using the DNS settings of any available network adapter. You may enter the GUID of a specific network adapter to use for external DNS lookups. The default value of the ExternalDNSAdapterGuid parameter is 00000000-0000-0000-0000-000000000000.
+The ExternalDNSAdapterGuid parameter specifies the network adapter that has the DNS settings used for DNS lookups of destinations that exist outside the Exchange organization. The concept of an external network adapter and an internal network adapter is only applicable in a multi-homed Exchange server environment. When no particular network adapter is specified as the network adapter for external DNS lookups, the value of the ExternalDNSAdapterGuid parameter is 00000000-0000-0000-0000-000000000000, and external DNS lookups are performed by using the DNS settings of any available network adapter. You might enter the GUID of a specific network adapter to use for external DNS lookups. The default value of the ExternalDNSAdapterGuid parameter is 00000000-0000-0000-0000-000000000000.
 
 If the value of the ExternalDNSAdapterEnabled parameter is set to $false, the value of the ExternalDNSAdapterGuid parameter is ignored, and the list of DNS servers from the ExternalDNSServers parameter is used.
 
@@ -862,7 +862,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-The InternalDNSAdapterGuid parameter specifies the network adapter that has the DNS settings used for DNS lookups of servers that exist inside the Exchange organization. The concept of an internal network adapter and an external network adapter is only applicable in a multi-homed Exchange server environment. When no particular network adapter is specified as the network adapter for external DNS lookups, the value of the InternalDNSAdapterGuid parameter is 00000000-0000-0000-0000-000000000000, and internal DNS lookups are performed by using the DNS settings of any available network adapter. You may enter the GUID of a specific network adapter to use for internal DNS lookups. The default value of the InternalDNSAdapterGuid parameter is 00000000-0000-0000-0000-000000000000.
+The InternalDNSAdapterGuid parameter specifies the network adapter that has the DNS settings used for DNS lookups of servers that exist inside the Exchange organization. The concept of an internal network adapter and an external network adapter is only applicable in a multi-homed Exchange server environment. When no particular network adapter is specified as the network adapter for external DNS lookups, the value of the InternalDNSAdapterGuid parameter is 00000000-0000-0000-0000-000000000000, and internal DNS lookups are performed by using the DNS settings of any available network adapter. You might enter the GUID of a specific network adapter to use for internal DNS lookups. The default value of the InternalDNSAdapterGuid parameter is 00000000-0000-0000-0000-000000000000.
 
 If the value of the InternalDNSAdapterEnabled parameter is set to $false, the value of the InternalDNSAdapterGuid parameter is ignored, and the list of DNS servers from the InternalDNSServers parameter is used.
 
@@ -1017,7 +1017,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value of the IrmLogMaxFileSize parameter must be less than or equal to the value of the IrmLogMaxDirectorySize parameter. The valid input range for either parameter is from 1 through 9223372036854775807 bytes. If you enter a value of unlimited, no size limit is imposed on the IRM log directory.
 
@@ -1047,7 +1047,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value of the IrmLogMaxFileSize parameter must be less than or equal to the value of the IrmLogMaxDirectorySize parameter. The valid input range for either parameter is from 1 through 9223372036854775807 bytes. If you enter a value of unlimited, no size limit is imposed on the IRM log files.
 
@@ -1067,7 +1067,9 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-The IrmLogPath parameter specifies the default IRM log directory location. The default location is %ExchangeInstallPath%Logging\\IRMLogs. If you set the value of the IrmLogPath parameter to $null, you effectively disable IRM logging. However, if you set the value of the IrmLogPath parameter to $null when the value of the IrmLogEnabled attribute is $true, Exchange will log errors in the Application event log. The preferred way for disabling IRM logging is to set the IrmLogEnabled to $false.
+The IrmLogPath parameter specifies the default IRM log directory location. The default location is %ExchangeInstallPath%Logging\\IRMLogs.
+
+If you set the value of this parameter to $null, you effectively disable IRM logging. However, if the value of the IrmLogEnabled parameter is $true, Exchange adds errors to the Application event log. The preferred way to disable IRM logging is to set the IrmLogEnabled parameter to $false.
 
 ```yaml
 Type: LocalLongFullPath
@@ -1275,7 +1277,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value of the MessageTrackingLogMaxFileSize parameter must be less than or equal to the value of the MessageTrackingLogMaxDirectorySize parameter. The valid input range for either parameter is from 1 through 9223372036854775807 bytes. If you enter a value of unlimited, no size limit is imposed on the message tracking log directory.
 
@@ -1304,7 +1306,7 @@ When you enter a value, qualify the value with one of the following units:
 - MB (megabytes)
 - GB (gigabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value of the MessageTrackingLogMaxFileSize parameter must be less than or equal to the value of the MessageTrackingLogMaxDirectorySize parameter. The valid input range for either parameter is from 1 through 4294967296 bytes (4 GB). If you enter a value of unlimited, no size limit is imposed on the message tracking log files.
 
@@ -1391,7 +1393,7 @@ When you enter a value, qualify the value with one of the following units:
 - MB (megabytes)
 - GB (gigabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The valid input range for this parameter is from 32768 through 2147483647 bytes.
 
@@ -1514,7 +1516,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-The PipelineTracingSenderAddress parameter specifies the sender address that invokes pipeline tracing. Only messages from this address generate pipeline tracing output. The address can be either inside or outside the Exchange organization. Depending on your requirements, you may have to set this parameter to different sender addresses and send new messages to start the transport agents or routes that you want to test. The default value of this parameter is $null.
+The PipelineTracingSenderAddress parameter specifies the sender address that invokes pipeline tracing. Only messages from this address generate pipeline tracing output. The address can be either inside or outside the Exchange organization. Depending on your requirements, you might have to set this parameter to different sender addresses and send new messages to start the transport agents or routes that you want to test. The default value of this parameter is $null.
 
 ```yaml
 Type: SmtpAddress
@@ -1622,7 +1624,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value of the QueueLogMaxFileSize parameter must be less than or equal to the value of the QueueLogMaxDirectorySize parameter. The valid input range for either parameter is from 1 through 9223372036854775807 bytes. If you enter a value of unlimited, no size limit is imposed on the queue log directory.
 
@@ -1652,7 +1654,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value of the QueueLogMaxFileSize parameter must be less than or equal to the value of the QueueLogMaxDirectorySize parameter. The valid input range for either parameter is from 1 through 9223372036854775807 bytes. If you enter a value of unlimited, no size limit is imposed on the queue log files.
 
@@ -1722,7 +1724,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value of the ReceiveProtocolLogMaxFileSize parameter must be less than or equal to the value of the ReceiveProtocolLogMaxDirectorySize parameter. The valid input range for either parameter is from 1 through 9223372036854775807 bytes. If you enter a value of unlimited, no size limit is imposed on the Receive connector protocol log directory.
 
@@ -1752,7 +1754,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value of the ReceiveProtocolLogMaxFileSize parameter must be less than or equal to the value of the ReceiveProtocolLogMaxDirectorySize parameter. The valid input range for either parameter is from 1 through 9223372036854775807 bytes. If you enter a value of unlimited, no size limit is imposed on the Receive connector protocol log files.
 
@@ -1831,7 +1833,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-The RootDropDirectoryPath parameter specifies the top-level location of the Drop directory used by all Foreign connectors defined in the Transport service on a Mailbox server. The value of the RootDropDirectoryPath parameter may be a local path, or a Universal Naming Convention (UNC) path to a remote server. By default, the RootDropDirectoryPath parameter is blank. This indicates the value of RootDropDirectoryPath is the Exchange installation folder. The RootDropDirectoryPath parameter is used with the DropDirectory parameter in the Set-ForeignConnector cmdlet to specify the location for outgoing messages going to the address spaces defined on the Foreign connector.
+The RootDropDirectoryPath parameter specifies the top-level location of the Drop directory used by all Foreign connectors defined in the Transport service on a Mailbox server. The value of the RootDropDirectoryPath parameter might be a local path, or a Universal Naming Convention (UNC) path to a remote server. By default, the RootDropDirectoryPath parameter is blank. This indicates the value of RootDropDirectoryPath is the Exchange installation folder. The RootDropDirectoryPath parameter is used with the DropDirectory parameter in the Set-ForeignConnector cmdlet to specify the location for outgoing messages going to the address spaces defined on the Foreign connector.
 
 ```yaml
 Type: String
@@ -1881,7 +1883,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The valid input range for this parameter is from 1 through 9223372036854775807 bytes. If you enter a value of unlimited, no size limit is imposed on the routing table log directory.
 
@@ -1956,7 +1958,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value of the SendProtocolLogMaxFileSize parameter must be less than or equal to the value of the SendProtocolLogMaxDirectorySize parameter. The valid input range for either parameter is from 1 through 9223372036854775807 bytes. If you enter a value of unlimited, no size limit is imposed on the Send connector protocol log directory.
 
@@ -1986,7 +1988,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value of the SendProtocolLogMaxFileSize parameter must be less than or equal to the value of the SendProtocolLogMaxDirectorySize parameter. The valid input range for either parameter is from 1 through 9223372036854775807 bytes. If you enter a value of unlimited, no size limit is imposed on the Send connector protocol log files.
 
@@ -2180,7 +2182,7 @@ Accept wildcard characters: False
 
 The UseDowngradedExchangeServerAuth parameter specifies whether the Generic Security Services application programming interface (GSSAPI) authentication method is used on connections where Transport Layer Security (TLS) is disabled.
 
-Normally, TLS is required for connections between the Transport services on Mailbox servers in your organization. On TLS secured connections, Kerberos authentication is used by default. However, there may be scenarios where you need to disable TLS between specific Transport services in your organization. When you do that, you need to set this parameter to $true to provide an alternative authentication method. The default value is $false. You shouldn't set this value to $true unless it's absolutely required.
+Normally, TLS is required for connections between the Transport services on Mailbox servers in your organization. On TLS secured connections, Kerberos authentication is used by default. However, there might be scenarios where you need to disable TLS between specific Transport services in your organization. When you do that, you need to set this parameter to $true to provide an alternative authentication method. The default value is $false. You shouldn't set this value to $true unless it's absolutely required.
 
 If you set this parameter to $true, you also need to create a specific Receive connector to service the non-TLS connections. This Receive connector must have remote IP address ranges specified to ensure that it's only used for non-TLS connections. You also must set the SuppressXAnonymousTls attribute of the Receive connector to $true.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-TransportService.md b/exchange/exchange-ps/ExchangePowerShell/Set-TransportService.md
index 676be05f31..60535549df 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-TransportService.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-TransportService.md
@@ -165,7 +165,7 @@ Set-TransportService [-Identity] <ServerIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -253,7 +253,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value of the ActiveUserStatisticsLogMaxFileSize parameter must be less than or equal to the value of the ActiveUserStatisticsLogMaxDirectorySize parameter. The valid input range for either parameter is from 1 through 9223372036854775807 bytes. If you enter a value of unlimited, no size limit is imposed on the server statistics log directory.
 
@@ -283,7 +283,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value of the ActiveUserStatisticsLogMaxFileSize parameter must be less than or equal to the value of the ActiveUserStatisticsLogMaxDirectorySize parameter. The valid input range for either parameter is from 1 through 9223372036854775807 bytes. If you enter a value of unlimited, no size limit is imposed on the server statistics log files.
 
@@ -371,7 +371,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value of the AgentLogMaxFileSize parameter must be less than or equal to the value of the AgentLogMaxDirectorySize parameter. If you enter a value of unlimited, no size limit is imposed on the agent log directory.
 
@@ -401,7 +401,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value of the AgentLogMaxFileSize parameter must be less than or equal to the value of the AgentLogMaxDirectorySize parameter. If you enter a value of unlimited, no size limit is imposed on the agent log files.
 
@@ -530,7 +530,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value of the ConnectivityLogMaxFileSize parameter must be less than or equal to the value of the ConnectivityLogMaxDirectorySize parameter. The valid input range for either parameter is from 1 through 9223372036854775807 bytes. If you enter a value of unlimited, no size limit is imposed on the connectivity log directory.
 
@@ -560,7 +560,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value of the ConnectivityLogMaxFileSize parameter must be less than or equal to the value of the ConnectivityLogMaxDirectorySize parameter. The valid input range for either parameter is from 1 through 9223372036854775807 bytes. If you enter a value of unlimited, no size limit is imposed on the connectivity log files.
 
@@ -692,7 +692,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value of the DnsLogMaxFileSize parameter must be less than or equal to the value of the DnsLogMaxDirectorySize parameter. If you enter a value of unlimited, no size limit is imposed on the DNS log directory.
 
@@ -722,7 +722,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value of the DnsLogMaxFileSize parameter must be less than or equal to the value of the DnsLogMaxDirectorySize parameter. If you enter a value of unlimited, no size limit is imposed on the DNS log files.
 
@@ -798,7 +798,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-The ExternalDNSAdapterGuid parameter specifies the network adapter that has the DNS settings used for DNS lookups of destinations that exist outside the Exchange organization. The concept of an external network adapter and an internal network adapter is only applicable in a multi-homed Exchange server environment. When no particular network adapter is specified as the network adapter for external DNS lookups, the value of the ExternalDNSAdapterGuid parameter is 00000000-0000-0000-0000-000000000000, and external DNS lookups are performed by using the DNS settings of any available network adapter. You may enter the GUID of a specific network adapter to use for external DNS lookups. The default value of the ExternalDNSAdapterGuid parameter is 00000000-0000-0000-0000-000000000000.
+The ExternalDNSAdapterGuid parameter specifies the network adapter that has the DNS settings used for DNS lookups of destinations that exist outside the Exchange organization. The concept of an external network adapter and an internal network adapter is only applicable in a multi-homed Exchange server environment. When no particular network adapter is specified as the network adapter for external DNS lookups, the value of the ExternalDNSAdapterGuid parameter is 00000000-0000-0000-0000-000000000000, and external DNS lookups are performed by using the DNS settings of any available network adapter. You might enter the GUID of a specific network adapter to use for external DNS lookups. The default value of the ExternalDNSAdapterGuid parameter is 00000000-0000-0000-0000-000000000000.
 
 If the value of the ExternalDNSAdapterEnabled parameter is set to $false, the value of the ExternalDNSAdapterGuid parameter is ignored, and the list of DNS servers from the ExternalDNSServers parameter is used.
 
@@ -896,7 +896,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-The InternalDNSAdapterGuid parameter specifies the network adapter that has the DNS settings used for DNS lookups of servers that exist inside the Exchange organization. The concept of an internal network adapter and an external network adapter is only applicable in a multi-homed Exchange server environment. When no particular network adapter is specified as the network adapter for external DNS lookups, the value of the InternalDNSAdapterGuid parameter is 00000000-0000-0000-0000-000000000000, and internal DNS lookups are performed by using the DNS settings of any available network adapter. You may enter the GUID of a specific network adapter to use for internal DNS lookups. The default value of the InternalDNSAdapterGuid parameter is 00000000-0000-0000-0000-000000000000.
+The InternalDNSAdapterGuid parameter specifies the network adapter that has the DNS settings used for DNS lookups of servers that exist inside the Exchange organization. The concept of an internal network adapter and an external network adapter is only applicable in a multi-homed Exchange server environment. When no particular network adapter is specified as the network adapter for external DNS lookups, the value of the InternalDNSAdapterGuid parameter is 00000000-0000-0000-0000-000000000000, and internal DNS lookups are performed by using the DNS settings of any available network adapter. You might enter the GUID of a specific network adapter to use for internal DNS lookups. The default value of the InternalDNSAdapterGuid parameter is 00000000-0000-0000-0000-000000000000.
 
 If the value of the InternalDNSAdapterEnabled parameter is set to $false, the value of the InternalDNSAdapterGuid parameter is ignored, and the list of DNS servers from the InternalDNSServers parameter is used.
 
@@ -965,7 +965,7 @@ The IntraOrgConnectorProtocolLoggingLevel parameter enables or disables SMTP pro
 
 Valid values are:
 
-- None: Protocol logging is disabled for the intra-organization Send connector in the Transport service and in the Mailbox Transport Submission service. This is the default value.
+- None: Protocol logging is disabled for the intra-organization Send connector in the Transport service and in the Mailbox Transport Submission service. This value is the default.
 - Verbose: Protocol logging is enabled for the intra-organization Send connector in the Transport service and in the Mailbox Transport Submission service. The location of the log files is controlled by the SendProtocolLogPath parameter.
 
 ```yaml
@@ -1057,7 +1057,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value of the IrmLogMaxFileSize parameter must be less than or equal to the value of the IrmLogMaxDirectorySize parameter. The valid input range for either parameter is from 1 through 9223372036854775807 bytes. If you enter a value of unlimited, no size limit is imposed on the IRM log directory.
 
@@ -1087,7 +1087,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value of the IrmLogMaxFileSize parameter must be less than or equal to the value of the IrmLogMaxDirectorySize parameter. The valid input range for either parameter is from 1 through 9223372036854775807 bytes. If you enter a value of unlimited, no size limit is imposed on the IRM log files.
 
@@ -1107,7 +1107,9 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-The IrmLogPath parameter specifies the default IRM log directory location. The default location is %ExchangeInstallPath%Logging\\IRMLogs. If you set the value of the IrmLogPath parameter to $null, you effectively disable IRM logging. However, if you set the value of the IrmLogPath parameter to $null when the value of the IrmLogEnabled attribute is $true, Exchange will log errors in the Application event log. The preferred way for disabling IRM logging is to set the IrmLogEnabled to $false.
+The IrmLogPath parameter specifies the default IRM log directory location. The default value is %ExchangeInstallPath%IRMLogs.
+
+If you set the value of this parameter to $null, you effectively disable IRM logging. However, if the value of the IrmLogEnabled parameter is $true, Exchange adds errors to the Application event log. The preferred way to disable IRM logging is to set the IrmLogEnabled parameter to $false.
 
 ```yaml
 Type: LocalLongFullPath
@@ -1315,7 +1317,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value of the MessageTrackingLogMaxFileSize parameter must be less than or equal to the value of the MessageTrackingLogMaxDirectorySize parameter. The valid input range for either parameter is from 1 through 9223372036854775807 bytes. If you enter a value of unlimited, no size limit is imposed on the message tracking log directory.
 
@@ -1344,7 +1346,7 @@ When you enter a value, qualify the value with one of the following units:
 - MB (megabytes)
 - GB (gigabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value of the MessageTrackingLogMaxFileSize parameter must be less than or equal to the value of the MessageTrackingLogMaxDirectorySize parameter. The valid input range for either parameter is from 1 through 4294967296 bytes (4 GB). If you enter a value of unlimited, no size limit is imposed on the message tracking log files.
 
@@ -1431,7 +1433,7 @@ When you enter a value, qualify the value with one of the following units:
 - MB (megabytes)
 - GB (gigabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The valid input range for this parameter is from 32768 through 2147483647 bytes.
 
@@ -1549,7 +1551,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-The PipelineTracingSenderAddress parameter specifies the sender email address that invokes pipeline tracing. Only messages from this address generate pipeline tracing output. The address can be either inside or outside the Exchange organization. Depending on your requirements, you may have to set this parameter to different sender addresses and send new messages to start the transport agents or routes that you want to test. The default value of this parameter is $null.
+The PipelineTracingSenderAddress parameter specifies the sender email address that invokes pipeline tracing. Only messages from this address generate pipeline tracing output. The address can be either inside or outside the Exchange organization. Depending on your requirements, you might have to set this parameter to different sender addresses and send new messages to start the transport agents or routes that you want to test. The default value of this parameter is $null.
 
 ```yaml
 Type: SmtpAddress
@@ -1635,7 +1637,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value of the QueueLogMaxFileSize parameter must be less than or equal to the value of the QueueLogMaxDirectorySize parameter. The valid input range for either parameter is from 1 through 9223372036854775807 bytes. If you enter a value of unlimited, no size limit is imposed on the queue log directory.
 
@@ -1665,7 +1667,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value of the QueueLogMaxFileSize parameter must be less than or equal to the value of the QueueLogMaxDirectorySize parameter. The valid input range for either parameter is from 1 through 9223372036854775807 bytes. If you enter a value of unlimited, no size limit is imposed on the queue log files.
 
@@ -1761,7 +1763,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value of this parameter must be greater than or equal to the value of the ReceiveProtocolLogMaxFileSize parameter.
 
@@ -1795,7 +1797,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value of this parameter must be less than or equal to the value of the ReceiveProtocolLogMaxDirectorySize parameter.
 
@@ -2053,7 +2055,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-The RootDropDirectoryPath parameter specifies the top-level location of the Drop directory used by all Foreign connectors defined in the Transport service on a Mailbox server. The value of the RootDropDirectoryPath parameter may be a local path, or a Universal Naming Convention (UNC) path to a remote server. By default, the RootDropDirectoryPath parameter is blank. This indicates the value of RootDropDirectoryPath is the Exchange installation folder. The RootDropDirectoryPath parameter is used with the DropDirectory parameter in the Set-ForeignConnector cmdlet to specify the location for outgoing messages going to the address spaces defined on the Foreign connector.
+The RootDropDirectoryPath parameter specifies the top-level location of the Drop directory used by all Foreign connectors defined in the Transport service on a Mailbox server. The value of the RootDropDirectoryPath parameter might be a local path, or a Universal Naming Convention (UNC) path to a remote server. By default, the RootDropDirectoryPath parameter is blank. This indicates the value of RootDropDirectoryPath is the Exchange installation folder. The RootDropDirectoryPath parameter is used with the DropDirectory parameter in the Set-ForeignConnector cmdlet to specify the location for outgoing messages going to the address spaces defined on the Foreign connector.
 
 ```yaml
 Type: String
@@ -2103,7 +2105,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The valid input range for this parameter is from 1 through 9223372036854775807 bytes. If you enter a value of unlimited, no size limit is imposed on the routing table log directory.
 
@@ -2177,7 +2179,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value of this parameter must be greater than or equal to the value of the SendProtocolLogMaxFileSize parameter.
 
@@ -2211,7 +2213,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value of this parameter must be less than or equal to the value of the SendProtocolLogMaxDirectorySize parameter.
 
@@ -3000,7 +3002,7 @@ Accept wildcard characters: False
 
 The UseDowngradedExchangeServerAuth parameter specifies whether the Generic Security Services application programming interface (GSSAPI) authentication method is used on connections where Transport Layer Security (TLS) is disabled.
 
-Normally, TLS is required for connections between the Transport services on Mailbox servers in your organization. On TLS secured connections, Kerberos authentication is used by default. However, there may be scenarios where you need to disable TLS between specific Transport services in your organization. When you do that, you need to set this parameter to $true to provide an alternative authentication method. The default value is $false. You shouldn't set this value to $true unless it's absolutely required.
+Normally, TLS is required for connections between the Transport services on Mailbox servers in your organization. On TLS secured connections, Kerberos authentication is used by default. However, there might be scenarios where you need to disable TLS between specific Transport services in your organization. When you do that, you need to set this parameter to $true to provide an alternative authentication method. The default value is $false. You shouldn't set this value to $true unless it's absolutely required.
 
 If you set this parameter to $true, you also need to create a specific Receive connector to service the non-TLS connections. This Receive connector must have remote IP address ranges specified to ensure that it's only used for non-TLS connections. You also must set the SuppressXAnonymousTls attribute of the Receive connector to $true.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-UMAutoAttendant.md b/exchange/exchange-ps/ExchangePowerShell/Set-UMAutoAttendant.md
index 5845994472..8136c757d5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-UMAutoAttendant.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-UMAutoAttendant.md
@@ -75,7 +75,7 @@ The Set-UMAutoAttendant cmdlet changes or modifies the settings of an existing U
 
 After this task is completed, the parameters and values specified are configured on the UM auto attendant.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-UMCallAnsweringRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-UMCallAnsweringRule.md
index c0944e0ead..9c17c4a91e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-UMCallAnsweringRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-UMCallAnsweringRule.md
@@ -55,7 +55,7 @@ You can also specify the following actions:
 
 After this task is completed, the cmdlet sets the parameters and the values specified.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -94,10 +94,10 @@ This example performs the following actions on the call answering rule MyCallAns
 - Sets the priority of the call answering rule to 2.
 - Creates key mappings for the call answering rule.
 
-If the caller reaches the voice mail for the user and the status of the user is set to Busy, the caller can:
+If the caller reaches the voice mail for the user and the status of the user is set to Busy, the caller can take one of the following actions:
 
 - Press the 1 key and be transferred to a receptionist at extension 45678.
-- Press the 2 key and the Find Me feature will be used for urgent issues and ring extension 23456 first and then 45671.
+- Press the 2 key and the Find Me feature is used for urgent issues and ring extension 23456 first and then 45671.
 
 ### Example 5
 ```powershell
@@ -272,7 +272,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016
 
-The Mailbox parameter specifies the UM-enabled mailbox where the call answering rule will be changed. You can use any value that uniquely identifies the mailbox. For example:
+The Mailbox parameter specifies the UM-enabled mailbox that you want to modify. You can use any value that uniquely identifies the mailbox. For example:
 
 - Name
 - Alias
@@ -321,7 +321,9 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016
 
-The Priority parameter specified the order that the call answering rule will be evaluated against other existing call answering rules. Call answering rules are processed in order of increasing priority values. The priority must be unique between all call answering rules in the UM-enabled mailbox. The priority on the call answering rule must be between 1 (highest) and 9 (lowest). The default is 9.
+The Priority parameter specifies a priority value for the rule that determines the order of rule processing. A lower integer value indicates a higher priority, and rules can't have the same priority value.
+
+A valid value is an integer from 1 (highest priority) to 9 (lowest priority). The default value is 9.
 
 ```yaml
 Type: Int32
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-UMCallRouterSettings.md b/exchange/exchange-ps/ExchangePowerShell/Set-UMCallRouterSettings.md
index d7d8b0961c..70f693b2b4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-UMCallRouterSettings.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-UMCallRouterSettings.md
@@ -37,7 +37,7 @@ Set-UMCallRouterSettings [[-Server] <ServerIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -152,7 +152,11 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016
 
-The IPAddressFamily parameter specifies whether the UM IP gateway will use Internet Protocol version 4 (IPv4), IPv6, or both to communicate. If set to IPv4Only, the UM IP gateway only uses IPv4 to communicate. If set to IPv6Only, the UM IP gateway only uses IPv6. If set to Any, IPv6 is used first, and then if necessary, it falls back to IPv4. The default is Any.
+The IPAddressFamily parameter specifies the Internet Protocol (IP) version to use. Valid values are:
+
+- IPv4Only: The UM IP gateway uses only IPv4 to communicate.
+- IPv6Only: The UM IP gateway uses only IPv6.
+- Any: IPv6 is used first. If IPv6 isn't available, IPV4 is used. This value is the default.
 
 ```yaml
 Type: IPAddressFamily
@@ -188,7 +192,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016
 
-This parameter has been deprecated and is no longer used.
+This parameter is deprecated and no longer used.
 
 ```yaml
 Type: Int32
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-UMDialPlan.md b/exchange/exchange-ps/ExchangePowerShell/Set-UMDialPlan.md
index 66c7c50481..7443667f03 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-UMDialPlan.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-UMDialPlan.md
@@ -83,7 +83,7 @@ UM dial plans are important to the operation of Unified Messaging. Modifications
 
 After this task is completed, the parameters and values specified are configured on the UM dial plan.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -226,7 +226,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
 
-The AllowHeuristicADCallingLineIdResolution parameter specifies whether to allow calling line ID resolution using telephone number fields that may be configured in Active Directory. When this parameter is set to $true, the telephone numbers such as those defined in the Mobile or Home telephone number fields in Active Directory are used. Setting this parameter to $true allows for resolution of calling IDs for both UM-enabled and non-UM-enabled users. The default is $true. You may want to set this parameter to $false if the telephone numbers for users aren't in a standard format. If the telephone numbers aren't in a standard format, the Mailbox server may not be able to correctly resolve the caller ID to a name of a user in a consistent manner.
+The AllowHeuristicADCallingLineIdResolution parameter specifies whether to allow calling line ID resolution using telephone number fields that might be configured in Active Directory. When this parameter is set to $true, the telephone numbers such as those defined in the Mobile or Home telephone number fields in Active Directory are used. Setting this parameter to $true allows for resolution of calling IDs for both UM-enabled and non-UM-enabled users. The default is $true. You might want to set this parameter to $false if the telephone numbers for users aren't in a standard format. If the telephone numbers aren't in a standard format, the Mailbox server might not be able to correctly resolve the caller ID to a name of a user in a consistent manner.
 
 ```yaml
 Type: Boolean
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-UMIPGateway.md b/exchange/exchange-ps/ExchangePowerShell/Set-UMIPGateway.md
index 31c4296216..d0fc8eafb1 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-UMIPGateway.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-UMIPGateway.md
@@ -42,11 +42,11 @@ Set-UMIPGateway [-Identity] <UMIPGatewayIdParameter>
 ## DESCRIPTION
 The Set-UMIPGateway cmdlet modifies configuration settings for a specific UM IP gateway, for example, the IP address to the IP gateway. These modifications include allowing outgoing calls and controlling communications with a Session Initiation Protocol (SIP)-enabled IP Private Branch eXchange (PBX) or IP gateway.
 
-It's possible that modifications to the UM IP gateway settings may disrupt communication between Mailbox servers and the SIP-enabled IP PBX or IP gateway. Modifications to a UM IP gateway should be performed only by an administrator who fully understands the implications of making configuration changes to the UM IP gateway.
+It's possible that modifications to the UM IP gateway settings might disrupt communication between Mailbox servers and the SIP-enabled IP PBX or IP gateway. Modifications to a UM IP gateway should be performed only by an administrator who fully understands the implications of making configuration changes to the UM IP gateway.
 
 After this task is completed, the parameters and values specified are configured on the UM IP gateway.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -102,7 +102,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
 
-The Address parameter specifies the IP address or the fully qualified domain name (FQDN) configured on the UM IP gateway or SIP-enabled IP PBX. An FQDN is required if the UM dial plan associated with the UM IP gateway is operating in SIP Secured or Secured mode. If an FQDN is used, verify that the Domain Name System (DNS) has been configured correctly.
+The Address parameter specifies the IP address or the fully qualified domain name (FQDN) configured on the UM IP gateway or SIP-enabled IP PBX. An FQDN is required if the UM dial plan associated with the UM IP gateway is operating in SIP Secured or Secured mode. If an FQDN is used, verify that the Domain Name System (DNS) is configured correctly.
 
 ```yaml
 Type: UMSmartHost
@@ -195,11 +195,11 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016
 
-The IPAddressFamily parameter specifies whether the UM IP gateway will use Internet Protocol version 4 (IPv4), IPv6, or both to communicate. Valid values are:
+The IPAddressFamily parameter specifies the Internet Protocol (IP) version to use. Valid values are:
 
-- IPv4Only: The UM IP gateway will only use IPv4 to communicate. This is the default value.
-- IPv6Only: The UM IP gateway will only use IPv6.
-- Any: IPv6 will be used first, and then if necessary, it will fall back to IPv4.
+- IPv4Only: The UM IP gateway uses only IPv4 to communicate. This value is the default.
+- IPv6Only: The UM IP gateway uses only IPv6.
+- Any: IPv6 is used first. If IPv6 isn't available, IPV4 is used.
 
 ```yaml
 Type: IPAddressFamily
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-UMMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Set-UMMailbox.md
index 642df840a8..e6f7eb7a8c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-UMMailbox.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-UMMailbox.md
@@ -49,11 +49,11 @@ Set-UMMailbox [-Identity] <MailboxIdParameter>
 ```
 
 ## DESCRIPTION
-The Set-UMMailbox cmdlet sets UM properties associated with a user who has been UM-enabled. Many of the UM properties for the user are stored on the user's mailbox, and other UM properties for the user are stored in Active Directory.
+The Set-UMMailbox cmdlet sets UM properties associated with a user who is UM-enabled. Many of the UM properties for the user are stored on the user's mailbox, and other UM properties for the user are stored in Active Directory.
 
 After this task is completed, the parameters and values specified are configured on the UM mailbox.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -289,11 +289,11 @@ The ImListMigrationCompleted parameter specifies whether the UM-enabled user's L
 Valid values are:
 
 - $true: The user's Lync or Skype for Business contact list is stored in their Exchange 2016 mailbox. This prevents you from migrating the mailbox back to an Exchange 2010 server.
-- $false: The user's Lync or Skype for Business contact list is stored on a Lync or Skype for Business server. This doesn't prevent you from migrating the mailbox back to an Exchange 2010 server. This is the default value.
+- $false: The user's Lync or Skype for Business contact list is stored on a Lync or Skype for Business server. This doesn't prevent you from migrating the mailbox back to an Exchange 2010 server. This value is the default.
 
 Lync Server 2013 and Skype for Business Server 2015 support storing the user's contact list in their Exchange 2016 mailbox. This feature is known as the unified contact store (UCS), and it allows applications to show a consistent, up-to-date contact list. However, Exchange 2010 doesn't support the unified contact store. Therefore, before you migrate a user's Exchange 2016 mailbox back to Exchange 2010, you need to move the user's Lync or Skype for Business contact list from the unified contact store back to a Lync 2013 or Skype for Business server. For more information, see [Configuring Microsoft Lync Server 2013 to use the unified contact store](https://learn.microsoft.com/lyncserver/lync-server-2013-configuring-lync-server-to-use-the-unified-contact-store).
 
-If you migrate an Exchange 2013 mailbox back to Exchange 2010 while the user's Lync or Skype for Business contact list is stored in the unified contact store, the user could permanently lose access to those contacts. After you verify the user's Lync or Skype for Business contact list has been moved back to a Lync 2013 or Skype for Business server, you should be able to complete the mailbox migration. If you need to migrate the mailbox despite the potential for data loss, you can manually set the ImListMigrationCompleted parameter to $false.
+If you migrate an Exchange 2013 mailbox back to Exchange 2010 while the user's Lync or Skype for Business contact list is stored in the unified contact store, the user could permanently lose access to those contacts. After you verify the user's Lync or Skype for Business contact list is moved back to a Lync 2013 or Skype for Business server, you should be able to complete the mailbox migration. If you need to migrate the mailbox despite the potential for data loss, you can manually set the ImListMigrationCompleted parameter to $false.
 
 ```yaml
 Type: Boolean
@@ -493,7 +493,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016
 
-The VoiceMailAnalysisEnabled parameter specifies whether a copy of each voice mail left for a UM-enabled user will be forwarded to Microsoft for analysis and improvement of speech recognition features.
+The VoiceMailAnalysisEnabled parameter specifies whether a copy of each voice mail left for a UM-enabled user is forwarded to Microsoft for analysis and improvement of speech recognition features.
 
 ```yaml
 Type: Boolean
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-UMMailboxPIN.md b/exchange/exchange-ps/ExchangePowerShell/Set-UMMailboxPIN.md
index 12b5298d35..51d113a847 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-UMMailboxPIN.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-UMMailboxPIN.md
@@ -36,11 +36,11 @@ Set-UMMailboxPIN [-Identity] <MailboxIdParameter>
 ```
 
 ## DESCRIPTION
-The Set-UMMailboxPIN cmdlet is used when a UM-enabled user has been locked out of a mailbox because either the user tried to log on by using an incorrect PIN multiple times or because the user has forgotten the PIN. You can use this cmdlet to set the user's PIN. The new PIN must comply with the PIN policy rules specified in the user's mailbox policy. The new PIN is sent to the user in an email message, or sent to an alternative email address. You can control whether the user must reset the PIN at logon and if the mailbox will continue to be locked.
+The Set-UMMailboxPIN cmdlet is used when a UM-enabled user is locked out of a mailbox because either the user tried to log on by using an incorrect PIN multiple times or because the user has forgotten the PIN. You can use this cmdlet to set the user's PIN. The new PIN must comply with the PIN policy rules specified in the user's mailbox policy. The new PIN is sent to the user in an email message, or sent to an alternative email address. You can control whether the user must reset the PIN at logon and if the mailbox remains locked.
 
 After this task is completed, the PIN on a UM-enabled mailbox is set.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -49,28 +49,28 @@ You need to be assigned permissions before you can run this cmdlet. Although thi
 Set-UMMailboxPIN -Identity tonysmith@contoso.com
 ```
 
-This example resets the PIN on the UM-enabled mailbox for tonysmith@contoso.com.
+This example resets the PIN on the UM-enabled mailbox for `tonysmith@contoso.com`.
 
 ### Example 2
 ```powershell
 Set-UMMailboxPIN -Identity tonysmith@contoso.com -PIN 1985848 -PinExpired $true
 ```
 
-This example resets the initial PIN to 1985848 on the UM-enabled mailbox for tonysmith@contoso.com, and then sets the PIN as expired so that the user will be asked to change the PIN the next time the user logs on.
+This example resets the initial PIN to 1985848 on the UM-enabled mailbox for `tonysmith@contoso.com`, and then sets the PIN as expired so that the user is asked to change the PIN the next time they sign in.
 
 ### Example 3
 ```powershell
 Set-UMMailboxPIN -Identity tonysmith@contoso.com -LockedOut $true
 ```
 
-This example locks the UM-enabled mailbox for tonysmith@contoso.com to prevent the user from accessing the mailbox.
+This example locks the UM-enabled mailbox for `tonysmith@contoso.com` to prevent the user from accessing the mailbox.
 
 ### Example 4
 ```powershell
 Set-UMMailboxPIN -Identity tonysmith@contoso.com -LockedOut $false
 ```
 
-This example unlocks the UM-enabled mailbox for tonysmith@contoso.com and allows the user access to the mailbox.
+This example unlocks the UM-enabled mailbox for `tonysmith@contoso.com` and allows the user access to the mailbox.
 
 ## PARAMETERS
 
@@ -169,7 +169,10 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
 
-The LockedOut parameter specifies whether the mailbox will continue to be locked. If set to $true, the mailbox is marked as locked out. By default, if this parameter is omitted or set to $false, the command clears the locked-out status on the mailbox.
+The LockedOut parameter specifies whether the mailbox is locked out of UM. Valid values are:
+
+- $true: The mailbox is locked out of UM.
+- $false: The locked-out status on the UM mailbox is cleared. This value is the default.
 
 ```yaml
 Type: Boolean
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-UMMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-UMMailboxPolicy.md
index abb4d78fb2..15310627c3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-UMMailboxPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-UMMailboxPolicy.md
@@ -79,13 +79,13 @@ When the Set-UMMailboxPolicy cmdlet is used to modify UM mailbox policy objects,
 
 After this task is completed, the parameters and values specified are configured on the UM mailbox policy.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
 ### Example 1
 ```powershell
-Set-UMMailboxPolicy -Identity MyUMMailboxPolicy -LogonFailuresBeforePINReset 8 -MaxLogonAttempts 12 -MinPINLength 8 -PINHistoryCount 10 -PINLifetime 60 -ResetPINText "The PIN used to allow you access to your mailbox using Outlook Voice Access has been reset."
+Set-UMMailboxPolicy -Identity MyUMMailboxPolicy -LogonFailuresBeforePINReset 8 -MaxLogonAttempts 12 -MinPINLength 8 -PINHistoryCount 10 -PINLifetime 60 -ResetPINText "The PIN used to allow you access to your mailbox using Outlook Voice Access is reset."
 ```
 
 This example sets the PIN settings for users associated with the UM mailbox policy MyUMMailboxPolicy.
@@ -454,7 +454,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
 
-The AllowVoiceMailAnalysis parameter specifies whether a copy of each voice mail left for the users associated with the UM mailbox policy will be forwarded to Microsoft for analysis and improvement of our speech recognition features.
+The AllowVoiceMailAnalysis parameter specifies whether a copy of each voice mail is forwarded to Microsoft for analysis and improvement of our speech recognition features.
 
 ```yaml
 Type: Boolean
@@ -565,7 +565,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
 
-The FaxServerURI parameter specifies the Session Initiation Protocol (SIP) Uniform Resource Identifier (URI) for the fax solution that serves the UM-enabled users associated with the UM mailbox policy. This fax product or fax service accepts incoming fax calls that were redirected from Exchange Unified Messaging servers and creates inbound fax messages for the UM-enabled users associated with the UM mailbox policy. Although you can enter more than one fax server URI, only one URI will be used by the Unified Messaging server.
+The FaxServerURI parameter specifies the Session Initiation Protocol (SIP) Uniform Resource Identifier (URI) for the fax solution that serves the UM-enabled users associated with the UM mailbox policy. This fax product or fax service accepts incoming fax calls that were redirected from Exchange Unified Messaging servers and creates inbound fax messages for the UM-enabled users associated with the UM mailbox policy. Although you can enter more than one fax server URI, only one URI is used by the Unified Messaging server.
 
 ```yaml
 Type: String
@@ -601,7 +601,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
 
-The InformCallerOfVoiceMailAnalysis parameter specifies whether the callers leaving the voice mails will be informed about the possibility of their voice mails being forwarded to Microsoft for analysis.
+The InformCallerOfVoiceMailAnalysis parameter specifies whether callers leaving voice mails are informed about the possibility of their voice mails being forwarded to Microsoft for analysis.
 
 ```yaml
 Type: Boolean
@@ -727,7 +727,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016
 
-The PINLifetime parameter specifies the number of days until a new password is required. The range is from 1 through 999. The default value is 60. If you specify Unlimited, the users' PINs won't expire.
+The PINLifetime parameter specifies the number of days until a new password is required. The range is from 1 through 999. The default value is 60. If you specify Unlimited, the PINs don't expire.
 
 ```yaml
 Type: Unlimited
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-UMServer.md b/exchange/exchange-ps/ExchangePowerShell/Set-UMServer.md
index 14c1d36b5b..8a8cb9ca5f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-UMServer.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-UMServer.md
@@ -48,7 +48,7 @@ The Set-UMServer cmdlet sets specific properties on a Unified Messaging server.
 
 After this task is completed, the cmdlet sets the parameters and the values specified.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -130,7 +130,9 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010
 
-The DialPlans parameter specifies all the dial plans for which this server will handle UM calls. If no dial plans are defined, the Unified Messaging server won't handle UM calls.
+The DialPlans parameter specifies the dial plans that the server handles UM calls for. You can specify multiple values separated by commas.
+
+If no dial plans are specified, the Unified Messaging server doesn't handle UM calls.
 
 ```yaml
 Type: MultiValuedProperty
@@ -314,7 +316,9 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010
 
-The IrmLogPath parameter specifies the default IRM log directory location. The default value is C:\\Program Files\\Microsoft\\Exchange Server\\V14. If you set the value of the IrmLogPath parameter to $null, you effectively disable IRM logging. However, if you set the value of the IrmLogPath parameter to $null when the value of the IrmLogEnabled attribute is $true, Exchange will log errors in the Application event log. The preferred way for disabling IRM logging is to set the IrmLogEnabled parameter to $false.
+The IrmLogPath parameter specifies the default IRM log directory location. The default value is %ExchangeInstallPath%IRMLogs.
+
+If you set the value of this parameter to $null, you effectively disable IRM logging. However, if the value of the IrmLogEnabled parameter is $true, Exchange adds errors to the Application event log. The preferred way to disable IRM logging is to set the IrmLogEnabled parameter to $false.
 
 ```yaml
 Type: LocalLongFullPath
@@ -426,7 +430,13 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010
 
-The UMStartupMode parameter specifies whether the Microsoft Exchange Unified Messaging service on a Unified Messaging server will start up in TCP, TLS, or Dual mode. If the Unified Messaging server is being added to UM dial plans that have different security settings, you should choose Dual mode. In Dual mode, the Unified Messaging server can listen on ports 5060 and 5061 at the same time. If the startup mode is changed, the Microsoft Exchange Unified Messaging service must be restarted.
+The UMStartupMode parameter specifies the startup mode for the Microsoft Exchange Unified Messaging service on an Exchange server. Valid values are:
+
+- TCP
+- TLS
+- Dual: Use this value to add the Unified Messaging server to UM dial plans with different security settings. The Unified Messaging server can listen on ports 5060 and 5061 at the same time.
+
+If you change the startup mode, you need to restart the Microsoft Exchange Unified Messaging service.
 
 ```yaml
 Type: UMStartupMode
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-UMService.md b/exchange/exchange-ps/ExchangePowerShell/Set-UMService.md
index 296d0acef8..6ae35474ca 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-UMService.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-UMService.md
@@ -43,7 +43,7 @@ Set-UMService [-Identity] <UMServerIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -209,11 +209,11 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016
 
-The IPAddressFamily parameter specifies whether the UM IP gateway will use IPv4, IPv6, or both to communicate. Valid values are:
+The IPAddressFamily parameter specifies the Internet Protocol (IP) version to use. Valid values are:
 
-- IPv4
-- IPv6
-- Any: IPv6 is used first and if necessary, the UM IP gateway falls back to IPv4. This is the default value.
+- IPv4Only: The UM IP gateway uses only IPv4 to communicate.
+- IPv6Only: The UM IP gateway uses only IPv6.
+- Any: IPv6 is used first. If IPv6 isn't available, IPV4 is used. This value is the default.
 
 ```yaml
 Type: IPAddressFamily
@@ -302,7 +302,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value of the IrmLogMaxFileSize parameter must be less than or equal to the value of the IrmLogMaxDirectorySize parameter. The valid input range for either parameter is from 1 through 9223372036854775807 bytes. If you enter a value of unlimited, no size limit is imposed on the connectivity log directory.
 
@@ -332,7 +332,7 @@ When you enter a value, qualify the value with one of the following units:
 - GB (gigabytes)
 - TB (terabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 The value of the IrmLogMaxFileSize parameter must be less than or equal to the value of the IrmLogMaxDirectorySize parameter. The valid input range for either parameter is from 1 through 9223372036854775807 bytes. If you enter a value of unlimited, no size limit is imposed on the IRM log files.
 
@@ -354,7 +354,7 @@ Accept wildcard characters: False
 
 The IrmLogPath parameter specifies the default IRM log directory location. The default location is %ExchangeInstallPath%IRMLogs.
 
-If you set the value of this parameter to $null, you effectively disable IRM logging. However, setting this parameter to $null when the value of the IrmLogEnabled parameter is $true, generates errors in the Application event log. The preferred way to disable IRM logging is to set the IrmLogEnabled parameter to $false.
+If you set the value of this parameter to $null, you effectively disable IRM logging. However, if the value of the IrmLogEnabled parameter is $true, Exchange adds errors to the Application event log. The preferred way to disable IRM logging is to set the IrmLogEnabled parameter to $false.
 
 ```yaml
 Type: LocalLongFullPath
@@ -412,7 +412,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016
 
-This parameter has been deprecated and is no longer used.
+This parameter is deprecated and no longer used.
 
 ```yaml
 Type: ServerStatus
@@ -432,7 +432,7 @@ Accept wildcard characters: False
 
 The UMStartupMode parameter specifies the startup mode for the Unified Messaging service. Valid values are:
 
-- TCP (This is the default value)
+- TCP (default value)
 - TLS
 - Dual: The service can listen on ports 5060 and 5061 at the same time. If you add the Exchange server to UM dial plans that have different security settings, you should use this value.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-UnifiedAuditLogRetentionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-UnifiedAuditLogRetentionPolicy.md
index 060174cdd0..1c7e08d02d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-UnifiedAuditLogRetentionPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-UnifiedAuditLogRetentionPolicy.md
@@ -51,7 +51,7 @@ This example adds the AeD (for eDiscovery Premium events) record type to the pol
 Set-UnifiedAuditLogRetentionPolicy -Name "SearchQueryPerformed by app@sharepoint" -Operations SearchQueryPerformed,FileAccessed -UserIds $null -RetentionDuration SixMonths -Priority 10000
 ```
 
-This example modifies an audit log retention policy and changes to retention duration to six months, adds an additional activity to the Operations parameter, and removes all values from the UserId property so that the policy will apply to all users.
+This example modifies an audit log retention policy and changes to retention duration to six months, adds an additional activity to the Operations parameter, and removes all values from the UserId property so the policy applies to all users.
 
 ## PARAMETERS
 
@@ -167,7 +167,7 @@ Accept wildcard characters: False
 
 > Applicable: Security & Compliance
 
-The Operations parameter specifies the audit log operations that are retained by the policy. The values you specify will overwrite any existing entries. For a list of the available values for this parameter, see [Audited activities](https://learn.microsoft.com/purview/audit-log-activities).
+The Operations parameter specifies the audit log operations that are retained by the policy. The values you specify overwrite any existing entries. For a list of the available values for this parameter, see [Audited activities](https://learn.microsoft.com/purview/audit-log-activities).
 
 You can enter multiple values separated by commas. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`.
 
@@ -189,7 +189,7 @@ Accept wildcard characters: False
 
 The RecordTypes parameter specifies the audit logs of a specific record type that are retained by the policy. For details about the available values, see [AuditLogRecordType](https://learn.microsoft.com/office/office-365-management-api/office-365-management-activity-api-schema#auditlogrecordtype).
 
-You can specify multiple values separated by commas. The values you specify will overwrite any existing entries.
+You can specify multiple values separated by commas. The values you specify overwrite any existing entries.
 
 ```yaml
 Type: MultiValuedProperty
@@ -207,7 +207,7 @@ Accept wildcard characters: False
 
 > Applicable: Security & Compliance
 
-The UserIds parameter specifies the audit logs that are retained by the policy based on the ID of the user who performed the action. The values you specify will overwrite any existing entries.
+The UserIds parameter specifies the audit logs that are retained by the policy based on the ID of the user who performed the action. The values you specify overwrite any existing entries.
 
 You can enter multiple values separated by commas. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-UnifiedGroup.md b/exchange/exchange-ps/ExchangePowerShell/Set-UnifiedGroup.md
index 0e64d4de95..561eb31f90 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-UnifiedGroup.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-UnifiedGroup.md
@@ -89,7 +89,7 @@ Microsoft 365 Groups are group objects that are available across Microsoft 365 s
 > [!NOTE]
 > You can't change the HiddenGroupMembershipEnabled setting on an existing Microsoft 365 Group. The setting is available only during new group creation.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -224,8 +224,8 @@ Accept wildcard characters: False
 
 The AlwaysSubscribeMembersToCalendarEvents switch controls the default subscription settings of new members that are added to the Microsoft 365 Group. Changing this setting doesn't affect existing group members.
 
-- If you use this switch without a value, all future members that are added to the group will have their subscriptions set to ReplyAndEvents. Previous events are not automatically added to their calendars.
-- If you use this exact syntax: `-AlwaysSubscribeMembersToCalendarEvents:$false,` all future members that are added to the group will have their subscriptions set to ReplyOnly.
+- If you use this switch without a value, all future members added to the group have their subscriptions set to ReplyAndEvents. Previous events are not automatically added to their calendars.
+- If you use this exact syntax: `-AlwaysSubscribeMembersToCalendarEvents:$false,` all future members added to the group have their subscriptions set to ReplyOnly.
 
 Group members can change their own subscription settings, which can override your intended use of this switch.
 
@@ -896,7 +896,7 @@ Accept wildcard characters: False
 
 The HiddenFromAddressListsEnabled parameter specifies whether the Microsoft 365 Group appears in the global address list (GAL) and other address lists in your organization. Valid values are:
 
-- $true: The Microsoft 365 Group is hidden from the GAL and other address lists. The group can still receive messages, but users can't search for or browse to the group in Outlook or Outlook on the web. Users also can't find the group by using the Discover option in Outlook on the web. For users that are members of the Microsoft 365 Group, the group will still appear in the navigation pane in Outlook and Outlook on the web if HiddenFromExchangeClientsEnabled property is **NOT** enabled.
+- $true: The Microsoft 365 Group is hidden from the GAL and other address lists. The group can still receive messages, but users can't search for or browse to the group in Outlook or Outlook on the web. Users also can't find the group by using the Discover option in Outlook on the web. For users that are members of the Microsoft 365 Group, the group still appears in the navigation pane in Outlook and Outlook on the web if HiddenFromExchangeClientsEnabled property is **NOT** enabled.
 - $false: The Microsoft 365 Group is visible in the GAL and other address lists.
 
 ```yaml
@@ -918,7 +918,7 @@ Accept wildcard characters: False
 The HiddenFromExchangeClientsEnabled switch specifies whether the Microsoft 365 Group is hidden from Outlook clients connected to Microsoft 365.
 
 - To enable this setting, you don't need to specify a value with this switch. The Microsoft 365 Group is hidden from Outlook experiences. The group isn't visible in the Outlook left-hand navigation and isn't visible in the global address list (GAL). The group name doesn't resolve during the creation of a new message in Outlook. The group can still receive messages, but users can't search for or browse to the group in Outlook or Outlook on the web. Users can't find the group by using the Discover option in Outlook on the web. The HiddenFromAddressListsEnabled property is set to the value True to prevent the group from showing in the GAL and in the Offline Address Book (OAB).
-- To disable this setting, use this exact syntax: `-HiddenFromExchangeClientsEnabled:$false`. The Microsoft 365 Group isn't hidden from Outlook experiences. The group will be visible in the GAL and other address lists. This is the default value.
+- To disable this setting, use this exact syntax: `-HiddenFromExchangeClientsEnabled:$false`. The Microsoft 365 Group isn't hidden from Outlook experiences. The group is visible in the GAL and other address lists. This value is the default.
 - If Microsoft 365 Groups are hidden from Exchange clients, users don't see the option to subscribe or unsubscribe to a Microsoft 365 Group.
 
 ```yaml
@@ -1074,7 +1074,7 @@ When you enter a value, qualify the value with one of the following units:
 - MB (megabytes)
 - GB (gigabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 A valid value is a number up to 1.999999 gigabytes (2147483647 bytes) or the value unlimited. The default value is unlimited, which indicates the maximum size is imposed elsewhere (for example, organization, server, or connector limits).
 
@@ -1105,7 +1105,7 @@ When you enter a value, qualify the value with one of the following units:
 - MB (megabytes)
 - GB (gigabytes)
 
-Unqualified values are typically treated as bytes, but small values may be rounded up to the nearest kilobyte.
+Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte.
 
 A valid value is a number up to 1.999999 gigabytes (2147483647 bytes) or the value unlimited. The default value is unlimited, which indicates the maximum size is imposed elsewhere (for example, organization, server, or connector limits).
 
@@ -1159,7 +1159,7 @@ Accept wildcard characters: False
 The ModerationEnabled parameter specifies whether moderation is enabled for this recipient. Valid value are:
 
 - $true: Moderation is enabled for this recipient. Messages sent to this recipient must be approved by a moderator before the messages are delivered.
-- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This is the default value.
+- $false: Moderation is disabled for this recipient. Messages sent to this recipient are delivered without the approval of a moderator. This value is the default.
 
 You use the ModeratedBy parameter to specify the moderators.
 
@@ -1298,7 +1298,7 @@ The SubscriptionEnabled switch specifies whether the group owners can enable sub
 - To change the value to $true, use this switch without a value.
 - To change the value to $false, use this exact syntax: `-SubscriptionEnabled:$false`. The value of the AutoSubscribeNewMembers parameter must also be $false before you can use the value $false for this switch.
 
-**Note**: You should use the value $false for this switch only if you intend to disable group owner ability to change subscription options on the group. Group owners will not be able to enable subscription options on the group settings using Outlook on the web or Outlook desktop. Group owners might see the error, "The group update is in progress" error when they try to enable Subscription option. Admins trying to enable Subscription from Microsoft admin center might also see error, "Can't save 'Send copies of group conversations and events to group member's inboxes' Either your assigned product license doesn't include Exchange Online or you have recently created this group and it's still not ready for management".
+**Note**: Use the value $false for this switch only to prevent group owners from changing subscription options on the group. When the value is $false, group owners can't enable subscription options on the group settings using Outlook on the web or Outlook desktop. Group owners might see the error, "The group update is in progress" error when they try to enable Subscription option. Admins trying to enable Subscription from Microsoft admin center might also see error, "Can't save 'Send copies of group conversations and events to group member's inboxes' Either your assigned product license doesn't include Exchange Online or you have recently created this group and it's still not ready for management".
 
 **Note**: This property is evaluated only when you add internal members from your organization. Guest user accounts are always subscribed when added as a member. You can manually remove subscriptions for guest users by using the Remove-UnifiedGroupLinks cmdlet.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-User.md b/exchange/exchange-ps/ExchangePowerShell/Set-User.md
index e8c30cc153..cbb748981c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-User.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-User.md
@@ -13,7 +13,7 @@ title: Set-User
 # Set-User
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Set-User cmdlet to modify user attributes. You can use this cmdlet to modify all objects that have user accounts (for example, user mailboxes, mail users, and user accounts).
 
@@ -96,7 +96,7 @@ Set-User [-Identity] <UserIdParameter>
 ## DESCRIPTION
 The Set-User cmdlet contains no mail-related properties for mailboxes or mail users. To modify the mail-related properties for a user, you need to use the corresponding cmdlet based on the object type (for example, Set-Mailbox or Set-MailUser).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -396,7 +396,7 @@ This parameter is available only in on-premises Exchange.
 
 The CreateDTMFMap parameter specifies whether to create a dual-tone multiple-frequency (DTMF) map for the recipient. This allows the recipient to be identified by using a telephone keypad in Unified Messaging (UM) environments. Valid values are:
 
-- $true: A DTMF map is created for the recipient. This is the default value.
+- $true: A DTMF map is created for the recipient. This value is the default.
 - $false: A DTMF map isn't created for the recipient.
 
 ```yaml
@@ -757,7 +757,7 @@ The LinkedMasterAccount parameter specifies the master account in the forest whe
 - Alias
 - $null
 
-If you set this parameter's value to $null, you will unlink the account and convert the linked mailbox into a non-linked user mailbox. The mailbox won't retain the permissions previously set on it such as Send As, full access, folder, and calendar delegation.
+If you set this parameter's value to $null, you unlink the account and convert the linked mailbox into a non-linked user mailbox. The mailbox doesn't retain the permissions previously set on it (for example, Send As, Full Access, folder permissions, and calendar delegation).
 
 This parameter is required only if you're connecting a linked user.
 
@@ -1171,7 +1171,7 @@ Accept wildcard characters: False
 The ResetPasswordOnNextLogon parameter specifies whether the user must change their password the next time they log on. Valid values are:
 
 - $true: The user is required to change their password the next time they log on.
-- $false: The user isn't required to change their password the next time they log on. This is the default value.
+- $false: The user isn't required to change their password the next time they log on. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -1191,7 +1191,7 @@ Accept wildcard characters: False
 
 This parameter is available only in on-premises Exchange.
 
-The SamAccountName parameter (also known as the pre-Windows 2000 user account or group name) specifies an object identifier that's compatible with older versions of Microsoft Windows client and server operating systems. The value can contain letters, numbers, spaces, periods (.), and the following characters: !, #, $, %, ^, &, -, \_, {, }, and ~. The last character can't be a period. Unicode characters are allowed, but accented characters may generate collisions (for example, o and ö match). The maximum length is 20 characters.
+The SamAccountName parameter (also known as the pre-Windows 2000 user account or group name) specifies an object identifier that's compatible with older versions of Microsoft Windows client and server operating systems. The value can contain letters, numbers, spaces, periods (.), and the following characters: !, #, $, %, ^, &, -, \_, {, }, and ~. The last character can't be a period. Unicode characters are allowed, but accented characters might generate collisions (for example, o and ö match). The maximum length is 20 characters.
 
 ```yaml
 Type: String
@@ -1209,7 +1209,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
 
-The SeniorityIndex parameter specifies the order in which this user will display in a hierarchical address book. A user with a value of 2 will display higher in an address book than a user with a value of 1.
+The SeniorityIndex parameter specifies the order in which this user is displayed in a hierarchical address book. A user with a value of 2 is displayed higher in an address book than a user with a value of 1.
 
 ```yaml
 Type: Int32
@@ -1369,7 +1369,7 @@ Accept wildcard characters: False
 
 This parameter is available only in on-premises Exchange.
 
-The UMCallingLineIds parameter specifies telephone numbers or extensions that can be mapped to a Unified Messaging (UM)-enabled user. You can specify more than one telephone number for each user, separated by a comma. This parameter accepts digits less than 128 characters in length and may include an optional plus sign (+) preceding the numbers. Each UM-enabled user must have a unique UMCallingLineIds parameter value.
+The UMCallingLineIds parameter specifies telephone numbers or extensions that can be mapped to a Unified Messaging (UM)-enabled user. You can specify more than one telephone number for each user, separated by a comma. This parameter accepts digits less than 128 characters in length and might include an optional plus sign (+) preceding the numbers. Each UM-enabled user must have a unique UMCallingLineIds parameter value.
 
 ```yaml
 Type: MultiValuedProperty
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-UserBriefingConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-UserBriefingConfig.md
index aa2f125de5..d27da2058d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-UserBriefingConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-UserBriefingConfig.md
@@ -78,7 +78,7 @@ Accept wildcard characters: False
 The Enabled parameter specifies whether to enable or disable the Briefing email for a specified user's mailbox. Valid values are:
 
 - $true: The daily briefing message is enabled.
-- $false: The daily briefing message is disabled. This is the default value.
+- $false: The daily briefing message is disabled. This value is the default.
 
 ```yaml
 Type: Boolean
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-UserPhoto.md b/exchange/exchange-ps/ExchangePowerShell/Set-UserPhoto.md
index 81d35e2f23..52522938ff 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-UserPhoto.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-UserPhoto.md
@@ -96,11 +96,11 @@ Set-UserPhoto [-Identity] <MailboxIdParameter>
 ## DESCRIPTION
 The user photos feature allows users to associate a picture with their account. User photos are stored in the user's Active Directory account and in the root directory of the user's Exchange mailbox. Administrators use the Set-UserPhoto cmdlet to configure user photos. Users can upload, preview, and save a user photo to their account in the Options page in Outlook on the web. When a user uploads a photo, a preview of the photo is displayed on the Options page in Outlook on the web. This is the preview state, and creates the same result as running the Set-UserPhoto cmdlet using the Preview parameter. If the user clicks Save, the preview photo is saved as the user's photo. This is the same result as running the `Set-UserPhoto -Save` command or running both the `Set-UserPhoto -Preview` and `Set-UserPhoto -Save` commands. If the user cancels the preview photo on the Options page in Outlook on the web, then the `Set-UserPhoto -Cancel` command is called.
 
-A user photo must be set for a user before you can run the Get-UserPhoto cmdlet to view information about the user's photo. Otherwise, you'll get an error message saying the user photo doesn't exist for the specified user. Alternatively, you can run the `Get-UserPhoto -Preview` command to view information about a preview photo.
+A user photo must be set for a user before you can run the Get-UserPhoto cmdlet to view information about the user's photo. Otherwise, you get an error message saying the user photo doesn't exist for the specified user. Alternatively, you can run the `Get-UserPhoto -Preview` command to view information about a preview photo.
 
-**Notes**: Changes to the user photo won't appear in SharePoint until the affected user visits their profile page (My Site) or any SharePoint page that shows their large thumbnail image.
+**Notes**: Changes to the user photo don't appear in SharePoint until the affected user visits their profile page (My Site) or any SharePoint page that shows their large thumbnail image.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -162,7 +162,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-The Cancel switch deletes the photo that's currently uploaded as the preview photo. You don't need to specify a value with this switch.
+The Cancel switch deletes the current preview photo. You don't need to specify a value with this switch.
 
 To delete the photo that's currently associated with a user's account, use the Remove-UserPhoto cmdlet. The Cancel switch only deletes the preview photo.
 
@@ -182,7 +182,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-The PictureData parameter specifies the photo file that will be uploaded to the user's account.
+The PictureData parameter specifies the photo file to upload to the user's account.
 
 A valid value for this parameter requires you to read the file to a byte-encoded object using the following syntax: `([System.IO.File]::ReadAllBytes('<Path>\<FileName>'))`. You can use this command as the parameter value, or you can write the output to a variable (`$data = [System.IO.File]::ReadAllBytes('<Path>\<FileName>')`) and use the variable as the parameter value (`$data`).
 
@@ -202,7 +202,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-The PictureStream parameter specifies the photo that will be uploaded to the user's account. This parameter is used by client applications such as Outlook on the web when users add a photo. To upload a photo using PowerShell, use the PictureData parameter to specify the photo file.
+The PictureStream parameter specifies the photo to upload to the user's account. This parameter is used by client applications such as Outlook on the web when users add a photo. To upload a photo using PowerShell, use the PictureData parameter to specify the photo file.
 
 ```yaml
 Type: Stream
@@ -222,7 +222,7 @@ Accept wildcard characters: False
 
 The Preview switch uploads a preview photo for the user account. You don't need to specify a value with this switch.
 
-A preview photo is the photo object that is uploaded to the user's account, but isn't saved. For example, if a user uploads a photo in Outlook on the web Options to preview before saving it. If you use the Preview switch to upload a preview photo, you need to run the command `Set-UserPhoto -Save` to save it as the user's photo.
+A preview photo is uploaded to the user's account, but isn't saved. For example, if a user uploads a photo in Outlook on the web Options to preview before saving it. If you use the Preview switch to upload a preview photo, you need to run the command `Set-UserPhoto -Save` to save it as the user's photo.
 
 ```yaml
 Type: SwitchParameter
@@ -240,7 +240,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-The Save switch specifies that the photo that's uploaded to the user's account will be saved as the user's photo. You don't need to specify a value with this switch.
+The Save switch specifies the uploaded photo is saved as the user's photo. You don't need to specify a value with this switch.
 
 ```yaml
 Type: SwitchParameter
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-WebServicesVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Set-WebServicesVirtualDirectory.md
index d1c909dfa0..f96a79084a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-WebServicesVirtualDirectory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-WebServicesVirtualDirectory.md
@@ -46,7 +46,7 @@ Set-WebServicesVirtualDirectory [-Identity] <VirtualDirectoryIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -103,7 +103,7 @@ Accept wildcard characters: False
 
 The BasicAuthentication parameter specifies whether Basic authentication is enabled on the virtual directory. Valid values are:
 
-- $true: Basic authentication is enabled. This is the default value.
+- $true: Basic authentication is enabled. This value is the default.
 - $false: Basic authentication is disabled.
 
 ```yaml
@@ -164,7 +164,7 @@ Accept wildcard characters: False
 The DigestAuthentication parameter specifies whether Digest authentication is enabled on the virtual directory. Valid values are:
 
 - $true: Digest authentication is enabled.
-- $false: Digest authentication is disabled. This is the default value.
+- $false: Digest authentication is disabled. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -206,7 +206,7 @@ The ExtendedProtectionFlags parameter specifies custom settings for Extended Pro
 - AllowDotlessSPN: Required if you want to use Service Principal Name (SPN) values that don't contain FQDNs (for example, HTTP/ContosoMail instead of HTTP/mail.contoso.com). You specify SPNs with the ExtendedProtectionSPNList parameter. This setting makes Extended Protection for Authentication less secure because dotless certificates aren't unique, so it isn't possible to ensure that the client-to-proxy connection was established over a secure channel.
 - NoServiceNameCheck: The SPN list isn't checked to validate a channel binding token. This setting makes Extended Protection for Authentication less secure. We generally don't recommend this setting.
 - Proxy: A proxy server is responsible for terminating the SSL channel. To use this setting, you need to register an SPN by using the ExtendedProtectionSPNList parameter.
-- ProxyCoHosting: HTTP and HTTPS traffic may be accessing the virtual directory and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server.
+- ProxyCoHosting: HTTP and HTTPS traffic might be accessing the virtual directory and a proxy server is located between at least some of the clients and the Client Access services on the Exchange server.
 
 ```yaml
 Type: MultiValuedProperty
@@ -226,7 +226,7 @@ Accept wildcard characters: False
 
 The ExtendedProtectionSPNList parameter specifies a list of valid Service Principal Names (SPNs) if you're using Extended Protection for Authentication on the virtual directory. Valid values are:
 
-- $null: This is the default value.
+- $null: This value is the default.
 - Single SPN or comma delimited list of valid SPNs: The SPN value format is `Protocol\FQDN`. For example, HTTP/mail.contoso.com. To add an SPN that's not an FQDN (for example, HTTP/ContosoMail), you also need to use the AllowDotlessSPN value for the ExtendedProtectionFlags parameter.
 
 ```yaml
@@ -247,8 +247,8 @@ Accept wildcard characters: False
 
 The ExtendedProtectionTokenChecking parameter defines how you want to use Extended Protection for Authentication on the virtual directory. Extended Protection for Authentication isn't enabled by default. Valid values are:
 
-- None: Extended Protection for Authentication isn't be used on the virtual directory. This is the default value.
-- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication will work, but may not be as secure as connections that use Extended Protection for Authentication.
+- None: Extended Protection for Authentication isn't be used on the virtual directory. This value is the default.
+- Allow: Extended Protection for Authentication is used for connections between clients and the virtual directory if both the client and server support it. Connections that don't support Extended Protection for Authentication work, but might not be as secure as connections that use Extended Protection for Authentication.
 - Require: Extended Protection for Authentication is used for all connections between clients and the virtual directory. If either the client or server doesn't support it, the connection will fail. If you use this value, you also need to set an SPN value for the ExtendedProtectionSPNList parameter.
 
 **Note**: If you use the value Allow or Require, and you have a proxy server between the client and the Client Access services on the Mailbox server that's configured to terminate the client-to-proxy SSL channel, you also need to configure one or more Service Principal Names (SPNs) by using the ExtendedProtectionSPNList parameter.
@@ -312,7 +312,7 @@ Accept wildcard characters: False
 The GzipLevel parameter sets the Gzip configuration for the Exchange Web Services virtual directory. Valid values are:
 
 - Off: No compression.
-- Low: Static compression only. This is the default value. This value has the same result as the Off value, because Exchange Web Services content is dynamic.
+- Low: Static compression only. This value is the default. This value has the same result as the Off value, because Exchange Web Services content is dynamic.
 - High: Static and dynamic compression. Content from Exchange Web Services is compressed if clients indicate support for Gzip compression in their requests.
 - Error: Identifies errors in the Gzip compression configuration.
 
@@ -394,7 +394,7 @@ Accept wildcard characters: False
 
 This parameter is available only in Exchange Server 2010.
 
-The MRSProxyMaxConnections parameter specifies the maximum number of simultaneous move sessions that an instance of MRSProxy will accept. This setting accepts values from 0 to unlimited. The default value is 100. For more information about MRSProxy, see [Understanding Move Requests](https://learn.microsoft.com/previous-versions/office/exchange-server-2010/dd298174(v=exchg.141)).
+The MRSProxyMaxConnections parameter specifies the maximum number of simultaneous move sessions that an instance of MRSProxy accepts. This setting accepts values from 0 to unlimited. The default value is 100. For more information about MRSProxy, see [Understanding Move Requests](https://learn.microsoft.com/previous-versions/office/exchange-server-2010/dd298174(v=exchg.141)).
 
 ```yaml
 Type: Unlimited
@@ -414,7 +414,7 @@ Accept wildcard characters: False
 
 The OAuthAuthentication parameter specifies whether OAuth authentication is enabled on the virtual directory. Valid values are:
 
-- $true: OAuth authentication is enabled. This is the default value.
+- $true: OAuth authentication is enabled. This value is the default.
 - $false: OAuth authentication is disabled.
 
 ```yaml
@@ -453,7 +453,7 @@ Accept wildcard characters: False
 
 The WindowsAuthentication parameter specifies whether Integrated Windows authentication is enabled on the virtual directory. Valid values are:
 
-- $true: Integrated Windows authentication is enabled. This is the default value.
+- $true: Integrated Windows authentication is enabled. This value is the default.
 - $false: Integrated Windows authentication is disabled.
 
 ```yaml
@@ -474,7 +474,7 @@ Accept wildcard characters: False
 
 The WSSecurityAuthentication parameter specifies whether WS-Security (Web Services Security) authentication is enabled on the virtual directory. Valid values are:
 
-- $true: WS-Security authentication is enabled. This is the default value.
+- $true: WS-Security authentication is enabled. This value is the default.
 - $false: WS-Security authentication is disabled.
 
 ```yaml
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-X400AuthoritativeDomain.md b/exchange/exchange-ps/ExchangePowerShell/Set-X400AuthoritativeDomain.md
index f23347ccc2..1cd18367dd 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-X400AuthoritativeDomain.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-X400AuthoritativeDomain.md
@@ -67,7 +67,7 @@ organizational unit name
 - Abbreviation: OU1 to OU4
 - Maximum character length: 32
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Start-ComplianceSearch.md b/exchange/exchange-ps/ExchangePowerShell/Start-ComplianceSearch.md
index 098c14c750..2d08dc0fc9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Start-ComplianceSearch.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Start-ComplianceSearch.md
@@ -13,7 +13,7 @@ title: Start-ComplianceSearch
 # Start-ComplianceSearch
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Start-ComplianceSearch cmdlet to start stopped, completed or not started compliance searches in Exchange Server 2016 or later and in the Microsoft Purview compliance portal.
 
@@ -31,7 +31,7 @@ Start-ComplianceSearch [-Identity] <ComplianceSearchIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 In on-premises Exchange, this cmdlet is available in the Mailbox Search role. By default, this role is assigned only to the Discovery Management role group.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Start-DatabaseAvailabilityGroup.md b/exchange/exchange-ps/ExchangePowerShell/Start-DatabaseAvailabilityGroup.md
index 8ee061322f..d2675e5692 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Start-DatabaseAvailabilityGroup.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Start-DatabaseAvailabilityGroup.md
@@ -44,7 +44,7 @@ Start-DatabaseAvailabilityGroup [-Identity] <DatabaseAvailabilityGroupIdParamete
 ## DESCRIPTION
 The Start-DatabaseAvailabilityGroup cmdlet is used to activate DAG members in a recovered datacenter after a datacenter switchover, as part of the switchback process to the recovered datacenter. The Start-DatabaseAvailabilityGroup cmdlet manipulates configuration and state so that the servers are incorporated into the operating DAG, and joined to the DAG's underlying cluster. The Move-ActiveMailboxDatabase cmdlet is then used to activate databases in the primary datacenter.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Start-EdgeSynchronization.md b/exchange/exchange-ps/ExchangePowerShell/Start-EdgeSynchronization.md
index 5f049f451d..f3be145a64 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Start-EdgeSynchronization.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Start-EdgeSynchronization.md
@@ -34,7 +34,7 @@ Start-EdgeSynchronization [-Confirm]
 ## DESCRIPTION
 The Microsoft Exchange EdgeSync service that runs on Mailbox servers replicates data stored in Active Directory to the local Active Directory Lightweight Directory Services (AD LDS) store on the Edge Transport server. After the initial replication, one-way synchronization of changed data in Active Directory to AD LDS keeps this data up to date.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -139,7 +139,7 @@ Accept wildcard characters: False
 
 The TargetServer parameter specifies an Edge Transport server to initiate edge synchronization with. If omitted, all Edge Transport servers are synchronized.
 
-You may want to use this parameter to specify a single Edge Transport server for synchronization if a new Edge Transport server has been installed or if that Edge Transport server has been unavailable for some time.
+You might want to use this parameter to specify a single Edge Transport server for synchronization if a new Edge Transport server is installed or if that Edge Transport server is unavailable for some time.
 
 ```yaml
 Type: String
diff --git a/exchange/exchange-ps/ExchangePowerShell/Start-HistoricalSearch.md b/exchange/exchange-ps/ExchangePowerShell/Start-HistoricalSearch.md
index 24d6078d40..30a29a3eb4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Start-HistoricalSearch.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Start-HistoricalSearch.md
@@ -46,11 +46,11 @@ Start-HistoricalSearch -EndDate <DateTime> -ReportTitle <String> -ReportType <Hi
 ```
 
 ## DESCRIPTION
-A historical search provides message trace and report details in a comma-separated value (CSV) file for messages that are aged between 1-4 hours (depending on your environment) and 90 days old. There is a limit of 250 historical searches that you can submit in a 24 hour period; you'll be warned if you're nearing the daily quota. Cancelled searches count against the daily quota. Also, in each CSV file there is a limit of 100000 results or lines.
+A historical search provides message trace and report details in a comma-separated value (CSV) file for messages that are aged between 1-4 hours (depending on your environment) and 90 days old. You can submit a maximum of 250 historical searches that you can submit in a 24 hour period. You get a warning if you approach the daily quota. Cancelled searches count against the daily quota. Also, in each CSV file there is a limit of 100000 results or lines.
 
 If you specify a distribution group, all messages might not be returned in the results. To ensure that all messages are returned, specify the individual recipient.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -344,7 +344,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online, Exchange Online Protection
 
-The MessageId parameter filters the results by the Message-ID header field of the message. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which may include angle brackets) and enclose the value in quotation marks (for example, "<d9683b4c-127b-413a-ae2e-fa7dfb32c69d@DM3NAM06BG401.Eop-nam06.prod.protection.outlook.com>").
+The MessageId parameter filters the results by the Message-ID header field of the message. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which might include angle brackets) and enclose the value in quotation marks (for example, "<d9683b4c-127b-413a-ae2e-fa7dfb32c69d@DM3NAM06BG401.Eop-nam06.prod.protection.outlook.com>").
 
 ```yaml
 Type: MultiValuedProperty
@@ -362,7 +362,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Online, Exchange Online Protection
 
-The NetworkMessageId parameter filters the message tracking log entries by the value of the NetworkMessageId field. This field contains a unique message ID value that persists across copies of the message that may be created due to bifurcation or distribution group expansion. An example value is 1341ac7b13fb42ab4d4408cf7f55890f.
+The NetworkMessageId parameter filters the message tracking log entries by the value of the NetworkMessageId field. This field contains a unique message ID value that persists across copies of the message that might be created due to bifurcation or distribution group expansion. An example value is 1341ac7b13fb42ab4d4408cf7f55890f.
 
 ```yaml
 Type: MultiValuedProperty
diff --git a/exchange/exchange-ps/ExchangePowerShell/Start-MailboxAssistant.md b/exchange/exchange-ps/ExchangePowerShell/Start-MailboxAssistant.md
index 262c4ad84e..cb4f85e871 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Start-MailboxAssistant.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Start-MailboxAssistant.md
@@ -31,7 +31,7 @@ Start-MailboxAssistant [-Identity] <UserIdParameter> -AssistantName <String>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Start-MailboxSearch.md b/exchange/exchange-ps/ExchangePowerShell/Start-MailboxSearch.md
index 8f54ac3548..a547ae884e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Start-MailboxSearch.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Start-MailboxSearch.md
@@ -13,7 +13,7 @@ title: Start-MailboxSearch
 # Start-MailboxSearch
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Start-MailboxSearch cmdlet to restart or resume a mailbox search that's been stopped.
 
@@ -43,7 +43,7 @@ In Exchange 2013 or later, mailbox searches are also used for In-Place Hold. How
 
 For more details, see [In-Place Hold and Litigation Hold in Exchange Server](https://learn.microsoft.com/Exchange/policy-and-compliance/holds/holds) and [In-Place eDiscovery in Exchange Server](https://learn.microsoft.com/Exchange/policy-and-compliance/ediscovery/ediscovery).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Start-ManagedFolderAssistant.md b/exchange/exchange-ps/ExchangePowerShell/Start-ManagedFolderAssistant.md
index 1d766dcae6..46ebde84f6 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Start-ManagedFolderAssistant.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Start-ManagedFolderAssistant.md
@@ -13,7 +13,7 @@ title: Start-ManagedFolderAssistant
 # Start-ManagedFolderAssistant
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Start-ManagedFolderAssistant cmdlet to immediately start messaging records management (MRM) processing of mailboxes that you specify.
 
@@ -111,13 +111,13 @@ Start-ManagedFolderAssistant [-Identity] <MailboxOrMailUserIdParameter> [-StopHo
 ## DESCRIPTION
 The Managed Folder Assistant uses the retention policy settings of users' mailboxes to process retention of items. This mailbox processing occurs automatically. You can use the Start-ManagedFolderAssistant cmdlet to immediately start processing the specified mailbox.
 
-In Exchange Server 2010 release to manufacturing (RTM), the Identity parameter specifies the Mailbox server to start the assistant and process all mailboxes on that server, and the Mailbox parameter specifies the mailbox to process. In Exchange 2010 Service Pack 1 (SP1) and later, the Mailbox parameter has been removed, and the Identity parameter accepts the mailbox or mail user to process.
+In Exchange Server 2010 release to manufacturing (RTM), the Identity parameter specifies the Mailbox server to start the assistant and process all mailboxes on that server, and the Mailbox parameter specifies the mailbox to process. In Exchange 2010 Service Pack 1 (SP1) and later, the Mailbox parameter is removed, and the Identity parameter accepts the mailbox or mail user to process.
 
 If you use these parameters in scheduled commands or scripts, we recommend that you review them and make any necessary changes.
 
 For more information, see [KB4032361](https://support.microsoft.com/help/4032361).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -353,9 +353,9 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
 
-The HoldCleanup switch instructs the Managed Folder Assistant to clean up duplicate versions of items in the Recoverable Items folder that may have been created when a mailbox is on In-Place Hold, Litigation Hold, or has Single Item Recovery enabled. You don't need to specify a value with this switch.
+The HoldCleanup switch instructs the Managed Folder Assistant to clean up duplicate versions of items in the Recoverable Items folder that might have been created when a mailbox is on In-Place Hold, Litigation Hold, or has Single Item Recovery enabled. You don't need to specify a value with this switch.
 
-Removing duplicate items from the Recoverable Items folder reduces the folder size and may help prevent reaching Recoverable Items quota limits. For more details about Recoverable Items quota limits, see [Recoverable Items folder in Exchange Server](https://learn.microsoft.com/Exchange/policy-and-compliance/recoverable-items-folder/recoverable-items-folder).
+Removing duplicate items from the Recoverable Items folder reduces the folder size and might help prevent reaching Recoverable Items quota limits. For more details about Recoverable Items quota limits, see [Recoverable Items folder in Exchange Server](https://learn.microsoft.com/Exchange/policy-and-compliance/recoverable-items-folder/recoverable-items-folder).
 
 ```yaml
 Type: SwitchParameter
@@ -401,7 +401,7 @@ This parameter is available only in the cloud-based service.
 
 The StopHoldCleanup switch stops a previous hold clean-up command that was issued on the mailbox. You don't need to specify a value with this switch.
 
-A hold clean-up command will run until it completely scans the Recoverable Items folder for duplicate versions of items (it even continues after an interruption). In some cases, the hold clean-up command gets stuck, which can block other regular MRM tasks on the mailbox (for example, expiring items). The StopHoldCleanup switch tells MRM to abandon the stuck hold clean-up task so that regular tasks can continue.
+A hold clean-up command runs until it completely scans the Recoverable Items folder for duplicate versions of items (it even continues after an interruption). In some cases, the hold clean-up command gets stuck, which can block other regular MRM tasks on the mailbox (for example, expiring items). The StopHoldCleanup switch tells MRM to abandon the stuck hold clean-up task so that regular tasks can continue.
 
 ```yaml
 Type: SwitchParameter
diff --git a/exchange/exchange-ps/ExchangePowerShell/Start-MigrationBatch.md b/exchange/exchange-ps/ExchangePowerShell/Start-MigrationBatch.md
index 5edc513378..2057afd43e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Start-MigrationBatch.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Start-MigrationBatch.md
@@ -13,7 +13,7 @@ title: Start-MigrationBatch
 # Start-MigrationBatch
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Start-MigrationBatch cmdlet to start a move request or migration batch that was created with the New-MigrationBatch cmdlet.
 
@@ -34,11 +34,11 @@ Start-MigrationBatch [[-Identity] <MigrationBatchIdParameter>]
 ## DESCRIPTION
 The Start-MigrationBatch cmdlet starts a pending migration batch that was created, but not started, with the New-MigrationBatch cmdlet.
 
-The Start-MigrationBatch cmdlet also will resume a Stopped migration batch or retry failures within a Failed or Synced with Errors migration batch. In the cloud-based service, the Start-MigrationBatch cmdlet can also retry failures within a Completed with Errors migration batch.
+The Start-MigrationBatch cmdlet also resumes a Stopped migration batch or retry failures within a Failed or Synced with Errors migration batch. In the cloud-based service, the Start-MigrationBatch cmdlet can also retry failures within a Completed with Errors migration batch.
 
 In the cloud-based service, the Start-MigrationBatch cmdlet can be run at any time to retry failed users within the batch.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Start-MigrationUser.md b/exchange/exchange-ps/ExchangePowerShell/Start-MigrationUser.md
index 4d47899a39..2a837896b8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Start-MigrationUser.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Start-MigrationUser.md
@@ -31,7 +31,7 @@ Start-MigrationUser [[-Identity] <MigrationUserIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Start-RetentionAutoTagLearning.md b/exchange/exchange-ps/ExchangePowerShell/Start-RetentionAutoTagLearning.md
index 829414c47f..00f627f80b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Start-RetentionAutoTagLearning.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Start-RetentionAutoTagLearning.md
@@ -46,7 +46,7 @@ Start-RetentionAutoTagLearning [-Identity] <MailboxIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Stop-ComplianceSearch.md b/exchange/exchange-ps/ExchangePowerShell/Stop-ComplianceSearch.md
index 0c82fe54f0..2d60f04091 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Stop-ComplianceSearch.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Stop-ComplianceSearch.md
@@ -13,7 +13,7 @@ title: Stop-ComplianceSearch
 # Stop-ComplianceSearch
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Stop-ComplianceSearch cmdlet to stop running compliance searches in Exchange Server 2016 or later and in the Microsoft Purview compliance portal.
 
@@ -29,7 +29,7 @@ Stop-ComplianceSearch [-Identity] <ComplianceSearchIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 In on-premises Exchange, this cmdlet is available in the Mailbox Search role. By default, this role is assigned only to the Discovery Management role group.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Stop-DatabaseAvailabilityGroup.md b/exchange/exchange-ps/ExchangePowerShell/Stop-DatabaseAvailabilityGroup.md
index 19efc5a0e9..3731c78feb 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Stop-DatabaseAvailabilityGroup.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Stop-DatabaseAvailabilityGroup.md
@@ -44,7 +44,7 @@ Stop-DatabaseAvailabilityGroup [-Identity] <DatabaseAvailabilityGroupIdParameter
 ## DESCRIPTION
 The Stop-DatabaseAvailabilityGroup cmdlet is used during a datacenter switchover. This cmdlet is used to mark one or members of the DAG as failed (also known as stopped).The Stop-DatabaseAvailabilityGroup cmdlet can be run against a DAG only when the DAG is configured with a DatacenterActivationMode value of DagOnly.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Stop-HistoricalSearch.md b/exchange/exchange-ps/ExchangePowerShell/Stop-HistoricalSearch.md
index 9cc67f057f..52153100c5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Stop-HistoricalSearch.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Stop-HistoricalSearch.md
@@ -31,7 +31,7 @@ A historical search provides message trace and report details in a comma-separat
 
 After you start a historical search by using the Start-HistoricalSearch cmdlet, the search is queued, but not actually running. While the search is queued and has the status value of NotStarted, you can use the Stop-HistoricalSearch cmdlet to stop it. After the search is actively running, and has a status value of InProgress, you can't stop it. When you stop a historical search, it's given a status value of Cancelled.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Stop-MailboxSearch.md b/exchange/exchange-ps/ExchangePowerShell/Stop-MailboxSearch.md
index aceebefb3b..ddfbcd46a5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Stop-MailboxSearch.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Stop-MailboxSearch.md
@@ -13,7 +13,7 @@ title: Stop-MailboxSearch
 # Stop-MailboxSearch
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Stop-MailboxSearch cmdlet to stop a mailbox search that's in progress.
 
@@ -34,7 +34,7 @@ Stop-MailboxSearch [-Identity] <SearchObjectIdParameter>
 ## DESCRIPTION
 In Microsoft Exchange, mailbox searches are used for In-Place eDiscovery and In-Place Hold. You can start and stop a mailbox search. For more information, see [In-Place eDiscovery in Exchange Server](https://learn.microsoft.com/Exchange/policy-and-compliance/ediscovery/ediscovery).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Stop-ManagedFolderAssistant.md b/exchange/exchange-ps/ExchangePowerShell/Stop-ManagedFolderAssistant.md
index f616dc45bb..da5e553d14 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Stop-ManagedFolderAssistant.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Stop-ManagedFolderAssistant.md
@@ -32,7 +32,7 @@ Stop-ManagedFolderAssistant [[-Identity] <ServerIdParameter>]
 ## DESCRIPTION
 The Managed Folder Assistant uses the managed folder mailbox policy settings of users to process mailbox items for retention and journaling as needed. Use the Stop-ManagedFolderAssistant cmdlet to stop the Managed Folder Assistant as soon as processing of the current mailbox is completed.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Stop-MigrationBatch.md b/exchange/exchange-ps/ExchangePowerShell/Stop-MigrationBatch.md
index 7673381499..56da49cbe3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Stop-MigrationBatch.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Stop-MigrationBatch.md
@@ -13,7 +13,7 @@ title: Stop-MigrationBatch
 # Stop-MigrationBatch
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Stop-MigrationBatch cmdlet to stop the processing of a migration batch that's in progress.
 
@@ -31,9 +31,9 @@ Stop-MigrationBatch [[-Identity] <MigrationBatchIdParameter>]
 ```
 
 ## DESCRIPTION
-The Stop-MigrationBatch cmdlet stops the migration batch that's being processed in your on-premises Exchange organization or by the cloud-based migration service running in Microsoft 365. You can only stop migration batches that have mailboxes that are still in the process of being migrated or are waiting to be migrated. Stopping a migration won't affect mailboxes that have been migrated already. The migration of mailboxes that are being actively migrated is stopped immediately. If all migration requests in a migration batch are completed or failed, this cmdlet won't run.
+The Stop-MigrationBatch cmdlet stops the migration batch that's being processed in your on-premises Exchange organization or by the cloud-based migration service running in Microsoft 365. You can only stop migration batches that have mailboxes that are still in the process of being migrated or are waiting to be migrated. Stopping a migration doesn't affect mailboxes that have been migrated already. The migration of mailboxes that are being actively migrated is stopped immediately. If all migration requests in a migration batch are completed or failed, this cmdlet doesn't run.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Stop-MigrationUser.md b/exchange/exchange-ps/ExchangePowerShell/Stop-MigrationUser.md
index 4572e320b5..966fa96a5a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Stop-MigrationUser.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Stop-MigrationUser.md
@@ -31,7 +31,7 @@ Stop-MigrationUser [[-Identity] <MigrationUserIdParameter>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Suspend-MailboxDatabaseCopy.md b/exchange/exchange-ps/ExchangePowerShell/Suspend-MailboxDatabaseCopy.md
index c9af7877eb..07496d4408 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Suspend-MailboxDatabaseCopy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Suspend-MailboxDatabaseCopy.md
@@ -43,7 +43,7 @@ Suspend-MailboxDatabaseCopy [-Identity] <DatabaseCopyIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Suspend-MailboxExportRequest.md b/exchange/exchange-ps/ExchangePowerShell/Suspend-MailboxExportRequest.md
index b307a83704..215f82623c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Suspend-MailboxExportRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Suspend-MailboxExportRequest.md
@@ -33,7 +33,7 @@ Suspend-MailboxExportRequest [-Identity] <MailboxExportRequestIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Suspend-MailboxImportRequest.md b/exchange/exchange-ps/ExchangePowerShell/Suspend-MailboxImportRequest.md
index 0e85b70046..214fd604b0 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Suspend-MailboxImportRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Suspend-MailboxImportRequest.md
@@ -13,7 +13,7 @@ title: Suspend-MailboxImportRequest
 # Suspend-MailboxImportRequest
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Suspend-MailboxImportRequest cmdlet to suspend an import request any time after the request was created, but before the request reaches the status of Completed. You can resume the move request by using the Resume-MailboxImportRequest cmdlet.
 
@@ -35,7 +35,7 @@ Suspend-MailboxImportRequest [-Identity] <MailboxImportRequestIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Suspend-MailboxRestoreRequest.md b/exchange/exchange-ps/ExchangePowerShell/Suspend-MailboxRestoreRequest.md
index bee939b219..67f90c841e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Suspend-MailboxRestoreRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Suspend-MailboxRestoreRequest.md
@@ -13,7 +13,7 @@ title: Suspend-MailboxRestoreRequest
 # Suspend-MailboxRestoreRequest
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Suspend-MailboxRestoreRequest cmdlet to suspend a restore request any time after the request was created, but before the request reaches the status of Completed. You can resume the restore request by using the Resume-MailboxRestoreRequest cmdlet.
 
@@ -31,7 +31,7 @@ Suspend-MailboxRestoreRequest [-Identity] <MailboxRestoreRequestIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Suspend-Message.md b/exchange/exchange-ps/ExchangePowerShell/Suspend-Message.md
index 6c10bb3750..ce944390fa 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Suspend-Message.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Suspend-Message.md
@@ -39,13 +39,13 @@ Suspend-Message [-Identity] <MessageIdentity>
 ```
 
 ## DESCRIPTION
-A message already in delivery won't be suspended. Delivery will continue and the message status will be PendingSuspend. If the delivery fails, the message will re-enter the queue and it will then be suspended. You can't suspend a message that's in the poison message queue.
+A message already in delivery isn't suspended. Delivery continues and the message status is PendingSuspend. If the delivery fails, the message re-enters the queue and then it's suspended. You can't suspend a message in the poison message queue.
 
 A message being sent to multiple recipients might be located in multiple queues. If you specify an Identity parameter, the message is suspended in a single queue if that identity matches only a single message. If the identity matches more than one message, you receive an error. To suspend a message in more than one queue in a single operation, you must use the Filter parameter.
 
 For instructions on how to resume a suspended message, see [Resume-Message](https://learn.microsoft.com/powershell/module/exchangepowershell/resume-message).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Suspend-MoveRequest.md b/exchange/exchange-ps/ExchangePowerShell/Suspend-MoveRequest.md
index 36c9a4986b..d9655f431c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Suspend-MoveRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Suspend-MoveRequest.md
@@ -13,7 +13,7 @@ title: Suspend-MoveRequest
 # Suspend-MoveRequest
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Suspend-MoveRequest cmdlet to suspend a move request any time after the move request was created, but before it reaches the status of CompletionInProgress. You can resume the move request by using the Resume-MoveRequest cmdlet.
 
@@ -32,7 +32,7 @@ Suspend-MoveRequest [-Identity] <MoveRequestIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Suspend-PublicFolderMailboxMigrationRequest.md b/exchange/exchange-ps/ExchangePowerShell/Suspend-PublicFolderMailboxMigrationRequest.md
index 8cff5348ae..13bad0297d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Suspend-PublicFolderMailboxMigrationRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Suspend-PublicFolderMailboxMigrationRequest.md
@@ -13,7 +13,7 @@ title: Suspend-PublicFolderMailboxMigrationRequest
 # Suspend-PublicFolderMailboxMigrationRequest
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Suspend-PublicFolderMailboxMigrationRequest cmdlet to suspend individual jobs in public folder migration batches that were created by using the New-MigrationBatch cmdlet.
 
@@ -31,7 +31,7 @@ Suspend-PublicFolderMailboxMigrationRequest [-Identity] <PublicFolderMailboxMigr
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Suspend-PublicFolderMigrationRequest.md b/exchange/exchange-ps/ExchangePowerShell/Suspend-PublicFolderMigrationRequest.md
index d3cdd9a07d..a699004778 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Suspend-PublicFolderMigrationRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Suspend-PublicFolderMigrationRequest.md
@@ -33,7 +33,7 @@ Suspend-PublicFolderMigrationRequest [-Identity] <PublicFolderMigrationRequestId
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Suspend-PublicFolderMoveRequest.md b/exchange/exchange-ps/ExchangePowerShell/Suspend-PublicFolderMoveRequest.md
index 3642df39c3..42a675cbdb 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Suspend-PublicFolderMoveRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Suspend-PublicFolderMoveRequest.md
@@ -31,7 +31,7 @@ Suspend-PublicFolderMoveRequest [-Identity] <PublicFolderMoveRequestIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Suspend-PublicFolderReplication.md b/exchange/exchange-ps/ExchangePowerShell/Suspend-PublicFolderReplication.md
index 499d868c9f..3a6df6e1ba 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Suspend-PublicFolderReplication.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Suspend-PublicFolderReplication.md
@@ -29,7 +29,7 @@ Suspend-PublicFolderReplication [-Confirm]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Suspend-Queue.md b/exchange/exchange-ps/ExchangePowerShell/Suspend-Queue.md
index eb7ca20f2e..120227683d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Suspend-Queue.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Suspend-Queue.md
@@ -43,7 +43,7 @@ The Suspend-Queue cmdlet stops processing on a queue that has a status of Active
 
 For instructions on how to resume suspended queues, see [Resume-Queue](https://learn.microsoft.com/powershell/module/exchangepowershell/resume-queue).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-ActiveSyncConnectivity.md b/exchange/exchange-ps/ExchangePowerShell/Test-ActiveSyncConnectivity.md
index dd664d7ac3..df131fd9b3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-ActiveSyncConnectivity.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-ActiveSyncConnectivity.md
@@ -17,7 +17,7 @@ This cmdlet is available only in on-premises Exchange.
 
 Use the Test-ActiveSyncConnectivity cmdlet to test connectivity to Microsoft Exchange ActiveSync virtual directories.
 
-**Note**: This cmdlet works best in Exchange 2010. In later versions of Exchange, the functionality of this cmdlet has been replaced by Managed Availability. For the best results, use the Invoke-MonitoringProbe cmdlet and specify the relevant active monitor probe instead of using this cmdlet.
+**Note**: This cmdlet works best in Exchange 2010. In later versions of Exchange, the functionality of this cmdlet is replaced by Managed Availability. For the best results, use the Invoke-MonitoringProbe cmdlet and specify the relevant active monitor probe instead of using this cmdlet.
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
@@ -59,7 +59,7 @@ The test results are displayed on-screen. The cmdlet returns the following infor
 
 You can write the results to a file by piping the output to ConvertTo-Html and Set-Content. For example: `Test-ActiveSyncConnectivity -ClientAccessServer MBX01 | ConvertTo-Html | Set-Content -Path "C:\My Documents\EAS Test.html"`.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -276,7 +276,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-The MonitoringInstance parameter specifies an identifier for this task when the test is run from Microsoft System Center Operations Manager (SCOM). This parameter is important because SCOM may run multiple instances of the test from the same server at the same time.
+The MonitoringInstance parameter specifies an identifier for this task when the test is run from Microsoft System Center Operations Manager (SCOM). This parameter is important because SCOM might run multiple instances of the test from the same server at the same time.
 
 ```yaml
 Type: String
diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-ApplicationAccessPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Test-ApplicationAccessPolicy.md
index adf203bba5..ec8f3c76ba 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-ApplicationAccessPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-ApplicationAccessPolicy.md
@@ -29,7 +29,7 @@ Test-ApplicationAccessPolicy [-Identity] <RecipientIdParameter> -AppId <String>
 ## DESCRIPTION
 This feature applies only to apps connecting to the Microsoft Graph API for Outlook resources.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-ArchiveConnectivity.md b/exchange/exchange-ps/ExchangePowerShell/Test-ArchiveConnectivity.md
index 8ed3187035..eaa3c1bee5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-ArchiveConnectivity.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-ArchiveConnectivity.md
@@ -33,7 +33,7 @@ Test-ArchiveConnectivity [-UserSmtp] <SmtpAddress>
 ## DESCRIPTION
 Running the Test-ArchiveConnectivity cmdlet validates connectivity to a user's archive mailbox. End-to-end verification includes testing whether an on-premises or cloud-based archive is provisioned for the on-premises mailbox user and whether it's enabled and logging on to the archive mailbox on behalf of the user. Successful completion of the command indicates that processes such as the Managed Folder Assistant and Outlook on the web are able to successfully access the archive mailbox.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-AssistantHealth.md b/exchange/exchange-ps/ExchangePowerShell/Test-AssistantHealth.md
index bf783610ca..020c9680a2 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-AssistantHealth.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-AssistantHealth.md
@@ -38,7 +38,7 @@ The Mailbox Assistants service runs on all servers that have the Mailbox server
 
 By default, when you run this cmdlet, it returns the RunspaceId, events, and performance counters in a table format.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -189,7 +189,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-The WatermarkBehindWarningThreholdInMinutes parameter specifies the threshold for watermark age. Event watermarks indicate the last time that events were successfully processed by an assistant. An event watermark that hasn't been updated in a while may indicate a problem. For each Mailbox Assistant, the Test-AssistantHealth cmdlet compares the current time with the time stamp of the last event watermark to determine the watermark age. If that age exceeds the value set by the WatermarkBehindWarningThreholdInMinutes parameter, a warning is generated.
+The WatermarkBehindWarningThreholdInMinutes parameter specifies the threshold for watermark age. Event watermarks indicate the last time that events were successfully processed by an assistant. An event watermark that hasn't been updated in a while might indicate a problem. For each Mailbox Assistant, the Test-AssistantHealth cmdlet compares the current time with the time stamp of the last event watermark to determine the watermark age. If that age exceeds the value set by the WatermarkBehindWarningThreholdInMinutes parameter, a warning is generated.
 
 You can specify a value from 1 through 10080 minutes. The default value is 60 minutes.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-CalendarConnectivity.md b/exchange/exchange-ps/ExchangePowerShell/Test-CalendarConnectivity.md
index 4053d7ba11..159c954cd1 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-CalendarConnectivity.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-CalendarConnectivity.md
@@ -17,7 +17,7 @@ This cmdlet is available only in on-premises Exchange.
 
 Use the Test-CalendarConnectivity cmdlet to verify that anonymous calendar sharing is enabled and working properly. The Calendar virtual directory is a subdirectory of the Microsoft Outlook on the web virtual directories. When you run this command without any parameters, the command tests calendar connectivity against all Outlook on the web virtual directories.
 
-**Note**: This cmdlet works best in Exchange 2010. In later versions of Exchange, the functionality of this cmdlet has been replaced by Managed Availability. For the best results, use the Invoke-MonitoringProbe cmdlet and specify the relevant active monitor probe instead of using this cmdlet.
+**Note**: This cmdlet works best in Exchange 2010. In later versions of Exchange, the functionality of this cmdlet is replaced by Managed Availability. For the best results, use the Invoke-MonitoringProbe cmdlet and specify the relevant active monitor probe instead of using this cmdlet.
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
@@ -59,7 +59,7 @@ The test results are displayed on-screen. The cmdlet returns the following infor
 
 You can write the results to a file by piping the output to ConvertTo-Html and Set-Content. For example: `Test-CalendarConnectivity -ClientAccessServer MBX01 | ConvertTo-Html | Set-Content -Path "C:\My Documents\Calendar Test.html"`.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-ClientAccessRule.md b/exchange/exchange-ps/ExchangePowerShell/Test-ClientAccessRule.md
index 85272491f6..8eb927c992 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-ClientAccessRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-ClientAccessRule.md
@@ -16,7 +16,7 @@ title: Test-ClientAccessRule
 > [!NOTE]
 > Beginning in October 2022, client access rules were deprecated for all Exchange Online organizations that weren't using them. Client access rules will be deprecated for all remaining organizations on September 1, 2025. If you choose to turn off client access rules before the deadline, the feature will be disabled in your organization. For more information, see [Update on Client Access Rules Deprecation in Exchange Online](https://techcommunity.microsoft.com/blog/exchange/update-on-client-access-rules-deprecation-in-exchange-online/4354809).
 
-This cmdlet is functional only in Exchange Server 2019 and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is functional only in Exchange Server 2019 and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Test-ClientAccessRule cmdlet to test how client access rules affect access to your organization. If any of the client properties you specify for this cmdlet match any client access rules, the rules are returned in the results.
 
@@ -42,7 +42,7 @@ Client access rules are like mail flow rules (also known as transport rules) for
 - RemotePowerShell:BasicAuthentication and NonBasicAuthentication.
 - ExchangeActiveSync:BasicAuthentication, OAuthAuthentication, and CertificateBasedAuthentication.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-DataClassification.md b/exchange/exchange-ps/ExchangePowerShell/Test-DataClassification.md
index f9003e70b8..ce07e02eed 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-DataClassification.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-DataClassification.md
@@ -13,7 +13,7 @@ title: Test-DataClassification
 # Test-DataClassification
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Test-DataClassification cmdlet to find the confidence and count of a sensitive information type that's found in a specified text string.
 
@@ -34,7 +34,7 @@ Test-DataClassification
 ## DESCRIPTION
 This cmdlet lets you know the classification results that are returned by the Microsoft classification engine in specific text. The classification results include the sensitive type, its count, and confidence.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-EcpConnectivity.md b/exchange/exchange-ps/ExchangePowerShell/Test-EcpConnectivity.md
index 36fa0baa49..8ee2056293 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-EcpConnectivity.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-EcpConnectivity.md
@@ -17,7 +17,7 @@ This cmdlet is available only in on-premises Exchange.
 
 Use the Test-EcpConnectivity cmdlet to test connectivity to Exchange Control Panel (ECP) virtual directories.
 
-**Note**: This cmdlet works best in Exchange 2010. In later versions of Exchange, the functionality of this cmdlet has been replaced by Managed Availability. For the best results, use the Invoke-MonitoringProbe cmdlet and specify the relevant active monitor probe instead of using this cmdlet.
+**Note**: This cmdlet works best in Exchange 2010. In later versions of Exchange, the functionality of this cmdlet is replaced by Managed Availability. For the best results, use the Invoke-MonitoringProbe cmdlet and specify the relevant active monitor probe instead of using this cmdlet.
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
@@ -58,7 +58,7 @@ The test results are displayed on-screen. The cmdlet returns the following infor
 
 You can write the results to a file by piping the output to ConvertTo-Html and Set-Content. For example: `Test-EcpConnectivity -ClientAccessServer MBX01 | ConvertTo-Html | Set-Content -Path "C:\My Documents\EAC Test.html"`.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-EdgeSynchronization.md b/exchange/exchange-ps/ExchangePowerShell/Test-EdgeSynchronization.md
index 46379fa713..6d52fd1d73 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-EdgeSynchronization.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-EdgeSynchronization.md
@@ -44,11 +44,11 @@ Test-EdgeSynchronization [-ExcludeRecipientTest]
 ```
 
 ## DESCRIPTION
-The Test-EdgeSynchronization cmdlet is a diagnostic cmdlet that provides a report of the synchronization status of subscribed Edge Transport servers. You can use the VerifyRecipient parameter with this cmdlet to verify that a single recipient has been synchronized to the Active Directory Lightweight Directory Services (AD LDS) instance. The Edge Subscription process establishes one-way replication of recipient and configuration information from Active Directory to AD LDS.
+The Test-EdgeSynchronization cmdlet is a diagnostic cmdlet that provides a report of the synchronization status of subscribed Edge Transport servers. You can use the VerifyRecipient parameter with this cmdlet to verify that a single recipient is synchronized to the Active Directory Lightweight Directory Services (AD LDS) instance. The Edge Subscription process establishes one-way replication of recipient and configuration information from Active Directory to AD LDS.
 
 This cmdlet compares the data stored in Active Directory and the data stored in AD LDS. Any inconsistencies in data are reported in the results output by this cmdlet.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -190,7 +190,7 @@ Accept wildcard characters: False
 The MonitoringContext parameter specifies whether to include the associated monitoring events and performance counters in the results. Valid values are:
 
 - $true: Monitoring events and performance counters are included in the command results. Typically, you include the monitoring events and performance counters in the results when the output is passed to Microsoft System Center Operations Manager (SCOM).
-- $false: Monitoring events and performance counters aren't included in the command results. This is the default value.
+- $false: Monitoring events and performance counters aren't included in the command results. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -210,7 +210,7 @@ Accept wildcard characters: False
 
 The TargetServer parameter specifies an Edge Transport server to initiate edge synchronization with. If omitted, all Edge Transport servers are synchronized.
 
-You may want to use this parameter to specify a single Edge Transport server for synchronization if a new Edge Transport server has been installed or if that Edge Transport server has been unavailable for some time.
+You might want to use this parameter to specify a single Edge Transport server for synchronization if a new Edge Transport server is installed or if that Edge Transport server is unavailable for some time.
 
 ```yaml
 Type: String
diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-ExchangeSearch.md b/exchange/exchange-ps/ExchangePowerShell/Test-ExchangeSearch.md
index b8ccea20c0..2e3de30489 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-ExchangeSearch.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-ExchangeSearch.md
@@ -60,7 +60,7 @@ The Test-ExchangeSearch cmdlet creates a hidden message and an attachment in the
 
 You can use the Verbose switch to get detailed information about each step performed by the cmdlet as part of the test.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-FederationTrust.md b/exchange/exchange-ps/ExchangePowerShell/Test-FederationTrust.md
index 691cbaca05..1337a5ab35 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-FederationTrust.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-FederationTrust.md
@@ -43,7 +43,7 @@ The Test-FederationTrust cmdlet runs the following series of tests to ensure tha
 - Certificates are checked to ensure they're valid and can be used with the Microsoft Federation Gateway.
 - A security token is requested from the Microsoft Federation Gateway. This test ensures that a token can be properly retrieved and used.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -102,7 +102,7 @@ Accept wildcard characters: False
 The MonitoringContext parameter specifies whether to include the associated monitoring events and performance counters in the results. Valid values are:
 
 - $true: Monitoring events and performance counters are included in the command results. Typically, you include the monitoring events and performance counters in the results when the output is passed to Microsoft System Center Operations Manager (SCOM).
-- $false: Monitoring events and performance counters aren't included in the command results. This is the default value.
+- $false: Monitoring events and performance counters aren't included in the command results. This value is the default.
 
 ```yaml
 Type: Boolean
diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-FederationTrustCertificate.md b/exchange/exchange-ps/ExchangePowerShell/Test-FederationTrustCertificate.md
index 15940fa909..96a42d4b29 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-FederationTrustCertificate.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-FederationTrustCertificate.md
@@ -31,7 +31,7 @@ Test-FederationTrustCertificate [-Confirm]
 ## DESCRIPTION
 The certificate used to establish a federation trust is propagated to all Exchange servers in the organization.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-IRMConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Test-IRMConfiguration.md
index 630e6705f1..cae7553941 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-IRMConfiguration.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-IRMConfiguration.md
@@ -13,7 +13,7 @@ title: Test-IRMConfiguration
 # Test-IRMConfiguration
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Test-IRMConfiguration cmdlet to test Information Rights Management (IRM) configuration and functionality.
 
@@ -34,7 +34,7 @@ Test-IRMConfiguration [[-Identity] <OrganizationIdParameter>] -Sender <SmtpAddre
 ## DESCRIPTION
 The Test-IRMConfiguration cmdlet performs a series of steps to test IRM configuration and functionality, including availability of an Active Directory Rights Management Services (AD RMS) server, prelicensing and journal report decryption. In Exchange Online organizations, it checks connectivity to RMS Online and obtains and validates the organization's Trusted Publishing Domain (TPD).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-ImapConnectivity.md b/exchange/exchange-ps/ExchangePowerShell/Test-ImapConnectivity.md
index b6812f1335..ed70baf7d5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-ImapConnectivity.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-ImapConnectivity.md
@@ -17,7 +17,7 @@ This cmdlet is available only in on-premises Exchange.
 
 Use the Test-ImapConnectivity cmdlet to verify that connectivity to the Microsoft Exchange IMAP4 service is working as expected.
 
-**Note**: This cmdlet works best in Exchange 2010. In later versions of Exchange, the functionality of this cmdlet has been replaced by Managed Availability. For the best results, use the Invoke-MonitoringProbe cmdlet and specify the relevant active monitor probe instead of using this cmdlet.
+**Note**: This cmdlet works best in Exchange 2010. In later versions of Exchange, the functionality of this cmdlet is replaced by Managed Availability. For the best results, use the Invoke-MonitoringProbe cmdlet and specify the relevant active monitor probe instead of using this cmdlet.
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
@@ -59,7 +59,7 @@ The test results are displayed on-screen. The cmdlet returns the following infor
 
 You can write the results to a file by piping the output to ConvertTo-Html and Set-Content. For example: `Test-IMAPConnectivity -ClientAccessServer MBX01 | ConvertTo-Html | Set-Content -Path "C:\My Documents\IMAP Test.html"`.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 **Note**: In Exchange 2013 or later, when you run this command to test a single mailbox on an Exchange server that isn't hosting the active mailbox database copy for the mailbox, you might see the following error message:
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-M365DataAtRestEncryptionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Test-M365DataAtRestEncryptionPolicy.md
index ce462c6e24..f6dcd67b34 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-M365DataAtRestEncryptionPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-M365DataAtRestEncryptionPolicy.md
@@ -30,7 +30,7 @@ Test-M365DataAtRestEncryptionPolicy [[-Identity] <DataEncryptionPolicyIdParamete
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-MAPIConnectivity.md b/exchange/exchange-ps/ExchangePowerShell/Test-MAPIConnectivity.md
index 423f2aba20..b144800754 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-MAPIConnectivity.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-MAPIConnectivity.md
@@ -13,7 +13,7 @@ title: Test-MAPIConnectivity
 # Test-MAPIConnectivity
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Test-MapiConnectivity cmdlet to verify server functionality by logging on to the mailbox that you specify. If you don't specify a mailbox, the cmdlet logs on to the SystemMailbox on the database that you specify.
 
@@ -75,7 +75,7 @@ There are three distinct parameters that you can use with the command: Database,
 - The Identity parameter takes a mailbox identity and tests the ability to log on to a specific mailbox.
 - The Server parameter takes a server identity and tests the ability to log on to each system mailbox on the specified server.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -317,7 +317,7 @@ This parameter is available only in on-premises Exchange.
 The MonitoringContext parameter specifies whether to include the associated monitoring events and performance counters in the results. Valid values are:
 
 - $true: Monitoring events and performance counters are included in the command results. Typically, you include the monitoring events and performance counters in the results when the output is passed to Microsoft System Center Operations Manager (SCOM).
-- $false: Monitoring events and performance counters aren't included in the command results. This is the default value.
+- $false: Monitoring events and performance counters aren't included in the command results. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -357,7 +357,7 @@ Accept wildcard characters: False
 
 This parameter is available only in on-premises Exchange.
 
-The Server parameter specifies the server on which you will test the MAPI connectivity. The command tests the MAPI connectivity to each system mailbox hosted on active databases on the specified server. You can use any value that uniquely identifies the server. For example:
+The Server parameter specifies the server to test MAPI connectivity on. The command tests the MAPI connectivity to each system mailbox hosted on active databases on the specified server. You can use any value that uniquely identifies the server. For example:
 
 - Name
 - FQDN
diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-MRSHealth.md b/exchange/exchange-ps/ExchangePowerShell/Test-MRSHealth.md
index 36a7b10727..ab340d8e87 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-MRSHealth.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-MRSHealth.md
@@ -36,7 +36,7 @@ Test-MRSHealth [[-Identity] <ServerIdParameter>]
 ## DESCRIPTION
 The Microsoft Exchange Mailbox Replication service runs on Mailbox servers. This command ensures that the Mailbox Replication service is running and that it responds to a remote procedure call (RPC) ping check.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -145,7 +145,7 @@ Accept wildcard characters: False
 The MonitoringContext parameter specifies whether to include the associated monitoring events and performance counters in the results. Valid values are:
 
 - $true: Monitoring events and performance counters are included in the command results. Typically, you include the monitoring events and performance counters in the results when the output is passed to Microsoft System Center Operations Manager (SCOM).
-- $false: Monitoring events and performance counters aren't included in the command results. This is the default value.
+- $false: Monitoring events and performance counters aren't included in the command results. This value is the default.
 
 ```yaml
 Type: Boolean
diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-Mailflow.md b/exchange/exchange-ps/ExchangePowerShell/Test-Mailflow.md
index b233b26e4c..cd3071a0cd 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-Mailflow.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-Mailflow.md
@@ -115,7 +115,7 @@ The Test-Mailflow results are displayed on-screen. The interesting values in the
 
 You can write the Test-Mailflow results to a file by piping the output to ConvertTo-Html or ConvertTo-Csv and adding ` > <filename>` to the command. For example: `Test-Mailflow -AutoDiscoverTargetMailboxServer | ConvertTo-Csv > "C:\My Documents\test-mailflow 2020-05-01.csv"`.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -124,7 +124,7 @@ You need to be assigned permissions before you can run this cmdlet. Although thi
 Test-Mailflow Mailbox1 -TargetMailboxServer Mailbox2
 ```
 
-This example tests message flow from the server name Mailbox1 to the server named Mailbox2. Note that you need to run this command while connected to Mailbox1.
+This example tests message flow from the server name Mailbox1 to the server named Mailbox2. You need to run this command while connected to Mailbox1.
 
 ### Example 2
 ```powershell
@@ -186,7 +186,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-The CrossPremises parameter specifies whether the mail flow test will be conducted in cross-premises mode.
+The CrossPremises parameter specifies whether the mail flow test is conducted in cross-premises mode.
 
 Set this parameter to $true if your organization is using a cross-premises deployment and you want to verify cross-premises mail flow.
 
@@ -409,7 +409,7 @@ Accept wildcard characters: False
 The MonitoringContext parameter specifies whether to include the associated monitoring events and performance counters in the results. Valid values are:
 
 - $true: Monitoring events and performance counters are included in the command results. Typically, you include the monitoring events and performance counters in the results when the output is passed to Microsoft System Center Operations Manager (SCOM).
-- $false: Monitoring events and performance counters aren't included in the command results. This is the default value.
+- $false: Monitoring events and performance counters aren't included in the command results. This value is the default.
 
 ```yaml
 Type: Boolean
diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-Message.md b/exchange/exchange-ps/ExchangePowerShell/Test-Message.md
index 38282de336..3ec53636f8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-Message.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-Message.md
@@ -15,7 +15,7 @@ title: Test-Message
 ## SYNOPSIS
 This cmdlet is functional only in the cloud-based service.
 
-Use the Test-Message cmdlet to simulate and report on the effects of mail flow rules (transport rules) and unified DLP rules on test email messages. Because this cmdlet introduces email into the DLP evaluation pipeline, actions such as Block, Moderate, etc. can take place on the test message. Related notifications will also be sent to any configured recipients.
+Use the Test-Message cmdlet to simulate and report on the effects of mail flow rules (transport rules) and unified DLP rules on test email messages. Because this cmdlet introduces email into the DLP evaluation pipeline, actions such as Block, Moderate, etc. can take place on the test message. Related notifications are also sent to any configured recipients.
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
@@ -45,7 +45,7 @@ Test-Message -Recipients <ProxyAddressCollection> -SendReportTo <RecipientIdPara
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-MigrationServerAvailability.md b/exchange/exchange-ps/ExchangePowerShell/Test-MigrationServerAvailability.md
index 7f8ff1c92e..083393ed0a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-MigrationServerAvailability.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-MigrationServerAvailability.md
@@ -13,7 +13,7 @@ title: Test-MigrationServerAvailability
 # Test-MigrationServerAvailability
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Test-MigrationServerAvailability cmdlet to test the availability of the target server in preparation to perform cross-forest mailbox moves, migration of on-premises mailboxes to Exchange Online, or to migrate on-premises mailbox data from an IMAP server to Exchange Online mailboxes. For all migration types, the cmdlet attempts to verify the connection settings used to connect to the target server.
 
@@ -179,7 +179,7 @@ If the verification is successful, you can use the same settings to create a mig
 - New-MigrationEndpoint
 - New-MigrationBatch
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -572,7 +572,7 @@ Accept wildcard characters: False
 
 This parameter is available only in the cloud-based service.
 
-The ServiceAccountKeyFileData parameter is used to specify information needed to authenticate as a service account. The data should come from the JSON key file that is downloaded when the service account that has been granted access to your remote tenant is created.
+The ServiceAccountKeyFileData parameter is used to specify information needed to authenticate as a service account. The data should come from the JSON key file that is downloaded when the service account that is granted access to your remote tenant is created.
 
 A valid value for this parameter requires you to read the file to a byte-encoded object using the following syntax: `([System.IO.File]::ReadAllBytes('<Path>\<FileName>'))`. You can use this command as the parameter value, or you can write the output to a variable (`$data = [System.IO.File]::ReadAllBytes('<Path>\<FileName>')`) and use the variable as the parameter value (`$data`).
 
@@ -594,7 +594,7 @@ Accept wildcard characters: False
 
 This parameter is available only in the cloud-based service.
 
-The SourceMailboxLegacyDN parameter specifies a mailbox on the target server. Use the LegacyExchangeDN for the on-premises test mailbox as the value for this parameter. The cmdlet will attempt to access this mailbox using the credentials for the administrator account on the target server.
+The SourceMailboxLegacyDN parameter specifies a mailbox on the target server. Use the LegacyExchangeDN for the on-premises test mailbox as the value for this parameter. The cmdlet attempts to access this mailbox using the credentials for the administrator account on the target server.
 
 ```yaml
 Type: String
@@ -699,8 +699,8 @@ The MailboxPermission parameter specifies what permissions are assigned to the m
 
 Specify one of the following values for the account defined by the Credentials parameter:
 
-- FullAccess: The account has been assigned the Full-Access permission to the mailboxes that will be migrated.
-- Admin: The account is a member of the Domain Admins group in the organization that hosts the mailboxes that will be migrated.
+- FullAccess: The account is assigned the Full-Access permission to the mailboxes to be migrated.
+- Admin: The account is a member of the Domain Admins group in the organization that hosts the mailboxes to be migrated.
 
 This parameter isn't used for testing the connection to the remote server for a remote move migration or an IMAP migration.
 
@@ -762,7 +762,7 @@ Accept wildcard characters: False
 
 This parameter is available only in the cloud-based service.
 
-The TestMailbox parameter specifies a mailbox on the target server. Use the primary SMTP address as the value for this parameter. The cmdlet will attempt to access this mailbox using the credentials for the administrator account on the target server.
+The TestMailbox parameter specifies a mailbox on the target server. Use the primary SMTP address as the value for this parameter. The cmdlet attempts to access this mailbox using the credentials for the administrator account on the target server.
 
 ```yaml
 Type: MailboxIdParameter
diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-OAuthConnectivity.md b/exchange/exchange-ps/ExchangePowerShell/Test-OAuthConnectivity.md
index 5af0c9a463..1b6bbe9634 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-OAuthConnectivity.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-OAuthConnectivity.md
@@ -13,7 +13,7 @@ title: Test-OAuthConnectivity
 # Test-OAuthConnectivity
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Test-OAuthConnectivity cmdlet to test OAuth authentication to partner applications for a user.
 
@@ -35,7 +35,7 @@ Test-OAuthConnectivity -Service <ModServiceType> -TargetUri <Uri>
 ## DESCRIPTION
 SharePoint, Lync and Skype for Business partner applications are automatically created in on-premises Exchange deployments. For the Test-OAuthConnectivity cmdlet to succeed for other partner applications in on-premises deployments, you first need to create the partner application by using the Configure-EnterprisePartnerApplication.ps1 script that's available in the %ExchangeInstallPath%Scripts folder ($env:ExchangeInstallPath\Scripts in PowerShell).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -92,7 +92,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
 
-The AppOnly switch specifies the cmdlet will authenticate to the specified service as Exchange without any user context. You don't need to specify a value with this switch.
+The AppOnly switch specifies the cmdlet authenticates to the specified service as Exchange without any user context. You don't need to specify a value with this switch.
 
 ```yaml
 Type: SwitchParameter
@@ -180,7 +180,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
 
-The UseCachedToken switch specifies that OAuth will try to use an existing, cached authorization token. You don't need to specify a value with this switch.
+The UseCachedToken switch specifies that OAuth tries to use an existing, cached authorization token. You don't need to specify a value with this switch.
 
 ```yaml
 Type: SwitchParameter
diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-OrganizationRelationship.md b/exchange/exchange-ps/ExchangePowerShell/Test-OrganizationRelationship.md
index df35984338..a0ebecd19c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-OrganizationRelationship.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-OrganizationRelationship.md
@@ -13,7 +13,7 @@ title: Test-OrganizationRelationship
 # Test-OrganizationRelationship
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Test-OrganizationRelationship cmdlet to verify that the organization relationship is properly configured and functioning as expected.
 
@@ -30,11 +30,11 @@ Test-OrganizationRelationship [[-Identity] <OrganizationRelationshipIdParameter>
 ```
 
 ## DESCRIPTION
-The Test-OrganizationRelationship cmdlet doesn't include any functional tests of federated sharing features, such as accessing user free/busy information or moving mailboxes between organizations. It only verifies that the configuration will allow these features to work correctly.
+The Test-OrganizationRelationship cmdlet doesn't include any functional tests of federated sharing features, such as accessing user free/busy information or moving mailboxes between organizations. The cmdlet only verifies that the configuration allows these features to work correctly.
 
 Before you can test an organization relationship, you must first create an organization relationship. For more information, see [Create an organization relationship](https://learn.microsoft.com/exchange/create-an-organization-relationship-exchange-2013-help).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-OutlookConnectivity.md b/exchange/exchange-ps/ExchangePowerShell/Test-OutlookConnectivity.md
index dd41d9350f..cb6b39db02 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-OutlookConnectivity.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-OutlookConnectivity.md
@@ -95,7 +95,7 @@ Test-OutlookConnectivity [[-Identity] <MailboxIdParameter>] -WSTestType <Virtual
 ## DESCRIPTION
 Running the Test-OutlookConnectivity cmdlet validates an Outlook connection defined by the provided parameters. The command is able to validate a single mailbox.
 
-The Test-OutlookConnectivity cmdlet runs the same process as the monitoring probes. The Microsoft Exchange Health Manager (MSExchangeHM) service must be running and have created the Outlook probes on the machine that will be tested. You need to select one of the Outlook probe identities to run the test. Use the [Get-MonitoringItemIdentity](https://learn.microsoft.com/powershell/module/exchangepowershell/get-monitoringitemidentity) cmdlet to see what probes are active.
+The Test-OutlookConnectivity cmdlet runs the same process as the monitoring probes. The Microsoft Exchange Health Manager (MSExchangeHM) service must be running and created the Outlook probes on the machine to be tested. You need to select one of the Outlook probe identities to run the test. Use the [Get-MonitoringItemIdentity](https://learn.microsoft.com/powershell/module/exchangepowershell/get-monitoringitemidentity) cmdlet to see what probes are active.
 
 This example lists the probes running in the backend services on a Mailbox server: `Get-MonitoringItemIdentity -Server MailboxServer1 -Identity outlook.protocol | ?{$_.Name -like '*probe'}`.
 
@@ -103,13 +103,13 @@ This example lists the probes running in the client access services on a Mailbox
 
 For more information on probes and the monitoring framework, see [Managed Availability](https://learn.microsoft.com/exchange/managed-availability-exchange-2013-help), [Managed Availability and Server Health](https://techcommunity.microsoft.com/t5/exchange-team-blog/managed-availability-and-server-health/ba-p/593180), and [Customizing Managed Availability](https://techcommunity.microsoft.com/t5/exchange-team-blog/customizing-managed-availability/ba-p/592164).
 
-By default, the cmdlet uses the test monitoring account attached to the specified probe. You may enter a different mailbox instead via the MailboxId parameter. The options and results follow.
+By default, the cmdlet uses the test monitoring account attached to the specified probe. You might enter a different mailbox instead via the MailboxId parameter. The options and results follow.
 
 - MailboxId and Credential are not specified: Generic connectivity test against a test mailbox using the system's test credentials.
 - MailboxId is specified, Credential is not: Connectivity test to the specific mailbox using the system's test credentials.
 - MailboxId and Credential are both specified: You get a connectivity test to the specific mailbox, and also a test that the credentials provided are valid for that mailbox
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -125,7 +125,7 @@ In Exchange 2013 or later, this example runs an MAPI over HTTP OutlookRpcSelfTes
 Test-OutlookConnectivity "Outlook.Protocol\OutlookRpcDeepTestProbe\Mailbox Database 1234512345" -RunFromServerId PrimaryMailbox -MailboxId johnd@contoso.com
 ```
 
-In Exchange 2013 or later, this example runs the OutlookRpcDeepTestProbe from the "PrimaryMailbox" server for the mailbox "johnd@contoso.com" mounted on "Mailbox Database 1234512345". Because the Credential parameter is not specified, the probe will use the default testing credentials.
+In Exchange 2013 or later, this example runs the OutlookRpcDeepTestProbe from the "PrimaryMailbox" server for the mailbox `johnd@contoso.com` mounted on "Mailbox Database 1234512345". Because the Credential parameter is not specified, the probe uses the default testing credentials.
 
 ### Example 3
 ```powershell
@@ -192,14 +192,14 @@ The ProbeIdentity parameter specifies the probe to use. Valid values are:
 Outlook Anywhere (RPC over HTTP) probes:
 
 - `Outlook.Protocol\OutlookRpcSelfTestProbe`: Validates that the RPC/HTTP endpoint is able to receive traffic on the Mailbox server. It does not attempt to log in to a mailbox. It is a high level check of connectivity.
-- `Outlook.Protocol\OutlookRpcDeepTestProbe`: Validates that the RPC/HTTP endpoint is working on the Mailbox server. It will attempt to connect to and log in to the mailbox. Since no database is specified, it will attempt to connect to the first database returned by the Get-MailboxDatabase cmdlet.
-- `Outlook.Protocol\OutlookRpcDeepTestProbe\<Case-sensitive Mailbox Database Name>`: Validates that the RPC/HTTP endpoint is working on the Mailbox Server. It will attempt to connect to and log in to the mailbox in the specified mailbox database. If the mailbox database name contains spaces, enclose the entire value in quotation marks (for example, `"Outlook.Protocol\OutlookRpcDeepTestProbe\Mailbox Database 0352791530"`).
+- `Outlook.Protocol\OutlookRpcDeepTestProbe`: Validates that the RPC/HTTP endpoint is working on the Mailbox server. It attempts to connect to and log in to the mailbox. Since no database is specified, it attempts to connect to the first database returned by the Get-MailboxDatabase cmdlet.
+- `Outlook.Protocol\OutlookRpcDeepTestProbe\<Case-sensitive Mailbox Database Name>`: Validates that the RPC/HTTP endpoint is working on the Mailbox Server. It attempts to connect to and log in to the mailbox in the specified mailbox database. If the mailbox database name contains spaces, enclose the entire value in quotation marks (for example, `"Outlook.Protocol\OutlookRpcDeepTestProbe\Mailbox Database 0352791530"`).
 
 MAPI over HTTP probes:
 
 - `OutlookMapiHttp.Protocol\OutlookMapiHttpSelfTestProbe`: Validates that the MAPI/HTTP endpoint is able to receive traffic on the Mailbox server. It does not attempt to log in to a mailbox. It is a high level check of connectivity.
-- `OutlookMapiHttp.Protocol\OutlookMapiHttpDeepTestProbe`: Validates that the MAPI/HTTP endpoint is working on the Mailbox server. It will attempt to connect and log in to the mailbox. Since no database is specified, it will attempt to connect to the first database returned by the Get-MailboxDatabase cmdlet.
-- `OutlookMapiHttp.Protocol\OutlookRpcDeepTestProbe\<Case-sensitive Mailbox Database Name>`: Validates that the MAPI/HTTP endpoint is working on the Mailbox Server. It will attempt to connect and log in to the mailbox in the specified database. If the mailbox database name contains spaces, enclose the entire value in quotation marks (for example, `"Outlook.Protocol\OutlookRpcDeepTestProbe\Mailbox Database 0352791530"`).
+- `OutlookMapiHttp.Protocol\OutlookMapiHttpDeepTestProbe`: Validates that the MAPI/HTTP endpoint is working on the Mailbox server. It attempts to connect and log in to the mailbox. Since no database is specified, it attempts to connect to the first database returned by the Get-MailboxDatabase cmdlet.
+- `OutlookMapiHttp.Protocol\OutlookRpcDeepTestProbe\<Case-sensitive Mailbox Database Name>`: Validates that the MAPI/HTTP endpoint is working on the Mailbox Server. It attempts to connect and log in to the mailbox in the specified database. If the mailbox database name contains spaces, enclose the entire value in quotation marks (for example, `"Outlook.Protocol\OutlookRpcDeepTestProbe\Mailbox Database 0352791530"`).
 
 ```yaml
 Type: String
@@ -284,7 +284,7 @@ This parameter is available only in Exchange Server 2010.
 
 The WSTestType parameter specifies type of servers that you want to include in your Outlook connectivity test. You can use the following values:
 
-- Unknown (This is the default value.)
+- Unknown (This value is the default.)
 - Internal
 - External
 
@@ -310,7 +310,7 @@ The Archive parameter specifies whether tests should be performed to connect to
 
 $true: Connect to the user's on-premises archive mailbox.
 
-$false: Don't connect to the user's on-premises mailbox. This is the default value.
+$false: Don't connect to the user's on-premises mailbox. This value is the default.
 
 ```yaml
 Type: Boolean
@@ -593,7 +593,9 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-The TimeOutSeconds parameter specifies the timeout period in seconds before the probe is ended. The default value is 30 seconds. The digits can be entered with or with the use of quotation marks. Either 10 or "10" will work. Any input error will default back to 30 seconds.
+The TimeOutSeconds parameter specifies the timeout period in seconds before the probe is ended. A valid value is an integer. The default value is 30 seconds.
+
+The default value is used if you specify invalid values for this parameter.
 
 ```yaml
 Type: String
diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-OutlookWebServices.md b/exchange/exchange-ps/ExchangePowerShell/Test-OutlookWebServices.md
index e0b137c685..fab514e05d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-OutlookWebServices.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-OutlookWebServices.md
@@ -66,7 +66,7 @@ Test-OutlookWebServices [[-Identity] <MailboxIdParameter>] [-MonitoringContext]
 ## DESCRIPTION
 The Test-OutlookWebServices cmdlet uses a specified address to verify that the Outlook provider is configured correctly.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -226,7 +226,7 @@ Accept wildcard characters: False
 The MonitoringContext parameter specifies whether to include the associated monitoring events and performance counters in the results. Valid values are:
 
 - $true: Monitoring events and performance counters are included in the command results. Typically, you include the monitoring events and performance counters in the results when the output is passed to Microsoft System Center Operations Manager (SCOM).
-- $false: Monitoring events and performance counters aren't included in the command results. This is the default value.
+- $false: Monitoring events and performance counters aren't included in the command results. This value is the default.
 
 ```yaml
 Type: Boolean

From 42e431c5609af1353963e64c2c1cc7850071101a Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Wed, 6 Aug 2025 10:54:07 -0700
Subject: [PATCH 122/145] Update Get-CsTeamsPersonalAttendantPolicy.md

---
 .../MicrosoftTeams/Get-CsTeamsPersonalAttendantPolicy.md        | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/teams/teams-ps/MicrosoftTeams/Get-CsTeamsPersonalAttendantPolicy.md b/teams/teams-ps/MicrosoftTeams/Get-CsTeamsPersonalAttendantPolicy.md
index 7c200d7327..508d9e4005 100644
--- a/teams/teams-ps/MicrosoftTeams/Get-CsTeamsPersonalAttendantPolicy.md
+++ b/teams/teams-ps/MicrosoftTeams/Get-CsTeamsPersonalAttendantPolicy.md
@@ -14,6 +14,8 @@ manager: jomarque
 
 ## SYNOPSIS
 
+Test
+
 **Limited Preview:** Functionality described in this document is currently in limited preview and only authorized organizations have access.
 
 Returns information about the Teams personal attendant policies configured for use in your organization.

From 10e97ab7161480d5eb65bf21b12f0e197da6e2cb Mon Sep 17 00:00:00 2001
From: Chris Davis <chris.davis@microsoft.com>
Date: Wed, 6 Aug 2025 11:01:55 -0700
Subject: [PATCH 123/145] Acrolinx 16

---
 .../ExchangePowerShell/Test-OwaConnectivity.md   |  4 ++--
 .../ExchangePowerShell/Test-PopConnectivity.md   |  4 ++--
 .../Test-PowerShellConnectivity.md               |  4 ++--
 .../ExchangePowerShell/Test-ReplicationHealth.md |  4 ++--
 .../ExchangePowerShell/Test-SenderId.md          |  2 +-
 .../ExchangePowerShell/Test-ServiceHealth.md     |  6 +++---
 .../Test-ServicePrincipalAuthorization.md        |  2 +-
 .../ExchangePowerShell/Test-SiteMailbox.md       |  2 +-
 .../ExchangePowerShell/Test-SmtpConnectivity.md  |  4 ++--
 .../ExchangePowerShell/Test-SystemHealth.md      |  2 +-
 .../ExchangePowerShell/Test-TextExtraction.md    |  4 ++--
 .../ExchangePowerShell/Test-UMConnectivity.md    |  8 ++++----
 .../Test-WebServicesConnectivity.md              |  4 ++--
 .../Undo-SoftDeletedMailbox.md                   |  8 ++++----
 .../Undo-SoftDeletedUnifiedGroup.md              |  2 +-
 .../Uninstall-TransportAgent.md                  |  2 +-
 .../ExchangePowerShell/Update-AddressList.md     |  2 +-
 .../Update-ComplianceCaseMember.md               |  2 +-
 .../ExchangePowerShell/Update-DatabaseSchema.md  |  4 ++--
 .../Update-DistributionGroupMember.md            |  8 ++++----
 .../Update-EmailAddressPolicy.md                 |  2 +-
 .../ExchangePowerShell/Update-ExchangeHelp.md    |  4 ++--
 .../Update-FileDistributionService.md            |  2 +-
 .../Update-GlobalAddressList.md                  |  2 +-
 .../Update-HybridConfiguration.md                |  4 ++--
 .../Update-MailboxDatabaseCopy.md                |  4 ++--
 .../Update-OfflineAddressBook.md                 |  2 +-
 .../ExchangePowerShell/Update-PublicFolder.md    |  2 +-
 .../Update-PublicFolderHierarchy.md              |  2 +-
 .../Update-PublicFolderMailbox.md                | 16 ++++++++--------
 .../ExchangePowerShell/Update-Recipient.md       |  4 ++--
 .../ExchangePowerShell/Update-RoleGroupMember.md |  6 +++---
 .../ExchangePowerShell/Update-SafeList.md        |  6 +++---
 .../ExchangePowerShell/Update-SiteMailbox.md     |  8 +++++---
 .../Update-StoreMailboxState.md                  |  6 +++---
 .../Update-eDiscoveryCaseAdmin.md                |  2 +-
 .../Upgrade-DistributionGroup.md                 |  2 +-
 .../Validate-OutboundConnector.md                |  2 +-
 .../ExchangePowerShell/Write-AdminAuditLog.md    |  4 ++--
 39 files changed, 80 insertions(+), 78 deletions(-)

diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-OwaConnectivity.md b/exchange/exchange-ps/ExchangePowerShell/Test-OwaConnectivity.md
index 05d8755233..4144d034bc 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-OwaConnectivity.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-OwaConnectivity.md
@@ -63,13 +63,13 @@ If the server hosting the test mailbox isn't available, the Test-OwaConnectivity
 
 If you run the Test-OwaConnectivity cmdlet on a Client Access server without using either the ClientAccessServer parameter or the URL parameter, the cmdlet tests the server on which you run the cmdlet. To test a specific Client Access server, use the ClientAccessServer parameter.
 
-To test a single URL, run the Test-OwaConnectivity cmdlet with the URL parameter and credentials for an existing Exchange mailbox. If the URL is behind a load balancer, you can't predict which Client Access server the command will test. Because credentials are required as part of the parameters when you use the URL parameter, you can use any account to run the Test-OwaConnectivity cmdlet when you use the URL parameter.
+To test a single URL, run the Test-OwaConnectivity cmdlet with the URL parameter and credentials for an existing Exchange mailbox. If the URL is behind a load balancer, you can't predict which Client Access server the command tests. Because credentials are required as part of the parameters when you use the URL parameter, you can use any account to run the Test-OwaConnectivity cmdlet when you use the URL parameter.
 
 If the command encounters a virtual directory that doesn't require Secure Sockets Layer (SSL), the command skips that directory unless the AllowUnsecureAccess parameter is used. If the AllowUnsecureAccess parameter is used, communications between servers are sent in clear text for purposes of the test.
 
 The Test-OwaConnectivity cmdlet can be run as a one-time interactive task or as a scheduled task under Microsoft System Center Operations Manager 2007 control. To run the Test-OwaConnectivity cmdlet as a System Center Operations Manager 2007 task, the Client Access test mailbox must be available on the Mailbox servers that the cmdlet tests against.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-PopConnectivity.md b/exchange/exchange-ps/ExchangePowerShell/Test-PopConnectivity.md
index 76991b73a4..7e5870d3cf 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-PopConnectivity.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-PopConnectivity.md
@@ -17,7 +17,7 @@ This cmdlet is available only in on-premises Exchange.
 
 Use the Test-PopConnectivity cmdlet to verify that the Microsoft Exchange POP3 service is working as expected.
 
-**Note**: This cmdlet works best in Exchange 2010. In later versions of Exchange, the functionality of this cmdlet has been replaced by Managed Availability. For the best results, use the Invoke-MonitoringProbe cmdlet and specify the relevant active monitor probe instead of using this cmdlet.
+**Note**: This cmdlet works best in Exchange 2010. In later versions of Exchange, the functionality of this cmdlet is replaced by Managed Availability. For the best results, use the Invoke-MonitoringProbe cmdlet and specify the relevant active monitor probe instead of using this cmdlet.
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
@@ -59,7 +59,7 @@ The test results are displayed on-screen. The cmdlet returns the following infor
 
 You can write the results to a file by piping the output to ConvertTo-Html and Set-Content. For example: `Test-PopConnectivity -ClientAccessServer MBX01 | ConvertTo-Html | Set-Content -Path "C:\My Documents\POP Test.html"`.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-PowerShellConnectivity.md b/exchange/exchange-ps/ExchangePowerShell/Test-PowerShellConnectivity.md
index 3a86af6c76..45ec1f55f2 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-PowerShellConnectivity.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-PowerShellConnectivity.md
@@ -17,7 +17,7 @@ This cmdlet is available only in on-premises Exchange.
 
 Use the Test-PowerShellConnectivity cmdlet to test client connectivity to Exchange remote PowerShell virtual directories.
 
-**Note**: This cmdlet works best in Exchange 2010. In later versions of Exchange, the functionality of this cmdlet has been replaced by Managed Availability. For the best results, use the Invoke-MonitoringProbe cmdlet and specify the relevant active monitor probe instead of using this cmdlet.
+**Note**: This cmdlet works best in Exchange 2010. In later versions of Exchange, the functionality of this cmdlet is replaced by Managed Availability. For the best results, use the Invoke-MonitoringProbe cmdlet and specify the relevant active monitor probe instead of using this cmdlet.
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
@@ -71,7 +71,7 @@ The test results are displayed on-screen. The cmdlet returns the following infor
 
 You can write the results to a file by piping the output to ConvertTo-Html and Set-Content. For example: `Test-PowerShellConnectivity -ClientAccessServer MBX01 | ConvertTo-Html | Set-Content -Path "C:\My Documents\PowerShell Test.html"`.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-ReplicationHealth.md b/exchange/exchange-ps/ExchangePowerShell/Test-ReplicationHealth.md
index 16dd2f9e99..8e5467e89d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-ReplicationHealth.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-ReplicationHealth.md
@@ -37,7 +37,7 @@ Test-ReplicationHealth [[-Identity] <ServerIdParameter>]
 ## DESCRIPTION
 The Test-ReplicationHealth cmdlet is designed for the proactive monitoring of continuous replication and the continuous replication pipeline, the availability of Active Manager and the health and status of the underlying cluster service, quorum and network components. The Test-ReplicationHealth cmdlet can be run locally or remotely against any Mailbox server in a DAG.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -163,7 +163,7 @@ Accept wildcard characters: False
 The MonitoringContext parameter specifies whether to include the associated monitoring events and performance counters in the results. Valid values are:
 
 - $true: Monitoring events and performance counters are included in the command results. Typically, you include the monitoring events and performance counters in the results when the output is passed to Microsoft System Center Operations Manager (SCOM).
-- $false: Monitoring events and performance counters aren't included in the command results. This is the default value.
+- $false: Monitoring events and performance counters aren't included in the command results. This value is the default.
 
 ```yaml
 Type: Boolean
diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-SenderId.md b/exchange/exchange-ps/ExchangePowerShell/Test-SenderId.md
index 90f55ad910..d60fe06337 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-SenderId.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-SenderId.md
@@ -34,7 +34,7 @@ Test-SenderId -IPAddress <IPAddress> -PurportedResponsibleDomain <SmtpDomain>
 ## DESCRIPTION
 The Test-SenderId cmdlet provides the results of a Sender ID check for the IP address and the corresponding domain name that you specify.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-ServiceHealth.md b/exchange/exchange-ps/ExchangePowerShell/Test-ServiceHealth.md
index 6ea5b4bb58..833a0a50b2 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-ServiceHealth.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-ServiceHealth.md
@@ -32,9 +32,9 @@ Test-ServiceHealth [[-Server] <ServerIdParameter>]
 ```
 
 ## DESCRIPTION
-This cmdlet isn't supported on Exchange 2013 Client Access servers (the cmdlet will return unexpected output).
+This cmdlet isn't supported on Exchange 2013 Client Access servers (the cmdlet returns unexpected output).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -138,7 +138,7 @@ Accept wildcard characters: False
 The MonitoringContext parameter specifies whether to include the associated monitoring events and performance counters in the results. Valid values are:
 
 - $true: Monitoring events and performance counters are included in the command results. Typically, you include the monitoring events and performance counters in the results when the output is passed to Microsoft System Center Operations Manager (SCOM).
-- $false: Monitoring events and performance counters aren't included in the command results. This is the default value.
+- $false: Monitoring events and performance counters aren't included in the command results. This value is the default.
 
 ```yaml
 Type: Boolean
diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-ServicePrincipalAuthorization.md b/exchange/exchange-ps/ExchangePowerShell/Test-ServicePrincipalAuthorization.md
index 957f3de564..b40a761d80 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-ServicePrincipalAuthorization.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-ServicePrincipalAuthorization.md
@@ -30,7 +30,7 @@ Test-ServicePrincipalAuthorization [-Identity] <ServicePrincipalIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-SiteMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Test-SiteMailbox.md
index 2361c7f9ca..8620f8cc97 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-SiteMailbox.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-SiteMailbox.md
@@ -37,7 +37,7 @@ Test-SiteMailbox [[-Identity] <RecipientIdParameter>]
 ## DESCRIPTION
 If you don't specify the RequestorIdentity parameter, the command uses the identification of the user running this command.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-SmtpConnectivity.md b/exchange/exchange-ps/ExchangePowerShell/Test-SmtpConnectivity.md
index 502a332306..5ad4bb647f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-SmtpConnectivity.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-SmtpConnectivity.md
@@ -42,7 +42,7 @@ When you run the Test-SmtpConnectivity cmdlet against a Mailbox server, the cmdl
 
 You can write the results to a file by piping the output to ConvertTo-Html or ConvertTo-Csv and adding ` > <filename>` to the command. For example: `Test-SmtpConnectivity Mailbox01 | ConvertTo-Csv > "C:\My Documents\SMTP Test.csv"`.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -137,7 +137,7 @@ Accept wildcard characters: False
 The MonitoringContext parameter specifies whether to include the associated monitoring events and performance counters in the results. Valid values are:
 
 - $true: Monitoring events and performance counters are included in the command results. Typically, you include the monitoring events and performance counters in the results when the output is passed to Microsoft System Center Operations Manager (SCOM).
-- $false: Monitoring events and performance counters aren't included in the command results. This is the default value.
+- $false: Monitoring events and performance counters aren't included in the command results. This value is the default.
 
 ```yaml
 Type: Boolean
diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-SystemHealth.md b/exchange/exchange-ps/ExchangePowerShell/Test-SystemHealth.md
index 5d3c22eb66..b12b185cce 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-SystemHealth.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-SystemHealth.md
@@ -48,7 +48,7 @@ Test-SystemHealth [-ADCredentials <PSCredential>]
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-TextExtraction.md b/exchange/exchange-ps/ExchangePowerShell/Test-TextExtraction.md
index f703ca42a6..e22bd0b9d2 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-TextExtraction.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-TextExtraction.md
@@ -13,7 +13,7 @@ title: Test-TextExtraction
 # Test-TextExtraction
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Test-TextExtraction cmdlet to return the text from unencrypted email message files.
 
@@ -34,7 +34,7 @@ This cmdlet doesn't work on encrypted email message files.
 
 The Microsoft classification engine uses the results to classify content and determine the sensitive information types in the message file.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-UMConnectivity.md b/exchange/exchange-ps/ExchangePowerShell/Test-UMConnectivity.md
index 5ca409cf40..d85acfead8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-UMConnectivity.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-UMConnectivity.md
@@ -17,7 +17,7 @@ This cmdlet is available only in on-premises Exchange.
 
 Use the Test-UMConnectivity cmdlet to test the operation of Unified Messaging (UM) servers.
 
-**Note**: This cmdlet works best in Exchange 2010. In later versions of Exchange, the functionality of this cmdlet has been replaced by Managed Availability. For the best results, use the Invoke-MonitoringProbe cmdlet and specify the relevant active monitor probe instead of using this cmdlet.
+**Note**: This cmdlet works best in Exchange 2010. In later versions of Exchange, the functionality of this cmdlet is replaced by Managed Availability. For the best results, use the Invoke-MonitoringProbe cmdlet and specify the relevant active monitor probe instead of using this cmdlet.
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
@@ -109,9 +109,9 @@ The Test-UMConnectivity cmdlet can be used to test the operation of a Mailbox se
 
 When you run this cmdlet in an on-premises Unified Messaging deployment, you need to create a UM IP gateway object for the computer or server that the cmdlet is testing. When you create the UM IP gateway object, you must configure it with a fully qualified domain name (FQDN) and that FQDN must match the name of the computer running this cmdlet.
 
-After this task is complete, the cmdlet will have tested the operation of the Mailbox server and related telephony components.
+After this task is complete, the cmdlet tested the operation of the Mailbox server and related telephony components.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -490,7 +490,7 @@ Accept wildcard characters: False
 The MonitoringContext parameter specifies whether to include the associated monitoring events and performance counters in the results. Valid values are:
 
 - $true: Monitoring events and performance counters are included in the command results. Typically, you include the monitoring events and performance counters in the results when the output is passed to Microsoft System Center Operations Manager (SCOM).
-- $false: Monitoring events and performance counters aren't included in the command results. This is the default value.
+- $false: Monitoring events and performance counters aren't included in the command results. This value is the default.
 
 ```yaml
 Type: Boolean
diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-WebServicesConnectivity.md b/exchange/exchange-ps/ExchangePowerShell/Test-WebServicesConnectivity.md
index db4d21c3d1..c156db20d0 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-WebServicesConnectivity.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-WebServicesConnectivity.md
@@ -17,7 +17,7 @@ This cmdlet is available only in on-premises Exchange.
 
 Use the Test-WebServicesConnectivity cmdlet to test client connectivity to Exchange Web Services virtual directories.
 
-**Note**: This cmdlet works best in Exchange 2010. In later versions of Exchange, the functionality of this cmdlet has been replaced by Managed Availability. For the best results, use the Invoke-MonitoringProbe cmdlet and specify the relevant active monitor probe instead of using this cmdlet.
+**Note**: This cmdlet works best in Exchange 2010. In later versions of Exchange, the functionality of this cmdlet is replaced by Managed Availability. For the best results, use the Invoke-MonitoringProbe cmdlet and specify the relevant active monitor probe instead of using this cmdlet.
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
@@ -90,7 +90,7 @@ The test results are displayed on-screen. The cmdlet returns the following infor
 
 You can write the results to a file by piping the output to ConvertTo-Html and Set-Content. For example: `Test-WebServicesConnectivity -ClientAccessServer MBX01 | ConvertTo-Html | Set-Content -Path "C:\My Documents\EWS Test.html"`.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Undo-SoftDeletedMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Undo-SoftDeletedMailbox.md
index 9adf6497ad..e78381ee09 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Undo-SoftDeletedMailbox.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Undo-SoftDeletedMailbox.md
@@ -15,7 +15,7 @@ title: Undo-SoftDeletedMailbox
 ## SYNOPSIS
 This cmdlet is available only in the cloud-based service.
 
-Use the Undo-SoftDeletedMailbox cmdlet to recover a mailbox that has been deleted. Mailboxes can be recovered within 30 days of being deleted.
+Use the Undo-SoftDeletedMailbox cmdlet to recover a mailbox that is deleted. Mailboxes can be recovered within 30 days of being deleted.
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
@@ -45,11 +45,11 @@ Undo-SoftDeletedMailbox [-SoftDeletedObject] <MailboxIdParameter>
 ```
 
 ## DESCRIPTION
-Use the Undo-SoftDeletedMailbox cmdlet to recover a mailbox that has been deleted. When a mailbox is deleted with the Remove-Mailbox or Disable-Mailbox cmdlet, it's not actually deleted. It's hidden in Exchange and moved in Active Directory to the organizational unit (OU) Soft Deleted Objects. This enables administrators to recover deleted mailboxes for up to 30 days after deletion.
+Use the Undo-SoftDeletedMailbox cmdlet to recover a mailbox that is deleted. When a mailbox is deleted with the Remove-Mailbox or Disable-Mailbox cmdlet, it's not actually deleted. It's hidden in Exchange and moved in Active Directory to the organizational unit (OU) Soft Deleted Objects. This enables administrators to recover deleted mailboxes for up to 30 days after deletion.
 
 If the Microsoft account (formerly known as a Windows Live ID) wasn't deleted when the mailbox was deleted, you have to specify a new Microsoft account and password when you use the Undo-SoftDeletedMailbox cmdlet to recover a mailbox.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -65,7 +65,7 @@ This example recovers the deleted mailbox for the user Florence Flipo. When this
 Undo-SoftDeletedMailbox bjohnson@contoso.edu -WindowsLiveID brianj@contoso.edu -Password (Get-Credential).password
 ```
 
-This example recovers the deleted mailbox for the user Brian Johnson. When this mailbox was deleted, the associated Microsoft account wasn't deleted. Note that a new Microsoft account and password have to be created to recover this mailbox. In the scenario, the old Microsoft account is retained as a proxy address for the mailbox.
+This example recovers the deleted mailbox for the user Brian Johnson. When this mailbox was deleted, the associated Microsoft account wasn't deleted. A new Microsoft account and password have to be created to recover this mailbox. In the scenario, the old Microsoft account is retained as a proxy address for the mailbox.
 
 ## PARAMETERS
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Undo-SoftDeletedUnifiedGroup.md b/exchange/exchange-ps/ExchangePowerShell/Undo-SoftDeletedUnifiedGroup.md
index b9843c0afd..f8fa5fc6a6 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Undo-SoftDeletedUnifiedGroup.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Undo-SoftDeletedUnifiedGroup.md
@@ -35,7 +35,7 @@ Soft-deleted Microsoft 365 Groups are groups that have been deleted, but can be
 
 To display all soft-deleted Microsoft 365 Groups in your organization, use the [Get-MgDirectoryDeletedItemAsGroup](https://learn.microsoft.com/powershell/module/microsoft.graph.identity.directorymanagement/get-mgdirectorydeleteditemasgroup) cmdlet in Microsoft Graph PowerShell. To permanently remove (purge) a soft-deleted Microsoft 365 Group, use the [Remove-MgDirectoryDeletedItem](https://learn.microsoft.com/powershell/module/microsoft.graph.identity.directorymanagement/remove-mgdirectorydeleteditem) cmdlet in Microsoft Graph PowerShell.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Uninstall-TransportAgent.md b/exchange/exchange-ps/ExchangePowerShell/Uninstall-TransportAgent.md
index 016b827ab3..c4dbca1080 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Uninstall-TransportAgent.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Uninstall-TransportAgent.md
@@ -37,7 +37,7 @@ You can install and uninstall transport agents in the following locations:
 - The Front End Transport service on Mailbox servers.
 - Edge Transport servers.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Update-AddressList.md b/exchange/exchange-ps/ExchangePowerShell/Update-AddressList.md
index f932437a97..b9d2e639b6 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Update-AddressList.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Update-AddressList.md
@@ -30,7 +30,7 @@ Update-AddressList [-Identity] <AddressListIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Update-ComplianceCaseMember.md b/exchange/exchange-ps/ExchangePowerShell/Update-ComplianceCaseMember.md
index 57863d7f9f..95df48bd89 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Update-ComplianceCaseMember.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Update-ComplianceCaseMember.md
@@ -74,7 +74,7 @@ Accept wildcard characters: False
 
 > Applicable: Security & Compliance
 
-The Members parameter specifies the users that will replace the current eDiscovery case members. You can use any value that uniquely identifies the user. For example:
+The Members parameter specifies the users that replace the current eDiscovery case members. You can use any value that uniquely identifies the user. For example:
 
 - Name
 - Distinguished name (DN)
diff --git a/exchange/exchange-ps/ExchangePowerShell/Update-DatabaseSchema.md b/exchange/exchange-ps/ExchangePowerShell/Update-DatabaseSchema.md
index a23646c719..28b74be06b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Update-DatabaseSchema.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Update-DatabaseSchema.md
@@ -15,7 +15,7 @@ title: Update-DatabaseSchema
 ## SYNOPSIS
 This cmdlet is available only in on-premises Exchange.
 
-Use the Update-DatabaseSchema cmdlet to upgrade the database schema for one or more databases after an Exchange software update that includes database schema updates has been installed on Mailbox servers in a database availability group (DAG). Some software updates for Exchange may include database schema updates. After such an update has been installed on all members of a DAG, the administrator must run the Update-DatabaseSchema cmdlet for each database in the DAG and dismount/mount or failover the database to trigger the database schema update. The in-place database schema upgrade engine ensures that no schema updates occur until all members of the DAG have compatible versions of the software.
+Use the Update-DatabaseSchema cmdlet to upgrade the database schema for one or more databases after an Exchange software update that includes database schema updates is installed on Mailbox servers in a database availability group (DAG). Some software updates for Exchange might include database schema updates. After such an update is installed on all members of a DAG, the administrator must run the Update-DatabaseSchema cmdlet for each database in the DAG and dismount/mount or failover the database to trigger the database schema update. The in-place database schema upgrade engine ensures that no schema updates occur until all members of the DAG have compatible versions of the software.
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
@@ -29,7 +29,7 @@ Update-DatabaseSchema [-Identity] <DatabaseIdParameter> -MajorVersion <UInt16> -
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Update-DistributionGroupMember.md b/exchange/exchange-ps/ExchangePowerShell/Update-DistributionGroupMember.md
index 797e2d1195..77501dbf64 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Update-DistributionGroupMember.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Update-DistributionGroupMember.md
@@ -13,7 +13,7 @@ title: Update-DistributionGroupMember
 # Update-DistributionGroupMember
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Update-DistributionGroupMember cmdlet to replace all members of distribution groups and mail-enabled security groups. To add or remove existing group members, use the Add-DistributionGroupMember and Remove-DistributionGroupMember cmdlets.
 
@@ -32,7 +32,7 @@ Update-DistributionGroupMember [-Identity] <DistributionGroupIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -138,7 +138,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
 
-The Members parameter specifies the recipients (mail-enabled objects) that will replace the current group members. You can use any value that uniquely identifies the recipient. For example:
+The Members parameter specifies the recipients (mail-enabled objects) that replace the current group members. You can use any value that uniquely identifies the recipient. For example:
 
 - Name
 - Alias
@@ -149,7 +149,7 @@ The Members parameter specifies the recipients (mail-enabled objects) that will
 
 You can enter multiple values separated by commas. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`.
 
-Although it isn't required, it's a good idea to add only security principals (for example, mailboxes and mail users with user accounts or other mail-enabled security groups) to mail-enabled security groups. If you assign permissions to a mail-enabled security group, any members that aren't security principals (for example, mail contacts or distribution groups) won't have the permissions assigned.
+Although it isn't required, it's a good idea to add only security principals (for example, mailboxes and mail users with user accounts or other mail-enabled security groups) to mail-enabled security groups. If you assign permissions to a mail-enabled security group, any members that aren't security principals (for example, mail contacts or distribution groups) don't have the permissions assigned.
 
 The maximum number of entries for this parameter is 10000.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Update-EmailAddressPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Update-EmailAddressPolicy.md
index 57d5e9ca5d..c93914c149 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Update-EmailAddressPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Update-EmailAddressPolicy.md
@@ -32,7 +32,7 @@ Update-EmailAddressPolicy [-Identity] <EmailAddressPolicyIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Update-ExchangeHelp.md b/exchange/exchange-ps/ExchangePowerShell/Update-ExchangeHelp.md
index 4d5145517d..9c99530bbe 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Update-ExchangeHelp.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Update-ExchangeHelp.md
@@ -31,7 +31,7 @@ The Update-ExchangeHelp cmdlet is available in Exchange Server 2013 or later.
 
 You need to run the Update-ExchangeHelp cmdlet on each Exchange server. By default, the cmdlet requires an Internet connection, but you can configure an offline mode.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -50,7 +50,7 @@ This example checks for the latest available version of Help for the Exchange Ma
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
-By default, the Update-ExchangeHelp cmdlet has a throttling period of 24 hours. If you run this cmdlet within 24 hours of the last time you ran it, it won't check for updates. You can use this switch to force the cmdlet to check for updates more frequently and to display status or error messages.
+By default, the Update-ExchangeHelp cmdlet has a throttling period of 24 hours. If you run this cmdlet within 24 hours of the last time you ran it, the cmdlet doesn't check for updates. You can use this switch to force the cmdlet to check for updates more frequently and to display status or error messages.
 
 ```yaml
 Type: SwitchParameter
diff --git a/exchange/exchange-ps/ExchangePowerShell/Update-FileDistributionService.md b/exchange/exchange-ps/ExchangePowerShell/Update-FileDistributionService.md
index 62bd156223..c7ef1e4eaf 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Update-FileDistributionService.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Update-FileDistributionService.md
@@ -35,7 +35,7 @@ The Update-FileDistributionService cmdlet forces the Microsoft Exchange File Dis
 
 If you don't use the Type parameter when running this command, OAB, Unified Messaging, and Group Metrics data are reloaded.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Update-GlobalAddressList.md b/exchange/exchange-ps/ExchangePowerShell/Update-GlobalAddressList.md
index 9122493067..4a98c2846a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Update-GlobalAddressList.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Update-GlobalAddressList.md
@@ -30,7 +30,7 @@ Update-GlobalAddressList [-Identity] <GlobalAddressListIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Update-HybridConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Update-HybridConfiguration.md
index 25c53663ef..32694c56bb 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Update-HybridConfiguration.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Update-HybridConfiguration.md
@@ -13,7 +13,7 @@ title: Update-HybridConfiguration
 # Update-HybridConfiguration
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Update-HybridConfiguration cmdlet to define the credentials that are used to update the hybrid configuration object.
 
@@ -32,7 +32,7 @@ Update-HybridConfiguration -OnPremisesCredentials <PSCredential> -TenantCredenti
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Update-MailboxDatabaseCopy.md b/exchange/exchange-ps/ExchangePowerShell/Update-MailboxDatabaseCopy.md
index 388cc0d20a..67ea153698 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Update-MailboxDatabaseCopy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Update-MailboxDatabaseCopy.md
@@ -80,7 +80,7 @@ The Update-MailboxDatabaseCopy cmdlet can also be used to seed a content index c
 
 You must suspend a database copy before you can update it using the Update-MailboxDatabaseCopy cmdlet. For detailed steps about how to suspend a database copy, see [Suspend or resume a mailbox database copy](https://learn.microsoft.com/Exchange/high-availability/manage-ha/suspend-resume-db-copies).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -352,7 +352,7 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-The Network parameter specifies which DAG network should be used for seeding. Note that content index catalog seeding always occurs over the MAPI network, even if you use this parameter to specify the DAG network.
+The Network parameter specifies which DAG network should be used for seeding. Content index catalog seeding always occurs over the MAPI network, even if you use this parameter to specify the DAG network.
 
 ```yaml
 Type: DatabaseAvailabilityGroupNetworkIdParameter
diff --git a/exchange/exchange-ps/ExchangePowerShell/Update-OfflineAddressBook.md b/exchange/exchange-ps/ExchangePowerShell/Update-OfflineAddressBook.md
index 24c1ffe456..a3de0ee78b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Update-OfflineAddressBook.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Update-OfflineAddressBook.md
@@ -31,7 +31,7 @@ Update-OfflineAddressBook [-Identity] <OfflineAddressBookIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Update-PublicFolder.md b/exchange/exchange-ps/ExchangePowerShell/Update-PublicFolder.md
index 7bf00fe065..3c4332d4c8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Update-PublicFolder.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Update-PublicFolder.md
@@ -30,7 +30,7 @@ Update-PublicFolder [-Identity] <PublicFolderIdParameter> -Server <ServerIdParam
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Update-PublicFolderHierarchy.md b/exchange/exchange-ps/ExchangePowerShell/Update-PublicFolderHierarchy.md
index 2902335a2c..a245e2ba23 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Update-PublicFolderHierarchy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Update-PublicFolderHierarchy.md
@@ -30,7 +30,7 @@ Update-PublicFolderHierarchy -Server <ServerIdParameter>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Update-PublicFolderMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Update-PublicFolderMailbox.md
index 3980dd3f42..0b48213ae6 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Update-PublicFolderMailbox.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Update-PublicFolderMailbox.md
@@ -13,7 +13,7 @@ title: Update-PublicFolderMailbox
 # Update-PublicFolderMailbox
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Update-PublicFolderMailbox cmdlet to update the hierarchy for public folders.
 
@@ -48,7 +48,7 @@ Update-PublicFolderMailbox [-Identity] <MailboxIdParameter> -FolderId <PublicFol
 ## DESCRIPTION
 This cmdlet only needs to be used if you want to manually invoke the hierarchy synchronizer and the mailbox assistant. Both these are invoked at least once every 24 hours for each public folder mailbox in the organization. The hierarchy synchronizer is invoked every 15 minutes if any users are logged on to a secondary mailbox through Outlook or an Exchange Web Services client.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -234,11 +234,11 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
 
-The ReconcileFolders switch specifies whether to look closely for differences in the folder hierarchy between the primary public folder mailbox and the secondary public folder mailbox. Folders that exist in the primary public folder mailbox and not in the secondary will be recreated. You don't need to specify a value with this switch.
+The ReconcileFolders switch specifies whether to look closely for differences in the folder hierarchy between the primary public folder mailbox and the secondary public folder mailbox. Folders that exist in the primary public folder mailbox and not in the secondary are recreated. You don't need to specify a value with this switch.
 
-In on-premises Exchange, folders that exist in the secondary public folder mailbox and not in the primary will be deleted.
+In on-premises Exchange, folders that exist in the secondary public folder mailbox and not in the primary are deleted.
 
-In Exchange Online, folders that exist in the secondary public folder mailbox and not in the primary will be moved to \NON_IPM_SUBTREE\LOST_AND_FOUND. See [this blog post](https://techcommunity.microsoft.com/t5/exchange-team-blog/introducing-public-folder-8220-lost-and-found-8221-functionality/ba-p/604043) for more details about LOST_AND_FOUND functionality.
+In Exchange Online, folders that exist in the secondary public folder mailbox and not in the primary are moved to \NON_IPM_SUBTREE\LOST_AND_FOUND. See [this blog post](https://techcommunity.microsoft.com/t5/exchange-team-blog/introducing-public-folder-8220-lost-and-found-8221-functionality/ba-p/604043) for more details about LOST_AND_FOUND functionality.
 
 In both the scenarios, public folders that were deleted or moved to LOST_AND_FOUND can be restored using Set-PublicFolder command.
 
@@ -250,7 +250,7 @@ This example restores the public folder named "Documents" from LOST_AND_FOUND to
 
 `Set-PublicFolder -Identity \NON_IPM_SUBTREE\DUMPSTER_ROOT\DUMPSTER_EXTEND\RESERVED_1\RESERVED_1\9f32c468-4bc2-42aa-b979-16a057394b2f\Documents -Path \Engineering`
 
-**Note**: You should use the ReconcileFolders switch only for repair or troubleshooting purposes to look for differences in the public folder hierarchy that aren't detected by a regular synchronization. These undetected differences may occur in database failover or disaster recovery scenarios. You must use this switch with the InvokeSynchronizer switch.
+**Note**: You should use the ReconcileFolders switch only for repair or troubleshooting purposes to look for differences in the public folder hierarchy that aren't detected by a regular synchronization. These undetected differences might occur in database failover or disaster recovery scenarios. You must use this switch with the InvokeSynchronizer switch.
 
 ```yaml
 Type: SwitchParameter
@@ -268,11 +268,11 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
 
-The SuppressStatus switch specifies that the output of this cmdlet is suppressed and that the command will run asynchronously in the background from the Exchange Management Shell. You don't need to specify a value with this switch.
+The SuppressStatus switch specifies that the output of this cmdlet is suppressed and that the command runs asynchronously in the background from the Exchange Management Shell. You don't need to specify a value with this switch.
 
 You can only use this switch with the InvokeSynchronizer switch.
 
-If you don't use this switch, the output will display status messages every 3 seconds for up to one minute. Until the minute passes, you can't use the PowerShell Window for other commands.
+If you don't use this switch, the output displays status messages every 3 seconds for up to one minute. Until the minute passes, you can't use the PowerShell Window for other commands.
 
 ```yaml
 Type: SwitchParameter
diff --git a/exchange/exchange-ps/ExchangePowerShell/Update-Recipient.md b/exchange/exchange-ps/ExchangePowerShell/Update-Recipient.md
index 3e39709f1d..df0c783950 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Update-Recipient.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Update-Recipient.md
@@ -13,7 +13,7 @@ title: Update-Recipient
 # Update-Recipient
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Update-Recipient cmdlet to add Exchange attributes to recipient objects.
 
@@ -37,7 +37,7 @@ In on-premises Exchange, before you can run the Update-Recipient cmdlet to conve
 - mailNickname
 - msExchHomeServerName
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Update-RoleGroupMember.md b/exchange/exchange-ps/ExchangePowerShell/Update-RoleGroupMember.md
index 8bb7860a0c..c9a3ecf00f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Update-RoleGroupMember.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Update-RoleGroupMember.md
@@ -13,7 +13,7 @@ title: Update-RoleGroupMember
 # Update-RoleGroupMember
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Update-RoleGroupMember cmdlet to modify the members of a management role group.
 
@@ -36,13 +36,13 @@ The Update-RoleGroupMember cmdlet enables you to replace the entire membership l
 
 The Add-RoleGroupMember and Remove-RoleGroupMember cmdlets can be used to add or remove role group members. You can combine these cmdlets with other cmdlets, such as Get-Mailbox, to add or remove multiple members without overwriting the entire membership list at once.
 
-If the ManagedBy property has been populated with role group managers, the user updating role group membership must be a role group manager. Alternately, if the user is a member of the Organization Management role group or is directly or indirectly assigned the Role Management role, the BypassSecurityGroupManagerCheck switch can be used to override the security group management check.
+If the ManagedBy property is populated with role group managers, the user updating role group membership must be a role group manager. Alternately, if the user is a member of the Organization Management role group or is directly or indirectly assigned the Role Management role, the BypassSecurityGroupManagerCheck switch can be used to override the security group management check.
 
 If the role group is a linked role group, you can't use the Update-RoleGroupMember cmdlet to modify members on the role group. Instead, you need to modify members on the foreign universal security group (USG) that's linked to the linked role group. To find the foreign USG that's linked to a role group, use the Get-RoleGroup cmdlet.
 
 For more information about role groups, see [Understanding management role groups](https://learn.microsoft.com/exchange/understanding-management-role-groups-exchange-2013-help).
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Update-SafeList.md b/exchange/exchange-ps/ExchangePowerShell/Update-SafeList.md
index df0c3abf32..9317fb9dd9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Update-SafeList.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Update-SafeList.md
@@ -35,9 +35,9 @@ Update-SafeList [-Identity] <MailboxIdParameter>
 ## DESCRIPTION
 The Update-SafeList cmdlet reads the safelist aggregation data stored on a Microsoft Outlook user mailbox and then hashes and writes the data to the corresponding user object in Active Directory. The command compares the binary attribute created to any value stored on the attribute. If the two values are identical, the command doesn't update the user attribute value with the safelist aggregation data. Safelist aggregation data contains the Outlook user's Safe Senders List and Safe Recipients List.
 
-Be mindful of the network and replication traffic that may be generated when you run the Update-SafeList cmdlet. Running the command on multiple mailboxes where safelists are heavily used may generate a significant amount of traffic. We recommend that if you run the command on multiple mailboxes, you should run the command during off-peak, non-business hours.
+Be mindful of the network and replication traffic that might be generated when you run the Update-SafeList cmdlet. Running the command on multiple mailboxes where safelists are heavily used might generate a significant amount of traffic. We recommend that if you run the command on multiple mailboxes, you should run the command during off-peak, non-business hours.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -155,7 +155,7 @@ The IncludeDomains switch specifies whether to include the sender domains specif
 
 By default, domains specified by the senders aren't included.
 
-In most cases, we don't recommend that you include domains because users may include the domains of large Internet service providers (ISPs), which could unintentionally provide addresses that may be used or spoofed by spammers.
+In most cases, we don't recommend that you include domains because users might include the domains of large Internet service providers (ISPs), which could unintentionally provide addresses that might be used or spoofed by spammers.
 
 ```yaml
 Type: SwitchParameter
diff --git a/exchange/exchange-ps/ExchangePowerShell/Update-SiteMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Update-SiteMailbox.md
index 8c732c49eb..36d54dd832 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Update-SiteMailbox.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Update-SiteMailbox.md
@@ -15,7 +15,7 @@ title: Update-SiteMailbox
 ## SYNOPSIS
 This cmdlet is available only in on-premises Exchange.
 
-Use the Update-SiteMailbox cmdlet to trigger a Microsoft SharePoint synchronization. This command synchronizes document content membership and permissions into Microsoft Exchange. You may need to perform this action when troubleshooting document or membership synchronization issues.
+Use the Update-SiteMailbox cmdlet to trigger a Microsoft SharePoint synchronization. This command synchronizes document content membership and permissions into Microsoft Exchange. You might need to perform this action when troubleshooting document or membership synchronization issues.
 
 Site mailboxes were deprecated in Exchange Online and SharePoint Online in 2017. For more information, see [Deprecation of Site Mailboxes](https://techcommunity.microsoft.com/t5/microsoft-sharepoint-blog/deprecation-of-site-mailboxes/ba-p/93028).
 
@@ -38,7 +38,7 @@ Update-SiteMailbox [-Identity] <RecipientIdParameter>
 ## DESCRIPTION
 If you are running this command against a site mailbox in which you aren't the owner, you need to use the BypassOwnerCheck parameter to run this cmdlet.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -128,7 +128,9 @@ Accept wildcard characters: False
 
 > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 
-The FullSync switch specifies full sync is expensive and will have a performance impact on the Exchange system. You don't need to specify a value with this switch.
+The FullSync switch specifies a full synchronization. You don't need to specify a value with this switch.
+
+Full synchronizations are expensive and affect the performance of the Exchange system.
 
 ```yaml
 Type: SwitchParameter
diff --git a/exchange/exchange-ps/ExchangePowerShell/Update-StoreMailboxState.md b/exchange/exchange-ps/ExchangePowerShell/Update-StoreMailboxState.md
index 4af3a76895..8c97f75874 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Update-StoreMailboxState.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Update-StoreMailboxState.md
@@ -29,9 +29,9 @@ Update-StoreMailboxState -Database <DatabaseIdParameter> -Identity <StoreMailbox
 ```
 
 ## DESCRIPTION
-The Update-StoreMailboxState cmdlet forces the mailbox store state in the Exchange store to be synchronized with Active Directory. In some cases, it's possible that the store state for a mailbox to become out-of-sync with the state of the corresponding Active Directory user account. This can result from Active Directory replication latency. For example, if a mailbox-enabled user account is disabled in Active Directory but isn't marked as disabled in the Exchange mailbox store. In this case, running the Update-StoreMailboxState will synchronize the mailbox store state with the state of the Active Directory user account and mark the mailbox as disabled in the mailbox store. You can use this command to troubleshoot issues that may be a result when the store state for a mailbox is unexpected or if you suspect that the store state is different than the state for the corresponding Active Directory account.
+The Update-StoreMailboxState cmdlet forces the mailbox store state in the Exchange store to be synchronized with Active Directory. In some cases, it's possible that the store state for a mailbox to become out-of-sync with the state of the corresponding Active Directory user account. This can result from Active Directory replication latency. For example, if a mailbox-enabled user account is disabled in Active Directory but isn't marked as disabled in the Exchange mailbox store. In this case, running the Update-StoreMailboxState synchronizes the mailbox store state with the state of the Active Directory user account and mark the mailbox as disabled in the mailbox store. You can use this command to troubleshoot issues that might be a result when the store state for a mailbox is unexpected or if you suspect that the store state is different than the state for the corresponding Active Directory account.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
@@ -155,6 +155,6 @@ To see the return types, which are also known as output types, that this cmdlet
 ## NOTES
 If a mailbox is moved to another database, the mailbox is immediately disabled. There's a 24-hour delay to allow for replication.
 
-In this scenario, Update-StoreMailboxState might not immediately update the DisconnectState and DisconnectReason properties in the output of Get-MailboxStatistics. The values will update approximately 24 hours after the move.
+In this scenario, Update-StoreMailboxState might not immediately update the DisconnectState and DisconnectReason properties in the output of Get-MailboxStatistics. The values update approximately 24 hours after the move.
 
 ## RELATED LINKS
diff --git a/exchange/exchange-ps/ExchangePowerShell/Update-eDiscoveryCaseAdmin.md b/exchange/exchange-ps/ExchangePowerShell/Update-eDiscoveryCaseAdmin.md
index 1ee6f8a622..72ff44c8c3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Update-eDiscoveryCaseAdmin.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Update-eDiscoveryCaseAdmin.md
@@ -50,7 +50,7 @@ This example replaces the existing eDiscovery Administrators with new users.
 
 > Applicable: Security & Compliance
 
-The Users parameter specifies the users that will replace the current eDiscovery Administrators. You can use any value that uniquely identifies the user. For example:
+The Users parameter specifies the users that replaces the current eDiscovery Administrators. You can use any value that uniquely identifies the user. For example:
 
 - Name
 - Distinguished name (DN)
diff --git a/exchange/exchange-ps/ExchangePowerShell/Upgrade-DistributionGroup.md b/exchange/exchange-ps/ExchangePowerShell/Upgrade-DistributionGroup.md
index 1545b8ffa2..3a013933e6 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Upgrade-DistributionGroup.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Upgrade-DistributionGroup.md
@@ -32,7 +32,7 @@ Upgrade-DistributionGroup [-DlIdentities] <MultiValuedProperty>
 ```
 
 ## DESCRIPTION
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Validate-OutboundConnector.md b/exchange/exchange-ps/ExchangePowerShell/Validate-OutboundConnector.md
index a68eaf0cde..1a4f895aa1 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Validate-OutboundConnector.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Validate-OutboundConnector.md
@@ -36,7 +36,7 @@ The Validate-OutboundConnector cmdlet performs two tests on the specified connec
 - SMTP connectivity to each smart host that's defined on the connector.
 - Send test email messages to one or more recipients in the domain that's configured on the connector.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Write-AdminAuditLog.md b/exchange/exchange-ps/ExchangePowerShell/Write-AdminAuditLog.md
index 71ab87ec02..c4eb0f5b84 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Write-AdminAuditLog.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Write-AdminAuditLog.md
@@ -13,7 +13,7 @@ title: Write-AdminAuditLog
 # Write-AdminAuditLog
 
 ## SYNOPSIS
-This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings may be exclusive to one environment or the other.
+This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other.
 
 Use the Write-AdminAuditLog cmdlet to write a comment to the administrator audit log.
 
@@ -34,7 +34,7 @@ When the Write-AdminAuditLog cmdlet runs, the value provided in the Comment para
 
 For the Write-AdminAuditLog cmdlet to write to the audit log, it must be included in the list of cmdlets being logged by administrator audit logging.
 
-You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
+You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 
 ## EXAMPLES
 

From 467ca5dcf274f8bd71ac4928b8804c1780c03882 Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Wed, 6 Aug 2025 11:21:41 -0700
Subject: [PATCH 124/145] Update Get-CsTeamsPersonalAttendantPolicy.md

---
 .../MicrosoftTeams/Get-CsTeamsPersonalAttendantPolicy.md        | 2 --
 1 file changed, 2 deletions(-)

diff --git a/teams/teams-ps/MicrosoftTeams/Get-CsTeamsPersonalAttendantPolicy.md b/teams/teams-ps/MicrosoftTeams/Get-CsTeamsPersonalAttendantPolicy.md
index 508d9e4005..7c200d7327 100644
--- a/teams/teams-ps/MicrosoftTeams/Get-CsTeamsPersonalAttendantPolicy.md
+++ b/teams/teams-ps/MicrosoftTeams/Get-CsTeamsPersonalAttendantPolicy.md
@@ -14,8 +14,6 @@ manager: jomarque
 
 ## SYNOPSIS
 
-Test
-
 **Limited Preview:** Functionality described in this document is currently in limited preview and only authorized organizations have access.
 
 Returns information about the Teams personal attendant policies configured for use in your organization.

From cf745085ba6698508b929a83d5e4edc313c4e28a Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Wed, 6 Aug 2025 11:26:54 -0700
Subject: [PATCH 125/145] Update Get-CsTeamsPersonalAttendantPolicy.md

---
 .../Get-CsTeamsPersonalAttendantPolicy.md           | 13 +++++++------
 1 file changed, 7 insertions(+), 6 deletions(-)

diff --git a/teams/teams-ps/MicrosoftTeams/Get-CsTeamsPersonalAttendantPolicy.md b/teams/teams-ps/MicrosoftTeams/Get-CsTeamsPersonalAttendantPolicy.md
index 7c200d7327..3d4f0402bb 100644
--- a/teams/teams-ps/MicrosoftTeams/Get-CsTeamsPersonalAttendantPolicy.md
+++ b/teams/teams-ps/MicrosoftTeams/Get-CsTeamsPersonalAttendantPolicy.md
@@ -1,13 +1,14 @@
 ---
-external help file: Microsoft.Rtc.Management.dll-Help.xml
-online version: https://learn.microsoft.com/powershell/module/microsoftteams/get-csteamspersonalattendantpolicy
 applicable: Microsoft Teams
-title: Get-CsTeamsPersonalAttendantPolicy
-schema: 2.0.0
 author: juliiva
-ms.author: juliiva
-ms.reviewer:
+external help file: Microsoft.Rtc.Management.dll-Help.xml
+Locale: en-US
 manager: jomarque
+Module Name: MicrosoftTeams
+ms.author: juliiva
+online version: https://learn.microsoft.com/powershell/module/microsoftteams/get-csteamspersonalattendantpolicy
+schema: 2.0.0
+title: Get-CsTeamsPersonalAttendantPolicy
 ---
 
 # Get-CsTeamsPersonalAttendantPolicy

From 3f8d58aa3557555a142b3d783e53364c07b04888 Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Wed, 6 Aug 2025 11:39:40 -0700
Subject: [PATCH 126/145] Update MicrosoftTeams.md

---
 .../teams-ps/MicrosoftTeams/MicrosoftTeams.md | 21 +++++++++++++++++++
 1 file changed, 21 insertions(+)

diff --git a/teams/teams-ps/MicrosoftTeams/MicrosoftTeams.md b/teams/teams-ps/MicrosoftTeams/MicrosoftTeams.md
index 1a498ef064..09b0588616 100644
--- a/teams/teams-ps/MicrosoftTeams/MicrosoftTeams.md
+++ b/teams/teams-ps/MicrosoftTeams/MicrosoftTeams.md
@@ -137,6 +137,12 @@ Returns the identified Mainline attendant question and answer flow.
 ### [Get-CsMeetingMigrationStatus](Get-CsMeetingMigrationStatus.md)
 You use the `Get-CsMeetingMigrationStatus` cmdlet to check the status of meeting migrations.
 
+### [Get-CsPersonalAttendantSettings](Get-CsPersonalAttendantSettings.md)
+Returns the personal attendant settings for a user.
+
+### [Get-CsTeamsPersonalAttendantPolicy](Get-CsTeamsPersonalAttendantPolicy.md)
+Returns information about the Teams personal attendant policies configured for use in your organization.
+
 ### [Get-CsOnlineApplicationInstance](Get-CsOnlineApplicationInstance.md)
 Get application instance for the tenant from Microsoft Entra ID.
 
@@ -674,6 +680,9 @@ Assigns a teams messaging policy at the per-user scope. Teams messaging policies
 ### [Grant-CsTeamsMobilityPolicy](Grant-CsTeamsMobilityPolicy.md)
 The TeamsMobilityPolicy allows Admins to control Teams mobile usage for users.
 
+### [Grant-CsTeamsPersonalAttendantPolicy](Grant-CsTeamsPersonalAttendantPolicy.md)
+Assigns a specific Teams Personal Attendant Policy to a user, a group of users, or sets the Global policy instance.
+
 ### [Grant-CsTeamsRecordingRollOutPolicy](Grant-CsTeamsRecordingRollOutPolicy.md)
 The CsTeamsRecordingRollOutPolicy controls roll out of the change that governs the storage for meeting recordings.
 
@@ -953,6 +962,9 @@ The TeamsMobilityPolicy allows Admins to control Teams mobile usage for users.
 ### [New-CsTeamsNetworkRoamingPolicy](New-CsTeamsNetworkRoamingPolicy.md)
 New-CsTeamsNetworkRoamingPolicy allows IT Admins to create policies for Network Roaming and Bandwidth Control experiences in Microsoft Teams.
 
+### [New-CsTeamsPersonalAttendantPolicy](New-CsTeamsPersonalAttendantPolicy.md)
+Create a new instance of a Teams Personal Attendant Policy.
+
 ### [New-CsTeamsRecordingRollOutPolicy](New-CsTeamsRecordingRollOutPolicy.md)
 The CsTeamsRecordingRollOutPolicy controls roll out of the change that governs the storage for meeting recordings.
 
@@ -1226,6 +1238,9 @@ Remove-CsTeamsNetworkRoamingPolicy allows IT Admins to delete policies for Netwo
 ### [Remove-CsTeamsNotificationAndFeedsPolicy](Remove-CsTeamsNotificationAndFeedsPolicy.md)
 Deletes an existing Teams Notification and Feeds Policy
 
+### [Remove-CsTeamsPersonalAttendantPolicy](Remove-CsTeamsPersonalAttendantPolicy.md)
+Deletes an instance of a Teams Personal Attendant Policy.
+
 ### [Remove-CsTeamsRecordingRollOutPolicy](Remove-CsTeamsRecordingRollOutPolicy.md)
 The CsTeamsRecordingRollOutPolicy controls roll out of the change that governs the storage for meeting recordings.
 
@@ -1367,6 +1382,9 @@ Modifies an existing Mainline Attendant appointment booking flow.
 ### [Set-CsMainlineAttendantQuestionAnswerFlow](Set-CsMainlineAttendantQuestionAnswerFlow.md)
 Modifies an existing Mainline Attendant question and answer (FAQ) flow.
 
+### [Set-CsPersonalAttendantSettings](Set-CsPersonalAttendantSettings.md)
+Modifies the personal attendant settings for a user.
+
 ### [Set-CsOnlineApplicationInstance](Set-CsOnlineApplicationInstance.md)
 Updates an application instance in Microsoft Entra ID.
 
@@ -1556,6 +1574,9 @@ The TeamsMobilityPolicy allows Admins to control Teams mobile usage for users.
 ### [Set-CsTeamsMultiTenantOrganizationConfiguration](Set-CsTeamsMultiTenantOrganizationConfiguration.md)
 This cmdlet configures the Multi-tenant Organization settings for the tenant.
 
+### [Set-CsTeamsPersonalAttendantPolicy](Set-CsTeamsPersonalAttendantPolicy.md)
+Update an existing Teams Personal Attendant Policies.
+
 ### [Set-CsTeamsNetworkRoamingPolicy](Set-CsTeamsNetworkRoamingPolicy.md)
 Set-CsTeamsNetworkRoamingPolicy allows IT Admins to create or update policies for Network Roaming and Bandwidth Control experiences in Microsoft Teams.
 

From 04e8e3eb887c10c27ba53b7d55efa9fb74d30721 Mon Sep 17 00:00:00 2001
From: Colin Longman <Colin.Longman@microsoft.com>
Date: Wed, 6 Aug 2025 13:46:52 -0700
Subject: [PATCH 127/145] Update Get-CsPersonalAttendantSettings.md

---
 .../MicrosoftTeams/Get-CsPersonalAttendantSettings.md         | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/teams/teams-ps/MicrosoftTeams/Get-CsPersonalAttendantSettings.md b/teams/teams-ps/MicrosoftTeams/Get-CsPersonalAttendantSettings.md
index 74e0fd7e61..bd61deb0f6 100644
--- a/teams/teams-ps/MicrosoftTeams/Get-CsPersonalAttendantSettings.md
+++ b/teams/teams-ps/MicrosoftTeams/Get-CsPersonalAttendantSettings.md
@@ -6,9 +6,9 @@ Locale: en-US
 manager: jomarque
 Module Name: MicrosoftTeams
 ms.author: juliiva
-online version: https://learn.microsoft.com/powershell/module/microsoftteams/get-csteamspersonalattendantpolicy
+online version: https://learn.microsoft.com/powershell/module/microsoftteams/get-cspersonalattendantsettings
 schema: 2.0.0
-title: Get-CsTeamsPersonalAttendantPolicy
+title: Get-CsPersonalAttendantSettings
 ---
 
 # Get-CsPersonalAttendantSettings

From 119c5ef8add1d8a3bd2ce0409d69960327c3451b Mon Sep 17 00:00:00 2001
From: Chris Davis <chris.davis@microsoft.com>
Date: Wed, 6 Aug 2025 17:43:51 -0700
Subject: [PATCH 128/145] Add Exchange Server SE

---
 .../ExchangePowerShell/Add-ADPermission.md    | 30 ++++-----
 .../Add-AttachmentFilterEntry.md              | 12 ++--
 .../Add-AvailabilityAddressSpace.md           | 20 +++---
 .../Add-ContentFilterPhrase.md                | 12 ++--
 .../Add-DatabaseAvailabilityGroupServer.md    | 14 ++--
 .../Add-DistributionGroupMember.md            | 14 ++--
 .../ExchangePowerShell/Add-FederatedDomain.md | 12 ++--
 .../Add-GlobalMonitoringOverride.md           | 24 +++----
 .../Add-IPAllowListEntry.md                   | 16 ++---
 .../Add-IPAllowListProvider.md                | 22 +++----
 .../Add-IPBlockListEntry.md                   | 16 ++---
 .../Add-IPBlockListProvider.md                | 24 +++----
 .../Add-MailboxDatabaseCopy.md                | 24 +++----
 .../Add-MailboxFolderPermission.md            | 14 ++--
 .../Add-MailboxPermission.md                  | 26 ++++----
 .../Add-ManagementRoleEntry.md                | 24 +++----
 .../Add-PublicFolderClientPermission.md       | 14 ++--
 .../ExchangePowerShell/Add-ResubmitRequest.md | 28 ++++----
 .../ExchangePowerShell/Add-RoleGroupMember.md | 14 ++--
 .../Add-ServerMonitoringOverride.md           | 20 +++---
 .../Clear-ActiveSyncDevice.md                 | 14 ++--
 .../ExchangePowerShell/Clear-MobileDevice.md  | 16 ++---
 .../Clear-TextMessagingAccount.md             | 12 ++--
 .../Compare-TextMessagingVerificationCode.md  | 12 ++--
 .../Complete-MigrationBatch.md                | 14 ++--
 .../ExchangePowerShell/Connect-Mailbox.md     | 46 ++++++-------
 .../Disable-AddressListPaging.md              |  8 +--
 .../ExchangePowerShell/Disable-App.md         | 12 ++--
 .../Disable-CmdletExtensionAgent.md           | 10 +--
 .../Disable-DistributionGroup.md              | 12 ++--
 .../ExchangePowerShell/Disable-InboxRule.md   | 16 ++---
 .../ExchangePowerShell/Disable-JournalRule.md | 10 +--
 .../ExchangePowerShell/Disable-MailContact.md | 12 ++--
 .../Disable-MailPublicFolder.md               | 10 +--
 .../ExchangePowerShell/Disable-MailUser.md    | 14 ++--
 .../ExchangePowerShell/Disable-Mailbox.md     | 26 ++++----
 .../Disable-MailboxQuarantine.md              | 18 +++---
 .../Disable-MalwareFilterRule.md              | 10 +--
 .../Disable-MetaCacheDatabase.md              |  8 +--
 .../Disable-OutlookProtectionRule.md          | 10 +--
 .../Disable-PushNotificationProxy.md          |  6 +-
 .../Disable-RemoteMailbox.md                  | 16 ++---
 .../Disable-ServiceEmailChannel.md            | 10 +--
 .../ExchangePowerShell/Disable-SweepRule.md   | 12 ++--
 .../Disable-TransportAgent.md                 | 12 ++--
 .../Disable-TransportRule.md                  | 10 +--
 .../ExchangePowerShell/Dismount-Database.md   | 10 +--
 .../Dump-ProvisioningCache.md                 | 18 +++---
 .../Enable-AddressListPaging.md               |  8 +--
 .../Enable-AntispamUpdates.md                 | 10 +--
 .../ExchangePowerShell/Enable-App.md          | 12 ++--
 .../Enable-CmdletExtensionAgent.md            | 10 +--
 .../Enable-DistributionGroup.md               | 16 ++---
 .../Enable-ExchangeCertificate.md             | 22 +++----
 .../ExchangePowerShell/Enable-InboxRule.md    | 16 ++---
 .../ExchangePowerShell/Enable-JournalRule.md  | 10 +--
 .../ExchangePowerShell/Enable-MailContact.md  | 26 ++++----
 .../Enable-MailPublicFolder.md                | 12 ++--
 .../ExchangePowerShell/Enable-MailUser.md     | 26 ++++----
 .../ExchangePowerShell/Enable-Mailbox.md      | 64 +++++++++----------
 .../Enable-MailboxQuarantine.md               | 16 ++---
 .../Enable-MalwareFilterRule.md               | 10 +--
 .../Enable-MetaCacheDatabase.md               |  8 +--
 .../Enable-OutlookProtectionRule.md           | 10 +--
 .../Enable-PushNotificationProxy.md           | 10 +--
 .../Enable-RemoteMailbox.md                   | 30 ++++-----
 .../Enable-ServiceEmailChannel.md             | 10 +--
 .../ExchangePowerShell/Enable-SweepRule.md    | 12 ++--
 .../Enable-TransportAgent.md                  | 12 ++--
 .../Enable-TransportRule.md                   | 12 ++--
 .../Export-ActiveSyncLog.md                   | 20 +++---
 .../Export-AutoDiscoverConfig.md              | 20 +++---
 .../Export-DlpPolicyCollection.md             | 10 +--
 .../Export-ExchangeCertificate.md             | 18 +++---
 .../Export-JournalRuleCollection.md           | 10 +--
 .../Export-MailboxDiagnosticLogs.md           | 22 +++----
 .../ExchangePowerShell/Export-Message.md      |  8 +--
 .../Export-MigrationReport.md                 | 16 ++---
 .../Export-RecipientDataProperty.md           | 14 ++--
 .../Export-TransportRuleCollection.md         | 10 +--
 .../ExchangePowerShell/Get-ADPermission.md    | 10 +--
 .../Get-ADServerSettings.md                   |  2 +-
 .../ExchangePowerShell/Get-ADSite.md          |  6 +-
 .../ExchangePowerShell/Get-AcceptedDomain.md  |  6 +-
 .../Get-ActiveSyncDevice.md                   | 18 +++---
 .../Get-ActiveSyncDeviceAccessRule.md         |  6 +-
 .../Get-ActiveSyncDeviceAutoblockThreshold.md |  6 +-
 .../Get-ActiveSyncDeviceClass.md              | 10 +--
 .../Get-ActiveSyncDeviceStatistics.md         | 14 ++--
 .../Get-ActiveSyncMailboxPolicy.md            |  6 +-
 .../Get-ActiveSyncOrganizationSettings.md     |  6 +-
 .../Get-ActiveSyncVirtualDirectory.md         | 12 ++--
 .../Get-AddressBookPolicy.md                  |  6 +-
 .../ExchangePowerShell/Get-AddressList.md     | 10 +--
 .../Get-AddressRewriteEntry.md                |  6 +-
 .../Get-AdminAuditLogConfig.md                |  4 +-
 .../Get-AdministrativeUnit.md                 | 10 +--
 97 files changed, 706 insertions(+), 706 deletions(-)

diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-ADPermission.md b/exchange/exchange-ps/ExchangePowerShell/Add-ADPermission.md
index 9b7f139ea5..72d50e2a33 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-ADPermission.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Add-ADPermission.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -90,7 +90,7 @@ This example assumes that another security mechanism is used to ensure the Recei
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the identity of the object that's getting permissions added. You can specify either the distinguished name (DN) of the object or the object's name if it's unique. If the DN or name contains spaces, enclose the name in quotation marks (").
 
@@ -108,7 +108,7 @@ Accept wildcard characters: False
 
 ### -Instance
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Instance parameter enables you to pass an entire object to the command to be processed. It's mainly used in scripts where an entire object must be passed to the command.
 
@@ -126,7 +126,7 @@ Accept wildcard characters: False
 
 ### -Owner
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Owner parameter specifies the owner of the Active Directory object. You can specify the following types of users or groups (security principals) for this parameter:
 
@@ -163,7 +163,7 @@ Accept wildcard characters: False
 
 ### -User
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The User parameter specifies who gets the permissions on the Active Directory object. You can specify the following types of users or groups (security principals) for this parameter:
 
@@ -205,7 +205,7 @@ Accept wildcard characters: False
 
 ### -AccessRights
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AccessRights parameter specifies the rights that you want to add for the user on the Active Directory object. Valid values include:
 
@@ -247,7 +247,7 @@ Accept wildcard characters: False
 
 ### -ChildObjectTypes
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ChildObjectTypes parameter specifies what type of object the permission should be applied to.
 
@@ -267,7 +267,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -288,7 +288,7 @@ Accept wildcard characters: False
 
 ### -Deny
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Deny switch specifies that the permissions you're adding are Deny permissions. You don't need to specify a value with this switch.
 
@@ -306,7 +306,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -326,7 +326,7 @@ Accept wildcard characters: False
 
 ### -ExtendedRights
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExtendedRights parameter specifies the extended rights needed to perform the operation.
 
@@ -344,7 +344,7 @@ Accept wildcard characters: False
 
 ### -InheritanceType
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The InheritanceType parameter specifies how permissions are inherited. Valid values are:
 
@@ -368,7 +368,7 @@ Accept wildcard characters: False
 
 ### -InheritedObjectType
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The InheritedObjectType parameter specifies what kind of object inherits this access control entry (ACE).
 
@@ -386,7 +386,7 @@ Accept wildcard characters: False
 
 ### -Properties
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Properties parameter specifies what properties the object contains.
 
@@ -406,7 +406,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-AttachmentFilterEntry.md b/exchange/exchange-ps/ExchangePowerShell/Add-AttachmentFilterEntry.md
index 89c8a158a9..db5f2e767d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-AttachmentFilterEntry.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Add-AttachmentFilterEntry.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
 Locale: en-US
@@ -54,7 +54,7 @@ This example adds an attachment filter entry based on the MIME content type imag
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Name parameter specifies the files that you want to block. Valid values are:
 
@@ -75,7 +75,7 @@ Accept wildcard characters: False
 
 ### -Type
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Type parameter specifies what type of attachment the attachment filter entry blocks. Valid values are:
 
@@ -96,7 +96,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -117,7 +117,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -137,7 +137,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-AvailabilityAddressSpace.md b/exchange/exchange-ps/ExchangePowerShell/Add-AvailabilityAddressSpace.md
index dde9b592f2..838c126e41 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-AvailabilityAddressSpace.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Add-AvailabilityAddressSpace.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
 Locale: en-US
@@ -76,7 +76,7 @@ In Exchange Online, this example sets up the sharing of free/busy information wi
 
 ### -AccessMethod
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The AccessMethod parameter specifies how the free/busy data is accessed. Valid values are:
 
@@ -100,7 +100,7 @@ Accept wildcard characters: False
 
 ### -ForestName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ForestName parameter specifies the SMTP domain name of the target forest that contains the users you're trying to read free/busy information from. If users are distributed among multiple SMTP domains in the target forest, run the Add-AvailabilityAddressSpace command once for each SMTP domain.
 
@@ -118,7 +118,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -139,7 +139,7 @@ Accept wildcard characters: False
 
 ### -Credentials
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Credentials parameter specifies the username and password that's used to access the Availability services in the target forest.
 
@@ -159,7 +159,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -179,7 +179,7 @@ Accept wildcard characters: False
 
 ### -ProxyUrl
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -201,7 +201,7 @@ Accept wildcard characters: False
 
 ### -TargetAutodiscoverEpr
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The TargetAutodiscoverEpr parameter specifies the Autodiscover URL of Exchange Web Services for the external organization that you're trying to read free/busy information from. For example, `https://contoso.com/autodiscover/autodiscover.xml`. Exchange uses Autodiscover to automatically detect the correct server endpoint for external requests.
 
@@ -267,7 +267,7 @@ Accept wildcard characters: False
 
 ### -UseServiceAccount
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -290,7 +290,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-ContentFilterPhrase.md b/exchange/exchange-ps/ExchangePowerShell/Add-ContentFilterPhrase.md
index 7e7cef98c9..09129774b2 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-ContentFilterPhrase.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Add-ContentFilterPhrase.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailControl-Help.xml
 Locale: en-US
@@ -47,7 +47,7 @@ This example adds the phrase Free credit report to the Block phrase list. Any me
 
 ### -Phrase
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Phrase parameter specifies a custom word or phrase for the Content Filter agent. When you pass an argument, you must enclose the Phrase parameter in quotation marks (") if the phrase contains spaces, for example: "This is a bad phrase". Custom phrases must be less than 257 characters in length.
 
@@ -65,7 +65,7 @@ Accept wildcard characters: False
 
 ### -Influence
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Influence parameter specifies whether the phrase being added cause messages that contain the phrase to be allowed or blocked. Valid values are GoodWord and BadWord.
 
@@ -85,7 +85,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -106,7 +106,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -126,7 +126,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-DatabaseAvailabilityGroupServer.md b/exchange/exchange-ps/ExchangePowerShell/Add-DatabaseAvailabilityGroupServer.md
index 8773c97f8a..304718b464 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-DatabaseAvailabilityGroupServer.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Add-DatabaseAvailabilityGroupServer.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -52,7 +52,7 @@ This example adds the Mailbox server MBX1 to the DAG DAG1.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the name of the DAG to which the server is being added.
 
@@ -70,7 +70,7 @@ Accept wildcard characters: False
 
 ### -MailboxServer
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MailboxServer parameter specifies the Mailbox server to add to the DAG. You can use any value that uniquely identifies the server. For example:
 
@@ -93,7 +93,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -114,7 +114,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -132,7 +132,7 @@ Accept wildcard characters: False
 
 ### -SkipDagValidation
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SkipDagValidation switch specifies whether to bypass the validation of the DAG's quorum model and the health check on the DAG's witness when adding members to the DAG. You don't need to specify a value with this switch.
 
@@ -150,7 +150,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-DistributionGroupMember.md b/exchange/exchange-ps/ExchangePowerShell/Add-DistributionGroupMember.md
index 7b4aa8a16e..27ef056242 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-DistributionGroupMember.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Add-DistributionGroupMember.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
 Locale: en-US
@@ -47,7 +47,7 @@ This example adds John Evans to the distribution group named Staff.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the group that you want to modify. You can use any value that uniquely identifies the group. For example:
 
@@ -72,7 +72,7 @@ Accept wildcard characters: False
 
 ### -BypassSecurityGroupManagerCheck
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The BypassSecurityGroupManagerCheck switch specifies whether to allow a user who isn't an owner of the group to modify or delete the group. You don't need to specify a value with this switch.
 
@@ -95,7 +95,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -116,7 +116,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -136,7 +136,7 @@ Accept wildcard characters: False
 
 ### -Member
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Member parameter specifies the recipient that you want to add to the group. A member can be any mail-enabled recipient in your organization. You can use any value that uniquely identifies the recipient. For example:
 
@@ -163,7 +163,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-FederatedDomain.md b/exchange/exchange-ps/ExchangePowerShell/Add-FederatedDomain.md
index a955e3dbaa..43d6ec2fd3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-FederatedDomain.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Add-FederatedDomain.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
 Locale: en-US
@@ -51,7 +51,7 @@ This example adds the domain Contoso.co.uk to the existing federation trust.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -69,7 +69,7 @@ Accept wildcard characters: False
 
 ### -DomainName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainName parameter specifies the secondary domain to be configured.
 
@@ -87,7 +87,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -108,7 +108,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -126,7 +126,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-GlobalMonitoringOverride.md b/exchange/exchange-ps/ExchangePowerShell/Add-GlobalMonitoringOverride.md
index 8a81090517..259ccd73c8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-GlobalMonitoringOverride.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Add-GlobalMonitoringOverride.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -66,7 +66,7 @@ This example adds a global monitoring override that disables the StorageLogicalD
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the identity of the probe, monitor, or responder. This parameter uses the syntax `HealthSetName\MonitoringItemName[\TargetResource]`. The values are case sensitive. For example, use `AD\ActiveDirectoryConnectivityServerReboot`, not `ad\activedirectoryconnectivityserverreboot`.
 
@@ -84,7 +84,7 @@ Accept wildcard characters: False
 
 ### -ApplyVersion
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ApplyVersion parameter specifies the version of Exchange that gets the override. If an Exchange server is older or newer than the version you specify, the override isn't applied to the server. Typically, you increase the Exchange version by applying Cumulative Updates or Service Packs.
 
@@ -106,7 +106,7 @@ Accept wildcard characters: False
 
 ### -ItemType
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ItemType parameter specifies the item type for the property that you want to override. Valid values are:
 
@@ -128,7 +128,7 @@ Accept wildcard characters: False
 
 ### -PropertyName
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PropertyName parameter specifies the property that you want to override.
 
@@ -146,7 +146,7 @@ Accept wildcard characters: False
 
 ### -PropertyValue
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PropertyValue parameter specifies the new value for the property that you want to override.
 
@@ -164,7 +164,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -185,7 +185,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -205,7 +205,7 @@ Accept wildcard characters: False
 
 ### -Duration
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Duration parameter specifies the length of time that the override is active.
 
@@ -229,7 +229,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
@@ -247,7 +247,7 @@ Accept wildcard characters: False
 
 ### -BuildRange
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -265,7 +265,7 @@ Accept wildcard characters: False
 
 ### -Roles
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-IPAllowListEntry.md b/exchange/exchange-ps/ExchangePowerShell/Add-IPAllowListEntry.md
index a084014efb..15d016541d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-IPAllowListEntry.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Add-IPAllowListEntry.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailControl-Help.xml
 Locale: en-US
@@ -67,7 +67,7 @@ This example adds the IP address range 192.168.0.1/24 to the list of allowed IP
 
 ### -IPAddress
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IPAddress parameter specifies a single IP address to add to the IP Allow list, for example, 192.168.0.1.
 
@@ -85,7 +85,7 @@ Accept wildcard characters: False
 
 ### -IPRange
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IPRange parameter specifies a range of IP addresses to add to the IP Allow list. Valid values are:
 
@@ -106,7 +106,7 @@ Accept wildcard characters: False
 
 ### -Comment
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Comment parameter specifies an optional comment. If you specify a value that contains spaces, enclose the value in quotation marks ("), for example: "This is an admin note".
 
@@ -124,7 +124,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -145,7 +145,7 @@ Accept wildcard characters: False
 
 ### -ExpirationTime
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExpirationTime parameter specifies a day and time when the IP Allow list entry expires. If you specify a time only and you don't specify a date, the current day is assumed.
 
@@ -165,7 +165,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
 
@@ -192,7 +192,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-IPAllowListProvider.md b/exchange/exchange-ps/ExchangePowerShell/Add-IPAllowListProvider.md
index d9f0360b2b..1082ee93e4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-IPAllowListProvider.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Add-IPAllowListProvider.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailControl-Help.xml
 Locale: en-US
@@ -57,7 +57,7 @@ This example adds an IP Allow list provider and configures a bitmask return valu
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Name parameter specifies a descriptive name for the IP Allow list provider.
 
@@ -75,7 +75,7 @@ Accept wildcard characters: False
 
 ### -LookupDomain
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The LookupDomain parameter specifies the host name that's required to use the allow list provider. Connection filtering sends the IP address of the connecting SMTP server to the host name value that you specify. An example value is allowlist.spamservice.com. The actual value you need to use is provided by the allow list provider.
 
@@ -93,7 +93,7 @@ Accept wildcard characters: False
 
 ### -AnyMatch
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AnyMatch parameter specifies whether any response by the allow list provider is treated as a match. Valid input for this parameter is $true or $false. The default value is $false. When this parameter is set to $true, and connection filtering sends the IP address of the connecting SMTP server to the allow list provider, any response code returned by the allow list provider causes connection filtering to allow messages from that source.
 
@@ -111,7 +111,7 @@ Accept wildcard characters: False
 
 ### -BitmaskMatch
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The BitmaskMatch parameter specifies the bit mask status code that's returned by the allow list provider. Use this parameter if the allow list provider returns bitmask responses. Valid input for this parameter is a single IP address in the format 127.0.0.1.
 
@@ -129,7 +129,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -150,7 +150,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -170,7 +170,7 @@ Accept wildcard characters: False
 
 ### -Enabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Enabled parameter specifies whether the connection filtering uses this IP Allow List provider. Valid input for this parameter is $true or $false. The default value is $true. By default, connection filtering uses new IP Allow List providers that you create.
 
@@ -188,7 +188,7 @@ Accept wildcard characters: False
 
 ### -IPAddressesMatch
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IPAddressesMatch parameter specifies the IP address status codes that are returned by the allow list provider. Use this parameter if the allow list provider returns IP address or A record responses. Valid input for this parameter one or more IP addresses in the format 127.0.0.1. You can enter multiple IP addresses separated by commas.
 
@@ -206,7 +206,7 @@ Accept wildcard characters: False
 
 ### -Priority
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Priority parameter specifies the order that the Connection Filtering agent queries the IP Allow list providers that you have configured. A lower priority integer value indicates a higher priority. By default, every time that you add a new IP Allow list provider, the entry is assigned a priority of N+1, where N is the number of IP Allow list providers that you have configured.
 
@@ -226,7 +226,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-IPBlockListEntry.md b/exchange/exchange-ps/ExchangePowerShell/Add-IPBlockListEntry.md
index 5507b123be..8fb02445ce 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-IPBlockListEntry.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Add-IPBlockListEntry.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailControl-Help.xml
 Locale: en-US
@@ -66,7 +66,7 @@ This example adds the IP address range 192.168.0.1/24 to the list of blocked IP
 
 ### -IPAddress
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IPAddress parameter specifies a single IP address to add to the IP Block list, for example, 192.168.0.1.
 
@@ -84,7 +84,7 @@ Accept wildcard characters: False
 
 ### -IPRange
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IPRange parameter specifies a range of IP addresses to add to the IP Block list. Valid values are:
 
@@ -105,7 +105,7 @@ Accept wildcard characters: False
 
 ### -Comment
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Comment parameter specifies an optional comment. If you specify a value that contains spaces, enclose the value in quotation marks ("), for example: "This is an admin note".
 
@@ -123,7 +123,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -144,7 +144,7 @@ Accept wildcard characters: False
 
 ### -ExpirationTime
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExpirationTime parameter specifies a day and time when the IP Block list entry expires. If you specify a time only and you don't specify a date, the current day is assumed.
 
@@ -164,7 +164,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
 
@@ -191,7 +191,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-IPBlockListProvider.md b/exchange/exchange-ps/ExchangePowerShell/Add-IPBlockListProvider.md
index e87c1f2b8d..a7505efecc 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-IPBlockListProvider.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Add-IPBlockListProvider.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailControl-Help.xml
 Locale: en-US
@@ -58,7 +58,7 @@ This example adds an IP Block list provider and configures a bitmask return valu
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Name parameter specifies a descriptive name for the IP Block list provider.
 
@@ -76,7 +76,7 @@ Accept wildcard characters: False
 
 ### -LookupDomain
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The LookupDomain parameter specifies the host name that's required to use the block list provider. Connection filtering sends the IP address of the connecting SMTP server to the host name value that you specify. An example value is blocklist.spamservice.com. The actual value you need to use is provided by the block list provider.
 
@@ -94,7 +94,7 @@ Accept wildcard characters: False
 
 ### -AnyMatch
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AnyMatch parameter specifies whether any response by the block list provider is treated as a match. Valid input for this parameter is $true or $false. The default value is $false. When this parameter is set to $true, and connection filtering sends the IP address of the connecting SMTP server to the block list provider, any response code returned by the block list provider causes connection filtering to block messages from that source.
 
@@ -112,7 +112,7 @@ Accept wildcard characters: False
 
 ### -BitmaskMatch
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The BitmaskMatch parameter specifies the bit mask status code that's returned by the block list provider. Use this parameter if the block list provider returns bitmask responses. Valid input for this parameter is a single IP address in the format 127.0.0.1.
 
@@ -130,7 +130,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -151,7 +151,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -171,7 +171,7 @@ Accept wildcard characters: False
 
 ### -Enabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Enabled parameter specifies whether the connection filtering uses this IP Block list provider. Valid input for this parameter is $true or $false. The default value is $true. By default, connection filtering uses new IP Block List providers that you create.
 
@@ -189,7 +189,7 @@ Accept wildcard characters: False
 
 ### -IPAddressesMatch
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IPAddressesMatch parameter specifies the IP address status codes that are returned by the block list provider. Use this parameter if the block list provider returns IP address or A record responses. Valid input for this parameter one or more IP addresses in the format 127.0.0.1. You can enter multiple IP addresses separated by commas.
 
@@ -207,7 +207,7 @@ Accept wildcard characters: False
 
 ### -Priority
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Priority parameter specifies the order that the Connection Filtering agent queries the IP Block list providers. A lower priority integer value indicates a higher priority. By default, every time that you add a new IP Block list provider, the entry is assigned a priority of N+1, where N is the number of IP Block list provider services that you have configured.
 
@@ -227,7 +227,7 @@ Accept wildcard characters: False
 
 ### -RejectionResponse
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RejectionResponse parameter specifies the text that you want to include in the SMTP rejection response when messages are blocked by connection filtering. The argument can't exceed 240 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -247,7 +247,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-MailboxDatabaseCopy.md b/exchange/exchange-ps/ExchangePowerShell/Add-MailboxDatabaseCopy.md
index c76c4e5760..94aac1dcad 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-MailboxDatabaseCopy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Add-MailboxDatabaseCopy.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -74,7 +74,7 @@ This example adds a copy of mailbox database DB3 to the Mailbox server MBX4. Rep
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the mailbox database that's being copied. You can use any value that uniquely identifies the database. For example:
 
@@ -96,7 +96,7 @@ Accept wildcard characters: False
 
 ### -MailboxServer
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MailboxServer parameter specifies the name of the server that hosts the database copy. This server must be a member of the same DAG and must not already host a copy of the database.
 
@@ -114,7 +114,7 @@ Accept wildcard characters: False
 
 ### -ActivationPreference
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ActivationPreference parameter value is used as part of Active Manager's best copy selection process and to redistribute active mailbox databases throughout the DAG when using the RedistributeActiveDatabases.ps1 script. The value for the activation preference is a number equal to or greater than 1, where 1 is at the top of the preference order. The preference number can't be larger than the number of copies of the mailbox database.
 
@@ -132,7 +132,7 @@ Accept wildcard characters: False
 
 ### -ConfigurationOnly
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ConfigurationOnly switch allows database copies to be added without invoking automatic seeding. You don't need to specify a value with this switch.
 
@@ -152,7 +152,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -173,7 +173,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -191,7 +191,7 @@ Accept wildcard characters: False
 
 ### -ReplayLagMaxDelay
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ReplayLagMaxDelay parameter specifies the maximum delay for lagged database copy play down (also known as deferred lagged copy play down). If the disk read IO latency is greater than 25 ms, lagged copy play down is delayed up to the value of this parameter.
 
@@ -215,7 +215,7 @@ Accept wildcard characters: False
 
 ### -ReplayLagTime
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ReplayLagTime parameter specifies the amount of time that the Microsoft Exchange Replication service waits before replaying log files that have been copied to the database copy.
 
@@ -237,7 +237,7 @@ Accept wildcard characters: False
 
 ### -SeedingPostponed
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SeedingPostponed switch specifies that the task doesn't seed the database copy, so you need to explicitly seed the database copy. You don't need to specify a value with this switch.
 
@@ -255,7 +255,7 @@ Accept wildcard characters: False
 
 ### -TruncationLagTime
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TruncationLagTime parameter specifies the amount of time that the Microsoft Exchange Replication service waits before truncating log files that have replayed into a copy of the database. The time period begins after the log is successfully replayed into the copy of the database.
 
@@ -277,7 +277,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-MailboxFolderPermission.md b/exchange/exchange-ps/ExchangePowerShell/Add-MailboxFolderPermission.md
index 93f7798c11..f8c9b6d56e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-MailboxFolderPermission.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Add-MailboxFolderPermission.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
 Locale: en-US
@@ -63,7 +63,7 @@ In Exchange Online, this example adds Laura as a calendar delegate to Ayla's mai
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the target mailbox and folder. The syntax is `MailboxID:\ParentFolder[\SubFolder]`.
 
@@ -96,7 +96,7 @@ Accept wildcard characters: False
 
 ### -AccessRights
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AccessRights parameter specifies the permissions that you want to add for the user on the mailbox folder.
 
@@ -148,7 +148,7 @@ Accept wildcard characters: False
 
 ### -User
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The User parameter specifies who's granted permission to the mailbox folder. Valid values are mail-enabled security principals (mail-enabled accounts or groups that have security identifiers or SIDs that can have permissions assigned to them). For example:
 
@@ -184,7 +184,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -205,7 +205,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -283,7 +283,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-MailboxPermission.md b/exchange/exchange-ps/ExchangePowerShell/Add-MailboxPermission.md
index e3d74dcb35..cb64d53366 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-MailboxPermission.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Add-MailboxPermission.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -103,7 +103,7 @@ In Exchange Online, this example assigns the administrator account admin@contoso
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the mailbox where you want to assign permissions to the user. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -132,7 +132,7 @@ Accept wildcard characters: False
 
 ### -AccessRights
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AccessRights parameter specifies the permission that you want to add for the user on the mailbox. Valid values are:
 
@@ -161,7 +161,7 @@ Accept wildcard characters: False
 
 ### -Instance
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -181,7 +181,7 @@ Accept wildcard characters: False
 
 ### -Owner
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Owner parameter specifies the owner of the mailbox object. You can specify the following types of users or groups (security principals) for this parameter:
 
@@ -220,7 +220,7 @@ Accept wildcard characters: False
 
 ### -User
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The User parameter specifies who gets the permissions on the mailbox. You can specify the following types of users or groups (security principals) for this parameter:
 
@@ -264,7 +264,7 @@ Accept wildcard characters: False
 
 ### -AutoMapping
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AutoMapping parameter includes or excludes the mailbox from the auto-mapping feature in Microsoft Outlook. Auto-mapping uses Autodiscover to automatically add mailboxes to a user's Outlook profile if the user has Full Access permission to the mailbox. However, Autodiscover doesn't enumerate security groups that have Full Access permission to the mailbox. Valid values are:
 
@@ -287,7 +287,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -308,7 +308,7 @@ Accept wildcard characters: False
 
 ### -Deny
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Deny switch specifies that the permissions you're adding are Deny permissions. You don't need to specify a value with this switch.
 
@@ -326,7 +326,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -366,7 +366,7 @@ Accept wildcard characters: False
 
 ### -IgnoreDefaultScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange PowerShell session, and to use the entire forest as the scope. You don't need to specify a value with this switch.
 
@@ -389,7 +389,7 @@ Accept wildcard characters: False
 
 ### -InheritanceType
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The InheritanceType parameter specifies how permissions are inherited by folders in the mailbox. Valid values are:
 
@@ -413,7 +413,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-ManagementRoleEntry.md b/exchange/exchange-ps/ExchangePowerShell/Add-ManagementRoleEntry.md
index ae6c6b0762..711946c26d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-ManagementRoleEntry.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Add-ManagementRoleEntry.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -90,7 +90,7 @@ In on-premises Exchange, this example adds the MailboxAudit script with the Depa
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the role entry that you want to add. This parameter uses the syntax: `Management role\role entry name` (for example, `CustomRole\Set-Mailbox`).
 
@@ -112,7 +112,7 @@ Accept wildcard characters: False
 
 ### -ParentRoleEntry
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ParentRoleEntry parameter specifies the role entry in the parent role to add to the role specified with the Role parameter. This parameter generally isn't used directly, but exists to enable the piping of role entries from the Get-ManagementRoleEntry cmdlet. If you use the ParentRoleEntry parameter, you can't use the UnScopedTopLevel switch.
 
@@ -130,7 +130,7 @@ Accept wildcard characters: False
 
 ### -Role
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Role parameter specifies the role to which the new role entry, specified by the ParentRoleEntry parameter, is added.
 
@@ -148,7 +148,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -169,7 +169,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -211,7 +211,7 @@ Accept wildcard characters: False
 
 ### -Overwrite
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Overwrite switch causes existing role entries to be overwritten by the role entries being added. You don't need to specify a value with this switch.
 
@@ -229,7 +229,7 @@ Accept wildcard characters: False
 
 ### -Parameters
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Parameters parameter specifies the parameters to be included in the role being added. The parameters specified must exist on the cmdlet associated with the role entry. You can specify multiple parameters, separated with commas.
 
@@ -247,7 +247,7 @@ Accept wildcard characters: False
 
 ### -PSSnapinName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -267,7 +267,7 @@ Accept wildcard characters: False
 
 ### -Type
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Type parameter specifies the type of role entry being added. The valid values are Cmdlet, Script and ApplicationPermission.
 
@@ -285,7 +285,7 @@ Accept wildcard characters: False
 
 ### -UnScopedTopLevel
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -311,7 +311,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-PublicFolderClientPermission.md b/exchange/exchange-ps/ExchangePowerShell/Add-PublicFolderClientPermission.md
index 8bfbcd9ac9..9686b9e4d2 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-PublicFolderClientPermission.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Add-PublicFolderClientPermission.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.WebClient-Help.xml
 Locale: en-US
@@ -53,7 +53,7 @@ This example adds permission for the user Chris to create items in the public fo
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the GUID or public folder name that represents a specific public folder. You can also include the path using the format TopLevelPublicFolder\\PublicFolder.
 
@@ -73,7 +73,7 @@ Accept wildcard characters: False
 
 ### -AccessRights
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AccessRights parameter specifies the rights that you want to add for the user on the public folder.
 
@@ -118,7 +118,7 @@ Accept wildcard characters: False
 
 ### -User
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The User parameter specifies the user for whom rights are being added.
 
@@ -141,7 +141,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -162,7 +162,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -209,7 +209,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-ResubmitRequest.md b/exchange/exchange-ps/ExchangePowerShell/Add-ResubmitRequest.md
index 74bb47fd4f..86d99f2f49 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-ResubmitRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Add-ResubmitRequest.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -66,7 +66,7 @@ This example replays the redundant copies of messages delivered from 6:00 PM Jun
 
 ### -EndTime
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The EndTime parameter specifies the delivery time of the latest messages that need to be resubmitted from Safety Net.
 
@@ -88,7 +88,7 @@ Accept wildcard characters: False
 
 ### -StartTime
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The StartTime parameter specifies the delivery time of the oldest messages that need to be resubmitted from Safety Net.
 
@@ -110,7 +110,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -131,7 +131,7 @@ Accept wildcard characters: False
 
 ### -CorrelationId
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -149,7 +149,7 @@ Accept wildcard characters: False
 
 ### -Destination
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Destination parameter specifies the GUID of the destination mailbox database. To find the GUID of the mailbox database, run the command: `Get-MailboxDatabase -Server <ServerName> | Format-List Name,GUID`.
 
@@ -169,7 +169,7 @@ Accept wildcard characters: False
 
 ### -MessageId
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MessageId parameter filters the results by the Message-ID header field of the message. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which might include angle brackets) and enclose the value in quotation marks (for example, "<d9683b4c-127b-413a-ae2e-fa7dfb32c69d@contoso.com>").
 
@@ -187,7 +187,7 @@ Accept wildcard characters: False
 
 ### -Recipient
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Recipient parameter filters the messages to resubmit from Safety Net by the specified recipient's email address.
 
@@ -207,7 +207,7 @@ Accept wildcard characters: False
 
 ### -ResubmitTo
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ResubmitTo parameter specifies the recipient's email address for resubmitted messages that are identified by using the Recipient or Sender parameters.
 
@@ -225,7 +225,7 @@ Accept wildcard characters: False
 
 ### -Sender
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Sender parameter filters the messages to resubmit from Safety Net by the specified sender's email address.
 
@@ -245,7 +245,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
 
@@ -270,7 +270,7 @@ Accept wildcard characters: False
 
 ### -TestOnly
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -288,7 +288,7 @@ Accept wildcard characters: False
 
 ### -UnresponsivePrimaryServers
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The UnresponsivePrimaryServers parameter identifies the primary servers that should resubmit the messages from Safety Net as being unavailable so other servers can resubmit the messages. If the primary servers are unavailable, you can designate other servers that hold redundant copies of the messages in Safety Net to resubmit their copies of the messages. However, you must identify the unresponsive primary servers to the other servers using this parameter.
 
@@ -306,7 +306,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-RoleGroupMember.md b/exchange/exchange-ps/ExchangePowerShell/Add-RoleGroupMember.md
index a700deba46..5786755108 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-RoleGroupMember.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Add-RoleGroupMember.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -75,7 +75,7 @@ This example adds the Training Assistants USG to the Training Administrators rol
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The Identity parameter specifies the role group to add a member to. If the role group name contains spaces, enclose the name in quotation marks (").
 
@@ -93,7 +93,7 @@ Accept wildcard characters: False
 
 ### -Member
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The Member parameter specifies who you want to add to the role group. You can specify the following types of users or groups (security principals) for this parameter:
 
@@ -129,7 +129,7 @@ Accept wildcard characters: False
 
 ### -BypassSecurityGroupManagerCheck
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The BypassSecurityGroupManagerCheck switch specifies whether to allow a user who isn't an owner of the group to modify or delete the group. You don't need to specify a value with this switch.
 
@@ -152,7 +152,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -173,7 +173,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -193,7 +193,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The WhatIf switch doesn't work in Security & Compliance PowerShell.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Add-ServerMonitoringOverride.md b/exchange/exchange-ps/ExchangePowerShell/Add-ServerMonitoringOverride.md
index d0ca5ec943..af9e8c7c0b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Add-ServerMonitoringOverride.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Add-ServerMonitoringOverride.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -54,7 +54,7 @@ This example adds a server monitoring override that disables the responder Activ
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the identity of the monitoring item that you want to override. This parameter uses the syntax `HealthSet\MonitoringItemName[\TargetResource]`. The values are case sensitive. For example, use `AD\ActiveDirectoryConnectivityConfigDCServerReboot`, not `ad\activedirectoryconnectivityconfigdcserverreboot`.
 
@@ -74,7 +74,7 @@ Accept wildcard characters: False
 
 ### -ApplyVersion
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ApplyVersion parameter specifies the version of Exchange that gets the override. If you update Exchange to a newer version (for example, you apply a Cumulative Update or Service Pack), the override is no longer applied to the server.
 
@@ -96,7 +96,7 @@ Accept wildcard characters: False
 
 ### -ItemType
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ItemType parameter specifies the server item type for the property that you want to override. Valid value are:
 
@@ -118,7 +118,7 @@ Accept wildcard characters: False
 
 ### -PropertyName
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PropertyName parameter specifies the server property that you want to override.
 
@@ -136,7 +136,7 @@ Accept wildcard characters: False
 
 ### -PropertyValue
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PropertyValue parameter specifies the new value for the server property that you want to override.
 
@@ -154,7 +154,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Exchange server where you want to add the monitoring override. You can use any value that uniquely identifies the server. For example:
 
@@ -179,7 +179,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -200,7 +200,7 @@ Accept wildcard characters: False
 
 ### -Duration
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Duration parameter specifies the length of time that the override is active.
 
@@ -224,7 +224,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Clear-ActiveSyncDevice.md b/exchange/exchange-ps/ExchangePowerShell/Clear-ActiveSyncDevice.md
index 2a911c759e..9e7abc5201 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Clear-ActiveSyncDevice.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Clear-ActiveSyncDevice.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
 Locale: en-US
@@ -67,7 +67,7 @@ This example cancels a previously sent Clear-ActiveSyncDevice command request fo
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the identity of the device that you want to reset.
 
@@ -85,7 +85,7 @@ Accept wildcard characters: False
 
 ### -Cancel
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Cancel switch specifies whether to issue a cancellation request for a pending remote device wipe. You don't need to specify a value with this switch.
 
@@ -103,7 +103,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -126,7 +126,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -146,7 +146,7 @@ Accept wildcard characters: False
 
 ### -NotificationEmailAddresses
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The NotificationEmailAddresses parameter specifies the notification email address for the remote device wipe confirmation. You can specify multiple values separated by commas.
 
@@ -164,7 +164,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Clear-MobileDevice.md b/exchange/exchange-ps/ExchangePowerShell/Clear-MobileDevice.md
index c202f39495..e6ee9c56d3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Clear-MobileDevice.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Clear-MobileDevice.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
 Locale: en-US
@@ -66,7 +66,7 @@ This example cancels a previously sent Clear-MobileDevice command request for th
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the mobile device that you want to reset. You can use the following values that uniquely identifies the mobile device:
 
@@ -88,7 +88,7 @@ Accept wildcard characters: False
 
 ### -AccountOnly
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AccountOnly switch specifies whether to perform an account-only remote device wipe where only Exchange mailbox data is removed from the device. You don't need to specify a value with this switch.
 
@@ -108,7 +108,7 @@ Accept wildcard characters: False
 
 ### -Cancel
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Cancel switch specifies whether to issue a cancellation request for a pending remote device wipe. You don't need to specify a value with this switch.
 
@@ -126,7 +126,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -149,7 +149,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -169,7 +169,7 @@ Accept wildcard characters: False
 
 ### -NotificationEmailAddresses
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The NotificationEmailAddresses parameter specifies the notification email address for the remote device wipe confirmation. You can specify multiple values separated by commas.
 
@@ -187,7 +187,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Clear-TextMessagingAccount.md b/exchange/exchange-ps/ExchangePowerShell/Clear-TextMessagingAccount.md
index e68025ff05..7e3d2fdad5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Clear-TextMessagingAccount.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Clear-TextMessagingAccount.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.WebClient-Help.xml
 Locale: en-US
@@ -48,7 +48,7 @@ This example clears the text messaging account settings and notification setting
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the target mailbox. You can any value that uniquely identifies the mailbox. For example:
 
@@ -77,7 +77,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -98,7 +98,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -118,7 +118,7 @@ Accept wildcard characters: False
 
 ### -IgnoreDefaultScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange PowerShell session, and to use the entire forest as the scope. You don't need to specify a value with this switch.
 
@@ -141,7 +141,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Compare-TextMessagingVerificationCode.md b/exchange/exchange-ps/ExchangePowerShell/Compare-TextMessagingVerificationCode.md
index 83845e82d0..e1af49693c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Compare-TextMessagingVerificationCode.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Compare-TextMessagingVerificationCode.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.WebClient-Help.xml
 Locale: en-US
@@ -63,7 +63,7 @@ This example compares the verification code 111555 to the code sent to Tony Smit
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the mailbox where you are trying to enable text messaging notifications. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -92,7 +92,7 @@ Accept wildcard characters: False
 
 ### -VerificationCode
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The VerificationCode parameter contains the verification code that the user specified.
 
@@ -110,7 +110,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -131,7 +131,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -151,7 +151,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Complete-MigrationBatch.md b/exchange/exchange-ps/ExchangePowerShell/Complete-MigrationBatch.md
index a8ed9f625e..5a40710740 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Complete-MigrationBatch.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Complete-MigrationBatch.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -61,7 +61,7 @@ This example completes the migration batch LocalMove1 and sends a notification e
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the name of the migration batch that you want to complete. The value for this parameter is specified by the Name parameter for the New-MigrationBatch cmdlet. Use the Get-MigrationBatch cmdlet to determine the value of this parameter for the migration batch.
 
@@ -99,7 +99,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -122,7 +122,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -142,7 +142,7 @@ Accept wildcard characters: False
 
 ### -NotificationEmails
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -184,7 +184,7 @@ Accept wildcard characters: False
 
 ### -SyncAndComplete
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SyncAndComplete switch specifies whether to trigger a synchronization immediately followed by a completion of the migration batch if the synchronization was successful. You don't need to specify a value with this switch.
 
@@ -202,7 +202,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Connect-Mailbox.md b/exchange/exchange-ps/ExchangePowerShell/Connect-Mailbox.md
index 8d4f60535b..37a5e4b89c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Connect-Mailbox.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Connect-Mailbox.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -168,7 +168,7 @@ This example connects a room mailbox.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the mailbox that you want to connect to a user account. This parameter doesn't specify an Active Directory object. You can use the following values to identify the mailbox:
 
@@ -192,7 +192,7 @@ Accept wildcard characters: False
 
 ### -Database
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Database parameter specifies the Exchange database that contains the mailbox that you want to connect. You can use any value that uniquely identifies the database. For example:
 
@@ -216,7 +216,7 @@ Accept wildcard characters: False
 
 ### -Equipment
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Equipment switch is required to connect equipment mailboxes. You don't need to specify a value with this switch.
 
@@ -236,7 +236,7 @@ Accept wildcard characters: False
 
 ### -LinkedDomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The LinkedDomainController parameter specifies the domain controller in the forest where the user account resides, if the mailbox is a linked mailbox. The domain controller in the forest where the user account resides is used to get security information for the account specified by the LinkedMasterAccount parameter. Use the fully qualified domain name (FQDN) of the domain controller that you want to use as the value for this parameter.
 
@@ -256,7 +256,7 @@ Accept wildcard characters: False
 
 ### -LinkedMasterAccount
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The LinkedMasterAccount parameter specifies the master account in the forest where the user account resides, if this mailbox is a linked mailbox. The master account is the account that the mailbox is linked to. The master account grants access to the mailbox. This parameter is required only if you're creating a linked mailbox. You can use any value that uniquely identifies the master account. For example:
 
@@ -281,7 +281,7 @@ Accept wildcard characters: False
 
 ### -Room
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Room switch is required to connect room mailboxes. You don't need to specify a value with this switch.
 
@@ -301,7 +301,7 @@ Accept wildcard characters: False
 
 ### -Shared
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Shared switch is required to connect shared mailboxes. You don't need to specify a value with this switch.
 
@@ -321,7 +321,7 @@ Accept wildcard characters: False
 
 ### -ValidateOnly
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ValidateOnly switch specifies whether to evaluate the potential success or failure of the command without making changes. You don't need to specify a value with this switch.
 
@@ -341,7 +341,7 @@ Accept wildcard characters: False
 
 ### -ActiveSyncMailboxPolicy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ActiveSyncMailboxPolicy parameter specifies the mobile device mailbox policy that's applied to the mailbox. You can use any value that uniquely identifies the policy. For example:.
 
@@ -365,7 +365,7 @@ Accept wildcard characters: False
 
 ### -AddressBookPolicy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AddressBookPolicy parameter specifies the address book policy that's applied to the mailbox. You can use any value that uniquely identifies the address book policy. For example:
 
@@ -389,7 +389,7 @@ Accept wildcard characters: False
 
 ### -Alias
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Alias parameter specifies the Exchange alias (also known as the mail nickname) for the recipient. This value identifies the recipient as a mail-enabled object, and shouldn't be confused with multiple email addresses for the same recipient (also known as proxy addresses). A recipient can have only one Alias value. The maximum length is 64 characters.
 
@@ -425,7 +425,7 @@ Accept wildcard characters: False
 
 ### -AllowLegacyDNMismatch
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -443,7 +443,7 @@ Accept wildcard characters: False
 
 ### -Archive
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Archive switch specifies whether to connect the associated archive mailbox. You don't need to specify a value with this switch.
 
@@ -461,7 +461,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -482,7 +482,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -500,7 +500,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -520,7 +520,7 @@ Accept wildcard characters: False
 
 ### -LinkedCredential
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The LinkedCredential parameter specifies the credentials used to access the domain controller that's specified by the LinkedDomainController parameter. This parameter is optional, even if you're connecting a linked mailbox.
 
@@ -540,7 +540,7 @@ Accept wildcard characters: False
 
 ### -ManagedFolderMailboxPolicy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -558,7 +558,7 @@ Accept wildcard characters: False
 
 ### -ManagedFolderMailboxPolicyAllowed
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -576,7 +576,7 @@ Accept wildcard characters: False
 
 ### -RetentionPolicy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RetentionPolicy parameter specifies the retention policy that's applied to the mailbox. You can use any value that uniquely identifies the policy. For example:
 
@@ -600,7 +600,7 @@ Accept wildcard characters: False
 
 ### -User
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The User parameter specifies the user object in Active Directory that you want to connect the mailbox to.
 
@@ -632,7 +632,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-AddressListPaging.md b/exchange/exchange-ps/ExchangePowerShell/Disable-AddressListPaging.md
index c525408a82..0c7b2a55ce 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-AddressListPaging.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-AddressListPaging.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -44,7 +44,7 @@ This example disables virtual list view for address lists in your organization.
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -67,7 +67,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -85,7 +85,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-App.md b/exchange/exchange-ps/ExchangePowerShell/Disable-App.md
index c176a7102c..1ca9ed7f04 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-App.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-App.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.WebClient-Help.xml
 Locale: en-US
@@ -66,7 +66,7 @@ This example disables the Share to Teams app for user Tony.
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the GUID of the app.
 
@@ -84,7 +84,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -107,7 +107,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -127,7 +127,7 @@ Accept wildcard characters: False
 
 ### -Mailbox
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Mailbox parameter specifies the identity of the mailbox. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -158,7 +158,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-CmdletExtensionAgent.md b/exchange/exchange-ps/ExchangePowerShell/Disable-CmdletExtensionAgent.md
index 1ba7f512d3..02844b93ac 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-CmdletExtensionAgent.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-CmdletExtensionAgent.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -49,7 +49,7 @@ This example disables the cmdlet extension agent named Scripting Agent.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the enabled cmdlet extension agent that you want to disable. You can use any value that uniquely identifies the agent. For example:
 
@@ -71,7 +71,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -94,7 +94,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -112,7 +112,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-DistributionGroup.md b/exchange/exchange-ps/ExchangePowerShell/Disable-DistributionGroup.md
index 81854c040f..ebe082cf21 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-DistributionGroup.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-DistributionGroup.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
 Locale: en-US
@@ -48,7 +48,7 @@ This example mail-disables the distribution group named Distribution Group1.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the distribution group or mail-enabled security group that you want to mail-disable. You can use any value that uniquely identifies the group. For example:
 
@@ -73,7 +73,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -96,7 +96,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -114,7 +114,7 @@ Accept wildcard characters: False
 
 ### -IgnoreDefaultScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange PowerShell session, and to use the entire forest as the scope. You don't need to specify a value with this switch.
 
@@ -137,7 +137,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-InboxRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-InboxRule.md
index dde3d20511..6844c2d30f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-InboxRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-InboxRule.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -50,7 +50,7 @@ This example disables the Inbox rule MoveAnnouncements in the mailbox Joe@Contos
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the Inbox rule that you want to disable. You can use any value that uniquely identifies the rule. For example:
 
@@ -73,7 +73,7 @@ Accept wildcard characters: False
 
 ### -AlwaysDeleteOutlookRulesBlob
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AlwaysDeleteOutlookRulesBlob switch hides a warning message when you use Outlook on the web (formerly known as Outlook Web App) or Exchange PowerShell to modify Inbox rules. You don't need to specify a value with this switch.
 
@@ -91,7 +91,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -114,7 +114,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -134,7 +134,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -156,7 +156,7 @@ Accept wildcard characters: False
 
 ### -Mailbox
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Mailbox parameter specifies the mailbox that contains the Inbox rule. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -185,7 +185,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch doesn't work on this cmdlet.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-JournalRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-JournalRule.md
index c2e684786c..afa8c7c7f9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-JournalRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-JournalRule.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailControl-Help.xml
 Locale: en-US
@@ -54,7 +54,7 @@ This example disables all journal rules. The Get-JournalRule cmdlet is used to a
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the journal rule you want to disable. Enter either the name or the GUID of the journal rule. You can omit this parameter label.
 
@@ -72,7 +72,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -95,7 +95,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -115,7 +115,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-MailContact.md b/exchange/exchange-ps/ExchangePowerShell/Disable-MailContact.md
index 66d3cc5e91..29c0f0cafb 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-MailContact.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-MailContact.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -48,7 +48,7 @@ This example mail-disables the mail contact named Ed Meadows.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the mail contact that you want to mail-disable. You can use any value that uniquely identifies the mail contact. For example:
 
@@ -73,7 +73,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -96,7 +96,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -114,7 +114,7 @@ Accept wildcard characters: False
 
 ### -IgnoreDefaultScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange PowerShell session, and to use the entire forest as the scope. You don't need to specify a value with this switch.
 
@@ -137,7 +137,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-MailPublicFolder.md b/exchange/exchange-ps/ExchangePowerShell/Disable-MailPublicFolder.md
index 19e6f06e0d..8c17a89a9b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-MailPublicFolder.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-MailPublicFolder.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.WebClient-Help.xml
 Locale: en-US
@@ -46,7 +46,7 @@ This example mail-disables the public folder Help Desk.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the GUID or public folder name that represents a specific public folder. You can also include the path using the format TopLevelPublicFolder\\PublicFolder.
 
@@ -66,7 +66,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -89,7 +89,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -136,7 +136,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-MailUser.md b/exchange/exchange-ps/ExchangePowerShell/Disable-MailUser.md
index 3bc30aea90..63338fd044 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-MailUser.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-MailUser.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -49,7 +49,7 @@ This example mail-disables an existing mail user.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the mail user that you want to mail-disable. You can use any value that uniquely identifies the mail user. For example:
 
@@ -74,7 +74,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -97,7 +97,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -115,7 +115,7 @@ Accept wildcard characters: False
 
 ### -IgnoreDefaultScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange PowerShell session, and to use the entire forest as the scope. You don't need to specify a value with this switch.
 
@@ -138,7 +138,7 @@ Accept wildcard characters: False
 
 ### -IgnoreLegalHold
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IgnoreLegalHold switch ignores the legal hold status of the user. You don't need to specify a value with this switch.
 
@@ -160,7 +160,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-Mailbox.md b/exchange/exchange-ps/ExchangePowerShell/Disable-Mailbox.md
index ffd3bd0dd9..273ce9e0bd 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-Mailbox.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-Mailbox.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -101,7 +101,7 @@ This example disables the remote archive for the on-premises user named John Woo
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the mailbox that you want to mailbox-disable. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -130,7 +130,7 @@ Accept wildcard characters: False
 
 ### -Arbitration
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -152,7 +152,7 @@ Accept wildcard characters: False
 
 ### -Archive
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Archive switch specifies whether to disconnect the archive mailbox from the associated user. You don't need to specify a value with this switch.
 
@@ -172,7 +172,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -195,7 +195,7 @@ Accept wildcard characters: False
 
 ### -DisableArbitrationMailboxWithOABsAllowed
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -215,7 +215,7 @@ Accept wildcard characters: False
 
 ### -DisableLastArbitrationMailboxAllowed
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -235,7 +235,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -255,7 +255,7 @@ Accept wildcard characters: False
 
 ### -IgnoreDefaultScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -280,7 +280,7 @@ Accept wildcard characters: False
 
 ### -IgnoreLegalHold
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -329,7 +329,7 @@ Accept wildcard characters: False
 
 ### -PublicFolder
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -351,7 +351,7 @@ Accept wildcard characters: False
 
 ### -RemoteArchive
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -373,7 +373,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-MailboxQuarantine.md b/exchange/exchange-ps/ExchangePowerShell/Disable-MailboxQuarantine.md
index 69bd293167..f33a6ec479 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-MailboxQuarantine.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-MailboxQuarantine.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -116,7 +116,7 @@ Accept wildcard characters: False
 
 ### -Database
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Database parameter specifies the database that contains the mailboxes you want to release from quarantine. You can use any value that uniquely identifies the database. For example:
 
@@ -142,7 +142,7 @@ Accept wildcard characters: False
 
 ### -IncludeAllDatabases
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IncludeAllDatabases switch specifies that you want to release all quarantined mailboxes in all databases on the server you specify with the Server parameter. You don't need to specify a value with this switch.
 
@@ -162,7 +162,7 @@ Accept wildcard characters: False
 
 ### -IncludeAllMailboxes
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IncludeAllMailboxes switch specifies that you want to release all mailboxes from quarantine in the database you specify with the Database parameter. You don't need to specify a value with this switch.
 
@@ -182,7 +182,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the server that contains the mailboxes that you want to release from quarantine by using the IncludeAllDatabases switch. You can use any value that uniquely identifies the server. For example:
 
@@ -207,7 +207,7 @@ Accept wildcard characters: False
 
 ### -StoreMailboxIdentity
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The StoreMailboxIdentity parameter specifies the mailbox that you want to release from quarantine when you use the Database parameter.
 
@@ -229,7 +229,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -252,7 +252,7 @@ Accept wildcard characters: False
 
 ### -IncludePassive
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IncludePassive switch specifies that you also want to release inactive copies of the mailbox from quarantine. You don't need to specify a value with this switch.
 
@@ -270,7 +270,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-MalwareFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-MalwareFilterRule.md
index 3135c19f76..28433ca829 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-MalwareFilterRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-MalwareFilterRule.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -45,7 +45,7 @@ This example disables the enabled malware filter rule named Contoso Recipients.
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the malware filter rule that you want to disable. You can use any value that uniquely identifies the rule. For example, you can use the name, GUID or distinguished name (DN) of the malware filter rule.
 
@@ -63,7 +63,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -86,7 +86,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -106,7 +106,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-MetaCacheDatabase.md b/exchange/exchange-ps/ExchangePowerShell/Disable-MetaCacheDatabase.md
index cff0f8762f..97db1f920f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-MetaCacheDatabase.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-MetaCacheDatabase.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2019
+applicable: Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -44,7 +44,7 @@ This example disables the metacache database on the Exchange server named Mailbo
 
 ### -Server
 
-> Applicable: Exchange Server 2019
+> Applicable: Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Mailbox server where you want to disable the metacache database. You can use any value that uniquely identifies the server. For example:
 
@@ -69,7 +69,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2019
+> Applicable: Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -90,7 +90,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2019
+> Applicable: Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-OutlookProtectionRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-OutlookProtectionRule.md
index f294454b97..7230030d14 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-OutlookProtectionRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-OutlookProtectionRule.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -51,7 +51,7 @@ This example disables the Outlook protection rule Project Contoso.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the name of the rule being disabled.
 
@@ -69,7 +69,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -92,7 +92,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -112,7 +112,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-PushNotificationProxy.md b/exchange/exchange-ps/ExchangePowerShell/Disable-PushNotificationProxy.md
index 45364575b0..8eb51ee19e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-PushNotificationProxy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-PushNotificationProxy.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
 Locale: en-US
@@ -45,7 +45,7 @@ This example disables the push notification proxy in the on-premises Exchange or
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -68,7 +68,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-RemoteMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Disable-RemoteMailbox.md
index ce5291ee76..805dcedf5e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-RemoteMailbox.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-RemoteMailbox.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -69,7 +69,7 @@ This example removes the cloud-based archive mailbox but keeps the cloud-based m
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the cloud-based mailbox. Valid values are:
 
@@ -96,7 +96,7 @@ Accept wildcard characters: False
 
 ### -Archive
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Archive switch specifies whether to disconnect the cloud-based archive mailbox from the associated cloud-based mailbox. You don't need to specify a value with this switch.
 
@@ -116,7 +116,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -139,7 +139,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -157,7 +157,7 @@ Accept wildcard characters: False
 
 ### -IgnoreDefaultScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange PowerShell session, and to use the entire forest as the scope. You don't need to specify a value with this switch.
 
@@ -180,7 +180,7 @@ Accept wildcard characters: False
 
 ### -IgnoreLegalHold
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IgnoreLegalHold switch ignores the legal hold status of the remote user. You don't need to specify a value with this switch.
 
@@ -200,7 +200,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-ServiceEmailChannel.md b/exchange/exchange-ps/ExchangePowerShell/Disable-ServiceEmailChannel.md
index 66799f5106..0a53d8ae61 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-ServiceEmailChannel.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-ServiceEmailChannel.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -61,7 +61,7 @@ This example disables the .NET service channel for the user Jeff Hay without req
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the identity of the user for which you want to enable the .NET service channel. The user specified must be a valid user in Active Directory who has an Exchange mailbox.
 
@@ -92,7 +92,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -115,7 +115,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -133,7 +133,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-SweepRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-SweepRule.md
index 5049dce174..a4cef4646f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-SweepRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-SweepRule.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -53,7 +53,7 @@ This example disables all Sweep rules in the specified mailbox.
 
 ### -Identity
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the Sweep rule that you want to disable. You can use any value that uniquely identifies the rule. For example:
 
@@ -75,7 +75,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -96,7 +96,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -116,7 +116,7 @@ Accept wildcard characters: False
 
 ### -Mailbox
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Mailbox parameter specifies the mailbox that contains the rule you want to disable. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -145,7 +145,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-TransportAgent.md b/exchange/exchange-ps/ExchangePowerShell/Disable-TransportAgent.md
index 675098e0b9..3eaed77483 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-TransportAgent.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-TransportAgent.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -46,7 +46,7 @@ This example shows how a fictitious application named Test App is disabled in th
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the display name of the transport agent to be disabled. The length of the name can't exceed 64 characters.
 
@@ -64,7 +64,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -87,7 +87,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -107,7 +107,7 @@ Accept wildcard characters: False
 
 ### -TransportService
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TransportService parameter specifies the transport service that you want to view or modify. Valid values for this parameter are:
 
@@ -131,7 +131,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-TransportRule.md b/exchange/exchange-ps/ExchangePowerShell/Disable-TransportRule.md
index 72a6cd1f6e..46e2f40a3a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Disable-TransportRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Disable-TransportRule.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -47,7 +47,7 @@ This example disables the rule named Sales Disclaimer.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the rule that you want to disable. You can use any value that uniquely identifies the rule. For example:
 
@@ -69,7 +69,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -92,7 +92,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -114,7 +114,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Dismount-Database.md b/exchange/exchange-ps/ExchangePowerShell/Dismount-Database.md
index 27e96b01a7..1cd64ef534 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Dismount-Database.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Dismount-Database.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -47,7 +47,7 @@ Regardless of where you run this cmdlet, it operates against the server hosting
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the database that you want to dismount. You can use any value that uniquely identifies the database. For example:
 
@@ -69,7 +69,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -90,7 +90,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -108,7 +108,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Dump-ProvisioningCache.md b/exchange/exchange-ps/ExchangePowerShell/Dump-ProvisioningCache.md
index 0ec91c54ca..5b91af3edb 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Dump-ProvisioningCache.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Dump-ProvisioningCache.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -62,7 +62,7 @@ This example displays all cache keys for the specified server and Windows PowerS
 
 ### -Server
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the fully qualified domain name (FQDN) of the server that the application you want to reset is running on.
 
@@ -80,7 +80,7 @@ Accept wildcard characters: False
 
 ### -Application
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Application parameter specifies the specific administrative application to reset the provisioning cache for. You can use the following values:
 
@@ -105,7 +105,7 @@ Accept wildcard characters: False
 
 ### -GlobalCache
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The GlobalCache switch specifies that all cache keys are cleared. You don't need to specify a value with this switch.
 
@@ -123,7 +123,7 @@ Accept wildcard characters: False
 
 ### -CacheKeys
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The CacheKeys parameter specifies the value for the cache key that you want to clear. The format for the values should contain 32 digits separated by four dashes: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
 
@@ -143,7 +143,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -164,7 +164,7 @@ Accept wildcard characters: False
 
 ### -CurrentOrganization
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The CurrentOrganization switch specifies that the provision cache is reset for this organization. You don't need to specify a value with this switch.
 
@@ -182,7 +182,7 @@ Accept wildcard characters: False
 
 ### -Organizations
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Organizations parameter specifies the organizations where the provisioning cache is reset. This parameter is used in multi-tenant deployments.
 
@@ -200,7 +200,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-AddressListPaging.md b/exchange/exchange-ps/ExchangePowerShell/Enable-AddressListPaging.md
index bb39c286cd..93281b268d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-AddressListPaging.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-AddressListPaging.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -46,7 +46,7 @@ This example enables virtual list view for your organization.
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -67,7 +67,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -85,7 +85,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-AntispamUpdates.md b/exchange/exchange-ps/ExchangePowerShell/Enable-AntispamUpdates.md
index 6a01e8936d..ca733a5aae 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-AntispamUpdates.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-AntispamUpdates.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailControl-Help.xml
 Locale: en-US
@@ -43,7 +43,7 @@ This cmdlet was deprecated in Microsoft Exchange Server 2010 Service Pack 1 and
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -61,7 +61,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -79,7 +79,7 @@ Accept wildcard characters: False
 
 ### -SpamSignatureUpdatesEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -97,7 +97,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-App.md b/exchange/exchange-ps/ExchangePowerShell/Enable-App.md
index 5379a54dbe..dfe13783a8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-App.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-App.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.WebClient-Help.xml
 Locale: en-US
@@ -64,7 +64,7 @@ This example enables the Share to Teams app for user Tony.
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the GUID of the app.
 
@@ -82,7 +82,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -103,7 +103,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -123,7 +123,7 @@ Accept wildcard characters: False
 
 ### -Mailbox
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Mailbox parameter specifies the mailbox. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -152,7 +152,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-CmdletExtensionAgent.md b/exchange/exchange-ps/ExchangePowerShell/Enable-CmdletExtensionAgent.md
index fa6ec7a67a..bb9a5e1e05 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-CmdletExtensionAgent.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-CmdletExtensionAgent.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -51,7 +51,7 @@ This example enables the cmdlet extension agent named Scripting Agent. Before yo
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the disabled cmdlet extension agent that you want to enable. You can use any value that uniquely identifies the agent. For example:
 
@@ -73,7 +73,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -94,7 +94,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -112,7 +112,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-DistributionGroup.md b/exchange/exchange-ps/ExchangePowerShell/Enable-DistributionGroup.md
index 3c3963ce8a..2687d8df3f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-DistributionGroup.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-DistributionGroup.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
 Locale: en-US
@@ -52,7 +52,7 @@ This example mail-enables the universal distribution group named Distribution Gr
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the universal security group or universal distribution group that you want to mail-enable. You can use any value that uniquely identifies the group. For example:
 
@@ -75,7 +75,7 @@ Accept wildcard characters: False
 
 ### -Alias
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Alias parameter specifies the Exchange alias (also known as the mail nickname) for the recipient. This value identifies the recipient as a mail-enabled object, and shouldn't be confused with multiple email addresses for the same recipient (also known as proxy addresses). A recipient can have only one Alias value. The maximum length is 64 characters.
 
@@ -111,7 +111,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -132,7 +132,7 @@ Accept wildcard characters: False
 
 ### -DisplayName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DisplayName parameter specifies the display name of the group. The display name is visible in the Exchange admin center and in address lists. The maximum length is 256 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -150,7 +150,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -168,7 +168,7 @@ Accept wildcard characters: False
 
 ### -PrimarySmtpAddress
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PrimarySmtpAddress parameter specifies the primary return email address that's used for the recipient.
 
@@ -188,7 +188,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-ExchangeCertificate.md b/exchange/exchange-ps/ExchangePowerShell/Enable-ExchangeCertificate.md
index 1d42298bb7..1d585aa2b4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-ExchangeCertificate.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-ExchangeCertificate.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -72,7 +72,7 @@ This example enables a certificate for POP, IMAP, SMTP and IIS services.
 
 ### -Thumbprint
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Thumbprint parameter specifies the certificate that you want to configure. You can find the thumbprint value by using the Get-ExchangeCertificate cmdlet.
 
@@ -92,7 +92,7 @@ Accept wildcard characters: False
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the certificate that you want to configure. Valid values are:
 
@@ -119,7 +119,7 @@ Accept wildcard characters: False
 
 ### -Services
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Services parameter specifies the Exchange services that the certificate is enabled for. Valid values are:
 
@@ -151,7 +151,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -172,7 +172,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -192,7 +192,7 @@ Accept wildcard characters: False
 
 ### -DoNotRequireSsl
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DoNotRequireSsl switch prevents the command from enabling the "require SSL" setting on the default web site when you enable the certificate for IIS. You don't need to specify a value with this switch.
 
@@ -212,7 +212,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -234,7 +234,7 @@ Accept wildcard characters: False
 
 ### -NetworkServiceAllowed
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The NetworkServiceAllowed switch gives the built-in Network Service account permission to read the certificate's private key without enabling the certificate for SMTP. You don't need to specify a value with this switch.
 
@@ -252,7 +252,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
 
@@ -279,7 +279,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-InboxRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-InboxRule.md
index 6c3673325b..3ea7170fbb 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-InboxRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-InboxRule.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -50,7 +50,7 @@ This example enables the Inbox rule named Move To Junk Mail in the mailbox that
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the Inbox rule that you want to enable. You can use any value that uniquely identifies the rule. For example:
 
@@ -73,7 +73,7 @@ Accept wildcard characters: False
 
 ### -AlwaysDeleteOutlookRulesBlob
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AlwaysDeleteOutlookRulesBlob switch hides a warning message when you use Outlook on the web (formerly known as Outlook Web App) or Exchange PowerShell to modify Inbox rules. You don't need to specify a value with this switch.
 
@@ -91,7 +91,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -112,7 +112,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -132,7 +132,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -154,7 +154,7 @@ Accept wildcard characters: False
 
 ### -Mailbox
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Mailbox parameter specifies the mailbox that contains the Inbox rule. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -183,7 +183,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-JournalRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-JournalRule.md
index 244d0391ce..82ee42db15 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-JournalRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-JournalRule.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailControl-Help.xml
 Locale: en-US
@@ -47,7 +47,7 @@ This example enables the existing journal rule Brokerage Communications.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the journal rule you want to enable. Enter either the name or GUID of the journal rule. You can omit this parameter label.
 
@@ -65,7 +65,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -86,7 +86,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -106,7 +106,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-MailContact.md b/exchange/exchange-ps/ExchangePowerShell/Enable-MailContact.md
index 2b9a9f8fda..fcf7d1cd3b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-MailContact.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-MailContact.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -54,7 +54,7 @@ This example mail-enables an existing contact that isn't mail-enabled.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the non-mail-enabled contact that you want to mail-enable. You can use any value that uniquely identifies the contact. For example:
 
@@ -77,7 +77,7 @@ Accept wildcard characters: False
 
 ### -ExternalEmailAddress
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExternalEmailAddress parameter specifies the target email address of the mail contact or mail user. By default, this value is used as the primary email address of the mail contact or mail user.
 
@@ -97,7 +97,7 @@ Accept wildcard characters: False
 
 ### -Alias
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Alias parameter specifies the Exchange alias (also known as the mail nickname) for the recipient. This value identifies the recipient as a mail-enabled object, and shouldn't be confused with multiple email addresses for the same recipient (also known as proxy addresses). A recipient can have only one Alias value. The maximum length is 64 characters.
 
@@ -133,7 +133,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -154,7 +154,7 @@ Accept wildcard characters: False
 
 ### -DisplayName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DisplayName parameter specifies the display name of the mail contact. The display name is visible in the Exchange admin center and in address lists. The maximum length is 256 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -172,7 +172,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -190,7 +190,7 @@ Accept wildcard characters: False
 
 ### -MacAttachmentFormat
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MacAttachmentFormat parameter specifies the Apple Macintosh operating system attachment format to use for messages sent to the mail contact or mail user. Valid values are:
 
@@ -218,7 +218,7 @@ Accept wildcard characters: False
 
 ### -MessageBodyFormat
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MessageBodyFormat parameter specifies the message body format for messages sent to the mail contact or mail user. Valid values are:
 
@@ -245,7 +245,7 @@ Accept wildcard characters: False
 
 ### -MessageFormat
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MessageFormat parameter specifies the message format for messages sent to the mail contact or mail user. Valid values are:
 
@@ -273,7 +273,7 @@ Accept wildcard characters: False
 
 ### -PrimarySmtpAddress
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PrimarySmtpAddress parameter specifies the primary return email address that's used for the recipient.
 
@@ -295,7 +295,7 @@ Accept wildcard characters: False
 
 ### -UsePreferMessageFormat
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The UsePreferMessageFormat specifies whether the message format settings configured for the mail user or mail contact override the global settings configured for the remote domain or configured by the message sender. Valid value are:
 
@@ -316,7 +316,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-MailPublicFolder.md b/exchange/exchange-ps/ExchangePowerShell/Enable-MailPublicFolder.md
index 34c3553ec7..215078a6d5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-MailPublicFolder.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-MailPublicFolder.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.WebClient-Help.xml
 Locale: en-US
@@ -55,7 +55,7 @@ This example mail-enables the public folder Reports that's in the parent folder
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the GUID or public folder name that represents a specific public folder. You can also include the path using the format TopLevelPublicFolder\\PublicFolder.
 
@@ -75,7 +75,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -96,7 +96,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -116,7 +116,7 @@ Accept wildcard characters: False
 
 ### -HiddenFromAddressListsEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The HiddenFromAddressListsEnabled parameter specifies whether the folder is hidden from address lists. Valid values are $true and $false. The default value is $false.
 
@@ -181,7 +181,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-MailUser.md b/exchange/exchange-ps/ExchangePowerShell/Enable-MailUser.md
index ceb3f644e4..83842d063a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-MailUser.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-MailUser.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -70,7 +70,7 @@ This example mail-enables user John with the external email address john@contoso
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the user that you want to mail-enable. You can use any value that uniquely identifies the user. For example:
 
@@ -93,7 +93,7 @@ Accept wildcard characters: False
 
 ### -ExternalEmailAddress
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExternalEmailAddress parameter specifies an email address outside the organization. Email messages sent to the mail-enabled user are sent to this external address.
 
@@ -111,7 +111,7 @@ Accept wildcard characters: False
 
 ### -Alias
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Alias parameter specifies the Exchange alias (also known as the mail nickname) for the recipient. This value identifies the recipient as a mail-enabled object, and shouldn't be confused with multiple email addresses for the same recipient (also known as proxy addresses). A recipient can have only one Alias value. The maximum length is 64 characters.
 
@@ -147,7 +147,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -168,7 +168,7 @@ Accept wildcard characters: False
 
 ### -DisplayName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DisplayName parameter specifies the display name of the mail user. The display name is visible in the Exchange admin center and in address lists. The maximum length is 256 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -186,7 +186,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -204,7 +204,7 @@ Accept wildcard characters: False
 
 ### -MacAttachmentFormat
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MacAttachmentFormat parameter specifies the Apple Macintosh operating system attachment format to use for messages sent to the mail contact or mail user. Valid values are:
 
@@ -232,7 +232,7 @@ Accept wildcard characters: False
 
 ### -MessageBodyFormat
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MessageBodyFormat parameter specifies the message body format for messages sent to the mail contact or mail user. Valid values are:
 
@@ -259,7 +259,7 @@ Accept wildcard characters: False
 
 ### -MessageFormat
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MessageFormat parameter specifies the message format for messages sent to the mail contact or mail user. Valid values are:
 
@@ -287,7 +287,7 @@ Accept wildcard characters: False
 
 ### -PrimarySmtpAddress
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PrimarySmtpAddress parameter specifies the primary return email address that's used for the recipient.
 
@@ -309,7 +309,7 @@ Accept wildcard characters: False
 
 ### -UsePreferMessageFormat
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The UsePreferMessageFormat specifies whether the message format settings configured for the mail user or mail contact override the global settings configured for the remote domain or configured by the message sender. Valid value are:
 
@@ -330,7 +330,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-Mailbox.md b/exchange/exchange-ps/ExchangePowerShell/Enable-Mailbox.md
index 4ca227e302..c29fa8ab72 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-Mailbox.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-Mailbox.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -304,7 +304,7 @@ This example creates a remote archive for the existing on-premises user named Ay
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the user or InetOrgPerson object that you want to mailbox-enable. You can use any value that uniquely identifies the user. For example:
 
@@ -327,7 +327,7 @@ Accept wildcard characters: False
 
 ### -Arbitration
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -349,7 +349,7 @@ Accept wildcard characters: False
 
 ### -ArchiveDomain
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -371,7 +371,7 @@ Accept wildcard characters: False
 
 ### -Discovery
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -393,7 +393,7 @@ Accept wildcard characters: False
 
 ### -Equipment
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -415,7 +415,7 @@ Accept wildcard characters: False
 
 ### -LinkedDomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -437,7 +437,7 @@ Accept wildcard characters: False
 
 ### -LinkedMasterAccount
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -464,7 +464,7 @@ Accept wildcard characters: False
 
 ### -LinkedRoom
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -486,7 +486,7 @@ Accept wildcard characters: False
 
 ### -PublicFolder
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -508,7 +508,7 @@ Accept wildcard characters: False
 
 ### -Room
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -530,7 +530,7 @@ Accept wildcard characters: False
 
 ### -Shared
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -552,7 +552,7 @@ Accept wildcard characters: False
 
 ### -ActiveSyncMailboxPolicy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -578,7 +578,7 @@ Accept wildcard characters: False
 
 ### -AddressBookPolicy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -604,7 +604,7 @@ Accept wildcard characters: False
 
 ### -Alias
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -642,7 +642,7 @@ Accept wildcard characters: False
 
 ### -Archive
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Archive switch creates an archive mailbox for an existing user that already has a mailbox. You don't need to specify a value with this switch.
 
@@ -660,7 +660,7 @@ Accept wildcard characters: False
 
 ### -ArchiveDatabase
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -684,7 +684,7 @@ Accept wildcard characters: False
 
 ### -ArchiveGuid
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -704,7 +704,7 @@ Accept wildcard characters: False
 
 ### -ArchiveName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ArchiveName parameter specifies the name of the archive mailbox. This is the name displayed to users in Outlook on the web (formerly known as Outlook Web App). If the value contains spaces, enclose the value in quotation marks (").
 
@@ -732,7 +732,7 @@ Accept wildcard characters: False
 
 ### -AuditLog
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -779,7 +779,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -800,7 +800,7 @@ Accept wildcard characters: False
 
 ### -Database
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -824,7 +824,7 @@ Accept wildcard characters: False
 
 ### -DisplayName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -846,7 +846,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -866,7 +866,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -886,7 +886,7 @@ Accept wildcard characters: False
 
 ### -HoldForMigration
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -910,7 +910,7 @@ Accept wildcard characters: False
 
 ### -LinkedCredential
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -976,7 +976,7 @@ Accept wildcard characters: False
 
 ### -PrimarySmtpAddress
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -998,7 +998,7 @@ Accept wildcard characters: False
 
 ### -RemoteArchive
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1020,7 +1020,7 @@ Accept wildcard characters: False
 
 ### -RetentionPolicy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1046,7 +1046,7 @@ Accept wildcard characters: False
 
 ### -RoleAssignmentPolicy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The RoleAssignmentPolicy parameter specifies the management role assignment policy that's assigned to the mailbox. You can use any value that uniquely identifies the policy. For example:
 
@@ -1070,7 +1070,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-MailboxQuarantine.md b/exchange/exchange-ps/ExchangePowerShell/Enable-MailboxQuarantine.md
index d539c0c031..fbb199722f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-MailboxQuarantine.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-MailboxQuarantine.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -100,7 +100,7 @@ Accept wildcard characters: False
 
 ### -Database
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Database parameter specifies the database that contains the mailboxes you want to quarantine. You can use any value that uniquely identifies the database. For example:
 
@@ -126,7 +126,7 @@ Accept wildcard characters: False
 
 ### -StoreMailboxIdentity
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The StoreMailboxIdentity parameter specifies the mailbox that you want to quarantine when you use the Database parameter.
 
@@ -148,7 +148,7 @@ Accept wildcard characters: False
 
 ### -AllowMigration
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AllowMigration switch allows a quarantined mailbox to be moved to another mailbox database or to the cloud. You don't need to specify a value with this switch.
 
@@ -168,7 +168,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -191,7 +191,7 @@ Accept wildcard characters: False
 
 ### -Duration
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Duration parameter specifies how long the mailbox should remain quarantined. The default value is 24 hours.
 
@@ -211,7 +211,7 @@ Accept wildcard characters: False
 
 ### -QuarantineReason
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The QuarantineReason parameter specifies why you quarantined the mailbox. The maximum length is 255 characters. If the value contains spaces, enclose the value in quotation marks.
 
@@ -229,7 +229,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-MalwareFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-MalwareFilterRule.md
index c8d9f1432e..d22115dc1d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-MalwareFilterRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-MalwareFilterRule.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -45,7 +45,7 @@ This example enables the disabled malware filter rule named Contoso Recipients.
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the malware filter rule that you want to enable. You can use any value that uniquely identifies the rule. For example, you can use the name, GUID or distinguished name (DN) of the malware filter rule.
 
@@ -63,7 +63,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -84,7 +84,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -104,7 +104,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-MetaCacheDatabase.md b/exchange/exchange-ps/ExchangePowerShell/Enable-MetaCacheDatabase.md
index 860be7f17a..c313a87911 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-MetaCacheDatabase.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-MetaCacheDatabase.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2019
+applicable: Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -44,7 +44,7 @@ This example enables the metacache database on the Exchange server named Mailbox
 
 ### -Server
 
-> Applicable: Exchange Server 2019
+> Applicable: Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Mailbox server where you want to enable the metacache database. You can use any value that uniquely identifies the server. For example:
 
@@ -69,7 +69,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2019
+> Applicable: Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -90,7 +90,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2019
+> Applicable: Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-OutlookProtectionRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-OutlookProtectionRule.md
index 46b914e2ec..92310c39a2 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-OutlookProtectionRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-OutlookProtectionRule.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -49,7 +49,7 @@ This example enables the Outlook protection rule Project Contoso.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the name of the rule being enabled.
 
@@ -67,7 +67,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -88,7 +88,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -108,7 +108,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-PushNotificationProxy.md b/exchange/exchange-ps/ExchangePowerShell/Enable-PushNotificationProxy.md
index 79a0e49acc..e1737bfa73 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-PushNotificationProxy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-PushNotificationProxy.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
 Locale: en-US
@@ -56,7 +56,7 @@ This example enables the push notification proxy in the on-premises Exchange org
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -77,7 +77,7 @@ Accept wildcard characters: False
 
 ### -Organization
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Organization parameter specifies the domain name of the Microsoft 365 organization. For example, contoso.onmicrosoft.com.
 
@@ -95,7 +95,7 @@ Accept wildcard characters: False
 
 ### -Uri
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Uri parameter specifies the push notification service endpoint in Microsoft 365. The default value is <https://outlook.office365.com/PushNotifications>.
 
@@ -113,7 +113,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-RemoteMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Enable-RemoteMailbox.md
index 26f49783c0..46ead9cf77 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-RemoteMailbox.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-RemoteMailbox.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -136,7 +136,7 @@ To mail-enable an on-premises user, create the associated mailbox in the service
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the identity of the existing on-premises user. You can use any value that uniquely identifies the user. For example:
 
@@ -162,7 +162,7 @@ Accept wildcard characters: False
 
 ### -Equipment
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Equipment switch specifies that the mailbox in the service should be created as an equipment resource mailbox. You don't need to specify a value with this switch.
 
@@ -184,7 +184,7 @@ Accept wildcard characters: False
 
 ### -Room
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Room switch specifies that the mailbox in the service should be created as a room resource mailbox. You don't need to specify a value with this switch.
 
@@ -204,7 +204,7 @@ Accept wildcard characters: False
 
 ### -Shared
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 **Note**: This switch is available only in Exchange 2013 CU21 or later and Exchange 2016 CU10 or later. To use this switch, you also need to run setup.exe /PrepareAD. For more information, see [KB4133605](https://support.microsoft.com/help/4133605).
 
@@ -226,7 +226,7 @@ Accept wildcard characters: False
 
 ### -ACLableSyncedObjectEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ACLableSyncedObjectEnabled switch specifies whether the remote mailbox is an ACLableSyncedMailboxUser. You don't need to specify a value with this switch.
 
@@ -244,7 +244,7 @@ Accept wildcard characters: False
 
 ### -Alias
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Alias parameter specifies the Exchange alias (also known as the mail nickname) for the recipient. This value identifies the recipient as a mail-enabled object, and shouldn't be confused with multiple email addresses for the same recipient (also known as proxy addresses). A recipient can have only one Alias value. The maximum length is 64 characters.
 
@@ -280,7 +280,7 @@ Accept wildcard characters: False
 
 ### -Archive
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Archive switch creates an archive mailbox for an existing cloud-based user that already has a mailbox. You don't need to specify a value with this switch.
 
@@ -298,7 +298,7 @@ Accept wildcard characters: False
 
 ### -ArchiveName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ArchiveName parameter specifies the name of the archive mailbox. This is the name displayed to users in Outlook on the web (formerly known as Outlook Web App). If the value contains spaces, enclose the value in quotation marks (").
 
@@ -324,7 +324,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -345,7 +345,7 @@ Accept wildcard characters: False
 
 ### -DisplayName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DisplayName parameter specifies the display name for the mailbox that's created in the service. The display name is visible in the Exchange admin center, address lists and Outlook. The maximum length is 256 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -363,7 +363,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -381,7 +381,7 @@ Accept wildcard characters: False
 
 ### -PrimarySmtpAddress
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PrimarySmtpAddress parameter specifies the primary return email address that's used for the recipient.
 
@@ -399,7 +399,7 @@ Accept wildcard characters: False
 
 ### -RemoteRoutingAddress
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RemoteRoutingAddress parameter specifies the SMTP address of the mailbox in the service that this user is associated with.
 
@@ -417,7 +417,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-ServiceEmailChannel.md b/exchange/exchange-ps/ExchangePowerShell/Enable-ServiceEmailChannel.md
index d4a9119467..3403dbce95 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-ServiceEmailChannel.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-ServiceEmailChannel.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -61,7 +61,7 @@ This example enables the .NET service channel for the user Tony Smith.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the identity of the user for which you want to enable the .NET service channel. The user specified must be a valid user in Active Directory who has an Exchange mailbox.
 
@@ -92,7 +92,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -113,7 +113,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -131,7 +131,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-SweepRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-SweepRule.md
index da7cacb624..15e4c16b69 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-SweepRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-SweepRule.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -53,7 +53,7 @@ This example enables all Sweep rules in the specified mailbox.
 
 ### -Identity
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the Sweep rule that you want to enable. You can use any value that uniquely identifies the rule. For example:
 
@@ -75,7 +75,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -96,7 +96,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -116,7 +116,7 @@ Accept wildcard characters: False
 
 ### -Mailbox
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Mailbox parameter specifies the mailbox that contains the rule you want to enable. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -145,7 +145,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-TransportAgent.md b/exchange/exchange-ps/ExchangePowerShell/Enable-TransportAgent.md
index 3b13e5f06b..2de9a60680 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-TransportAgent.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-TransportAgent.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -46,7 +46,7 @@ This example enables a fictitious application named Test App in the Transport se
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the display name of the transport agent to be enabled. The length of the name can't exceed 64 characters.
 
@@ -64,7 +64,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -85,7 +85,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -105,7 +105,7 @@ Accept wildcard characters: False
 
 ### -TransportService
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TransportService parameter specifies the transport service that you want to view or modify. Valid values for this parameter are:
 
@@ -129,7 +129,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Enable-TransportRule.md b/exchange/exchange-ps/ExchangePowerShell/Enable-TransportRule.md
index a5df89ce00..7cda6c6bb0 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Enable-TransportRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Enable-TransportRule.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -55,7 +55,7 @@ This example enables the transport rule named "Require approval of messages to c
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the rule that you want to enable. You can use any value that uniquely identifies the rule. For example:
 
@@ -77,7 +77,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -98,7 +98,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -120,7 +120,7 @@ Accept wildcard characters: False
 
 ### -Mode
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Mode parameter specifies how the rule operates after it's enabled. Valid values are:
 
@@ -144,7 +144,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Export-ActiveSyncLog.md b/exchange/exchange-ps/ExchangePowerShell/Export-ActiveSyncLog.md
index cce74c131a..34f5758bc8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Export-ActiveSyncLog.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Export-ActiveSyncLog.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
 Locale: en-US
@@ -66,7 +66,7 @@ This example exports the Exchange ActiveSync log for the date range 02/01/18 to
 
 ### -Filename
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Filename parameter specifies the name of the input file.
 
@@ -84,7 +84,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -105,7 +105,7 @@ Accept wildcard characters: False
 
 ### -EndDate
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The EndDate parameter specifies the end date of the date range of the report.
 
@@ -123,7 +123,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -143,7 +143,7 @@ Accept wildcard characters: False
 
 ### -OutputPath
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The OutputPath parameter specifies the name and location for the output file.
 
@@ -161,7 +161,7 @@ Accept wildcard characters: False
 
 ### -OutputPrefix
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The OutputPrefix parameter specifies a prefix to append to the name of the output file.
 
@@ -179,7 +179,7 @@ Accept wildcard characters: False
 
 ### -StartDate
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The StartDate parameter specifies the start date of the date range for the report.
 
@@ -197,7 +197,7 @@ Accept wildcard characters: False
 
 ### -UseGMT
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The UseGMT switch specifies that Coordinated Universal Time (Greenwich Mean Time) is used for the time in the report output. You don't need to specify a value with this switch.
 
@@ -217,7 +217,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Export-AutoDiscoverConfig.md b/exchange/exchange-ps/ExchangePowerShell/Export-AutoDiscoverConfig.md
index c347036561..ccc78e937b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Export-AutoDiscoverConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Export-AutoDiscoverConfig.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -58,7 +58,7 @@ This example specifies that Exchange is deployed in more than one Active Directo
 
 ### -TargetForestDomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TargetForestDomainController parameter specifies the forest or domain controller that you want to export the Autodiscover configuration to.
 
@@ -78,7 +78,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -99,7 +99,7 @@ Accept wildcard characters: False
 
 ### -DeleteConfig
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DeleteConfig parameter causes the command to delete your configuration settings on the service connection point object.
 
@@ -117,7 +117,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -135,7 +135,7 @@ Accept wildcard characters: False
 
 ### -MultipleExchangeDeployments
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MultipleExchangeDeployments parameter specifies whether multiple Exchange deployments exist. Valid values are:
 
@@ -156,7 +156,7 @@ Accept wildcard characters: False
 
 ### -PreferredSourceFqdn
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PreferredSourceFqdn parameter specifies the FQDN of the Active Directory domain for the Autodiscover pointer service connection point object.
 
@@ -174,7 +174,7 @@ Accept wildcard characters: False
 
 ### -SourceForestCredential
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SourceForestCredential parameter specifies the credentials to use when connecting to the source forest.
 
@@ -194,7 +194,7 @@ Accept wildcard characters: False
 
 ### -TargetForestCredential
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TargetForestCredential parameter specifies the credentials to use to connect to the target forest.
 
@@ -214,7 +214,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Export-DlpPolicyCollection.md b/exchange/exchange-ps/ExchangePowerShell/Export-DlpPolicyCollection.md
index 63d707a6a2..9c9512e38c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Export-DlpPolicyCollection.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Export-DlpPolicyCollection.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -51,7 +51,7 @@ This example exports all the elements of the existing DLP policies to the file C
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the DLP policy you want to export. You can use any value that uniquely identifies the DLP policy. For example, you can specify the name, GUID or distinguished name (DN) of the DLP policy.
 
@@ -69,7 +69,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -90,7 +90,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -108,7 +108,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Export-ExchangeCertificate.md b/exchange/exchange-ps/ExchangePowerShell/Export-ExchangeCertificate.md
index 46aae8392f..6adbf7004e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Export-ExchangeCertificate.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Export-ExchangeCertificate.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -110,7 +110,7 @@ This example exports the same pending certificate request from Example 3. This m
 
 ### -Thumbprint
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Thumbprint parameter specifies the certificate or certificate request that you want to export. You can find the thumbprint value by using the Get-ExchangeCertificate cmdlet.
 
@@ -130,7 +130,7 @@ Accept wildcard characters: False
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the certificate or certificate request that you want to export. Valid values are:
 
@@ -157,7 +157,7 @@ Accept wildcard characters: False
 
 ### -BinaryEncoded
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The BinaryEncoded switch encodes the exported certificate or certificate request file by using Distinguished Encoding Rules (DER). You don't need to specify a value with this switch.
 
@@ -177,7 +177,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -198,7 +198,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -240,7 +240,7 @@ Accept wildcard characters: False
 
 ### -Password
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Password parameter specifies the password for the private key or chain of trust in the exported certificate file. To import the exported certificate file on another server, you need to know the password.
 
@@ -264,7 +264,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
 
@@ -291,7 +291,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Export-JournalRuleCollection.md b/exchange/exchange-ps/ExchangePowerShell/Export-JournalRuleCollection.md
index 556b223c09..d4f3c87368 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Export-JournalRuleCollection.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Export-JournalRuleCollection.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailControl-Help.xml
 Locale: en-US
@@ -59,7 +59,7 @@ In Exchange Server 2010, this example exports legacy journal rules that were cre
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the name of a journal rule.
 
@@ -77,7 +77,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -98,7 +98,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -136,7 +136,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Export-MailboxDiagnosticLogs.md b/exchange/exchange-ps/ExchangePowerShell/Export-MailboxDiagnosticLogs.md
index 98b784d811..825ccbe272 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Export-MailboxDiagnosticLogs.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Export-MailboxDiagnosticLogs.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
 Locale: en-US
@@ -73,7 +73,7 @@ This example retrieves the calendar permissions diagnostic log for the mailbox n
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies that mailbox that contains the diagnostics logs that you want to view. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -102,7 +102,7 @@ Accept wildcard characters: False
 
 ### -ComponentName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ComponentName parameter specifies the component that you want to retrieve the diagnostic logs for. Valid values depend on the type and location of the mailbox (on-premises Exchange or Exchange Online). Valid values include:
 
@@ -143,7 +143,7 @@ Accept wildcard characters: False
 
 ### -ExtendedProperties
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ExtendedProperties switch specifies whether to retrieve all of the well-known properties from the mailbox table that are useful for troubleshooting. You don't need to specify a value with this switch.
 
@@ -161,7 +161,7 @@ Accept wildcard characters: False
 
 ### -Archive
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -181,7 +181,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -202,7 +202,7 @@ Accept wildcard characters: False
 
 ### -Credential
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -224,7 +224,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -266,7 +266,7 @@ Accept wildcard characters: False
 
 ### -ReadFromDomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -290,7 +290,7 @@ Accept wildcard characters: False
 
 ### -ResultSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
 
@@ -308,7 +308,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Export-Message.md b/exchange/exchange-ps/ExchangePowerShell/Export-Message.md
index c550e5f436..4872d122c5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Export-Message.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Export-Message.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -65,7 +65,7 @@ This example retrieves all messages from the specified queue. The query results
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the message. Valid input for this parameter uses the syntax Server\\Queue\\MessageInteger or Queue\\MessageInteger or MessageInteger, for example, Mailbox01\\contoso.com\\5 or 10. For details about message identity, see [Message identity](https://learn.microsoft.com/Exchange/mail-flow/queues/queues-and-messages-in-powershell#message-identity).
 
@@ -83,7 +83,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -104,7 +104,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Export-MigrationReport.md b/exchange/exchange-ps/ExchangePowerShell/Export-MigrationReport.md
index f01bf9c014..22acb5a533 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Export-MigrationReport.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Export-MigrationReport.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -57,7 +57,7 @@ There are no examples for using this cmdlet because the values used for the requ
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is reserved for internal Microsoft use.
 
@@ -75,7 +75,7 @@ Accept wildcard characters: False
 
 ### -CsvStream
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is reserved for internal Microsoft use.
 
@@ -93,7 +93,7 @@ Accept wildcard characters: False
 
 ### -RowCount
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is reserved for internal Microsoft use.
 
@@ -111,7 +111,7 @@ Accept wildcard characters: False
 
 ### -StartingRowIndex
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is reserved for internal Microsoft use.
 
@@ -129,7 +129,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -150,7 +150,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -190,7 +190,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Export-RecipientDataProperty.md b/exchange/exchange-ps/ExchangePowerShell/Export-RecipientDataProperty.md
index f7ded90650..3ee91c7402 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Export-RecipientDataProperty.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Export-RecipientDataProperty.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -68,7 +68,7 @@ This example exports Ayla Kol's picture file to the local computer.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the mailbox or mail contact from which you want to export the recipient data. You can use any value that uniquely identifies the user. For example:
 
@@ -93,7 +93,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -114,7 +114,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -132,7 +132,7 @@ Accept wildcard characters: False
 
 ### -Picture
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Picture switch specifies that you're exporting the user's picture. You don't need to specify a value with this switch.
 
@@ -154,7 +154,7 @@ Accept wildcard characters: False
 
 ### -SpokenName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SpokenName switch specifies that you're exporting the user's spoken name. You don't need to specify a value with this switch.
 
@@ -176,7 +176,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Export-TransportRuleCollection.md b/exchange/exchange-ps/ExchangePowerShell/Export-TransportRuleCollection.md
index 733a9c53f1..2166bad553 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Export-TransportRuleCollection.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Export-TransportRuleCollection.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -66,7 +66,7 @@ You need to run these commands in this example on an Exchange 2010 Hub Transport
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter is functional only in Exchange Server 2010.
 
@@ -90,7 +90,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -111,7 +111,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -177,7 +177,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ADPermission.md b/exchange/exchange-ps/ExchangePowerShell/Get-ADPermission.md
index bb70e13cd8..a41e3a4695 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ADPermission.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ADPermission.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -62,7 +62,7 @@ This example returns the permissions that have been granted to the user Chris on
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the identity of the object for which you're retrieving permissions. You can retrieve the permissions for any Active Directory object using its distinguished name (DN). If the object is an Exchange object, you might be able to use the object's name. If the DN or the object's name contains spaces, enclose the value in quotation marks (").
 
@@ -80,7 +80,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -100,7 +100,7 @@ Accept wildcard characters: False
 
 ### -Owner
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Owner switch returns the owner of the Active Directory object. You don't need to specify a value with this switch.
 
@@ -120,7 +120,7 @@ Accept wildcard characters: False
 
 ### -User
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The user parameter filters the results who has permissions on the Active Directory object. You can specify the following types of users or groups (security principals) for this parameter:
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ADServerSettings.md b/exchange/exchange-ps/ExchangePowerShell/Get-ADServerSettings.md
index d34e36afaa..d986ca399b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ADServerSettings.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ADServerSettings.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ADSite.md b/exchange/exchange-ps/ExchangePowerShell/Get-ADSite.md
index 6849e8bdc0..cf5940515c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ADSite.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ADSite.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -45,7 +45,7 @@ This example displays the configuration details for the Active Directory site na
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the identity of the Active Directory site for which you want to view configuration details. The identity can be expressed as a GUID or the Active Directory site name. If the Active Directory site name includes spaces, enclose the name in quotation marks (").
 
@@ -63,7 +63,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AcceptedDomain.md b/exchange/exchange-ps/ExchangePowerShell/Get-AcceptedDomain.md
index 7748fcd4fb..f8e9f88d86 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AcceptedDomain.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-AcceptedDomain.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -51,7 +51,7 @@ This example lists all the authoritative accepted domains in your organization.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies a string value for the accepted domain. Enter either the GUID or the name of the accepted domain.
 
@@ -69,7 +69,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDevice.md b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDevice.md
index 38fa08786f..e1b5977672 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDevice.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDevice.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
 Locale: en-US
@@ -79,7 +79,7 @@ This example returns the owner names of all Outlook Mobile apps that synch via H
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the ActiveSync device that you want to view. You can use any value that uniquely identifies the device. For example:
 
@@ -101,7 +101,7 @@ Accept wildcard characters: False
 
 ### -Mailbox
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Mailbox parameter specifies the mailbox that has the associated ActiveSync device that you want to view. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -130,7 +130,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -150,7 +150,7 @@ Accept wildcard characters: False
 
 ### -Filter
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Filter parameter uses OPATH syntax to filter the results by the specified properties and values. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`.
 
@@ -198,7 +198,7 @@ Accept wildcard characters: False
 
 ### -Monitoring
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -220,7 +220,7 @@ Accept wildcard characters: False
 
 ### -OrganizationalUnit
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The OrganizationalUnit parameter filters the results based on the object's location in Active Directory. Only objects that exist in the specified location are returned. Valid input for this parameter is an organizational unit (OU) or domain that's returned by the Get-OrganizationalUnit cmdlet. You can use any value that uniquely identifies the OU or domain. For example:
 
@@ -243,7 +243,7 @@ Accept wildcard characters: False
 
 ### -ResultSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
 
@@ -261,7 +261,7 @@ Accept wildcard characters: False
 
 ### -SortBy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SortBy parameter specifies the property to sort the results by. You can sort by only one property at a time. The results are sorted in ascending order.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceAccessRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceAccessRule.md
index 969dff3485..0015a845a2 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceAccessRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceAccessRule.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
 Locale: en-US
@@ -52,7 +52,7 @@ This example lists all device access rules set up on the server.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the unique identifier for the device access rule.
 
@@ -70,7 +70,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceAutoblockThreshold.md b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceAutoblockThreshold.md
index 3eae2e954e..05910263be 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceAutoblockThreshold.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceAutoblockThreshold.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
 Locale: en-US
@@ -45,7 +45,7 @@ This example retrieves the threshold settings for the Autoblock threshold rule f
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the name of the Autoblock threshold rule.
 
@@ -63,7 +63,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceClass.md b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceClass.md
index 136f9d646d..3759a942e5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceClass.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceClass.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
 Locale: en-US
@@ -54,7 +54,7 @@ This example lists all device types within the organization along with a count o
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the ActiveSync device class that you want to view. You can use any value that uniquely identifies the ActiveSync device class. For example:
 
@@ -76,7 +76,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -96,7 +96,7 @@ Accept wildcard characters: False
 
 ### -Filter
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Filter parameter uses OPATH syntax to filter the results by the specified properties and values. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`.
 
@@ -129,7 +129,7 @@ Accept wildcard characters: False
 
 ### -SortBy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SortBy parameter specifies the property to sort the results by. You can sort by only one property at a time. The results are sorted in ascending order.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceStatistics.md
index 08446a5d56..d5c0c86cbd 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceStatistics.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncDeviceStatistics.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
 Locale: en-US
@@ -79,7 +79,7 @@ This example retrieves the statistics for the mobile phone configured to synchro
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the user's device ID. If the Mailbox parameter is specified, the Identity parameter is disabled.
 
@@ -97,7 +97,7 @@ Accept wildcard characters: False
 
 ### -Mailbox
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Mailbox parameter specifies the user mailbox for which you want to retrieve the mobile phone statistics. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -126,7 +126,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -146,7 +146,7 @@ Accept wildcard characters: False
 
 ### -GetMailboxLog
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The GetMailboxLog switch specifies whether to send the mobile device statistics to the email addresses that are specified by the NotificationEmailAddresses parameter. You don't need to specify a value with this switch.
 
@@ -164,7 +164,7 @@ Accept wildcard characters: False
 
 ### -NotificationEmailAddresses
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The NotificationEmailAddresses parameter specifies a comma-separated list of email addresses to receive the mobile device statistics when you use the GetMailboxLog switch.
 
@@ -184,7 +184,7 @@ Accept wildcard characters: False
 
 ### -ShowRecoveryPassword
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ShowRecoveryPassword parameter specifies whether to return the recovery password for the mobile phone as one of the displayed statistics. If this parameter is set to $true, the command returns the recovery password for the mobile phone as one of the displayed statistics.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncMailboxPolicy.md
index daa6a942b5..f77182f9be 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncMailboxPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncMailboxPolicy.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
 Locale: en-US
@@ -61,7 +61,7 @@ This example returns the policy settings for the Mobile Device mailbox policy na
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the policy name.
 
@@ -79,7 +79,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncOrganizationSettings.md b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncOrganizationSettings.md
index a8b91cba75..c0fca3521c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncOrganizationSettings.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncOrganizationSettings.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
 Locale: en-US
@@ -43,7 +43,7 @@ This example retrieves the ActiveSync organization settings.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the ActiveSync organization settings object that you want to view. The default name of this object is Mobile Mailbox Settings.
 
@@ -61,7 +61,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncVirtualDirectory.md
index a5ff61bfa0..789f2035f0 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncVirtualDirectory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ActiveSyncVirtualDirectory.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
 Locale: en-US
@@ -71,7 +71,7 @@ This example returns a summary list of all Exchange ActiveSync virtual directori
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the ActiveSync virtual directory that you want to view. You can use any value that uniquely identifies the virtual directory. For example:
 
@@ -97,7 +97,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Exchange server that hosts the virtual directory. You can use any value that uniquely identifies the server. For example:
 
@@ -122,7 +122,7 @@ Accept wildcard characters: False
 
 ### -ADPropertiesOnly
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ADPropertiesOnly switch specifies whether to return only the virtual directory properties that are stored in Active Directory. You don't need to specify a value with this switch.
 
@@ -142,7 +142,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -160,7 +160,7 @@ Accept wildcard characters: False
 
 ### -ShowMailboxVirtualDirectories
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ShowMailboxVirtualDirectories switch shows information about backend virtual directories on Mailbox servers. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AddressBookPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-AddressBookPolicy.md
index 14bcfbf882..0b2ce64377 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AddressBookPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-AddressBookPolicy.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -59,7 +59,7 @@ This example returns information about all address book policies for which the o
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the identity of the address book policy.
 
@@ -77,7 +77,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AddressList.md b/exchange/exchange-ps/ExchangePowerShell/Get-AddressList.md
index 16fd763848..dda29c302b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AddressList.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-AddressList.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -69,7 +69,7 @@ This example returns detailed information for the address list named building4th
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the address list that you want to view. You can use any value that uniquely identifies the address list. For example:
 
@@ -94,7 +94,7 @@ Accept wildcard characters: False
 
 ### -Container
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Container parameter filters the results based on the location of the address list. Only address lists under the specified path are returned. Valid input for this parameter is the root "\\" (also known as All Address Lists) or an existing address list. You can use any value that uniquely identifies the address list. For example:
 
@@ -119,7 +119,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -139,7 +139,7 @@ Accept wildcard characters: False
 
 ### -SearchText
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SearchText parameter filters the results based on the name and display name of the address list. Only address lists whose names or display names that contain the specified text string are returned. If the value contains spaces, enclose the value in quotation marks (").
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AddressRewriteEntry.md b/exchange/exchange-ps/ExchangePowerShell/Get-AddressRewriteEntry.md
index c4273ec8f9..0112ac6ebb 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AddressRewriteEntry.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-AddressRewriteEntry.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
 Locale: en-US
@@ -50,7 +50,7 @@ This example returns the detailed configuration of a single address rewrite entr
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the address rewrite entry to be retrieved. The Identity parameter accepts a GUID or the unique address rewrite name. You can omit the Identity parameter label.
 
@@ -68,7 +68,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AdminAuditLogConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-AdminAuditLogConfig.md
index 975a94075f..915760fcaa 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AdminAuditLogConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-AdminAuditLogConfig.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
 Locale: en-US
@@ -47,7 +47,7 @@ This example displays the administrator audit logging settings. The output of th
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AdministrativeUnit.md b/exchange/exchange-ps/ExchangePowerShell/Get-AdministrativeUnit.md
index 9a605c829e..3f34d4e2c3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AdministrativeUnit.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-AdministrativeUnit.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -54,7 +54,7 @@ This example returns detailed information about the administrative unit with the
 
 ### -Identity
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the administrative unit that you want to view. You can use any value that uniquely identifies the administrative unit. For example:
 
@@ -78,7 +78,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -99,7 +99,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -119,7 +119,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 

From 4f4b79d3ff4f34ca5c4dc5518d955225d4498e5b Mon Sep 17 00:00:00 2001
From: Chris Davis <chris.davis@microsoft.com>
Date: Thu, 7 Aug 2025 08:18:01 -0700
Subject: [PATCH 129/145] Add Exchange Server SE 2

---
 .../ExchangePowerShell/Get-ADSiteLink.md      |  6 +--
 .../ExchangePowerShell/Get-AgentLog.md        | 10 ++--
 .../exchange-ps/ExchangePowerShell/Get-App.md | 12 ++---
 .../Get-AttachmentFilterEntry.md              |  6 +--
 .../Get-AttachmentFilterListConfig.md         |  4 +-
 .../ExchangePowerShell/Get-AuditLogSearch.md  | 12 ++---
 .../ExchangePowerShell/Get-AuthConfig.md      |  4 +-
 .../ExchangePowerShell/Get-AuthRedirect.md    |  6 +--
 .../ExchangePowerShell/Get-AuthServer.md      |  6 +--
 .../Get-AuthenticationPolicy.md               |  4 +-
 .../Get-AutodiscoverVirtualDirectory.md       | 12 ++---
 .../Get-AvailabilityAddressSpace.md           |  6 +--
 .../Get-AvailabilityConfig.md                 |  6 +--
 .../ExchangePowerShell/Get-CASMailbox.md      | 34 ++++++-------
 .../ExchangePowerShell/Get-CASMailboxPlan.md  | 12 ++---
 .../Get-CalendarDiagnosticAnalysis.md         | 10 ++--
 .../Get-CalendarDiagnosticLog.md              | 30 ++++++------
 .../Get-CalendarNotification.md               | 12 ++---
 .../Get-CalendarProcessing.md                 | 10 ++--
 .../Get-ClassificationRuleCollection.md       |  6 +--
 .../Get-ClientAccessArray.md                  |  8 ++--
 .../Get-ClientAccessRule.md                   | 10 ++--
 .../Get-ClientAccessServer.md                 | 10 ++--
 .../Get-ClientAccessService.md                | 10 ++--
 .../Get-CmdletExtensionAgent.md               | 10 ++--
 .../Get-ComplianceSearch.md                   |  8 ++--
 .../Get-ComplianceSearchAction.md             | 18 +++----
 .../Get-ComplianceSecurityFilter.md           | 12 ++---
 .../ExchangePowerShell/Get-Contact.md         | 24 +++++-----
 .../Get-ContentFilterConfig.md                |  4 +-
 .../Get-ContentFilterPhrase.md                |  8 ++--
 .../Get-DataClassification.md                 |  8 ++--
 .../Get-DatabaseAvailabilityGroup.md          |  8 ++--
 .../Get-DatabaseAvailabilityGroupNetwork.md   |  8 ++--
 .../Get-DeliveryAgentConnector.md             |  6 +--
 .../ExchangePowerShell/Get-DetailsTemplate.md | 10 ++--
 .../Get-DistributionGroup.md                  | 26 +++++-----
 .../Get-DistributionGroupMember.md            | 14 +++---
 .../ExchangePowerShell/Get-DlpPolicy.md       |  6 +--
 .../Get-DlpPolicyTemplate.md                  |  6 +--
 .../Get-DomainController.md                   | 10 ++--
 .../Get-DynamicDistributionGroup.md           | 26 +++++-----
 .../Get-EcpVirtualDirectory.md                | 12 ++---
 .../Get-EdgeSubscription.md                   |  6 +--
 .../Get-EdgeSyncServiceConfig.md              |  8 ++--
 ...t-EligibleDistributionGroupForMigration.md | 10 ++--
 .../Get-EmailAddressPolicy.md                 |  8 ++--
 .../ExchangePowerShell/Get-EventLogLevel.md   |  8 ++--
 .../Get-ExchangeAssistanceConfig.md           |  6 +--
 .../Get-ExchangeCertificate.md                | 14 +++---
 .../Get-ExchangeDiagnosticInfo.md             | 12 ++---
 .../ExchangePowerShell/Get-ExchangeFeature.md | 10 ++--
 .../ExchangePowerShell/Get-ExchangeServer.md  | 10 ++--
 .../Get-ExchangeServerAccessLicense.md        |  2 +-
 .../Get-ExchangeServerAccessLicenseUser.md    |  4 +-
 .../Get-ExchangeSettings.md                   | 30 ++++++------
 .../Get-FailedContentIndexDocuments.md        | 26 +++++-----
 .../Get-FederatedDomainProof.md               |  8 ++--
 .../Get-FederatedOrganizationIdentifier.md    |  8 ++--
 .../Get-FederationInformation.md              | 10 ++--
 .../ExchangePowerShell/Get-FederationTrust.md |  6 +--
 .../Get-ForeignConnector.md                   |  6 +--
 .../Get-FrontendTransportService.md           |  6 +--
 .../Get-GlobalAddressList.md                  |  8 ++--
 .../Get-GlobalMonitoringOverride.md           |  4 +-
 .../ExchangePowerShell/Get-Group.md           | 24 +++++-----
 .../ExchangePowerShell/Get-HealthReport.md    | 14 +++---
 .../Get-HostedContentFilterRule.md            |  8 ++--
 .../Get-HybridConfiguration.md                |  4 +-
 .../Get-IPAllowListConfig.md                  |  4 +-
 .../Get-IPAllowListEntry.md                   | 10 ++--
 .../Get-IPAllowListProvider.md                |  6 +--
 .../Get-IPAllowListProvidersConfig.md         |  4 +-
 .../Get-IPBlockListConfig.md                  |  4 +-
 .../Get-IPBlockListEntry.md                   | 10 ++--
 .../Get-IPBlockListProvider.md                |  6 +--
 .../Get-IPBlockListProvidersConfig.md         |  4 +-
 .../Get-IRMConfiguration.md                   |  4 +-
 .../ExchangePowerShell/Get-ImapSettings.md    |  6 +--
 .../ExchangePowerShell/Get-InboxRule.md       | 18 +++----
 .../Get-IntraOrganizationConfiguration.md     |  2 +-
 .../Get-IntraOrganizationConnector.md         |  6 +--
 .../ExchangePowerShell/Get-JournalRule.md     |  6 +--
 .../ExchangePowerShell/Get-LogonStatistics.md | 10 ++--
 .../ExchangePowerShell/Get-Mailbox.md         | 48 +++++++++----------
 .../Get-MailboxAuditBypassAssociation.md      |  8 ++--
 .../Get-MailboxAutoReplyConfiguration.md      | 12 ++---
 .../Get-MailboxCalendarConfiguration.md       |  6 +--
 .../Get-MailboxCalendarFolder.md              |  6 +--
 .../ExchangePowerShell/Get-MailboxDatabase.md | 16 +++----
 .../Get-MailboxDatabaseCopyStatus.md          | 18 +++----
 .../Get-MailboxExportRequest.md               | 20 ++++----
 .../Get-MailboxExportRequestStatistics.md     | 18 +++----
 .../ExchangePowerShell/Get-MailboxFolder.md   | 14 +++---
 .../Get-MailboxFolderPermission.md            | 10 ++--
 .../Get-MailboxFolderStatistics.md            | 16 +++----
 .../Get-MailboxImportRequest.md               | 20 ++++----
 97 files changed, 521 insertions(+), 521 deletions(-)

diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ADSiteLink.md b/exchange/exchange-ps/ExchangePowerShell/Get-ADSiteLink.md
index cc1b89a208..b2dc772e31 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ADSiteLink.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ADSiteLink.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -50,7 +50,7 @@ This example returns a list of all IP site links in your organization that have
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the name or GUID of the IP site link for which you want to view configuration information.
 
@@ -68,7 +68,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AgentLog.md b/exchange/exchange-ps/ExchangePowerShell/Get-AgentLog.md
index 5c34512eea..97f37bc9e7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AgentLog.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-AgentLog.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -45,7 +45,7 @@ This example returns a report that has statistics collected between 09:00 (9 A.M
 
 ### -EndDate
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The EndDate parameter specifies the end date of the date range.
 
@@ -65,7 +65,7 @@ Accept wildcard characters: False
 
 ### -Location
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Location parameter specifies the directory that contains the log files that you can use to build usage reports. The default path is %ExchangeInstallPath%TransportRoles\\Logs\\AgentLog. You need to enclose the file path in quotation marks (").
 
@@ -83,7 +83,7 @@ Accept wildcard characters: False
 
 ### -StartDate
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The StartDate parameter specifies the start date of the date range.
 
@@ -103,7 +103,7 @@ Accept wildcard characters: False
 
 ### -TransportService
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TransportService parameter specifies the transport service that you want to view or modify. Valid values for this parameter are:
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-App.md b/exchange/exchange-ps/ExchangePowerShell/Get-App.md
index 4dfc80bbfd..6fcb3f8850 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-App.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-App.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.WebClient-Help.xml
 Locale: en-US
@@ -62,7 +62,7 @@ This example displays the summary list of apps installed by administrators for t
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the GUID of the app that you want to view. To find the GUID value of an app, run the command Get-App | Format-Table -Auto DisplayName,AppId.
 
@@ -80,7 +80,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -100,7 +100,7 @@ Accept wildcard characters: False
 
 ### -Mailbox
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Mailbox parameter specifies the identity of the mailbox where the apps are installed. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -133,7 +133,7 @@ Accept wildcard characters: False
 
 ### -OrganizationApp
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The OrganizationApp switch includes apps that are installed for the organization (not bound to a specific user) in the results. You don't need to specify a value with this switch.
 
@@ -151,7 +151,7 @@ Accept wildcard characters: False
 
 ### -PrivateCatalog
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The PrivateCatalog switch includes private catalog add-ins in the results. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AttachmentFilterEntry.md b/exchange/exchange-ps/ExchangePowerShell/Get-AttachmentFilterEntry.md
index eef7c64274..646a49659f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AttachmentFilterEntry.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-AttachmentFilterEntry.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
 Locale: en-US
@@ -59,7 +59,7 @@ This example returns only the attachment filter entries that filter attachments
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies which attachment filter entry the command retrieves. The Identity parameter accepts values in the format Type:Name, where Type is one of the following values:
 
@@ -80,7 +80,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AttachmentFilterListConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-AttachmentFilterListConfig.md
index f58a7b6e34..66ab27f224 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AttachmentFilterListConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-AttachmentFilterListConfig.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
 Locale: en-US
@@ -44,7 +44,7 @@ This example returns detailed information about the Attachment Filtering agent c
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AuditLogSearch.md b/exchange/exchange-ps/ExchangePowerShell/Get-AuditLogSearch.md
index 1074a5cee0..2045a18d7e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AuditLogSearch.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-AuditLogSearch.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
 Locale: en-US
@@ -55,7 +55,7 @@ This example returns a list of current administrator audit log searches.
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the GUID for an audit log search. You can run the command Get-AuditLogSearch | Format-List Identity to display the GUIDs for all current audit log searches.
 
@@ -73,7 +73,7 @@ Accept wildcard characters: False
 
 ### -CreatedAfter
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The CreatedAfter parameter filters the results to audit log searches that were created after the specified date.
 
@@ -93,7 +93,7 @@ Accept wildcard characters: False
 
 ### -CreatedBefore
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The CreatedBefore parameter filters the results to audit log searches that were created before the specified date.
 
@@ -113,7 +113,7 @@ Accept wildcard characters: False
 
 ### -ResultSize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
 
@@ -131,7 +131,7 @@ Accept wildcard characters: False
 
 ### -Type
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Type parameter specifies the type of audit log searches to return. Use the value Admin to return administrator audit log searches or use mailbox to return mailbox audit log searches. If the Type parameter isn't used, the cmdlet returns both administrator and mailbox audit log searches.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AuthConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-AuthConfig.md
index 9f1e7d1fa9..7bdab82ee5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AuthConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-AuthConfig.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -42,7 +42,7 @@ This example retrieves the authorization configuration for the Exchange organiza
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AuthRedirect.md b/exchange/exchange-ps/ExchangePowerShell/Get-AuthRedirect.md
index 2fd82357b2..657835080e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AuthRedirect.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-AuthRedirect.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -52,7 +52,7 @@ This example shows detailed information about the OAuth redirection object named
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the existing OAuth redirection object that you want to view. The object name uses the syntax `AuthRedirect-Bearer-GUID`.
 
@@ -70,7 +70,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AuthServer.md b/exchange/exchange-ps/ExchangePowerShell/Get-AuthServer.md
index 18a995e5e5..a92ebaca89 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AuthServer.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-AuthServer.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -52,7 +52,7 @@ This example retrieves detailed information for the authorization server named W
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the authorization server object that you want to view. You can use any value that uniquely identifies the authorization server. For example:
 
@@ -74,7 +74,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AuthenticationPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-AuthenticationPolicy.md
index 0cc8f2ce52..67391dcc72 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AuthenticationPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-AuthenticationPolicy.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -57,7 +57,7 @@ In Exchange Online, this example specifies whether legacy Exchange tokens for Ou
 
 ### -Identity
 
-> Applicable: Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the authentication policy you want to view. You can use any value that uniquely identifies the policy. For example:
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AutodiscoverVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Get-AutodiscoverVirtualDirectory.md
index 9427b28c13..d247dcbc5e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AutodiscoverVirtualDirectory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-AutodiscoverVirtualDirectory.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -69,7 +69,7 @@ This example returns a summary list of all Autodiscover virtual directories in t
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the Autodiscover virtual directory that you want to view. You can use any value that uniquely identifies the virtual directory. For example:
 
@@ -95,7 +95,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Exchange server that hosts the virtual directory. You can use any value that uniquely identifies the server. For example:
 
@@ -120,7 +120,7 @@ Accept wildcard characters: False
 
 ### -ADPropertiesOnly
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ADPropertiesOnly switch specifies whether to return only the virtual directory properties that are stored in Active Directory. You don't need to specify a value with this switch.
 
@@ -140,7 +140,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -158,7 +158,7 @@ Accept wildcard characters: False
 
 ### -ShowMailboxVirtualDirectories
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ShowMailboxVirtualDirectories switch shows information about backend virtual directories on Mailbox servers. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AvailabilityAddressSpace.md b/exchange/exchange-ps/ExchangePowerShell/Get-AvailabilityAddressSpace.md
index dd98d48602..5b91b6e32b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AvailabilityAddressSpace.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-AvailabilityAddressSpace.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
 Locale: en-US
@@ -52,7 +52,7 @@ This example returns details information for the availability address space obje
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the availability address space that you want to view. You can use any value that uniquely identifies the object. For example:
 
@@ -74,7 +74,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AvailabilityConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-AvailabilityConfig.md
index 41769cda65..7a7ef25ed3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-AvailabilityConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-AvailabilityConfig.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
 Locale: en-US
@@ -48,7 +48,7 @@ In Exchange Online, this examples returns the tenant IDs that free/busy informat
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the availability configuration that you want to view. You don't need to use this parameter, because there's only one availability configuration object named Availability Configuration in any organization.
 
@@ -66,7 +66,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-CASMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Get-CASMailbox.md
index 01bae9325f..a7e139117d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-CASMailbox.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-CASMailbox.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.WebClient-Help.xml
 Locale: en-US
@@ -108,7 +108,7 @@ In Exchange Online, this example filters the cmdlet output to only include share
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the mailbox that you want to view. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -137,7 +137,7 @@ Accept wildcard characters: False
 
 ### -ActiveSyncDebugLogging
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ActiveSyncDebugLogging switch shows the actual value of the ActiveSyncDebugLogging property for the mailbox. You don't need to specify a value with this switch.
 
@@ -159,7 +159,7 @@ Accept wildcard characters: False
 
 ### -ActiveSyncSuppressReadReceipt
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is reserved for internal Microsoft use.
 
@@ -177,7 +177,7 @@ Accept wildcard characters: False
 
 ### -Anr
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Anr parameter specifies a string on which to perform an ambiguous name resolution (ANR) search. You can specify a partial string and search for objects with an attribute that matches that string. The default attributes searched are:
 
@@ -201,7 +201,7 @@ Accept wildcard characters: False
 
 ### -Credential
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Credential parameter specifies the username and password that's used to run this command. Typically, you use this parameter in scripts or when you need to provide different credentials that have the required permissions.
 
@@ -221,7 +221,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -241,7 +241,7 @@ Accept wildcard characters: False
 
 ### -Filter
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Filter parameter uses OPATH syntax to filter the results by the specified properties and values. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`.
 
@@ -268,7 +268,7 @@ Accept wildcard characters: False
 
 ### -IgnoreDefaultScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange PowerShell session, and to use the entire forest as the scope. You don't need to specify a value with this switch.
 
@@ -291,7 +291,7 @@ Accept wildcard characters: False
 
 ### -Monitoring
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -313,7 +313,7 @@ Accept wildcard characters: False
 
 ### -OrganizationalUnit
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The OrganizationalUnit parameter filters the results based on the object's location in Active Directory. Only objects that exist in the specified location are returned. Valid input for this parameter is an organizational unit (OU) or domain that's returned by the Get-OrganizationalUnit cmdlet. You can use any value that uniquely identifies the OU or domain. For example:
 
@@ -336,7 +336,7 @@ Accept wildcard characters: False
 
 ### -ProtocolSettings
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ProtocolSettings switch returns the server names, TCP ports and encryption methods for the following settings:
 
@@ -365,7 +365,7 @@ Accept wildcard characters: False
 
 ### -ReadFromDomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -389,7 +389,7 @@ Accept wildcard characters: False
 
 ### -ReadIsOptimizedForAccessibility
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ReadIsOptimizedForAccessibility switch specifies whether to read the value of the IsOptimizedForAccessibility property on the mailbox (whether the mailbox is configured to use the light version of Outlook on the web). You don't need to specify a value with this switch.
 
@@ -407,7 +407,7 @@ Accept wildcard characters: False
 
 ### -RecalculateHasActiveSyncDevicePartnership
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RecalculateHasActiveSyncDevicePartnership switch recalculates the value of the HasActiveSyncDevicePartnership property on the mailbox. You don't need to specify a value with this switch.
 
@@ -460,7 +460,7 @@ Accept wildcard characters: False
 
 ### -ResultSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
 
@@ -478,7 +478,7 @@ Accept wildcard characters: False
 
 ### -SortBy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SortBy parameter specifies the property to sort the results by. You can sort by only one property at a time. The results are sorted in ascending order.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-CASMailboxPlan.md b/exchange/exchange-ps/ExchangePowerShell/Get-CASMailboxPlan.md
index b18ba0fbd9..6f009eb993 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-CASMailboxPlan.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-CASMailboxPlan.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -57,7 +57,7 @@ This example returns detailed information about the specified CAS mailbox plan.
 
 ### -Identity
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the CAS mailbox plan that you want to view. You can use any value that uniquely identifies the CAS mailbox plan. For example:
 
@@ -101,7 +101,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -119,7 +119,7 @@ Accept wildcard characters: False
 
 ### -Filter
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Filter parameter uses OPATH syntax to filter the results by the specified properties and values. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`.
 
@@ -166,7 +166,7 @@ Accept wildcard characters: False
 
 ### -ResultSize
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
 
@@ -184,7 +184,7 @@ Accept wildcard characters: False
 
 ### -SortBy
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SortBy parameter specifies the property to sort the results by. You can sort by only one property at a time. The results are sorted in ascending order.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-CalendarDiagnosticAnalysis.md b/exchange/exchange-ps/ExchangePowerShell/Get-CalendarDiagnosticAnalysis.md
index 254a8bc41d..0d4e77967b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-CalendarDiagnosticAnalysis.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-CalendarDiagnosticAnalysis.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
 Locale: en-US
@@ -101,7 +101,7 @@ For basic analysis of the items, don't include the DetailLevel parameter, or use
 
 ### -CalendarLogs
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The CalendarLogs parameter specifies the calendar item that you want to analyze. You identify the calendar item by storing the output of the Get-CalendarDiagnosticLog cmdlet to a variable and using that variable for the value of this parameter.
 
@@ -151,7 +151,7 @@ Accept wildcard characters: False
 
 ### -DetailLevel
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DetailLevel parameter specifies the level of detail you want to see in the analysis output. Valid values are:
 
@@ -172,7 +172,7 @@ Accept wildcard characters: False
 
 ### -GlobalObjectId
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The GlobalObjectId parameter specifies the identity of the calendar item you want to analyze. In Exchange 2013, you can use this parameter with the LogLocation parameter to specify the calendar item if the location contains multiple exported .msg files.
 
@@ -192,7 +192,7 @@ Accept wildcard characters: False
 
 ### -OutputAs
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The OutputAs parameter specifies the output format of the command. Valid values are:
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-CalendarDiagnosticLog.md b/exchange/exchange-ps/ExchangePowerShell/Get-CalendarDiagnosticLog.md
index 381a1fe665..59170cb682 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-CalendarDiagnosticLog.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-CalendarDiagnosticLog.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
 Locale: en-US
@@ -115,7 +115,7 @@ In **Exchange 2013**, this example exports all calendar items in the Calendar Di
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the mailbox that contains the calendar items. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -172,7 +172,7 @@ Accept wildcard characters: False
 
 ### -MeetingID
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MeetingID parameter filters the results by the globally unique identifier of the calendar item. The value is the CleanGlobalObjectId property of the calendar item that's available in the output of this cmdlet, or by using other MAPI examination tools. An example value is 040000008200E00074C5B7101A82E00800000000B0225ABF0710C80100000000000000001000000005B27C05AA7C4646B0835D5EB4E41C55. This value is constant throughout the lifetime of the calendar item.
 
@@ -194,7 +194,7 @@ Accept wildcard characters: False
 
 ### -Subject
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Subject parameter identifies the calendar items by the specified text in the Subject field. The text values that you specify aren't case sensitive. If the value contains spaces, enclose the value in quotation marks ("). You can control whether to use exact matching by using the ExactMatch parameter.
 
@@ -214,7 +214,7 @@ Accept wildcard characters: False
 
 ### -Credential
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -236,7 +236,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -256,7 +256,7 @@ Accept wildcard characters: False
 
 ### -EndDate
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The EndDate parameter specifies the end date of the date range.
 
@@ -276,7 +276,7 @@ Accept wildcard characters: False
 
 ### -EntryId
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The EntryId parameter filters the results by entry ID. You can specify multiple values separated by commas.
 
@@ -294,7 +294,7 @@ Accept wildcard characters: False
 
 ### -ExactMatch
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ExactMatch parameter specifies whether to use an exact match or a partial match for text values that you specify for the Subject parameter. Valid values are:
 
@@ -321,7 +321,7 @@ Accept wildcard characters: False
 
 ### -ItemClass
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ItemClass parameter filters the results by the specified MessageClass property value of the calendar item (for example, IPM.Appointment). You can specify multiple values separated by commas.
 
@@ -341,7 +341,7 @@ Accept wildcard characters: False
 
 ### -ItemIds
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ItemIds parameter filters the results by item ID. You can specify multiple values separated by commas.
 
@@ -359,7 +359,7 @@ Accept wildcard characters: False
 
 ### -Latest
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Latest switch specifies whether to return calendar log data for only the most recent calendar item. You don't need to specify a value with this switch.
 
@@ -377,7 +377,7 @@ Accept wildcard characters: False
 
 ### -ReadFromDomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -401,7 +401,7 @@ Accept wildcard characters: False
 
 ### -ResultSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter determines the number of results returned by the cmdlet. The maximum value is 1000.
 
@@ -419,7 +419,7 @@ Accept wildcard characters: False
 
 ### -StartDate
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The StartDate parameter specifies the start date of the date range.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-CalendarNotification.md b/exchange/exchange-ps/ExchangePowerShell/Get-CalendarNotification.md
index 8805d48276..908c4eb1f9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-CalendarNotification.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-CalendarNotification.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.WebClient-Help.xml
 Locale: en-US
@@ -50,7 +50,7 @@ This example returns the calendar text message notification settings for Tony's
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the mailbox that you want to view. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -79,7 +79,7 @@ Accept wildcard characters: False
 
 ### -Credential
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Credential parameter specifies the username and password that's used to run this command. Typically, you use this parameter in scripts or when you need to provide different credentials that have the required permissions.
 
@@ -99,7 +99,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -117,7 +117,7 @@ Accept wildcard characters: False
 
 ### -ReadFromDomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ReadFromDomainController switch specifies that information should be read from a domain controller in the user's domain. You don't need to specify a value with this switch.
 
@@ -139,7 +139,7 @@ Accept wildcard characters: False
 
 ### -ResultSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-CalendarProcessing.md b/exchange/exchange-ps/ExchangePowerShell/Get-CalendarProcessing.md
index 7e0d1c3a47..72c4b9ede9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-CalendarProcessing.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-CalendarProcessing.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
 Locale: en-US
@@ -47,7 +47,7 @@ This example shows the calendar processing options for the resource mailbox Room
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the resource mailbox that you want to view. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -76,7 +76,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -96,7 +96,7 @@ Accept wildcard characters: False
 
 ### -ReadFromDomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -120,7 +120,7 @@ Accept wildcard characters: False
 
 ### -ResultSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ClassificationRuleCollection.md b/exchange/exchange-ps/ExchangePowerShell/Get-ClassificationRuleCollection.md
index d193a9e80d..f4eaa39c92 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ClassificationRuleCollection.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ClassificationRuleCollection.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -52,7 +52,7 @@ This example returns detailed information about the classification rule collecti
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the classification rule collection you want to view. You can use any value that uniquely identifies the classification rule collection. For example, you can specify the name, rule collection name or distinguished name (DN) of the classification rule collection.
 
@@ -70,7 +70,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessArray.md b/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessArray.md
index 8bc2e48ab3..1b1d7b33b3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessArray.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessArray.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -58,7 +58,7 @@ This example returns detailed information for the Client Access array named CASA
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the Client Access array that you want to view. You can use these values:
 
@@ -82,7 +82,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -100,7 +100,7 @@ Accept wildcard characters: False
 
 ### -Site
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Site parameter filters the results by Active Directory site. You can use any value that uniquely identifies the site. For example:
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessRule.md
index 256fd14a48..954e243ebd 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessRule.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.WebClient-Help.xml
 Locale: en-US
@@ -57,7 +57,7 @@ This example retrieves details about the client access rule named "Block Client
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the client access rule that you want to view. You can use any value that uniquely identifies the client access rule. For example:
 
@@ -79,7 +79,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -100,7 +100,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter is functional only in on-premises Exchange.
 
@@ -120,7 +120,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessServer.md b/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessServer.md
index 09650e1a71..3feb15fdc8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessServer.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessServer.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.WebClient-Help.xml
 Locale: en-US
@@ -54,7 +54,7 @@ This example returns detailed information for the server mail.contoso.com.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the server with the Client Access server role installed that you want to view.
 
@@ -79,7 +79,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -97,7 +97,7 @@ Accept wildcard characters: False
 
 ### -IncludeAlternateServiceAccountCredentialPassword
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IncludeAlternateServiceAccountCredentialPassword switch specifies whether to include the password of the alternate service account in the results. You don't need to specify a value with this switch.
 
@@ -117,7 +117,7 @@ Accept wildcard characters: False
 
 ### -IncludeAlternateServiceAccountCredentialStatus
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IncludeAlternateServiceAccountCredentialStatus parameter specifies whether to include the status of the alternate service account in the results. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessService.md b/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessService.md
index 0bc4dd10e3..9045c8e052 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessService.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessService.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.WebClient-Help.xml
 Locale: en-US
@@ -52,7 +52,7 @@ This example returns detailed information for the server mail.contoso.com.
 
 ### -Identity
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the server with the Client Access server role installed that you want to view.
 
@@ -77,7 +77,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -95,7 +95,7 @@ Accept wildcard characters: False
 
 ### -IncludeAlternateServiceAccountCredentialPassword
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IncludeAlternateServiceAccountCredentialPassword switch specifies whether to include the password of the alternate service account in the results. You don't need to specify a value with this switch.
 
@@ -115,7 +115,7 @@ Accept wildcard characters: False
 
 ### -IncludeAlternateServiceAccountCredentialStatus
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IncludeAlternateServiceAccountCredentialStatus parameter specifies whether to include the status of the alternate service account in the results. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-CmdletExtensionAgent.md b/exchange/exchange-ps/ExchangePowerShell/Get-CmdletExtensionAgent.md
index 2de9f2d0a0..3a30158c94 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-CmdletExtensionAgent.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-CmdletExtensionAgent.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -61,7 +61,7 @@ This example displays detailed information for the Exchange cmdlet extension age
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the name of the cmdlet extension agent that you want to view. You can use any value that uniquely identifies the agent. For example:
 
@@ -83,7 +83,7 @@ Accept wildcard characters: False
 
 ### -Assembly
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Assembly parameter filters the results by the specified Assembly property value. The value for the built-in Exchange cmdlet extension agents is Microsoft.Exchange.ProvisioningAgent.dll.
 
@@ -101,7 +101,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -119,7 +119,7 @@ Accept wildcard characters: False
 
 ### -Enabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Enabled parameter filters the results by enabled or disabled cmdlet extension agents. Valid values are:
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceSearch.md b/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceSearch.md
index 9ae15ddfbb..982edba701 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceSearch.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceSearch.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 author: chrisda
 external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
 Locale: en-US
@@ -56,7 +56,7 @@ This examples show details of the compliance search named Case 1234.
 
 ### -Identity
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The Identity parameter specifies the compliance search that you want to view.
 
@@ -117,7 +117,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -137,7 +137,7 @@ Accept wildcard characters: False
 
 ### -ResultSize
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceSearchAction.md b/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceSearchAction.md
index b21f4a1973..691fd08ab6 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceSearchAction.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceSearchAction.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 author: chrisda
 external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
 Locale: en-US
@@ -98,7 +98,7 @@ This example shows details about the compliance search action named "Case 1234_P
 
 ### -Identity
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The Identity parameter specifies the compliance search action that you want to view. You can use any value that uniquely identifies the compliance search action. For example:
 
@@ -149,7 +149,7 @@ Accept wildcard characters: False
 
 ### -Details
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The Details switch specifies whether to include detailed information in the results. You don't need to specify a value with this switch.
 
@@ -167,7 +167,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 This parameter is functional only in on-premises Exchange.
 
@@ -187,7 +187,7 @@ Accept wildcard characters: False
 
 ### -Export
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 **Note**: After May 26, 2025, this parameter is no longer functional. For more information, see [Upcoming changes to Microsoft Purview eDiscovery](https://techcommunity.microsoft.com/blog/microsoft-security-blog/upcoming-changes-to-microsoft-purview-ediscovery/4405084).
 
@@ -209,7 +209,7 @@ Accept wildcard characters: False
 
 ### -IncludeCredential
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The IncludeCredential switch specifies whether to include the credential in the results. You don't need to specify a value with this switch.
 
@@ -247,7 +247,7 @@ Accept wildcard characters: False
 
 ### -Preview
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The Preview switch filters the results by Preview compliance search actions. You don't need to specify a value with this switch.
 
@@ -267,7 +267,7 @@ Accept wildcard characters: False
 
 ### -Purge
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 **Note**: In Security & Compliance PowerShell, this parameter is available only in the Search and Purge role. By default, this role is assigned only to the Organization Management and Data Investigator role groups.
 
@@ -289,7 +289,7 @@ Accept wildcard characters: False
 
 ### -ResultSize
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceSecurityFilter.md b/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceSecurityFilter.md
index 1bf2a33a12..c3f73ba2a2 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceSecurityFilter.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ComplianceSecurityFilter.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 author: chrisda
 external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
 Locale: en-US
@@ -55,7 +55,7 @@ This example returns detailed information about the compliance security filter n
 
 ### -Action
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The Action parameter filters the results by the type of search action that a filter is applied to. Valid values are:
 
@@ -79,7 +79,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -100,7 +100,7 @@ Accept wildcard characters: False
 
 ### -FilterName
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The FilterName parameter specifies the name of the compliance security filter that you want to view. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -118,7 +118,7 @@ Accept wildcard characters: False
 
 ### -User
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The User parameter filters the results by the user who gets a filter applied to their searches. Valid values are:
 
@@ -140,7 +140,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The WhatIf switch doesn't work in Security & Compliance PowerShell.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-Contact.md b/exchange/exchange-ps/ExchangePowerShell/Get-Contact.md
index 2869b21596..81424e6505 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-Contact.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-Contact.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -81,7 +81,7 @@ This example uses the Anr parameter to retrieve all mail-enabled contacts whose
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the contact that you want to view. You can use any value that uniquely identifies the contact. For example:
 
@@ -104,7 +104,7 @@ Accept wildcard characters: False
 
 ### -Anr
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Anr parameter specifies a string on which to perform an ambiguous name resolution (ANR) search. You can specify a partial string and search for objects with an attribute that matches that string. The default attributes searched are:
 
@@ -128,7 +128,7 @@ Accept wildcard characters: False
 
 ### -Credential
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -150,7 +150,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -170,7 +170,7 @@ Accept wildcard characters: False
 
 ### -Filter
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Filter parameter uses OPATH syntax to filter the results by the specified properties and values. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`.
 
@@ -197,7 +197,7 @@ Accept wildcard characters: False
 
 ### -IgnoreDefaultScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -222,7 +222,7 @@ Accept wildcard characters: False
 
 ### -OrganizationalUnit
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The OrganizationalUnit parameter filters the results based on the object's location in Active Directory. Only objects that exist in the specified location are returned. Valid input for this parameter is an organizational unit (OU) or domain that's returned by the Get-OrganizationalUnit cmdlet. You can use any value that uniquely identifies the OU or domain. For example:
 
@@ -245,7 +245,7 @@ Accept wildcard characters: False
 
 ### -ReadFromDomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -269,7 +269,7 @@ Accept wildcard characters: False
 
 ### -RecipientTypeDetails
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The RecipientTypeDetails parameter filters the results by the specified contact subtype. Valid values are:
 
@@ -293,7 +293,7 @@ Accept wildcard characters: False
 
 ### -ResultSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
 
@@ -311,7 +311,7 @@ Accept wildcard characters: False
 
 ### -SortBy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The SortBy parameter specifies the property to sort the results by. You can sort by only one property at a time. The results are sorted in ascending order.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ContentFilterConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-ContentFilterConfig.md
index fc479a47c6..0f2fff212e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ContentFilterConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ContentFilterConfig.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailControl-Help.xml
 Locale: en-US
@@ -42,7 +42,7 @@ This example returns detailed information about the content filter configuration
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ContentFilterPhrase.md b/exchange/exchange-ps/ExchangePowerShell/Get-ContentFilterPhrase.md
index 2e50b904e8..0f05d0c960 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ContentFilterPhrase.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ContentFilterPhrase.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailControl-Help.xml
 Locale: en-US
@@ -65,7 +65,7 @@ This example returns all custom words and phrases that contain the words free of
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies a custom word or phrase to display. You must enclose the value of the Identity parameter in quotation marks (").
 
@@ -85,7 +85,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -105,7 +105,7 @@ Accept wildcard characters: False
 
 ### -Phrase
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Phrase parameter specifies a custom word or phrase to display. You must enclose the value of the Phrase parameter in quotation marks (").
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DataClassification.md b/exchange/exchange-ps/ExchangePowerShell/Get-DataClassification.md
index 00d4186107..5e0a7b3d85 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DataClassification.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-DataClassification.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -69,7 +69,7 @@ This example returns details of the built-in data classification rule named SWIF
 
 ### -ClassificationRuleCollectionIdentity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ClassificationRuleCollectionIdentity parameter filters the results by the name of the data classification rule collection. The data classification rule collection that contains the built-in data classification rules is named Microsoft Rule Package. The data classification that contains new data classification rules that you create that use document fingerprints is named Fingerprint Classification Collection.
 
@@ -87,7 +87,7 @@ Accept wildcard characters: False
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the data classification rule that you want to view. You can use any value that uniquely identifies the data classification rule. For example:
 
@@ -109,7 +109,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DatabaseAvailabilityGroup.md b/exchange/exchange-ps/ExchangePowerShell/Get-DatabaseAvailabilityGroup.md
index 4b2ad570fd..41cc3f44e7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DatabaseAvailabilityGroup.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-DatabaseAvailabilityGroup.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -61,7 +61,7 @@ This example displays the properties of the DAG DAG2. Because it includes the St
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the name of the DAG to query.
 
@@ -79,7 +79,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -97,7 +97,7 @@ Accept wildcard characters: False
 
 ### -Status
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Status parameter instructs the command to query Active Directory for additional information and to include real-time status information in the output. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DatabaseAvailabilityGroupNetwork.md b/exchange/exchange-ps/ExchangePowerShell/Get-DatabaseAvailabilityGroupNetwork.md
index 06b82d75b5..e98e8e73a5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DatabaseAvailabilityGroupNetwork.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-DatabaseAvailabilityGroupNetwork.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -77,7 +77,7 @@ This example gets complete configuration and status information for the network
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the name of a DAG or a DAG network.
 
@@ -95,7 +95,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -113,7 +113,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Mailbox server in the DAG to retrieve health information for the DAG network from. You can use any value that uniquely identifies the server. For example:
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DeliveryAgentConnector.md b/exchange/exchange-ps/ExchangePowerShell/Get-DeliveryAgentConnector.md
index 985c0a3e68..ebf13c319c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DeliveryAgentConnector.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-DeliveryAgentConnector.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -52,7 +52,7 @@ This example retrieves a list of all delivery agent connectors in your organizat
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the GUID or name of the delivery agent connector.
 
@@ -70,7 +70,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DetailsTemplate.md b/exchange/exchange-ps/ExchangePowerShell/Get-DetailsTemplate.md
index db826becce..769cf1f0e9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DetailsTemplate.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-DetailsTemplate.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -61,7 +61,7 @@ This example retrieves all attributes for all User details template types in all
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the GUID of the details template or specifies the details template type and language separated by a backslash, for example, en-us\\User. Details template types are:
 
@@ -86,7 +86,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -107,7 +107,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -125,7 +125,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DistributionGroup.md b/exchange/exchange-ps/ExchangePowerShell/Get-DistributionGroup.md
index db98febfb6..49bda2ddb0 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DistributionGroup.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-DistributionGroup.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
 Locale: en-US
@@ -114,7 +114,7 @@ This example returns all distribution groups and mail-enabled security groups wh
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the distribution group or mail-enabled security group that you want to view. You can use any values that uniquely identifies the group. For example:
 
@@ -139,7 +139,7 @@ Accept wildcard characters: False
 
 ### -Anr
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Anr parameter specifies a string on which to perform an ambiguous name resolution (ANR) search. You can specify a partial string and search for objects with an attribute that matches that string. The default attributes searched are:
 
@@ -163,7 +163,7 @@ Accept wildcard characters: False
 
 ### -Credential
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Credential parameter specifies the username and password that's used to run this command. Typically, you use this parameter in scripts or when you need to provide different credentials that have the required permissions.
 
@@ -183,7 +183,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -203,7 +203,7 @@ Accept wildcard characters: False
 
 ### -Filter
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Filter parameter uses OPATH syntax to filter the results by the specified properties and values. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`.
 
@@ -230,7 +230,7 @@ Accept wildcard characters: False
 
 ### -IgnoreDefaultScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -409,7 +409,7 @@ Accept wildcard characters: False
 
 ### -ManagedBy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ManagedBy parameter filters the results by the owner of the group. You can use any value that uniquely identifies the owner. For example:
 
@@ -434,7 +434,7 @@ Accept wildcard characters: False
 
 ### -OrganizationalUnit
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The OrganizationalUnit parameter filters the results based on the object's location in Active Directory. Only objects that exist in the specified location are returned. Valid input for this parameter is an organizational unit (OU) or domain that's returned by the Get-OrganizationalUnit cmdlet. You can use any value that uniquely identifies the OU or domain. For example:
 
@@ -457,7 +457,7 @@ Accept wildcard characters: False
 
 ### -ReadFromDomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -481,7 +481,7 @@ Accept wildcard characters: False
 
 ### -RecipientTypeDetails
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The RecipientTypeDetails parameter filters the results by the specified distribution group subtype. Valid values are:
 
@@ -506,7 +506,7 @@ Accept wildcard characters: False
 
 ### -ResultSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
 
@@ -524,7 +524,7 @@ Accept wildcard characters: False
 
 ### -SortBy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The SortBy parameter specifies the property to sort the results by. You can sort by only one property at a time. The results are sorted in ascending order.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DistributionGroupMember.md b/exchange/exchange-ps/ExchangePowerShell/Get-DistributionGroupMember.md
index fced01ba5f..13fe1b9472 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DistributionGroupMember.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-DistributionGroupMember.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
 Locale: en-US
@@ -76,7 +76,7 @@ In the cloud-based service, this example downloads a comma-separated value (CSV)
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the distribution group or mail-enabled security group. You can use any value that uniquely identifies the group. For example:
 
@@ -101,7 +101,7 @@ Accept wildcard characters: False
 
 ### -Credential
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Credential parameter specifies the username and password that's used to run this command. Typically, you use this parameter in scripts or when you need to provide different credentials that have the required permissions.
 
@@ -121,7 +121,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -141,7 +141,7 @@ Accept wildcard characters: False
 
 ### -IgnoreDefaultScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -188,7 +188,7 @@ Accept wildcard characters: False
 
 ### -ReadFromDomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -212,7 +212,7 @@ Accept wildcard characters: False
 
 ### -ResultSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DlpPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-DlpPolicy.md
index e211930a67..879c90089d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DlpPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-DlpPolicy.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -52,7 +52,7 @@ This example returns detailed information about the DLP policy named Employee Nu
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the DLP policy that you want to view. You can use any value that uniquely identifies the policy. For example:
 
@@ -74,7 +74,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DlpPolicyTemplate.md b/exchange/exchange-ps/ExchangePowerShell/Get-DlpPolicyTemplate.md
index 7152f5927d..83bbc7993e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DlpPolicyTemplate.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-DlpPolicyTemplate.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -52,7 +52,7 @@ This example returns detailed information about the DLP policy template named GL
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the DLP policy template you want to view. You can use any value that uniquely identifies the DLP policy template. For example, you can specify the name, GUID or distinguished name (DN) of the DLP policy template.
 
@@ -70,7 +70,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DomainController.md b/exchange/exchange-ps/ExchangePowerShell/Get-DomainController.md
index 17becbdbe3..4d274a36d3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DomainController.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-DomainController.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -61,7 +61,7 @@ For more information about pipelining and the Format-Table cmdlet, see [About Pi
 
 ### -GlobalCatalog
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The GlobalCatalog switch specifies whether the command should return a list of global catalog servers. You don't need to specify a value with this switch.
 
@@ -79,7 +79,7 @@ Accept wildcard characters: False
 
 ### -Credential
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Credential parameter specifies the username and password that's used to run this command. Typically, you use this parameter in scripts or when you need to provide different credentials that have the required permissions.
 
@@ -101,7 +101,7 @@ Accept wildcard characters: False
 
 ### -DomainName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainName parameter specifies the fully qualified domain name (FQDN) of the domain for which you want to return a list of domain controllers.
 
@@ -119,7 +119,7 @@ Accept wildcard characters: False
 
 ### -Forest
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Forest parameter specifies the FQDN of the root domain of the forest for which you want to return a list of domain controllers.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-DynamicDistributionGroup.md b/exchange/exchange-ps/ExchangePowerShell/Get-DynamicDistributionGroup.md
index 5b6aa5a8d5..04bd1bfbd6 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-DynamicDistributionGroup.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-DynamicDistributionGroup.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
 Locale: en-US
@@ -128,7 +128,7 @@ This example returns the members for the dynamic distribution group named Full T
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the dynamic distribution group that you want to view. You can use any value that uniquely identifies the dynamic distribution group. For example:
 
@@ -153,7 +153,7 @@ Accept wildcard characters: False
 
 ### -Anr
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Anr parameter specifies a string on which to perform an ambiguous name resolution (ANR) search. You can specify a partial string and search for objects with an attribute that matches that string. The default attributes searched are:
 
@@ -177,7 +177,7 @@ Accept wildcard characters: False
 
 ### -Credential
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Credential parameter specifies the username and password that's used to run this command. Typically, you use this parameter in scripts or when you need to provide different credentials that have the required permissions.
 
@@ -197,7 +197,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -217,7 +217,7 @@ Accept wildcard characters: False
 
 ### -Filter
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Filter parameter uses OPATH syntax to filter the results by the specified properties and values. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`.
 
@@ -244,7 +244,7 @@ Accept wildcard characters: False
 
 ### -IgnoreDefaultScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -423,7 +423,7 @@ Accept wildcard characters: False
 
 ### -IncludeSystemObjects
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -443,7 +443,7 @@ Accept wildcard characters: False
 
 ### -ManagedBy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ManagedBy parameter filters the results by the owner of the group. You can use any value that uniquely identifies the owner. For example:
 
@@ -468,7 +468,7 @@ Accept wildcard characters: False
 
 ### -OrganizationalUnit
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The OrganizationalUnit parameter filters the results based on the object's location in Active Directory. Only objects that exist in the specified location are returned. Valid input for this parameter is an organizational unit (OU) or domain that's returned by the Get-OrganizationalUnit cmdlet. You can use any value that uniquely identifies the OU or domain. For example:
 
@@ -491,7 +491,7 @@ Accept wildcard characters: False
 
 ### -ReadFromDomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -515,7 +515,7 @@ Accept wildcard characters: False
 
 ### -ResultSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
 
@@ -533,7 +533,7 @@ Accept wildcard characters: False
 
 ### -SortBy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The SortBy parameter specifies the property to sort the results by. You can sort by only one property at a time. The results are sorted in ascending order.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-EcpVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Get-EcpVirtualDirectory.md
index f16142ba9d..088a852375 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-EcpVirtualDirectory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-EcpVirtualDirectory.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -71,7 +71,7 @@ This example returns a summary list of all Exchange Control Panel virtual direct
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the ECP virtual directory that you want to view. You can use any value that uniquely identifies the virtual directory. For example:
 
@@ -97,7 +97,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Exchange server that hosts the virtual directory. You can use any value that uniquely identifies the server. For example:
 
@@ -122,7 +122,7 @@ Accept wildcard characters: False
 
 ### -ADPropertiesOnly
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ADPropertiesOnly switch specifies whether to return only the virtual directory properties that are stored in Active Directory. You don't need to specify a value with this switch.
 
@@ -142,7 +142,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -160,7 +160,7 @@ Accept wildcard characters: False
 
 ### -ShowMailboxVirtualDirectories
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ShowMailboxVirtualDirectories switch shows information about backend virtual directories on Mailbox servers. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-EdgeSubscription.md b/exchange/exchange-ps/ExchangePowerShell/Get-EdgeSubscription.md
index 848fef4f46..33533e1544 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-EdgeSubscription.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-EdgeSubscription.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -52,7 +52,7 @@ This example retrieves the Edge Subscription information for the Edge Transport
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the name of the Edge Transport server for which you want to retrieve Edge Subscription information. The identity is expressed as the host name of the Edge Transport server. If no identity is specified, all Edge Subscriptions are returned.
 
@@ -70,7 +70,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-EdgeSyncServiceConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-EdgeSyncServiceConfig.md
index cf67707480..a9aa2ccf24 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-EdgeSyncServiceConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-EdgeSyncServiceConfig.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -44,7 +44,7 @@ This example reads the configuration of the Microsoft Exchange EdgeSync service
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the name of the Microsoft Exchange EdgeSync service configuration you want to view.
 
@@ -62,7 +62,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -80,7 +80,7 @@ Accept wildcard characters: False
 
 ### -Site
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Site parameter specifies the Active Directory site that EdgeSync connects to for synchronizing configuration and recipient data.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-EligibleDistributionGroupForMigration.md b/exchange/exchange-ps/ExchangePowerShell/Get-EligibleDistributionGroupForMigration.md
index 18f1ca9705..37f3f6bc74 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-EligibleDistributionGroupForMigration.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-EligibleDistributionGroupForMigration.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
 Locale: en-US
@@ -53,7 +53,7 @@ This example returns a summary list of all distribution groups that can be upgra
 
 ### -Identity
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter filters the results by the email address of the specified distribution group. If no results are returned for the specified email address, the group can't be upgraded to a Microsoft 365 Group.
 
@@ -73,7 +73,7 @@ Accept wildcard characters: False
 
 ### -ManagedBy
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ManagedBy parameter filters the results by the manager of the distribution group (the ManagedBy property). You can use any value that uniquely identifies the distribution group manager. For example:
 
@@ -100,7 +100,7 @@ Accept wildcard characters: False
 
 ### -OrganizationalUnit
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The OrganizationalUnit parameter filters the results based on the object's location in Active Directory. Only objects that exist in the specified location are returned. Valid input for this parameter is an organizational unit (OU) or domain that's returned by the Get-OrganizationalUnit cmdlet. You can use any value that uniquely identifies the OU or domain. For example:
 
@@ -123,7 +123,7 @@ Accept wildcard characters: False
 
 ### -ResultSize
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-EmailAddressPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-EmailAddressPolicy.md
index 6b73acce8c..e9219c252c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-EmailAddressPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-EmailAddressPolicy.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -51,7 +51,7 @@ This example returns detailed information for the email address policy named Con
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the email address policy that you want to view. You can use any value that uniquely identifies the policy. For example:
 
@@ -73,7 +73,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -93,7 +93,7 @@ Accept wildcard characters: False
 
 ### -IncludeMailboxSettingOnlyPolicy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is functional only in Exchange Server 2010.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-EventLogLevel.md b/exchange/exchange-ps/ExchangePowerShell/Get-EventLogLevel.md
index 28431d01ac..02209e4607 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-EventLogLevel.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-EventLogLevel.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -51,7 +51,7 @@ This example displays the event categories and log levels for the server Exchang
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter filters the results by the name of the event category. To see the available event categories, run the following command: Get-EventLogLevel.
 
@@ -71,7 +71,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
 
@@ -96,7 +96,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeAssistanceConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeAssistanceConfig.md
index 41ba1e52ca..a8a7a89513 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeAssistanceConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeAssistanceConfig.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -50,7 +50,7 @@ This example shows the configuration information for all organizations and forma
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the identity of the organization.
 
@@ -68,7 +68,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeCertificate.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeCertificate.md
index 1a7503a3a4..1e8ea547d3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeCertificate.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeCertificate.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -128,7 +128,7 @@ This example shows which certificate Exchange selects for the domain name mail.c
 
 ### -Thumbprint
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Thumbprint parameter specifies the thumbprint value of the certificate that you want to view.
 
@@ -148,7 +148,7 @@ Accept wildcard characters: False
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the certificate that you want to view. Valid values are:
 
@@ -173,7 +173,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -193,7 +193,7 @@ Accept wildcard characters: False
 
 ### -DomainName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainName parameter filters the results by the fully qualified domain name (FQDN) or server name values in the Subject Name or the Subject Alternative Name fields. You can specify multiple values separated by commas.
 
@@ -211,7 +211,7 @@ Accept wildcard characters: False
 
 ### -Instance
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is deprecated and no longer used.
 
@@ -229,7 +229,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeDiagnosticInfo.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeDiagnosticInfo.md
index 8bf3fbf192..70cd83db86 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeDiagnosticInfo.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeDiagnosticInfo.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.Management-Help.xml
 Locale: en-US
@@ -55,7 +55,7 @@ This example display the XML output of the command in format that's easier to re
 
 ### -Argument
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Argument parameter specifies a valid argument to use with the specified Component value.
 
@@ -77,7 +77,7 @@ Accept wildcard characters: False
 
 ### -Component
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Component parameter returns detailed information for the specified Component of the given Process value.
 
@@ -97,7 +97,7 @@ Accept wildcard characters: False
 
 ### -Process
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Process parameter provides details for the specified Exchange process. Valid values are the name of the process (for example, MSExchangeTransport or Microsoft.Exchange.Directory.TopologyService).
 
@@ -117,7 +117,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
 
@@ -142,7 +142,7 @@ Accept wildcard characters: False
 
 ### -Unlimited
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Unlimited switch tells the command to return all available information. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeFeature.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeFeature.md
index b9e03ef705..81225184cb 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeFeature.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeFeature.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2019
+applicable: Exchange Server 2019, Exchange Server SE
 author: lusassl-msft
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -53,7 +53,7 @@ This example returns information about the feature with the feature id PING.1.0.
 
 ### -Identity
 
-> Applicable: Exchange Server 2019
+> Applicable: Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the Exchange server that you want to modify. You can use any value that uniquely identifies the server. For example:
 
@@ -78,7 +78,7 @@ Accept wildcard characters: False
 
 ### -FeatureID
 
-> Applicable: Exchange Server 2019
+> Applicable: Exchange Server 2019, Exchange Server SE
 
 The FeatureID parameter specifies the feature you want to query information about.
 
@@ -96,7 +96,7 @@ Accept wildcard characters: False
 
 ### -RingLevel
 
-> Applicable: Exchange Server 2019
+> Applicable: Exchange Server 2019, Exchange Server SE
 
 The RingLevel parameter specifies the ring level you want to query information about.
 
@@ -114,7 +114,7 @@ Accept wildcard characters: False
 
 ### -Status
 
-> Applicable: Exchange Server 2019
+> Applicable: Exchange Server 2019, Exchange Server SE
 
 The Status parameter specifies the status you want to query information about.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServer.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServer.md
index c98652453b..f9f4549937 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServer.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServer.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -64,7 +64,7 @@ This example returns detailed information about the Exchange server named Mailbo
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the Exchange server that you want to view. You can use any value that uniquely identifies the Exchange server. For example:
 
@@ -89,7 +89,7 @@ Accept wildcard characters: False
 
 ### -Domain
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Domain parameter filters the results by the fully qualified domain name (FQDN) of the domain (for example, contoso.com).
 
@@ -109,7 +109,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -129,7 +129,7 @@ Accept wildcard characters: False
 
 ### -Status
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Status switch specifies whether to include additional property values in the results, for example, the Watson state, StaticDomainControllers, and runtime domain controller usage. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServerAccessLicense.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServerAccessLicense.md
index f9685a6836..10296db440 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServerAccessLicense.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServerAccessLicense.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServerAccessLicenseUser.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServerAccessLicenseUser.md
index 983741a576..13f0438929 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServerAccessLicenseUser.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeServerAccessLicenseUser.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -44,7 +44,7 @@ This example returns the unique users for the license named Exchange Server 2016
 
 ### -LicenseName
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The LicenseName parameter specifies the license type that you want to view. You can find the available license type values by running the Get-ExchangeServerAccessLicense cmdlet. Valid values are:
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeSettings.md b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeSettings.md
index b3c862a120..b61081fd3d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeSettings.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ExchangeSettings.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -62,7 +62,7 @@ This example returns a summary list of all Exchange setting objects.
 
 ### -Identity
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the name of the Exchange setting object. You can use any value that uniquely identifies the object. For example:
 
@@ -84,7 +84,7 @@ Accept wildcard characters: False
 
 ### -ConfigName
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ConfigName parameter filter the results by the specified property name. The value you specify is visible in the EffectiveSetting property.
 
@@ -104,7 +104,7 @@ Accept wildcard characters: False
 
 ### -Database
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Database parameter filters the results by mailbox database. You can use any value that uniquely identifies the database. For example:
 
@@ -127,7 +127,7 @@ Accept wildcard characters: False
 
 ### -Diagnostic
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Diagnostic switch specifies whether to return extremely detailed information in the results. You don't need to specify a value with this switch.
 
@@ -149,7 +149,7 @@ Accept wildcard characters: False
 
 ### -DiagnosticArgument
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DiagnosticArgument parameter modifies the results that are returned by using the Diagnostic switch. Typically, you use the Diagnostic switch and the DiagnosticArgument parameter only at the request of Microsoft Customer Service and Support to troubleshoot problems.
 
@@ -167,7 +167,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -185,7 +185,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -205,7 +205,7 @@ Accept wildcard characters: False
 
 ### -GenericScopeName
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The GenericScopeName parameter filters the results by the scope. The available values are determined by the schema of the Exchange setting object.
 
@@ -223,7 +223,7 @@ Accept wildcard characters: False
 
 ### -GenericScopes
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The GenericScopes parameter filters the results by the scope. The available values are determined by the schema of the Exchange setting object. This parameter uses the syntax `"key1=value1","key2=value2", "keyN=valueN`.
 
@@ -241,7 +241,7 @@ Accept wildcard characters: False
 
 ### -GenericScopeValue
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The GenericScopeValue parameter filters the results by the value of the scope specified by the GenericScopeName parameter. The available values are determined by the schema of the Exchange setting object.
 
@@ -259,7 +259,7 @@ Accept wildcard characters: False
 
 ### -Organization
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -277,7 +277,7 @@ Accept wildcard characters: False
 
 ### -Process
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Process parameter filters the results by the specified process. The available values are determined by the schema of the Exchange setting object.
 
@@ -295,7 +295,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter filters the results by Exchange server. You can use any value that uniquely identifies the server. For example:
 
@@ -318,7 +318,7 @@ Accept wildcard characters: False
 
 ### -User
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The User parameter filters the results by user. You identify the user by their GUID value (for example, 87246450-1b19-4c81-93dc-1a4200eff66c). To find the GUID for a user, run the following command: `Get-User <UserIdentity> | Format-List Name,GUID`.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-FailedContentIndexDocuments.md b/exchange/exchange-ps/ExchangePowerShell/Get-FailedContentIndexDocuments.md
index 5bfda847f8..066bbf3c00 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-FailedContentIndexDocuments.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-FailedContentIndexDocuments.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.WebClient-Help.xml
 Locale: en-US
@@ -93,7 +93,7 @@ This example retrieves a list of items that couldn't be indexed by Exchange Sear
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the mailbox that you want to view. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -122,7 +122,7 @@ Accept wildcard characters: False
 
 ### -MailboxDatabase
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MailboxDatabase parameter specifies the database from which to get the mailbox. You can use any value that uniquely identifies the database. For example:
 
@@ -144,7 +144,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies a Mailbox server. You can use the following values:
 
@@ -166,7 +166,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -187,7 +187,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -205,7 +205,7 @@ Accept wildcard characters: False
 
 ### -Archive
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Archive switch restricts the scope of the cmdlet to the user's archive. You don't need to specify a value with this switch.
 
@@ -225,7 +225,7 @@ Accept wildcard characters: False
 
 ### -EndDate
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The EndDate parameter specifies the end date of the date range.
 
@@ -245,7 +245,7 @@ Accept wildcard characters: False
 
 ### -ErrorCode
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ErrorCode parameter allows you to retrieve documents that failed indexing with a specific error code. You can use the cmdlet without this parameter to list all failed documents for a mailbox, a mailbox database or a Mailbox server. The output includes the error codes and reason for failure. If required, you can then restrict the output to a specific error code from the results.
 
@@ -263,7 +263,7 @@ Accept wildcard characters: False
 
 ### -FailureMode
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The FailureMode parameter specifies the type of error. Use the following values.
 
@@ -285,7 +285,7 @@ Accept wildcard characters: False
 
 ### -ResultSize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is reserved for internal Microsoft use.
 
@@ -303,7 +303,7 @@ Accept wildcard characters: False
 
 ### -StartDate
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The StartDate parameter specifies the start date of the date range.
 
@@ -323,7 +323,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-FederatedDomainProof.md b/exchange/exchange-ps/ExchangePowerShell/Get-FederatedDomainProof.md
index 4885ae058c..42a8bff194 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-FederatedDomainProof.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-FederatedDomainProof.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
 Locale: en-US
@@ -53,7 +53,7 @@ This example uses a specific certificate for the domain contoso.com.
 
 ### -DomainName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainName parameter specifies the domain name for which the cryptographically secure string is generated.
 
@@ -71,7 +71,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -89,7 +89,7 @@ Accept wildcard characters: False
 
 ### -Thumbprint
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Thumbprint parameter specifies the thumbprint of an existing certificate.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-FederatedOrganizationIdentifier.md b/exchange/exchange-ps/ExchangePowerShell/Get-FederatedOrganizationIdentifier.md
index aedaada0b0..0e704f6ca6 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-FederatedOrganizationIdentifier.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-FederatedOrganizationIdentifier.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
 Locale: en-US
@@ -53,7 +53,7 @@ This example retrieves the Exchange organization's federated organization identi
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the organization ID.
 
@@ -71,7 +71,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -91,7 +91,7 @@ Accept wildcard characters: False
 
 ### -IncludeExtendedDomainInfo
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The IncludeExtendedDomainInfo switch specifies that the command query Microsoft Federation Gateway for the status of each accepted domain that's federated. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-FederationInformation.md b/exchange/exchange-ps/ExchangePowerShell/Get-FederationInformation.md
index cbc458cea9..d899966f96 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-FederationInformation.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-FederationInformation.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
 Locale: en-US
@@ -50,7 +50,7 @@ This example gets federation information from the domain contoso.com.
 
 ### -DomainName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The DomainName parameter specifies the domain name for which federation information is to be retrieved.
 
@@ -68,7 +68,7 @@ Accept wildcard characters: False
 
 ### -BypassAdditionalDomainValidation
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The BypassAdditionalDomainValidation switch specifies that the command skip validation of domains from the external Exchange organization. You don't need to specify a value with this switch.
 
@@ -88,7 +88,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -108,7 +108,7 @@ Accept wildcard characters: False
 
 ### -TrustedHostnames
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The TrustedHostnames parameter specifies the fully qualified domain name (FQDN) of federation endpoints. Federation endpoints are the client access (frontend) services on Mailbox servers in an organization with federation enabled. Explicitly specifying the TrustedHostnames parameter allows the cmdlet to bypass prompting if the certificate presented by the endpoint doesn't match the domain name specified in the DomainName parameter.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-FederationTrust.md b/exchange/exchange-ps/ExchangePowerShell/Get-FederationTrust.md
index a6583ce2f7..7d1bbbde17 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-FederationTrust.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-FederationTrust.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
 Locale: en-US
@@ -43,7 +43,7 @@ This example retrieves properties of the federation trust configured for the Exc
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies a federation trust ID. If not specified, the cmdlet returns all federation trusts configured for the Exchange organization.
 
@@ -61,7 +61,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ForeignConnector.md b/exchange/exchange-ps/ExchangePowerShell/Get-ForeignConnector.md
index e2055e5041..807457d46f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ForeignConnector.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ForeignConnector.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -50,7 +50,7 @@ This example displays detailed configuration information for the Foreign connect
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the Foreign connector that you want to examine. The Identity parameter can take any of the following values for the Foreign connector object:
 
@@ -72,7 +72,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-FrontendTransportService.md b/exchange/exchange-ps/ExchangePowerShell/Get-FrontendTransportService.md
index ff407fa6e7..61cce09aa7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-FrontendTransportService.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-FrontendTransportService.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -52,7 +52,7 @@ This example retrieves the detailed configuration information for the Front End
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the Exchange server with the Client Access server role installed that you want to view.
 
@@ -77,7 +77,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-GlobalAddressList.md b/exchange/exchange-ps/ExchangePowerShell/Get-GlobalAddressList.md
index 9f93791074..bc4c1f9df5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-GlobalAddressList.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-GlobalAddressList.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -62,7 +62,7 @@ This example returns detailed information about the GAL named GAL\_AgencyB.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the global address list that you want to view. You can use any value that uniquely identifies the GAL. For example:
 
@@ -84,7 +84,7 @@ Accept wildcard characters: False
 
 ### -DefaultOnly
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DefaultOnly switch filters the results so only the default GAL is returned. You don't need to use a value with this switch.
 
@@ -102,7 +102,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-GlobalMonitoringOverride.md b/exchange/exchange-ps/ExchangePowerShell/Get-GlobalMonitoringOverride.md
index 75a07338cb..a92c1f42de 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-GlobalMonitoringOverride.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-GlobalMonitoringOverride.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -49,7 +49,7 @@ This example returns detailed information for the global monitoring overrides th
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-Group.md b/exchange/exchange-ps/ExchangePowerShell/Get-Group.md
index 175c1c7ad4..2d55c82323 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-Group.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-Group.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
 Locale: en-US
@@ -83,7 +83,7 @@ This example uses the Anr parameter to return all groups that begin with "Mar".
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The Identity parameter specifies the group object that you want to view. You can use any value that uniquely identifies the group. For example:
 
@@ -106,7 +106,7 @@ Accept wildcard characters: False
 
 ### -Anr
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Anr parameter specifies a string on which to perform an ambiguous name resolution (ANR) search. You can specify a partial string and search for objects with an attribute that matches that string. The default attributes searched are:
 
@@ -130,7 +130,7 @@ Accept wildcard characters: False
 
 ### -Credential
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -152,7 +152,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -174,7 +174,7 @@ Accept wildcard characters: False
 
 ### -Filter
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Filter parameter uses OPATH syntax to filter the results by the specified properties and values. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`.
 
@@ -201,7 +201,7 @@ Accept wildcard characters: False
 
 ### -IgnoreDefaultScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -226,7 +226,7 @@ Accept wildcard characters: False
 
 ### -OrganizationalUnit
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The OrganizationalUnit parameter filters the results based on the object's location in Active Directory. Only objects that exist in the specified location are returned. Valid input for this parameter is an organizational unit (OU) or domain that's returned by the Get-OrganizationalUnit cmdlet. You can use any value that uniquely identifies the OU or domain. For example:
 
@@ -249,7 +249,7 @@ Accept wildcard characters: False
 
 ### -ReadFromDomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -273,7 +273,7 @@ Accept wildcard characters: False
 
 ### -RecipientTypeDetails
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The RecipientTypeDetails parameter filters the results by the specified group subtype. Valid values are:
 
@@ -301,7 +301,7 @@ Accept wildcard characters: False
 
 ### -ResultSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
 
@@ -319,7 +319,7 @@ Accept wildcard characters: False
 
 ### -SortBy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The SortBy parameter specifies the property to sort the results by. You can sort by only one property at a time. The results are sorted in ascending order.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-HealthReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-HealthReport.md
index 8629351a23..ac6f437d9e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-HealthReport.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-HealthReport.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -56,7 +56,7 @@ This example retrieves health information for the server named Mailbox01.
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
 
@@ -79,7 +79,7 @@ Accept wildcard characters: False
 
 ### -GroupSize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The GroupSize parameter determines the size of the group to process against for a rollup. The default value is 12.
 
@@ -97,7 +97,7 @@ Accept wildcard characters: False
 
 ### -HaImpactingOnly
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The HaImpactingOnly switch filters the results to only the monitors that have HaImpacting set to True. You don't need to specify a value with this switch.
 
@@ -115,7 +115,7 @@ Accept wildcard characters: False
 
 ### -HealthSet
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The HealthSet parameter filters the results by the specified health set. Monitors that are similar or are tied to a component's architecture are grouped to form a health set. You can determine the collection of monitors (and associated probes and responders) in a given health set by using the Get-MonitoringItemIdentity cmdlet.
 
@@ -133,7 +133,7 @@ Accept wildcard characters: False
 
 ### -MinimumOnlinePercent
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MinimumOnlinePercent parameter specifies the number of members in the group to be functioning with rollup information Degraded instead of Unhealthy. The default value is 70 percent.
 
@@ -151,7 +151,7 @@ Accept wildcard characters: False
 
 ### -RollupGroup
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RollupGroup switch specifies that the health data is rolled up across servers with redundancy limits. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-HostedContentFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-HostedContentFilterRule.md
index 61414d2265..e2df6989bd 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-HostedContentFilterRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-HostedContentFilterRule.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -51,7 +51,7 @@ This example retrieves details about the spam filter rule named Contoso Recipien
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the spam filter rule that you want to view. You can use any value that uniquely identifies the rule. For example:
 
@@ -73,7 +73,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -91,7 +91,7 @@ Accept wildcard characters: False
 
 ### -State
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The State parameter filters the results by the state of the rule. Valid values are:
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-HybridConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Get-HybridConfiguration.md
index 2d7cd5fc46..9e64f221a2 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-HybridConfiguration.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-HybridConfiguration.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -42,7 +42,7 @@ This example returns detailed information about the hybrid deployment configurat
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-IPAllowListConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-IPAllowListConfig.md
index fa783a57cf..0d1ece03ec 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-IPAllowListConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-IPAllowListConfig.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailControl-Help.xml
 Locale: en-US
@@ -44,7 +44,7 @@ This example returns detailed information about the IP Allow list configuration
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-IPAllowListEntry.md b/exchange/exchange-ps/ExchangePowerShell/Get-IPAllowListEntry.md
index 33954acbcb..9554627b22 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-IPAllowListEntry.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-IPAllowListEntry.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailControl-Help.xml
 Locale: en-US
@@ -60,7 +60,7 @@ This example returns an IP Allow list entry in which the specified IP address is
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the identity integer value of the IP Allow list entry that you want to view. When you add an entry to the IP Allow list, the Identity value is automatically assigned.
 
@@ -78,7 +78,7 @@ Accept wildcard characters: False
 
 ### -IPAddress
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IPAddress parameter specifies an IP address to view in the IP Allow list entry or entries. For example, if you have an IP Allow list entry that specifies a range of IP addresses from 192.168.0.1 through 192.168.0.20, enter any IP address in the IP Allow list IP address range to return the IP Allow list entry.
 
@@ -96,7 +96,7 @@ Accept wildcard characters: False
 
 ### -ResultSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
 
@@ -114,7 +114,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-IPAllowListProvider.md b/exchange/exchange-ps/ExchangePowerShell/Get-IPAllowListProvider.md
index 7cc5d7d182..4c02a98691 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-IPAllowListProvider.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-IPAllowListProvider.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailControl-Help.xml
 Locale: en-US
@@ -50,7 +50,7 @@ This example returns detailed information for the IP Allow list provider named C
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the IP Allow list provider that you want to view. You can use any value that uniquely identifies the IP Allow list provider. For example:
 
@@ -72,7 +72,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-IPAllowListProvidersConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-IPAllowListProvidersConfig.md
index 33845fc425..76c2a9caf3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-IPAllowListProvidersConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-IPAllowListProvidersConfig.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailControl-Help.xml
 Locale: en-US
@@ -44,7 +44,7 @@ This example returns detailed information about the IP Allow list providers conf
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-IPBlockListConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-IPBlockListConfig.md
index badc1fb114..814407a7b2 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-IPBlockListConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-IPBlockListConfig.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailControl-Help.xml
 Locale: en-US
@@ -44,7 +44,7 @@ This example returns detailed information about the IP Block list configuration
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-IPBlockListEntry.md b/exchange/exchange-ps/ExchangePowerShell/Get-IPBlockListEntry.md
index ac6528eb90..497fb75329 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-IPBlockListEntry.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-IPBlockListEntry.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailControl-Help.xml
 Locale: en-US
@@ -60,7 +60,7 @@ This example returns machine-generated entries in the IP Block list that are ins
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the identity integer value of the IP Block list entry that you want to view. When you add an entry to the IP Block list, the Identity value is automatically assigned.
 
@@ -78,7 +78,7 @@ Accept wildcard characters: False
 
 ### -IPAddress
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IPAddress parameter specifies an IP address to view in the IP Block list entry or entries. For example, if you have an IP Block list entry that specifies a range of IP addresses from 192.168.0.1 through 192.168.0.20, enter any IP address in the IP Block list IP address range to return the IP Block list entry.
 
@@ -96,7 +96,7 @@ Accept wildcard characters: False
 
 ### -ResultSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
 
@@ -114,7 +114,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-IPBlockListProvider.md b/exchange/exchange-ps/ExchangePowerShell/Get-IPBlockListProvider.md
index a6befcee10..dd1c0f63eb 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-IPBlockListProvider.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-IPBlockListProvider.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailControl-Help.xml
 Locale: en-US
@@ -50,7 +50,7 @@ This example returns detailed information for the existing IP Block list provide
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the IP Block list provider that you want to view. You can use any value that uniquely identifies the IP Block list provider. For example:
 
@@ -72,7 +72,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-IPBlockListProvidersConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-IPBlockListProvidersConfig.md
index f84def95bc..0360780512 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-IPBlockListProvidersConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-IPBlockListProvidersConfig.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailControl-Help.xml
 Locale: en-US
@@ -44,7 +44,7 @@ This example returns detailed information about the IP Block list providers on t
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-IRMConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Get-IRMConfiguration.md
index 34e73d32b3..d609d6bd9d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-IRMConfiguration.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-IRMConfiguration.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailControl-Help.xml
 Locale: en-US
@@ -44,7 +44,7 @@ This example retrieves the IRM configuration in your organization.
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ImapSettings.md b/exchange/exchange-ps/ExchangePowerShell/Get-ImapSettings.md
index aa7c94f41a..aa9e21ca9f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ImapSettings.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ImapSettings.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -43,7 +43,7 @@ This example displays the settings and values of the Microsoft Exchange IMAP4 se
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -61,7 +61,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-InboxRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-InboxRule.md
index d534f407cd..3428804391 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-InboxRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-InboxRule.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -61,7 +61,7 @@ This example retrieves the Inbox rule ReceivedLastYear from the mailbox joe@cont
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the Inbox rule that you want to view. You can use any value that uniquely identifies the rule. For example:
 
@@ -84,7 +84,7 @@ Accept wildcard characters: False
 
 ### -BypassScopeCheck
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The BypassScopeCheck switch specifies whether to bypass the scope check for the user that's running the command. You don't need to specify a value with this switch.
 
@@ -102,7 +102,7 @@ Accept wildcard characters: False
 
 ### -DescriptionTimeFormat
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DescriptionTimeFormat parameter specifies the format for time values in the rule description. For example:
 
@@ -122,7 +122,7 @@ Accept wildcard characters: False
 
 ### -DescriptionTimeZone
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DescriptionTimeZone parameter specifies time zone that's used for time values in the rule description.
 
@@ -146,7 +146,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -166,7 +166,7 @@ Accept wildcard characters: False
 
 ### -IncludeHidden
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IncludeHidden switch specifies whether to include hidden Inbox rules in the results. You don't need to specify a value with this switch.
 
@@ -184,7 +184,7 @@ Accept wildcard characters: False
 
 ### -Mailbox
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Mailbox parameter specifies the mailbox that contains the Inbox rule. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -253,7 +253,7 @@ Accept wildcard characters: False
 
 ### -SweepRules
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-IntraOrganizationConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Get-IntraOrganizationConfiguration.md
index c604bab845..09a889529c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-IntraOrganizationConfiguration.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-IntraOrganizationConfiguration.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
 Locale: en-US
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-IntraOrganizationConnector.md b/exchange/exchange-ps/ExchangePowerShell/Get-IntraOrganizationConnector.md
index e1f54a76a5..7f8893e54e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-IntraOrganizationConnector.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-IntraOrganizationConnector.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
 Locale: en-US
@@ -52,7 +52,7 @@ This example returns details about the Intra-Organization connector named "MainC
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the Intra-Organization connector that you want to view. You can use any value that uniquely identifies the connector. For example:
 
@@ -74,7 +74,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-JournalRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-JournalRule.md
index a5bf61f338..35a9d4bfd9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-JournalRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-JournalRule.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailControl-Help.xml
 Locale: en-US
@@ -52,7 +52,7 @@ This example retrieves the specific journal rule Brokerage Communications and pi
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the rule you want to view. Enter either the name or the GUID of the journal rule. You can omit the parameter label.
 
@@ -70,7 +70,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-LogonStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-LogonStatistics.md
index d64ba0f423..a0b449dff7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-LogonStatistics.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-LogonStatistics.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -62,7 +62,7 @@ This example returns logon statistics for all users connected to the server Serv
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the mailbox to get logon statistics from. You can use one of the following values to identify the mailbox:
 
@@ -92,7 +92,7 @@ Accept wildcard characters: False
 
 ### -Database
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Database parameter specifies the mailbox database to get logon statistics from (all mailboxes in the specified database). You can use any value that uniquely identifies the mailbox database. For example:
 
@@ -118,7 +118,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Mailbox server to get logon statistics from (all mailboxes on all databases, including recovery databases, on the specified server). You can use one of the following values to identify the server:
 
@@ -143,7 +143,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-Mailbox.md b/exchange/exchange-ps/ExchangePowerShell/Get-Mailbox.md
index b1f77201f7..f40d64b16c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-Mailbox.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-Mailbox.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -211,7 +211,7 @@ This example returns information about the remote archive mailbox for the user e
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the mailbox that you want to view. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -242,7 +242,7 @@ Accept wildcard characters: False
 
 ### -Anr
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Anr parameter specifies a string on which to perform an ambiguous name resolution (ANR) search. You can specify a partial string and search for objects with an attribute that matches that string. The default attributes searched are:
 
@@ -266,7 +266,7 @@ Accept wildcard characters: False
 
 ### -Arbitration
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -290,7 +290,7 @@ Accept wildcard characters: False
 
 ### -Archive
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Archive switch specifies whether to return only mailboxes that have an archive enabled in the results. You don't need to specify a value with this switch.
 
@@ -308,7 +308,7 @@ Accept wildcard characters: False
 
 ### -AuditLog
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -332,7 +332,7 @@ Accept wildcard characters: False
 
 ### -AuxAuditLog
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -356,7 +356,7 @@ Accept wildcard characters: False
 
 ### -Credential
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -378,7 +378,7 @@ Accept wildcard characters: False
 
 ### -Database
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -404,7 +404,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -424,7 +424,7 @@ Accept wildcard characters: False
 
 ### -Filter
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Filter parameter uses OPATH syntax to filter the results by the specified properties and values. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`.
 
@@ -451,7 +451,7 @@ Accept wildcard characters: False
 
 ### -GroupMailbox
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The GroupMailbox switch specifies whether to return only Microsoft 365 Groups in the results. You don't need to specify a value with this switch.
 
@@ -469,7 +469,7 @@ Accept wildcard characters: False
 
 ### -IgnoreDefaultScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -692,7 +692,7 @@ Accept wildcard characters: False
 
 ### -Migration
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Migration switch specifies whether to return only migration mailboxes in the results. You don't need to specify a value with this switch.
 
@@ -710,7 +710,7 @@ Accept wildcard characters: False
 
 ### -Monitoring
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -732,7 +732,7 @@ Accept wildcard characters: False
 
 ### -OrganizationalUnit
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The OrganizationalUnit parameter filters the results based on the object's location in Active Directory. Only objects that exist in the specified location are returned. Valid input for this parameter is an organizational unit (OU) or domain that's returned by the Get-OrganizationalUnit cmdlet. You can use any value that uniquely identifies the OU or domain. For example:
 
@@ -755,7 +755,7 @@ Accept wildcard characters: False
 
 ### -PublicFolder
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The PublicFolder switch specifies whether to return only public folder mailboxes in the results. You don't need to specify a value with this switch.
 
@@ -775,7 +775,7 @@ Accept wildcard characters: False
 
 ### -ReadFromDomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -799,7 +799,7 @@ Accept wildcard characters: False
 
 ### -RecipientTypeDetails
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RecipientTypeDetails parameter filters the results by the specified mailbox subtype. Valid values are:
 
@@ -831,7 +831,7 @@ Accept wildcard characters: False
 
 ### -RemoteArchive
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -853,7 +853,7 @@ Accept wildcard characters: False
 
 ### -ResultSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
 
@@ -871,7 +871,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -926,7 +926,7 @@ Accept wildcard characters: False
 
 ### -SortBy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SortBy parameter specifies the property to sort the results by. You can sort by only one property at a time. The results are sorted in ascending order.
 
@@ -954,7 +954,7 @@ Accept wildcard characters: False
 
 ### -SupervisoryReviewPolicy
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxAuditBypassAssociation.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxAuditBypassAssociation.md
index 909b2e8062..acbf528c80 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxAuditBypassAssociation.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxAuditBypassAssociation.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
 Locale: en-US
@@ -62,7 +62,7 @@ This example returns all accounts that are configured for mailbox audit logging
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the user account or computer account where you want to view the value of the AuditBypassEnabled property.
 
@@ -80,7 +80,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -100,7 +100,7 @@ Accept wildcard characters: False
 
 ### -ResultSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxAutoReplyConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxAutoReplyConfiguration.md
index 35f606e712..2b46e024e2 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxAutoReplyConfiguration.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxAutoReplyConfiguration.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -62,7 +62,7 @@ This example retrieves Automatic Replies settings for Tony's mailbox at contoso.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the mailbox that you want to view. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -91,7 +91,7 @@ Accept wildcard characters: False
 
 ### -Credential
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Credential parameter specifies the username and password that's used to run this command. Typically, you use this parameter in scripts or when you need to provide different credentials that have the required permissions.
 
@@ -111,7 +111,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -131,7 +131,7 @@ Accept wildcard characters: False
 
 ### -ReadFromDomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ReadFromDomainController switch specifies that information should be read from a domain controller in the user's domain. You don't need to specify a value with this switch.
 
@@ -153,7 +153,7 @@ Accept wildcard characters: False
 
 ### -ResultSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ResultSize parameter specifies the maximum number of settings to return. If you want to return all settings that match the command, use unlimited for the value of this parameter.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxCalendarConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxCalendarConfiguration.md
index 4001d80f30..253bb2bb1b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxCalendarConfiguration.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxCalendarConfiguration.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -82,7 +82,7 @@ This example requests that the domain controller DC1 retrieves calendar settings
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the mailbox that you want to view. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -111,7 +111,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxCalendarFolder.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxCalendarFolder.md
index c0a830aac8..6a4ba7c36a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxCalendarFolder.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxCalendarFolder.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
 Locale: en-US
@@ -60,7 +60,7 @@ This example returns all provided publishing information for the specified calen
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the calendar folder that you want to view. The syntax is `MailboxID:\ParentFolder[\SubFolder]`.
 
@@ -93,7 +93,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxDatabase.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxDatabase.md
index 91f420193f..1f12278e17 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxDatabase.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxDatabase.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -75,7 +75,7 @@ This example returns detailed information about the mailbox database named Mailb
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the mailbox database that you want to view. You can use any value that uniquely identifies the database. For example:
 
@@ -99,7 +99,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter filters the results by the specified Mailbox server. You can use any value that uniquely identifies the server. For example:
 
@@ -124,7 +124,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -142,7 +142,7 @@ Accept wildcard characters: False
 
 ### -DumpsterStatistics
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DumpsterStatistics switch specifies that transport dumpster statistics be returned with the database status. You don't need to specify a value with this switch.
 
@@ -160,7 +160,7 @@ Accept wildcard characters: False
 
 ### -IncludeCorrupted
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -198,7 +198,7 @@ Accept wildcard characters: False
 
 ### -IncludePreExchange2013
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IncludePreExchange2013 switch specifies whether to return information about Exchange 2010 or earlier mailbox databases. You don't need to specify a value with this switch.
 
@@ -216,7 +216,7 @@ Accept wildcard characters: False
 
 ### -Status
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Status switch specifies whether to retrieve the available free space in the database root and information about the following attributes:
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxDatabaseCopyStatus.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxDatabaseCopyStatus.md
index e4b66a20fa..14fc9d8aa4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxDatabaseCopyStatus.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxDatabaseCopyStatus.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -76,7 +76,7 @@ This example returns the status for the copy of database DB1 on the Mailbox serv
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the name of the database copy for which the command should gather information. The Identity parameter can be specified in the form of `<Database>\<Server>`. Specifying just `<Database>` returns information for all copies of the database. This parameter can't be combined with the Server parameter.
 
@@ -94,7 +94,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies that a Mailbox server returns status information for all of its mailbox database copies. This parameter can't be combined with the Identity parameter.
 
@@ -112,7 +112,7 @@ Accept wildcard characters: False
 
 ### -Active
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Active switch specifies whether to return mailbox database copy status for the active mailbox database copy only. You don't need to specify a value with this switch.
 
@@ -130,7 +130,7 @@ Accept wildcard characters: False
 
 ### -ConnectionStatus
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is deprecated and no longer used.
 
@@ -148,7 +148,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -166,7 +166,7 @@ Accept wildcard characters: False
 
 ### -Local
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Local switch specifies whether to return mailbox database copy status information from only the local Mailbox server. You don't need to specify a value with this switch.
 
@@ -184,7 +184,7 @@ Accept wildcard characters: False
 
 ### -ExtendedErrorInfo
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExtendedErrorInfo switch specifies whether to return an output object containing any exception details. You don't need to specify a value with this switch.
 
@@ -202,7 +202,7 @@ Accept wildcard characters: False
 
 ### -UseServerCache
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The UseServerCache switch specifies whether to enable a server-side remote procedure call (RPC) caching of status information for 5 seconds. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxExportRequest.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxExportRequest.md
index ea3af86b8e..c9dfe85b03 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxExportRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxExportRequest.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -100,7 +100,7 @@ This example returns all export requests that have the name DB01toPST where the
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the identity of the export request. By default, export requests are named `<alias>\MailboxExportX` (where X = 0-9). If you specified a name for the export request when the request was created using the New-MailboxExportRequest cmdlet, use the following syntax: `Alias\Name`. Exchange automatically precedes the request with the mailbox's alias.
 
@@ -127,7 +127,7 @@ Accept wildcard characters: False
 
 ### -BatchName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The BatchName parameter specifies the name given to a batch export request.
 
@@ -173,7 +173,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -191,7 +191,7 @@ Accept wildcard characters: False
 
 ### -HighPriority
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The HighPriority parameter filters the results based on the Priority value that was assigned when the request was created. Valid input for this parameter is $true or $false. Here's how these values filter the results:
 
@@ -249,7 +249,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Name parameter specifies that export requests that have the specified name are returned.
 
@@ -273,7 +273,7 @@ Accept wildcard characters: False
 
 ### -ResultSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
 
@@ -291,7 +291,7 @@ Accept wildcard characters: False
 
 ### -Status
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Status parameter filters the results based on status. You can use the following values:
 
@@ -324,7 +324,7 @@ Accept wildcard characters: False
 
 ### -Suspend
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Suspend parameter specifies whether to return requests that have been suspended. Valid input for this parameter is $true or $false.
 
@@ -344,7 +344,7 @@ Accept wildcard characters: False
 
 ### -RequestQueue
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RequestQueue parameter identifies the request based on the mailbox database where the request is being run. You can use any value that uniquely identifies the database. For example:
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxExportRequestStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxExportRequestStatistics.md
index 5877037fe2..20454976c2 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxExportRequestStatistics.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxExportRequestStatistics.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -108,7 +108,7 @@ This example returns additional information for all the export requests that hav
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the identity of the export request. By default, export requests are named `<alias>\MailboxExportX` (where X = 0-9). If you specified a name for the export request when it was created by using the New-MailboxExportRequest cmdlet, use the following syntax: `Alias\Name`.
 
@@ -150,7 +150,7 @@ Accept wildcard characters: False
 
 ### -RequestQueue
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is for debugging purposes only.
 
@@ -176,7 +176,7 @@ Accept wildcard characters: False
 
 ### -Diagnostic
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Diagnostic switch specifies whether to return extremely detailed information in the results. You don't need to specify a value with this switch.
 
@@ -196,7 +196,7 @@ Accept wildcard characters: False
 
 ### -DiagnosticArgument
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DiagnosticArgument parameter modifies the results that are returned by using the Diagnostic switch. Typically, you use the Diagnostic switch and the DiagnosticArgument parameter only at the request of Microsoft Customer Service and Support to troubleshoot problems.
 
@@ -234,7 +234,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -252,7 +252,7 @@ Accept wildcard characters: False
 
 ### -IncludeReport
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IncludeReport switch specifies whether to return additional details, which can be used for troubleshooting. You don't need to specify a value with this switch.
 
@@ -270,7 +270,7 @@ Accept wildcard characters: False
 
 ### -ReportOnly
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ReportOnly switch returns the results as an array of report entries (encoded strings). You don't need to specify a value with this switch.
 
@@ -288,7 +288,7 @@ Accept wildcard characters: False
 
 ### -RequestGuid
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RequestGuid parameter specifies the unique identifier for the export request. To find the export request GUID, use the Get-MailboxExportRequest cmdlet. If you specify the RequestGuid parameter, you must also specify the RequestQueue parameter. You can't use this parameter with the Identity parameter.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxFolder.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxFolder.md
index 681bdd6120..682f41b72f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxFolder.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxFolder.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -87,7 +87,7 @@ This example returns a summary list of all levels of folders under Inbox in your
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the mailbox folder that you want to view. The syntax is `[MailboxID]:[\ParentFolder][\SubFolder]`.
 
@@ -124,7 +124,7 @@ Accept wildcard characters: False
 
 ### -GetChildren
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The GetChildren switch specifies whether to return only the first level of subfolders under the specified parent folder. You don't need to specify a value with this switch.
 
@@ -144,7 +144,7 @@ Accept wildcard characters: False
 
 ### -Recurse
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Recurse switch specifies whether to return the specified parent folder and all of its subfolders. You don't need to specify a value with this switch.
 
@@ -164,7 +164,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -184,7 +184,7 @@ Accept wildcard characters: False
 
 ### -MailFolderOnly
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MailFolderOnly switch specifies whether to return only the mail folders in the specified mailbox. You don't need to specify a value with this switch.
 
@@ -202,7 +202,7 @@ Accept wildcard characters: False
 
 ### -ResultSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxFolderPermission.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxFolderPermission.md
index 198d611d27..5ee63ba381 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxFolderPermission.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxFolderPermission.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
 Locale: en-US
@@ -64,7 +64,7 @@ This example returns the permissions for the Calendar folder in John's mailbox,
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the mailbox folder that you want to view. The syntax is `MailboxID:\ParentFolder[\SubFolder]`.
 
@@ -97,7 +97,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -117,7 +117,7 @@ Accept wildcard characters: False
 
 ### -GroupMailbox
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The GroupMailbox switch is required to return Microsoft 365 Groups in the results. You don't need to specify a value with this switch.
 
@@ -195,7 +195,7 @@ Accept wildcard characters: False
 
 ### -User
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The User parameter filters the results by the specified mailbox, mail user, or mail-enabled security group (security principal) that's granted permission to the mailbox folder.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxFolderStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxFolderStatistics.md
index 7bd91cd3c4..dfc0f44929 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxFolderStatistics.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxFolderStatistics.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
 Locale: en-US
@@ -117,7 +117,7 @@ This example uses the FolderScope parameter to view inbox folders statistics for
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the identity of the mailbox or mail user. You can use any value that uniquely identifies the mailbox or mail user. For example:
 
@@ -186,7 +186,7 @@ Accept wildcard characters: False
 
 ### -Archive
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Archive switch specifies whether to return the usage statistics of the archive associated with the mailbox or mail user. You don't need to specify a value with this switch.
 
@@ -204,7 +204,7 @@ Accept wildcard characters: False
 
 ### -AuditLog
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -244,7 +244,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -264,7 +264,7 @@ Accept wildcard characters: False
 
 ### -FolderScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The FolderScope parameter specifies the scope of the search by folder type. Valid parameter values include:
 
@@ -304,7 +304,7 @@ Accept wildcard characters: False
 
 ### -IncludeAnalysis
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IncludeAnalysis switch specifies whether to scan all items within a folder and return statistics related to the folder and item size. You don't need to specify a value with this switch.
 
@@ -324,7 +324,7 @@ Accept wildcard characters: False
 
 ### -IncludeOldestAndNewestItems
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IncludeOldestAndNewestItems switch specifies whether to return the dates of the oldest and newest items in each folder. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxImportRequest.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxImportRequest.md
index 0f27c0ce17..4ee78760e3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxImportRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxImportRequest.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -102,7 +102,7 @@ This example returns all import requests that have the name Recovered where the
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the identity of the import request. By default, import requests are named `<alias>\MailboxImportX` (where X = 0-9). If you specify a name for the import request, use the following syntax: `Alias\Name`. Microsoft Exchange automatically precedes the request with the mailbox's alias.
 
@@ -129,7 +129,7 @@ Accept wildcard characters: False
 
 ### -BatchName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The BatchName parameter specifies the name given to a batch import request.
 
@@ -175,7 +175,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -195,7 +195,7 @@ Accept wildcard characters: False
 
 ### -HighPriority
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -257,7 +257,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Name parameter specifies that import requests that have the specified name are returned.
 
@@ -279,7 +279,7 @@ Accept wildcard characters: False
 
 ### -ResultSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
 
@@ -297,7 +297,7 @@ Accept wildcard characters: False
 
 ### -Status
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Status parameter filters the results based on status. You can use the following values:
 
@@ -330,7 +330,7 @@ Accept wildcard characters: False
 
 ### -Suspend
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Suspend parameter specifies whether to return requests that have been suspended. Valid input for this parameter is $true or $false.
 
@@ -350,7 +350,7 @@ Accept wildcard characters: False
 
 ### -RequestQueue
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 

From 2fe6dbc699b0674a15bea0a26b83370ef6c6d4e4 Mon Sep 17 00:00:00 2001
From: Chris Davis <chris.davis@microsoft.com>
Date: Thu, 7 Aug 2025 09:13:13 -0700
Subject: [PATCH 130/145] Add Exchange Server SE 3

---
 .../ExchangePowerShell/Get-MailContact.md     | 24 +++++-----
 .../Get-MailPublicFolder.md                   | 20 ++++-----
 .../ExchangePowerShell/Get-MailUser.md        | 22 +++++-----
 .../Get-MailboxImportRequestStatistics.md     | 18 ++++----
 .../Get-MailboxJunkEmailConfiguration.md      | 12 ++---
 .../ExchangePowerShell/Get-MailboxLocation.md | 14 +++---
 .../Get-MailboxMessageConfiguration.md        | 12 ++---
 .../Get-MailboxPermission.md                  | 16 +++----
 .../Get-MailboxRegionalConfiguration.md       |  8 ++--
 .../Get-MailboxRepairRequest.md               | 16 +++----
 .../Get-MailboxRestoreRequest.md              | 24 +++++-----
 .../Get-MailboxRestoreRequestStatistics.md    | 18 ++++----
 .../ExchangePowerShell/Get-MailboxSearch.md   | 14 +++---
 .../ExchangePowerShell/Get-MailboxServer.md   |  8 ++--
 .../Get-MailboxSpellingConfiguration.md       |  6 +--
 .../Get-MailboxStatistics.md                  | 28 ++++++------
 .../Get-MailboxTransportService.md            |  6 +--
 .../Get-MailboxUserConfiguration.md           | 12 ++---
 .../Get-MalwareFilterPolicy.md                |  6 +--
 .../Get-MalwareFilterRule.md                  |  8 ++--
 .../Get-MalwareFilteringServer.md             |  6 +--
 .../Get-ManagedFolderMailboxPolicy.md         |  2 +-
 .../ExchangePowerShell/Get-ManagementRole.md  | 20 ++++-----
 .../Get-ManagementRoleAssignment.md           | 44 +++++++++----------
 .../Get-ManagementRoleEntry.md                | 12 ++---
 .../ExchangePowerShell/Get-ManagementScope.md | 10 ++---
 .../Get-MapiVirtualDirectory.md               | 10 ++---
 .../ExchangePowerShell/Get-Message.md         | 28 ++++++------
 .../ExchangePowerShell/Get-MessageCategory.md |  8 ++--
 .../Get-MessageClassification.md              |  8 ++--
 .../Get-MessageTrackingLog.md                 | 32 +++++++-------
 .../Get-MessageTrackingReport.md              | 24 +++++-----
 .../ExchangePowerShell/Get-MigrationBatch.md  | 16 +++----
 .../ExchangePowerShell/Get-MigrationConfig.md |  4 +-
 .../Get-MigrationEndpoint.md                  | 14 +++---
 .../Get-MigrationStatistics.md                |  8 ++--
 .../ExchangePowerShell/Get-MigrationUser.md   | 16 +++----
 .../Get-MigrationUserStatistics.md            | 18 ++++----
 .../ExchangePowerShell/Get-MobileDevice.md    | 26 +++++------
 .../Get-MobileDeviceMailboxPolicy.md          |  6 +--
 .../Get-MobileDeviceStatistics.md             | 22 +++++-----
 .../Get-MonitoringItemHelp.md                 |  6 +--
 .../Get-MonitoringItemIdentity.md             |  6 +--
 .../ExchangePowerShell/Get-MoveRequest.md     | 38 ++++++++--------
 .../Get-MoveRequestStatistics.md              | 18 ++++----
 .../Get-NetworkConnectionInfo.md              |  6 +--
 .../ExchangePowerShell/Get-Notification.md    | 16 +++----
 .../Get-OabVirtualDirectory.md                | 12 ++---
 .../Get-OfflineAddressBook.md                 |  8 ++--
 .../Get-OnlineMeetingConfiguration.md         |  6 +--
 .../Get-OrganizationConfig.md                 |  4 +-
 .../Get-OrganizationRelationship.md           |  6 +--
 .../Get-OrganizationalUnit.md                 | 14 +++---
 .../ExchangePowerShell/Get-OutlookAnywhere.md | 12 ++---
 .../Get-OutlookProtectionRule.md              |  6 +--
 .../ExchangePowerShell/Get-OutlookProvider.md |  6 +--
 .../Get-OwaMailboxPolicy.md                   |  6 +--
 .../Get-OwaVirtualDirectory.md                | 12 ++---
 .../Get-PartnerApplication.md                 |  8 ++--
 .../Get-PendingFederatedDomain.md             |  2 +-
 .../ExchangePowerShell/Get-PolicyTipConfig.md | 12 ++---
 .../ExchangePowerShell/Get-PopSettings.md     |  6 +--
 .../Get-PowerShellVirtualDirectory.md         | 12 ++---
 .../ExchangePowerShell/Get-PublicFolder.md    | 20 ++++-----
 .../Get-PublicFolderClientPermission.md       | 10 ++---
 .../Get-PublicFolderDatabase.md               | 12 ++---
 .../Get-PublicFolderItemStatistics.md         |  8 ++--
 .../Get-PublicFolderMailboxDiagnostics.md     | 14 +++---
 ...Get-PublicFolderMailboxMigrationRequest.md | 20 ++++-----
 ...FolderMailboxMigrationRequestStatistics.md | 18 ++++----
 .../Get-PublicFolderMigrationRequest.md       | 20 ++++-----
 ...-PublicFolderMigrationRequestStatistics.md | 18 ++++----
 .../Get-PublicFolderMoveRequest.md            | 20 ++++-----
 .../Get-PublicFolderMoveRequestStatistics.md  | 18 ++++----
 .../Get-PublicFolderStatistics.md             | 10 ++---
 .../ExchangePowerShell/Get-Queue.md           | 26 +++++------
 .../ExchangePowerShell/Get-QueueDigest.md     | 20 ++++-----
 .../ExchangePowerShell/Get-RMSTemplate.md     |  8 ++--
 .../Get-ReceiveConnector.md                   |  8 ++--
 .../ExchangePowerShell/Get-Recipient.md       | 40 ++++++++---------
 .../Get-RecipientFilterConfig.md              |  6 +--
 .../Get-RecoverableItems.md                   | 20 ++++-----
 .../ExchangePowerShell/Get-RemoteDomain.md    |  6 +--
 .../ExchangePowerShell/Get-RemoteMailbox.md   | 24 +++++-----
 .../ExchangePowerShell/Get-ResourceConfig.md  |  6 +--
 .../ExchangePowerShell/Get-ResubmitRequest.md |  6 +--
 .../ExchangePowerShell/Get-RetentionPolicy.md |  6 +--
 .../Get-RetentionPolicyTag.md                 | 14 +++---
 .../Get-RoleAssignmentPolicy.md               |  6 +--
 .../ExchangePowerShell/Get-RoleGroup.md       | 16 +++----
 .../ExchangePowerShell/Get-RoleGroupMember.md | 10 ++---
 .../ExchangePowerShell/Get-RpcClientAccess.md |  6 +--
 .../Get-SearchDocumentFormat.md               |  6 +--
 .../Get-SecurityPrincipal.md                  | 18 ++++----
 .../ExchangePowerShell/Get-SendConnector.md   |  6 +--
 .../Get-SenderFilterConfig.md                 |  6 +--
 96 files changed, 650 insertions(+), 650 deletions(-)

diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailContact.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailContact.md
index 95a7d4a31c..e1762e870e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailContact.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailContact.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -76,7 +76,7 @@ This example retrieves detailed information for the mail contact named Arlene.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the mail contact that you want to view. You can use any value that uniquely identifies the mail contact. For example:
 
@@ -101,7 +101,7 @@ Accept wildcard characters: False
 
 ### -ANR
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Anr parameter specifies a string on which to perform an ambiguous name resolution (ANR) search. You can specify a partial string and search for objects with an attribute that matches that string. The default attributes searched are:
 
@@ -125,7 +125,7 @@ Accept wildcard characters: False
 
 ### -Credential
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -147,7 +147,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -167,7 +167,7 @@ Accept wildcard characters: False
 
 ### -Filter
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Filter parameter uses OPATH syntax to filter the results by the specified properties and values. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`.
 
@@ -194,7 +194,7 @@ Accept wildcard characters: False
 
 ### -IgnoreDefaultScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -219,7 +219,7 @@ Accept wildcard characters: False
 
 ### -OrganizationalUnit
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The OrganizationalUnit parameter filters the results based on the object's location in Active Directory. Only objects that exist in the specified location are returned. Valid input for this parameter is an organizational unit (OU) or domain that's returned by the Get-OrganizationalUnit cmdlet. You can use any value that uniquely identifies the OU or domain. For example:
 
@@ -242,7 +242,7 @@ Accept wildcard characters: False
 
 ### -ReadFromDomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -266,7 +266,7 @@ Accept wildcard characters: False
 
 ### -RecipientTypeDetails
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The RecipientTypeDetails parameter filters the results by the specified mail contact subtype. Valid values are:
 
@@ -289,7 +289,7 @@ Accept wildcard characters: False
 
 ### -ResultSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
 
@@ -307,7 +307,7 @@ Accept wildcard characters: False
 
 ### -SortBy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The SortBy parameter specifies the property to sort the results by. You can sort by only one property at a time. The results are sorted in ascending order.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailPublicFolder.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailPublicFolder.md
index c9c71c1564..5c3de390b6 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailPublicFolder.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailPublicFolder.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.WebClient-Help.xml
 Locale: en-US
@@ -79,7 +79,7 @@ This example returns all mail-enabled public folders that begin with the word Ma
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the GUID or public folder name that represents a specific public folder. You can also include the path using the format \\TopLevelPublicFolder\\PublicFolder.
 
@@ -99,7 +99,7 @@ Accept wildcard characters: False
 
 ### -Anr
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Anr parameter specifies a string on which to perform an ambiguous name resolution (ANR) search. You can specify a partial string and search for objects with an attribute that matches that string. The default attributes searched are:
 
@@ -123,7 +123,7 @@ Accept wildcard characters: False
 
 ### -Credential
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Credential parameter specifies the username and password that's used to run this command. Typically, you use this parameter in scripts or when you need to provide different credentials that have the required permissions.
 
@@ -143,7 +143,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -163,7 +163,7 @@ Accept wildcard characters: False
 
 ### -Filter
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Filter parameter uses OPATH syntax to filter the results by the specified properties and values. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`.
 
@@ -190,7 +190,7 @@ Accept wildcard characters: False
 
 ### -IgnoreDefaultScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange PowerShell session, and to use the entire forest as the scope. You don't need to specify a value with this switch.
 
@@ -233,7 +233,7 @@ Accept wildcard characters: False
 
 ### -ReadFromDomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -257,7 +257,7 @@ Accept wildcard characters: False
 
 ### -ResultSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
 
@@ -300,7 +300,7 @@ Accept wildcard characters: False
 
 ### -SortBy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SortBy parameter specifies the property to sort the results by. You can sort by only one property at a time. The results are sorted in ascending order.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailUser.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailUser.md
index 8198063763..92601103eb 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailUser.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailUser.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -101,7 +101,7 @@ This example returns detailed information for the mail user named Ed.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the mail user that you want to view. You can use any value that uniquely identifies the mail user. For example:
 
@@ -126,7 +126,7 @@ Accept wildcard characters: False
 
 ### -Anr
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Anr parameter specifies a string on which to perform an ambiguous name resolution (ANR) search. You can specify a partial string and search for objects with an attribute that matches that string. The default attributes searched are:
 
@@ -150,7 +150,7 @@ Accept wildcard characters: False
 
 ### -Credential
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -172,7 +172,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -192,7 +192,7 @@ Accept wildcard characters: False
 
 ### -Filter
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Filter parameter uses OPATH syntax to filter the results by the specified properties and values. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`.
 
@@ -239,7 +239,7 @@ Accept wildcard characters: False
 
 ### -IgnoreDefaultScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -284,7 +284,7 @@ Accept wildcard characters: False
 
 ### -OrganizationalUnit
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The OrganizationalUnit parameter filters the results based on the object's location in Active Directory. Only objects that exist in the specified location are returned. Valid input for this parameter is an organizational unit (OU) or domain that's returned by the Get-OrganizationalUnit cmdlet. You can use any value that uniquely identifies the OU or domain. For example:
 
@@ -307,7 +307,7 @@ Accept wildcard characters: False
 
 ### -ReadFromDomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -331,7 +331,7 @@ Accept wildcard characters: False
 
 ### -ResultSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
 
@@ -369,7 +369,7 @@ Accept wildcard characters: False
 
 ### -SortBy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The SortBy parameter specifies the property to sort the results by. You can sort by only one property at a time. The results are sorted in ascending order.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxImportRequestStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxImportRequestStatistics.md
index 9d553d04e1..7712bbbfc7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxImportRequestStatistics.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxImportRequestStatistics.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -110,7 +110,7 @@ This example returns additional information for all the import requests that hav
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the identity of the import request. By default, import requests are named `<alias>\MailboxImportX` (where X = 0-9). If you specified a name when you created the import request, use the following syntax: `Alias\Name`.
 
@@ -152,7 +152,7 @@ Accept wildcard characters: False
 
 ### -RequestQueue
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -180,7 +180,7 @@ Accept wildcard characters: False
 
 ### -Diagnostic
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -202,7 +202,7 @@ Accept wildcard characters: False
 
 ### -DiagnosticArgument
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -242,7 +242,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -262,7 +262,7 @@ Accept wildcard characters: False
 
 ### -IncludeReport
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IncludeReport switch specifies whether to return additional details, which can be used for troubleshooting. You don't need to specify a value with this switch.
 
@@ -300,7 +300,7 @@ Accept wildcard characters: False
 
 ### -RequestGuid
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -322,7 +322,7 @@ Accept wildcard characters: False
 
 ### -ReportOnly
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ReportOnly switch returns the results as an array of report entries (encoded strings). You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxJunkEmailConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxJunkEmailConfiguration.md
index 4f7d3ec93d..982e3fe365 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxJunkEmailConfiguration.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxJunkEmailConfiguration.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -69,7 +69,7 @@ To return all mailboxes where the junk email rule is enabled, change the value $
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the mailbox that you want to view. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -100,7 +100,7 @@ Accept wildcard characters: True
 
 ### -Credential
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Credential parameter specifies the username and password that's used to run this command. Typically, you use this parameter in scripts or when you need to provide different credentials that have the required permissions.
 
@@ -120,7 +120,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -140,7 +140,7 @@ Accept wildcard characters: False
 
 ### -ReadFromDomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ReadFromDomainController switch specifies that information should be read from a domain controller in the user's domain. You don't need to specify a value with this switch.
 
@@ -162,7 +162,7 @@ Accept wildcard characters: False
 
 ### -ResultSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxLocation.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxLocation.md
index 13d0a15a7b..d731ec4912 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxLocation.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxLocation.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -75,7 +75,7 @@ In Exchange Server or Exchange Online, this example returns the mailbox location
 
 ### -Database
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -101,7 +101,7 @@ Accept wildcard characters: False
 
 ### -Identity
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the mailbox location object that you want to view. The value uses the either of the following formats:
 
@@ -155,7 +155,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -198,7 +198,7 @@ Accept wildcard characters: False
 
 ### -MailboxLocationType
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MailboxLocationType filters the results by the type of mailbox. Valid values are:
 
@@ -224,7 +224,7 @@ Accept wildcard characters: False
 
 ### -ResultSize
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
 
@@ -242,7 +242,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxMessageConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxMessageConfiguration.md
index c198362e18..f3e799f010 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxMessageConfiguration.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxMessageConfiguration.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -60,7 +60,7 @@ This example returns the Outlook on the web settings for Tony's mailbox and spec
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the mailbox. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -89,7 +89,7 @@ Accept wildcard characters: False
 
 ### -Credential
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Credential parameter specifies the username and password to use to access the mailbox.
 
@@ -109,7 +109,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -129,7 +129,7 @@ Accept wildcard characters: False
 
 ### -ReadFromDomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ReadFromDomainController switch specifies that information should be read from a domain controller in the user's domain. You don't need to specify a value with this switch.
 
@@ -151,7 +151,7 @@ Accept wildcard characters: False
 
 ### -ResultSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxPermission.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxPermission.md
index 6a41b26466..74ca8ef07c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxPermission.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxPermission.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -99,7 +99,7 @@ This example returns the owner information for the resource mailbox Room222.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the mailbox you want to view. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -128,7 +128,7 @@ Accept wildcard characters: False
 
 ### -Credential
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Credential parameter specifies the username and password that's used to run this command. Typically, you use this parameter in scripts or when you need to provide different credentials that have the required permissions.
 
@@ -148,7 +148,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -250,7 +250,7 @@ Accept wildcard characters: False
 
 ### -Owner
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Owner switch returns the owner information for the mailbox that's specified by the Identity parameter. You don't need to specify a value with this switch.
 
@@ -270,7 +270,7 @@ Accept wildcard characters: False
 
 ### -ReadFromDomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ReadFromDomainController switch specifies that information should be read from a domain controller in the user's domain. You don't need to specify a value with this switch.
 
@@ -292,7 +292,7 @@ Accept wildcard characters: False
 
 ### -ResultSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
 
@@ -352,7 +352,7 @@ Accept wildcard characters: False
 
 ### -User
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The User parameter filters the results by who has permissions to the mailbox that's specified by the Identity parameter. You can specify the following types of users or groups (security principals) for this parameter:
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxRegionalConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxRegionalConfiguration.md
index 23813b7c6f..0947fd27bf 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxRegionalConfiguration.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxRegionalConfiguration.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -74,7 +74,7 @@ This example returns the regional settings for Alice Jakobsen's mailbox and also
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the mailbox that you want to view. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -123,7 +123,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -183,7 +183,7 @@ Accept wildcard characters: False
 
 ### -VerifyDefaultFolderNameLanguage
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The VerifyDefaultFolderNameLanguage switch verifies that the default folder names are localized in the language that's specified for the mailbox (the Language property value). You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxRepairRequest.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxRepairRequest.md
index b7e31ea498..2f7356ae9a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxRepairRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxRepairRequest.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -85,7 +85,7 @@ This example uses the Database and StoreMailbox parameters to display the Identi
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the mailbox repair request to display information about. Mailbox repair requests are identified by a complex GUID that is created when a new mailbox repair request is created. This GUID consists of a database ID, a Request ID and a job ID. The format is `DatabaseGuid\RequestGuid\JobGuid`.
 
@@ -105,7 +105,7 @@ Accept wildcard characters: False
 
 ### -Database
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Database parameter returns mailbox repair requests for all mailboxes on the specified database. You can use any value that uniquely identifies the database. For example:
 
@@ -129,7 +129,7 @@ Accept wildcard characters: False
 
 ### -Mailbox
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Mailbox parameter specifies the mailbox that you want to get mailbox repair request information about. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -160,7 +160,7 @@ Accept wildcard characters: False
 
 ### -StoreMailbox
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The StoreMailbox parameter specifies the mailbox GUID of the mailbox that you want to get mailbox repair request information about. Use this parameter with the Database parameter.
 
@@ -180,7 +180,7 @@ Accept wildcard characters: False
 
 ### -Archive
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Archive switch displays information about the associated archive mailbox if the archive mailbox was included when the mailbox repair request was created. You don't need to specify a value with this switch.
 
@@ -202,7 +202,7 @@ Accept wildcard characters: False
 
 ### -Detailed
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 Use the Detailed parameter to display mailbox-level repair tasks associated with the repair request. You don't need to specify a value with this switch.
 
@@ -220,7 +220,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxRestoreRequest.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxRestoreRequest.md
index 9f68aae6cd..cec72542e6 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxRestoreRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxRestoreRequest.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -82,7 +82,7 @@ This example returns all restore requests that have the name RestoreToMBD01 wher
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the identity of the restore request. The Identity parameter consists of the alias of the mailbox to be restored and the name that was specified when the restore request was created. The identity of the restore request uses the following syntax: `Alias\Name`.
 
@@ -104,7 +104,7 @@ Accept wildcard characters: False
 
 ### -BatchName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The BatchName parameter specifies the name given to a batch of restore requests.
 
@@ -124,7 +124,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -144,7 +144,7 @@ Accept wildcard characters: False
 
 ### -HighPriority
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The HighPriority parameter filters the results based on the Priority value that was assigned when the request was created. Valid input for this parameter is $true or $false. Here's how these values filter the results:
 
@@ -167,7 +167,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Name parameter specifies that any restore request that has the specified name is returned.
 
@@ -191,7 +191,7 @@ Accept wildcard characters: False
 
 ### -RequestQueue
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -217,7 +217,7 @@ Accept wildcard characters: False
 
 ### -ResultSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
 
@@ -235,7 +235,7 @@ Accept wildcard characters: False
 
 ### -SourceDatabase
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -261,7 +261,7 @@ Accept wildcard characters: False
 
 ### -Status
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Status parameter filters the results based on status. You can use the following values:
 
@@ -292,7 +292,7 @@ Accept wildcard characters: False
 
 ### -Suspend
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Suspend parameter specifies whether to return requests that have been suspended. Valid input for this parameter is $true or $false.
 
@@ -338,7 +338,7 @@ Accept wildcard characters: False
 
 ### -TargetMailbox
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The TargetMailbox parameter specifies the identity of the target mailbox. You can use the following values:
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxRestoreRequestStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxRestoreRequestStatistics.md
index 9ef9b9e6e7..0420909f8f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxRestoreRequestStatistics.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxRestoreRequestStatistics.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -106,7 +106,7 @@ This example returns additional information for all the restore requests that ha
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the identity of the restore request. The Identity parameter consists of the alias of the mailbox to be restored and the name that was specified when the restore request was created. The identity of the restore request uses the following syntax: `Alias\Name`.
 
@@ -150,7 +150,7 @@ Accept wildcard characters: False
 
 ### -RequestQueue
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -178,7 +178,7 @@ Accept wildcard characters: False
 
 ### -IncludeReport
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IncludeReport switch specifies whether to return additional details, which can be used for troubleshooting. You don't need to specify a value with this switch.
 
@@ -196,7 +196,7 @@ Accept wildcard characters: False
 
 ### -RequestGuid
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -216,7 +216,7 @@ Accept wildcard characters: False
 
 ### -Diagnostic
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -238,7 +238,7 @@ Accept wildcard characters: False
 
 ### -DiagnosticArgument
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -278,7 +278,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -318,7 +318,7 @@ Accept wildcard characters: False
 
 ### -ReportOnly
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ReportOnly switch returns the results as an array of report entries (encoded strings). You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxSearch.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxSearch.md
index 1dd6099661..98b2f45979 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxSearch.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxSearch.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
 Locale: en-US
@@ -70,7 +70,7 @@ Get-MailboxSearch "Project Hamilton" | Format-List
 
 This example retrieves all properties for the mailbox search Project Hamilton.
 
-The Identity parameter is a positional parameter. Positional parameters can be used without the label (Identity). For more information about positional parameters, see [About Parameters](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_parameters).
+The Identity parameter is positional, which means you can use it without the -Identity label in the supported location in the command (in this case, first). For more information about positional parameters, see [About Parameters](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_parameters).
 
 ### Example 3
 ```powershell
@@ -85,7 +85,7 @@ This example retrieves the In-Place Holds that a user is placed on. The first co
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the name of the search query. If a name isn't provided, all mailbox search queries are returned.
 
@@ -114,7 +114,7 @@ Accept wildcard characters: False
 
 ### -InPlaceHoldIdentity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The InPlaceHoldIdentity parameter specifies the GUID of an In-Place Hold. Use this parameter to search for an In-Place Hold that a user is placed on. GUIDs of all In-Place Holds that a user is placed on are added to the user's InPlaceHolds property. You can retrieve the property by using the Get-Mailbox cmdlet.
 
@@ -132,7 +132,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -152,7 +152,7 @@ Accept wildcard characters: False
 
 ### -ResultSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
 
@@ -170,7 +170,7 @@ Accept wildcard characters: False
 
 ### -ShowDeletionInProgressSearches
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is reserved for internal Microsoft use.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxServer.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxServer.md
index 4c6925717f..ec9c99d48b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxServer.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxServer.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -53,7 +53,7 @@ This example returns detailed information about the Mailbox server named Server1
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the Mailbox server that you want to view. You can use any value that uniquely identifies the Mailbox server. For example:
 
@@ -75,7 +75,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -93,7 +93,7 @@ Accept wildcard characters: False
 
 ### -Status
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Status switch specifies whether to include additional property values in the results, for example, the Locale value. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxSpellingConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxSpellingConfiguration.md
index fc0ca8f8a2..ba8137229d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxSpellingConfiguration.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxSpellingConfiguration.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -64,7 +64,7 @@ This example returns the Outlook on the web spelling checker options for Tony's
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the mailbox that you want to view. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -93,7 +93,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxStatistics.md
index fa20e834d4..6d6ca0714b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxStatistics.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxStatistics.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -150,7 +150,7 @@ This example returns the detailed move history and a verbose detailed move repor
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the mailbox that you want to return statistics for. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -179,7 +179,7 @@ Accept wildcard characters: False
 
 ### -StoreMailboxIdentity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -204,7 +204,7 @@ Accept wildcard characters: False
 
 ### -Archive
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Archive switch specifies whether to return mailbox statistics for the archive mailbox that's associated with the mailbox. You don't need to specify a value with this switch.
 
@@ -222,7 +222,7 @@ Accept wildcard characters: False
 
 ### -CopyOnServer
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -251,7 +251,7 @@ Accept wildcard characters: False
 
 ### -Database
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -277,7 +277,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -297,7 +297,7 @@ Accept wildcard characters: False
 
 ### -Filter
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -328,7 +328,7 @@ Accept wildcard characters: False
 
 ### -IncludeMoveHistory
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IncludeMoveHistory switch specifies whether to return additional information about the mailbox that includes the history of a completed move request, such as status, flags, target database, bad items, start times, end times, duration that the move request was in various stages, and failure codes. You don't need to specify a value with this switch.
 
@@ -346,7 +346,7 @@ Accept wildcard characters: False
 
 ### -IncludeMoveReport
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IncludeMoveReport switch specifies whether to return a verbose detailed move report for a completed move request, such as server connections and move stages. You don't need to specify a value with this switch.
 
@@ -366,7 +366,7 @@ Accept wildcard characters: False
 
 ### -IncludePassive
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -410,7 +410,7 @@ Accept wildcard characters: False
 
 ### -IncludeQuarantineDetails
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -432,7 +432,7 @@ Accept wildcard characters: False
 
 ### -NoADLookup
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -454,7 +454,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxTransportService.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxTransportService.md
index d93f8c7443..6baf5e6e72 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxTransportService.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxTransportService.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -52,7 +52,7 @@ This example retrieves the detailed transport configuration information for the
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the server that you want to view.
 
@@ -70,7 +70,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxUserConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxUserConfiguration.md
index c5a73d9071..20cc71b95a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MailboxUserConfiguration.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MailboxUserConfiguration.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -52,7 +52,7 @@ This example returns detailed information for the specified user configuration i
 
 ### -Identity
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the user configuration item that you want to view. This parameter uses the syntax MailboxFolder\ItemName:
 
@@ -73,7 +73,7 @@ Accept wildcard characters: False
 
 ### -Mailbox
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Mailbox parameter specifies the mailbox that contains the user configuration items you want to view. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -102,7 +102,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is reserved for internal Microsoft use.
 
@@ -120,7 +120,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -140,7 +140,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is reserved for internal Microsoft use.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MalwareFilterPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-MalwareFilterPolicy.md
index 70fc40e4e3..fe9000d741 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MalwareFilterPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MalwareFilterPolicy.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -52,7 +52,7 @@ This example retrieves detailed configuration information for the malware filter
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the malware filter policy that you want to view. You can use any value that uniquely identifies the policy. For example, you can use the name, GUID or distinguished name (DN) of the malware filter policy.
 
@@ -70,7 +70,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MalwareFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-MalwareFilterRule.md
index 851fe8bee1..7b16455434 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MalwareFilterRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MalwareFilterRule.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -51,7 +51,7 @@ This example retrieves detailed configuration information for the malware filter
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the malware filter rule that you want to view. You can use any value that uniquely identifies the rule. For example, you can use the name, GUID or distinguished name (DN) of the malware filter rule.
 
@@ -69,7 +69,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -89,7 +89,7 @@ Accept wildcard characters: False
 
 ### -State
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The State parameter filters the results by enabled or disabled malware filter rules. Valid input for this parameter is Enabled or Disabled.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MalwareFilteringServer.md b/exchange/exchange-ps/ExchangePowerShell/Get-MalwareFilteringServer.md
index a5aa694930..53a20c6cae 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MalwareFilteringServer.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MalwareFilteringServer.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -50,7 +50,7 @@ This example returns the detailed Exchange Malware agent settings on a Mailbox s
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the server where you want to view the anti-malware settings. You can use any value that uniquely identifies the server. For example:
 
@@ -73,7 +73,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ManagedFolderMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-ManagedFolderMailboxPolicy.md
index 7c810e181a..04ff9158a5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ManagedFolderMailboxPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ManagedFolderMailboxPolicy.md
@@ -41,7 +41,7 @@ Get-ManagedFolderMailboxPolicy "PM Storage Template"
 
 This example returns all the attributes of the managed folder mailbox policy PM Storage Template.
 
-The Identity parameter is a positional parameter. Positional parameters can be used without the label (Identity). For more information about positional parameters, see [About Parameters](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_parameters).
+The Identity parameter is positional, which means you can use it without the -Identity label in the supported location in the command (in this case, first).  For more information about positional parameters, see [About Parameters](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_parameters).
 
 ## PARAMETERS
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ManagementRole.md b/exchange/exchange-ps/ExchangePowerShell/Get-ManagementRole.md
index 67b161bb48..c5b12d0a70 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ManagementRole.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ManagementRole.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -114,7 +114,7 @@ This example lists the immediate children of the Mail Recipients role. Only the
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The Identity parameter specifies the role you want to view. If the role you want to view contains spaces, enclose the name in quotation marks ("). You can use the wildcard character (\*) and a partial role name to match multiple roles.
 
@@ -132,7 +132,7 @@ Accept wildcard characters: False
 
 ### -GetChildren
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The GetChildren parameter retrieves a list of all the roles that were created based on the parent role specified in the Identity parameter. You don't need to specify a value with this switch.
 
@@ -154,7 +154,7 @@ Accept wildcard characters: False
 
 ### -Recurse
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The Recurse parameter retrieves a list of all the roles that were created based on the parent role specified in the Identity parameter. You don't need to specify a value with this switch.
 
@@ -176,7 +176,7 @@ Accept wildcard characters: False
 
 ### -Cmdlet
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The Cmdlet parameter returns a list of all roles that include the specified cmdlet.
 
@@ -194,7 +194,7 @@ Accept wildcard characters: False
 
 ### -CmdletParameters
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The CmdletParameters parameter returns a list of all roles that include the specified parameter or parameters. You can specify more than one parameter by separating each parameter with a comma. If you specify multiple parameters, only the roles that include all of the specified parameters are returned.
 
@@ -212,7 +212,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -232,7 +232,7 @@ Accept wildcard characters: False
 
 ### -RoleType
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The RoleType parameter returns a list of roles that match the specified role type. For a list of valid role types, see [Understanding management roles](https://learn.microsoft.com/exchange/understanding-management-roles-exchange-2013-help).
 
@@ -250,7 +250,7 @@ Accept wildcard characters: False
 
 ### -Script
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The Script parameter returns a list of all roles that include the specified script.
 
@@ -268,7 +268,7 @@ Accept wildcard characters: False
 
 ### -ScriptParameters
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The ScriptParameters parameter returns a list of all roles that include the specified parameter or parameters. You can specify more than one parameter by separating each parameter with a comma. If you specify multiple parameters, only the roles that include all of the specified parameters are returned.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ManagementRoleAssignment.md b/exchange/exchange-ps/ExchangePowerShell/Get-ManagementRoleAssignment.md
index e3ee03a9c7..c9ef714304 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ManagementRoleAssignment.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ManagementRoleAssignment.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -133,7 +133,7 @@ This example retrieves all the role assignments that can modify the database Con
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the name of the role assignment to retrieve. If the name of the role assignment contains spaces, enclose it in quotation marks ("). If the RoleAssignee parameter is used, you can't use the Identity parameter.
 
@@ -151,7 +151,7 @@ Accept wildcard characters: False
 
 ### -AssignmentMethod
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The AssignmentMethod parameter specifies the type of role assignment to include in the results returned by the cmdlet. You can specify one or more of the following values:
 
@@ -178,7 +178,7 @@ Accept wildcard characters: False
 
 ### -ConfigWriteScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ConfigWriteScope parameter specifies the type of management configuration scope to include in the results returned by the cmdlet. The valid values are None, OrganizationConfig, CustomConfigScope, and ExclusiveConfigScope.
 
@@ -196,7 +196,7 @@ Accept wildcard characters: False
 
 ### -CustomConfigWriteScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -220,7 +220,7 @@ Accept wildcard characters: False
 
 ### -CustomRecipientWriteScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The CustomRecipientWriteScope parameter returns only the regular role assignments that include the specified recipient-based regular scope.
 
@@ -242,7 +242,7 @@ Accept wildcard characters: False
 
 ### -Delegating
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Delegating parameter specifies whether delegating or regular role assignments should be returned.
 
@@ -262,7 +262,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -282,7 +282,7 @@ Accept wildcard characters: False
 
 ### -Enabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Enabled parameter specifies whether enabled or disabled role assignments should be returned. To return enabled role assignments, specify a value of $true. To return disabled role assignments, specify a value of $false.
 
@@ -300,7 +300,7 @@ Accept wildcard characters: False
 
 ### -Exclusive
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Exclusive parameter specifies whether exclusive or regular role assignments should be returned.
 
@@ -320,7 +320,7 @@ Accept wildcard characters: False
 
 ### -ExclusiveConfigWriteScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -344,7 +344,7 @@ Accept wildcard characters: False
 
 ### -ExclusiveRecipientWriteScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ExclusiveRecipientWriteScope parameter returns only the exclusive role assignments that include the specified recipient-based exclusive scope.
 
@@ -366,7 +366,7 @@ Accept wildcard characters: False
 
 ### -GetEffectiveUsers
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The GetEffectiveUsers switch specifies that the command should show the list of users in the role groups, role assignment policies, or USGs that are associated with the role assignment. You don't need to specify a value with this switch.
 
@@ -386,7 +386,7 @@ Accept wildcard characters: False
 
 ### -RecipientAdministrativeUnitScope
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter is functional only in the cloud-based service.
 
@@ -428,7 +428,7 @@ Accept wildcard characters: False
 
 ### -RecipientOrganizationalUnitScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The RecipientOrganizationalUnitScope parameter returns only the role assignments that include the specified organizational unit (OU). If the OU tree contains spaces, enclose it in quotation marks (").
 
@@ -446,7 +446,7 @@ Accept wildcard characters: False
 
 ### -RecipientWriteScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The RecipientWriteScope parameter returns only the role assignments associated with the recipient scope restriction type specified. The valid values are None, MyGAL, Self, OU, CustomRecipientScope, MyDistributionGroups and ExclusiveRecipientScope.
 
@@ -464,7 +464,7 @@ Accept wildcard characters: False
 
 ### -Role
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Role parameter returns only the role assignments associated with the specified management role. If the name of the role contains spaces, enclose it in quotation marks (").
 
@@ -482,7 +482,7 @@ Accept wildcard characters: False
 
 ### -RoleAssignee
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The RoleAssignee parameter specifies the role group, assignment policy, user, or universal security group (USG) for which you want to view role assignments. If the RoleAssignee parameter is used, you can't use the Identity parameter.
 
@@ -504,7 +504,7 @@ Accept wildcard characters: False
 
 ### -RoleAssigneeType
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The RoleAssigneeType parameter specifies the type of role assignee to return. The valid values are User, SecurityGroup, RoleAssignmentPolicy, ForeignSecurityPrincipal, RoleGroup, LinkedRoleGroup and Computer.
 
@@ -522,7 +522,7 @@ Accept wildcard characters: False
 
 ### -WritableDatabase
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -548,7 +548,7 @@ Accept wildcard characters: False
 
 ### -WritableRecipient
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WritableRecipient parameter specifies the recipient object you want to test to determine which role assignments allow it to be modified. The command takes into account the roles and scopes associated with each role assignment. If the recipient name contains spaces, enclose it in quotation marks (").
 
@@ -568,7 +568,7 @@ Accept wildcard characters: False
 
 ### -WritableServer
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ManagementRoleEntry.md b/exchange/exchange-ps/ExchangePowerShell/Get-ManagementRoleEntry.md
index 6069d86005..2653a15989 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ManagementRoleEntry.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ManagementRoleEntry.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -65,7 +65,7 @@ This example retrieves the Tier 2 Help Desk\\Set-Mailbox role entry and pipes th
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the role entry that you want to view. This parameter uses the syntax: `<management role>\<role entry name>` (for example, `CustomRole\Set-Mailbox`).
 
@@ -89,7 +89,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -109,7 +109,7 @@ Accept wildcard characters: False
 
 ### -Parameters
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Parameters parameter includes only the role entries that contain the parameters specified. You can specify multiple parameters, separated by commas. You can use the wildcard character (\*) with partial parameter names to retrieve all parameters that match the value you specify.
 
@@ -129,7 +129,7 @@ Accept wildcard characters: False
 
 ### -PSSnapinName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The PSSnapinName parameter specifies the Windows PowerShell snap-in that contains the role entry to return. Use the Get-PSSnapin cmdlet to retrieve a list of available Windows PowerShell snap-ins.
 
@@ -167,7 +167,7 @@ Accept wildcard characters: False
 
 ### -Type
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Type parameter specifies the type of role entry to return. The valid values for the Type parameter are any combination of the following parameters, separated by commas: Cmdlet, Script and ApplicationPermission.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ManagementScope.md b/exchange/exchange-ps/ExchangePowerShell/Get-ManagementScope.md
index e3d35c1cde..3b5949b7df 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ManagementScope.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ManagementScope.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -70,7 +70,7 @@ This example retrieves a list of exclusive scopes.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the name of the management scope to return. If the management scope name contains spaces, enclose it in quotation marks (").
 
@@ -88,7 +88,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -108,7 +108,7 @@ Accept wildcard characters: False
 
 ### -Exclusive
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Exclusive parameter specifies whether exclusive scopes should be returned. If the Exclusive parameter isn't specified, regular scopes and exclusive scopes are returned. If the Exclusive parameter is set to $True, only exclusive scopes are returned. If the Exclusive parameter is set to $False, only regular scopes are returned. The valid values are $True and $False.
 
@@ -126,7 +126,7 @@ Accept wildcard characters: False
 
 ### -Orphan
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Orphan switch specifies whether to return only management scopes that aren't associated with role assignments. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MapiVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Get-MapiVirtualDirectory.md
index 8d63f79498..572f31c8f5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MapiVirtualDirectory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MapiVirtualDirectory.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -73,7 +73,7 @@ This example returns a summary list of all MAPI virtual directories in the clien
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the MAPI virtual directory that you want to view. You can use any value that uniquely identifies the virtual directory. For example:
 
@@ -99,7 +99,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Exchange server that hosts the virtual directory. You can use any value that uniquely identifies the server. For example:
 
@@ -124,7 +124,7 @@ Accept wildcard characters: False
 
 ### -ADPropertiesOnly
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ADPropertiesOnly switch specifies whether to return only the virtual directory properties that are stored in Active Directory. You don't need to specify a value with this switch.
 
@@ -144,7 +144,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-Message.md b/exchange/exchange-ps/ExchangePowerShell/Get-Message.md
index 2aa1848340..3ce55a4842 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-Message.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-Message.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -99,7 +99,7 @@ This example displays all messages queued on the server named Server01. The resu
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the message. Valid input for this parameter uses the syntax Server\\Queue\\MessageInteger or Queue\\MessageInteger or MessageInteger, for example, Mailbox01\\contoso.com\\5 or 10. For details about message identity, see [Message identity](https://learn.microsoft.com/Exchange/mail-flow/queues/queues-and-messages-in-powershell#message-identity).
 
@@ -117,7 +117,7 @@ Accept wildcard characters: False
 
 ### -BookmarkIndex
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The BookmarkIndex parameter specifies the position in the result set where the displayed results start. The value of this parameter is a 1-based index in the total result set. The BookmarkIndex parameter can't be used with the BookmarkObject parameter.
 
@@ -135,7 +135,7 @@ Accept wildcard characters: False
 
 ### -BookmarkObject
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The BookmarkObject parameter specifies the object in the result set where the displayed results start. The BookmarkObject parameter can't be used with the BookmarkIndex parameter.
 
@@ -153,7 +153,7 @@ Accept wildcard characters: False
 
 ### -Filter
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Filter parameter specifies one or more messages by using OPATH filter syntax. The OPATH filter includes a message property name followed by a comparison operator and value (for example, `"FromAddress -like '*@contoso.com'"`). For details about filterable message properties and comparison operators, see [Properties of messages in queues](https://learn.microsoft.com/Exchange/mail-flow/queues/message-properties) and [Find queues and messages in queues in the Exchange Management Shell](https://learn.microsoft.com/Exchange/mail-flow/queues/queues-and-messages-in-powershell).
 
@@ -173,7 +173,7 @@ Accept wildcard characters: False
 
 ### -IncludeBookmark
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IncludeBookmark parameter specifies whether to include the bookmark object when the query results are displayed. The IncludeBookmark parameter is valid when it's used with the BookmarkObject or BookmarkIndex parameters. If you don't specify a value for the IncludeBookmark parameter, the default value of $true is used.
 
@@ -191,7 +191,7 @@ Accept wildcard characters: False
 
 ### -IncludeComponentLatencyInfo
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IncludeComponentLatencyInfo switch specifies whether the information about component latency is included in the message properties. You don't need to specify a value with this switch.
 
@@ -211,7 +211,7 @@ Accept wildcard characters: False
 
 ### -IncludeRecipientInfo
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IncludeRecipientInfo switch specifies whether to display the message recipients in the Recipients field. You don't need to specify a value with this switch.
 
@@ -243,7 +243,7 @@ Accept wildcard characters: False
 
 ### -Queue
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Queue parameter specifies the identity of the queue that contains the messages that you want to display. Valid input for this parameter uses the syntax `<Server>\<Queue>` or `<Queue>`, for example, Mailbox01\\contoso.com or Unreachable. For details about queue identity, see the "Queue identity" section in [Find queues and messages in queues in the Exchange Management Shell](https://learn.microsoft.com/exchange/mail-flow/queues/queues-and-messages-in-powershell#queue-identity).
 
@@ -263,7 +263,7 @@ Accept wildcard characters: False
 
 ### -ResultSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
 
@@ -281,7 +281,7 @@ Accept wildcard characters: False
 
 ### -ReturnPageInfo
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ReturnPageInfo parameter is a hidden parameter. Use it to return information about the total number of results and the index of the first object of the current page. The default value is $false.
 
@@ -299,7 +299,7 @@ Accept wildcard characters: False
 
 ### -SearchForward
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SearchForward parameter specifies whether to search forward or backward in the result set. The default value is $true. This value causes the result page to be calculated forward from either the start of the result set or forward from a bookmark if specified.
 
@@ -317,7 +317,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
 
@@ -344,7 +344,7 @@ Accept wildcard characters: False
 
 ### -SortOrder
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SortOrder parameter specifies an array of message properties used to control the sort order of the result set. Separate each property by using a comma. Prepend a plus sign (+) symbol to the beginning of the property name to display the results in ascending order. Prepend a minus sign (-) symbol to the beginning of the property name to display the results in descending order.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MessageCategory.md b/exchange/exchange-ps/ExchangePowerShell/Get-MessageCategory.md
index 3eaf7fb54c..fdd042b6bd 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MessageCategory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MessageCategory.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -46,7 +46,7 @@ This example retrieves message categories from the mailbox User1.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the name of the message category to be retrieved.
 
@@ -64,7 +64,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -84,7 +84,7 @@ Accept wildcard characters: False
 
 ### -Mailbox
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Mailbox parameter specifies the mailbox that you want to view. You can use any value that uniquely identifies the mailbox. For example:
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MessageClassification.md b/exchange/exchange-ps/ExchangePowerShell/Get-MessageClassification.md
index 4dc5651fcc..b1e4ff3155 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MessageClassification.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MessageClassification.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -44,7 +44,7 @@ This example lists all message classifications in your organization.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the message classification that you want to view. You can use any value that uniquely identifies the message classification. For example:
 
@@ -66,7 +66,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -88,7 +88,7 @@ Accept wildcard characters: False
 
 ### -IncludeLocales
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IncludeLocales switch specifies whether to return message classification locale information in the results. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MessageTrackingLog.md b/exchange/exchange-ps/ExchangePowerShell/Get-MessageTrackingLog.md
index d2f4eae656..c97f3baf2a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MessageTrackingLog.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MessageTrackingLog.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -76,7 +76,7 @@ This example searches the message tracking logs on the Mailbox server named Mail
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -96,7 +96,7 @@ Accept wildcard characters: False
 
 ### -End
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The End parameter specifies the end date and time of the date range. Message delivery information is returned up to, but not including, the specified date and time.
 
@@ -116,7 +116,7 @@ Accept wildcard characters: False
 
 ### -EventId
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The EventId parameter filters the message tracking log entries by the value of the EventId field. The EventId value classifies each message event. Example values include DSN, Defer, Deliver, Send, or Receive.
 
@@ -134,7 +134,7 @@ Accept wildcard characters: False
 
 ### -InternalMessageId
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The InternalMessageId parameter filters the message tracking log entries by the value of the InternalMessageId field. The InternalMessageId value is a message identifier that's assigned by the Exchange server that's currently processing the message.
 
@@ -154,7 +154,7 @@ Accept wildcard characters: False
 
 ### -MessageId
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MessageId parameter filters the message tracking log entries by the value of the MessageId field. The value of MessageId corresponds to the value of the Message-Id: header field in the message. If the Message-ID header field is blank or doesn't exist, an arbitrary value is assigned. Be sure to include the full MessageId string (which might include angle brackets) and enclose the value in quotation marks (for example, "<d9683b4c-127b-413a-ae2e-fa7dfb32c69d@contoso.com>").
 
@@ -172,7 +172,7 @@ Accept wildcard characters: False
 
 ### -MessageSubject
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MessageSubject parameter filters the message tracking log entries by the value of the message subject. The value of the MessageSubject parameter automatically supports partial matches without using wildcards or special characters. For example, if you specify the MessageSubject value sea, the results include messages with Seattle in the subject. By default, message subjects are stored in the message tracking logs.
 
@@ -190,7 +190,7 @@ Accept wildcard characters: False
 
 ### -Recipients
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Recipients parameter filters the message tracking log entries by the SMTP email address of the message recipients. Multiple recipients in a single message are logged in a single message tracking log entry. Unexpanded distribution group recipients are logged by using the group's SMTP email address. You can specify multiple recipients using an array of email addresses.
 
@@ -208,7 +208,7 @@ Accept wildcard characters: False
 
 ### -Reference
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Reference parameter filters the message tracking log entries by the value of the Reference field. The Reference field contains additional information for specific types of events. For example, the Reference field value for a DSN message tracking entry contains the InternalMessageId value of the message that caused the DSN. For many types of events, the value of Reference is blank.
 
@@ -226,7 +226,7 @@ Accept wildcard characters: False
 
 ### -ResultSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
 
@@ -244,7 +244,7 @@ Accept wildcard characters: False
 
 ### -Sender
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Sender parameter filters the message tracking log entries by the sender's SMTP email address.
 
@@ -262,7 +262,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
 
@@ -287,7 +287,7 @@ Accept wildcard characters: False
 
 ### -Start
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Start parameter specifies the start date and time of the date range.
 
@@ -307,7 +307,7 @@ Accept wildcard characters: False
 
 ### -NetworkMessageId
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The NetworkMessageId parameter filters the message tracking log entries by the value of the NetworkMessageId field. This field contains a unique message ID value that persists across copies of the message that might be created due to bifurcation or distribution group expansion. An example value is 1341ac7b13fb42ab4d4408cf7f55890f.
 
@@ -325,7 +325,7 @@ Accept wildcard characters: False
 
 ### -Source
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Source parameter filters the message tracking log entries by the value of the Source field. These values indicate the transport component that's responsible for the message tracking event. For more information, see [Source values in the message tracking log](https://learn.microsoft.com/Exchange/mail-flow/transport-logs/message-tracking#source-values-in-the-message-tracking-log).
 
@@ -343,7 +343,7 @@ Accept wildcard characters: False
 
 ### -TransportTrafficType
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TransportTrafficType parameter filters the message tracking log entries by the value of the TransportTrafficType field. However, this field isn't interesting for on-premises Exchange organizations.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MessageTrackingReport.md b/exchange/exchange-ps/ExchangePowerShell/Get-MessageTrackingReport.md
index 67532cc6d9..dbe1ef3dea 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MessageTrackingReport.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MessageTrackingReport.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -69,7 +69,7 @@ This example searches the message tracking data for the specific message trackin
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the message tracking report ID that you want to view.
 
@@ -89,7 +89,7 @@ Accept wildcard characters: False
 
 ### -BypassDelegateChecking
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The BypassDelegateChecking switch allows Help desk staff and administrators to retrieve message tracking reports for any user. You don't need to specify a value with this switch.
 
@@ -109,7 +109,7 @@ Accept wildcard characters: False
 
 ### -DetailLevel
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DetailLevel parameter specifies the amount of detail to return in the results. Valid values are:
 
@@ -130,7 +130,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -148,7 +148,7 @@ Accept wildcard characters: False
 
 ### -DoNotResolve
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DoNotResolve switch specifies whether to prevent the resolution of email addresses to display names. You don't need to specify a value with this switch.
 
@@ -168,7 +168,7 @@ Accept wildcard characters: False
 
 ### -RecipientPathFilter
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RecipientPathFilter parameter specifies the email address of the recipient when you use the ReportTemplate parameter with the value RecipientPath.
 
@@ -186,7 +186,7 @@ Accept wildcard characters: False
 
 ### -Recipients
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Recipients parameter specifies the email addresses of the recipients when you use the ReportTemplate parameter with the value Summary. You can specify multiple email addresses separated by commas.
 
@@ -204,7 +204,7 @@ Accept wildcard characters: False
 
 ### -ReportTemplate
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ReportTemplate parameter specifies a predefined format for the output. Valid values are:
 
@@ -225,7 +225,7 @@ Accept wildcard characters: False
 
 ### -ResultSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
 
@@ -243,7 +243,7 @@ Accept wildcard characters: False
 
 ### -Status
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Status parameter filters the results by the specified delivery status codes. Valid values are:
 
@@ -267,7 +267,7 @@ Accept wildcard characters: False
 
 ### -TraceLevel
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TraceLevel parameter specifies the details to include in the results. Valid values are:
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MigrationBatch.md b/exchange/exchange-ps/ExchangePowerShell/Get-MigrationBatch.md
index fb5ffbccec..0c0ec8d88d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MigrationBatch.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MigrationBatch.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -102,7 +102,7 @@ This example displays information about all migration batches associated with th
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter identifies the name of the current migration batch. The value for this parameter is specified by the Name parameter of the New-MigrationBatch cmdlet.
 
@@ -122,7 +122,7 @@ Accept wildcard characters: False
 
 ### -Diagnostic
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -144,7 +144,7 @@ Accept wildcard characters: False
 
 ### -DiagnosticArgument
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -204,7 +204,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -224,7 +224,7 @@ Accept wildcard characters: False
 
 ### -Endpoint
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Endpoint parameter returns a list of migration batches associated with the specified migration endpoint.
 
@@ -244,7 +244,7 @@ Accept wildcard characters: False
 
 ### -IncludeReport
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IncludeReport switch returns additional information about the specified migration batch. You don't need to specify a value with this switch.
 
@@ -304,7 +304,7 @@ Accept wildcard characters: False
 
 ### -Status
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Status parameter returns a list of migration batches that have the specified status state. Use one of the following values:
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MigrationConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-MigrationConfig.md
index a256dc66ad..e9547ccb5c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MigrationConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MigrationConfig.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -77,7 +77,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MigrationEndpoint.md b/exchange/exchange-ps/ExchangePowerShell/Get-MigrationEndpoint.md
index 3ea33df985..31f0965b95 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MigrationEndpoint.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MigrationEndpoint.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -82,7 +82,7 @@ This example retrieves the settings for the migration endpoint, OnboardingME01.
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the name of the migration endpoint you want to retrieve settings for.
 
@@ -100,7 +100,7 @@ Accept wildcard characters: False
 
 ### -ConnectionSettings
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -120,7 +120,7 @@ Accept wildcard characters: False
 
 ### -Diagnostic
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -142,7 +142,7 @@ Accept wildcard characters: False
 
 ### -DiagnosticArgument
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -202,7 +202,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -242,7 +242,7 @@ Accept wildcard characters: False
 
 ### -Type
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Type parameter filters the results by the type of migration. Valid values for this parameter are:
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MigrationStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-MigrationStatistics.md
index 05587e4c0a..316105390a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MigrationStatistics.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MigrationStatistics.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -46,7 +46,7 @@ This example returns the default statistics for the migration batches.
 
 ### -Diagnostic
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -68,7 +68,7 @@ Accept wildcard characters: False
 
 ### -DiagnosticArgument
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -128,7 +128,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MigrationUser.md b/exchange/exchange-ps/ExchangePowerShell/Get-MigrationUser.md
index 4f85b2de43..b152b9d8ca 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MigrationUser.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MigrationUser.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -98,7 +98,7 @@ This example retrieves more detailed information about any ongoing migration for
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the particular ongoing migration that you want to retrieve information about. The Identity parameter is usually represented as an email address.
 
@@ -116,7 +116,7 @@ Accept wildcard characters: False
 
 ### -MailboxGuid
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MailboxGuid parameter specifies the GUID of a mailbox for which you want to view the migration information.
 
@@ -134,7 +134,7 @@ Accept wildcard characters: False
 
 ### -BatchId
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The BatchId parameter specifies the name of the migration batch for which you want to return users.
 
@@ -152,7 +152,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -230,7 +230,7 @@ Accept wildcard characters: False
 
 ### -ResultSize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
 
@@ -248,7 +248,7 @@ Accept wildcard characters: False
 
 ### -Status
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Status parameter returns information about migration users that have the specified status state. Use one of the following values:
 
@@ -288,7 +288,7 @@ Accept wildcard characters: False
 
 ### -StatusSummary
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The StatusSummary parameter returns abbreviated information about migration users that have the specified status value. Use one of the following values:
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MigrationUserStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-MigrationUserStatistics.md
index cc7cf9ad2f..8b8cc0bd56 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MigrationUserStatistics.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MigrationUserStatistics.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -87,7 +87,7 @@ In on-premises Exchange, this example uses the Diagnostic parameter to display d
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the user that you want to retrieve migration information about. Use an email address as the value for this parameter.
 
@@ -105,7 +105,7 @@ Accept wildcard characters: False
 
 ### -Diagnostic
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -127,7 +127,7 @@ Accept wildcard characters: False
 
 ### -DiagnosticArgument
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -167,7 +167,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -207,7 +207,7 @@ Accept wildcard characters: False
 
 ### -IncludeReport
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IncludeReport switch specifies whether to return additional details, which can be used for troubleshooting. You don't need to specify a value with this switch.
 
@@ -225,7 +225,7 @@ Accept wildcard characters: False
 
 ### -IncludeSkippedItems
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IncludeSkippedItems switch specifies whether to include skipped items for the user. You don't need to specify a value with this switch.
 
@@ -243,7 +243,7 @@ Accept wildcard characters: False
 
 ### -LimitSkippedItemsTo
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The LimitSkippedItemsTo parameter specifies the maximum number of skipped items to display information about in the SkippedItems property in command output. For example, if this parameter is set to 5, the cmdlet returns information for up to five skipped items for the specified user, even if there are more than five skipped items.
 
@@ -281,7 +281,7 @@ Accept wildcard characters: False
 
 ### -SkipSubscription
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SkipSubscription switch specifies whether to skip loading the subscription for the user. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MobileDevice.md b/exchange/exchange-ps/ExchangePowerShell/Get-MobileDevice.md
index d54fc9963c..0a6ffc561b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MobileDevice.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MobileDevice.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
 Locale: en-US
@@ -85,7 +85,7 @@ This example returns detailed information about the specified device on Lila's m
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the mobile device that you want to view. You can use the following values that uniquely identifies the mobile device:
 
@@ -107,7 +107,7 @@ Accept wildcard characters: False
 
 ### -Mailbox
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Mailbox parameter filters the results by mailbox. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -138,7 +138,7 @@ Accept wildcard characters: False
 
 ### -ActiveSync
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ActiveSync switch filters the results by Exchange ActiveSync devices. You don't need to specify a value with this switch.
 
@@ -156,7 +156,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -176,7 +176,7 @@ Accept wildcard characters: False
 
 ### -Filter
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Filter parameter uses OPATH syntax to filter the results by the specified properties and values. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`.
 
@@ -224,7 +224,7 @@ Accept wildcard characters: False
 
 ### -Monitoring
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -246,7 +246,7 @@ Accept wildcard characters: False
 
 ### -OrganizationalUnit
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The OrganizationalUnit parameter filters the results based on the object's location in Active Directory. Only objects that exist in the specified location are returned. Valid input for this parameter is an organizational unit (OU) or domain that's returned by the Get-OrganizationalUnit cmdlet. You can use any value that uniquely identifies the OU or domain. For example:
 
@@ -269,7 +269,7 @@ Accept wildcard characters: False
 
 ### -OWAforDevices
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The OWAforDevices switch filters the results by whether Outlook on the web for devices is enabled for the device. You don't need to specify a value with this switch.
 
@@ -287,7 +287,7 @@ Accept wildcard characters: False
 
 ### -ResultSize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
 
@@ -305,7 +305,7 @@ Accept wildcard characters: False
 
 ### -SortBy
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SortBy parameter specifies the property to sort the results by. You can sort by only one property at a time. The results are sorted in ascending order.
 
@@ -343,7 +343,7 @@ Accept wildcard characters: False
 
 ### -RestApi
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RestApi switch filters the results by REST API devices. You don't need to specify a value with this switch.
 
@@ -361,7 +361,7 @@ Accept wildcard characters: False
 
 ### -UniversalOutlook
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The UniversalOutlook switch filters the results by Mail and Calendar devices. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MobileDeviceMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-MobileDeviceMailboxPolicy.md
index ce8b3ca55f..565645f4d4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MobileDeviceMailboxPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MobileDeviceMailboxPolicy.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
 Locale: en-US
@@ -52,7 +52,7 @@ This example returns the policy settings for the Mobile Device mailbox policy De
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the policy name.
 
@@ -70,7 +70,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MobileDeviceStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-MobileDeviceStatistics.md
index ae8aeb20f0..5d6f6c1c20 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MobileDeviceStatistics.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MobileDeviceStatistics.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
 Locale: en-US
@@ -89,7 +89,7 @@ This example retrieves the statistics for the mobile phone that's configured to
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the mobile device that you want to view. You can use the following values that uniquely identifies the mobile device:
 
@@ -113,7 +113,7 @@ Accept wildcard characters: False
 
 ### -Mailbox
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Mailbox parameter filters the results by the user mailbox that's associated with the mobile device. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -144,7 +144,7 @@ Accept wildcard characters: False
 
 ### -ActiveSync
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ActiveSync switch filters the results by Exchange ActiveSync devices. You don't need to specify a value with this switch.
 
@@ -162,7 +162,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -182,7 +182,7 @@ Accept wildcard characters: False
 
 ### -GetMailboxLog
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The GetMailboxLog switch specifies whether to send the mobile device statistics to the email addresses that are specified by the NotificationEmailAddresses parameter. You don't need to specify a value with this switch.
 
@@ -200,7 +200,7 @@ Accept wildcard characters: False
 
 ### -NotificationEmailAddresses
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The NotificationEmailAddresses parameter specifies a comma-separated list of email addresses to receive the mobile device statistics when you use the GetMailboxLog switch.
 
@@ -220,7 +220,7 @@ Accept wildcard characters: False
 
 ### -OWAforDevices
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The OWAforDevices switch filters the results by devices where Outlook on the web for devices is enabled. You don't need to specify a value with this switch.
 
@@ -238,7 +238,7 @@ Accept wildcard characters: False
 
 ### -ShowRecoveryPassword
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ShowRecoveryPassword switch specifies whether to return the recovery password for the mobile device as one of the displayed statistics. You don't need to specify a value with this switch.
 
@@ -256,7 +256,7 @@ Accept wildcard characters: False
 
 ### -RestApi
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RestApi switch filters the results by REST API devices. You don't need to specify a value with this switch.
 
@@ -274,7 +274,7 @@ Accept wildcard characters: False
 
 ### -UniversalOutlook
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The UniversalOutlook switch filters the results by Mail and Calendar devices. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MonitoringItemHelp.md b/exchange/exchange-ps/ExchangePowerShell/Get-MonitoringItemHelp.md
index 738fa466ce..0f30abca7c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MonitoringItemHelp.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MonitoringItemHelp.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -42,7 +42,7 @@ This example retrieves health set information for a monitoring item on the serve
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the identity of the monitoring item. The parameter uses the syntax: `<HealthSet>\<MonitoringItemName>[\<TargetResource>]`. You can find the available values in the Identity property of the output of the Get-MonitoringItem cmdlet.
 
@@ -60,7 +60,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Exchange server that contains the monitoring item. You can use any value that uniquely identifies the server. For example:
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MonitoringItemIdentity.md b/exchange/exchange-ps/ExchangePowerShell/Get-MonitoringItemIdentity.md
index 3ac2e98fc2..5ed8bba101 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MonitoringItemIdentity.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MonitoringItemIdentity.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -42,7 +42,7 @@ This example returns information about the health set named OutlookMapiHttp.Prox
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the health set that you want to view. To see the list of available health sets, you can use the Get-ServerHealth or Get-HealthReport cmdlets.
 
@@ -60,7 +60,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Exchange server that contains the health set. You can use any value that uniquely identifies the server. For example:
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MoveRequest.md b/exchange/exchange-ps/ExchangePowerShell/Get-MoveRequest.md
index 34a6e39394..7ecd1bd9a6 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MoveRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MoveRequest.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -90,7 +90,7 @@ This example retrieves the status of move requests in the FromDB01ToDB02 batch t
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the identity of the move request, which is the identity of the mailbox or mail user. You can use any value that uniquely identifies the mailbox or mail user. For example:
 
@@ -132,7 +132,7 @@ Accept wildcard characters: False
 
 ### -BatchName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The BatchName parameter specifies the name that was given to a batch move request.
 
@@ -152,7 +152,7 @@ Accept wildcard characters: False
 
 ### -Credential
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -174,7 +174,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -194,7 +194,7 @@ Accept wildcard characters: False
 
 ### -Flags
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Flags parameter specifies the move type to retrieve information for. Valid value are:
 
@@ -229,7 +229,7 @@ Accept wildcard characters: False
 
 ### -HighPriority
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -251,7 +251,7 @@ Accept wildcard characters: False
 
 ### -IncludeSoftDeletedObjects
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -271,7 +271,7 @@ Accept wildcard characters: False
 
 ### -MoveStatus
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MoveStatus parameter returns move requests in the specified status. You can use the following values:
 
@@ -301,7 +301,7 @@ Accept wildcard characters: False
 
 ### -Offline
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Offline parameter specifies whether to return mailboxes that are being moved in offline mode. This parameter accepts $true or $false.
 
@@ -321,7 +321,7 @@ Accept wildcard characters: False
 
 ### -OrganizationalUnit
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The OrganizationalUnit parameter filters the results based on the object's location in Active Directory. Only objects that exist in the specified location are returned. Valid input for this parameter is an organizational unit (OU) or domain that's returned by the Get-OrganizationalUnit cmdlet. You can use any value that uniquely identifies the OU or domain. For example:
 
@@ -344,7 +344,7 @@ Accept wildcard characters: False
 
 ### -Protect
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -397,7 +397,7 @@ Accept wildcard characters: False
 
 ### -RemoteHostName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RemoteHostName parameter specifies the FQDN of the cross-forest organization from which you're moving the mailbox.
 
@@ -417,7 +417,7 @@ Accept wildcard characters: False
 
 ### -ResultSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
 
@@ -435,7 +435,7 @@ Accept wildcard characters: False
 
 ### -SortBy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SortBy parameter specifies the property to sort the results by. You can sort by only one property at a time. The results are sorted in ascending order.
 
@@ -461,7 +461,7 @@ Accept wildcard characters: False
 
 ### -SourceDatabase
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -519,7 +519,7 @@ Accept wildcard characters: False
 
 ### -Suspend
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Suspend parameter specifies whether to return mailboxes with moves that have been suspended. This parameter accepts $true or $false.
 
@@ -539,7 +539,7 @@ Accept wildcard characters: False
 
 ### -SuspendWhenReadyToComplete
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SuspendWhenReadytoComplete parameter specifies whether to return mailboxes that have been moved with the New-MoveRequest command and its SuspendWhenReadyToComplete switch. This parameter accepts $true or $false.
 
@@ -559,7 +559,7 @@ Accept wildcard characters: False
 
 ### -TargetDatabase
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-MoveRequestStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-MoveRequestStatistics.md
index b3d60fea23..818b63f0d8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-MoveRequestStatistics.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-MoveRequestStatistics.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -117,7 +117,7 @@ This example exports the move request information so you can later import it int
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the identity of the mailbox or mail user. You can use one of the following values:
 
@@ -145,7 +145,7 @@ Accept wildcard characters: False
 
 ### -MoveRequestQueue
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -215,7 +215,7 @@ Accept wildcard characters: False
 
 ### -Diagnostic
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -237,7 +237,7 @@ Accept wildcard characters: False
 
 ### -DiagnosticArgument
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -301,7 +301,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -321,7 +321,7 @@ Accept wildcard characters: False
 
 ### -IncludeReport
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IncludeReport switch specifies whether to return additional details, which can be used for troubleshooting. You don't need to specify a value with this switch.
 
@@ -339,7 +339,7 @@ Accept wildcard characters: False
 
 ### -MailboxGuid
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -392,7 +392,7 @@ Accept wildcard characters: False
 
 ### -ReportOnly
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is reserved for internal Microsoft use.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-NetworkConnectionInfo.md b/exchange/exchange-ps/ExchangePowerShell/Get-NetworkConnectionInfo.md
index 65e665e779..b405db7a1f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-NetworkConnectionInfo.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-NetworkConnectionInfo.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -51,7 +51,7 @@ This example retrieves network configuration information for all network adapter
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the server you want to query. You can use any value that uniquely identifies the server. For example:
 
@@ -76,7 +76,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-Notification.md b/exchange/exchange-ps/ExchangePowerShell/Get-Notification.md
index 88a4d4185b..b960600134 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-Notification.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-Notification.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.WebClient-Help.xml
 Locale: en-US
@@ -85,7 +85,7 @@ This example displays detailed information for the specified notification event.
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the notification event that you want to view. You identify the notification event by its AlternativeID property value (a GUID). You can find this value by running the command Get-Notification | Format-List DisplayName,AlternateID,StartTime,Status,Type.
 
@@ -103,7 +103,7 @@ Accept wildcard characters: False
 
 ### -Settings
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -127,7 +127,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -147,7 +147,7 @@ Accept wildcard characters: False
 
 ### -ProcessType
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ProcessType parameter filters the results by the type of notification event. Valid values are:
 
@@ -171,7 +171,7 @@ Accept wildcard characters: False
 
 ### -ResultSize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
 
@@ -189,7 +189,7 @@ Accept wildcard characters: False
 
 ### -StartDate
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The StartDate parameter specifies the start date of the date range.
 
@@ -209,7 +209,7 @@ Accept wildcard characters: False
 
 ### -Summary
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Summary switch includes only the ProcessType and Status property values in the results. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-OabVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Get-OabVirtualDirectory.md
index 8cad368b7a..0411b0f962 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-OabVirtualDirectory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-OabVirtualDirectory.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -69,7 +69,7 @@ This example returns detailed information for the OAB virtual directory named "O
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the OAB virtual directory that you want to view. You can use any value that uniquely identifies the virtual directory. For example:
 
@@ -95,7 +95,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Exchange server that hosts the virtual directory. You can use any value that uniquely identifies the server. For example:
 
@@ -120,7 +120,7 @@ Accept wildcard characters: False
 
 ### -ADPropertiesOnly
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ADPropertiesOnly switch specifies whether to return only the virtual directory properties that are stored in Active Directory. You don't need to specify a value with this switch.
 
@@ -140,7 +140,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -158,7 +158,7 @@ Accept wildcard characters: False
 
 ### -ShowMailboxVirtualDirectories
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ShowMailboxVirtualDirectories switch shows information about backend virtual directories on Mailbox servers. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-OfflineAddressBook.md b/exchange/exchange-ps/ExchangePowerShell/Get-OfflineAddressBook.md
index 299ffe54d0..b5c271b429 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-OfflineAddressBook.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-OfflineAddressBook.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -67,7 +67,7 @@ This example returns specific properties for all existing OABs, including the Ge
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the OAB that you want to view. You can use any value that uniquely identifies the OAB. For example:
 
@@ -91,7 +91,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -121,7 +121,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-OnlineMeetingConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Get-OnlineMeetingConfiguration.md
index 402cc08950..4cec7f369b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-OnlineMeetingConfiguration.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-OnlineMeetingConfiguration.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
 Locale: en-US
@@ -50,7 +50,7 @@ This example gets the Skype Meetings configuration for the specified mailbox.
 
 ### -Identity
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the mailbox that you want to view. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -79,7 +79,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-OrganizationConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-OrganizationConfig.md
index d269f440c7..2da5c4b45a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-OrganizationConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-OrganizationConfig.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -62,7 +62,7 @@ If the value of EwsApplicationAccessPolicy is EnforceBlockList, all applications
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-OrganizationRelationship.md b/exchange/exchange-ps/ExchangePowerShell/Get-OrganizationRelationship.md
index 7effe3c9ad..4c576ed8d4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-OrganizationRelationship.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-OrganizationRelationship.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
 Locale: en-US
@@ -50,7 +50,7 @@ This example retrieves the organization relationship settings by using the FQDN
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the identity of the organizational relationship. You can use the following values:
 
@@ -72,7 +72,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-OrganizationalUnit.md b/exchange/exchange-ps/ExchangePowerShell/Get-OrganizationalUnit.md
index 35252328c5..0ad6645a48 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-OrganizationalUnit.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-OrganizationalUnit.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -69,7 +69,7 @@ For more information about pipelining and the Format-Table cmdlet, see [About Pi
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the OU or domain that you want to view. You can use any value that uniquely identifies the OU or domain. For example:
 
@@ -94,7 +94,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -114,7 +114,7 @@ Accept wildcard characters: False
 
 ### -IncludeContainers
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IncludeContainers switch instructs the command to return containers in the results. You don't need to specify a value with this switch.
 
@@ -132,7 +132,7 @@ Accept wildcard characters: False
 
 ### -SingleNodeOnly
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SingleNodeOnly switch instructs the command to return only the first level child OUs beneath the OU specified in the Identity parameter. You don't need to specify a value with this switch.
 
@@ -150,7 +150,7 @@ Accept wildcard characters: False
 
 ### -ResultSize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
 
@@ -168,7 +168,7 @@ Accept wildcard characters: False
 
 ### -SearchText
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SearchText parameter enables you to search the names of all OUs in your organization for the specified string. Only the OUs that match the string you specify are returned. If the string you specify contains spaces, enclose it in quotation marks (").
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-OutlookAnywhere.md b/exchange/exchange-ps/ExchangePowerShell/Get-OutlookAnywhere.md
index 112de05d73..84da3e4ffd 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-OutlookAnywhere.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-OutlookAnywhere.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -62,7 +62,7 @@ This example returns information about the Outlook Anywhere virtual directory na
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the Outlook Anywhere virtual directory that you want to view. You can use any value that uniquely identifies the virtual directory. For example:
 
@@ -88,7 +88,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Exchange server that hosts the virtual directory. You can use any value that uniquely identifies the server. For example:
 
@@ -113,7 +113,7 @@ Accept wildcard characters: False
 
 ### -ADPropertiesOnly
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ADPropertiesOnly switch specifies whether to return only the virtual directory properties that are stored in Active Directory. You don't need to specify a value with this switch.
 
@@ -133,7 +133,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -151,7 +151,7 @@ Accept wildcard characters: False
 
 ### -ShowMailboxVirtualDirectories
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ShowMailboxVirtualDirectories switch shows information about backend virtual directories on Mailbox servers. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-OutlookProtectionRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-OutlookProtectionRule.md
index c6efe5855d..dbe9cc5f7e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-OutlookProtectionRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-OutlookProtectionRule.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -56,7 +56,7 @@ The Identity parameter is positional. When used after the cmdlet name, the param
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter identifies an Outlook protection rule.
 
@@ -74,7 +74,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-OutlookProvider.md b/exchange/exchange-ps/ExchangePowerShell/Get-OutlookProvider.md
index d399eecb7f..1c4402fee5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-OutlookProvider.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-OutlookProvider.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -52,7 +52,7 @@ This example returns detailed information for the Outlook provider named WEB.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the ADIDParameter value of the MAPI protocol that you want to view. Typical values are:
 
@@ -74,7 +74,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-OwaMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-OwaMailboxPolicy.md
index 6e68f829bf..835a172b5c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-OwaMailboxPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-OwaMailboxPolicy.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.WebClient-Help.xml
 Locale: en-US
@@ -57,7 +57,7 @@ This example retrieves the information for the mailbox policy named Corporate fo
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the mailbox policy that you want to view. You can use any value that uniquely identifies the policy. For example:
 
@@ -79,7 +79,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-OwaVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Get-OwaVirtualDirectory.md
index e918994ed0..1595552983 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-OwaVirtualDirectory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-OwaVirtualDirectory.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.WebClient-Help.xml
 Locale: en-US
@@ -73,7 +73,7 @@ This example returns a summary list of all Outlook on the web virtual directorie
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the OWA virtual directory that you want to view. You can use any value that uniquely identifies the virtual directory. For example:
 
@@ -99,7 +99,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Exchange server that hosts the virtual directory. You can use any value that uniquely identifies the server. For example:
 
@@ -124,7 +124,7 @@ Accept wildcard characters: False
 
 ### -ADPropertiesOnly
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ADPropertiesOnly switch specifies whether to return only the virtual directory properties that are stored in Active Directory. You don't need to specify a value with this switch.
 
@@ -144,7 +144,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -162,7 +162,7 @@ Accept wildcard characters: False
 
 ### -ShowMailboxVirtualDirectories
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ShowMailboxVirtualDirectories switch shows information about backend virtual directories on Mailbox servers. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-PartnerApplication.md b/exchange/exchange-ps/ExchangePowerShell/Get-PartnerApplication.md
index 51e6a7a743..2c16113aca 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-PartnerApplication.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-PartnerApplication.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -46,7 +46,7 @@ This example retrieves settings for all partner applications configured in Excha
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the identity of a partner application.
 
@@ -64,7 +64,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -84,7 +84,7 @@ Accept wildcard characters: False
 
 ### -Organization
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-PendingFederatedDomain.md b/exchange/exchange-ps/ExchangePowerShell/Get-PendingFederatedDomain.md
index 1b57b6d5c1..8297d834ea 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-PendingFederatedDomain.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-PendingFederatedDomain.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
 Locale: en-US
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-PolicyTipConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-PolicyTipConfig.md
index 2ac670e3e4..fddb48a8f3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-PolicyTipConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-PolicyTipConfig.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -67,7 +67,7 @@ This example returns details about the custom English Policy Tip for the action
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the custom Policy Tip you want to view. You can use any value that uniquely identifies the custom Policy Tip. For example:
 
@@ -92,7 +92,7 @@ Accept wildcard characters: False
 
 ### -Action
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Action parameter filters the Policy Tips by action. Valid values for this parameter are:
 
@@ -118,7 +118,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -138,7 +138,7 @@ Accept wildcard characters: False
 
 ### -Locale
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Locale parameter specifies a locale-specific version of the Policy Tip.
 
@@ -160,7 +160,7 @@ Accept wildcard characters: False
 
 ### -Original
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Original switch specifies whether to include built-in Policy Tips in the results. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-PopSettings.md b/exchange/exchange-ps/ExchangePowerShell/Get-PopSettings.md
index d140d3fa03..706330731d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-PopSettings.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-PopSettings.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -50,7 +50,7 @@ This example returns detailed information for the Microsoft Exchange POP3 servic
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -68,7 +68,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-PowerShellVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Get-PowerShellVirtualDirectory.md
index 4324161baf..328b56bf0b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-PowerShellVirtualDirectory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-PowerShellVirtualDirectory.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -69,7 +69,7 @@ This example returns a summary list of all PowerShell virtual directories in the
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the PowerShell virtual directory that you want to view. You can use any value that uniquely identifies the virtual directory. For example:
 
@@ -95,7 +95,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Exchange server that hosts the virtual directory. You can use any value that uniquely identifies the server. For example:
 
@@ -120,7 +120,7 @@ Accept wildcard characters: False
 
 ### -ADPropertiesOnly
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ADPropertiesOnly switch specifies whether to return only the virtual directory properties that are stored in Active Directory. You don't need to specify a value with this switch.
 
@@ -140,7 +140,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -158,7 +158,7 @@ Accept wildcard characters: False
 
 ### -ShowMailboxVirtualDirectories
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ShowMailboxVirtualDirectories switch shows information about backend virtual directories on Mailbox servers. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolder.md b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolder.md
index aeeccce66a..6c9add4dfd 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolder.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolder.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.WebClient-Help.xml
 Locale: en-US
@@ -120,7 +120,7 @@ This example returns the public folders that reside in the public folder content
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the name and path of the public folder you want to view. A valid value uses the syntax: `\Level1\Level2\...\LevenN\PublicFolder`. For example, `"\Customer Discussion"` or `"\Engineering\Customer Discussion"`.
 
@@ -138,7 +138,7 @@ Accept wildcard characters: False
 
 ### -GetChildren
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The GetChildren switch specifies whether to return only the children of the folder specified by the Identity parameter. You don't need to specify a value with this switch.
 
@@ -158,7 +158,7 @@ Accept wildcard characters: False
 
 ### -Recurse
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Recurse switch specifies whether to return the specified public folder and all its children. You don't need to specify a value with this switch.
 
@@ -178,7 +178,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -198,7 +198,7 @@ Accept wildcard characters: False
 
 ### -LostAndFound
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The LostAndFound switch specifies whether to return only orphaned folders that are located in \\NON\_IPM\_SUBTREE\\LOST\_AND\_FOUND. You don't need to specify a value with this switch.
 
@@ -220,7 +220,7 @@ Accept wildcard characters: False
 
 ### -Mailbox
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Mailbox parameter specifies the identity of the hierarchy public folder mailbox. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -249,7 +249,7 @@ Accept wildcard characters: False
 
 ### -Organization
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -269,7 +269,7 @@ Accept wildcard characters: False
 
 ### -ResidentFolders
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ResidentFolders switch specifies whether to return public folders that reside in a specific content public folder mailbox. You don't need to specify a value with this switch.
 
@@ -289,7 +289,7 @@ Accept wildcard characters: False
 
 ### -ResultSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ResultSize parameter specifies the maximum number of results to return. The default maximum is 10,000. For no limit on the returned results, set this parameter to Unlimited. This parameter can only be passed in combination with the Recurse or GetChildren parameters.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderClientPermission.md b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderClientPermission.md
index 2b1aef2051..5eac0aa6f6 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderClientPermission.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderClientPermission.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.WebClient-Help.xml
 Locale: en-US
@@ -56,7 +56,7 @@ This example retrieves the permissions for the public folder My Public Folder, f
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the GUID or public folder name that represents a specific public folder. You can also include the path using the format \\TopLevelPublicFolder\\PublicFolder.
 
@@ -76,7 +76,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -141,7 +141,7 @@ Accept wildcard characters: False
 
 ### -User
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The User parameter specifies the user for whom you want to view the permissions on the public folder.
 
@@ -164,7 +164,7 @@ Accept wildcard characters: False
 
 ### -Mailbox
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Mailbox parameter specifies the public folder mailbox that you want to view the permissions for. You can use any value that uniquely identifies the mailbox. For example:
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderDatabase.md b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderDatabase.md
index 4e6b5127ba..4f590bdc8e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderDatabase.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderDatabase.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.WebClient-Help.xml
 Locale: en-US
@@ -75,7 +75,7 @@ This example returns information about all public folders on Server01.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the public folder database that you want to view. You can use any value that uniquely identifies the database. For example:
 
@@ -101,7 +101,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter filters the results by the specified Exchange server. You can use any value that uniquely identifies the server. For example:
 
@@ -126,7 +126,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -166,7 +166,7 @@ Accept wildcard characters: False
 
 ### -Status
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Status switch specifies whether to include additional backup and mount status information for servers running Exchange 2010. You don't need to specify a value with this switch.
 
@@ -184,7 +184,7 @@ Accept wildcard characters: False
 
 ### -IncludeCorrupted
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderItemStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderItemStatistics.md
index 877ef36542..cbc33d3800 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderItemStatistics.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderItemStatistics.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.WebClient-Help.xml
 Locale: en-US
@@ -66,7 +66,7 @@ This example exports the output of the Get-PublicFolderItemStatistics command to
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the GUID or public folder name that represents a specific public folder. You can also include the path using the following format: \\TopLevelPublicFolder\\PublicFolder
 
@@ -84,7 +84,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -104,7 +104,7 @@ Accept wildcard characters: False
 
 ### -Mailbox
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Mailbox parameter specifies the identity of the hierarchy public folder mailbox that you want to view. You can use any value that uniquely identifies the mailbox. For example:
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMailboxDiagnostics.md b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMailboxDiagnostics.md
index 3c19ede799..e818298491 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMailboxDiagnostics.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMailboxDiagnostics.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.WebClient-Help.xml
 Locale: en-US
@@ -54,7 +54,7 @@ This example returns the diagnostic information for the public folder mailbox Sa
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the identity of the public folder mailbox. The public folder mailbox is where the content of the public folder resides.
 
@@ -85,7 +85,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -106,7 +106,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -126,7 +126,7 @@ Accept wildcard characters: False
 
 ### -IncludeDumpsterInfo
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IncludeDumpsterInfo specifies whether to include diagnostic information for the \\NON\_IPM\_TREE\\DUMPSTER\_ROOT folder (the dumpster for public folder mailboxes is included in the results. You don't need to specify a value with this switch.
 
@@ -144,7 +144,7 @@ Accept wildcard characters: False
 
 ### -IncludeHierarchyInfo
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IncludeHierarchyInfo switch specifies whether to include folder hierarchy information in the results. You don't need to specify a value with this switch.
 
@@ -175,7 +175,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMailboxMigrationRequest.md b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMailboxMigrationRequest.md
index ab22880711..2bf548c962 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMailboxMigrationRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMailboxMigrationRequest.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -85,7 +85,7 @@ This example returns duplicate public folder migration requests (requests create
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the public folder mailbox migration request that you want to view. The value uses the syntax: `\PublicFolderMailboxMigration<GUID>` (for example, `\PublicFolderMailboxMigrationac6d9eb4-ee49-405f-b90d-04e9a258bd7e`).
 
@@ -112,7 +112,7 @@ Accept wildcard characters: False
 
 ### -BatchName
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The BatchName parameter filters the results by the friendly BatchName value that was assigned when the batch job was created. The format of this value is: `MigrationService:<Batch name provided at batch creation>`.
 
@@ -132,7 +132,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -152,7 +152,7 @@ Accept wildcard characters: False
 
 ### -HighPriority
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -177,7 +177,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Name parameter specifies the name of the public folder mailbox migration request. If the name was not specified at creation, the default value is `PublicFolderMailboxMigration<GUID>` (for example, `PublicFolderMailboxMigration2ffdef13-01b9-4586-af2b-d5a5482010a8`).
 
@@ -197,7 +197,7 @@ Accept wildcard characters: False
 
 ### -RequestQueue
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -223,7 +223,7 @@ Accept wildcard characters: False
 
 ### -ResultSize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
 
@@ -241,7 +241,7 @@ Accept wildcard characters: False
 
 ### -Status
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Status parameter filters the results based on status. You can use the following values:
 
@@ -272,7 +272,7 @@ Accept wildcard characters: False
 
 ### -Suspend
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Suspend parameter specifies whether to return requests that have been suspended. Valid input for this parameter is $true or $false.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMailboxMigrationRequestStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMailboxMigrationRequestStatistics.md
index 39bb0267b1..b2aa35b5b9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMailboxMigrationRequestStatistics.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMailboxMigrationRequestStatistics.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -77,7 +77,7 @@ This example uses the Identity parameter to return information about the specifi
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the public folder mailbox migration request. The default identity value is `\PublicFolderMailboxMigration<UniqueIdentifier>` (for example, `PublicFolderMailboxMigrationac6d9eb4-ee49-405f-b90d-04e9a258bd7e`).
 
@@ -97,7 +97,7 @@ Accept wildcard characters: False
 
 ### -RequestQueue
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -125,7 +125,7 @@ Accept wildcard characters: False
 
 ### -Diagnostic
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -147,7 +147,7 @@ Accept wildcard characters: False
 
 ### -DiagnosticArgument
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -187,7 +187,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -207,7 +207,7 @@ Accept wildcard characters: False
 
 ### -IncludeReport
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IncludeReport switch specifies whether to return additional details, which can be used for troubleshooting. You don't need to specify a value with this switch.
 
@@ -245,7 +245,7 @@ Accept wildcard characters: False
 
 ### -ReportOnly
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ReportOnly switch returns the results as an array of report entries (encoded strings). You don't need to specify a value with this switch.
 
@@ -263,7 +263,7 @@ Accept wildcard characters: False
 
 ### -RequestGuid
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMigrationRequest.md b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMigrationRequest.md
index 0bd6706de5..39b9e08d9a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMigrationRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMigrationRequest.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -68,7 +68,7 @@ This example returns all migration requests that have the name PFMigrate10\_11\_
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the identity of the public folder migration request that you want to view. You can use the following values:
 
@@ -91,7 +91,7 @@ Accept wildcard characters: False
 
 ### -BatchName
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The BatchName parameter specifies the name that was given to a batch migration request.
 
@@ -111,7 +111,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -129,7 +129,7 @@ Accept wildcard characters: False
 
 ### -HighPriority
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The HighPriority parameter filters the results based on the Priority value that was assigned when the request was created. Valid input for this parameter is $true or $false. Here's how these values filter the results:
 
@@ -152,7 +152,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Name parameter filters the results by the name of the public folder migration request.
 
@@ -172,7 +172,7 @@ Accept wildcard characters: False
 
 ### -RequestQueue
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RequestQueue parameter identifies the request based on the mailbox database where the request is being run. You can use any value that uniquely identifies the database. For example:
 
@@ -196,7 +196,7 @@ Accept wildcard characters: False
 
 ### -ResultSize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
 
@@ -214,7 +214,7 @@ Accept wildcard characters: False
 
 ### -Status
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Status parameter filters the results based on status. You can use the following values:
 
@@ -245,7 +245,7 @@ Accept wildcard characters: False
 
 ### -Suspend
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Suspend parameter specifies whether to return requests that have been suspended. Valid input for this parameter is $true or $false.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMigrationRequestStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMigrationRequestStatistics.md
index 9345f6dc9f..500b1ab3dd 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMigrationRequestStatistics.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMigrationRequestStatistics.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -70,7 +70,7 @@ This example returns additional information about the migration request and expo
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the migration request that you want to view. You can use the following values:
 
@@ -93,7 +93,7 @@ Accept wildcard characters: False
 
 ### -RequestQueue
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is for debugging purposes only.
 
@@ -119,7 +119,7 @@ Accept wildcard characters: False
 
 ### -Diagnostic
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Diagnostic switch specifies whether to return extremely detailed information in the results. You don't need to specify a value with this switch.
 
@@ -139,7 +139,7 @@ Accept wildcard characters: False
 
 ### -DiagnosticArgument
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DiagnosticArgument parameter modifies the results that are returned by using the Diagnostic switch. Typically, you use the Diagnostic switch and the DiagnosticArgument parameter only at the request of Microsoft Customer Service and Support to troubleshoot problems.
 
@@ -157,7 +157,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -175,7 +175,7 @@ Accept wildcard characters: False
 
 ### -IncludeReport
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IncludeReport switch specifies whether to return additional details, which can be used for troubleshooting. You don't need to specify a value with this switch.
 
@@ -193,7 +193,7 @@ Accept wildcard characters: False
 
 ### -ReportOnly
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ReportOnly switch returns the results as an array of report entries (encoded strings). You don't need to specify a value with this switch.
 
@@ -211,7 +211,7 @@ Accept wildcard characters: False
 
 ### -RequestGuid
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RequestGuid parameter specifies the GUID of a migration request.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMoveRequest.md b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMoveRequest.md
index 61e9261c2b..1c8e001ecc 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMoveRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMoveRequest.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -66,7 +66,7 @@ This example returns the status of in-progress and queued requests that are on t
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the identity of the public folder move request. The default identity assigned to public folder move requests is \\PublicFolderMove.
 
@@ -113,7 +113,7 @@ Accept wildcard characters: False
 
 ### -BatchName
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The BatchName parameter specifies the name that was given to a batch public folder move request.
 
@@ -133,7 +133,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is functional only in on-premises Exchange.
 
@@ -153,7 +153,7 @@ Accept wildcard characters: False
 
 ### -HighPriority
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The HighPriority parameter filters the results based on the Priority value that was assigned when the request was created. Valid input for this parameter is $true or $false. Here's how these values filter the results:
 
@@ -176,7 +176,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Name parameter specifies the name of the public folder move request. If you didn't specify a name when creating the move request, PublicFolderMove is the default name assigned to the request.
 
@@ -216,7 +216,7 @@ Accept wildcard characters: False
 
 ### -RequestQueue
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RequestQueue parameter identifies the request based on the mailbox database where the request is being run. You can use any value that uniquely identifies the database. For example:
 
@@ -240,7 +240,7 @@ Accept wildcard characters: False
 
 ### -ResultSize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
 
@@ -258,7 +258,7 @@ Accept wildcard characters: False
 
 ### -Status
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Status parameter filters the results based on status. You can use the following values:
 
@@ -289,7 +289,7 @@ Accept wildcard characters: False
 
 ### -Suspend
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Suspend parameter specifies whether to return requests that have been suspended. Valid input for this parameter is $true or $false.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMoveRequestStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMoveRequestStatistics.md
index a2987dd3dc..69f5e45fee 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMoveRequestStatistics.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderMoveRequestStatistics.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -70,7 +70,7 @@ This example returns the detailed statistics for the move request \\PublicFolder
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the identity of the public folder move request. The default public folder move request identity is \\PublicFolderMove.
 
@@ -90,7 +90,7 @@ Accept wildcard characters: False
 
 ### -RequestQueue
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is for debugging purposes only.
 
@@ -116,7 +116,7 @@ Accept wildcard characters: False
 
 ### -Diagnostic
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Diagnostic switch specifies whether to return extremely detailed information in the results. You don't need to specify a value with this switch.
 
@@ -136,7 +136,7 @@ Accept wildcard characters: False
 
 ### -DiagnosticArgument
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DiagnosticArgument parameter modifies the results that are returned by using the Diagnostic switch. Typically, you use the Diagnostic switch and the DiagnosticArgument parameter only at the request of Microsoft Customer Service and Support to troubleshoot problems.
 
@@ -174,7 +174,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is functional only in on-premises Exchange.
 
@@ -194,7 +194,7 @@ Accept wildcard characters: False
 
 ### -IncludeReport
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IncludeReport switch specifies whether to return additional details, which can be used for troubleshooting. You don't need to specify a value with this switch.
 
@@ -232,7 +232,7 @@ Accept wildcard characters: False
 
 ### -ReportOnly
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ReportOnly switch returns the results as an array of report entries (encoded strings). You don't need to specify a value with this switch.
 
@@ -250,7 +250,7 @@ Accept wildcard characters: False
 
 ### -RequestGuid
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RequestGuid parameter specifies the GUID of the public folder move request for which you want to view the request statistics.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderStatistics.md
index 51087f7a02..d08bcc2f72 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderStatistics.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-PublicFolderStatistics.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.WebClient-Help.xml
 Locale: en-US
@@ -46,7 +46,7 @@ This example retrieves statistics about the public folder Marketing\\2013\\Pamph
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the GUID or public folder name that represents a specific public folder. You can also include the path using the format \\TopLevelPublicFolder\\PublicFolder.
 
@@ -66,7 +66,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -86,7 +86,7 @@ Accept wildcard characters: False
 
 ### -Mailbox
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Mailbox parameter specifies the identity of the hierarchy public folder mailbox. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -115,7 +115,7 @@ Accept wildcard characters: False
 
 ### -ResultSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is available only in on-premises Exchange.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-Queue.md b/exchange/exchange-ps/ExchangePowerShell/Get-Queue.md
index 02f901b65b..87030c6e7f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-Queue.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-Queue.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -89,7 +89,7 @@ This example lists only the external queues.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the queue. Valid input for this parameter uses the syntax Server\\Queue or Queue, for example, Mailbox01\\contoso.com or Unreachable. For details about queue identity, see [Queue identity](https://learn.microsoft.com/Exchange/mail-flow/queues/queues-and-messages-in-powershell#queue-identity).
 
@@ -107,7 +107,7 @@ Accept wildcard characters: False
 
 ### -BookmarkIndex
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The BookmarkIndex parameter specifies the position in the result set where the displayed results start. The value of this parameter is a 1-based index in the total result set. The BookmarkIndex parameter can't be used with the BookmarkObject parameter.
 
@@ -125,7 +125,7 @@ Accept wildcard characters: False
 
 ### -BookmarkObject
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The BookmarkObject parameter specifies the object in the result set where the displayed results start. The BookmarkObject parameter can't be used with the BookmarkIndex parameter.
 
@@ -143,7 +143,7 @@ Accept wildcard characters: False
 
 ### -Exclude
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Exclude parameter specifies the types of queues you want to exclude from the results. Valid values for this parameter are:
 
@@ -165,7 +165,7 @@ Accept wildcard characters: False
 
 ### -Filter
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Filter parameter specifies one or more queues by using OPATH filter syntax. The OPATH filter includes a queue property name followed by a comparison operator and value (for example, `"NextHopDomain -eq 'contoso.com'"`). For details about filterable queue properties and comparison operators, see [Queue properties in Exchange Server](https://learn.microsoft.com/Exchange/mail-flow/queues/queue-properties) and [Find queues and messages in queues in the Exchange Management Shell](https://learn.microsoft.com/Exchange/mail-flow/queues/queues-and-messages-in-powershell).
 
@@ -185,7 +185,7 @@ Accept wildcard characters: False
 
 ### -Include
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Include parameter specifies the types of queues you want to include the results. Valid values for this parameter are:
 
@@ -207,7 +207,7 @@ Accept wildcard characters: False
 
 ### -IncludeBookmark
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IncludeBookmark parameter specifies whether to include the bookmark object when the query results are displayed. The IncludeBookmark parameter is valid when it's used with the BookmarkObject or BookmarkIndex parameters. If you don't specify a value for the IncludeBookmark parameter, the default value of $true is used.
 
@@ -225,7 +225,7 @@ Accept wildcard characters: False
 
 ### -ResultSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
 
@@ -243,7 +243,7 @@ Accept wildcard characters: False
 
 ### -ReturnPageInfo
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ReturnPageInfo parameter is a hidden parameter. Use it to return information about the total number of results and the index of the first object of the current page. The default value is $false.
 
@@ -261,7 +261,7 @@ Accept wildcard characters: False
 
 ### -SearchForward
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SearchForward parameter specifies whether to search forward or backward in the result set. The default value is $true. This value causes the result page to be calculated forward from either the start of the result set or forward from a bookmark if specified.
 
@@ -279,7 +279,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
 
@@ -306,7 +306,7 @@ Accept wildcard characters: False
 
 ### -SortOrder
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SortOrder parameter specifies an array of message properties used to control the sort order of the result set. Separate each property by using a comma. Prepend a plus sign (+) symbol to the beginning of the property name to display the results in ascending order. Prepend a minus sign (-) symbol to the beginning of the property name to display the results in descending order.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-QueueDigest.md b/exchange/exchange-ps/ExchangePowerShell/Get-QueueDigest.md
index 3e658ea466..e71a73e68b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-QueueDigest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-QueueDigest.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -90,7 +90,7 @@ This example returns information about all queues in the DAG named DAG01.
 
 ### -Dag
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Dag parameter filters the delivery queue results by DAG. You can specify any value that uniquely identifies the DAG. You can specify multiple values separated by commas. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -110,7 +110,7 @@ Accept wildcard characters: False
 
 ### -Forest
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Forest switch filters the delivery queue results by Active Directory forest. You don't need to specify a value with the Forest switch.
 
@@ -130,7 +130,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter filters the delivery queue results by Exchange server. You can specify any value that uniquely identifies the server. You can specify multiple values separated by commas. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -150,7 +150,7 @@ Accept wildcard characters: False
 
 ### -Site
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Site parameter filters the delivery queue results by Active Directory site. You can specify any value that uniquely identifies the site. You can specify multiple sites separated by commas.
 
@@ -170,7 +170,7 @@ Accept wildcard characters: False
 
 ### -DetailsLevel
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DetailsLevel parameter specifies the level of detail to display in the results. Valid values for this parameter are None, Normal and Verbose. The default value is Normal.
 
@@ -188,7 +188,7 @@ Accept wildcard characters: False
 
 ### -Filter
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Filter parameter specifies one or more queues by using OPATH filter syntax. The OPATH filter includes a queue property name followed by a comparison operator and value (for example, `"NextHopDomain -eq 'contoso.com'"`). For details about filterable queue properties and comparison operators, see [Queue properties in Exchange Server](https://learn.microsoft.com/Exchange/mail-flow/queues/queue-properties) and [Find queues and messages in queues in the Exchange Management Shell](https://learn.microsoft.com/Exchange/mail-flow/queues/queues-and-messages-in-powershell).
 
@@ -208,7 +208,7 @@ Accept wildcard characters: False
 
 ### -GroupBy
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The GroupedBy parameter sorts the messages in the delivery queue results. Valid values are:
 
@@ -236,7 +236,7 @@ Accept wildcard characters: False
 
 ### -ResultSize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ResultSize parameter filters the delivery queue results by the number of messages in the queue. Valid input for this parameter is an integer. The default value is 1000. For example, if you specify the value 50, the command displays the 50 queues that contain the most messages.
 
@@ -254,7 +254,7 @@ Accept wildcard characters: False
 
 ### -Timeout
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Timeout parameter specifies the number of seconds before the operation times out. The default value is 10 seconds.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-RMSTemplate.md b/exchange/exchange-ps/ExchangePowerShell/Get-RMSTemplate.md
index dcd9a4ad30..b40d1b10ac 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-RMSTemplate.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-RMSTemplate.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailControl-Help.xml
 Locale: en-US
@@ -55,7 +55,7 @@ This example retrieves the Company Confidential RMS template.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the name of the RMS template.
 
@@ -73,7 +73,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -93,7 +93,7 @@ Accept wildcard characters: False
 
 ### -ResultSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ReceiveConnector.md b/exchange/exchange-ps/ExchangePowerShell/Get-ReceiveConnector.md
index 1405cdb418..eb4b435b49 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ReceiveConnector.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ReceiveConnector.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -60,7 +60,7 @@ This example displays detailed information for the Receive connector named Recei
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the Receive connector that you want to view. You can use any value that uniquely identifies the Receive connector. For example:
 
@@ -85,7 +85,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -105,7 +105,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter filters the results by the specified Mailbox server or Edge Transport server. You can use any value that uniquely identifies the server. For example:
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-Recipient.md b/exchange/exchange-ps/ExchangePowerShell/Get-Recipient.md
index fb5e831977..a3b965ac4a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-Recipient.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-Recipient.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -146,7 +146,7 @@ This example retrieves information about all the mail contacts in your organizat
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The Identity parameter specifies the recipient object that you want to view. You can use any value that uniquely identifies the recipient. For example:
 
@@ -171,7 +171,7 @@ Accept wildcard characters: False
 
 ### -Anr
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The Anr parameter specifies a string on which to perform an ambiguous name resolution (ANR) search. You can specify a partial string and search for objects with an attribute that matches that string. The default attributes searched are:
 
@@ -218,7 +218,7 @@ Accept wildcard characters: False
 
 ### -BookmarkDisplayName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 This parameter is reserved for internal Microsoft use.
 
@@ -256,7 +256,7 @@ Accept wildcard characters: False
 
 ### -Credential
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -278,7 +278,7 @@ Accept wildcard characters: False
 
 ### -Database
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -302,7 +302,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -322,7 +322,7 @@ Accept wildcard characters: False
 
 ### -Filter
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The Filter parameter uses OPATH syntax to filter the results by the specified properties and values. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`.
 
@@ -349,7 +349,7 @@ Accept wildcard characters: False
 
 ### -IgnoreDefaultScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -374,7 +374,7 @@ Accept wildcard characters: False
 
 ### -IncludeBookmarkObject
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 This parameter is reserved for internal Microsoft use.
 
@@ -412,7 +412,7 @@ Accept wildcard characters: False
 
 ### -IncludeSoftDeletedRecipients
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The IncludeSoftDeletedRecipients switch specifies whether to include soft deleted recipients in the results. You don't need to specify a value with this switch.
 
@@ -434,7 +434,7 @@ Accept wildcard characters: False
 
 ### -OrganizationalUnit
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The OrganizationalUnit parameter filters the results based on the object's location in Active Directory. Only objects that exist in the specified location are returned. Valid input for this parameter is an organizational unit (OU) or domain that's returned by the Get-OrganizationalUnit cmdlet. You can use any value that uniquely identifies the OU or domain. For example:
 
@@ -457,7 +457,7 @@ Accept wildcard characters: False
 
 ### -Properties
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 This parameter is reserved for internal Microsoft use.
 
@@ -475,7 +475,7 @@ Accept wildcard characters: False
 
 ### -PropertySet
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 This parameter is reserved for internal Microsoft use.
 
@@ -493,7 +493,7 @@ Accept wildcard characters: False
 
 ### -ReadFromDomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -517,7 +517,7 @@ Accept wildcard characters: False
 
 ### -RecipientPreviewFilter
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The RecipientPreviewFilter parameter tests a recipient filter that you would use in a dynamic distribution group, address list, or email address policy. This parameter uses the LDAP filter syntax.
 
@@ -535,7 +535,7 @@ Accept wildcard characters: False
 
 ### -RecipientType
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The RecipientType parameter filters the results by the specified recipient type. Valid values are:
 
@@ -564,7 +564,7 @@ Accept wildcard characters: False
 
 ### -RecipientTypeDetails
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The RecipientTypeDetails parameter filters the results by the specified recipient subtype. Valid values are:
 
@@ -615,7 +615,7 @@ Accept wildcard characters: False
 
 ### -ResultSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
 
@@ -633,7 +633,7 @@ Accept wildcard characters: False
 
 ### -SortBy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The SortBy parameter specifies the property to sort the results by. You can sort by only one property at a time. The results are sorted in ascending order.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-RecipientFilterConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-RecipientFilterConfig.md
index bba82d81ec..2daa8baa62 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-RecipientFilterConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-RecipientFilterConfig.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailControl-Help.xml
 Locale: en-US
@@ -43,7 +43,7 @@ This example returns detailed information about the recipient filter configurati
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -61,7 +61,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-RecoverableItems.md b/exchange/exchange-ps/ExchangePowerShell/Get-RecoverableItems.md
index 8d5b5d87bb..f7cdee932f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-RecoverableItems.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-RecoverableItems.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
 Locale: en-US
@@ -76,7 +76,7 @@ This example returns all of the available recoverable deleted messages with the
 
 ### -Identity
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the mailbox that contains the deleted items that you want to view. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -107,7 +107,7 @@ Accept wildcard characters: False
 
 ### -EntryID
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The EntryID parameter specifies the deleted item that you want to restore. The EntryID value for the deleted item is unique in the mailbox.
 
@@ -127,7 +127,7 @@ Accept wildcard characters: False
 
 ### -FilterEndTime
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The FilterEndTime specifies the end date/time of the date range. This parameter uses the LastModifiedTime value of the item.
 
@@ -147,7 +147,7 @@ Accept wildcard characters: False
 
 ### -FilterItemType
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The FilterItemType parameter filters the results by the specified MessageClass (ItemClass) property value of the deleted item. For example:
 
@@ -171,7 +171,7 @@ Accept wildcard characters: False
 
 ### -FilterStartTime
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The FilterStartTime specifies the start date/time of the date range. This parameter uses the LastModifiedTime value of the item.
 
@@ -191,7 +191,7 @@ Accept wildcard characters: False
 
 ### -LastParentFolderID
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The LastParentFolderID parameter specifies the FolderID value of the item before it was deleted. For example, 53B93149989CA54DBC9702AE619B9CCA000062CE9397.
 
@@ -251,7 +251,7 @@ Accept wildcard characters: False
 
 ### -ResultSize
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
 
@@ -289,7 +289,7 @@ Accept wildcard characters: False
 
 ### -SourceFolder
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SourceFolder parameter specifies where to search for deleted items in the mailbox. Valid values are:
 
@@ -315,7 +315,7 @@ Accept wildcard characters: False
 
 ### -SubjectContains
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SubjectContains parameter filters the items by the specified text value in the Subject field. If the value contains spaces, enclose the value in quotation marks (").
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-RemoteDomain.md b/exchange/exchange-ps/ExchangePowerShell/Get-RemoteDomain.md
index 7244b020da..40f8322e49 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-RemoteDomain.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-RemoteDomain.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -58,7 +58,7 @@ This example returns all domains where Transport Neutral Encapsulation Format (T
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the remote domain that you want to view. You can use any value that uniquely identifies the remote domain. For example:
 
@@ -80,7 +80,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-RemoteMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Get-RemoteMailbox.md
index b68d619e0f..98107afa9a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-RemoteMailbox.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-RemoteMailbox.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -85,7 +85,7 @@ First, run the following command to prompt you for your credentials and then sto
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the remote mailbox that you want to view. You can use any value that uniquely identifies the remote mailbox. For example:
 
@@ -114,7 +114,7 @@ Accept wildcard characters: False
 
 ### -Anr
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Anr parameter specifies a string on which to perform an ambiguous name resolution (ANR) search. You can specify a partial string and search for objects with an attribute that matches that string. The default attributes searched are:
 
@@ -138,7 +138,7 @@ Accept wildcard characters: False
 
 ### -Archive
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Archive switch is required to return the user's archive mailbox in the results. You don't need to specify a value with this switch.
 
@@ -156,7 +156,7 @@ Accept wildcard characters: False
 
 ### -Credential
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Credential parameter specifies the username and password that's used to run this command. Typically, you use this parameter in scripts or when you need to provide different credentials that have the required permissions.
 
@@ -176,7 +176,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -194,7 +194,7 @@ Accept wildcard characters: False
 
 ### -Filter
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Filter parameter uses OPATH syntax to filter the results by the specified properties and values. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`.
 
@@ -221,7 +221,7 @@ Accept wildcard characters: False
 
 ### -IgnoreDefaultScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange PowerShell session, and to use the entire forest as the scope. You don't need to specify a value with this switch.
 
@@ -244,7 +244,7 @@ Accept wildcard characters: False
 
 ### -OnPremisesOrganizationalUnit
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The OnPremisesOrganizationalUnit parameter filters the results by the object's location in Active Directory.
 
@@ -269,7 +269,7 @@ Accept wildcard characters: False
 
 ### -ReadFromDomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ReadFromDomainController switch specifies that information should be read from a domain controller in the user's domain. You don't need to specify a value with this switch.
 
@@ -291,7 +291,7 @@ Accept wildcard characters: False
 
 ### -ResultSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
 
@@ -311,7 +311,7 @@ Accept wildcard characters: False
 
 ### -SortBy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SortBy parameter specifies the property to sort the results by. You can sort by only one property at a time. The results are sorted in ascending order.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ResourceConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-ResourceConfig.md
index 077decbd72..fc294207d1 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ResourceConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ResourceConfig.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
 Locale: en-US
@@ -43,7 +43,7 @@ This example returns all of the available custom room and equipment mailbox prop
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -63,7 +63,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ResubmitRequest.md b/exchange/exchange-ps/ExchangePowerShell/Get-ResubmitRequest.md
index a4f888b146..d5c1c38d27 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ResubmitRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ResubmitRequest.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -50,7 +50,7 @@ This example returns details about the resubmit request with the identity 1.
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the resubmit request you want to view. Each resubmit request is identified by an incremented integer value.
 
@@ -68,7 +68,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-RetentionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-RetentionPolicy.md
index 877c8a1f16..efc449f3f5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-RetentionPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-RetentionPolicy.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
 Locale: en-US
@@ -45,7 +45,7 @@ This example returns all the properties of the retention policy RP Finance. The
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the policy name.
 
@@ -63,7 +63,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-RetentionPolicyTag.md b/exchange/exchange-ps/ExchangePowerShell/Get-RetentionPolicyTag.md
index a76704a0e9..d7b2481544 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-RetentionPolicyTag.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-RetentionPolicyTag.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
 Locale: en-US
@@ -85,7 +85,7 @@ This example returns all retention tags of Inbox and All types and pipes the res
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the name of the tag.
 
@@ -103,7 +103,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -123,7 +123,7 @@ Accept wildcard characters: False
 
 ### -IncludeSystemTags
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IncludeSystemTags switch specifies whether to return any system tags. You don't need to specify a value with this switch.
 
@@ -141,7 +141,7 @@ Accept wildcard characters: False
 
 ### -Mailbox
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Mailbox parameter returns the retention tags that are assigned to the retention policy that's applied to the specified mailbox. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -172,7 +172,7 @@ Accept wildcard characters: False
 
 ### -OptionalInMailbox
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The OptionalInMailbox parameter is used with the Mailbox parameter to return any opt-in retention tags that are assigned to the specified mailbox. You don't need to specify a value with this switch.
 
@@ -192,7 +192,7 @@ Accept wildcard characters: False
 
 ### -Types
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Types parameter specifies the type of retention tag to return. Valid values include:
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-RoleAssignmentPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-RoleAssignmentPolicy.md
index ba3b5931f4..b9add7499b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-RoleAssignmentPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-RoleAssignmentPolicy.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -65,7 +65,7 @@ For more information about pipelining and the Format-List cmdlet, see [About Pip
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the name of the assignment policy to view. If the name contains spaces, enclose the name in quotation marks (").
 
@@ -83,7 +83,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-RoleGroup.md b/exchange/exchange-ps/ExchangePowerShell/Get-RoleGroup.md
index b39c089258..cc8f06f83a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-RoleGroup.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-RoleGroup.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -71,7 +71,7 @@ This example retrieves a list of all linked role groups and the Active Directory
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The Identity parameter specifies the role group to retrieve. If the name of the role group contains spaces, enclose the name in quotation marks (").
 
@@ -91,7 +91,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -111,7 +111,7 @@ Accept wildcard characters: False
 
 ### -Filter
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The Filter parameter uses OPATH syntax to filter the results by the specified properties and values. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`.
 
@@ -147,7 +147,7 @@ Accept wildcard characters: False
 
 ### -ReadFromDomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -171,7 +171,7 @@ Accept wildcard characters: False
 
 ### -ResultSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
 
@@ -189,7 +189,7 @@ Accept wildcard characters: False
 
 ### -ShowPartnerLinked
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 This parameter is functional only in the cloud-based service.
 
@@ -211,7 +211,7 @@ Accept wildcard characters: False
 
 ### -SortBy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The SortBy parameter specifies the property to sort the results by. You can sort by only one property at a time. The results are sorted in ascending order.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-RoleGroupMember.md b/exchange/exchange-ps/ExchangePowerShell/Get-RoleGroupMember.md
index 0d162d0acd..cb790ab104 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-RoleGroupMember.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-RoleGroupMember.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -54,7 +54,7 @@ This example retrieves a list of all the members of the Organization Administrat
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The Identity parameter specifies the role group for which member information should be retrieved. If the role group name contains spaces, enclose the name in quotation marks (").
 
@@ -72,7 +72,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -92,7 +92,7 @@ Accept wildcard characters: False
 
 ### -ReadFromDomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -116,7 +116,7 @@ Accept wildcard characters: False
 
 ### -ResultSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-RpcClientAccess.md b/exchange/exchange-ps/ExchangePowerShell/Get-RpcClientAccess.md
index 75649aaa67..cda52a6cce 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-RpcClientAccess.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-RpcClientAccess.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -50,7 +50,7 @@ This example returns detailed information for the RPC Client Access service on t
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -68,7 +68,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Exchange server that you want to view.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SearchDocumentFormat.md b/exchange/exchange-ps/ExchangePowerShell/Get-SearchDocumentFormat.md
index a9c7d69dd8..3c75cb6c59 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SearchDocumentFormat.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-SearchDocumentFormat.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -52,7 +52,7 @@ This example retrieves all properties of the docx file format.
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the identity of a file format.
 
@@ -70,7 +70,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SecurityPrincipal.md b/exchange/exchange-ps/ExchangePowerShell/Get-SecurityPrincipal.md
index e79ff3157f..3028fa32a9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SecurityPrincipal.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-SecurityPrincipal.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -72,7 +72,7 @@ This example retrieves well-known security principals and displays only the Name
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The Identity parameter specifies the security principal. When the security principal is explicitly specified by using this parameter, no additional security principals are returned.
 
@@ -90,7 +90,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -110,7 +110,7 @@ Accept wildcard characters: False
 
 ### -Filter
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The Filter parameter uses OPATH syntax to filter the results by the specified properties and values. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`.
 
@@ -137,7 +137,7 @@ Accept wildcard characters: False
 
 ### -IncludeDomainLocalFrom
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -159,7 +159,7 @@ Accept wildcard characters: False
 
 ### -OrganizationalUnit
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The OrganizationalUnit parameter filters the results based on the object's location in Active Directory. Only objects that exist in the specified location are returned. Valid input for this parameter is an organizational unit (OU) or domain that's returned by the Get-OrganizationalUnit cmdlet. You can use any value that uniquely identifies the OU or domain. For example:
 
@@ -182,7 +182,7 @@ Accept wildcard characters: False
 
 ### -ResultSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
 
@@ -200,7 +200,7 @@ Accept wildcard characters: False
 
 ### -RoleGroupAssignable
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The RoleGroupAssignable switch filters security principals by returning only objects that can be assigned to an RBAC role group. You don't need to specify a value with this switch.
 
@@ -218,7 +218,7 @@ Accept wildcard characters: False
 
 ### -Types
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The Types parameter filters the results by object type. Valid values are:
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SendConnector.md b/exchange/exchange-ps/ExchangePowerShell/Get-SendConnector.md
index b88096e120..2f89d0aed1 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SendConnector.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-SendConnector.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -43,7 +43,7 @@ This example displays detailed information about the Send connector named Contos
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the name, or GUID of the Send connector. If the Identity name contains spaces, enclose the name in quotation marks ("). You can omit the Identity parameter label. You can also include the server name by using the format ServerName\\ConnectorName.
 
@@ -61,7 +61,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SenderFilterConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-SenderFilterConfig.md
index 3a2fac09b4..0640040e6e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SenderFilterConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-SenderFilterConfig.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailControl-Help.xml
 Locale: en-US
@@ -43,7 +43,7 @@ This example returns detailed information about the Sender Filter configuration
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -61,7 +61,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 

From 6102e6acd53564e876355feee7b9c3a8fbcdbb38 Mon Sep 17 00:00:00 2001
From: Chris Davis <chris.davis@microsoft.com>
Date: Thu, 7 Aug 2025 12:08:54 -0700
Subject: [PATCH 131/145] Add Exchange Server SE 4

---
 .../ExchangePowerShell/Get-SenderIdConfig.md  |   4 +-
 .../Get-SenderReputationConfig.md             |   4 +-
 .../Get-ServerComponentState.md               |   8 +-
 .../ExchangePowerShell/Get-ServerHealth.md    |   8 +-
 .../Get-ServerMonitoringOverride.md           |   4 +-
 .../ExchangePowerShell/Get-SettingOverride.md |   6 +-
 .../ExchangePowerShell/Get-SharingPolicy.md   |   6 +-
 .../ExchangePowerShell/Get-SiteMailbox.md     |  16 +-
 .../Get-SiteMailboxDiagnostics.md             |  12 +-
 .../Get-SiteMailboxProvisioningPolicy.md      |   6 +-
 .../ExchangePowerShell/Get-SmimeConfig.md     |   4 +-
 .../Get-StoreUsageStatistics.md               |  16 +-
 .../ExchangePowerShell/Get-SweepRule.md       |  12 +-
 .../ExchangePowerShell/Get-SystemMessage.md   |   8 +-
 .../Get-TextMessagingAccount.md               |  12 +-
 .../Get-ThrottlingPolicy.md                   |  12 +-
 .../Get-ThrottlingPolicyAssociation.md        |  14 +-
 .../ExchangePowerShell/Get-TransportAgent.md  |   8 +-
 .../ExchangePowerShell/Get-TransportConfig.md |   6 +-
 .../Get-TransportPipeline.md                  |   4 +-
 .../ExchangePowerShell/Get-TransportRule.md   |  14 +-
 .../Get-TransportRuleAction.md                |   4 +-
 .../Get-TransportRulePredicate.md             |   4 +-
 .../ExchangePowerShell/Get-TransportServer.md |   6 +-
 .../Get-TransportService.md                   |   6 +-
 .../ExchangePowerShell/Get-Trust.md           |   4 +-
 .../ExchangePowerShell/Get-User.md            |  36 ++---
 .../ExchangePowerShell/Get-UserPhoto.md       |  28 ++--
 .../Get-UserPrincipalNamesSuffix.md           |   4 +-
 .../Get-WebServicesVirtualDirectory.md        |  12 +-
 .../Get-X400AuthoritativeDomain.md            |   6 +-
 .../Import-DlpPolicyCollection.md             |  14 +-
 .../Import-DlpPolicyTemplate.md               |   8 +-
 .../Import-ExchangeCertificate.md             |  20 +--
 .../Import-JournalRuleCollection.md           |  12 +-
 .../Import-RecipientDataProperty.md           |  16 +-
 .../Import-TransportRuleCollection.md         |  14 +-
 .../Install-TransportAgent.md                 |  16 +-
 .../Invoke-ComplianceSearchActionStep.md      |   8 +-
 .../Invoke-MonitoringProbe.md                 |  24 +--
 .../ExchangePowerShell/Mount-Database.md      |  16 +-
 .../Move-ActiveMailboxDatabase.md             |  40 ++---
 .../ExchangePowerShell/Move-AddressList.md    |  12 +-
 .../ExchangePowerShell/Move-DatabasePath.md   |  20 +--
 .../Move-OfflineAddressBook.md                |  12 +-
 .../ExchangePowerShell/New-AcceptedDomain.md  |  14 +-
 .../New-ActiveSyncDeviceAccessRule.md         |  14 +-
 .../New-ActiveSyncMailboxPolicy.md            | 114 +++++++-------
 .../New-ActiveSyncVirtualDirectory.md         |  36 ++---
 .../New-AddressBookPolicy.md                  |  18 +--
 .../ExchangePowerShell/New-AddressList.md     |  56 +++----
 .../New-AddressRewriteEntry.md                |  18 +--
 .../New-AdminAuditLogSearch.md                |  26 ++--
 .../exchange-ps/ExchangePowerShell/New-App.md |  44 +++---
 .../ExchangePowerShell/New-AuthRedirect.md    |  12 +-
 .../ExchangePowerShell/New-AuthServer.md      |  22 +--
 .../New-AuthenticationPolicy.md               |  40 ++---
 .../New-AutodiscoverVirtualDirectory.md       |  36 ++---
 .../New-ClassificationRuleCollection.md       |  10 +-
 .../New-ClientAccessRule.md                   |  30 ++--
 .../New-ComplianceSearch.md                   |  26 ++--
 .../New-ComplianceSearchAction.md             |  54 +++----
 .../New-ComplianceSecurityFilter.md           |  18 +--
 .../New-DataClassification.md                 |  18 +--
 .../New-DatabaseAvailabilityGroup.md          |  24 +--
 .../New-DatabaseAvailabilityGroupNetwork.md   |  20 +--
 .../New-DeliveryAgentConnector.md             |  28 ++--
 .../New-DistributionGroup.md                  |  50 +++---
 .../ExchangePowerShell/New-DlpPolicy.md       |  22 +--
 .../New-DynamicDistributionGroup.md           |  68 ++++-----
 .../New-EcpVirtualDirectory.md                |  28 ++--
 .../New-EdgeSubscription.md                   |  22 +--
 .../New-EdgeSyncServiceConfig.md              |  36 ++---
 .../New-EmailAddressPolicy.md                 |  60 ++++----
 .../New-ExchangeCertificate.md                |  40 ++---
 .../New-ExchangeSettings.md                   |  12 +-
 .../ExchangePowerShell/New-FederationTrust.md |  24 +--
 .../ExchangePowerShell/New-Fingerprint.md     |  10 +-
 .../New-ForeignConnector.md                   |  16 +-
 .../New-GlobalAddressList.md                  |  52 +++----
 .../New-HybridConfiguration.md                |  26 ++--
 .../ExchangePowerShell/New-InboxRule.md       | 142 +++++++++---------
 .../New-IntraOrganizationConnector.md         |  16 +-
 .../ExchangePowerShell/New-JournalRule.md     |  18 +--
 .../ExchangePowerShell/New-MailContact.md     |  42 +++---
 .../ExchangePowerShell/New-MailMessage.md     |  14 +-
 .../ExchangePowerShell/New-MailUser.md        |  54 +++----
 .../ExchangePowerShell/New-Mailbox.md         | 112 +++++++-------
 .../New-MailboxAuditLogSearch.md              |  28 ++--
 .../ExchangePowerShell/New-MailboxDatabase.md |  32 ++--
 .../New-MailboxExportRequest.md               |  62 ++++----
 .../ExchangePowerShell/New-MailboxFolder.md   |  12 +-
 .../New-MailboxImportRequest.md               |  58 +++----
 .../New-MailboxRepairRequest.md               |  22 +--
 .../New-MailboxRestoreRequest.md              |  64 ++++----
 .../ExchangePowerShell/New-MailboxSearch.md   |  54 +++----
 .../New-MalwareFilterPolicy.md                |  46 +++---
 97 files changed, 1223 insertions(+), 1223 deletions(-)

diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SenderIdConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-SenderIdConfig.md
index a48fe97c5b..81bcb35fbc 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SenderIdConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-SenderIdConfig.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailControl-Help.xml
 Locale: en-US
@@ -42,7 +42,7 @@ This example returns detailed information about the Sender ID configuration on t
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SenderReputationConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-SenderReputationConfig.md
index 8bec50233b..e4512448d3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SenderReputationConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-SenderReputationConfig.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailControl-Help.xml
 Locale: en-US
@@ -42,7 +42,7 @@ This example returns detailed information about the sender reputation configurat
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ServerComponentState.md b/exchange/exchange-ps/ExchangePowerShell/Get-ServerComponentState.md
index 357deadb5d..8f7f96e303 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ServerComponentState.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ServerComponentState.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -51,7 +51,7 @@ This example returns detailed information for the component state of the Unified
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the Exchange server where you want to view the configuration settings. You can use the following values:
 
@@ -73,7 +73,7 @@ Accept wildcard characters: False
 
 ### -Component
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Component parameter specifies the component or endpoint for which you want to retrieve the state. To see the available values, run the following command: `Get-ServerComponentState <ServerName>`.
 
@@ -91,7 +91,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ServerHealth.md b/exchange/exchange-ps/ExchangePowerShell/Get-ServerHealth.md
index 19532a3368..5b71ddbc7c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ServerHealth.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ServerHealth.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -55,7 +55,7 @@ This example returns the server health for server Server01.
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
 
@@ -78,7 +78,7 @@ Accept wildcard characters: False
 
 ### -HaImpactingOnly
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The HaImpactingOnly switch specifies whether the cmdlet must roll up only the monitors that have HaImpacting set to True. You don't need to specify a value with this switch.
 
@@ -96,7 +96,7 @@ Accept wildcard characters: False
 
 ### -HealthSet
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The HealthSet parameter returns the health state of a group of monitors. Monitors that are similar or are tied to a component's architecture are grouped to form a health set. You can determine the collection of monitors (and associated probes and responders) in a given health set by using the Get-MonitoringItemIdentity cmdlet.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ServerMonitoringOverride.md b/exchange/exchange-ps/ExchangePowerShell/Get-ServerMonitoringOverride.md
index afcf7555af..720886c80d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ServerMonitoringOverride.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ServerMonitoringOverride.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -42,7 +42,7 @@ This example retrieves all monitoring overrides for the Exch01 server.
 
 ### -Server
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SettingOverride.md b/exchange/exchange-ps/ExchangePowerShell/Get-SettingOverride.md
index 3a53168c56..017e066e64 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SettingOverride.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-SettingOverride.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -54,7 +54,7 @@ This example displays a detailed information for the setting override object nam
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the setting override that you want to view. You can use any value that uniquely identifies the override. For example:
 
@@ -76,7 +76,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SharingPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-SharingPolicy.md
index 8f7acb12f7..86326ea869 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SharingPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-SharingPolicy.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
 Locale: en-US
@@ -52,7 +52,7 @@ This example retrieves the full information for the sharing policy Fabrikam.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the sharing policy that you want to view. You can use one of the following values:
 
@@ -75,7 +75,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SiteMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Get-SiteMailbox.md
index 72d4c05408..e6cecbe607 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SiteMailbox.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-SiteMailbox.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -66,7 +66,7 @@ This example queries for site mailboxes that are marked for deletion and removes
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the identity of the site mailbox. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -91,7 +91,7 @@ Accept wildcard characters: False
 
 ### -Anr
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Anr parameter specifies a string on which to perform an ambiguous name resolution (ANR) search. You can specify a partial string and search for objects with an attribute that matches that string. The default attributes searched are:
 
@@ -115,7 +115,7 @@ Accept wildcard characters: False
 
 ### -BypassOwnerCheck
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The BypassOwnerCheck parameter is used when the account that's running the command isn't a member or owner of the site mailbox. You don't need to specify a value with this switch.
 
@@ -135,7 +135,7 @@ Accept wildcard characters: False
 
 ### -DeletedSiteMailbox
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DeletedSiteMailbox switch returns site mailboxes that have been marked for pending deletion. You don't need to specify a value with this switch.
 
@@ -155,7 +155,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -173,7 +173,7 @@ Accept wildcard characters: False
 
 ### -ReadFromDomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ReadFromDomainController switch specifies that information should be read from a domain controller in the user's domain. You don't need to specify a value with this switch.
 
@@ -195,7 +195,7 @@ Accept wildcard characters: False
 
 ### -ResultSize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SiteMailboxDiagnostics.md b/exchange/exchange-ps/ExchangePowerShell/Get-SiteMailboxDiagnostics.md
index 89878ddd9b..d1fc25520b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SiteMailboxDiagnostics.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-SiteMailboxDiagnostics.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -57,7 +57,7 @@ This example returns the event information for the Marketing Events 2015 site ma
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the site mailbox that you want to view. You can use any value that uniquely identifies the site mailbox. For example:
 
@@ -82,7 +82,7 @@ Accept wildcard characters: False
 
 ### -BypassOwnerCheck
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The BypassOwnerCheck parameter is used when the account that's running the command isn't a member or owner of the site mailbox. You don't need to specify a value with this switch.
 
@@ -102,7 +102,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -123,7 +123,7 @@ Accept wildcard characters: False
 
 ### -SendMeEmail
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SendMeEmail switch specifies that the diagnostic information is sent to the primary SMTP email address of the user account that's running the command. You don't need to specify a value with this switch.
 
@@ -141,7 +141,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SiteMailboxProvisioningPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-SiteMailboxProvisioningPolicy.md
index aa2e7109d2..5f5dcbe69b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SiteMailboxProvisioningPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-SiteMailboxProvisioningPolicy.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.WebClient-Help.xml
 Locale: en-US
@@ -54,7 +54,7 @@ This example returns detailed information about the site mailbox provisioning po
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the site mailbox provisioning policy that you want to view. You can use any value that uniquely identifies the policy. For example:
 
@@ -76,7 +76,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SmimeConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-SmimeConfig.md
index 248d152e27..ba46b91d68 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SmimeConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-SmimeConfig.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -42,7 +42,7 @@ This example shows the S/MIME configuration that's used with Outlook on the web.
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter is reserved for internal Microsoft use.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-StoreUsageStatistics.md b/exchange/exchange-ps/ExchangePowerShell/Get-StoreUsageStatistics.md
index df48bbb8a6..8fb4dd1461 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-StoreUsageStatistics.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-StoreUsageStatistics.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -80,7 +80,7 @@ This example retrieves store usage statistics for database DB1 and sorts the out
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the mailbox to get usage statistics from. You can use one of the following values to identify the mailbox:
 
@@ -110,7 +110,7 @@ Accept wildcard characters: False
 
 ### -Database
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Database parameter specifies the name of the mailbox database to get usage statistics from (the top 25 largest mailboxes on the specified mailbox database). You can use any value that uniquely identifies the mailbox database. For example:
 
@@ -134,7 +134,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Mailbox server to get usage statistics from (the top 25 mailboxes on all active databases on the specified server). You can use one of the following values to identify the server:
 
@@ -157,7 +157,7 @@ Accept wildcard characters: False
 
 ### -CopyOnServer
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The CopyOnServer parameter specifies the mailbox database copy to get usage statistics from. You can use any value that uniquely identifies the mailbox database. For example:
 
@@ -181,7 +181,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -199,7 +199,7 @@ Accept wildcard characters: False
 
 ### -Filter
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Filter parameter uses OPATH syntax to filter the results by the specified properties and values. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`.
 
@@ -226,7 +226,7 @@ Accept wildcard characters: False
 
 ### -IncludePassive
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IncludePassive switch specifies whether to include usage statistics from active and passive copies of mailbox databases on the Mailbox server you specified with the Server parameter. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SweepRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-SweepRule.md
index 55817a5d14..da057d7310 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SweepRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-SweepRule.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -61,7 +61,7 @@ This example returns detailed information for the Sweep rule with the specified
 
 ### -Identity
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the Sweep rule that you want to view. You can use any value that uniquely identifies the rule. For example:
 
@@ -83,7 +83,7 @@ Accept wildcard characters: False
 
 ### -BypassScopeCheck
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The BypassScopeCheck switch specifies whether to bypass the scope check for the user that's running the command. You don't need to specify a value with this switch.
 
@@ -101,7 +101,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -121,7 +121,7 @@ Accept wildcard characters: False
 
 ### -Mailbox
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Mailbox parameter filters the results by the specified mailbox. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -150,7 +150,7 @@ Accept wildcard characters: False
 
 ### -Provider
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Provider parameter filters the results by the specified provider.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-SystemMessage.md b/exchange/exchange-ps/ExchangePowerShell/Get-SystemMessage.md
index f04bf393c2..e1fe24a3eb 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-SystemMessage.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-SystemMessage.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -76,7 +76,7 @@ You should output the list to a file, because the list is very long, and you get
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the custom system message that you want to view. You can use any value that uniquely identifies the system message. For example:
 
@@ -145,7 +145,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -165,7 +165,7 @@ Accept wildcard characters: False
 
 ### -Original
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Original switch filters the results by the default system messages that are included with Exchange. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-TextMessagingAccount.md b/exchange/exchange-ps/ExchangePowerShell/Get-TextMessagingAccount.md
index 929df3f676..6991b2a2b4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-TextMessagingAccount.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-TextMessagingAccount.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.WebClient-Help.xml
 Locale: en-US
@@ -57,7 +57,7 @@ This example finds all user mailboxes where text messaging notifications are ena
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the mailbox that you want to view. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -86,7 +86,7 @@ Accept wildcard characters: False
 
 ### -Credential
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Credential parameter specifies the username and password that's used to run this command. Typically, you use this parameter in scripts or when you need to provide different credentials that have the required permissions.
 
@@ -106,7 +106,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -126,7 +126,7 @@ Accept wildcard characters: False
 
 ### -ReadFromDomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ReadFromDomainController switch specifies that information should be read from a domain controller in the user's domain. You don't need to specify a value with this switch.
 
@@ -148,7 +148,7 @@ Accept wildcard characters: False
 
 ### -ResultSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ThrottlingPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-ThrottlingPolicy.md
index 43844b9234..3425dedb68 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ThrottlingPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ThrottlingPolicy.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.WebClient-Help.xml
 Locale: en-US
@@ -57,7 +57,7 @@ This example displays the parameters and values for throttling policy Throttling
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter identifies the name of the throttling policy that you want to return settings for.
 
@@ -75,7 +75,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -95,7 +95,7 @@ Accept wildcard characters: False
 
 ### -Diagnostics
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Diagnostics switch specifies whether you want the output to include the diagnostics string. You don't need to specify a value with this switch.
 
@@ -113,7 +113,7 @@ Accept wildcard characters: False
 
 ### -Explicit
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Explicit switch specifies whether to return only the policy settings that have been directly assigned using this policy. You don't need to specify a value with this switch.
 
@@ -131,7 +131,7 @@ Accept wildcard characters: False
 
 ### -ThrottlingPolicyScope
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ThrottlingPolicyScope parameter specifies the scope of the throttling policy. You can use the following values:
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ThrottlingPolicyAssociation.md b/exchange/exchange-ps/ExchangePowerShell/Get-ThrottlingPolicyAssociation.md
index 8ba0ee4aea..96ab8b7745 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-ThrottlingPolicyAssociation.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-ThrottlingPolicyAssociation.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -73,7 +73,7 @@ This example returns detailed information for the throttling policy association
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the throttling policy association that you want to view. You can use any value that uniquely identifies the throttling policy association. For example:
 
@@ -105,7 +105,7 @@ Accept wildcard characters: False
 
 ### -Anr
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Anr parameter specifies a string on which to perform an ambiguous name resolution (ANR) search. You can specify a partial string and search for objects with an attribute that matches that string. The default attributes searched are:
 
@@ -129,7 +129,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -149,7 +149,7 @@ Accept wildcard characters: False
 
 ### -ResultSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
 
@@ -167,7 +167,7 @@ Accept wildcard characters: False
 
 ### -SortBy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -185,7 +185,7 @@ Accept wildcard characters: False
 
 ### -ThrottlingPolicy
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ThrottlingPolicy parameter filters the results by throttling policy. You can use any value that uniquely identifies the throttling policy. For example:
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-TransportAgent.md b/exchange/exchange-ps/ExchangePowerShell/Get-TransportAgent.md
index 1be1f2f60b..6d15812ff3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-TransportAgent.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-TransportAgent.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -51,7 +51,7 @@ This example displays detailed information about the Transport Rule agent that's
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the display name of the transport agent to be displayed. The length of the name can't exceed 64 characters.
 
@@ -69,7 +69,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -89,7 +89,7 @@ Accept wildcard characters: False
 
 ### -TransportService
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TransportService parameter specifies the transport service that you want to view or modify. Valid values for this parameter are:
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-TransportConfig.md b/exchange/exchange-ps/ExchangePowerShell/Get-TransportConfig.md
index ffef43d5a4..aae5714bfc 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-TransportConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-TransportConfig.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -52,7 +52,7 @@ This example lists all delivery status notification-related (DSN) configuration
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -72,7 +72,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-TransportPipeline.md b/exchange/exchange-ps/ExchangePowerShell/Get-TransportPipeline.md
index 31d4c51174..75dccf9a86 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-TransportPipeline.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-TransportPipeline.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -57,7 +57,7 @@ This example returns a list of agents registered in the transport pipeline, with
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-TransportRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-TransportRule.md
index 00a45e85c7..8a2eecaadb 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-TransportRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-TransportRule.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -73,7 +73,7 @@ In on-premises Exchange, this example returns a summary list of all rules that e
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the rule that you want to view. You can use any value that uniquely identifies the rule. For example:
 
@@ -95,7 +95,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -117,7 +117,7 @@ Accept wildcard characters: False
 
 ### -State
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The State parameter specifies filters the results by enabled or disabled rules. Valid values are:
 
@@ -140,7 +140,7 @@ Accept wildcard characters: False
 
 ### -DlpPolicy
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 **Note**: This parameter is functional only in on-premises Exchange.
 
@@ -185,7 +185,7 @@ Accept wildcard characters: False
 
 ### -Filter
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Filter parameter filters the results by using an OPATH. This parameter searches the Description property, which includes the conditions, exceptions, actions and the associated values of a transport rule.
 
@@ -207,7 +207,7 @@ Accept wildcard characters: False
 
 ### -ResultSize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-TransportRuleAction.md b/exchange/exchange-ps/ExchangePowerShell/Get-TransportRuleAction.md
index 5d266e9ba2..e68c4223b8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-TransportRuleAction.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-TransportRuleAction.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -53,7 +53,7 @@ For more information about pipelining, see [About Pipelines](https://learn.micro
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Name parameter specifies the name of the action that you want to view. To see the list of available names, run the command Get-TransportRuleAction.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-TransportRulePredicate.md b/exchange/exchange-ps/ExchangePowerShell/Get-TransportRulePredicate.md
index 0a039b0a93..bf8df73ee2 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-TransportRulePredicate.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-TransportRulePredicate.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -64,7 +64,7 @@ For more information about how to work with the output of a command, see [Workin
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Name parameter specifies the name of the predicate that you want to view. To see the list of available names, run the command Get-TransportRulePredicate.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-TransportServer.md b/exchange/exchange-ps/ExchangePowerShell/Get-TransportServer.md
index c4e3d2faa6..03fbc9ba82 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-TransportServer.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-TransportServer.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -52,7 +52,7 @@ This example retrieves the detailed transport configuration information for the
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the Transport server that you want to view. You can use any value that uniquely identifies the server. For example:
 
@@ -75,7 +75,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-TransportService.md b/exchange/exchange-ps/ExchangePowerShell/Get-TransportService.md
index 2f68807ab2..dde404dc0d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-TransportService.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-TransportService.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -50,7 +50,7 @@ This example retrieves the detailed transport configuration information for the
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the Mailbox server that hosts the Transport service configuration you want to view. You can use any value that uniquely identifies the server. For example:
 
@@ -75,7 +75,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-Trust.md b/exchange/exchange-ps/ExchangePowerShell/Get-Trust.md
index a188003b37..0ebb762b37 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-Trust.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-Trust.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -44,7 +44,7 @@ This example enumerates all trusts for the domain Contoso.com.
 
 ### -DomainName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainName parameter specifies that trusts returned are restricted to the domain name specified.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-User.md b/exchange/exchange-ps/ExchangePowerShell/Get-User.md
index 1c78f20404..6d70b49b80 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-User.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-User.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -104,9 +104,9 @@ This example uses the Filter parameter to retrieve information about all users t
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
-The Identity parameter the user that you want to view. You can use any value that uniquely identifies the user. For example:
+The Identity parameter specifies the user that you want to view. You can use any value that uniquely identifies the user. For example:
 
 - Name
 - User principal name (UPN)
@@ -128,7 +128,7 @@ Accept wildcard characters: False
 
 ### -Anr
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Anr parameter specifies a string on which to perform an ambiguous name resolution (ANR) search. You can specify a partial string and search for objects with an attribute that matches that string. The default attributes searched are:
 
@@ -152,7 +152,7 @@ Accept wildcard characters: False
 
 ### -Arbitration
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -176,7 +176,7 @@ Accept wildcard characters: False
 
 ### -AuditLog
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -200,7 +200,7 @@ Accept wildcard characters: False
 
 ### -AuxAuditLog
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -224,7 +224,7 @@ Accept wildcard characters: False
 
 ### -Credential
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -246,7 +246,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -266,7 +266,7 @@ Accept wildcard characters: False
 
 ### -Filter
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The Filter parameter uses OPATH syntax to filter the results by the specified properties and values. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`.
 
@@ -293,7 +293,7 @@ Accept wildcard characters: False
 
 ### -IgnoreDefaultScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -360,7 +360,7 @@ Accept wildcard characters: False
 
 ### -OrganizationalUnit
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The OrganizationalUnit parameter filters the results based on the object's location in Active Directory. Only objects that exist in the specified location are returned. Valid input for this parameter is an organizational unit (OU) or domain that's returned by the Get-OrganizationalUnit cmdlet. You can use any value that uniquely identifies the OU or domain. For example:
 
@@ -383,7 +383,7 @@ Accept wildcard characters: False
 
 ### -PublicFolder
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance
 
 The PublicFolder switch is required to return public folder mailboxes in the results. You don't need to specify a value with this switch.
 
@@ -403,7 +403,7 @@ Accept wildcard characters: False
 
 ### -ReadFromDomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -427,7 +427,7 @@ Accept wildcard characters: False
 
 ### -RecipientTypeDetails
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The RecipientTypeDetails parameter filters the results by the specified user subtype. Valid values are:
 
@@ -471,7 +471,7 @@ Accept wildcard characters: False
 
 ### -ResultSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
 
@@ -489,7 +489,7 @@ Accept wildcard characters: False
 
 ### -Sortby
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The SortBy parameter specifies the property to sort the results by. You can sort by only one property at a time. The results are sorted in ascending order.
 
@@ -518,7 +518,7 @@ Accept wildcard characters: False
 
 ### -SupervisoryReviewPolicy
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-UserPhoto.md b/exchange/exchange-ps/ExchangePowerShell/Get-UserPhoto.md
index fe70eb0bcf..14e09ae227 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-UserPhoto.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-UserPhoto.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -82,7 +82,7 @@ This example displays information about the user photo that was uploaded to Pila
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the user account. You can use any value that uniquely identifies the user account. For example:
 
@@ -111,7 +111,7 @@ Accept wildcard characters: False
 
 ### -Anr
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Anr parameter specifies a string on which to perform an ambiguous name resolution (ANR) search. You can specify a partial string and search for objects with an attribute that matches that string. The default attributes searched are:
 
@@ -135,7 +135,7 @@ Accept wildcard characters: False
 
 ### -Credential
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Credential parameter specifies the username and password that's used to run this command. Typically, you use this parameter in scripts or when you need to provide different credentials that have the required permissions.
 
@@ -155,7 +155,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -173,7 +173,7 @@ Accept wildcard characters: False
 
 ### -Filter
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Filter parameter uses OPATH syntax to filter the results by the specified properties and values. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`.
 
@@ -200,7 +200,7 @@ Accept wildcard characters: False
 
 ### -GroupMailbox
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The GroupMailbox switch is required to return Microsoft 365 Groups in the results. You don't need to specify a value with this switch.
 
@@ -218,7 +218,7 @@ Accept wildcard characters: False
 
 ### -IgnoreDefaultScope
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange PowerShell session, and to use the entire forest as the scope. You don't need to specify a value with this switch.
 
@@ -241,7 +241,7 @@ Accept wildcard characters: False
 
 ### -OrganizationalUnit
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The OrganizationalUnit parameter filters the results based on the object's location in Active Directory. Only objects that exist in the specified location are returned. Valid input for this parameter is an organizational unit (OU) or domain that's returned by the Get-OrganizationalUnit cmdlet. You can use any value that uniquely identifies the OU or domain. For example:
 
@@ -264,7 +264,7 @@ Accept wildcard characters: False
 
 ### -PhotoType
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -282,7 +282,7 @@ Accept wildcard characters: False
 
 ### -Preview
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Preview switch filters the results by preview photos. You don't need to specify a value with this switch.
 
@@ -302,7 +302,7 @@ Accept wildcard characters: False
 
 ### -ReadFromDomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ReadFromDomainController switch specifies that information should be read from a domain controller in the user's domain. You don't need to specify a value with this switch.
 
@@ -324,7 +324,7 @@ Accept wildcard characters: False
 
 ### -ResultSize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
 
@@ -342,7 +342,7 @@ Accept wildcard characters: False
 
 ### -SortBy
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SortBy parameter specifies the property to sort the results by. You can sort by only one property at a time. The results are sorted in ascending order.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-UserPrincipalNamesSuffix.md b/exchange/exchange-ps/ExchangePowerShell/Get-UserPrincipalNamesSuffix.md
index a33308cebd..6430bf259d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-UserPrincipalNamesSuffix.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-UserPrincipalNamesSuffix.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -48,7 +48,7 @@ This example returns all UPN suffixes for the Active Directory forest.
 
 ### -OrganizationalUnit
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The OrganizationalUnit parameter filters the results based on the object's location in Active Directory. Only objects that exist in the specified location are returned. Valid input for this parameter is an organizational unit (OU) or domain that's returned by the Get-OrganizationalUnit cmdlet. You can use any value that uniquely identifies the OU or domain. For example:
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-WebServicesVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Get-WebServicesVirtualDirectory.md
index da0f74a7e0..9d9c09075b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-WebServicesVirtualDirectory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-WebServicesVirtualDirectory.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -73,7 +73,7 @@ This example returns a summary list of all virtual directories in the client acc
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the EWS virtual directory that you want to view. You can use any value that uniquely identifies the virtual directory. For example:
 
@@ -99,7 +99,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Exchange server that hosts the virtual directory. You can use any value that uniquely identifies the server. For example:
 
@@ -124,7 +124,7 @@ Accept wildcard characters: False
 
 ### -ADPropertiesOnly
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ADPropertiesOnly switch specifies whether to return only the virtual directory properties that are stored in Active Directory. You don't need to specify a value with this switch.
 
@@ -144,7 +144,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -162,7 +162,7 @@ Accept wildcard characters: False
 
 ### -ShowMailboxVirtualDirectories
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ShowMailboxVirtualDirectories switch shows information about backend virtual directories on Mailbox servers. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-X400AuthoritativeDomain.md b/exchange/exchange-ps/ExchangePowerShell/Get-X400AuthoritativeDomain.md
index a16c7bb305..c236807d50 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Get-X400AuthoritativeDomain.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Get-X400AuthoritativeDomain.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -43,7 +43,7 @@ This example displays detailed information about the X.400 authoritative domain
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies a string value for the X.400 authoritative domain. Enter either the GUID or the name of the remote domain.
 
@@ -61,7 +61,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Import-DlpPolicyCollection.md b/exchange/exchange-ps/ExchangePowerShell/Import-DlpPolicyCollection.md
index 52656dd2d1..bbfb2641f2 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Import-DlpPolicyCollection.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Import-DlpPolicyCollection.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -52,7 +52,7 @@ This example imports the DLP policy collection in the file C:\\My Documents\\DLP
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the name of the DLP policy you want to import. The DLP policy must exist in the XML file you specify with the FileData parameter.
 
@@ -70,7 +70,7 @@ Accept wildcard characters: False
 
 ### -FileData
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The FileData parameter specifies the DLP policy collection file you want to import.
 
@@ -90,7 +90,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -111,7 +111,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -129,7 +129,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -149,7 +149,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Import-DlpPolicyTemplate.md b/exchange/exchange-ps/ExchangePowerShell/Import-DlpPolicyTemplate.md
index 812c878550..1399990e4d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Import-DlpPolicyTemplate.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Import-DlpPolicyTemplate.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -44,7 +44,7 @@ This example imports the DLP policy template file C:\\My Documents\\External DLP
 
 ### -FileData
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The FileData parameter specifies the DLP policy template file you want to import.
 
@@ -64,7 +64,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -85,7 +85,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Import-ExchangeCertificate.md b/exchange/exchange-ps/ExchangePowerShell/Import-ExchangeCertificate.md
index 506ea14827..69bbc1e97c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Import-ExchangeCertificate.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Import-ExchangeCertificate.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -103,7 +103,7 @@ This example imports a chain of certificates from the PKCS #7 file C:\\Certifica
 
 ### -FileData
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The FileData parameter specifies the contents of the certificate file that you want to import.
 
@@ -155,7 +155,7 @@ Accept wildcard characters: False
 
 ### -Instance
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is deprecated and no longer used.
 
@@ -173,7 +173,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -194,7 +194,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -214,7 +214,7 @@ Accept wildcard characters: False
 
 ### -FriendlyName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The FriendlyName parameter specifies a friendly name for the certificate. The value must be less than 64 characters.
 
@@ -234,7 +234,7 @@ Accept wildcard characters: False
 
 ### -Password
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Password parameter specifies the password that's required to import the certificate.
 
@@ -258,7 +258,7 @@ Accept wildcard characters: False
 
 ### -PrivateKeyExportable
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PrivateKeyExportable parameter specifies whether the certificate has an exportable private key and controls whether you can export the certificate from this server. Valid values are:
 
@@ -279,7 +279,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
 
@@ -304,7 +304,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Import-JournalRuleCollection.md b/exchange/exchange-ps/ExchangePowerShell/Import-JournalRuleCollection.md
index 66936d5797..103cbbca56 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Import-JournalRuleCollection.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Import-JournalRuleCollection.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailControl-Help.xml
 Locale: en-US
@@ -51,7 +51,7 @@ This example imports journal rules from the XML file named ExportedJournalRules.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the name of a journal rule to be imported.
 
@@ -69,7 +69,7 @@ Accept wildcard characters: False
 
 ### -FileData
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The FileData parameter specifies the XML file that contains the exported journal rule collection from the Export-JournalRuleCollection cmdlet.
 
@@ -89,7 +89,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -110,7 +110,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -128,7 +128,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Import-RecipientDataProperty.md b/exchange/exchange-ps/ExchangePowerShell/Import-RecipientDataProperty.md
index 772de76e50..abff75dbab 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Import-RecipientDataProperty.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Import-RecipientDataProperty.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -64,7 +64,7 @@ This example imports the picture file for Ayla Kol.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the mailbox or contact that you're adding the picture or spoken name file to. You can use any value that uniquely identifies the user. For example:
 
@@ -87,7 +87,7 @@ Accept wildcard characters: False
 
 ### -FileData
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The FileData parameter specifies the picture or spoken name file that you want to import.
 
@@ -111,7 +111,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -132,7 +132,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -152,7 +152,7 @@ Accept wildcard characters: False
 
 ### -Picture
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Picture switch specifies that you're importing the user's picture file. You don't need to specify a value with this switch.
 
@@ -172,7 +172,7 @@ Accept wildcard characters: False
 
 ### -SpokenName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SpokenName switch specifies that you're importing the user's spoken name file. You don't need to specify a value with this switch.
 
@@ -192,7 +192,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Import-TransportRuleCollection.md b/exchange/exchange-ps/ExchangePowerShell/Import-TransportRuleCollection.md
index cb5499437f..8da3bcf345 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Import-TransportRuleCollection.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Import-TransportRuleCollection.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -52,7 +52,7 @@ This example imports a transport rule collection from the XML file named Exporte
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter is functional only in Exchange Server 2010.
 
@@ -76,7 +76,7 @@ Accept wildcard characters: False
 
 ### -FileData
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The FileData parameter specifies the XML file that contains the exported transport rule collection from the Export-TransportRuleCollection cmdlet.
 
@@ -96,7 +96,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -117,7 +117,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -139,7 +139,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -159,7 +159,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Install-TransportAgent.md b/exchange/exchange-ps/ExchangePowerShell/Install-TransportAgent.md
index b05098dde5..cabaefff7e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Install-TransportAgent.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Install-TransportAgent.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -48,7 +48,7 @@ This example shows how a fictitious application named Test App is installed in t
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Name parameter specifies the display name of the transport agent to be installed. The length of the name can't exceed 64 characters.
 
@@ -66,7 +66,7 @@ Accept wildcard characters: False
 
 ### -AssemblyPath
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AssemblyPath parameter specifies the location of the transport agent Microsoft.NET assembly. Universal Naming Convention (UNC) file paths can't be used.
 
@@ -84,7 +84,7 @@ Accept wildcard characters: False
 
 ### -TransportAgentFactory
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TransportAgentFactory parameter specifies the Microsoft.NET class type of the transport agent factory. The developer of the transport agent being installed provides the transport agent factory and related information. For more information, see the documentation provided by the developer of the transport agent.
 
@@ -102,7 +102,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -123,7 +123,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -143,7 +143,7 @@ Accept wildcard characters: False
 
 ### -TransportService
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TransportService parameter specifies the transport service that you want to view or modify. Valid values for this parameter are:
 
@@ -167,7 +167,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Invoke-ComplianceSearchActionStep.md b/exchange/exchange-ps/ExchangePowerShell/Invoke-ComplianceSearchActionStep.md
index 815fd65f2d..e32f56a522 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Invoke-ComplianceSearchActionStep.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Invoke-ComplianceSearchActionStep.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance
+applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance
 author: chrisda
 external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
 Locale: en-US
@@ -42,7 +42,7 @@ This cmdlet is reserved for internal Microsoft use.
 
 ### -Identity
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance
 
 This cmdlet is reserved for internal Microsoft use.
 
@@ -60,7 +60,7 @@ Accept wildcard characters: False
 
 ### -Parameters
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance
 
 This cmdlet is reserved for internal Microsoft use.
 
@@ -78,7 +78,7 @@ Accept wildcard characters: False
 
 ### -Step
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance
 
 This cmdlet is reserved for internal Microsoft use.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Invoke-MonitoringProbe.md b/exchange/exchange-ps/ExchangePowerShell/Invoke-MonitoringProbe.md
index 62068c483c..62251f7198 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Invoke-MonitoringProbe.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Invoke-MonitoringProbe.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -53,7 +53,7 @@ This example creates an Exchange ActiveSync monitoring probe on the EX1 server.
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the identity of the monitoring probe to run.
 
@@ -71,7 +71,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
 
@@ -96,7 +96,7 @@ Accept wildcard characters: False
 
 ### -Account
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Account parameter specifies the identity of the mailbox or user account that's used to run the monitoring probe.
 
@@ -114,7 +114,7 @@ Accept wildcard characters: False
 
 ### -Endpoint
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Endpoint parameter specifies the name of the monitoring probe endpoint to connect to, for example, contoso.mail.com.
 
@@ -132,7 +132,7 @@ Accept wildcard characters: False
 
 ### -ItemTargetExtension
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ItemTargetExtension parameter specifies cmdlet extension data that you can pass to the monitoring probe. The probe that runs on the server might require specific data for its execution. This data is presented to the probe on execution in an XML format.
 
@@ -150,7 +150,7 @@ Accept wildcard characters: False
 
 ### -Password
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Password parameter specifies the password of the mailbox or user account that's used to run the monitoring probe.
 
@@ -168,7 +168,7 @@ Accept wildcard characters: False
 
 ### -PropertyOverride
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PropertyOverride parameter specifies a property that you want to override, for example, to set the time-out value to be extended beyond the default value.
 
@@ -186,7 +186,7 @@ Accept wildcard characters: False
 
 ### -SecondaryAccount
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SecondaryAccount parameter specifies the identity of the delegate mailbox or user account that's used to run the monitoring probe.
 
@@ -204,7 +204,7 @@ Accept wildcard characters: False
 
 ### -SecondaryEndpoint
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SecondaryEndpoint parameter specifies the name of the secondary monitoring probe endpoint to connect to, for example, contoso.mail.fabrikam.com.
 
@@ -222,7 +222,7 @@ Accept wildcard characters: False
 
 ### -SecondaryPassword
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SecondaryPassword parameter specifies the password of the delegate mailbox or user account that's used to run the monitoring probe.
 
@@ -240,7 +240,7 @@ Accept wildcard characters: False
 
 ### -TimeOutSeconds
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TimeOutSeconds parameter specifies the monitoring operation time-out period.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Mount-Database.md b/exchange/exchange-ps/ExchangePowerShell/Mount-Database.md
index 041d064d31..ab7bc9a6e9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Mount-Database.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Mount-Database.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -48,7 +48,7 @@ This example mounts the database MyDatabase.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies mailbox database that you want to mount. You can use any value that uniquely identifies the database. For example:
 
@@ -70,7 +70,7 @@ Accept wildcard characters: False
 
 ### -AcceptDataLoss
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AcceptDataLoss switch specifies that you accept the data loss caused by missing committed transaction log files without asking for confirmation. You don't need to specify a value with this switch.
 
@@ -88,7 +88,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -109,7 +109,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -127,7 +127,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -147,7 +147,7 @@ Accept wildcard characters: False
 
 ### -NewCapacity
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The NewCapacity switch specifies that you want to trigger the forced creation of a database only if all copies of the database don't have an .edb file. You don't need to specify a value with this switch.
 
@@ -165,7 +165,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Move-ActiveMailboxDatabase.md b/exchange/exchange-ps/ExchangePowerShell/Move-ActiveMailboxDatabase.md
index 34ab7820b4..f5020e52c7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Move-ActiveMailboxDatabase.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Move-ActiveMailboxDatabase.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -136,7 +136,7 @@ This example performs a server switchover for the Mailbox server MBX1. All activ
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the mailbox database that you want to activate. You can use any value that uniquely identifies the database. For example:
 
@@ -160,7 +160,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the server that you want to move all active mailbox databases from. You can use any value that uniquely identifies the server. For example:
 
@@ -185,7 +185,7 @@ Accept wildcard characters: False
 
 ### -ActivatePreferredOnServer
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ActivatePreferredOnServer parameter specifies the Mailbox server where you want to activate all mailbox databases that have copies with an ActivationPreference value of 1. You can use any value that uniquely identifies the server. For example:
 
@@ -210,7 +210,7 @@ Accept wildcard characters: False
 
 ### -ActivateOnServer
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ActivateOnServer parameter specifies the name of the Mailbox server on which the mailbox database copy should be activated.
 
@@ -228,7 +228,7 @@ Accept wildcard characters: False
 
 ### -SkipAllChecks
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SkipAllChecks switch specifies whether to skip all checks. You don't need to specify a value with this switch.
 
@@ -250,7 +250,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -271,7 +271,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -289,7 +289,7 @@ Accept wildcard characters: False
 
 ### -MountDialOverride
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MountDialOverride parameter is used to override the auto database mount dial (AutoDatabaseMountDial) setting for the target server and specify an alternate setting. Valid value are:
 
@@ -313,7 +313,7 @@ Accept wildcard characters: False
 
 ### -MoveAllDatabasesOrNone
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MoveAllDatabasesOrNone switch specifies whether to prevent any databases from moving if a single active database on the server can't be moved. You don't need to specify a value with this switch.
 
@@ -331,7 +331,7 @@ Accept wildcard characters: False
 
 ### -MoveComment
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MoveComment parameter specifies an optional administrative reason for the move operation. The comment is recorded in the Event log.
 
@@ -349,7 +349,7 @@ Accept wildcard characters: False
 
 ### -SkipActiveCopyChecks
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SkipActiveCopyChecks switch specifies whether to skip checking the current active copy to see if it's currently a seeding source for any passive databases. You don't need to specify a value with this switch.
 
@@ -369,7 +369,7 @@ Accept wildcard characters: False
 
 ### -SkipClientExperienceChecks
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SkipClientExperienceChecks switch specifies whether to skip the search catalog (content index) state check to see if the search catalog is healthy and up to date. You don't need to specify a value with this switch.
 
@@ -389,7 +389,7 @@ Accept wildcard characters: False
 
 ### -SkipCpuChecks
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SkipCpuChecks switch specifies whether to skip the high CPU utilization checks. You don't need to specify a value with this switch.
 
@@ -407,7 +407,7 @@ Accept wildcard characters: False
 
 ### -SkipHealthChecks
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SkipHealthChecks switch specifies whether to bypass passive copy health checks. You don't need to specify a value with this switch.
 
@@ -427,7 +427,7 @@ Accept wildcard characters: False
 
 ### -SkipLagChecks
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SkipLagChecks switch specifies whether to allow a copy to be activated that has replay and copy queues outside of the configured criteria. You don't need to specify a value with this switch.
 
@@ -445,7 +445,7 @@ Accept wildcard characters: False
 
 ### -SkipMaximumActiveDatabasesChecks
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SkipMaximumActiveDatabasesChecks switch specifies whether to skip checking the value of MaximumPreferredActiveDatabases during the best copy and server selection (BCSS) process. You don't need to specify a value with this switch.
 
@@ -465,7 +465,7 @@ Accept wildcard characters: False
 
 ### -SkipMoveSuppressionChecks
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SkipMoveSuppressionChecks switch specifies whether to skip the move suppression checks. You don't need to specify a value with this switch.
 
@@ -483,7 +483,7 @@ Accept wildcard characters: False
 
 ### -TerminateOnWarning
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TerminateOnWarning switch specifies whether to terminate the task and output an error message if a warning is encountered during the switchover operation. You don't need to specify a value with this switch.
 
@@ -501,7 +501,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Move-AddressList.md b/exchange/exchange-ps/ExchangePowerShell/Move-AddressList.md
index fa8ea18b19..9892cff13c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Move-AddressList.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Move-AddressList.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -45,7 +45,7 @@ This example moves the address list with GUID c3fffd8e-026b-41b9-88c4-8c21697ac8
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the address list that you want to move. You can use any value that uniquely identifies the address list. For example:
 
@@ -68,7 +68,7 @@ Accept wildcard characters: False
 
 ### -Target
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Container parameter specifies where to move the address list. Valid input for this parameter is under the root "\\" (also known as All Address Lists) or under an existing address list. You can use any value that uniquely identifies the address list. For example:
 
@@ -91,7 +91,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -114,7 +114,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -132,7 +132,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Move-DatabasePath.md b/exchange/exchange-ps/ExchangePowerShell/Move-DatabasePath.md
index 529019505c..bd0bd4b690 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Move-DatabasePath.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Move-DatabasePath.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -56,7 +56,7 @@ This example sets a new path for the mailbox database specified by the mailbox d
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the database that you want to move. You can use any value that uniquely identifies the database. For example:
 
@@ -78,7 +78,7 @@ Accept wildcard characters: False
 
 ### -ConfigurationOnly
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ConfigurationOnly switch specifies whether to change the configuration of the database without moving any files. You don't need to specify a value with this switch.
 
@@ -98,7 +98,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -121,7 +121,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -139,7 +139,7 @@ Accept wildcard characters: False
 
 ### -EDBFilePath
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The EdbFilePath parameter specifies a new file path for the database. All current database files are moved to this location. The default location is `%ExchangeInstallPath%Mailbox\LocalCopies\MBDatabase.edb`. This file path can't be the same as the path for the backup copy of the database.
 
@@ -157,7 +157,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -177,7 +177,7 @@ Accept wildcard characters: False
 
 ### -LogFolderPath
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The LogFolderPath parameter specifies the folder where log files are stored.
 
@@ -195,7 +195,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
@@ -213,7 +213,7 @@ Accept wildcard characters: False
 
 ### -EDBFilePath
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The EdbFilePath parameter specifies a new file path for the database. All current database files are moved to this location. The default location is ``%ExchangeInstallPath%Mailbox\LocalCopies\MBDatabase.edb`. This file path can't be the same as the path for the backup copy of the database.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Move-OfflineAddressBook.md b/exchange/exchange-ps/ExchangePowerShell/Move-OfflineAddressBook.md
index a9ca973abe..68e4449b9b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Move-OfflineAddressBook.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Move-OfflineAddressBook.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -46,7 +46,7 @@ This example moves OAB generation in Exchange 2010 to the server named Server1.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the GUID, distinguished name (DN), or OAB name that represents a specific OAB. You can also include the path by using the format Server\\OfflineAddressBookName.
 
@@ -66,7 +66,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -89,7 +89,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -107,7 +107,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
 
@@ -132,7 +132,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AcceptedDomain.md b/exchange/exchange-ps/ExchangePowerShell/New-AcceptedDomain.md
index bd520684c0..06426431a7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-AcceptedDomain.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-AcceptedDomain.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -46,7 +46,7 @@ This example creates the new authoritative accepted domain Contoso.
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Name parameter specifies a unique name for the accepted domain object.
 
@@ -64,7 +64,7 @@ Accept wildcard characters: False
 
 ### -DomainName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainName parameter specifies the SMTP domain that you want to establish as an accepted domain. Valid input for the DomainName parameter is an SMTP domain. You can use a wildcard character to specify all subdomains of a specified domain, as shown in the following example: \*.contoso.com.
 
@@ -84,7 +84,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -105,7 +105,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -125,7 +125,7 @@ Accept wildcard characters: False
 
 ### -DomainType
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainType parameter specifies the type of accepted domain that you want to configure. Valid values are Authoritative, InternalRelay or ExternalRelay. You must set at least one value.
 
@@ -147,7 +147,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ActiveSyncDeviceAccessRule.md b/exchange/exchange-ps/ExchangePowerShell/New-ActiveSyncDeviceAccessRule.md
index 831cfa333c..f8372ace21 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-ActiveSyncDeviceAccessRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-ActiveSyncDeviceAccessRule.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
 Locale: en-US
@@ -54,7 +54,7 @@ This example creates a device access rule that uses the UserAgent characteristic
 
 ### -AccessLevel
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AccessLevel parameter specifies the access level of devices that are defined by the rule. Valid values for this parameter are Allow, Block and Quarantine.
 
@@ -72,7 +72,7 @@ Accept wildcard characters: False
 
 ### -Characteristic
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Characteristic parameter specifies the device characteristic or category that's used by the rule. Valid values for this parameter are:
 
@@ -96,7 +96,7 @@ Accept wildcard characters: False
 
 ### -QueryString
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The QueryString parameter specifies the device identifier that's used by the rule. This parameter uses a text value that's used with Characteristic parameter value to define the device. Wildcards or partial matches aren't allowed.
 
@@ -116,7 +116,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -137,7 +137,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -157,7 +157,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ActiveSyncMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-ActiveSyncMailboxPolicy.md
index 2b7ff6ccd4..139dad571a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-ActiveSyncMailboxPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-ActiveSyncMailboxPolicy.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
 Locale: en-US
@@ -118,7 +118,7 @@ This example creates the Mobile Device mailbox policy Contoso that has several p
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Name parameter specifies the name of the policy.
 
@@ -156,7 +156,7 @@ Accept wildcard characters: False
 
 ### -AllowBluetooth
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowBluetooth parameter specifies whether the Bluetooth capabilities of the mobile phone are allowed. The available options are Disable, HandsfreeOnly, and Allow. The default value is Allow.
 
@@ -174,7 +174,7 @@ Accept wildcard characters: False
 
 ### -AllowBrowser
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowBrowser parameter specifies whether Microsoft Pocket Internet Explorer is allowed on the mobile phone. The default value is $true. This parameter doesn't affect non-Microsoft browsers.
 
@@ -192,7 +192,7 @@ Accept wildcard characters: False
 
 ### -AllowCamera
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowCamera parameter specifies whether the mobile phone's camera is allowed. The default value is $true.
 
@@ -210,7 +210,7 @@ Accept wildcard characters: False
 
 ### -AllowConsumerEmail
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowConsumerEmail parameter specifies whether the mobile phone user can configure a personal email account on the device. The default value is $true.
 
@@ -228,7 +228,7 @@ Accept wildcard characters: False
 
 ### -AllowDesktopSync
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowDesktopSync parameter specifies whether the mobile phone can synchronize with a desktop computer through a cable. The default value is $true.
 
@@ -246,7 +246,7 @@ Accept wildcard characters: False
 
 ### -AllowExternalDeviceManagement
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowExternalDeviceManagement parameter specifies whether an external device management program is allowed to manage the device.
 
@@ -264,7 +264,7 @@ Accept wildcard characters: False
 
 ### -AllowHTMLEmail
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowHTMLEmail parameter specifies whether HTML email is enabled on the device. The default value is $true.
 
@@ -282,7 +282,7 @@ Accept wildcard characters: False
 
 ### -AllowInternetSharing
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowInternetSharing parameter specifies whether the mobile phone can be used as a modem to connect a computer to the Internet. The default value is $true.
 
@@ -300,7 +300,7 @@ Accept wildcard characters: False
 
 ### -AllowIrDA
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowIrDA parameter specifies whether infrared connections are allowed to the mobile phone. The default value is $true.
 
@@ -318,7 +318,7 @@ Accept wildcard characters: False
 
 ### -AllowMobileOTAUpdate
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowMobileOTAUpdate parameter specifies whether certain updates are seen by devices that implemented support for this restricting functionality. Further control can be specified via the MobileOTAUpdateMode parameter.
 
@@ -336,7 +336,7 @@ Accept wildcard characters: False
 
 ### -AllowNonProvisionableDevices
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 When set to $true, the AllowNonProvisionableDevices parameter enables all devices to synchronize with the computer running Exchange, regardless of whether the device can enforce all the specific settings established in the Mobile Device mailbox policy. This also includes devices managed by a separate device management system. When set to $false, this parameter blocks these devices that aren't provisioned from synchronizing with the server running Exchange. The default value is $false.
 
@@ -354,7 +354,7 @@ Accept wildcard characters: False
 
 ### -AllowPOPIMAPEmail
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowPOPIMAPEmail parameter specifies whether the user can configure a POP3 or IMAP4 email account on the device. The default value is $true.
 
@@ -372,7 +372,7 @@ Accept wildcard characters: False
 
 ### -AllowRemoteDesktop
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowRemoteDesktop parameter specifies whether the mobile phone can initiate a remote desktop connection. The default value is $true.
 
@@ -390,7 +390,7 @@ Accept wildcard characters: False
 
 ### -AllowSimpleDevicePassword
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowSimpleDevicePassword parameter specifies whether a simple device password is allowed. A simple device password is a password that has a specific pattern, such as 1111 or 1234. The default value is $true.
 
@@ -408,7 +408,7 @@ Accept wildcard characters: False
 
 ### -AllowSMIMEEncryptionAlgorithmNegotiation
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowSMIMEEncryptionAlgorithmNegotiation parameter specifies whether the messaging application on the device can negotiate the encryption algorithm in case a recipient's certificate doesn't support the specified encryption algorithm.
 
@@ -426,7 +426,7 @@ Accept wildcard characters: False
 
 ### -AllowSMIMESoftCerts
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowSMIMESoftCerts parameter specifies whether S/MIME software certificates are allowed. The default value is $true.
 
@@ -444,7 +444,7 @@ Accept wildcard characters: False
 
 ### -AllowStorageCard
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowStorageCard parameter specifies whether the device can access information stored on a storage card. The default value is $true.
 
@@ -462,7 +462,7 @@ Accept wildcard characters: False
 
 ### -AllowTextMessaging
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowTextMessaging parameter specifies whether text messaging is allowed from the device. The default value is $true.
 
@@ -480,7 +480,7 @@ Accept wildcard characters: False
 
 ### -AllowUnsignedApplications
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowUnsignedApplications parameter specifies whether unsigned applications can be installed on the device. The default value is $true.
 
@@ -498,7 +498,7 @@ Accept wildcard characters: False
 
 ### -AllowUnsignedInstallationPackages
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowUnsignedInstallationPackages parameter specifies whether unsigned installation packages can be run on the device. The default value is $true.
 
@@ -516,7 +516,7 @@ Accept wildcard characters: False
 
 ### -AllowWiFi
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowWiFi parameter specifies whether wireless Internet access is allowed on the device. The default value is $true.
 
@@ -534,7 +534,7 @@ Accept wildcard characters: False
 
 ### -AlphanumericDevicePasswordRequired
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AlphanumericDevicePasswordRequired parameter specifies whether the device password must be alphanumeric. The default value is $false.
 
@@ -552,7 +552,7 @@ Accept wildcard characters: False
 
 ### -ApprovedApplicationList
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ApprovedApplicationList parameter specifies a list of approved applications for the device.
 
@@ -570,7 +570,7 @@ Accept wildcard characters: False
 
 ### -AttachmentsEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AttachmentsEnabled parameter specifies whether the user can download attachments. When set to $false, the user is blocked from downloading attachments. The default value is $true.
 
@@ -588,7 +588,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -609,7 +609,7 @@ Accept wildcard characters: False
 
 ### -DeviceEncryptionEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DeviceEncryptionEnabled parameter, when set to $true, enables device encryption on the mobile phone. The default value is $false. Currently, only the storage card can be encrypted on devices running Windows Mobile 6.0 or later. We recommend that you don't use this setting and use the RequireStorageCardEncryption parameter instead.
 
@@ -627,7 +627,7 @@ Accept wildcard characters: False
 
 ### -DevicePasswordEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 When set to $true, the DevicePasswordEnabled parameter specifies that the user set a password for the device. The default value is $false.
 
@@ -645,7 +645,7 @@ Accept wildcard characters: False
 
 ### -DevicePasswordExpiration
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DevicePasswordExpiration parameter specifies the length of time, in days, that a password can be used. After this length of time, a new password must be created. The format of the parameter is dd.hh.mm:ss, for example, 24.00:00 = 24 hours.
 
@@ -663,7 +663,7 @@ Accept wildcard characters: False
 
 ### -DevicePasswordHistory
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DevicePasswordHistory parameter specifies the number of previously used passwords to store. When a user creates a password, the user can't reuse a stored password that was previously used.
 
@@ -681,7 +681,7 @@ Accept wildcard characters: False
 
 ### -DevicePolicyRefreshInterval
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DevicePolicyRefreshInterval parameter specifies how often the policy is sent from the server to the mobile phone
 
@@ -699,7 +699,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -719,7 +719,7 @@ Accept wildcard characters: False
 
 ### -IrmEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IrmEnabled parameter specifies whether Information Rights Management (IRM) is enabled for the mailbox policy.
 
@@ -737,7 +737,7 @@ Accept wildcard characters: False
 
 ### -IsDefault
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IsDefault parameter specifies whether this policy is the default Mobile Device mailbox policy. The default value is $false. If another policy is currently set as the default, setting this parameter replaces the old default policy with this policy.
 
@@ -755,7 +755,7 @@ Accept wildcard characters: False
 
 ### -IsDefaultPolicy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IsDefault parameter specifies whether this policy is the default Mobile Device mailbox policy. The default value is $false. If another policy is currently set as the default, setting this parameter replaces the old default policy with this policy.
 
@@ -773,7 +773,7 @@ Accept wildcard characters: False
 
 ### -MaxAttachmentSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MaxAttachmentSize parameter specifies the maximum size of attachments that can be downloaded to the mobile phone. The default value is Unlimited.
 
@@ -791,7 +791,7 @@ Accept wildcard characters: False
 
 ### -MaxCalendarAgeFilter
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MaxCalendarAgeFilter parameter specifies the maximum range of calendar days that can be synchronized to the device. Valid values are:
 
@@ -815,7 +815,7 @@ Accept wildcard characters: False
 
 ### -MaxDevicePasswordFailedAttempts
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MaxDevicePasswordFailedAttempts parameter specifies the number of attempts a user can make to enter the correct password for the device. You can enter any number from 4 through 16. The default value is 8.
 
@@ -833,7 +833,7 @@ Accept wildcard characters: False
 
 ### -MaxEmailAgeFilter
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MaxEmailAgeFilter parameter specifies the maximum number of days of email items to synchronize to the device.
 
@@ -862,7 +862,7 @@ Accept wildcard characters: False
 
 ### -MaxEmailBodyTruncationSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MaxEmailBodyTruncationSize parameter specifies the maximum size at which email messages are truncated when synchronized to the device. The value is specified in kilobytes (KB).
 
@@ -880,7 +880,7 @@ Accept wildcard characters: False
 
 ### -MaxEmailHTMLBodyTruncationSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MaxEmailHTMLBodyTruncationSize parameter specifies the maximum size at which HTML-formatted email messages are synchronized to the device. The value is specified in KB.
 
@@ -898,7 +898,7 @@ Accept wildcard characters: False
 
 ### -MaxInactivityTimeDeviceLock
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MaxInactivityTimeDeviceLock parameter specifies the length of time that the device can be inactive before the password is required to reactivate the device. You can enter any interval between 30 seconds and 1 hour. The default value is 15 minutes. The format of the parameter is hh.mm:ss, for example, 15:00 = 15 minutes.
 
@@ -916,7 +916,7 @@ Accept wildcard characters: False
 
 ### -MinDevicePasswordComplexCharacters
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MinDevicePasswordComplexCharacters parameter specifies the minimum number of complex characters required in a device password. A complex character isn't a letter.
 
@@ -934,7 +934,7 @@ Accept wildcard characters: False
 
 ### -MinDevicePasswordLength
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MinDevicePasswordLength parameter specifies the minimum number of characters in the device password. You can enter any number from 1 through 16. The maximum length a password can be is 16 characters. The default value is 4.
 
@@ -952,7 +952,7 @@ Accept wildcard characters: False
 
 ### -PasswordRecoveryEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The PasswordRecoveryEnabled parameter specifies whether you can store the recovery password for the device on an Exchange server. When set to $true, you can store the recovery password for the device on an Exchange server. The default value is $false. The recovery password can be viewed from either Outlook on the web or the Exchange admin center.
 
@@ -970,7 +970,7 @@ Accept wildcard characters: False
 
 ### -RequireDeviceEncryption
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RequireDeviceEncryption parameter specifies whether encryption is required on the device. The default value is $false.
 
@@ -988,7 +988,7 @@ Accept wildcard characters: False
 
 ### -RequireEncryptedSMIMEMessages
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RequireEncryptedSMIMEMessages parameter specifies whether you must encrypt S/MIME messages. The default value is $false.
 
@@ -1006,7 +1006,7 @@ Accept wildcard characters: False
 
 ### -RequireEncryptionSMIMEAlgorithm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RequireEncryptionSMIMEAlgorithm parameter specifies what required algorithm must be used when encrypting a message.
 
@@ -1024,7 +1024,7 @@ Accept wildcard characters: False
 
 ### -RequireManualSyncWhenRoaming
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RequireManualSyncWhenRoaming parameter specifies whether the device must synchronize manually while roaming. The default value is $false.
 
@@ -1042,7 +1042,7 @@ Accept wildcard characters: False
 
 ### -RequireSignedSMIMEAlgorithm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RequireSignedSMIMEAlgorithm parameter specifies what required algorithm must be used when signing a message.
 
@@ -1060,7 +1060,7 @@ Accept wildcard characters: False
 
 ### -RequireSignedSMIMEMessages
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RequireSignedSMIMEMessages parameter specifies whether the device must send signed S/MIME messages.
 
@@ -1078,7 +1078,7 @@ Accept wildcard characters: False
 
 ### -RequireStorageCardEncryption
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RequireStorageCardEncryption parameter specifies whether encryption of a storage card is required. The default value is $true.
 
@@ -1096,7 +1096,7 @@ Accept wildcard characters: False
 
 ### -UnapprovedInROMApplicationList
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The UnapprovedInROMApplicationList parameter specifies a list of applications that can't be run in ROM.
 
@@ -1114,7 +1114,7 @@ Accept wildcard characters: False
 
 ### -UNCAccessEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The UNCAccessEnabled parameter specifies whether access to Microsoft Windows file shares is enabled. Access to specific shares is configured on the Microsoft Exchange ActiveSync virtual directory.
 
@@ -1132,7 +1132,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
@@ -1150,7 +1150,7 @@ Accept wildcard characters: False
 
 ### -WSSAccessEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WSSAccessEnabled parameter specifies whether access to Microsoft Windows SharePoint Services is enabled. Access to specific shares is configured on the Exchange ActiveSync virtual directory.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ActiveSyncVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/New-ActiveSyncVirtualDirectory.md
index ff2968558b..57c9747043 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-ActiveSyncVirtualDirectory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-ActiveSyncVirtualDirectory.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
 Locale: en-US
@@ -74,7 +74,7 @@ This example creates an Exchange ActiveSync virtual directory for the company Fo
 
 ### -ApplicationRoot
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ApplicationRoot parameter specifies the metabase path of the virtual directory. By default, this path is the same as the website in which the virtual directory is created.
 
@@ -92,7 +92,7 @@ Accept wildcard characters: False
 
 ### -AppPoolId
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AppPoolId parameter specifies the IIS application pool in which the virtual directory runs. We recommend that you leave this parameter at its default setting.
 
@@ -110,7 +110,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -131,7 +131,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -149,7 +149,7 @@ Accept wildcard characters: False
 
 ### -ExtendedProtectionFlags
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExtendedProtectionFlags parameter specifies custom settings for Extended Protection for Authentication on the virtual directory. Valid values are:
 
@@ -173,7 +173,7 @@ Accept wildcard characters: False
 
 ### -ExtendedProtectionSPNList
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExtendedProtectionSPNList parameter specifies a list of valid Service Principal Names (SPNs) if you're using Extended Protection for Authentication on the virtual directory. Valid values are:
 
@@ -194,7 +194,7 @@ Accept wildcard characters: False
 
 ### -ExtendedProtectionTokenChecking
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExtendedProtectionTokenChecking parameter defines how you want to use Extended Protection for Authentication on the virtual directory. Extended Protection for Authentication isn't enabled by default. Valid values are:
 
@@ -218,7 +218,7 @@ Accept wildcard characters: False
 
 ### -ExternalAuthenticationMethods
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExternalAuthenticationMethods parameter restricts the authentication methods that can be used to connect to the virtual directory from outside the firewall. Valid values are:
 
@@ -261,7 +261,7 @@ Accept wildcard characters: False
 
 ### -ExternalUrl
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExternalURL parameter specifies the URL that's used to connect to the virtual directory from outside the firewall.
 
@@ -279,7 +279,7 @@ Accept wildcard characters: False
 
 ### -InstallProxySubDirectory
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The InstallProxySubDirectory parameter was used to create an subdirectory that was required for proxying ActiveSync connections with Exchange 2007.
 
@@ -297,7 +297,7 @@ Accept wildcard characters: False
 
 ### -InternalAuthenticationMethods
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The InternalAuthenticationMethods parameter restricts the authentication methods that can be used to connect to the virtual directory from inside the firewall. Valid values are:
 
@@ -340,7 +340,7 @@ Accept wildcard characters: False
 
 ### -InternalUrl
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The InternalURL parameter specifies the URL that's used to connect to the virtual directory from inside the firewall.
 
@@ -358,7 +358,7 @@ Accept wildcard characters: False
 
 ### -Path
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Path parameter specifies the file system path of the virtual directory. We recommend using this parameter only when you need to use a custom location for the virtual directory files. The default value is blank ($null), which indicates the default location is used.
 
@@ -376,7 +376,7 @@ Accept wildcard characters: False
 
 ### -Role
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Role parameter species the configuration for the virtual directory. Valid values are:
 
@@ -399,7 +399,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Exchange server that hosts the virtual directory. You can use any value that uniquely identifies the server. For example:
 
@@ -422,7 +422,7 @@ Accept wildcard characters: False
 
 ### -WebSiteName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WebSiteName parameter specifies the name of the IIS website under which the virtual directory is created. You don't need to use this parameter to create the virtual directory under the default website.
 
@@ -440,7 +440,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AddressBookPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-AddressBookPolicy.md
index 36f586f9a4..f9491f7295 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-AddressBookPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-AddressBookPolicy.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -53,7 +53,7 @@ This example creates an address book policy with the following settings:
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Name parameter specifies the name of the address book policy.
 
@@ -71,7 +71,7 @@ Accept wildcard characters: False
 
 ### -AddressLists
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AddressLists parameter specifies the address lists for mailbox users who are assigned this address book policy. You can use any value that uniquely identifies the address list. For example:
 
@@ -97,7 +97,7 @@ Accept wildcard characters: False
 
 ### -GlobalAddressList
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The GlobalAddressList parameter specifies the GAL for mailbox users who are assigned this address book policy. You can use any value that uniquely identifies the GAL. For example:
 
@@ -123,7 +123,7 @@ Accept wildcard characters: False
 
 ### -OfflineAddressBook
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The OfflineAddressBook parameter specifies the OAB for mailbox users who are assigned this address book policy. You can use any value that uniquely identifies the OAB. For example:
 
@@ -149,7 +149,7 @@ Accept wildcard characters: False
 
 ### -RoomList
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RoomList parameter specifies an address list that used for location experiences for mailbox users who have this address book policy assigned to them.
 
@@ -179,7 +179,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -200,7 +200,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -220,7 +220,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AddressList.md b/exchange/exchange-ps/ExchangePowerShell/New-AddressList.md
index 8c147fdbe2..a87dfe3fdd 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-AddressList.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-AddressList.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -103,7 +103,7 @@ This example creates the address list AL\_AgencyB that includes mailboxes that h
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Name parameter specifies the unique name for the new address list. The maximum length is 64 characters, and it can't include a carriage return or a backslash (\\). If the value contains spaces, enclose the value in quotation marks (").
 
@@ -121,7 +121,7 @@ Accept wildcard characters: False
 
 ### -IncludedRecipients
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IncludedRecipients parameter specifies a precanned filter that's based on the recipient type. Valid values are:
 
@@ -150,7 +150,7 @@ Accept wildcard characters: False
 
 ### -RecipientFilter
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RecipientFilter parameter specifies a custom OPATH filter that's based on the value of any available recipient property. You can use any available Windows PowerShell operator, and wildcards and partial matches are supported. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`.
 
@@ -179,7 +179,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCompany
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalCompany parameter specifies a precanned filter that's based on the value of the recipient's Company property. You can specify multiple values separated by commas.
 
@@ -201,7 +201,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute1
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalCustomAttribute1 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute1 property. You can specify multiple values separated by commas.
 
@@ -223,7 +223,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute10
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalCustomAttribute10 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute10 property. You can specify multiple values separated by commas.
 
@@ -245,7 +245,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute11
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalCustomAttribute11 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute11 property. You can specify multiple values separated by commas.
 
@@ -267,7 +267,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute12
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalCustomAttribute12 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute12 property. You can specify multiple values separated by commas.
 
@@ -289,7 +289,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute13
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalCustomAttribute13 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute13 property. You can specify multiple values separated by commas.
 
@@ -311,7 +311,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute14
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalCustomAttribute14 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute14 property. You can specify multiple values separated by commas.
 
@@ -333,7 +333,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute15
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalCustomAttribute15 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute15 property. You can specify multiple values separated by commas.
 
@@ -355,7 +355,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute2
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalCustomAttribute2 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute2 property. You can specify multiple values separated by commas.
 
@@ -377,7 +377,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute3
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalCustomAttribute3 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute3 property. You can specify multiple values separated by commas.
 
@@ -399,7 +399,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute4
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalCustomAttribute4 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute4 property. You can specify multiple values separated by commas.
 
@@ -421,7 +421,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute5
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalCustomAttribute5 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute5 property. You can specify multiple values separated by commas.
 
@@ -443,7 +443,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute6
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalCustomAttribute6 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute6 property. You can specify multiple values separated by commas.
 
@@ -465,7 +465,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute7
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalCustomAttribute7 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute7 property. You can specify multiple values separated by commas.
 
@@ -487,7 +487,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute8
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalCustomAttribute8 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute8 property. You can specify multiple values separated by commas.
 
@@ -509,7 +509,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute9
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalCustomAttribute9 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute9 property. You can specify multiple values separated by commas.
 
@@ -531,7 +531,7 @@ Accept wildcard characters: False
 
 ### -ConditionalDepartment
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalDepartment parameter specifies a precanned filter that's based on the value of the recipient's Department property. You can specify multiple values separated by commas.
 
@@ -553,7 +553,7 @@ Accept wildcard characters: False
 
 ### -ConditionalStateOrProvince
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalStateOrProvince parameter specifies a precanned filter that's based on the value of the recipient's StateOrProvince property. You can specify multiple values separated by commas.
 
@@ -575,7 +575,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -596,7 +596,7 @@ Accept wildcard characters: False
 
 ### -Container
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Container parameter specifies where to create the address list. Valid input for this parameter is under the root "\\" (also known as All Address Lists) or under an existing address list. You can use any value that uniquely identifies the address list. For example:
 
@@ -621,7 +621,7 @@ Accept wildcard characters: False
 
 ### -DisplayName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DisplayName parameter specifies the display name of the address list. The display name is visible in the Exchange admin center and Outlook. The maximum length is 256 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -641,7 +641,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -661,7 +661,7 @@ Accept wildcard characters: False
 
 ### -RecipientContainer
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -688,7 +688,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AddressRewriteEntry.md b/exchange/exchange-ps/ExchangePowerShell/New-AddressRewriteEntry.md
index 0d8d06f58d..6512dfd601 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-AddressRewriteEntry.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-AddressRewriteEntry.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
 Locale: en-US
@@ -61,7 +61,7 @@ This example creates an address rewrite entry that rewrites all email addresses
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Name parameter specifies a unique name for this address rewrite entry.
 
@@ -79,7 +79,7 @@ Accept wildcard characters: False
 
 ### -ExternalAddress
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExternalAddress parameter specifies the final email addresses that you want. If the InternalAddress parameter specifies a single email address (chris@contoso.com), the ExternalAddress parameter must also specify a single email address (support@contoso.com). If the InternalAddress parameter specifies a single domain (contoso.com) or a domain and all subdomains (\*.contoso.com), the ExternalAddress parameter must specify a single domain (fabrikam.com).
 
@@ -99,7 +99,7 @@ Accept wildcard characters: False
 
 ### -InternalAddress
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The InternalAddress parameter specifies the original email addresses that you want to change. You can use the following values:
 
@@ -121,7 +121,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -142,7 +142,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -162,7 +162,7 @@ Accept wildcard characters: False
 
 ### -ExceptionList
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExceptionList parameter specifies the email address domains that shouldn't be rewritten when the InternalAddress parameter contains the wildcard character to rewrite addresses in a domain and all subdomains (\*.contoso.com). You can enter multiple domain values in the ExceptionList parameter separated by commas.
 
@@ -180,7 +180,7 @@ Accept wildcard characters: False
 
 ### -OutboundOnly
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The OutboundOnly parameter enables or disables outbound-only address rewriting. Valid input for this parameter is $true or $false. The value $true means address rewriting occurs in outbound mail only. The value $false means address rewriting occurs on outbound mail and also on inbound mail (rewritten email addresses are changed back to the original email addresses in inbound mail). The default value is $false.
 
@@ -202,7 +202,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AdminAuditLogSearch.md b/exchange/exchange-ps/ExchangePowerShell/New-AdminAuditLogSearch.md
index 18a80d3e96..19b0cf5723 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-AdminAuditLogSearch.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-AdminAuditLogSearch.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
 Locale: en-US
@@ -68,7 +68,7 @@ This example returns entries in the administrator audit log of an Exchange Onlin
 
 ### -EndDate
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The EndDate parameter specifies the end date of the date range.
 
@@ -87,7 +87,7 @@ Accept wildcard characters: False
 
 ### -StartDate
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The StartDate parameter specifies the start date of the date range.
 
@@ -106,7 +106,7 @@ Accept wildcard characters: False
 
 ### -StatusMailRecipients
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The StatusMailRecipients parameter specifies the recipients that should receive the administrator audit log report. The recipient must be a valid SMTP address.
 
@@ -125,7 +125,7 @@ Accept wildcard characters: False
 
 ### -Cmdlets
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The Cmdlets parameter specifies the cmdlets you want to search for in the administrator audit log. Only the log entries that contain the cmdlets you specify are returned.
 
@@ -144,7 +144,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -164,7 +164,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -184,7 +184,7 @@ Accept wildcard characters: False
 
 ### -ExternalAccess
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The ExternalAccess parameter returns only audit log entries for cmdlets that were run by a user outside of your organization. In Exchange Online, use this parameter to return audit log entries for cmdlets run by Microsoft datacenter administrators.
 
@@ -201,7 +201,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The Name parameter specifies the name of the administrator audit log search. The name is shown in the subject line of the audit log report email message.
 
@@ -220,7 +220,7 @@ Accept wildcard characters: False
 
 ### -ObjectIds
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The ObjectIds parameter specifies that only administrator audit log entries that contain the specified changed objects should be returned. This parameter accepts a variety of objects, such as mailboxes, aliases, Send connector names and so on.
 
@@ -239,7 +239,7 @@ Accept wildcard characters: False
 
 ### -Parameters
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The Parameters parameter specifies the parameters you want to search for in the administrator audit log. Only the log entries that contain the parameters you specify are returned. You can only use this parameter if you use the Cmdlets parameter.
 
@@ -258,7 +258,7 @@ Accept wildcard characters: False
 
 ### -UserIds
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The UserIds parameter specifies that only the administrator audit log entries that contain the specified ID of the user who ran the cmdlet should be returned.
 
@@ -277,7 +277,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The WhatIf switch doesn't work in Security & Compliance PowerShell.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-App.md b/exchange/exchange-ps/ExchangePowerShell/New-App.md
index 89e31054bb..30d95ae4f1 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-App.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-App.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.WebClient-Help.xml
 Locale: en-US
@@ -168,7 +168,7 @@ Accept wildcard characters: False
 
 ### -AllowReadWriteMailbox
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowReadWriteMailbox switch specifies whether the app allows read/write mailbox permission. You don't need to specify a value with this switch.
 
@@ -246,7 +246,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -267,7 +267,7 @@ Accept wildcard characters: False
 
 ### -DefaultStateForUser
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DefaultStateForUser parameter specifies the default initial state of an organization app. Valid values are:
 
@@ -291,7 +291,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -311,7 +311,7 @@ Accept wildcard characters: False
 
 ### -DownloadOnly
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The DownloadOnly switch specifies whether to get the app manifest file and prompt the user for confirmation before committing to actual installation. You don't need to specify a value with this switch.
 
@@ -331,7 +331,7 @@ Accept wildcard characters: False
 
 ### -Enabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Enabled parameter specifies whether the app is available to users in the organization. Valid values are:
 
@@ -354,7 +354,7 @@ Accept wildcard characters: False
 
 ### -Etoken
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter is reserved for internal Microsoft use.
 
@@ -372,7 +372,7 @@ Accept wildcard characters: False
 
 ### -FileData
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The FileData parameter specifies the location of the app manifest file. You need to specify only one source location for the app manifest file. You can specify the app manifest file by using the MarketplaceServicesUrl, Url, or FileData parameter.
 
@@ -392,7 +392,7 @@ Accept wildcard characters: False
 
 ### -FileStream
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The FileStream parameter is used only by the Exchange admin center to support the app file uploader. Don't use this parameter to specify the app manifest file. You can specify the app manifest file by using the MarketplaceServicesUrl, Url or FileData parameter.
 
@@ -430,7 +430,7 @@ Accept wildcard characters: False
 
 ### -Mailbox
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Mailbox parameter specifies the mailbox where you want to install the app. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -459,7 +459,7 @@ Accept wildcard characters: False
 
 ### -MarketplaceAssetID
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The MarketplaceAssetID parameter specifies the Office Store identifier for the app. You need to use this parameter if you use theMarketplaceServicesUrl parameter.
 
@@ -477,7 +477,7 @@ Accept wildcard characters: False
 
 ### -MarketplaceCorrelationID
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The MarketplaceCorrelationID parameter specifies the Office Store correlation identifier for the app.
 
@@ -495,7 +495,7 @@ Accept wildcard characters: False
 
 ### -MarketplaceQueryMarket
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The MarketplaceQueryMarket parameter specifies the locale that an app is filed under at the office marketplace. For example, an app for the United States market in English uses the value en-US. The default value is en-US.
 
@@ -513,7 +513,7 @@ Accept wildcard characters: False
 
 ### -MarketplaceServicesUrl
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The MarketplaceServicesUrl parameter specifies the full services URL for the app. You need to specify only one source location for the app manifest file. You can specify the app manifest file by using the MarketplaceServicesUrl, Url or FileData parameter.
 
@@ -531,7 +531,7 @@ Accept wildcard characters: False
 
 ### -MarketplaceUserProfileType
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The MarketplaceUserProfileType parameter specifies the user profile type for the Office Store.
 
@@ -549,7 +549,7 @@ Accept wildcard characters: False
 
 ### -OrganizationApp
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The OrganizationApp switch specifies that the scope of the app is organizational (not bound to a specific user). You don't need to specify a value with this switch.
 
@@ -567,7 +567,7 @@ Accept wildcard characters: False
 
 ### -PrivateCatalog
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The PrivateCatalog switch specifies whether the app is located in a private catalog. You don't need to specify a value with this switch.
 
@@ -585,7 +585,7 @@ Accept wildcard characters: False
 
 ### -ProvidedTo
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ProvidedTo parameter specifies the availability of the app in your organization. Valid values are:
 
@@ -628,7 +628,7 @@ Accept wildcard characters: False
 
 ### -Url
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Url parameter specifies the full URL location of the app manifest file that you want to install. You need to specify only one source location for the app manifest file. You can specify the app manifest file by using the MarketplaceServicesUrl, Url or FileData parameter.
 
@@ -648,7 +648,7 @@ Accept wildcard characters: False
 
 ### -UserList
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The UserList parameter specifies who can use an organizational app. This parameter is limited to 1000 users. In the cloud-based service, this value is less relevant as Office Add-in management is moving to [Centralized Deployment](https://learn.microsoft.com/office/dev/add-ins/publish/centralized-deployment).
 
@@ -703,7 +703,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AuthRedirect.md b/exchange/exchange-ps/ExchangePowerShell/New-AuthRedirect.md
index 4b5e2d74af..d1e633e1c3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-AuthRedirect.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-AuthRedirect.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -50,7 +50,7 @@ This example creates an OAuth redirection object with the following settings:
 
 ### -AuthScheme
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AuthScheme parameter specifies the authentication scheme that's used by the authentication redirection object. Typically, this value is Bearer.
 
@@ -68,7 +68,7 @@ Accept wildcard characters: False
 
 ### -TargetUrl
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TargetUrl parameter specifies the FQDN of the Exchange Client Access Server that's responsible for processing the redirected OAuth authentication requests.
 
@@ -86,7 +86,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -107,7 +107,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -125,7 +125,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AuthServer.md b/exchange/exchange-ps/ExchangePowerShell/New-AuthServer.md
index 7b361bd869..5099979d85 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-AuthServer.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-AuthServer.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -75,7 +75,7 @@ This command creates an authorization server object with the specified settings.
 
 ### -Name
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Name parameter specifies a unique name for the authorization server object. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -93,7 +93,7 @@ Accept wildcard characters: False
 
 ### -AuthMetadataUrl
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AuthMetadataUrl parameter specifies the URL for the Microsoft 365 authorization server for your cloud-based organization.
 
@@ -111,7 +111,7 @@ Accept wildcard characters: False
 
 ### -Type
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Type parameter specifies the type of authorization tokens that are issued by the authorization server. Valid values are:
 
@@ -135,7 +135,7 @@ Accept wildcard characters: False
 
 ### -ApplicationIdentifier
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available in the April 18, 2025 Hotfix update (HU) for Exchange 2019 CU15 and Exchange 2016 CU23.
 
@@ -155,7 +155,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -176,7 +176,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -194,7 +194,7 @@ Accept wildcard characters: False
 
 ### -DomainName
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in Exchange Server 2016 (CU18 or higher) and Exchange Server 2019 (CU7 or higher).
 
@@ -216,7 +216,7 @@ Accept wildcard characters: False
 
 ### -Enabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Enabled parameter specifies whether the authorization server is enabled. Valid values are:
 
@@ -237,7 +237,7 @@ Accept wildcard characters: False
 
 ### -TrustAnySSLCertificate
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TrustAnySSLCertificate switch allows Exchange to accept certificates from untrusted certification authorities (CAs). You don't need to specify a value with this switch.
 
@@ -257,7 +257,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AuthenticationPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-AuthenticationPolicy.md
index a0774f7214..7859c4f25f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-AuthenticationPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-AuthenticationPolicy.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -79,7 +79,7 @@ In Exchange 2019, this example creates a new authentication policy named Researc
 
 ### -Name
 
-> Applicable: Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Name parameter specifies the unique name for the authentication policy. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -361,7 +361,7 @@ Accept wildcard characters: False
 
 ### -BlockLegacyAuthActiveSync
 
-> Applicable: Exchange Server 2019
+> Applicable: Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -389,7 +389,7 @@ Accept wildcard characters: False
 
 ### -BlockLegacyAuthAutodiscover
 
-> Applicable: Exchange Server 2019
+> Applicable: Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -417,7 +417,7 @@ Accept wildcard characters: False
 
 ### -BlockLegacyAuthImap
 
-> Applicable: Exchange Server 2019
+> Applicable: Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -445,7 +445,7 @@ Accept wildcard characters: False
 
 ### -BlockLegacyAuthMapi
 
-> Applicable: Exchange Server 2019
+> Applicable: Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -473,7 +473,7 @@ Accept wildcard characters: False
 
 ### -BlockLegacyAuthOfflineAddressBook
 
-> Applicable: Exchange Server 2019
+> Applicable: Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -501,7 +501,7 @@ Accept wildcard characters: False
 
 ### -BlockLegacyAuthPop
 
-> Applicable: Exchange Server 2019
+> Applicable: Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -529,7 +529,7 @@ Accept wildcard characters: False
 
 ### -BlockLegacyAuthRpc
 
-> Applicable: Exchange Server 2019
+> Applicable: Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -557,7 +557,7 @@ Accept wildcard characters: False
 
 ### -BlockLegacyAuthWebServices
 
-> Applicable: Exchange Server 2019
+> Applicable: Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -585,7 +585,7 @@ Accept wildcard characters: False
 
 ### -BlockModernAuthActiveSync
 
-> Applicable: Exchange Server 2019
+> Applicable: Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -605,7 +605,7 @@ Accept wildcard characters: False
 
 ### -BlockModernAuthAutodiscover
 
-> Applicable: Exchange Server 2019
+> Applicable: Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -625,7 +625,7 @@ Accept wildcard characters: False
 
 ### -BlockModernAuthImap
 
-> Applicable: Exchange Server 2019
+> Applicable: Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -645,7 +645,7 @@ Accept wildcard characters: False
 
 ### -BlockModernAuthMapi
 
-> Applicable: Exchange Server 2019
+> Applicable: Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -665,7 +665,7 @@ Accept wildcard characters: False
 
 ### -BlockModernAuthOfflineAddressBook
 
-> Applicable: Exchange Server 2019
+> Applicable: Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -685,7 +685,7 @@ Accept wildcard characters: False
 
 ### -BlockModernAuthPop
 
-> Applicable: Exchange Server 2019
+> Applicable: Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -705,7 +705,7 @@ Accept wildcard characters: False
 
 ### -BlockModernAuthRpc
 
-> Applicable: Exchange Server 2019
+> Applicable: Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -725,7 +725,7 @@ Accept wildcard characters: False
 
 ### -BlockModernAuthWebServices
 
-> Applicable: Exchange Server 2019
+> Applicable: Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -745,7 +745,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Applicable: Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Applicable: Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -766,7 +766,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Applicable: Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Applicable: Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-AutodiscoverVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/New-AutodiscoverVirtualDirectory.md
index 044ee90f33..b1efe2e9ee 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-AutodiscoverVirtualDirectory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-AutodiscoverVirtualDirectory.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -64,7 +64,7 @@ This example creates the virtual directory autodiscover under the website autodi
 
 ### -ApplicationRoot
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ApplicationRoot parameter specifies the metabase path of the virtual directory. By default, this path is the same as the website in which the virtual directory is created.
 
@@ -82,7 +82,7 @@ Accept wildcard characters: False
 
 ### -AppPoolId
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AppPoolId parameter specifies the IIS application pool in which the virtual directory runs. We recommend that you leave this parameter at its default setting.
 
@@ -100,7 +100,7 @@ Accept wildcard characters: False
 
 ### -BasicAuthentication
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The BasicAuthentication parameter specifies whether Basic authentication is enabled on the virtual directory. Valid values are:
 
@@ -121,7 +121,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -142,7 +142,7 @@ Accept wildcard characters: False
 
 ### -DigestAuthentication
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DigestAuthentication parameter specifies whether Digest authentication is enabled on the virtual directory. Valid values are:
 
@@ -163,7 +163,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -181,7 +181,7 @@ Accept wildcard characters: False
 
 ### -ExtendedProtectionFlags
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExtendedProtectionFlags parameter specifies custom settings for Extended Protection for Authentication on the virtual directory. Valid values are:
 
@@ -205,7 +205,7 @@ Accept wildcard characters: False
 
 ### -ExtendedProtectionSPNList
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExtendedProtectionSPNList parameter specifies a list of valid Service Principal Names (SPNs) if you're using Extended Protection for Authentication on the virtual directory. Valid values are:
 
@@ -226,7 +226,7 @@ Accept wildcard characters: False
 
 ### -ExtendedProtectionTokenChecking
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExtendedProtectionTokenChecking parameter defines how you want to use Extended Protection for Authentication on the virtual directory. Extended Protection for Authentication isn't enabled by default. Valid values are:
 
@@ -290,7 +290,7 @@ Accept wildcard characters: False
 
 ### -OAuthAuthentication
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The OAuthAuthentication parameter specifies whether OAuth authentication is enabled on the virtual directory. Valid values are:
 
@@ -311,7 +311,7 @@ Accept wildcard characters: False
 
 ### -Path
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Path parameter specifies the file system path of the virtual directory. We recommend using this parameter only when you need to use a custom location for the virtual directory files. The default value is blank ($null), which indicates the default location is used.
 
@@ -329,7 +329,7 @@ Accept wildcard characters: False
 
 ### -Role
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Role parameter species the configuration for the virtual directory. Valid values are:
 
@@ -352,7 +352,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Exchange server that hosts the virtual directory. You can use any value that uniquely identifies the server. For example:
 
@@ -375,7 +375,7 @@ Accept wildcard characters: False
 
 ### -WebSiteName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WebSiteName parameter specifies the name of the IIS website under which the virtual directory is created. You don't need to use this parameter to create the virtual directory under the default website.
 
@@ -393,7 +393,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
@@ -411,7 +411,7 @@ Accept wildcard characters: False
 
 ### -WindowsAuthentication
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WindowsAuthentication parameter specifies whether Integrated Windows authentication is enabled on the virtual directory. Valid values are:
 
@@ -432,7 +432,7 @@ Accept wildcard characters: False
 
 ### -WSSecurityAuthentication
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WSSecurityAuthentication parameter specifies whether WS-Security (Web Services Security) authentication is enabled on the virtual directory. Valid values are:
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ClassificationRuleCollection.md b/exchange/exchange-ps/ExchangePowerShell/New-ClassificationRuleCollection.md
index 3c89147d16..66d655e57c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-ClassificationRuleCollection.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-ClassificationRuleCollection.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -47,7 +47,7 @@ This example imports the classification rule collection file C:\\My Documents\\E
 
 ### -FileData
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The FileData parameter specifies the classification rule collection file you want to import.
 
@@ -67,7 +67,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -90,7 +90,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -110,7 +110,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ClientAccessRule.md b/exchange/exchange-ps/ExchangePowerShell/New-ClientAccessRule.md
index ee0bc3376f..23ba2b0095 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-ClientAccessRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-ClientAccessRule.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.WebClient-Help.xml
 Locale: en-US
@@ -93,7 +93,7 @@ This example creates a new client access rule named Block ActiveSync that blocks
 
 ### -Name
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Name parameter specifies a unique name for the client access rule.
 
@@ -111,7 +111,7 @@ Accept wildcard characters: False
 
 ### -Action
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Action parameter specifies the action for the client access rule. Valid values for this parameter are AllowAccess and DenyAccess.
 
@@ -161,7 +161,7 @@ Accept wildcard characters: False
 
 ### -AnyOfClientIPAddressesOrRanges
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The AnyOfClientIPAddressesOrRanges parameter specifies a condition for the client access rule that's based on the client's IPv4 or IPv6 address. Valid values are:
 
@@ -187,7 +187,7 @@ Accept wildcard characters: False
 
 ### -AnyOfProtocols
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The AnyOfProtocols parameter specifies a condition for the client access rule that's based on the client's protocol.
 
@@ -242,7 +242,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -265,7 +265,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -285,7 +285,7 @@ Accept wildcard characters: False
 
 ### -Enabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Enabled parameter specifies whether the client access rule is enabled or disabled. Valid values for this parameter are $true or $false. The default value is $true.
 
@@ -335,7 +335,7 @@ Accept wildcard characters: False
 
 ### -ExceptAnyOfClientIPAddressesOrRanges
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ExceptAnyOfClientIPAddressesOrRanges parameter specifies an exception for the client access rule that's based on the client's IPv4 or IPv6 address. Valid values are:
 
@@ -434,7 +434,7 @@ Accept wildcard characters: False
 
 ### -ExceptUsernameMatchesAnyOfPatterns
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter is functional only in the cloud-based service.
 
@@ -456,7 +456,7 @@ Accept wildcard characters: False
 
 ### -Priority
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Priority parameter specifies a priority value for the rule that determines the order of rule processing. A lower integer value indicates a higher priority, the value 0 is the highest priority, and rules can't have the same priority value.
 
@@ -482,7 +482,7 @@ Accept wildcard characters: False
 
 ### -Scope
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Scope parameter specifies the scope of the client access rule. Valid values are:
 
@@ -521,7 +521,7 @@ Accept wildcard characters: False
 
 ### -UsernameMatchesAnyOfPatterns
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter is functional only in the cloud-based service.
 
@@ -543,7 +543,7 @@ Accept wildcard characters: True
 
 ### -UserRecipientFilter
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter is functional only in the cloud-based service.
 
@@ -594,7 +594,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ComplianceSearch.md b/exchange/exchange-ps/ExchangePowerShell/New-ComplianceSearch.md
index d3311f357a..1d65d88cca 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-ComplianceSearch.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-ComplianceSearch.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 author: chrisda
 external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
 Locale: en-US
@@ -83,7 +83,7 @@ This example creates a new compliance search named AnnBeebe-InactiveMailbox that
 
 ### -Name
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The Name parameter specifies the name of the compliance search. If the value contains spaces, enclose the value in quotation marks.
 
@@ -103,7 +103,7 @@ Accept wildcard characters: False
 
 ### -AllowNotFoundExchangeLocationsEnabled
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The AllowNotFoundExchangeLocationsEnabled parameter specifies whether to include mailboxes other than regular user mailboxes in the compliance search. Valid values are:
 
@@ -155,7 +155,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -176,7 +176,7 @@ Accept wildcard characters: False
 
 ### -ContentMatchQuery
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The ContentMatchQuery parameter specifies a content search filter.
 
@@ -196,7 +196,7 @@ Accept wildcard characters: False
 
 ### -Description
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The Description parameter specifies an optional description for the compliance search. If the value contains spaces, enclose the value in quotation marks.
 
@@ -214,7 +214,7 @@ Accept wildcard characters: False
 
 ### -ExchangeLocation
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The ExchangeLocation parameter specifies the mailboxes to include. Valid values are:
 
@@ -238,7 +238,7 @@ Accept wildcard characters: False
 
 ### -ExchangeLocationExclusion
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 This parameter is functional only in on-premises Exchange.
 
@@ -263,7 +263,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -346,7 +346,7 @@ Accept wildcard characters: False
 
 ### -Language
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The Language parameter specifies the language for the compliance search.
 
@@ -366,7 +366,7 @@ Accept wildcard characters: False
 
 ### -LogLevel
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -468,7 +468,7 @@ Accept wildcard characters: False
 
 ### -StatusMailRecipients
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -488,7 +488,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 This parameter is reserved for internal Microsoft use.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ComplianceSearchAction.md b/exchange/exchange-ps/ExchangePowerShell/New-ComplianceSearchAction.md
index bb12c6f155..e8e407d23b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-ComplianceSearchAction.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-ComplianceSearchAction.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 author: chrisda
 external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
 Locale: en-US
@@ -143,7 +143,7 @@ This example exports the results returned by the content search named "Case 321
 
 ### -SearchName
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The SearchName parameter specifies the name of the existing content search to associate with the content search action. You can specify multiple content searches separated by commas.
 
@@ -183,7 +183,7 @@ Accept wildcard characters: False
 
 ### -ArchiveFormat
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 This parameter is deprecated and no longer used.
 
@@ -203,7 +203,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -246,7 +246,7 @@ Accept wildcard characters: False
 
 ### -ExchangeArchiveFormat
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 **Note**: After May 26, 2025, this parameter is no longer functional. For more information, see [Upcoming changes to Microsoft Purview eDiscovery](https://techcommunity.microsoft.com/blog/microsoft-security-blog/upcoming-changes-to-microsoft-purview-ediscovery/4405084).
 
@@ -279,7 +279,7 @@ Accept wildcard characters: False
 
 ### -Export
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 **Note**: After May 26, 2025, this parameter is no longer functional. For more information, see [Upcoming changes to Microsoft Purview eDiscovery](https://techcommunity.microsoft.com/blog/microsoft-security-blog/upcoming-changes-to-microsoft-purview-ediscovery/4405084).
 
@@ -305,7 +305,7 @@ Accept wildcard characters: False
 
 ### -FileTypeExclusionsForUnindexedItems
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 **Note**: After May 26, 2025, this parameter is no longer functional. For more information, see [Upcoming changes to Microsoft Purview eDiscovery](https://techcommunity.microsoft.com/blog/microsoft-security-blog/upcoming-changes-to-microsoft-purview-ediscovery/4405084).
 
@@ -325,7 +325,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -345,7 +345,7 @@ Accept wildcard characters: False
 
 ### -Format
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 In Security & Compliance PowerShell, this parameter requires the Export role. By default, this role is assigned only to the eDiscovery Manager role group.
 
@@ -369,7 +369,7 @@ Accept wildcard characters: False
 
 ### -IncludeCredential
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The IncludeCredential switch specifies whether to include the credential in the results. You don't need to specify a value with this switch.
 
@@ -412,7 +412,7 @@ Accept wildcard characters: False
 
 ### -JobOptions
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 This parameter is reserved for internal Microsoft use.
 
@@ -430,7 +430,7 @@ Accept wildcard characters: False
 
 ### -NotifyEmail
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 **Note**: After May 26, 2025, this parameter is no longer functional. For more information, see [Upcoming changes to Microsoft Purview eDiscovery](https://techcommunity.microsoft.com/blog/microsoft-security-blog/upcoming-changes-to-microsoft-purview-ediscovery/4405084).
 
@@ -454,7 +454,7 @@ Accept wildcard characters: False
 
 ### -NotifyEmailCC
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 **Note**: After May 26, 2025, this parameter is no longer functional. For more information, see [Upcoming changes to Microsoft Purview eDiscovery](https://techcommunity.microsoft.com/blog/microsoft-security-blog/upcoming-changes-to-microsoft-purview-ediscovery/4405084).
 
@@ -478,7 +478,7 @@ Accept wildcard characters: False
 
 ### -Preview
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 In Security & Compliance PowerShell, this parameter requires the Preview role. By default, this role is assigned only to the eDiscovery Manager role group.
 
@@ -498,7 +498,7 @@ Accept wildcard characters: False
 
 ### -Purge
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 **Note**: In Security & Compliance PowerShell, this switch is available only in the Search and Purge role. By default, this role is assigned only to the Organization Management and Data Investigator role groups.
 
@@ -526,7 +526,7 @@ Accept wildcard characters: False
 
 ### -PurgeType
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 **Note**: In Security & Compliance PowerShell, this parameter is available only in the Search and Purge role. By default, this role is assigned only to the Organization Management and Data Investigator role groups.
 
@@ -549,7 +549,7 @@ Accept wildcard characters: False
 
 ### -ReferenceActionName
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 This parameter is reserved for internal Microsoft use.
 
@@ -567,7 +567,7 @@ Accept wildcard characters: False
 
 ### -Region
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 This parameter is reserved for internal Microsoft use.
 
@@ -585,7 +585,7 @@ Accept wildcard characters: False
 
 ### -Report
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 **Note**: After May 26, 2025, this parameter is no longer functional. For more information, see [Upcoming changes to Microsoft Purview eDiscovery](https://techcommunity.microsoft.com/blog/microsoft-security-blog/upcoming-changes-to-microsoft-purview-ediscovery/4405084).
 
@@ -607,7 +607,7 @@ Accept wildcard characters: False
 
 ### -RetentionReport
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 **Note**: After May 26, 2025, this parameter is no longer functional. For more information, see [Upcoming changes to Microsoft Purview eDiscovery](https://techcommunity.microsoft.com/blog/microsoft-security-blog/upcoming-changes-to-microsoft-purview-ediscovery/4405084).
 
@@ -627,7 +627,7 @@ Accept wildcard characters: False
 
 ### -RetryOnError
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The RetryOnError switch specifies whether to retry the action on any items that failed without re-running the entire action all over again. You don't need to specify a value with this switch.
 
@@ -645,7 +645,7 @@ Accept wildcard characters: False
 
 ### -Scenario
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 In Security & Compliance PowerShell, this parameter requires the Preview role. By default, this role is assigned only to the eDiscovery Manager role group.
 
@@ -672,7 +672,7 @@ Accept wildcard characters: False
 
 ### -Scope
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 **Note**: After May 26, 2025, this parameter is no longer functional. For more information, see [Upcoming changes to Microsoft Purview eDiscovery](https://techcommunity.microsoft.com/blog/microsoft-security-blog/upcoming-changes-to-microsoft-purview-ediscovery/4405084).
 
@@ -718,7 +718,7 @@ Accept wildcard characters: False
 
 ### -SharePointArchiveFormat
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 **Note**: After May 26, 2025, this parameter is no longer functional. For more information, see [Upcoming changes to Microsoft Purview eDiscovery](https://techcommunity.microsoft.com/blog/microsoft-security-blog/upcoming-changes-to-microsoft-purview-ediscovery/4405084).
 
@@ -748,7 +748,7 @@ Accept wildcard characters: False
 
 ### -ShareRootPath
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -770,7 +770,7 @@ Accept wildcard characters: False
 
 ### -Version
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 This parameter is reserved for internal Microsoft use.
 
@@ -788,7 +788,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The WhatIf switch doesn't work in Security & Compliance PowerShell.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ComplianceSecurityFilter.md b/exchange/exchange-ps/ExchangePowerShell/New-ComplianceSecurityFilter.md
index fb2266e405..f5a9a1faf0 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-ComplianceSecurityFilter.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-ComplianceSecurityFilter.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 author: chrisda
 external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
 Locale: en-US
@@ -77,7 +77,7 @@ This example prevents the user from performing any compliance search actions on
 
 ### -Action
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The Action parameter specifies that type of search action that the filter is applied to. Valid values are:
 
@@ -101,7 +101,7 @@ Accept wildcard characters: False
 
 ### -FilterName
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The FilterName parameter specifies the name for the compliance security filter. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -119,7 +119,7 @@ Accept wildcard characters: False
 
 ### -Users
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The Users parameter specifies the user who gets this filter applied to their searches. Valid values are:
 
@@ -143,7 +143,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -164,7 +164,7 @@ Accept wildcard characters: False
 
 ### -Description
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The Description parameter specifies a description for the compliance security filter. The maximum length is 256 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -182,7 +182,7 @@ Accept wildcard characters: False
 
 ### -Filters
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The Filters parameter specifies the search criteria for the compliance security filter. The filters are applied to the users specified by the Users parameter. You can create three different types of filters:
 
@@ -208,7 +208,7 @@ Accept wildcard characters: False
 
 ### -Region
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The Region parameter specifies the satellite location for multi-geo tenants to conduct eDiscovery searches in. Valid values are:
 
@@ -239,7 +239,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The WhatIf switch doesn't work in Security & Compliance PowerShell.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DataClassification.md b/exchange/exchange-ps/ExchangePowerShell/New-DataClassification.md
index 4fd215d87d..814dda3ec9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-DataClassification.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-DataClassification.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -59,7 +59,7 @@ This example creates a new data classification rule named "Contoso Employee-Cust
 
 ### -Description
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Description parameter specifies a description for the data classification rule.
 
@@ -77,7 +77,7 @@ Accept wildcard characters: False
 
 ### -Fingerprints
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Fingerprints parameter specifies the byte-encoded files to use as document fingerprints. You can use multiple document fingerprints separated by commas. For instructions on how to import documents to use as templates for fingerprints, see [New-Fingerprint](https://learn.microsoft.com/powershell/module/exchangepowershell/new-fingerprint) or the Examples section.
 
@@ -95,7 +95,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Name parameter specifies a name for the data classification rule. The value must be less than 256 characters.
 
@@ -115,7 +115,7 @@ Accept wildcard characters: False
 
 ### -ClassificationRuleCollectionIdentity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is reserved for internal Microsoft use.
 
@@ -133,7 +133,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -154,7 +154,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -172,7 +172,7 @@ Accept wildcard characters: False
 
 ### -Locale
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Locale parameter specifies the language that's associated with the data classification rule.
 
@@ -194,7 +194,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DatabaseAvailabilityGroup.md b/exchange/exchange-ps/ExchangePowerShell/New-DatabaseAvailabilityGroup.md
index dbe1a8d9f5..ef1b7794e4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-DatabaseAvailabilityGroup.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-DatabaseAvailabilityGroup.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -83,7 +83,7 @@ This example creates a DAG named DAG3. DAG3 is configured to use SERVER1 for the
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Name parameter specifies a unique name for the new DAG of up to 15 characters. The name you use must not conflict with any computer name in the organization.
 
@@ -101,7 +101,7 @@ Accept wildcard characters: False
 
 ### -ActivityState
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -119,7 +119,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -140,7 +140,7 @@ Accept wildcard characters: False
 
 ### -DagConfiguration
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -158,7 +158,7 @@ Accept wildcard characters: False
 
 ### -DatabaseAvailabilityGroupIpAddresses
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DatabaseAvailabilityGroupIpAddresses parameter specifies one or more static IPv4 addresses to the DAG when a Mailbox server is added to a DAG. If you specify the value Any or 0.0.0.0, the system attempts to lease one or more IPv4 addresses from a DHCP server to assign to the DAG. If you don't use this parameter, or if you specify the value 255.255.255.255 or None, the DAG is created without a cluster administrative access point.
 
@@ -176,7 +176,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -194,7 +194,7 @@ Accept wildcard characters: False
 
 ### -FileSystem
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The FileSystem parameter specifies the file system that's used for the DAG. Valid values are:
 
@@ -215,7 +215,7 @@ Accept wildcard characters: False
 
 ### -ThirdPartyReplication
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ThirdPartyReplication parameter specifies to configure and enable a DAG to use non-Microsoft replication that leverages the Exchange Third Party Replication API instead of the built-in continuous replication. Valid values are Enabled and Disabled. After this mode is enabled, it can't be changed.
 
@@ -233,7 +233,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
@@ -251,7 +251,7 @@ Accept wildcard characters: False
 
 ### -WitnessDirectory
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WitnessDirectory parameter specifies the name of the directory on the witness server used to store file share witness data. The directory and share should be hosted on an Exchange server other than any of the Mailbox servers in the DAG. This allows an Exchange administrator to maintain operational control over the directory. The specified directory can't be used by any other DAGs, or used for any purpose other than for the witness server. If you don't use this parameter, the default witness directory is used.
 
@@ -269,7 +269,7 @@ Accept wildcard characters: False
 
 ### -WitnessServer
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WitnessServer parameter specifies the name of a server used as a quorum witness when the DAG contains an even number of members. The specified server can't be a member of the DAG that's configured to use it. A stand-alone Mailbox server, or a Mailbox server in another DAG is recommended.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DatabaseAvailabilityGroupNetwork.md b/exchange/exchange-ps/ExchangePowerShell/New-DatabaseAvailabilityGroupNetwork.md
index 002a7d6101..03792b5b80 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-DatabaseAvailabilityGroupNetwork.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-DatabaseAvailabilityGroupNetwork.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -49,7 +49,7 @@ This example creates the DAG network DAG1Repl in the DAG DAG1. A subnet of 10.0.
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Name parameter specifies the name of the DAG network being created.
 
@@ -67,7 +67,7 @@ Accept wildcard characters: False
 
 ### -DatabaseAvailabilityGroup
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DatabaseAvailabilityGroup parameter specifies the name of the DAG that'll use the network being created.
 
@@ -85,7 +85,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -106,7 +106,7 @@ Accept wildcard characters: False
 
 ### -Description
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Description parameter specifies an optional description of up to 256 characters for the DAG network being created.
 
@@ -124,7 +124,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -142,7 +142,7 @@ Accept wildcard characters: False
 
 ### -IgnoreNetwork
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IgnoreNetwork parameter excludes the DAG network from use by the DAG.
 
@@ -160,7 +160,7 @@ Accept wildcard characters: False
 
 ### -ReplicationEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ReplicationEnabled parameter specifies whether the DAG network being created is enabled for continuous replication.
 
@@ -178,7 +178,7 @@ Accept wildcard characters: False
 
 ### -Subnets
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Subnets parameter specifies the subnets for the DAG network being created.
 
@@ -196,7 +196,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DeliveryAgentConnector.md b/exchange/exchange-ps/ExchangePowerShell/New-DeliveryAgentConnector.md
index 3320d9ce11..40b22a450d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-DeliveryAgentConnector.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-DeliveryAgentConnector.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -64,7 +64,7 @@ The address space for the connector is c=US;a=Fabrikam;p=Contoso.
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Name parameter specifies the name of this delivery agent connector. The value for the Name parameter can't exceed 64 characters.
 
@@ -82,7 +82,7 @@ Accept wildcard characters: False
 
 ### -AddressSpaces
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AddressSpaces parameter specifies the domain names that the delivery agent connector is responsible for. The complete syntax for entering an address space is: `AddressSpaceType:AddressSpace;AddressSpaceCost`. Enclose each address space in quotation marks (").
 
@@ -100,7 +100,7 @@ Accept wildcard characters: False
 
 ### -DeliveryProtocol
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DeliveryProtocol parameter specifies the communication protocol that determines which delivery agents are responsible for servicing the connector.
 
@@ -118,7 +118,7 @@ Accept wildcard characters: False
 
 ### -Comment
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Comment parameter specifies an optional comment. If you specify a value that contains spaces, enclose the value in quotation marks ("), for example: "This is an admin note".
 
@@ -136,7 +136,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -157,7 +157,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -177,7 +177,7 @@ Accept wildcard characters: False
 
 ### -Enabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Enabled parameter specifies whether the delivery agent connector is enabled.
 
@@ -197,7 +197,7 @@ Accept wildcard characters: False
 
 ### -IsScopedConnector
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IsScopedConnector parameter specifies the availability of the connector to other Mailbox servers. If the value of this parameter is $false, the connector can be used by all Mailbox servers in your organization. If the value of this parameter is $true, the connector can only be used by Mailbox servers in the same Active Directory site. The default value is $false.
 
@@ -215,7 +215,7 @@ Accept wildcard characters: False
 
 ### -MaxConcurrentConnections
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MaxConcurrentConnections parameter specifies the maximum number of concurrent connections this connector accepts from a specific IP address. The default value is 5.
 
@@ -233,7 +233,7 @@ Accept wildcard characters: False
 
 ### -MaxMessageSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MaxMessageSize parameter specifies the maximum size of a message that's allowed to pass through this connector. When you enter a value, qualify the value with one of the following units:
 
@@ -258,7 +258,7 @@ Accept wildcard characters: False
 
 ### -MaxMessagesPerConnection
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MaxMessagesPerConnection parameter specifies the maximum number of messages this connector accepts per connection. The connector terminates the connection after this limit is reached, and the sending server has to initiate a new connection to send more messages. The default value is 20.
 
@@ -276,7 +276,7 @@ Accept wildcard characters: False
 
 ### -SourceTransportServers
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SourceTransportServers parameter specifies the list of Mailbox servers that host this connector. You can specify more than one server by separating their names with commas.
 
@@ -296,7 +296,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DistributionGroup.md b/exchange/exchange-ps/ExchangePowerShell/New-DistributionGroup.md
index a8e5f0ae79..d42dea38c6 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-DistributionGroup.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-DistributionGroup.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
 Locale: en-US
@@ -86,7 +86,7 @@ This example creates a distribution group named ITDepartment and specifies the m
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Name parameter specifies the unique name of the group. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -106,7 +106,7 @@ Accept wildcard characters: False
 
 ### -Alias
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Alias parameter specifies the Exchange alias (also known as the mail nickname) for the recipient. This value identifies the recipient as a mail-enabled object, and shouldn't be confused with multiple email addresses for the same recipient (also known as proxy addresses). A recipient can have only one Alias value. The maximum length is 64 characters.
 
@@ -142,7 +142,7 @@ Accept wildcard characters: False
 
 ### -ArbitrationMailbox
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -196,7 +196,7 @@ Accept wildcard characters: False
 
 ### -BypassNestedModerationEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ByPassNestedModerationEnabled parameter specifies how to handle message approval when a moderated group contains other moderated groups as members. Valid values are:
 
@@ -219,7 +219,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -240,7 +240,7 @@ Accept wildcard characters: False
 
 ### -CopyOwnerToMember
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The CopyOwnerToMember switch specifies whether group owners specified by the ManagedBy parameter are also members of the group. You don't need to specify a value with this switch.
 
@@ -278,7 +278,7 @@ Accept wildcard characters: False
 
 ### -DisplayName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The DisplayName parameter specifies the display name of the group. The display name is visible in the Exchange admin center and in address lists. The maximum length is 256 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -300,7 +300,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -344,7 +344,7 @@ Accept wildcard characters: False
 
 ### -IgnoreNamingPolicy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The IgnoreNamingPolicy switch specifies whether to prevent this group from being affected by your organization's group naming policy. You don't need to specify a value with this switch.
 
@@ -364,7 +364,7 @@ Accept wildcard characters: False
 
 ### -ManagedBy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ManagedBy parameter specifies an owner for the group. A group must have at least one owner. If you don't use this parameter to specify the owner when you create the group, the user account that created the group is the owner. The group owner is able to:
 
@@ -414,7 +414,7 @@ Accept wildcard characters: False
 
 ### -MemberDepartRestriction
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The MemberDepartRestriction parameter specifies the restrictions that you put on requests to leave the group. Valid values are:
 
@@ -435,7 +435,7 @@ Accept wildcard characters: False
 
 ### -MemberJoinRestriction
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The MemberJoinRestriction parameter specifies the restrictions that you put on requests to join the group. Valid values are:
 
@@ -457,7 +457,7 @@ Accept wildcard characters: False
 
 ### -Members
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Members parameter specifies the recipients (mail-enabled objects) that are members of the group. You can use any value that uniquely identifies the recipient. For example:
 
@@ -490,7 +490,7 @@ Accept wildcard characters: False
 
 ### -ModeratedBy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ModeratedBy parameter specifies one or more moderators for this group. A moderator approves messages sent to the group before the messages are delivered. A moderator must be a mailbox, mail user, or mail contact in your organization. You can use any value that uniquely identifies the moderator. For example:
 
@@ -521,7 +521,7 @@ Accept wildcard characters: False
 
 ### -ModerationEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ModerationEnabled parameter specifies whether moderation is enabled for this recipient. Valid value are:
 
@@ -544,7 +544,7 @@ Accept wildcard characters: False
 
 ### -Notes
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Notes parameters specifies additional information about the object. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -562,7 +562,7 @@ Accept wildcard characters: False
 
 ### -OrganizationalUnit
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The OrganizationalUnit parameter specifies the location in Active Directory where the group is created.
 
@@ -587,7 +587,7 @@ Accept wildcard characters: False
 
 ### -PrimarySmtpAddress
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The PrimarySmtpAddress parameter specifies the primary return email address that's used for the recipient.
 
@@ -605,7 +605,7 @@ Accept wildcard characters: False
 
 ### -RequireSenderAuthenticationEnabled
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The RequireSenderAuthenticationEnabled parameter specifies whether to accept messages only from authenticated (internal) senders. Valid values are:
 
@@ -628,7 +628,7 @@ Accept wildcard characters: False
 
 ### -RoomList
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The RoomList switch specifies that all members of this distribution group are room mailboxes. You don't need to specify a value with this switch.
 
@@ -648,7 +648,7 @@ Accept wildcard characters: False
 
 ### -SamAccountName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -668,7 +668,7 @@ Accept wildcard characters: False
 
 ### -SendModerationNotifications
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The SendModerationNotifications parameter specifies when moderation notification messages are sent. Valid values are:
 
@@ -692,7 +692,7 @@ Accept wildcard characters: False
 
 ### -Type
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Type parameter specifies the type of group that you want to create. Valid values are:
 
@@ -715,7 +715,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DlpPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-DlpPolicy.md
index e366f86920..fb92390c12 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-DlpPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-DlpPolicy.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -56,7 +56,7 @@ This example creates a new DLP policy named Contoso PII with the following value
 
 ### -Name
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Name parameter specifies a descriptive name for the DLP policy.
 
@@ -74,7 +74,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -95,7 +95,7 @@ Accept wildcard characters: False
 
 ### -Description
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Description parameter specifies an optional description for the DLP policy.
 
@@ -113,7 +113,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -131,7 +131,7 @@ Accept wildcard characters: False
 
 ### -Mode
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Mode parameter specifies the action and notification level of the DLP policy. Valid values for this parameter are:
 
@@ -155,7 +155,7 @@ Accept wildcard characters: False
 
 ### -Parameters
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Parameters parameter specifies the parameter values that are required by the DLP policy template that you specify using the Template or TemplateData parameters. DLP policy templates might contain parameters that need to be populated with values from your organization. For example, a DLP policy template might include an exception group that defines users who are exempt from the DLP policy.
 
@@ -175,7 +175,7 @@ Accept wildcard characters: False
 
 ### -State
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The State parameter enables or disables the DLP policy. Valid input for this parameter is Enabled or Disabled. By default, a new DLP policy that you create is enabled. If you want to create a disabled DLP policy, specify the value Disabled for this parameter.
 
@@ -193,7 +193,7 @@ Accept wildcard characters: False
 
 ### -Template
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Template parameter specifies the existing DLP policy template from which you can create a new DLP policy. You can't use the Template and TemplateData parameters in the same command.
 
@@ -211,7 +211,7 @@ Accept wildcard characters: False
 
 ### -TemplateData
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The TemplateData parameter specifies an external DLP policy template file from which you can create a new DLP policy. You can't use the TemplateData and Template parameters in the same command.
 
@@ -231,7 +231,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DynamicDistributionGroup.md b/exchange/exchange-ps/ExchangePowerShell/New-DynamicDistributionGroup.md
index 97a2f8867f..4cf94192f6 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-DynamicDistributionGroup.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-DynamicDistributionGroup.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
 Locale: en-US
@@ -108,7 +108,7 @@ This example creates a dynamic distribution group named Washington Management Te
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Name parameter specifies the unique name of the dynamic distribution group. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -128,7 +128,7 @@ Accept wildcard characters: False
 
 ### -IncludedRecipients
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The IncludedRecipients parameter specifies a precanned filter that's based on the recipient type. Valid values are:
 
@@ -157,7 +157,7 @@ Accept wildcard characters: False
 
 ### -RecipientFilter
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The RecipientFilter parameter specifies a custom OPATH filter that's based on the value of any available recipient property. You can use any available Windows PowerShell operator, and wildcards and partial matches are supported. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`.
 
@@ -188,7 +188,7 @@ Accept wildcard characters: False
 
 ### -Alias
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Alias parameter specifies the Exchange alias (also known as the mail nickname) for the recipient. This value identifies the recipient as a mail-enabled object, and shouldn't be confused with multiple email addresses for the same recipient (also known as proxy addresses). A recipient can have only one Alias value. The maximum length is 64 characters.
 
@@ -224,7 +224,7 @@ Accept wildcard characters: False
 
 ### -ArbitrationMailbox
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -255,7 +255,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCompany
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ConditionalCompany parameter specifies a precanned filter that's based on the value of the recipient's Company property. You can specify multiple values separated by commas.
 
@@ -277,7 +277,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute1
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ConditionalCustomAttribute1 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute1 property. You can specify multiple values separated by commas.
 
@@ -299,7 +299,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute10
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ConditionalCustomAttribute10 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute10 property. You can specify multiple values separated by commas.
 
@@ -321,7 +321,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute11
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ConditionalCustomAttribute11 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute11 property. You can specify multiple values separated by commas.
 
@@ -343,7 +343,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute12
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ConditionalCustomAttribute12 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute12 property. You can specify multiple values separated by commas.
 
@@ -365,7 +365,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute13
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ConditionalCustomAttribute13 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute13 property. You can specify multiple values separated by commas.
 
@@ -387,7 +387,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute14
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ConditionalCustomAttribute14 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute14 property. You can specify multiple values separated by commas.
 
@@ -409,7 +409,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute15
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ConditionalCustomAttribute15 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute15 property. You can specify multiple values separated by commas.
 
@@ -431,7 +431,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute2
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ConditionalCustomAttribute2 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute2 property. You can specify multiple values separated by commas.
 
@@ -453,7 +453,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute3
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ConditionalCustomAttribute3 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute3 property. You can specify multiple values separated by commas.
 
@@ -475,7 +475,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute4
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ConditionalCustomAttribute4 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute4 property. You can specify multiple values separated by commas.
 
@@ -497,7 +497,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute5
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ConditionalCustomAttribute5 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute5 property. You can specify multiple values separated by commas.
 
@@ -519,7 +519,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute6
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ConditionalCustomAttribute6 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute6 property. You can specify multiple values separated by commas.
 
@@ -541,7 +541,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute7
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ConditionalCustomAttribute7 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute7 property. You can specify multiple values separated by commas.
 
@@ -563,7 +563,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute8
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ConditionalCustomAttribute8 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute8 property. You can specify multiple values separated by commas.
 
@@ -585,7 +585,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute9
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ConditionalCustomAttribute9 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute9 property. You can specify multiple values separated by commas.
 
@@ -607,7 +607,7 @@ Accept wildcard characters: False
 
 ### -ConditionalDepartment
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ConditionalDepartment parameter specifies a precanned filter that's based on the value of the recipient's Department property. You can specify multiple values separated by commas.
 
@@ -629,7 +629,7 @@ Accept wildcard characters: False
 
 ### -ConditionalStateOrProvince
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ConditionalStateOrProvince parameter specifies a precanned filter that's based on the value of the recipient's StateOrProvince property. You can specify multiple values separated by commas.
 
@@ -651,7 +651,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -692,7 +692,7 @@ Accept wildcard characters: False
 
 ### -DisplayName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The DisplayName parameter specifies the display name of the dynamic distribution group. The display name is visible in the Exchange admin center and in address lists. The maximum length is 256 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -712,7 +712,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -732,7 +732,7 @@ Accept wildcard characters: False
 
 ### -ModeratedBy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ModeratedBy parameter specifies one or more moderators for this recipient. A moderator approves messages sent to the recipient before the messages are delivered. A moderator must be a mailbox, mail user, or mail contact in your organization. You can use any value that uniquely identifies the moderator. For example:
 
@@ -761,7 +761,7 @@ Accept wildcard characters: False
 
 ### -ModerationEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ModerationEnabled parameter specifies whether moderation is enabled for this recipient. Valid value are:
 
@@ -784,7 +784,7 @@ Accept wildcard characters: False
 
 ### -OrganizationalUnit
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The OrganizationalUnit parameter specifies the organizational unit (OU) where the dynamic distribution group is created.
 
@@ -815,7 +815,7 @@ Accept wildcard characters: False
 
 ### -PrimarySmtpAddress
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The PrimarySmtpAddress parameter specifies the primary return email address that's used for the recipient.
 
@@ -833,7 +833,7 @@ Accept wildcard characters: False
 
 ### -RecipientContainer
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The RecipientContainer parameter specifies a filter that's based on the recipient's location in Active Directory. Valid input for this parameter is an organizational unit (OU) or domain that's returned by the Get-OrganizationalUnit cmdlet. You can use any value that uniquely identifies the OU or domain. For example:
 
@@ -862,7 +862,7 @@ Accept wildcard characters: False
 
 ### -SendModerationNotifications
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The SendModerationNotifications parameter specifies when moderation notification messages are sent. Valid values are:
 
@@ -886,7 +886,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-EcpVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/New-EcpVirtualDirectory.md
index d7db96a683..825155ed1e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-EcpVirtualDirectory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-EcpVirtualDirectory.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -56,7 +56,7 @@ This example creates the ECP virtual directory on the Exchange server named Serv
 
 ### -AppPoolId
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AppPoolId parameter sets the IIS application pool where the ECP virtual directory runs. We recommend that you leave this parameter at its default setting.
 
@@ -74,7 +74,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -95,7 +95,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -113,7 +113,7 @@ Accept wildcard characters: False
 
 ### -ExtendedProtectionFlags
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExtendedProtectionFlags parameter specifies custom settings for Extended Protection for Authentication on the virtual directory. Valid values are:
 
@@ -137,7 +137,7 @@ Accept wildcard characters: False
 
 ### -ExtendedProtectionSPNList
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExtendedProtectionSPNList parameter specifies a list of valid Service Principal Names (SPNs) if you're using Extended Protection for Authentication on the virtual directory. Valid values are:
 
@@ -158,7 +158,7 @@ Accept wildcard characters: False
 
 ### -ExtendedProtectionTokenChecking
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExtendedProtectionTokenChecking parameter defines how you want to use Extended Protection for Authentication on the virtual directory. Extended Protection for Authentication isn't enabled by default. Valid values are:
 
@@ -182,7 +182,7 @@ Accept wildcard characters: False
 
 ### -ExternalUrl
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExternalURL parameter specifies the URL that's used to connect to the virtual directory from outside the firewall.
 
@@ -202,7 +202,7 @@ Accept wildcard characters: False
 
 ### -InternalUrl
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The InternalURL parameter specifies the URL that's used to connect to the virtual directory from inside the firewall.
 
@@ -222,7 +222,7 @@ Accept wildcard characters: False
 
 ### -Path
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Path parameter sets the file system path of the ECP virtual directory. This parameter should be used with care and only when you must use a different file system path than the default.
 
@@ -240,7 +240,7 @@ Accept wildcard characters: False
 
 ### -Role
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Role parameter species the configuration for the virtual directory. Valid values are:
 
@@ -263,7 +263,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Exchange server that hosts the virtual directory. You can use any value that uniquely identifies the server. For example:
 
@@ -288,7 +288,7 @@ Accept wildcard characters: False
 
 ### -WebSiteName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WebSiteName parameter specifies the name of the IIS website where the ECP virtual directory is created.
 
@@ -306,7 +306,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-EdgeSubscription.md b/exchange/exchange-ps/ExchangePowerShell/New-EdgeSubscription.md
index 0f3c1a24b3..4732c31488 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-EdgeSubscription.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-EdgeSubscription.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -71,7 +71,7 @@ This example also imports the Edge Subscription file generated in Example 1 to t
 
 ### -AccountExpiryDuration
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AccountExpiryDuration parameter specifies how soon the EdgeSync bootstrap replication account (ESBRA) created by this command expires.
 
@@ -93,7 +93,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -114,7 +114,7 @@ Accept wildcard characters: False
 
 ### -CreateInboundSendConnector
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The CreateInboundSendConnector parameter specifies whether to create the Send connector to connect the Edge Transport server and the Hub Transport servers. The default value is $true. The Send connector address space is set to "--", the smart hosts are set to "--", the Edge Transport server is set as the source server and Domain Name System (DNS) routing is disabled. This parameter is only used when you run the command on the Hub Transport server.
 
@@ -132,7 +132,7 @@ Accept wildcard characters: False
 
 ### -CreateInternetSendConnector
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The CreateInternetSendConnector parameter specifies whether to create the Send connector to connect to the Internet. The default value is $true. The Send connector address space is set to all domains (\*), the Edge Transport server is set as the source server, and DNS routing is enabled. This parameter is only used when you run the command on the Hub Transport server.
 
@@ -150,7 +150,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -170,7 +170,7 @@ Accept wildcard characters: False
 
 ### -FileData
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The FileData parameter specifies the byte-encoded data object that contains the Edge Subscription file information.
 
@@ -192,7 +192,7 @@ Accept wildcard characters: False
 
 ### -FileName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The FileName parameter specifies the full path of the Edge Subscription file.
 
@@ -212,7 +212,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -235,7 +235,7 @@ Accept wildcard characters: False
 
 ### -Site
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Site parameter specifies the name of the Active Directory site that contains the Mailbox servers with which the Edge Transport servers are associated. This parameter is used and required only when you run the command on a Mailbox server.
 
@@ -253,7 +253,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-EdgeSyncServiceConfig.md b/exchange/exchange-ps/ExchangePowerShell/New-EdgeSyncServiceConfig.md
index c64ac8e72c..3558c79196 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-EdgeSyncServiceConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-EdgeSyncServiceConfig.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -63,7 +63,7 @@ This example creates EdgeSync service settings with the following configuration:
 
 ### -ConfigurationSyncInterval
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ConfigurationSyncInterval parameter specifies how frequently the EdgeSync service synchronizes configuration data. The default value is 3 minutes.
 
@@ -83,7 +83,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -104,7 +104,7 @@ Accept wildcard characters: False
 
 ### -CookieValidDuration
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The CookieValidDuration parameter specifies how long a cookie record is valid. The default value is 21 days.
 
@@ -124,7 +124,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -142,7 +142,7 @@ Accept wildcard characters: False
 
 ### -FailoverDCInterval
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The FailoverDCInterval parameter specifies how long EdgeSync waits before failing over to another domain controller if it can't read configuration data from Active Directory. The default value is 5 minutes.
 
@@ -162,7 +162,7 @@ Accept wildcard characters: False
 
 ### -LockDuration
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The LockDuration parameter specifies how long an instance of the EdgeSync service can maintain an exclusive lock on the synchronization rights. While an EdgeSync service maintains an exclusive lock on synchronization rights, no other EdgeSync service can take over synchronization. The default value is 6 minutes.
 
@@ -182,7 +182,7 @@ Accept wildcard characters: False
 
 ### -LockRenewalDuration
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The LockRenewalDuration parameter specifies how long before the expiry of an exclusive lock an EdgeSync service can renew the lock. The default value is 4 minutes.
 
@@ -202,7 +202,7 @@ Accept wildcard characters: False
 
 ### -LogEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The LogEnabled parameter enables or disables the EdgeSync log. Valid input for this parameter is $true or $false. The default value is $true.
 
@@ -220,7 +220,7 @@ Accept wildcard characters: False
 
 ### -LogLevel
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The LogLevel parameter specifies the EdgeSync logging level. Valid values are:
 
@@ -243,7 +243,7 @@ Accept wildcard characters: False
 
 ### -LogMaxAge
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The LogMaxAge parameter specifies the maximum duration in days to keep the EdgeSyncLog files. Log files older than the specified value can be overwritten. The default value is 30 days.
 
@@ -263,7 +263,7 @@ Accept wildcard characters: False
 
 ### -LogMaxDirectorySize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The LogMaxDirectorySize parameter specifies the maximum amount of disk space the EdgeSyncLog directory can use. The default value is 250 MB.
 
@@ -293,7 +293,7 @@ Accept wildcard characters: False
 
 ### -LogMaxFileSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The LogMaxFileSize parameter specifies the maximum log file size for the EdgeSyncLog files. The default value is 10 MB.
 
@@ -323,7 +323,7 @@ Accept wildcard characters: False
 
 ### -LogPath
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The LogPath parameter specifies the default location for the EdgeSyncLog files. The default value is TransportRoles\\Logs\\EdgeSync\\.
 
@@ -341,7 +341,7 @@ Accept wildcard characters: False
 
 ### -OptionDuration
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The OptionDuration parameter specifies how long an instance of the EdgeSync service can maintain an optional lock on synchronization rights. While an EdgeSync service maintains an optional lock on synchronization rights, another EdgeSync service can take over synchronization after the optional lock has expired if it's initiated using the Start-EdgeSynchronization command. The default value is 30 minutes.
 
@@ -361,7 +361,7 @@ Accept wildcard characters: False
 
 ### -RecipientSyncInterval
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RecipientSyncInterval parameter specifies how frequently the EdgeSync service synchronizes recipient data from the global catalog. The default value is 5 minutes.
 
@@ -381,7 +381,7 @@ Accept wildcard characters: False
 
 ### -Site
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Site parameter specifies the Active Directory site that EdgeSync connects to for synchronizing configuration and recipient data.
 
@@ -399,7 +399,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-EmailAddressPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-EmailAddressPolicy.md
index aaa242cc86..47015880ec 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-EmailAddressPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-EmailAddressPolicy.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -175,7 +175,7 @@ This example creates an email address policy in an on-premises Exchange organiza
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Name parameter specifies the unique name of the email address policy. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -193,7 +193,7 @@ Accept wildcard characters: False
 
 ### -EnabledEmailAddressTemplates
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The EnabledEmailAddressTemplates parameter specifies the rules in the email address policy that are used to generate email addresses for recipients.
 
@@ -224,7 +224,7 @@ Accept wildcard characters: False
 
 ### -EnabledPrimarySMTPAddressTemplate
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The EnabledPrimarySMTPAddressTemplate parameter specifies the rule in the email address policy that's used to generate the primary SMTP email addresses for recipients. You can use this parameter instead of the EnabledEmailAddressTemplates if the policy only applies the primary email address and no additional proxy addresses.
 
@@ -248,7 +248,7 @@ Accept wildcard characters: False
 
 ### -IncludedRecipients
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -301,7 +301,7 @@ Accept wildcard characters: False
 
 ### -RecipientFilter
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -332,7 +332,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCompany
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -356,7 +356,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute1
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -380,7 +380,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute10
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -404,7 +404,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute11
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -428,7 +428,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute12
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -452,7 +452,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute13
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -476,7 +476,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute14
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -500,7 +500,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute15
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -524,7 +524,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute2
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -548,7 +548,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute3
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -572,7 +572,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute4
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -596,7 +596,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute5
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -620,7 +620,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute6
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -644,7 +644,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute7
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -668,7 +668,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute8
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -692,7 +692,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute9
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -716,7 +716,7 @@ Accept wildcard characters: False
 
 ### -ConditionalDepartment
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -740,7 +740,7 @@ Accept wildcard characters: False
 
 ### -ConditionalStateOrProvince
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -764,7 +764,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -785,7 +785,7 @@ Accept wildcard characters: False
 
 ### -DisabledEmailAddressTemplates
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -812,7 +812,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -866,7 +866,7 @@ Accept wildcard characters: False
 
 ### -Priority
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Priority parameter specifies the order that the email address policies are evaluated. By default, every time that you add a new email address policy, the policy is assigned a priority of N+1, where N is the number of email address policies that you've created.
 
@@ -888,7 +888,7 @@ Accept wildcard characters: False
 
 ### -RecipientContainer
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -915,7 +915,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ExchangeCertificate.md b/exchange/exchange-ps/ExchangePowerShell/New-ExchangeCertificate.md
index 9c2195d866..34bd153ff5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-ExchangeCertificate.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-ExchangeCertificate.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -182,7 +182,7 @@ This example creates a new DER encoded (binary) certificate renewal request file
 
 ### -BinaryEncoded
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The BinaryEncoded switch specifies whether to encode the new certificate request by using Distinguished Encoding Rules (DER). You don't need to specify a value with this switch.
 
@@ -206,7 +206,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -227,7 +227,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -247,7 +247,7 @@ Accept wildcard characters: False
 
 ### -DomainName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainName parameter specifies one or more FQDNs or server names for theSubject Alternative Name field (also known as the Subject Alt Name or SAN field) of the certificate request or self-signed certificate.
 
@@ -274,7 +274,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -294,7 +294,7 @@ Accept wildcard characters: False
 
 ### -FriendlyName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The FriendlyName parameter specifies a friendly name for the certificate request or self-signed certificate. The value must be less than 64 characters.
 
@@ -314,7 +314,7 @@ Accept wildcard characters: False
 
 ### -GenerateRequest
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The GenerateRequest switch specifies that you're creating a certificate request for a certification authority (CA). You don't need to specify a value with this switch.
 
@@ -338,7 +338,7 @@ Accept wildcard characters: False
 
 ### -IncludeAcceptedDomains
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IncludeAcceptedDomains switch specifies that all accepted domains in the Exchange organization are included in the Subject Alternative Name field of the certificate request or self-signed certificate. You don't need to specify a value with this switch.
 
@@ -361,7 +361,7 @@ Accept wildcard characters: False
 
 ### -IncludeAutoDiscover
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IncludeAutoDiscover switch specifies whether to add a Subject Alternative Namevalue with the prefix autodiscover for each accepted domain in the Exchange organization. You don't need to specify a value with this switch.
 
@@ -389,7 +389,7 @@ Accept wildcard characters: False
 
 ### -IncludeServerFQDN
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IncludeServerFQDN switch specifies that the FQDN of the Exchange server is included in the Subject Alternative Name field of the new certificate request or self-signed certificate. You don't need to specify a value with this switch.
 
@@ -409,7 +409,7 @@ Accept wildcard characters: False
 
 ### -IncludeServerNetBIOSName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IncludeServerNetBIOSName switch specifies that the NetBIOS name of the Exchange server is included in the Subject Alternative Name field of the new certificate request or self-signed certificate. You don't need to specify a value with this switch
 
@@ -429,7 +429,7 @@ Accept wildcard characters: False
 
 ### -Instance
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is deprecated and no longer used.
 
@@ -447,7 +447,7 @@ Accept wildcard characters: False
 
 ### -KeySize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The KeySize parameter specifies the size (in bits) of the RSA public key that's associated with the new certificate request or self-signed certificate. Valid values are:
 
@@ -469,7 +469,7 @@ Accept wildcard characters: False
 
 ### -PrivateKeyExportable
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PrivateKeyExportable parameter specifies whether the certificate has an exportable private key, and controls whether you can export the certificate from the server (and import the certificate on other servers). Valid values are:
 
@@ -516,7 +516,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
 
@@ -541,7 +541,7 @@ Accept wildcard characters: False
 
 ### -Services
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Services parameter specifies the Exchange services that the new self-signed certificate is enabled for. Valid values are:
 
@@ -574,7 +574,7 @@ Accept wildcard characters: False
 
 ### -SubjectKeyIdentifier
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SubjectKeyIdentifier parameter specifies the unique subject key identifier for a newself-signed certificate. For example, run the command: $ski = [System.Guid]::NewGuid().ToString("N"), and use the value $ski for this parameter.
 
@@ -592,7 +592,7 @@ Accept wildcard characters: False
 
 ### -SubjectName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SubjectName parameter specifies the Subject field of the certificate request or self-signed certificate.
 
@@ -626,7 +626,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ExchangeSettings.md b/exchange/exchange-ps/ExchangePowerShell/New-ExchangeSettings.md
index 230a474641..8341371024 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-ExchangeSettings.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-ExchangeSettings.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -46,7 +46,7 @@ This example creates a new Exchange settings object for the Audit configuration
 
 ### -Name
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Name parameter specifies the name of a valid Exchange configuration schema that you want to create an Exchange settings object for. Valid values are
 
@@ -74,7 +74,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -95,7 +95,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -113,7 +113,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -133,7 +133,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-FederationTrust.md b/exchange/exchange-ps/ExchangePowerShell/New-FederationTrust.md
index 15c47b377e..3068107b6d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-FederationTrust.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-FederationTrust.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
 Locale: en-US
@@ -66,7 +66,7 @@ This example creates the federation trust Microsoft Federation Gateway with a ce
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Name parameter specifies a friendly name for the federation trust.
 
@@ -84,7 +84,7 @@ Accept wildcard characters: False
 
 ### -ApplicationUri
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ApplicationUri parameter specifies the primary domain used for the federated organization identifier.
 
@@ -104,7 +104,7 @@ Accept wildcard characters: False
 
 ### -SkipNamespaceProviderProvisioning
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SkipNamespaceProviderProvisioning switch specifies that the trust and federated organization identifier are provisioned externally without using federation functionality in Microsoft Exchange. You don't need to specify a value with this switch.
 
@@ -124,7 +124,7 @@ Accept wildcard characters: False
 
 ### -Thumbprint
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Thumbprint parameter specifies the thumbprint of a certificate issued by a public certification authority (CA) trusted by the Microsoft Federation Gateway. For more details, see [Federation](https://learn.microsoft.com/exchange/federation-exchange-2013-help).
 
@@ -142,7 +142,7 @@ Accept wildcard characters: False
 
 ### -AdministratorProvisioningId
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AdministratorProvisioningId parameter specifies the provisioning key returned by the Microsoft Federation Gateway when an organization has already registered a SiteID or ApplicationID.
 
@@ -162,7 +162,7 @@ Accept wildcard characters: False
 
 ### -ApplicationIdentifier
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ApplicationIdentifier parameter specifies the SiteID or ApplicationID when an organization has already registered a SiteID or ApplicationID.
 
@@ -182,7 +182,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -203,7 +203,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -221,7 +221,7 @@ Accept wildcard characters: False
 
 ### -MetadataUrl
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MetadataUrl parameter specifies the URL where WS-FederationMetadata is published by the Microsoft Federation Gateway.
 
@@ -261,7 +261,7 @@ Accept wildcard characters: False
 
 ### -UseLegacyProvisioningService
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The UseLegacyProvisioningService switch specifies that the legacy interface on the Microsoft Federation Gateway is used for managing the federation trust, including federated domains, certificates, and federation metadata. You don't need to specify a value with this switch.
 
@@ -281,7 +281,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-Fingerprint.md b/exchange/exchange-ps/ExchangePowerShell/New-Fingerprint.md
index 223d295bfa..1e126802d1 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-Fingerprint.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-Fingerprint.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -50,7 +50,7 @@ This example creates a new document fingerprint based on the file C:\\My Documen
 
 ### -FileData
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The FileData parameter specifies the file to use as a document fingerprint.
 
@@ -70,7 +70,7 @@ Accept wildcard characters: False
 
 ### -Description
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Description parameter specifies a description for the document fingerprint.
 
@@ -88,7 +88,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -109,7 +109,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ForeignConnector.md b/exchange/exchange-ps/ExchangePowerShell/New-ForeignConnector.md
index 4dc46016af..7903f6f0e9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-ForeignConnector.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-ForeignConnector.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -55,7 +55,7 @@ This example creates a Foreign connector with the following properties:
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Name parameter specifies the name for the Foreign connector.
 
@@ -73,7 +73,7 @@ Accept wildcard characters: False
 
 ### -AddressSpaces
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AddressSpaces parameter specifies the domain names to which the Foreign connector sends messages. The complete syntax for entering each address space is: `AddressSpaceType:AddressSpace;AddressSpaceCost`.
 
@@ -104,7 +104,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -125,7 +125,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -145,7 +145,7 @@ Accept wildcard characters: False
 
 ### -IsScopedConnector
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IsScopedConnector parameter specifies the availability of the connector to other Mailbox servers. When the value of this parameter is $false, the connector can be used by all Mailbox servers in the Exchange organization. When the value of this parameter is $true, the connector can be used only by Mailbox servers in the same Active Directory site. The default value is $false.
 
@@ -163,7 +163,7 @@ Accept wildcard characters: False
 
 ### -SourceTransportServers
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SourceTransportServers parameter specifies the names of the Mailbox servers that use this Foreign connector. Having a single Foreign connector homed on multiple servers provides fault tolerance and high availability if one of the Mailbox servers fails. The default value of this parameter is the name of the server on which this Foreign connector is first installed.
 
@@ -183,7 +183,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-GlobalAddressList.md b/exchange/exchange-ps/ExchangePowerShell/New-GlobalAddressList.md
index e642369e00..2bdd854f7b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-GlobalAddressList.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-GlobalAddressList.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -92,7 +92,7 @@ This example creates the GAL named GAL\_AgencyB by using the RecipientFilter par
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Name parameter specifies a unique name for the global address list. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -110,7 +110,7 @@ Accept wildcard characters: False
 
 ### -IncludedRecipients
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IncludedRecipients parameter specifies a precanned filter that's based on the recipient type. Valid values are:
 
@@ -139,7 +139,7 @@ Accept wildcard characters: False
 
 ### -RecipientFilter
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RecipientFilter parameter specifies a custom OPATH filter that's based on the value of any available recipient property. You can use any available Windows PowerShell operator, and wildcards and partial matches are supported. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`.
 
@@ -168,7 +168,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCompany
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalCompany parameter specifies a precanned filter that's based on the value of the recipient's Company property. You can specify multiple values separated by commas.
 
@@ -190,7 +190,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute1
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalCustomAttribute1 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute1 property. You can specify multiple values separated by commas.
 
@@ -212,7 +212,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute10
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalCustomAttribute10 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute10 property. You can specify multiple values separated by commas.
 
@@ -234,7 +234,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute11
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalCustomAttribute11 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute11 property. You can specify multiple values separated by commas.
 
@@ -256,7 +256,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute12
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalCustomAttribute12 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute12 property. You can specify multiple values separated by commas.
 
@@ -278,7 +278,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute13
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalCustomAttribute13 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute13 property. You can specify multiple values separated by commas.
 
@@ -300,7 +300,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute14
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalCustomAttribute14 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute14 property. You can specify multiple values separated by commas.
 
@@ -322,7 +322,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute15
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalCustomAttribute15 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute15 property. You can specify multiple values separated by commas.
 
@@ -344,7 +344,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute2
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalCustomAttribute2 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute2 property. You can specify multiple values separated by commas.
 
@@ -366,7 +366,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute3
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalCustomAttribute3 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute3 property. You can specify multiple values separated by commas.
 
@@ -388,7 +388,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute4
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalCustomAttribute4 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute4 property. You can specify multiple values separated by commas.
 
@@ -410,7 +410,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute5
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalCustomAttribute5 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute5 property. You can specify multiple values separated by commas.
 
@@ -432,7 +432,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute6
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalCustomAttribute6 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute6 property. You can specify multiple values separated by commas.
 
@@ -454,7 +454,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute7
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalCustomAttribute7 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute7 property. You can specify multiple values separated by commas.
 
@@ -476,7 +476,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute8
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalCustomAttribute8 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute8 property. You can specify multiple values separated by commas.
 
@@ -498,7 +498,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute9
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalCustomAttribute9 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute9 property. You can specify multiple values separated by commas.
 
@@ -520,7 +520,7 @@ Accept wildcard characters: False
 
 ### -ConditionalDepartment
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalDepartment parameter specifies a precanned filter that's based on the value of the recipient's Department property. You can specify multiple values separated by commas.
 
@@ -542,7 +542,7 @@ Accept wildcard characters: False
 
 ### -ConditionalStateOrProvince
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalStateOrProvince parameter specifies a precanned filter that's based on the value of the recipient's StateOrProvince property. You can specify multiple values separated by commas.
 
@@ -564,7 +564,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -585,7 +585,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -605,7 +605,7 @@ Accept wildcard characters: False
 
 ### -RecipientContainer
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -632,7 +632,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-HybridConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/New-HybridConfiguration.md
index 8ba792670c..2d22f8387f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-HybridConfiguration.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-HybridConfiguration.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -92,7 +92,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -113,7 +113,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -131,7 +131,7 @@ Accept wildcard characters: False
 
 ### -Domains
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Domains parameter specifies the domain namespaces used in the hybrid deployment. These domains must be configured as accepted domains in either on-premises Exchange or Exchange Online. The domains are used in configuring the organization relationships and Send and Receive connectors used by the hybrid configuration.
 
@@ -151,7 +151,7 @@ Accept wildcard characters: False
 
 ### -EdgeTransportServers
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The EdgeTransportServers parameter specifies the Edge Transport servers that are configured to support the hybrid deployment features. The Edge Transport server must be accessible from the internet on port 25. Valid values are:
 
@@ -176,7 +176,7 @@ Accept wildcard characters: False
 
 ### -ExternalIPAddresses
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExternalIPAddresses parameter is a legacy parameter that specifies the publicly accessible inbound IP address of Microsoft Exchange Server 2010 Hub Transport servers.
 
@@ -196,7 +196,7 @@ Accept wildcard characters: False
 
 ### -Features
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Features parameter specifies the features that are enabled for the hybrid configuration. Valid values are:
 
@@ -225,7 +225,7 @@ Accept wildcard characters: False
 
 ### -OnPremisesSmartHost
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The OnPremisesSmartHost parameter specifies the FQDN of the on-premises Exchange Mailbox server used for secure mail transport between on-premises Exchange and Exchange Online.
 
@@ -243,7 +243,7 @@ Accept wildcard characters: False
 
 ### -ReceivingTransportServers
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ReceivingTransportServers parameter specifies the Mailbox servers defined in the outbound connector configuration in Exchange Online. Valid values are:
 
@@ -290,7 +290,7 @@ Accept wildcard characters: False
 
 ### -SendingTransportServers
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SendingTransportServers parameter specifies the Mailbox servers defined in the inbound connector configuration in Exchange Online. Valid values are:
 
@@ -317,7 +317,7 @@ Accept wildcard characters: False
 
 ### -ServiceInstance
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is meaningful only in Office 365 operated by 21Vianet in China.
 
@@ -339,7 +339,7 @@ Accept wildcard characters: False
 
 ### -TlsCertificateName
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TlsCertificateName parameter specifies the X.509 certificate to use for TLS encryption. Valid syntax for this parameter is `"<I>X.500Issuer<S>X.500Subject"`:
 
@@ -388,7 +388,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-InboxRule.md b/exchange/exchange-ps/ExchangePowerShell/New-InboxRule.md
index 7afb9dee03..435d789401 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-InboxRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-InboxRule.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -132,7 +132,7 @@ This example raises the message importance to High if the mailbox owner is in th
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Name parameter specifies the name of the Inbox rule. The maximum length is 512 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -150,7 +150,7 @@ Accept wildcard characters: False
 
 ### -FromMessageId
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The FromMessageId parameter specifies the message that's used to create the Inbox rule. The rule is based on the properties of the message. You identify the message by its Base64-encoded StoreObjectId property value. For example:
 
@@ -177,7 +177,7 @@ Accept wildcard characters: False
 
 ### -ValidateOnly
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ValidateOnly switch specifies whether to evaluate the potential success or failure of the command without making changes. You don't need to specify a value with this switch.
 
@@ -195,7 +195,7 @@ Accept wildcard characters: False
 
 ### -AlwaysDeleteOutlookRulesBlob
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AlwaysDeleteOutlookRulesBlob switch hides a warning message when you use Outlook on the web (formerly known as Outlook Web App) or Exchange PowerShell to modify Inbox rules. You don't need to specify a value with this switch.
 
@@ -213,7 +213,7 @@ Accept wildcard characters: False
 
 ### -ApplyCategory
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ApplyCategory parameter specifies an action for the Inbox rule that applies the specified category to messages. A valid value is any text value that you want to define as a category. You can specify multiple categories separated by commas. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -233,7 +233,7 @@ Accept wildcard characters: False
 
 ### -ApplySystemCategory
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ApplySystemCategory parameter specifies an action for the Inbox rule that applies the specified system category to messages. System categories are available to all mailboxes in the organization. Valid values are:
 
@@ -278,7 +278,7 @@ Accept wildcard characters: False
 
 ### -BodyContainsWords
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The BodyContainsWords parameter specifies a condition for the Inbox rule that looks for the specified words or phrases in the body of messages.
 
@@ -302,7 +302,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -323,7 +323,7 @@ Accept wildcard characters: False
 
 ### -CopyToFolder
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The CopyToFolder parameter specifies an action for the Inbox rule that copies messages to the specified mailbox folder. The syntax is `MailboxID:\ParentFolder[\SubFolder]`.
 
@@ -356,7 +356,7 @@ Accept wildcard characters: False
 
 ### -DeleteMessage
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DeleteMessage parameter specifies an action for the Inbox rule that sends messages to the Deleted Items folder. Valid values are:
 
@@ -377,7 +377,7 @@ Accept wildcard characters: False
 
 ### -DeleteSystemCategory
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DeleteSystemCategory parameter specifies an action for the Inbox rule that deletes the specified system category from messages. System categories are available to all mailboxes in the organization. Valid values are:
 
@@ -422,7 +422,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -442,7 +442,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfBodyContainsWords
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ExceptIfBodyContainsWords parameter specifies an exception for the Inbox rule that looks for the specified words or phrases in the body of messages.
 
@@ -466,7 +466,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfFlaggedForAction
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ExceptIfFlaggedForAction parameter specifies an exception for the Inbox rule that looks messages with the specified message flag. Valid values are:
 
@@ -498,7 +498,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfFrom
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ExceptIfFrom parameter specifies an exception for the Inbox rule that looks for the specified sender in messages. You can use any value that uniquely identifies the sender. For example:
 
@@ -527,7 +527,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfFromAddressContainsWords
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ExceptIfFromAddressContainsWords parameter specifies an exception for the Inbox rule that looks for messages where the specified words are in the sender's email address.
 
@@ -551,7 +551,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfHasAttachment
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ExceptIfHasAttachment parameter specifies an exception for the Inbox rule that looks for messages with attachments. Valid values are:
 
@@ -574,7 +574,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfHasClassification
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ExceptIfHasClassification parameter specifies an exception for the Inbox rule that looks for messages with the specified message classification. You can find message classifications by using the Get-MessageClassification cmdlet. You can specify multiple message classifications separated by commas.
 
@@ -594,7 +594,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfHeaderContainsWords
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The HeaderContainsWords parameter specifies an exception for the Inbox rule that looks for the specified words or phrases in the header fields of messages.
 
@@ -618,7 +618,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfMessageTypeMatches
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ExceptIfMessageTypeMatches parameter specifies an exception for the Inbox rule that looks for messages of the specified type. Valid values are:
 
@@ -650,7 +650,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfMyNameInCcBox
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ExceptIfMyNameInCcBox parameter specifies an exception for the Inbox rule that looks for messages where the mailbox owner is in the Cc field. Valid values are:
 
@@ -673,7 +673,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfMyNameInToBox
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ExceptIfMyNameInToBox parameter specifies an exception for the Inbox rule that looks for messages where the mailbox owner is in the To field. Valid values are:
 
@@ -696,7 +696,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfMyNameInToOrCcBox
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ExceptIfMyNameInToOrCcBox parameter specifies an exception for the Inbox rule that looks for messages where the mailbox owner is in the To or Cc fields Valid values are.
 
@@ -719,7 +719,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfMyNameNotInToBox
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ExceptIfMyNameNotInToBox parameter specifies an exception for the Inbox rule that looks for messages where the mailbox owner isn't in the To field. Valid values are:
 
@@ -742,7 +742,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfReceivedAfterDate
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ExceptIfReceivedAfterDate parameter specifies an exception for the Inbox rule that looks for messages received after the specified date.
 
@@ -764,7 +764,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfReceivedBeforeDate
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ExceptIfReceivedBeforeDate parameter specifies an exception for the Inbox rule that looks for messages received before the specified date.
 
@@ -786,7 +786,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfRecipientAddressContainsWords
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ExceptIfRecipientAddressContainsWords parameter specifies an exception for the Inbox rule that looks for messages where the specified words are in recipient email addresses.
 
@@ -808,7 +808,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfSentOnlyToMe
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ExceptIfSentOnlyToMe parameter specifies an exception for the Inbox rule that looks for messages where the only recipient is the mailbox owner. Valid values are:
 
@@ -831,7 +831,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfSentTo
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ExceptIfSentTo parameter specifies an exception that looks for recipients in messages. You can use any value that uniquely identifies the recipient. For example:
 
@@ -860,7 +860,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfSubjectContainsWords
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ExceptIfSubjectContainsWords parameter specifies an exception for the Inbox rule that looks for the specified words or phrases in the Subject field of messages.
 
@@ -884,7 +884,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfSubjectOrBodyContainsWords
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ExceptIfSubjectOrBodyContainsWords parameter specifies an exception for the Inbox rule that looks for the specified words or phrases in the Subject field or body of messages.
 
@@ -908,7 +908,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfWithImportance
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ExceptIfWithImportance parameter specifies an exception for the Inbox rule that looks for messages with the specified importance level. Valid values are:
 
@@ -932,7 +932,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfWithinSizeRangeMaximum
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ExceptIfWithinSizeRangeMaximum parameter specifies part of an exception for the Inbox rule that looks for messages that smaller than specified maximum size.
 
@@ -964,7 +964,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfWithinSizeRangeMinimum
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ExceptIfWithinSizeRangeMinimum parameter specifies part of an exception for the Inbox rule that looks for messages that are larger than the specified minimum size.
 
@@ -996,7 +996,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfWithSensitivity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ExceptIfWithSensitivity parameter specifies an exception for the Inbox rule that looks for messages with the specified sensitivity level. Valid values are:
 
@@ -1021,7 +1021,7 @@ Accept wildcard characters: False
 
 ### -FlaggedForAction
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The FlaggedForAction parameter specifies a condition for the Inbox rule that looks for messages with the specified message flag. Valid values are:
 
@@ -1051,7 +1051,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -1071,7 +1071,7 @@ Accept wildcard characters: False
 
 ### -ForwardAsAttachmentTo
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ForwardAsAttachmentTo parameter specifies an action for the Inbox rule that forwards the message to the specified recipient as an attachment. You can use any value that uniquely identifies the recipient. For example:
 
@@ -1098,7 +1098,7 @@ Accept wildcard characters: False
 
 ### -ForwardTo
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ForwardTo parameter specifies an action for the Inbox rule that forwards the message to the specified recipient. You can use any value that uniquely identifies the recipient. For example:
 
@@ -1125,7 +1125,7 @@ Accept wildcard characters: False
 
 ### -From
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The From parameter specifies a condition for the Inbox rule that looks for the specified sender in messages. You can use any value that uniquely identifies the sender. For example:
 
@@ -1154,7 +1154,7 @@ Accept wildcard characters: False
 
 ### -FromAddressContainsWords
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The FromAddressContainsWords parameter specifies a condition for the Inbox rule that looks for messages where the specified words are in the sender's email address.
 
@@ -1178,7 +1178,7 @@ Accept wildcard characters: False
 
 ### -HasAttachment
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The HasAttachment parameter specifies a condition for the Inbox rule that looks for messages with attachments. Valid values are:
 
@@ -1201,7 +1201,7 @@ Accept wildcard characters: False
 
 ### -HasClassification
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The HasClassification parameter specifies a condition for the Inbox rule that looks for messages with the specified message classification. You can find message classifications by using the Get-MessageClassification cmdlet. You can specify multiple message classifications separated by commas.
 
@@ -1221,7 +1221,7 @@ Accept wildcard characters: False
 
 ### -HeaderContainsWords
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The HeaderContainsWords parameter specifies a condition for the Inbox rule that looks for the specified words or phrases in the header fields of messages.
 
@@ -1245,7 +1245,7 @@ Accept wildcard characters: False
 
 ### -Mailbox
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Mailbox parameter specifies the mailbox that contains the Inbox rule. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -1274,7 +1274,7 @@ Accept wildcard characters: False
 
 ### -MarkAsRead
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MarkAsRead parameter specifies an action for the Inbox rule that marks messages as read. Valid values are:
 
@@ -1295,7 +1295,7 @@ Accept wildcard characters: False
 
 ### -MarkImportance
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MarkImportance parameter specifies an action for the Inbox rule that marks messages with the specified importance flag. Valid values are:
 
@@ -1317,7 +1317,7 @@ Accept wildcard characters: False
 
 ### -MessageTypeMatches
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MessageTypeMatches parameter specifies a condition for the Inbox rule that looks for messages of the specified type. Valid values are:
 
@@ -1349,7 +1349,7 @@ Accept wildcard characters: False
 
 ### -MoveToFolder
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MoveToFolder parameter specifies an action for the Inbox rule that moves messages to the specified mailbox folder. The syntax is `MailboxID:\ParentFolder[\SubFolder]`.
 
@@ -1382,7 +1382,7 @@ Accept wildcard characters: False
 
 ### -MyNameInCcBox
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MyNameInCcBox parameter specifies a condition for the Inbox rule that looks for messages where the mailbox owner is in the Cc field. Valid values are:
 
@@ -1405,7 +1405,7 @@ Accept wildcard characters: False
 
 ### -MyNameInToBox
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MyNameInToBox parameter specifies a condition for the Inbox rule that looks for messages where the mailbox owner is in the To field. Valid values are:
 
@@ -1428,7 +1428,7 @@ Accept wildcard characters: False
 
 ### -MyNameInToOrCcBox
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MyNameInToOrCcBox parameter specifies a condition for the Inbox rule that looks for messages where the mailbox owner is in the To or Cc fields Valid values are.
 
@@ -1451,7 +1451,7 @@ Accept wildcard characters: False
 
 ### -MyNameNotInToBox
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MyNameNotInToBox parameter specifies a condition for the Inbox rule that looks for messages where the mailbox owner isn't in the To field. Valid values are:
 
@@ -1474,7 +1474,7 @@ Accept wildcard characters: False
 
 ### -PinMessage
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The PinMessage parameter specifies an action for the Inbox rule that pins messages to the top of the Inbox. Valid values are:
 
@@ -1495,7 +1495,7 @@ Accept wildcard characters: False
 
 ### -Priority
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Priority parameter specifies a priority for the Inbox rule that determines the order of rule processing. A lower integer value indicates a higher priority,
 
@@ -1513,7 +1513,7 @@ Accept wildcard characters: False
 
 ### -ReceivedAfterDate
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ReceivedAfterDate parameter specifies a condition for the Inbox rule that looks for messages received after the specified date.
 
@@ -1535,7 +1535,7 @@ Accept wildcard characters: False
 
 ### -ReceivedBeforeDate
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ReceivedBeforeDate parameter specifies a condition for the Inbox rule that looks for messages received before the specified date.
 
@@ -1557,7 +1557,7 @@ Accept wildcard characters: False
 
 ### -RecipientAddressContainsWords
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RecipientAddressContainsWords parameter specifies a condition for the Inbox rule that looks for messages where the specified words are in recipient email addresses.
 
@@ -1579,7 +1579,7 @@ Accept wildcard characters: False
 
 ### -RedirectTo
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RedirectTo parameter specifies an action for the Inbox rule that redirects the message to the specified recipient. You can use any value that uniquely identifies the recipient. For example:
 
@@ -1606,7 +1606,7 @@ Accept wildcard characters: False
 
 ### -SendTextMessageNotificationTo
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1628,7 +1628,7 @@ Accept wildcard characters: False
 
 ### -SentOnlyToMe
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SentOnlyToMe parameter specifies a condition for the Inbox rule that looks for messages where the only recipient is the mailbox owner. Valid values are:
 
@@ -1651,7 +1651,7 @@ Accept wildcard characters: False
 
 ### -SentTo
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SentTo parameter specifies a condition for the Inbox rule that looks for messages with the specified recipients. You can use any value that uniquely identifies the recipient. For example:
 
@@ -1700,7 +1700,7 @@ Accept wildcard characters: False
 
 ### -StopProcessingRules
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The StopProcessingRules parameter specifies an action for the Inbox rule that stops processing additional rules if the conditions of this Inbox rule are met. Valid values are:If set to $true, the StopProcessingRules parameter instructs Exchange to stop processing additional rules if the conditions of this Inbox rule are met.
 
@@ -1721,7 +1721,7 @@ Accept wildcard characters: False
 
 ### -SubjectContainsWords
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SubjectContainsWords parameter specifies a condition for the Inbox rule that looks for the specified words or phrases in the Subject field of messages.
 
@@ -1745,7 +1745,7 @@ Accept wildcard characters: False
 
 ### -SubjectOrBodyContainsWords
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SubjectOrBodyContainsWords parameter specifies a condition for the Inbox rule that looks for the specified words or phrases in the Subject field or body of messages.
 
@@ -1769,7 +1769,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
@@ -1787,7 +1787,7 @@ Accept wildcard characters: False
 
 ### -WithImportance
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WithImportance parameter specifies a condition for the Inbox rule that looks for messages with the specified importance level. Valid values are:
 
@@ -1811,7 +1811,7 @@ Accept wildcard characters: False
 
 ### -WithinSizeRangeMaximum
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WithinSizeRangeMaximum parameter specifies part of a condition for the Inbox rule that looks for messages that are smaller than specified maximum size.
 
@@ -1843,7 +1843,7 @@ Accept wildcard characters: False
 
 ### -WithinSizeRangeMinimum
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WithinSizeRangeMinimum parameter specifies part of a condition for the Inbox rule that looks for messages that are larger than the specified minimum size.
 
@@ -1875,7 +1875,7 @@ Accept wildcard characters: False
 
 ### -WithSensitivity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WithSensitivity parameter specifies a condition for the Inbox rule that looks for messages with the specified sensitivity level. Valid values are:
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-IntraOrganizationConnector.md b/exchange/exchange-ps/ExchangePowerShell/New-IntraOrganizationConnector.md
index 69e235ceee..20404af3e4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-IntraOrganizationConnector.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-IntraOrganizationConnector.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
 Locale: en-US
@@ -51,7 +51,7 @@ This example creates an Intra-Organization connector named "MainCloudConnector"
 
 ### -Name
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Name parameter specifies a friendly name for the Intra-Organization connector. If the value contains spaces, enclose the value in double quotation marks.
 
@@ -69,7 +69,7 @@ Accept wildcard characters: False
 
 ### -DiscoveryEndpoint
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DiscoveryEndpoint parameter specifies the externally-accessible URL that's used for the Autodiscover service for the domain that's configured in the Intra-Organization connector.
 
@@ -87,7 +87,7 @@ Accept wildcard characters: False
 
 ### -TargetAddressDomains
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The TargetAddressDomains parameter specifies the domain namespaces to use in the Intra-organization connector. These domains must have valid Autodiscover endpoints defined in their organizations. The domains and their associated Autodiscover endpoints are used by the Intra-Organization connector for feature and service connectivity.
 
@@ -107,7 +107,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -128,7 +128,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -148,7 +148,7 @@ Accept wildcard characters: False
 
 ### -Enabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Enabled parameter enables or disabled the Intra-organization connector. The valid values for this parameter are $true or $false. The default value is $true.
 
@@ -188,7 +188,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-JournalRule.md b/exchange/exchange-ps/ExchangePowerShell/New-JournalRule.md
index 97291cdb9b..86bcf47960 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-JournalRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-JournalRule.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailControl-Help.xml
 Locale: en-US
@@ -52,7 +52,7 @@ This example creates and enables a journal rule. The rule applies to all email m
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Name parameter specifies the name of the journal rule. The name of the rule can be up to 64 characters long.
 
@@ -70,7 +70,7 @@ Accept wildcard characters: False
 
 ### -JournalEmailAddress
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The JournalEmailAddress parameter specifies a recipient object to which journal reports are sent. You can use any value that uniquely identifies the recipient. For example:
 
@@ -95,7 +95,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -116,7 +116,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -136,7 +136,7 @@ Accept wildcard characters: False
 
 ### -Enabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Enabled parameter specifies whether the journal rule is enabled or disabled. If the rule is disabled, it isn't applied to any email messages. The default value is $false.
 
@@ -154,7 +154,7 @@ Accept wildcard characters: False
 
 ### -Recipient
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Recipient parameter specifies the SMTP address of a mailbox, contact, or distribution group to journal. If you specify a distribution group, all recipients in that distribution group are journaled. All messages sent to or from a recipient are journaled.
 
@@ -174,7 +174,7 @@ Accept wildcard characters: False
 
 ### -Scope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Scope parameter specifies the scope of email messages to which the journal rule is applied. Valid values for this parameter are as follows:
 
@@ -196,7 +196,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MailContact.md b/exchange/exchange-ps/ExchangePowerShell/New-MailContact.md
index 38a1dafa95..e6db45960c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-MailContact.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-MailContact.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -60,7 +60,7 @@ This example creates a new mail contact named Chris Ashton.
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Name parameter specifies the unique name of the mail contact. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -80,7 +80,7 @@ Accept wildcard characters: False
 
 ### -ExternalEmailAddress
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ExternalEmailAddress parameter specifies the target email address of the mail contact or mail user. By default, this value is used as the primary email address of the mail contact or mail user.
 
@@ -100,7 +100,7 @@ Accept wildcard characters: False
 
 ### -Alias
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Alias parameter specifies the Exchange alias (also known as the mail nickname) for the recipient. This value identifies the recipient as a mail-enabled object, and shouldn't be confused with multiple email addresses for the same recipient (also known as proxy addresses). A recipient can have only one Alias value. The maximum length is 64 characters.
 
@@ -136,7 +136,7 @@ Accept wildcard characters: False
 
 ### -ArbitrationMailbox
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -167,7 +167,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -188,7 +188,7 @@ Accept wildcard characters: False
 
 ### -DisplayName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The DisplayName parameter specifies the display name of the mail contact. The display name is visible in the Exchange admin center and in address lists. The maximum length is 256 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -208,7 +208,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -228,7 +228,7 @@ Accept wildcard characters: False
 
 ### -FirstName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The FirstName parameter specifies the user's first name.
 
@@ -246,7 +246,7 @@ Accept wildcard characters: False
 
 ### -Initials
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Initials parameter specifies the user's middle initials.
 
@@ -264,7 +264,7 @@ Accept wildcard characters: False
 
 ### -LastName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The LastName parameter specifies the user's last name.
 
@@ -282,7 +282,7 @@ Accept wildcard characters: False
 
 ### -MacAttachmentFormat
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The MacAttachmentFormat parameter specifies the Apple Macintosh operating system attachment format to use for messages sent to the mail contact or mail user. Valid values are:
 
@@ -310,7 +310,7 @@ Accept wildcard characters: False
 
 ### -MessageBodyFormat
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The MessageBodyFormat parameter specifies the message body format for messages sent to the mail contact or mail user. Valid values are:
 
@@ -337,7 +337,7 @@ Accept wildcard characters: False
 
 ### -MessageFormat
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The MessageBodyFormat parameter specifies the message body format for messages sent to the mail contact or mail user. Valid values are:
 
@@ -364,7 +364,7 @@ Accept wildcard characters: False
 
 ### -ModeratedBy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ModeratedBy parameter specifies one or more moderators for this mail contact. A moderator approves messages sent to the mail contact before the messages are delivered. A moderator must be a mailbox, mail user, or mail contact in your organization. You can use any value that uniquely identifies the moderator. For example:
 
@@ -393,7 +393,7 @@ Accept wildcard characters: False
 
 ### -ModerationEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ModerationEnabled parameter specifies whether moderation is enabled for this recipient. Valid value are:
 
@@ -416,7 +416,7 @@ Accept wildcard characters: False
 
 ### -OrganizationalUnit
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The OrganizationalUnit parameter specifies the location in Active Directory where the new contact is created.
 
@@ -441,7 +441,7 @@ Accept wildcard characters: False
 
 ### -PrimarySmtpAddress
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -465,7 +465,7 @@ Accept wildcard characters: False
 
 ### -SendModerationNotifications
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The SendModerationNotifications parameter specifies when moderation notification messages are sent. Valid values are:
 
@@ -489,7 +489,7 @@ Accept wildcard characters: False
 
 ### -UsePreferMessageFormat
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The UsePreferMessageFormat specifies whether the message format settings configured for the mail user or mail contact override the global settings configured for the remote domain or configured by the message sender. Valid value are:
 
@@ -510,7 +510,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MailMessage.md b/exchange/exchange-ps/ExchangePowerShell/New-MailMessage.md
index a2f50ad71e..c27f6e123b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-MailMessage.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-MailMessage.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -85,7 +85,7 @@ This example creates an email message in the Drafts folder with the subject and
 
 ### -Body
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Body parameter specifies the content of the body section of the new email message.
 
@@ -103,7 +103,7 @@ Accept wildcard characters: False
 
 ### -BodyFormat
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The BodyFormat parameter specifies the format of the message body. The values can be PlainText, Rtf (Rich Text Format), or Html. By default, if the BodyFormat parameter isn't specified when the Body parameter is used, the message body is rendered in plain text.
 
@@ -121,7 +121,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -142,7 +142,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -162,7 +162,7 @@ Accept wildcard characters: False
 
 ### -Subject
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Subject parameter specifies the content of the subject field of the new email message.
 
@@ -180,7 +180,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MailUser.md b/exchange/exchange-ps/ExchangePowerShell/New-MailUser.md
index 3aa57b37d4..5f25229c09 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-MailUser.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-MailUser.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -236,7 +236,7 @@ This example creates a new mail user for Ed Meadows in the contoso.com cloud-bas
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Name parameter specifies the unique name of the mail user. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -256,7 +256,7 @@ Accept wildcard characters: False
 
 ### -ExternalEmailAddress
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ExternalEmailAddress parameter specifies the target email address of the mail contact or mail user. By default, this value is used as the primary email address of the mail contact or mail user.
 
@@ -314,7 +314,7 @@ Accept wildcard characters: False
 
 ### -Password
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Password parameter specifies the password for the user's account.
 
@@ -338,7 +338,7 @@ Accept wildcard characters: False
 
 ### -UserPrincipalName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -358,7 +358,7 @@ Accept wildcard characters: False
 
 ### -Alias
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Alias parameter specifies the Exchange alias (also known as the mail nickname) for the recipient. This value identifies the recipient as a mail-enabled object, and shouldn't be confused with multiple email addresses for the same recipient (also known as proxy addresses). A recipient can have only one Alias value. The maximum length is 64 characters.
 
@@ -394,7 +394,7 @@ Accept wildcard characters: False
 
 ### -ArbitrationMailbox
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -425,7 +425,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -446,7 +446,7 @@ Accept wildcard characters: False
 
 ### -DisplayName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The DisplayName parameter specifies the display name of the mail user. The display name is visible in the Exchange admin center, in address lists, and in Outlook. The maximum length is 256 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -466,7 +466,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -486,7 +486,7 @@ Accept wildcard characters: False
 
 ### -FirstName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The FirstName parameter specifies the user's first name.
 
@@ -504,7 +504,7 @@ Accept wildcard characters: False
 
 ### -ImmutableId
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ImmutableId parameter is used by GAL synchronization (GALSync) and specifies a unique and immutable identifier in the form of an SMTP address for an Exchange mailbox used for federated delegation when requesting Security Assertion Markup Language (SAML) tokens. If federation is configured for this mailbox and you don't set this parameter when you create the mailbox, Exchange creates the value for the immutable ID based upon the mailbox's ExchangeGUID and the federated account namespace, for example, 7a78e7c8-620e-4d85-99d3-c90d90f29699@mail.contoso.com.
 
@@ -524,7 +524,7 @@ Accept wildcard characters: False
 
 ### -Initials
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Initials parameter specifies the user's middle initials.
 
@@ -542,7 +542,7 @@ Accept wildcard characters: False
 
 ### -LastName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The LastName parameter specifies the user's last name.
 
@@ -600,7 +600,7 @@ Accept wildcard characters: False
 
 ### -MacAttachmentFormat
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The MacAttachmentFormat parameter specifies the Apple Macintosh operating system attachment format to use for messages sent to the mail contact or mail user. Valid values are:
 
@@ -648,7 +648,7 @@ Accept wildcard characters: False
 
 ### -MessageBodyFormat
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The MessageBodyFormat parameter specifies the message body format for messages sent to the mail contact or mail user. Valid values are:
 
@@ -675,7 +675,7 @@ Accept wildcard characters: False
 
 ### -MessageFormat
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The MessageFormat parameter specifies the message format for messages sent to the mail contact or mail user. Valid values are:
 
@@ -703,7 +703,7 @@ Accept wildcard characters: False
 
 ### -ModeratedBy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ModeratedBy parameter specifies one or more moderators for this recipient. A moderator approves messages sent to the recipient before the messages are delivered. A moderator must be a mailbox, mail user, or mail contact in your organization. You can use any value that uniquely identifies the moderator. For example:
 
@@ -732,7 +732,7 @@ Accept wildcard characters: False
 
 ### -ModerationEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ModerationEnabled parameter specifies whether moderation is enabled for this recipient. Valid value are:
 
@@ -755,7 +755,7 @@ Accept wildcard characters: False
 
 ### -OrganizationalUnit
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The OrganizationalUnit parameter specifies the location in Active Directory where the new mail user is created.
 
@@ -780,7 +780,7 @@ Accept wildcard characters: False
 
 ### -PrimarySmtpAddress
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter is functional only in on-premises Exchange.
 
@@ -804,7 +804,7 @@ Accept wildcard characters: False
 
 ### -RemotePowerShellEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The RemotePowerShellEnabled parameter specifies whether the user has access to Exchange PowerShell. Valid values are:
 
@@ -829,7 +829,7 @@ Accept wildcard characters: False
 
 ### -ResetPasswordOnNextLogon
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -852,7 +852,7 @@ Accept wildcard characters: False
 
 ### -SamAccountName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -872,7 +872,7 @@ Accept wildcard characters: False
 
 ### -SendModerationNotifications
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The SendModerationNotifications parameter specifies when moderation notification messages are sent. Valid values are:
 
@@ -896,7 +896,7 @@ Accept wildcard characters: False
 
 ### -UsePreferMessageFormat
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The UsePreferMessageFormat specifies whether the message format settings configured for the mail user or mail contact override the global settings configured for the remote domain or configured by the message sender. Valid value are:
 
@@ -917,7 +917,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-Mailbox.md b/exchange/exchange-ps/ExchangePowerShell/New-Mailbox.md
index 28c5437879..a8af131a6d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-Mailbox.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-Mailbox.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -810,7 +810,7 @@ This example assumes that you've already created a mail-enabled security group n
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Name parameter specifies the unique name of the mailbox. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -830,7 +830,7 @@ Accept wildcard characters: False
 
 ### -AccountDisabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -852,7 +852,7 @@ Accept wildcard characters: False
 
 ### -Arbitration
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -876,7 +876,7 @@ Accept wildcard characters: False
 
 ### -ArchiveDomain
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -898,7 +898,7 @@ Accept wildcard characters: False
 
 ### -Discovery
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Discovery switch is required to create Discovery mailboxes. You don't need to specify a value with this switch.
 
@@ -918,7 +918,7 @@ Accept wildcard characters: False
 
 ### -EnableRoomMailboxAccount
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is functional only in on-premises Exchange.
 
@@ -947,7 +947,7 @@ Accept wildcard characters: False
 
 ### -Equipment
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Equipment switch is required to create equipment mailboxes. You don't need to specify a value with this switch.
 
@@ -1007,7 +1007,7 @@ Accept wildcard characters: False
 
 ### -LinkedDomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1029,7 +1029,7 @@ Accept wildcard characters: False
 
 ### -LinkedMasterAccount
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1054,7 +1054,7 @@ Accept wildcard characters: False
 
 ### -LinkedRoom
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1096,7 +1096,7 @@ Accept wildcard characters: False
 
 ### -Migration
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Migration switch is required to create migration mailboxes. You don't need to specify a value with this switch.
 
@@ -1114,7 +1114,7 @@ Accept wildcard characters: False
 
 ### -Password
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Password parameter specifies the password for the mailbox (the user account that's associated with the mailbox). This parameter isn't required if you're creating a linked mailbox, resource mailbox, or shared mailbox, because the associated user accounts are disabled for these types of mailboxes.
 
@@ -1138,7 +1138,7 @@ Accept wildcard characters: False
 
 ### -PublicFolder
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The PublicFolder switch is required to create public folder mailboxes. You don't need to specify a value with this switch.
 
@@ -1180,7 +1180,7 @@ Accept wildcard characters: False
 
 ### -Room
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Room switch is required to create room mailboxes. You don't need to specify a value with this switch.
 
@@ -1204,7 +1204,7 @@ Accept wildcard characters: False
 
 ### -Shared
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Shared switch is required to create shared mailboxes. You don't need to specify a value with this switch.
 
@@ -1224,7 +1224,7 @@ Accept wildcard characters: False
 
 ### -UserPrincipalName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1246,7 +1246,7 @@ Accept wildcard characters: False
 
 ### -ActiveSyncMailboxPolicy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ActiveSyncMailboxPolicy parameter specifies the mobile device mailbox policy that's applied to the mailbox. You can use any value that uniquely identifies the policy. For example:.
 
@@ -1270,7 +1270,7 @@ Accept wildcard characters: False
 
 ### -AddressBookPolicy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1296,7 +1296,7 @@ Accept wildcard characters: False
 
 ### -Alias
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Alias parameter specifies the Exchange alias (also known as the mail nickname) for the recipient. This value identifies the recipient as a mail-enabled object, and shouldn't be confused with multiple email addresses for the same recipient (also known as proxy addresses). A recipient can have only one Alias value. The maximum length is 64 characters.
 
@@ -1332,7 +1332,7 @@ Accept wildcard characters: False
 
 ### -ArbitrationMailbox
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1363,7 +1363,7 @@ Accept wildcard characters: False
 
 ### -Archive
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Archive switch specifies that an archive mailbox is created for this mailbox. You don't need to specify a value with this switch.
 
@@ -1381,7 +1381,7 @@ Accept wildcard characters: False
 
 ### -ArchiveDatabase
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1405,7 +1405,7 @@ Accept wildcard characters: False
 
 ### -AuditLog
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1429,7 +1429,7 @@ Accept wildcard characters: False
 
 ### -AuxAuditLog
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1453,7 +1453,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -1474,7 +1474,7 @@ Accept wildcard characters: False
 
 ### -Database
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1500,7 +1500,7 @@ Accept wildcard characters: False
 
 ### -DisplayName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DisplayName parameter specifies the display name of the mailbox. The display name is visible in the Exchange admin center, in address lists, and in Outlook. The maximum length is 256 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -1520,7 +1520,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1540,7 +1540,7 @@ Accept wildcard characters: False
 
 ### -FirstName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The FirstName parameter specifies the user's first name.
 
@@ -1558,7 +1558,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -1578,7 +1578,7 @@ Accept wildcard characters: False
 
 ### -HoldForMigration
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The HoldForMigration switch specifies whether to prevent any client or user, except the Microsoft Exchange Mailbox Replication service (MRS) process, from logging on to a public folder mailbox. You don't need to specify a value with this switch.
 
@@ -1600,7 +1600,7 @@ Accept wildcard characters: False
 
 ### -ImmutableId
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ImmutableId parameter is used by GAL synchronization (GALSync) and specifies a unique and immutable identifier in the form of an SMTP address for an Exchange mailbox used for federated delegation when requesting Security Assertion Markup Language (SAML) tokens. If federation is configured for this mailbox and you don't set this parameter when you create the mailbox, Exchange creates the value for the immutable ID based upon the mailbox's ExchangeGUID and the federated account namespace, for example, 7a78e7c8-620e-4d85-99d3-c90d90f29699@mail.contoso.com.
 
@@ -1620,7 +1620,7 @@ Accept wildcard characters: False
 
 ### -Initials
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Initials parameter specifies the user's middle initials.
 
@@ -1638,7 +1638,7 @@ Accept wildcard characters: False
 
 ### -IsExcludedFromServingHierarchy
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IsExcludedFromServingHierarchy parameter prevents users from accessing the public folder hierarchy on this public folder mailbox. For load-balancing purposes, users are equally distributed across public folder mailboxes by default. When this parameter is set on a public folder mailbox, that mailbox isn't included in this automatic load-balancing and can't be accessed by users to retrieve the public folder hierarchy. However, if an administrator has set the DefaultPublicFolderMailbox property on a user mailbox to a specific public folder mailbox, the user can still access the specified public folder mailbox, even if the IsExcludedFromServingHierarchy parameter is set for that public folder mailbox.
 
@@ -1656,7 +1656,7 @@ Accept wildcard characters: False
 
 ### -LastName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The LastName parameter specifies the user's last name.
 
@@ -1674,7 +1674,7 @@ Accept wildcard characters: False
 
 ### -LinkedCredential
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1794,7 +1794,7 @@ Accept wildcard characters: False
 
 ### -ModeratedBy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ModeratedBy parameter specifies one or more moderators for this recipient. A moderator approves messages sent to the recipient before the messages are delivered. A moderator must be a mailbox, mail user, or mail contact in your organization. You can use any value that uniquely identifies the moderator. For example:
 
@@ -1823,7 +1823,7 @@ Accept wildcard characters: False
 
 ### -ModerationEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ModerationEnabled parameter specifies whether moderation is enabled for this recipient. Valid value are:
 
@@ -1846,7 +1846,7 @@ Accept wildcard characters: False
 
 ### -Office
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Office parameter specifies the user's physical office name or number.
 
@@ -1864,7 +1864,7 @@ Accept wildcard characters: False
 
 ### -OrganizationalUnit
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The OrganizationalUnit parameter specifies the location in Active Directory where the new mailbox is created.
 
@@ -1889,7 +1889,7 @@ Accept wildcard characters: False
 
 ### -Phone
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Phone parameter specifies the user's telephone number.
 
@@ -1907,7 +1907,7 @@ Accept wildcard characters: False
 
 ### -PrimarySmtpAddress
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The PrimarySmtpAddress parameter specifies the primary return email address that's used for the recipient.
 
@@ -1947,7 +1947,7 @@ Accept wildcard characters: False
 
 ### -RemoteArchive
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1967,7 +1967,7 @@ Accept wildcard characters: False
 
 ### -RemotePowerShellEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RemotePowerShellEnabled parameter specifies whether the user has access to Exchange PowerShell. Valid values are:
 
@@ -1992,7 +1992,7 @@ Accept wildcard characters: False
 
 ### -ResetPasswordOnNextLogon
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ResetPasswordOnNextLogon parameter specifies whether the user is required to change their password the next time they log on to their mailbox. Valid values are:
 
@@ -2013,7 +2013,7 @@ Accept wildcard characters: False
 
 ### -ResourceCapacity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ResourceCapacity parameter specifies the capacity of the resource mailbox. For example, you can use this parameter to identify the number of seats in a conference room (room mailbox) or in a vehicle (equipment mailbox). A valid value is an integer.
 
@@ -2031,7 +2031,7 @@ Accept wildcard characters: False
 
 ### -RetentionPolicy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -2061,7 +2061,7 @@ Accept wildcard characters: False
 
 ### -RoleAssignmentPolicy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RoleAssignmentPolicy parameter specifies the role assignment policy that's applied to the mailbox. You can use any value that uniquely identifies the role assignment policy. For example:
 
@@ -2087,7 +2087,7 @@ Accept wildcard characters: False
 
 ### -RoomMailboxPassword
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is functional only in on-premises Exchange.
 
@@ -2123,7 +2123,7 @@ Accept wildcard characters: False
 
 ### -SamAccountName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -2143,7 +2143,7 @@ Accept wildcard characters: False
 
 ### -SendModerationNotifications
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SendModerationNotifications parameter specifies when moderation notification messages are sent. Valid values are:
 
@@ -2167,7 +2167,7 @@ Accept wildcard characters: False
 
 ### -SharingPolicy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -2195,7 +2195,7 @@ Accept wildcard characters: False
 
 ### -SupervisoryReviewPolicy
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -2235,7 +2235,7 @@ Accept wildcard characters: False
 
 ### -ThrottlingPolicy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -2263,7 +2263,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MailboxAuditLogSearch.md b/exchange/exchange-ps/ExchangePowerShell/New-MailboxAuditLogSearch.md
index 4aa8ca23e8..a23fd4ffa8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-MailboxAuditLogSearch.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-MailboxAuditLogSearch.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
 Locale: en-US
@@ -67,7 +67,7 @@ This example returns entries from the mailbox audit logs of all users in organiz
 
 ### -EndDate
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The EndDate parameter specifies the end date of the date range.
 
@@ -87,7 +87,7 @@ Accept wildcard characters: False
 
 ### -StartDate
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The StartDate parameter specifies the start date of the date range.
 
@@ -107,7 +107,7 @@ Accept wildcard characters: False
 
 ### -StatusMailRecipients
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The StatusMailRecipients parameter specifies the email address where the search results are sent. You can specify multiple values separated by commas.
 
@@ -125,7 +125,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -146,7 +146,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -166,7 +166,7 @@ Accept wildcard characters: False
 
 ### -ExternalAccess
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ExternalAccess parameter specifies whether to return only audit log entries for mailbox access by users that are outside of your organization. In Exchange Online, this parameter returns audit log entries for mailbox access by Microsoft datacenter administrators. Valid values are:
 
@@ -208,7 +208,7 @@ Accept wildcard characters: False
 
 ### -HasAttachments
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The HasAttachments parameter filters the search by messages that have attachments. Valid values are:
 
@@ -229,7 +229,7 @@ Accept wildcard characters: False
 
 ### -LogonTypes
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The LogonTypes parameter specifies the type of logons. Valid values are:
 
@@ -254,7 +254,7 @@ Accept wildcard characters: False
 
 ### -Mailboxes
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Mailboxes parameter specifies the mailbox to retrieve mailbox audit log entries from.
 
@@ -276,7 +276,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Name parameter specifies a name for the search. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -294,7 +294,7 @@ Accept wildcard characters: False
 
 ### -Operations
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Operations parameter filters the search results by the operations that are logged by mailbox audit logging. Valid values are:
 
@@ -327,7 +327,7 @@ Accept wildcard characters: False
 
 ### -ShowDetails
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ShowDetails switch specifies that details of each log entry are retrieved. You don't need to specify a value with this switch.
 
@@ -345,7 +345,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MailboxDatabase.md b/exchange/exchange-ps/ExchangePowerShell/New-MailboxDatabase.md
index 13b7f9cdaf..53a44cc183 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-MailboxDatabase.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-MailboxDatabase.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -68,7 +68,7 @@ This example creates the mailbox database DB1 on the Mailbox server named Server
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Name parameter specifies the name of the new mailbox database. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -86,7 +86,7 @@ Accept wildcard characters: False
 
 ### -Recovery
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Recovery switch specifies that the new database is designated as a recovery database. You don't need to specify a value with this switch.
 
@@ -104,7 +104,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
 
@@ -127,7 +127,7 @@ Accept wildcard characters: False
 
 ### -AutoDagExcludeFromMonitoring
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AutoDagExcludeFromMonitoring parameter specifies that the database being created should not be monitored by managed availability.
 
@@ -145,7 +145,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -166,7 +166,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -184,7 +184,7 @@ Accept wildcard characters: False
 
 ### -EdbFilePath
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The EdbFilePath parameter specifies the path to the database files. The default location is `%ExchangeInstallPath%Mailbox\<Mailbox DB Name>\<Mailbox DB Name>.edb`.
 
@@ -202,7 +202,7 @@ Accept wildcard characters: False
 
 ### -IsExcludedFromInitialProvisioning
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IsExcludedFromInitialProvisioning switch specifies that this database is temporarily not considered by the mailbox provisioning load balancer. You don't need to specify a value with this switch.
 
@@ -222,7 +222,7 @@ Accept wildcard characters: False
 
 ### -IsExcludedFromProvisioning
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IsExcludedFromProvisioning parameter specifies whether this database is considered by the mailbox provisioning load balancer. If the IsExcludedFromProvisioning parameter is set to $true, no new mailboxes are automatically added to this database.
 
@@ -240,7 +240,7 @@ Accept wildcard characters: False
 
 ### -IsSuspendedFromProvisioning
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IsSuspendedFromProvisioning parameter specifies whether this database is temporarily considered by the mailbox provisioning load balancer.
 
@@ -258,7 +258,7 @@ Accept wildcard characters: False
 
 ### -LogFolderPath
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The LogFolderPath parameter specifies the folder location for log files.The default location is `%ExchangeInstallPath%Mailbox\<Mailbox DB Name>`
 
@@ -276,7 +276,7 @@ Accept wildcard characters: False
 
 ### -OfflineAddressBook
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The OfflineAddressBook parameter specifies the associated offline address book (OAB) for the new mailbox database.
 
@@ -294,7 +294,7 @@ Accept wildcard characters: False
 
 ### -PublicFolderDatabase
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PublicFolderDatabase parameter specifies the associated public folder database for the new mailbox database. You can use any value that uniquely identifies the public folder database. For example:
 
@@ -316,7 +316,7 @@ Accept wildcard characters: False
 
 ### -SkipDatabaseLogFolderCreation
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -334,7 +334,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MailboxExportRequest.md b/exchange/exchange-ps/ExchangePowerShell/New-MailboxExportRequest.md
index a4d5b91ef0..2341ba1ddd 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-MailboxExportRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-MailboxExportRequest.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -196,7 +196,7 @@ Accept wildcard characters: False
 
 ### -ComplianceStorePath
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -214,7 +214,7 @@ Accept wildcard characters: False
 
 ### -FilePath
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The FilePath parameter specifies the network share path of the .pst file to which data is exported, for example, \\\\SERVER01\\PST Files\\exported.pst.
 
@@ -257,7 +257,7 @@ Accept wildcard characters: False
 
 ### -AcceptLargeDataLoss
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AcceptLargeDataLoss switch specifies the request should continue even if a large number of items in the source mailbox can't be copied to the target mailbox. You don't need to specify a value with this switch.
 
@@ -279,7 +279,7 @@ Accept wildcard characters: False
 
 ### -AssociatedMessagesCopyOption
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AssociatedMessagesCopyOption parameter specifies whether associated messages are copied when the request is processed. Associated messages are special messages that contain hidden data with information about rules, views, and forms. By default, associated messages are copied. This parameter accepts the following values:
 
@@ -303,7 +303,7 @@ Accept wildcard characters: False
 
 ### -BadItemLimit
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The BadItemLimit parameter specifies the maximum number of bad items that are allowed before the request fails. A bad item is a corrupt item in the source mailbox that can't be copied to the target mailbox. Also included in the bad item limit are missing items. Missing items are items in the source mailbox that can't be found in the target mailbox when the request is ready to complete.
 
@@ -325,7 +325,7 @@ Accept wildcard characters: False
 
 ### -BatchName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The BatchName parameter specifies a descriptive name for exporting a batch of mailboxes. You can use the name in the BatchName parameter as a string search when you use the Get-MailboxExportRequest cmdlet.
 
@@ -343,7 +343,7 @@ Accept wildcard characters: False
 
 ### -CompletedRequestAgeLimit
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The CompletedRequestAgeLimit parameter specifies how long the request is kept after completion before it's automatically removed. The default value is 30 days.
 
@@ -361,7 +361,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -382,7 +382,7 @@ Accept wildcard characters: False
 
 ### -ConflictResolutionOption
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ConflictResolutionOption parameter specifies what to do if there are multiple matching messages in the target. Valid values are:
 
@@ -407,7 +407,7 @@ Accept wildcard characters: False
 
 ### -ContentFilter
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 **Important**: You can't use this parameter to export between two dates. You can export from a specific date, or export to a specific date, but not both.
 
@@ -436,7 +436,7 @@ Accept wildcard characters: False
 
 ### -ContentFilterLanguage
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ContentFilterLanguage parameter specifies the language being used in the ContentFilter parameter for string searches.
 
@@ -456,7 +456,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -474,7 +474,7 @@ Accept wildcard characters: False
 
 ### -ExcludeDumpster
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExcludeDumpster switch specifies whether to exclude the Recoverable Items folder. You don't need to specify a value with this switch.
 
@@ -498,7 +498,7 @@ Accept wildcard characters: False
 
 ### -ExcludeFolders
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExcludeFolders parameter specifies the list of folders to exclude during the export.
 
@@ -546,7 +546,7 @@ Accept wildcard characters: False
 
 ### -IncludeFolders
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IncludeFolders parameter specifies the list of folders to include during the export.
 
@@ -594,7 +594,7 @@ Accept wildcard characters: False
 
 ### -InternalFlags
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The InternalFlags parameter specifies the optional steps in the request. This parameter is used primarily for debugging purposes.
 
@@ -612,7 +612,7 @@ Accept wildcard characters: False
 
 ### -IsArchive
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IsArchive switch specifies that you're exporting from the user's archive. You don't need to specify a value with this switch.
 
@@ -630,7 +630,7 @@ Accept wildcard characters: False
 
 ### -LargeItemLimit
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The LargeItemLimit parameter specifies the maximum number of large items that are allowed before the request fails. A large item is a message in the source mailbox that exceeds the maximum message size that's allowed in the target mailbox. If the target mailbox doesn't have a specifically configured maximum message size value, the organization-wide value is used.
 
@@ -677,7 +677,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Name parameter specifies the name of the specific request for tracking and display purposes. Because you can have multiple export requests per mailbox, Exchange precedes the name with the mailbox's alias. For example, if you create an export request for a user's mailbox that has the alias Kweku and specify the value of this parameter as PC1toArchive, the identity of this export request is Kweku\\PC1toArchive.
 
@@ -697,7 +697,7 @@ Accept wildcard characters: False
 
 ### -PreferredMessageFormat
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -715,7 +715,7 @@ Accept wildcard characters: False
 
 ### -Priority
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Priority parameter specifies the order in which the request should be processed in the request queue. Requests are processed in order, based on server health, status, priority, and last update time. Valid priority values are:
 
@@ -741,7 +741,7 @@ Accept wildcard characters: False
 
 ### -RemoteHostName
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -759,7 +759,7 @@ Accept wildcard characters: False
 
 ### -RequestExpiryInterval
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RequestExpiryInterval parameter specifies an age limit for a completed or failed request. When you use this parameter, the completed or failed request is automatically removed after the specified interval expires. If you don't use this parameter:
 
@@ -784,7 +784,7 @@ Accept wildcard characters: False
 
 ### -SkipMerging
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SkipMerging parameter specifies steps in the export that should be skipped. This parameter is used primarily for debugging purposes.
 
@@ -802,7 +802,7 @@ Accept wildcard characters: False
 
 ### -SourceRootFolder
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SourceRootFolder parameter specifies the root folder of the mailbox from which data is exported. If this parameter isn't specified, the command exports all folders.
 
@@ -820,7 +820,7 @@ Accept wildcard characters: False
 
 ### -Suspend
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Suspend switch specifies whether to suspend the request. You don't need to specify a value with this switch.
 
@@ -840,7 +840,7 @@ Accept wildcard characters: False
 
 ### -SuspendComment
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SuspendComment parameter specifies a description about why the request was suspended. You can only use this parameter if you specify the Suspend parameter.
 
@@ -858,7 +858,7 @@ Accept wildcard characters: False
 
 ### -TargetRootFolder
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TargetRootFolder parameter specifies the top-level folder in which to export data. If you don't specify this parameter, the command exports folders to the top of the folder structure in the target .pst file. Content is merged under existing folders, and new folders are created if they don't already exist in the target folder structure.
 
@@ -876,7 +876,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
@@ -894,7 +894,7 @@ Accept wildcard characters: False
 
 ### -WorkloadType
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MailboxFolder.md b/exchange/exchange-ps/ExchangePowerShell/New-MailboxFolder.md
index d7e9d64fe5..234aa513a8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-MailboxFolder.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-MailboxFolder.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -54,7 +54,7 @@ This example creates the folder named Personal in the root folder hierarchy of y
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Name parameter specifies the name of the new folder. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -72,7 +72,7 @@ Accept wildcard characters: False
 
 ### -Parent
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Parent parameter specifies where to create the new mailbox folder. The syntax is `[MailboxID]:\[ParentFolder][\SubFolder]`.
 
@@ -111,7 +111,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -132,7 +132,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -152,7 +152,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MailboxImportRequest.md b/exchange/exchange-ps/ExchangePowerShell/New-MailboxImportRequest.md
index 3354f48df9..a97de519b4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-MailboxImportRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-MailboxImportRequest.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -235,7 +235,7 @@ Accept wildcard characters: False
 
 ### -FilePath
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -262,7 +262,7 @@ Accept wildcard characters: False
 
 ### -AcceptLargeDataLoss
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AcceptLargeDataLoss switch specifies the request should continue even if a large number of items in the source mailbox can't be copied to the target mailbox. You don't need to specify a value with this switch.
 
@@ -284,7 +284,7 @@ Accept wildcard characters: False
 
 ### -AssociatedMessagesCopyOption
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AssociatedMessagesCopyOption parameter specifies whether associated messages are copied when the request is processed. Associated messages are special messages that contain hidden data with information about rules, views, and forms. By default, associated messages are copied. This parameter accepts the following values:
 
@@ -328,7 +328,7 @@ Accept wildcard characters: False
 
 ### -BadItemLimit
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The BadItemLimit parameter specifies the maximum number of bad items that are allowed before the request fails. A bad item is a corrupt item in the source mailbox that can't be copied to the target mailbox. Also included in the bad item limit are missing items. Missing items are items in the source mailbox that can't be found in the target mailbox when the request is ready to complete.
 
@@ -350,7 +350,7 @@ Accept wildcard characters: False
 
 ### -BatchName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The BatchName parameter specifies a descriptive name for importing a batch of mailboxes. You can use the name in the BatchName parameter as a string search when you use the Get-MailboxImportRequest cmdlet.
 
@@ -368,7 +368,7 @@ Accept wildcard characters: False
 
 ### -CompletedRequestAgeLimit
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The CompletedRequestAgeLimit parameter specifies how long the request is kept after completion before being automatically removed. The default value is 30 days.
 
@@ -386,7 +386,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -407,7 +407,7 @@ Accept wildcard characters: False
 
 ### -ConflictResolutionOption
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConflictResolutionOption parameter specifies what to do if there are multiple matching messages in the target. Valid values are:
 
@@ -432,7 +432,7 @@ Accept wildcard characters: False
 
 ### -ContentCodePage
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ContentCodePage parameter specifies the specific code page to use for an ANSI pst file. ANSI pst files are used in Outlook 97 to Outlook 2002. You can find the valid values in the [Code Page Identifiers](https://learn.microsoft.com/windows/win32/intl/code-page-identifiers) topic.
 
@@ -450,7 +450,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -470,7 +470,7 @@ Accept wildcard characters: False
 
 ### -ExcludeDumpster
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ExcludeDumpster switch specifies whether to exclude the Recoverable Items folder. You don't need to specify a value with this switch.
 
@@ -494,7 +494,7 @@ Accept wildcard characters: False
 
 ### -ExcludeFolders
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ExcludeFolders parameter specifies the list of folders to exclude during the import.
 
@@ -542,7 +542,7 @@ Accept wildcard characters: False
 
 ### -IncludeFolders
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IncludeFolders parameter specifies the list of folders to include during the import.
 
@@ -588,7 +588,7 @@ Accept wildcard characters: False
 
 ### -InternalFlags
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -608,7 +608,7 @@ Accept wildcard characters: False
 
 ### -IsArchive
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IsArchive switch specifies that you're importing the .pst file into the user's archive. You don't need to specify a value with this switch.
 
@@ -626,7 +626,7 @@ Accept wildcard characters: False
 
 ### -LargeItemLimit
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The LargeItemLimit parameter specifies the maximum number of large items that are allowed before the request fails. A large item is a message in the source mailbox that exceeds the maximum message size that's allowed in the target mailbox. If the target mailbox doesn't have a specifically configured maximum message size value, the organization-wide value is used.
 
@@ -673,7 +673,7 @@ Accept wildcard characters: False
 
 ### -MigrationMailbox
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is reserved for internal Microsoft use.
 
@@ -751,7 +751,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Name parameter specifies the name of the specific request for tracking and display purposes. Because you can have multiple import requests per mailbox, Exchange precedes the name with the mailbox's alias. For example, if you create an import request for a user's mailbox that has the alias Kweku and specify the value of this parameter as PC1toArchive, the identity of this import request is Kweku\\PC1toArchive.
 
@@ -771,7 +771,7 @@ Accept wildcard characters: False
 
 ### -Priority
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -791,7 +791,7 @@ Accept wildcard characters: False
 
 ### -RequestExpiryInterval
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RequestExpiryInterval parameter specifies an age limit for a completed or failed request. When you use this parameter, the completed or failed request is automatically removed after the specified interval expires. If you don't use this parameter:
 
@@ -836,7 +836,7 @@ Accept wildcard characters: False
 
 ### -SkipMerging
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SkipMerging parameter specifies steps in the import that should be skipped. This parameter is used primarily for debugging purposes.
 
@@ -854,7 +854,7 @@ Accept wildcard characters: False
 
 ### -SourceEndpoint
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is reserved for internal Microsoft use.
 
@@ -872,7 +872,7 @@ Accept wildcard characters: False
 
 ### -SourceRootFolder
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SourceRootFolder parameter specifies the root folder of the .pst file from which data is imported. When specified, the folder hierarchy outside the value of the SourceRootFolder parameter isn't imported, and the SourceRootFolder parameter is mapped to the TargetRootFolder parameter. If this parameter isn't specified, the command imports all folders.
 
@@ -890,7 +890,7 @@ Accept wildcard characters: False
 
 ### -Suspend
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Suspend switch specifies whether to suspend the request. You don't need to specify a value with this switch.
 
@@ -910,7 +910,7 @@ Accept wildcard characters: False
 
 ### -SuspendComment
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SuspendComment parameter specifies a description about why the request was suspended. You can only use this parameter if you specify the Suspend parameter.
 
@@ -928,7 +928,7 @@ Accept wildcard characters: False
 
 ### -TargetRootFolder
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The TargetRootFolder parameter specifies the top-level mailbox folder that the imported content is placed in. If you don't specify this parameter, the command imports folders to the top of the folder structure in the target mailbox or archive. If the folder already exists, content is merged under existing folders, and new folders are created if they don't already exist in the target folder structure.
 
@@ -946,7 +946,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
@@ -964,7 +964,7 @@ Accept wildcard characters: False
 
 ### -WorkloadType
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MailboxRepairRequest.md b/exchange/exchange-ps/ExchangePowerShell/New-MailboxRepairRequest.md
index 4342464833..0c6bc785d5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-MailboxRepairRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-MailboxRepairRequest.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -96,7 +96,7 @@ This example creates a variable that identifies Ann Beebe's mailbox and then use
 
 ### -Database
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Database parameter repairs or detects corruption in all mailboxes in the specified database. You can use any value that uniquely identifies the database. For example:
 
@@ -122,7 +122,7 @@ Accept wildcard characters: False
 
 ### -Mailbox
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Mailbox parameter specifies the mailbox that you want to repair or detect corruption in. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -153,7 +153,7 @@ Accept wildcard characters: False
 
 ### -StoreMailbox
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The StoreMailbox parameter specifies the mailbox GUID of the mailbox you want to repair or detect corruption in. Use this parameter with the Database parameter.
 
@@ -173,7 +173,7 @@ Accept wildcard characters: False
 
 ### -CorruptionType
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The CorruptionType parameter specifies the type of corruption that you want to detect and repair. You can use the following values:
 
@@ -235,7 +235,7 @@ Accept wildcard characters: False
 
 ### -Archive
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Archive switch specifies whether to repair or detect corruption the archive mailbox that's associated with the specified mailbox. You don't need to specify a value with this switch.
 
@@ -257,7 +257,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -278,7 +278,7 @@ Accept wildcard characters: False
 
 ### -DetectOnly
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DetectOnly switch specifies that you want to report errors, but not fix them. You don't need to specify a value with this switch.
 
@@ -296,7 +296,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -314,7 +314,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -334,7 +334,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MailboxRestoreRequest.md b/exchange/exchange-ps/ExchangePowerShell/New-MailboxRestoreRequest.md
index 4df394dfdc..095d7d0fc6 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-MailboxRestoreRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-MailboxRestoreRequest.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -365,7 +365,7 @@ Accept wildcard characters: False
 
 ### -SourceDatabase
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -429,7 +429,7 @@ Accept wildcard characters: False
 
 ### -SourceMailbox
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SourceMailbox parameter specifies the soft-deleted mailbox that you want to restore. The best way to identify the soft-deleted mailbox is by its GUID value. You can find the GUID value by running the following command: Get-Mailbox -SoftDeletedMailbox.
 
@@ -447,7 +447,7 @@ Accept wildcard characters: False
 
 ### -SourceStoreMailbox
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is functional only in on-premises Exchange.
 
@@ -489,7 +489,7 @@ Accept wildcard characters: False
 
 ### -TargetMailbox
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The TargetMailbox parameter specifies the GUID of the target mailbox or mail user where you want to restore content to. The target mailbox or mail user needs to exist before you can run this command successfully.
 
@@ -513,7 +513,7 @@ Accept wildcard characters: False
 
 ### -AcceptLargeDataLoss
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AcceptLargeDataLoss switch specifies the request should continue even if a large number of items in the source mailbox can't be copied to the target mailbox. You don't need to specify a value with this switch.
 
@@ -535,7 +535,7 @@ Accept wildcard characters: False
 
 ### -AllowLegacyDNMismatch
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowLegacyDNMismatch switch specifies that the operation should continue if the LegacyExchangeDN of the source physical mailbox and the target mailbox don't match. You don't need to specify a value with this switch.
 
@@ -557,7 +557,7 @@ Accept wildcard characters: False
 
 ### -AssociatedMessagesCopyOption
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AssociatedMessagesCopyOption parameter specifies whether associated messages are copied when the request is processed. Associated messages are special messages that contain hidden data with information about rules, views, and forms. Valid values are:
 
@@ -581,7 +581,7 @@ Accept wildcard characters: False
 
 ### -BadItemLimit
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The BadItemLimit parameter specifies the maximum number of bad items that are allowed before the request fails. A bad item is a corrupt item in the source mailbox that can't be copied to the target mailbox. Also included in the bad item limit are missing items. Missing items are items in the source mailbox that can't be found in the target mailbox when the request is ready to complete.
 
@@ -605,7 +605,7 @@ Accept wildcard characters: False
 
 ### -BatchName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The BatchName parameter specifies a descriptive name for restoring a batch of mailboxes. You can use the name in the BatchName parameter as a string search when you use the Get-MailboxRestoreRequest cmdlet.
 
@@ -623,7 +623,7 @@ Accept wildcard characters: False
 
 ### -CompletedRequestAgeLimit
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The CompletedRequestAgeLimit parameter specifies how long the status of a completed restore request is set to Completed. If this parameter is set to a value of 0, the status is cleared immediately instead of being changed to Completed.
 
@@ -641,7 +641,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -662,7 +662,7 @@ Accept wildcard characters: False
 
 ### -ConflictResolutionOption
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConflictResolutionOption parameter specifies what to do if there are multiple matching messages in the target. Valid values are:
 
@@ -738,7 +738,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is functional only in on-premises Exchange.
 
@@ -758,7 +758,7 @@ Accept wildcard characters: False
 
 ### -ExcludeDumpster
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ExcludeDumpster switch specifies whether to exclude the Recoverable Items folder. You don't need to specify a value with this switch.
 
@@ -782,7 +782,7 @@ Accept wildcard characters: False
 
 ### -ExcludeFolders
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ExcludeFolders parameter specifies the list of folders to exclude during the restore request.
 
@@ -828,7 +828,7 @@ Accept wildcard characters: False
 
 ### -IncludeFolders
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IncludeFolders parameter specifies the list of folder to include during the restore request.
 
@@ -874,7 +874,7 @@ Accept wildcard characters: False
 
 ### -InternalFlags
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -894,7 +894,7 @@ Accept wildcard characters: False
 
 ### -LargeItemLimit
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The LargeItemLimit parameter specifies the maximum number of large items that are allowed before the request fails. A large item is a message in the source mailbox that exceeds the maximum message size that's allowed in the target mailbox. If the target mailbox doesn't have a specifically configured maximum message size value, the organization-wide value is used.
 
@@ -943,7 +943,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Name parameter specifies the name of the specific request for tracking and display purposes. Because you can have multiple restore requests per mailbox, Exchange precedes the name with the mailbox's alias. For example, if you create an export request for a user's mailbox that has the alias Kweku and specify the value of this parameter as RestoreFailedMoves, the identity of this export request is Kweku\\RestoreFailedMoves.
 
@@ -963,7 +963,7 @@ Accept wildcard characters: False
 
 ### -Priority
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -992,7 +992,7 @@ Accept wildcard characters: False
 
 ### -RequestExpiryInterval
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1019,7 +1019,7 @@ Accept wildcard characters: False
 
 ### -SkipMerging
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SkipMerging parameter specifies folder-related items to skip when restoring the mailbox. Use one of the following values:
 
@@ -1044,7 +1044,7 @@ Accept wildcard characters: False
 
 ### -SourceIsArchive
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SourceIsArchive switch specifies that the source mailbox is an archive mailbox. You don't need to specify a value with this switch.
 
@@ -1064,7 +1064,7 @@ Accept wildcard characters: False
 
 ### -SourceRootFolder
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SourceRootFolder parameter specifies the root folder of the mailbox from which data is restored. If this parameter isn't specified, the command restores all folders.
 
@@ -1082,7 +1082,7 @@ Accept wildcard characters: False
 
 ### -Suspend
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Suspend switch specifies whether to suspend the request. You don't need to specify a value with this switch.
 
@@ -1102,7 +1102,7 @@ Accept wildcard characters: False
 
 ### -SuspendComment
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SuspendComment parameter specifies a description about why the request was suspended. You can only use this parameter if you specify the Suspend parameter.
 
@@ -1120,7 +1120,7 @@ Accept wildcard characters: False
 
 ### -TargetIsArchive
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The TargetIsArchive switch specifies that the content is restored into the specified target mailbox's archive. You don't need to specify a value with this switch.
 
@@ -1138,7 +1138,7 @@ Accept wildcard characters: False
 
 ### -TargetRootFolder
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The TargetRootFolder parameter specifies the top-level folder in which to restore data. If you don't specify this parameter, the command restores folders to the top of the folder structure in the target mailbox or archive. Content is merged under existing folders, and new folders are created if they don't already exist in the target folder structure.
 
@@ -1158,7 +1158,7 @@ Accept wildcard characters: False
 
 ### -TargetType
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The TargetType parameter specifies the type of mailbox that's the target for the restore operation. Valid values are:
 
@@ -1180,7 +1180,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
@@ -1198,7 +1198,7 @@ Accept wildcard characters: False
 
 ### -WorkloadType
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MailboxSearch.md b/exchange/exchange-ps/ExchangePowerShell/New-MailboxSearch.md
index 36cb459e8b..9a3283d0a7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-MailboxSearch.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-MailboxSearch.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
 Locale: en-US
@@ -105,7 +105,7 @@ In on-premises Exchange, this example creates an In-Place Hold named Hold for al
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Name parameter specifies a friendly name for the search. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -125,7 +125,7 @@ Accept wildcard characters: False
 
 ### -AllPublicFolderSources
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllPublicFolderSources parameter specifies whether to include all public folders in the organization in the search. Valid values are:
 
@@ -146,7 +146,7 @@ Accept wildcard characters: False
 
 ### -AllSourceMailboxes
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllSourceMailboxes parameter specifies whether to include all mailboxes in the search. Valid values are:
 
@@ -167,7 +167,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -188,7 +188,7 @@ Accept wildcard characters: False
 
 ### -Description
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Description parameter specifies a description for the search. The description isn't displayed to users. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -206,7 +206,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -248,7 +248,7 @@ Accept wildcard characters: False
 
 ### -EndDate
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The EndDate parameter specifies the end date of the date range.
 
@@ -268,7 +268,7 @@ Accept wildcard characters: False
 
 ### -EstimateOnly
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The EstimateOnly switch specifies that only an estimate of the number of items to be returned is provided. You don't need to specify a value with this switch.
 
@@ -288,7 +288,7 @@ Accept wildcard characters: False
 
 ### -ExcludeDuplicateMessages
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ExcludeDuplicateMessages parameter eliminates duplication of messages in search results. Valid values are:
 
@@ -309,7 +309,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -329,7 +329,7 @@ Accept wildcard characters: False
 
 ### -IncludeKeywordStatistics
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IncludeKeywordStatistics switch returns keyword statistics (number of instances for each keyword) in search results. You don't need to specify a value with this switch.
 
@@ -347,7 +347,7 @@ Accept wildcard characters: False
 
 ### -IncludeUnsearchableItems
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IncludeUnsearchableItems switch specifies that items that couldn't be indexed by Exchange Search should be included in the results. You don't need to specify a value with this switch.
 
@@ -367,7 +367,7 @@ Accept wildcard characters: False
 
 ### -InPlaceHoldEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The InPlaceHoldEnabled parameter specifies whether to set an In-Place Hold on items in the search results. Valid values are:
 
@@ -392,7 +392,7 @@ Accept wildcard characters: False
 
 ### -InPlaceHoldIdentity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is reserved for internal Microsoft use.
 
@@ -410,7 +410,7 @@ Accept wildcard characters: False
 
 ### -ItemHoldPeriod
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ItemHoldPeriod parameter specifies the number of days for the In-Place Hold onthe mailbox items (all mailbox items or the items that are returned in the search query results). The duration is calculated from the time the item is received or created in the mailbox. Valid values are:
 
@@ -431,7 +431,7 @@ Accept wildcard characters: False
 
 ### -Language
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Language parameter specifies a locale for the search.
 
@@ -451,7 +451,7 @@ Accept wildcard characters: False
 
 ### -LogLevel
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The LogLevel parameter specifies the logging level for the search. Valid values are:
 
@@ -473,7 +473,7 @@ Accept wildcard characters: False
 
 ### -MessageTypes
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MessageTypes parameter specifies the message types to include in the search query. Valid values are:
 
@@ -504,7 +504,7 @@ Accept wildcard characters: False
 
 ### -Recipients
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Recipients parameter specifies one or more recipients to include in the search query. Messages that have the specified recipients in the To, Cc, and Bcc fields are returned in the search results.
 
@@ -546,7 +546,7 @@ Accept wildcard characters: False
 
 ### -SearchQuery
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SearchQuery parameter specifies keywords for the search query by using the Keyword Query Language (KQL). For more information, see [Keyword Query Language (KQL) syntax reference](https://learn.microsoft.com/sharepoint/dev/general-development/keyword-query-language-kql-syntax-reference) and [Keyword queries and search conditions for eDiscovery](https://learn.microsoft.com/purview/ediscovery-keyword-queries-and-search-conditions).
 
@@ -574,7 +574,7 @@ Accept wildcard characters: False
 
 ### -Senders
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Senders parameter specifies one or more senders to include in the search query. Messages that have the specified sender are returned in the search results. Senders can include users, distribution groups (messages sent by members of the group), SMTP addresses, or domains.
 
@@ -594,7 +594,7 @@ Accept wildcard characters: False
 
 ### -SourceMailboxes
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SourceMailboxes parameter specifies the identity of one or more mailboxes to be searched. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -630,7 +630,7 @@ Accept wildcard characters: False
 
 ### -StartDate
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The StartDate parameter specifies the start date of the date range.
 
@@ -650,7 +650,7 @@ Accept wildcard characters: False
 
 ### -StatusMailRecipients
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The StatusMailRecipients parameter specifies one or more recipients to receive a status email message upon completion of the search. You can use any value that uniquely identifies the recipient. For example:
 
@@ -677,7 +677,7 @@ Accept wildcard characters: False
 
 ### -TargetMailbox
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The TargetMailbox parameter specifies the destination mailbox where the search results are copied. You can use any value that uniquely identifies themailbox. For example:
 
@@ -706,7 +706,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch doesn't work on this cmdlet.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MalwareFilterPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-MalwareFilterPolicy.md
index 952710db59..2e11030806 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-MalwareFilterPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-MalwareFilterPolicy.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -74,7 +74,7 @@ This example creates a new malware filter policy named Contoso Malware Filter Po
 
 ### -Name
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Name parameter specifies the unique name of the malware filter policy. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -92,7 +92,7 @@ Accept wildcard characters: False
 
 ### -Action
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -116,7 +116,7 @@ Accept wildcard characters: False
 
 ### -AdminDisplayName
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The AdminDisplayName parameter specifies a description for the policy. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -134,7 +134,7 @@ Accept wildcard characters: False
 
 ### -BypassInboundMessages
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -157,7 +157,7 @@ Accept wildcard characters: False
 
 ### -BypassOutboundMessages
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -180,7 +180,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -201,7 +201,7 @@ Accept wildcard characters: False
 
 ### -CustomAlertText
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -223,7 +223,7 @@ Accept wildcard characters: False
 
 ### -CustomExternalBody
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The CustomExternalBody parameter specifies the custom body to use in notification messages for malware detections in messages from external senders. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -246,7 +246,7 @@ Accept wildcard characters: False
 
 ### -CustomExternalSubject
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The CustomExternalSubject parameter specifies the custom subject to use in notification messages for malware detections in messages from external senders. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -269,7 +269,7 @@ Accept wildcard characters: False
 
 ### -CustomFromAddress
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The CustomFromAddress parameter specifies the custom From address to use in notification messages for malware detections in messages from internal or external senders.
 
@@ -294,7 +294,7 @@ Accept wildcard characters: False
 
 ### -CustomFromName
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The CustomFromName parameter specifies the custom From name to use in notification messages for malware detections in messages from internal or external senders. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -319,7 +319,7 @@ Accept wildcard characters: False
 
 ### -CustomInternalBody
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The CustomInternalBody parameter specifies the custom body to use in notification messages for malware detections in messages from internal senders. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -342,7 +342,7 @@ Accept wildcard characters: False
 
 ### -CustomInternalSubject
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The CustomInternalSubject parameter specifies the custom subject to use in notification messages for malware detections in messages from internal senders. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -365,7 +365,7 @@ Accept wildcard characters: False
 
 ### -CustomNotifications
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The CustomNotifications parameter enables or disables the customization of notification messages for malware detections. Valid values are:
 
@@ -393,7 +393,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -413,7 +413,7 @@ Accept wildcard characters: False
 
 ### -EnableExternalSenderAdminNotifications
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The EnableExternalSenderAdminNotifications parameter enables or disables sending notification messages to an administrator for malware detections in messages from internal senders. Valid values are:
 
@@ -436,7 +436,7 @@ Accept wildcard characters: False
 
 ### -EnableExternalSenderNotifications
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -486,7 +486,7 @@ Accept wildcard characters: False
 
 ### -EnableInternalSenderAdminNotifications
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The EnableInternalSenderAdminNotifications parameter enables or disables sending notification messages to an administrator for malware detections in messages from internal senders. Valid values are:
 
@@ -509,7 +509,7 @@ Accept wildcard characters: False
 
 ### -EnableInternalSenderNotifications
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -532,7 +532,7 @@ Accept wildcard characters: False
 
 ### -ExternalSenderAdminAddress
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ExternalSenderAdminAddress parameter specifies the email address of the administrator who receives notifications messages for malware detections in messages from external senders.
 
@@ -607,7 +607,7 @@ Accept wildcard characters: False
 
 ### -InternalSenderAdminAddress
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The InternalSenderAdminAddress parameter specifies the email address of the administrator who receives notifications messages for malware detections in messages from internal senders.
 
@@ -677,7 +677,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 

From e064e2939b34a4cc7326d8f6edbe9878e9295dc3 Mon Sep 17 00:00:00 2001
From: Chris Davis <chris.davis@microsoft.com>
Date: Thu, 7 Aug 2025 14:16:30 -0700
Subject: [PATCH 132/145] Add Exchange Server SE 5

---
 .../New-MalwareFilterRule.md                  |  30 +-
 .../ExchangePowerShell/New-ManagementRole.md  |  18 +-
 .../New-ManagementRoleAssignment.md           |  38 +-
 .../ExchangePowerShell/New-ManagementScope.md |  26 +-
 .../New-MapiVirtualDirectory.md               |  24 +-
 .../New-MessageClassification.md              |  26 +-
 .../ExchangePowerShell/New-MigrationBatch.md  |  82 ++---
 .../New-MigrationEndpoint.md                  |  32 +-
 .../New-MobileDeviceMailboxPolicy.md          | 112 +++---
 .../ExchangePowerShell/New-MoveRequest.md     |  86 ++---
 .../New-OabVirtualDirectory.md                |  32 +-
 .../New-OfflineAddressBook.md                 |  24 +-
 .../New-OrganizationRelationship.md           |  44 +--
 .../New-OutlookProtectionRule.md              |  26 +-
 .../ExchangePowerShell/New-OutlookProvider.md |  10 +-
 .../New-OwaMailboxPolicy.md                   |  10 +-
 .../New-OwaVirtualDirectory.md                |  32 +-
 .../New-PartnerApplication.md                 |  26 +-
 .../ExchangePowerShell/New-PolicyTipConfig.md |  12 +-
 .../New-PowerShellVirtualDirectory.md         |  30 +-
 .../ExchangePowerShell/New-PublicFolder.md    |  16 +-
 .../New-PublicFolderMigrationRequest.md       |  44 +--
 .../New-PublicFolderMoveRequest.md            |  36 +-
 .../New-ReceiveConnector.md                   | 124 +++----
 .../ExchangePowerShell/New-RemoteDomain.md    |  12 +-
 .../ExchangePowerShell/New-RemoteMailbox.md   |  56 +--
 .../ExchangePowerShell/New-RetentionPolicy.md |  14 +-
 .../New-RetentionPolicyTag.md                 |  34 +-
 .../New-RoleAssignmentPolicy.md               |  16 +-
 .../ExchangePowerShell/New-RoleGroup.md       |  34 +-
 .../New-SearchDocumentFormat.md               |  18 +-
 .../ExchangePowerShell/New-SendConnector.md   |  80 ++---
 .../ExchangePowerShell/New-SettingOverride.md |  26 +-
 .../ExchangePowerShell/New-SharingPolicy.md   |  16 +-
 .../ExchangePowerShell/New-SiteMailbox.md     |  24 +-
 .../New-SiteMailboxProvisioningPolicy.md      |  22 +-
 .../ExchangePowerShell/New-SweepRule.md       |  32 +-
 .../New-SyncMailPublicFolder.md               |  76 ++--
 .../ExchangePowerShell/New-SystemMessage.md   |  18 +-
 .../New-ThrottlingPolicy.md                   | 246 ++++++-------
 .../ExchangePowerShell/New-TransportRule.md   | 332 +++++++++---------
 .../New-WebServicesVirtualDirectory.md        |  50 +--
 .../New-X400AuthoritativeDomain.md            |  14 +-
 .../ExchangePowerShell/Redirect-Message.md    |  10 +-
 .../ExchangePowerShell/Remove-ADPermission.md |  28 +-
 .../Remove-AcceptedDomain.md                  |  10 +-
 .../Remove-ActiveSyncDevice.md                |  10 +-
 .../Remove-ActiveSyncDeviceAccessRule.md      |  10 +-
 .../Remove-ActiveSyncDeviceClass.md           |  10 +-
 .../Remove-ActiveSyncMailboxPolicy.md         |  12 +-
 .../Remove-ActiveSyncVirtualDirectory.md      |  10 +-
 .../Remove-AddressBookPolicy.md               |  10 +-
 .../ExchangePowerShell/Remove-AddressList.md  |  12 +-
 .../Remove-AddressRewriteEntry.md             |  10 +-
 .../ExchangePowerShell/Remove-App.md          |  16 +-
 .../Remove-AttachmentFilterEntry.md           |  10 +-
 .../ExchangePowerShell/Remove-AuthRedirect.md |  10 +-
 .../ExchangePowerShell/Remove-AuthServer.md   |  10 +-
 .../Remove-AuthenticationPolicy.md            |   8 +-
 .../Remove-AutodiscoverVirtualDirectory.md    |  10 +-
 .../Remove-AvailabilityAddressSpace.md        |  10 +-
 .../Remove-CalendarEvents.md                  |  16 +-
 .../Remove-ClassificationRuleCollection.md    |  10 +-
 .../Remove-ClientAccessRule.md                |  10 +-
 .../Remove-ComplianceSearch.md                |   8 +-
 .../Remove-ComplianceSecurityFilter.md        |   8 +-
 .../Remove-ContentFilterPhrase.md             |  12 +-
 .../Remove-DataClassification.md              |  10 +-
 .../Remove-DatabaseAvailabilityGroup.md       |  10 +-
 ...Remove-DatabaseAvailabilityGroupNetwork.md |  10 +-
 .../Remove-DatabaseAvailabilityGroupServer.md |  16 +-
 .../Remove-DeliveryAgentConnector.md          |  10 +-
 .../Remove-DistributionGroup.md               |  14 +-
 .../Remove-DistributionGroupMember.md         |  14 +-
 .../ExchangePowerShell/Remove-DlpPolicy.md    |  10 +-
 .../Remove-DlpPolicyTemplate.md               |  10 +-
 .../Remove-DynamicDistributionGroup.md        |  12 +-
 .../Remove-EcpVirtualDirectory.md             |  10 +-
 .../Remove-EdgeSubscription.md                |  12 +-
 .../Remove-EmailAddressPolicy.md              |  10 +-
 .../Remove-ExchangeCertificate.md             |  14 +-
 .../Remove-FederatedDomain.md                 |  14 +-
 .../Remove-FederationTrust.md                 |  10 +-
 .../Remove-ForeignConnector.md                |  10 +-
 .../Remove-GlobalAddressList.md               |  10 +-
 .../Remove-GlobalMonitoringOverride.md        |  18 +-
 .../Remove-HybridConfiguration.md             |   8 +-
 .../Remove-IPAllowListEntry.md                |  10 +-
 .../Remove-IPAllowListProvider.md             |  10 +-
 .../Remove-IPBlockListEntry.md                |  10 +-
 .../Remove-IPBlockListProvider.md             |  10 +-
 .../ExchangePowerShell/Remove-InboxRule.md    |  16 +-
 .../Remove-IntraOrganizationConnector.md      |  10 +-
 .../ExchangePowerShell/Remove-JournalRule.md  |  10 +-
 .../ExchangePowerShell/Remove-Mailbox.md      |  38 +-
 .../Remove-MailboxDatabase.md                 |  10 +-
 .../Remove-MailboxDatabaseCopy.md             |  10 +-
 97 files changed, 1348 insertions(+), 1348 deletions(-)

diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MalwareFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/New-MalwareFilterRule.md
index 2b3a5a5742..cdd83af3d6 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-MalwareFilterRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-MalwareFilterRule.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -57,7 +57,7 @@ This example creates a new malware filter rule named Contoso Recipients with the
 
 ### -Name
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Name parameter specifies a unique name for the malware filter rule.
 
@@ -75,7 +75,7 @@ Accept wildcard characters: False
 
 ### -MalwareFilterPolicy
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The MalwareFilterPolicy parameter specifies the malware filter policy that's associated with the malware filter rule.
 
@@ -101,7 +101,7 @@ Accept wildcard characters: False
 
 ### -Comments
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Comments parameter specifies informative comments for the rule, such as what the rule is used for or how it has changed over time. The length of the comment can't exceed 1024 characters.
 
@@ -119,7 +119,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -140,7 +140,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -160,7 +160,7 @@ Accept wildcard characters: False
 
 ### -Enabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Enabled parameter enables or disables the malware filter rule. Valid input for this parameter is $true or $false. The default value is $true.
 
@@ -178,7 +178,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfRecipientDomainIs
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ExceptIfRecipientDomainIs parameter specifies an exception that looks for recipients with email addresses in the specified domains. You can specify multiple domains separated by commas.
 
@@ -196,7 +196,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfSentTo
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ExceptIfSentTo parameter specifies an exception that looks for recipients in messages. You can use any value that uniquely identifies the recipient. For example:
 
@@ -223,7 +223,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfSentToMemberOf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ExceptIfSentToMemberOf parameter specifies an exception that looks for messages sent to members of distribution groups, mail-enabled security groups, or sent to Microsoft 365 Groups. You can use any value that uniquely identifies the group. For example:
 
@@ -252,7 +252,7 @@ Accept wildcard characters: False
 
 ### -Priority
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Priority parameter specifies a priority value for the rule that determines the order of rule processing. A lower integer value indicates a higher priority, the value 0 is the highest priority, and rules can't have the same priority value.
 
@@ -278,7 +278,7 @@ Accept wildcard characters: False
 
 ### -RecipientDomainIs
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The RecipientDomainIs parameter specifies a condition that looks for recipients with email addresses in the specified domains. You can specify multiple domains separated by commas.
 
@@ -296,7 +296,7 @@ Accept wildcard characters: False
 
 ### -SentTo
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The SentTo parameter specifies a condition that looks for recipients in messages. You can use any value that uniquely identifies the recipient. For example:
 
@@ -323,7 +323,7 @@ Accept wildcard characters: False
 
 ### -SentToMemberOf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The SentToMemberOf parameter specifies a condition that looks for messages sent to members of distribution groups, mail-enabled security groups, or sent to Microsoft 365 Groups. You can use any value that uniquely identifies the group. For example:
 
@@ -352,7 +352,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ManagementRole.md b/exchange/exchange-ps/ExchangePowerShell/New-ManagementRole.md
index fa552a0a5e..8384bfbed8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-ManagementRole.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-ManagementRole.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -87,7 +87,7 @@ In on-premises Exchange, this example creates the unscoped management role In-ho
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Name parameter specifies the name of the role. The maximum length of the name is 64 characters. If the name contains spaces, enclose the name in quotation marks (").
 
@@ -105,7 +105,7 @@ Accept wildcard characters: False
 
 ### -Parent
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Parent parameter specifies the identity of the role to copy. If the name of the role contains spaces, enclose the name in quotation marks ("). If you specify the Parent parameter, you can't use the UnScopedTopLevel switch.
 
@@ -123,7 +123,7 @@ Accept wildcard characters: False
 
 ### -UnScopedTopLevel
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -149,7 +149,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -170,7 +170,7 @@ Accept wildcard characters: False
 
 ### -Description
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Description parameter specifies the description that's displayed when the management role is viewed using the Get-ManagementRole cmdlet. Enclose the description in quotation marks (").
 
@@ -188,7 +188,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -208,7 +208,7 @@ Accept wildcard characters: False
 
 ### -EnabledCmdlets
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The EnabledCmdlets parameter specifies the cmdlets that are copied from the parent role. You can specify multiple values separated by commas.
 
@@ -250,7 +250,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ManagementRoleAssignment.md b/exchange/exchange-ps/ExchangePowerShell/New-ManagementRoleAssignment.md
index 1e4c1d0ef6..6ba6506e29 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-ManagementRoleAssignment.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-ManagementRoleAssignment.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -179,7 +179,7 @@ This example assigns the Mail Recipients role to the Contoso Sub - Seattle role
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Name parameter specifies a name for the new management role assignment. The maximum length of the name is 64 characters. If the management role assignment name contains spaces, enclose the name in quotation marks ("). If you don't specify a name, a name is created automatically.
 
@@ -221,7 +221,7 @@ Accept wildcard characters: False
 
 ### -Computer
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -243,7 +243,7 @@ Accept wildcard characters: False
 
 ### -Policy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Policy parameter specifies the name of the management role assignment policy to assign the management role to. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -265,7 +265,7 @@ Accept wildcard characters: False
 
 ### -Role
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Role parameter specifies the existing role to assign. You can use any value that uniquely identifies the role. For example:
 
@@ -291,7 +291,7 @@ Accept wildcard characters: False
 
 ### -SecurityGroup
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The SecurityGroup parameter specifies the name of the management role group or mail-enabled universal security group to assign the management role to. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -311,7 +311,7 @@ Accept wildcard characters: False
 
 ### -User
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The User parameter specifies the user to assign the management role to.
 
@@ -336,7 +336,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -357,7 +357,7 @@ Accept wildcard characters: False
 
 ### -CustomConfigWriteScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -377,7 +377,7 @@ Accept wildcard characters: False
 
 ### -CustomRecipientWriteScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The CustomRecipientWriteScope parameter specifies the existing recipient-based management scope to associate with this management role assignment. If the management scope name contains spaces, enclose the name in quotation marks ("). If you use the CustomRecipientWriteScope parameter, you can't use the RecipientOrganizationalUnitScope or ExclusiveRecipientWriteScope parameters.
 
@@ -423,7 +423,7 @@ Accept wildcard characters: False
 
 ### -Delegating
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Delegating switch specifies whether the user or USG assigned to the role can delegate the role to other users or groups. You don't need to specify a value with this switch.
 
@@ -441,7 +441,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -461,7 +461,7 @@ Accept wildcard characters: False
 
 ### -ExclusiveConfigWriteScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -481,7 +481,7 @@ Accept wildcard characters: False
 
 ### -ExclusiveRecipientWriteScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ExclusiveRecipientWriteScope parameter specifies the exclusive recipient-based management scope to associate with the new role assignment. If you use the ExclusiveRecipientWriteScope parameter, you can't use the CustomRecipientWriteScope or RecipientOrganizationalUnitScope parameters. If the scope name contains spaces, enclose the name in quotation marks (").
 
@@ -521,7 +521,7 @@ Accept wildcard characters: False
 
 ### -RecipientAdministrativeUnitScope
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter is functional only in the cloud-based service.
 
@@ -563,7 +563,7 @@ Accept wildcard characters: False
 
 ### -RecipientOrganizationalUnitScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The RecipientOrganizationalUnitScope parameter specifies the OU to scope the new role assignment to. If you use the RecipientOrganizationalUnitScope parameter, you can't use the CustomRecipientWriteScope or ExclusiveRecipientWriteScope parameters. To specify an OU, use the syntax: domain/ou. If the OU name contains spaces, enclose the domain and OU in quotation marks (").
 
@@ -581,7 +581,7 @@ Accept wildcard characters: False
 
 ### -RecipientRelativeWriteScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The RecipientRelativeWriteScope parameter specifies the type of restriction to apply to a recipient scope. The available types are None, Organization, MyGAL, Self, and MyDistributionGroups. The RecipientRelativeWriteScope parameter is automatically set when the CustomRecipientWriteScope or RecipientOrganizationalUnitScope parameters are used.
 
@@ -601,7 +601,7 @@ Accept wildcard characters: False
 
 ### -UnScopedTopLevel
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -625,7 +625,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ManagementScope.md b/exchange/exchange-ps/ExchangePowerShell/New-ManagementScope.md
index 7689690822..3fea608e67 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-ManagementScope.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-ManagementScope.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -129,7 +129,7 @@ This example creates the Seattle Databases scope and sets a database restriction
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Name parameter specifies the name of the management scope. The name can be up to 64 characters. If the name contains spaces, enclose the name in quotation marks (").
 
@@ -147,7 +147,7 @@ Accept wildcard characters: False
 
 ### -DatabaseList
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -175,7 +175,7 @@ Accept wildcard characters: False
 
 ### -DatabaseRestrictionFilter
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -206,7 +206,7 @@ Accept wildcard characters: False
 
 ### -RecipientRestrictionFilter
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The RecipientRestrictionFilter parameter uses OPATH filter syntax to specify the recipients that are included in the scope. The syntax is `"Property -ComparisonOperator 'Value'"`.
 
@@ -235,7 +235,7 @@ Accept wildcard characters: False
 
 ### -ServerList
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -264,7 +264,7 @@ Accept wildcard characters: False
 
 ### -ServerRestrictionFilter
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -295,7 +295,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -316,7 +316,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -336,7 +336,7 @@ Accept wildcard characters: False
 
 ### -Exclusive
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Exclusive switch specifies that the role should be an exclusive scope. You don't need to specify a value with this switch.
 
@@ -356,7 +356,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -376,7 +376,7 @@ Accept wildcard characters: False
 
 ### -RecipientRoot
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The RecipientRoot parameter specifies the organizational unit (OU) under which the filter specified with the RecipientRestrictionFilter parameter should be applied. Valid input for this parameter is an OU or domain that's returned by the Get-OrganizationalUnit cmdlet. You can use any value that uniquely identifies the OU or domain. For example:
 
@@ -401,7 +401,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MapiVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/New-MapiVirtualDirectory.md
index 2e66284d4f..63de2bf232 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-MapiVirtualDirectory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-MapiVirtualDirectory.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -57,7 +57,7 @@ This example creates a new MAPI virtual directory that has the following configu
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -78,7 +78,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -96,7 +96,7 @@ Accept wildcard characters: False
 
 ### -ExtendedProtectionFlags
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExtendedProtectionFlags parameter specifies custom settings for Extended Protection for Authentication on the virtual directory. Valid values are:
 
@@ -120,7 +120,7 @@ Accept wildcard characters: False
 
 ### -ExtendedProtectionSPNList
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExtendedProtectionSPNList parameter specifies a list of valid Service Principal Names (SPNs) if you're using Extended Protection for Authentication on the virtual directory. Valid values are:
 
@@ -141,7 +141,7 @@ Accept wildcard characters: False
 
 ### -ExtendedProtectionTokenChecking
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExtendedProtectionTokenChecking parameter defines how you want to use Extended Protection for Authentication on the virtual directory. Extended Protection for Authentication isn't enabled by default. Valid values are:
 
@@ -165,7 +165,7 @@ Accept wildcard characters: False
 
 ### -ExternalUrl
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExternalURL parameter specifies the URL that's used to connect to the virtual directory from outside the firewall.
 
@@ -187,7 +187,7 @@ Accept wildcard characters: False
 
 ### -IISAuthenticationMethods
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IISAuthenticationMethods parameter specifies the authentication methods that are enabled on the virtual directory in Internet Information Services (IIS). Valid values for this parameter are:
 
@@ -216,7 +216,7 @@ Accept wildcard characters: False
 
 ### -InternalUrl
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The InternalURL parameter specifies the URL that's used to connect to the virtual directory from inside the firewall.
 
@@ -263,7 +263,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Exchange server that hosts the virtual directory. You can use any value that uniquely identifies the server. For example:
 
@@ -286,7 +286,7 @@ Accept wildcard characters: False
 
 ### -WebSiteName
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WebSiteName parameter specifies the name of the IIS website under which the virtual directory is created. You don't need to use this parameter to create the virtual directory under the default website.
 
@@ -304,7 +304,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MessageClassification.md b/exchange/exchange-ps/ExchangePowerShell/New-MessageClassification.md
index bf7fa10717..552bd2da44 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-MessageClassification.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-MessageClassification.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -75,7 +75,7 @@ In on-premises Exchange, this example creates a locale-specific (Spanish - Spain
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Name parameter specifies the unique name for the message classification. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -93,7 +93,7 @@ Accept wildcard characters: False
 
 ### -DisplayName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DisplayName parameter specifies the title of the message classification that's displayed in Outlook and selected by users. The maximum length is 256 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -113,7 +113,7 @@ Accept wildcard characters: False
 
 ### -Locale
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is functional on in on-premises Exchange.
 
@@ -135,7 +135,7 @@ Accept wildcard characters: False
 
 ### -SenderDescription
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SenderDescription parameter specifies the detailed text that's shown to Outlook senders when they select a message classification to apply to a message before they send the message. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -153,7 +153,7 @@ Accept wildcard characters: False
 
 ### -ClassificationID
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ClassificationID parameter specifies the classification ID (GUID) of an existing message classification that you want to import and use in your Exchange organization. Use this parameter if you're configuring message classifications that span two Exchange forests in the same organization.
 
@@ -173,7 +173,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -194,7 +194,7 @@ Accept wildcard characters: False
 
 ### -DisplayPrecedence
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DisplayPrecedence parameter specifies the relative precedence of the message classification to other message classifications that might be applied to a specified message. Valid values are:
 
@@ -224,7 +224,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -246,7 +246,7 @@ Accept wildcard characters: False
 
 ### -PermissionMenuVisible
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The PermissionMenuVisible parameter specifies whether the values that you entered for the DisplayName and RecipientDescription parameters are displayed in Outlook as the user composes a message. Valid values are:
 
@@ -267,7 +267,7 @@ Accept wildcard characters: False
 
 ### -RecipientDescription
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RecipientDescription parameter specifies the detailed text that's shown to Outlook recipient when they receive a message that has the message classification applied. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -287,7 +287,7 @@ Accept wildcard characters: False
 
 ### -RetainClassificationEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RetainClassificationEnabled parameter specifies whether the message classification should persist with the message if the message is forwarded or replied to.
 
@@ -307,7 +307,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MigrationBatch.md b/exchange/exchange-ps/ExchangePowerShell/New-MigrationBatch.md
index e928c46162..c7ee0db4cd 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-MigrationBatch.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-MigrationBatch.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -587,7 +587,7 @@ A Google Workspace migration batch is created that uses the CSV migration file g
 
 ### -UserIds
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The UserIds parameter specifies the users that you want to copy from an existing migration batch (for example, if a previous migration was partially successful). You identify a user by email address or by their Guid property value from the Get-MigrationUser cmdlet. You can specify multiple users separated by commas.
 
@@ -609,7 +609,7 @@ Accept wildcard characters: False
 
 ### -Users
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Users parameter specifies the users that you want to copy from an existing migration batch (for example, if a previous migration was partially successful). You identify the users by using the Get-MigrationUser cmdlet. For example:
 
@@ -675,7 +675,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Name parameter specifies an unique name for the migration batch on each system (Exchange On-premises or Exchange Online). The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks.
 
@@ -693,7 +693,7 @@ Accept wildcard characters: False
 
 ### -CSVData
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The CSVData parameter specifies the CSV file that contains information about the user mailboxes to be moved or migrated. The required attributes in the header row of the CSV file vary depending on the type of migration. For more information, see [CSV files for mailbox migration](https://learn.microsoft.com/exchange/csv-files-for-mailbox-migration-exchange-2013-help).
 
@@ -715,7 +715,7 @@ Accept wildcard characters: False
 
 ### -Local
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -735,7 +735,7 @@ Accept wildcard characters: False
 
 ### -SourcePublicFolderDatabase
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -779,7 +779,7 @@ Accept wildcard characters: False
 
 ### -AllowIncrementalSyncs
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -802,7 +802,7 @@ Accept wildcard characters: False
 
 ### -AllowUnknownColumnsInCsv
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowUnknownColumnsInCsv parameter specifies whether to allow extra columns in the CSV file that aren't used by migration. Valid values are:
 
@@ -843,7 +843,7 @@ Accept wildcard characters: False
 
 ### -ArchiveOnly
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ArchiveOnly switch specifies that only archive mailboxes are migrated for the users in the migration batch (primary mailboxes aren't migrated). You don't need to specify a value with this switch.
 
@@ -865,7 +865,7 @@ Accept wildcard characters: False
 
 ### -AutoComplete
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AutoComplete switch forces the finalization of the individual mailboxes as soon as the mailbox has completed initial synchronization. You don't need to specify a value with this switch.
 
@@ -907,7 +907,7 @@ Accept wildcard characters: False
 
 ### -AutoRetryCount
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -927,7 +927,7 @@ Accept wildcard characters: False
 
 ### -AutoStart
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AutoStart switch immediately starts the processing of the new migration batch. You don't need to specify a value with this switch.
 
@@ -967,7 +967,7 @@ Accept wildcard characters: False
 
 ### -BadItemLimit
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The BadItemLimit parameter specifies the maximum number of bad items that are allowed before the migration request fails. A bad item is a corrupt item in the source mailbox that can't be copied to the target mailbox. Also included in the bad item limit are missing items. Missing items are items in the source mailbox that can't be found in the target mailbox when the migration request is ready to complete.
 
@@ -989,7 +989,7 @@ Accept wildcard characters: False
 
 ### -CompleteAfter
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is functional only in the cloud-based service.
 
@@ -1016,7 +1016,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -1105,7 +1105,7 @@ Accept wildcard characters: False
 
 ### -DisableOnCopy
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DisableOnCopy switch disables the original migration job item for a user if you're copying users from an existing batch to a new batch by using the UserIds or Users parameters. You don't need to specify a value with this switch.
 
@@ -1123,7 +1123,7 @@ Accept wildcard characters: False
 
 ### -DisallowExistingUsers
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1145,7 +1145,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1339,7 +1339,7 @@ Accept wildcard characters: False
 
 ### -LargeItemLimit
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The LargeItemLimit parameter specifies the maximum number of large items that are allowed before the migration request fails. A large item is a message in the source mailbox that exceeds the maximum message size that's allowed in the target mailbox. If the target mailbox doesn't have a specifically configured maximum message size value, the organization-wide value is used.
 
@@ -1366,7 +1366,7 @@ Accept wildcard characters: False
 
 ### -Locale
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1408,7 +1408,7 @@ Accept wildcard characters: False
 
 ### -MoveOptions
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MoveOptions parameter specifies the stages of the migration that you want to skip for debugging purposes. Don't use this parameter unless you're directed to do so by Microsoft Customer Service and Support or specific documentation.
 
@@ -1428,7 +1428,7 @@ Accept wildcard characters: False
 
 ### -NotificationEmails
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The NotificationEmails parameter specifies one or more email addresses that migration status reports are sent to. Specify the value as a string array, and separate multiple email addresses with commas.
 
@@ -1468,7 +1468,7 @@ Accept wildcard characters: False
 
 ### -PrimaryOnly
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The PrimaryOnly switch specifies that only primary mailboxes are migrated for the users in the migration batch that also have archive mailboxes (archive mailboxes aren't migrated). You don't need to specify a value with this switch.
 
@@ -1490,7 +1490,7 @@ Accept wildcard characters: False
 
 ### -PublicFolderToUnifiedGroup
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is functional only in the cloud-based service.
 
@@ -1550,7 +1550,7 @@ Accept wildcard characters: False
 
 ### -ReportInterval
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ReportInterval parameter specifies how frequently emailed reports should be sent to the email addresses listed within NotificationEmails.
 
@@ -1712,7 +1712,7 @@ Accept wildcard characters: False
 
 ### -SkipMerging
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SkipMerging parameter specifies the stages of the migration that you want to skip for debugging purposes. Don't use this parameter unless you're directed to do so by Microsoft Customer Service and Support or specific documentation.
 
@@ -1730,7 +1730,7 @@ Accept wildcard characters: False
 
 ### -SkipMoving
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is replaced by the MoveOptions parameter.
 
@@ -1770,7 +1770,7 @@ Accept wildcard characters: False
 
 ### -SkipReports
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SkipReports switch specifies that you want to skip automatic reporting for the migration. You don't need to specify a value with this switch.
 
@@ -1808,7 +1808,7 @@ Accept wildcard characters: False
 
 ### -SkipSteps
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1833,7 +1833,7 @@ Accept wildcard characters: False
 
 ### -SourceEndpoint
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SourceEndpoint parameter specifies the migration endpoint to use for the source of the migration batch. You create the migration endpoint by using the New-MigrationEndpoint cmdlet. You can use any value that uniquely identifies the migration endpoint. For example:
 
@@ -1876,7 +1876,7 @@ Accept wildcard characters: False
 
 ### -StartAfter
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The StartAfter parameter specifies a delay before the data migration for the users within the batch is started. The migration is prepared, but the actual data migration for the user doesn't start until the date/time you specify with this parameter.
 
@@ -1901,7 +1901,7 @@ Accept wildcard characters: False
 
 ### -TargetArchiveDatabases
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The TargetArchiveDatabases parameter specifies the database where the archive mailboxes specified in the migration batch are migrated to. You can use any value that uniquely identifies the database. For example:
 
@@ -1929,7 +1929,7 @@ Accept wildcard characters: False
 
 ### -TargetDatabases
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The TargetDatabases parameter specifies the identity of the database that you're moving mailboxes to. You can use any value that uniquely identifies the database. For example:
 
@@ -1959,7 +1959,7 @@ Accept wildcard characters: False
 
 ### -TargetDeliveryDomain
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The TargetDeliveryDomain parameter specifies the FQDN of the external email address created in the source forest for the mail-enabled user when the migration batch is complete.
 
@@ -1979,7 +1979,7 @@ Accept wildcard characters: False
 
 ### -TargetEndpoint
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The TargetEndpoint parameter specifies the migration endpoint to use for the destination of the migration batch. You create the migration endpoint by using the New-MigrationEndpoint cmdlet. You can use any value that uniquely identifies the migration endpoint. For example:
 
@@ -2002,7 +2002,7 @@ Accept wildcard characters: False
 
 ### -TimeZone
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The TimeZone parameter specifies the time zone of the administrator who submits the migration batch.
 
@@ -2030,7 +2030,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
@@ -2048,7 +2048,7 @@ Accept wildcard characters: False
 
 ### -WorkflowControlFlags
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WorkflowControlFlags parameter specifies advanced controls for the steps that are performed in the migration. Valid values are:
 
@@ -2072,7 +2072,7 @@ Accept wildcard characters: False
 
 ### -WorkflowTemplate
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WorkflowTemplate parameter specifies advanced controls for the steps that are performed in the migration. Don't use this parameter unless you're directed to do so by Microsoft Customer Service and Support or specific documentation.
 
@@ -2090,7 +2090,7 @@ Accept wildcard characters: False
 
 ### -WorkloadType
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MigrationEndpoint.md b/exchange/exchange-ps/ExchangePowerShell/New-MigrationEndpoint.md
index 137f345d59..d71d215217 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-MigrationEndpoint.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-MigrationEndpoint.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -299,7 +299,7 @@ This example creates an IMAP migration endpoint that supports 50 concurrent migr
 
 ### -Name
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Name parameter specifies the name you give to the new migration endpoint. You can use the Name parameter when you run the New-MigrationBatch cmdlet.
 
@@ -317,7 +317,7 @@ Accept wildcard characters: False
 
 ### -Autodiscover
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 For an Exchange migration, the Autodiscover switch specifies whether to get other connection settings for the on-premises server from the Autodiscover service. You don't need to specify a value with this switch.
 
@@ -335,7 +335,7 @@ Accept wildcard characters: False
 
 ### -Compliance
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Compliance switch specifies that the endpoint type is compliance. You don't need to specify a value with this switch.
 
@@ -353,7 +353,7 @@ Accept wildcard characters: False
 
 ### -Credentials
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Credentials parameter specifies the credentials to connect to the source or target endpoint for all Exchange migration types.
 
@@ -373,7 +373,7 @@ Accept wildcard characters: False
 
 ### -EmailAddress
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The EmailAddress parameter specifies the email address used by the Autodiscover service or in some cases used to validate the endpoint when you specify the connection settings manually.
 
@@ -411,7 +411,7 @@ Accept wildcard characters: False
 
 ### -ExchangeRemoteMove
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ExchangeRemoteMove switch specifies the type of endpoint for cross-forest moves and remote move migrations in a hybrid deployment. You don't need to specify a value with this switch.
 
@@ -489,7 +489,7 @@ Accept wildcard characters: False
 
 ### -PSTImport
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -549,7 +549,7 @@ Accept wildcard characters: False
 
 ### -PublicFolderToUnifiedGroup
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The PublicFolderToUnifiedGroup switch specifies that the endpoint type is public folders to Microsoft 365 Groups. You don't need to specify a value with this switch.
 
@@ -567,7 +567,7 @@ Accept wildcard characters: False
 
 ### -RemoteServer
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RemoteServer parameter specifies the FQDN of the remote server, which depends on the protocol type for moves:
 
@@ -732,7 +732,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -753,7 +753,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -824,7 +824,7 @@ Accept wildcard characters: False
 
 ### -MaxConcurrentIncrementalSyncs
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MaxConcurrentIncrementalSyncs parameter specifies the maximum number of incremental syncs allowed per endpoint. The default value is 20.
 
@@ -842,7 +842,7 @@ Accept wildcard characters: False
 
 ### -MaxConcurrentMigrations
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MaxConcurrentMigrations parameter specifies the maximum number of mailboxes that are migrated during initial sync. This parameter is applicable for all migration types. The default value is 100.
 
@@ -980,7 +980,7 @@ Accept wildcard characters: False
 
 ### -SkipVerification
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SkipVerification switch specifies whether to skip verifying that the remote server is reachable when creating a migration endpoint. You don't need to specify a value with this switch.
 
@@ -1033,7 +1033,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MobileDeviceMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-MobileDeviceMailboxPolicy.md
index 8d609417e7..863ff11d57 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-MobileDeviceMailboxPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-MobileDeviceMailboxPolicy.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
 Locale: en-US
@@ -119,7 +119,7 @@ This example creates the mobile device mailbox policy Contoso Policy that has se
 
 ### -Name
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Name parameter specifies the name of the mobile device mailbox policy. You can use any value that uniquely identifies the policy. For example:
 
@@ -163,7 +163,7 @@ Accept wildcard characters: False
 
 ### -AllowBluetooth
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowBluetooth parameter specifies whether the Bluetooth capabilities are allowed on the mobile device. Valid values are:
 
@@ -189,7 +189,7 @@ Accept wildcard characters: False
 
 ### -AllowBrowser
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowBrowser parameter specifies whether Microsoft Pocket Internet Explorer is allowed on the mobile device. Valid input for this parameter is $true or $false. The default value is $true. This parameter doesn't affect non-Microsoft browsers.
 
@@ -207,7 +207,7 @@ Accept wildcard characters: False
 
 ### -AllowCamera
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowCamera parameter specifies whether the mobile device's camera is allowed. Valid input for this parameter is $true or $false. The default value is $true.
 
@@ -225,7 +225,7 @@ Accept wildcard characters: False
 
 ### -AllowConsumerEmail
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowConsumerEmail parameter specifies whether the user can configure a personal email account on the mobile device. Valid input for this parameter is $true or $false. The default value is $true. This parameter doesn't control access to email accounts using non-Microsoft mobile device email programs.
 
@@ -243,7 +243,7 @@ Accept wildcard characters: False
 
 ### -AllowDesktopSync
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowDesktopSync parameter specifies whether the mobile device can synchronize with a desktop computer through a cable. Valid input for this parameter is $true or $false. The default value is $true.
 
@@ -261,7 +261,7 @@ Accept wildcard characters: False
 
 ### -AllowExternalDeviceManagement
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowExternalDeviceManagement parameter specifies whether an external device management program is allowed to manage the mobile device. Valid input for this parameter is $true or $false. The default value is $false.
 
@@ -299,7 +299,7 @@ Accept wildcard characters: False
 
 ### -AllowHTMLEmail
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowHTMLEmail parameter specifies whether HTML-formatted email is enabled on the mobile device. Valid input for this parameter is $true or $false. The default value is $true. If set to $false, all email is converted to plain text before synchronization occurs.
 
@@ -317,7 +317,7 @@ Accept wildcard characters: False
 
 ### -AllowInternetSharing
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowInternetSharing parameter specifies whether the mobile device can be used as a modem to connect a computer to the Internet. This process is also known as tethering. Valid input for this parameter is $true or $false. The default value is $true.
 
@@ -335,7 +335,7 @@ Accept wildcard characters: False
 
 ### -AllowIrDA
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowIrDA parameter specifies whether infrared connections are allowed to the mobile device. Valid input for this parameter is $true or $false. The default value is $true.
 
@@ -373,7 +373,7 @@ Accept wildcard characters: False
 
 ### -AllowMobileOTAUpdate
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowMobileOTAUpdate parameter specifies whether the policy can be sent to the mobile device over a cellular data connection. Valid input for this parameter is $true or $false. The default value is $true.
 
@@ -391,7 +391,7 @@ Accept wildcard characters: False
 
 ### -AllowNonProvisionableDevices
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowNonProvisionableDevices parameter specifies whether all mobile devices can synchronize with Exchange. Valid input for this parameter is $true or $false. The default value is $true.
 
@@ -411,7 +411,7 @@ Accept wildcard characters: False
 
 ### -AllowPOPIMAPEmail
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowPOPIMAPEmail parameter specifies whether the user can configure a POP3 or IMAP4 email account on the mobile device. Valid input for this parameter is $true or $false. The default value is $true. This parameter doesn't control access by non-Microsoft email programs.
 
@@ -429,7 +429,7 @@ Accept wildcard characters: False
 
 ### -AllowRemoteDesktop
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowRemoteDesktop parameter specifies whether the mobile device can initiate a remote desktop connection. Valid input for this parameter is $true or $false. The default value is $true.
 
@@ -447,7 +447,7 @@ Accept wildcard characters: False
 
 ### -AllowSimplePassword
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowSimplePassword parameter specifies whether a simple password is allowed on the mobile device. A simple password is a password that has a specific pattern, such as 1111 or 1234. Valid input for this parameter is $true or $false. The default value is $true.
 
@@ -465,7 +465,7 @@ Accept wildcard characters: False
 
 ### -AllowSMIMEEncryptionAlgorithmNegotiation
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowSMIMEEncryptionAlgorithmNegotiation parameter specifies whether the messaging application on the mobile device can negotiate the encryption algorithm if a recipient's certificate doesn't support the specified encryption algorithm. Valid values for this parameter are:
 
@@ -489,7 +489,7 @@ Accept wildcard characters: False
 
 ### -AllowSMIMESoftCerts
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowSMIMESoftCerts parameter specifies whether S/MIME software certificates are allowed on the mobile device. Valid input for this parameter is $true or $false. The default value is $true.
 
@@ -507,7 +507,7 @@ Accept wildcard characters: False
 
 ### -AllowStorageCard
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowStorageCard parameter specifies whether the mobile device can access information stored on a storage card. Valid input for this parameter is $true or $false. The default value is $true.
 
@@ -525,7 +525,7 @@ Accept wildcard characters: False
 
 ### -AllowTextMessaging
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowTextMessaging parameter specifies whether text messaging is allowed from the mobile device. Valid input for this parameter is $true or $false. The default value is $true.
 
@@ -543,7 +543,7 @@ Accept wildcard characters: False
 
 ### -AllowUnsignedApplications
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowUnsignedApplications parameter specifies whether unsigned applications can be installed on the mobile device. Valid input for this parameter is $true or $false. The default value is $true.
 
@@ -561,7 +561,7 @@ Accept wildcard characters: False
 
 ### -AllowUnsignedInstallationPackages
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowUnsignedInstallationPackages parameter specifies whether unsigned installation packages are allowed to run on the mobile device. Valid input for this parameter is $true or $false. The default value is $true.
 
@@ -579,7 +579,7 @@ Accept wildcard characters: False
 
 ### -AllowWiFi
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowWiFi parameter specifies whether wireless Internet access is allowed on the mobile device. Valid input for this parameter is $true or $false. The default value is $true.
 
@@ -597,7 +597,7 @@ Accept wildcard characters: False
 
 ### -AlphanumericPasswordRequired
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AlphanumericPasswordRequired parameter specifies whether the password for the mobile device must be alphanumeric. Valid input for this parameter is $true or $false. The default value is $false.
 
@@ -615,7 +615,7 @@ Accept wildcard characters: False
 
 ### -ApprovedApplicationList
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ApprovedApplicationList parameter specifies a configured list of approved applications for the device.
 
@@ -633,7 +633,7 @@ Accept wildcard characters: False
 
 ### -AttachmentsEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AttachmentsEnabled parameter specifies whether attachments can be downloaded on the mobile device. Valid input for this parameter is $true or $false. The default value is $true.
 
@@ -653,7 +653,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -674,7 +674,7 @@ Accept wildcard characters: False
 
 ### -DeviceEncryptionEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 **Note**: This setting is supported by Outlook for iOS and Android.
 
@@ -696,7 +696,7 @@ Accept wildcard characters: False
 
 ### -DevicePolicyRefreshInterval
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DevicePolicyRefreshInterval parameter specifies how often the policy is sent to the mobile device.
 
@@ -718,7 +718,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -738,7 +738,7 @@ Accept wildcard characters: False
 
 ### -IrmEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IrmEnabled parameter specifies whether Information Rights Management (IRM) is enabled for the mobile device. Valid input for this parameter is $true or $false. The default value is $true.
 
@@ -756,7 +756,7 @@ Accept wildcard characters: False
 
 ### -IsDefault
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IsDefault parameter specifies whether this policy is the default mobile device mailbox policy. Valid input for this parameter is $true or $false. The default value for the built-in mobile device mailbox policy named Default is $true. The default value for new mobile device mailbox policies that you create is $false.
 
@@ -776,7 +776,7 @@ Accept wildcard characters: False
 
 ### -MaxAttachmentSize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MaxAttachmentSize parameter specifies the maximum size of attachments that can be downloaded to the mobile device. Valid input for this parameter is a size value between 0 and 2147482624 bytes (approximately 2 GB), or the value Unlimited. The default value is Unlimited.
 
@@ -802,7 +802,7 @@ Accept wildcard characters: False
 
 ### -MaxCalendarAgeFilter
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MaxCalendarAgeFilter parameter specifies the maximum range of calendar days that can be synchronized to the mobile device. Valid values for this parameter are:
 
@@ -828,7 +828,7 @@ Accept wildcard characters: False
 
 ### -MaxEmailAgeFilter
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MaxEmailAgeFilter parameter specifies the maximum number of days of email items to synchronize to the mobile device. Valid values for this parameter are:
 
@@ -855,7 +855,7 @@ Accept wildcard characters: False
 
 ### -MaxEmailBodyTruncationSize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MaxEmailBodyTruncationSize parameter specifies the maximum size at which email messages are truncated when synchronized to the mobile device. Valid input for this parameter is an integer between 0 and 2147483647 (Int32) or the value Unlimited. The default value is Unlimited.
 
@@ -875,7 +875,7 @@ Accept wildcard characters: False
 
 ### -MaxEmailHTMLBodyTruncationSize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MaxEmailHTMLBodyTruncationSize parameter specifies the maximum size at which HTML-formatted email messages are truncated when synchronized to the mobile device. Valid input for this parameter is an integer between 0 and 2147483647 (Int32) or the value Unlimited. The default value is Unlimited.
 
@@ -895,7 +895,7 @@ Accept wildcard characters: False
 
 ### -MaxInactivityTimeLock
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MaxInactivityTimeLock parameter specifies the length of time that the mobile device can be inactive before the password is required to reactivate it. Valid values are:
 
@@ -916,7 +916,7 @@ Accept wildcard characters: False
 
 ### -MaxPasswordFailedAttempts
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MaxPasswordFailedAttempts parameter specifies the number of attempts a user can make to enter the correct password for the mobile device.
 
@@ -936,7 +936,7 @@ Accept wildcard characters: False
 
 ### -MinPasswordComplexCharacters
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MinPasswordComplexCharacters parameter specifies the character sets that are required in the password of the mobile device. The character sets are:
 
@@ -970,7 +970,7 @@ Accept wildcard characters: False
 
 ### -MinPasswordLength
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 **Note**: This setting is supported by Outlook for Android.
 
@@ -992,7 +992,7 @@ Accept wildcard characters: False
 
 ### -PasswordEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The PasswordEnabled parameter specifies whether a password is required on the mobile device. Valid input for this parameter is $true or $false. The default value is $false.
 
@@ -1012,7 +1012,7 @@ Accept wildcard characters: False
 
 ### -PasswordExpiration
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The PasswordExpiration parameter specifies how long a password can be used on a mobile device before the user is forced to change the password. Valid values are:
 
@@ -1033,7 +1033,7 @@ Accept wildcard characters: False
 
 ### -PasswordHistory
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The PasswordHistory parameter specifies the number of unique new passwords that need to be created on the mobile device before an old password can be reused.
 
@@ -1053,7 +1053,7 @@ Accept wildcard characters: False
 
 ### -PasswordRecoveryEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The PasswordRecoveryEnabled parameter specifies whether the recovery password for the mobile device is stored in Exchange. Valid input for this parameter is $true or $false. The default value is $false.
 
@@ -1073,7 +1073,7 @@ Accept wildcard characters: False
 
 ### -RequireDeviceEncryption
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RequireDeviceEncryption parameter specifies whether encryption is required on the mobile device. Valid input for this parameter is $true or $false. The default value is $false.
 
@@ -1091,7 +1091,7 @@ Accept wildcard characters: False
 
 ### -RequireEncryptedSMIMEMessages
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RequireEncryptedSMIMEMessages parameter specifies whether the mobile device must send encrypted S/MIME messages. Valid input for this parameter is $true or $false. The default value is $false.
 
@@ -1109,7 +1109,7 @@ Accept wildcard characters: False
 
 ### -RequireEncryptionSMIMEAlgorithm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RequireEncryptionSMIMEAlgorithm parameter specifies the algorithm that's required to encrypt S/MIME messages on a mobile device. The valid values for this parameter are:
 
@@ -1135,7 +1135,7 @@ Accept wildcard characters: False
 
 ### -RequireManualSyncWhenRoaming
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RequireManualSyncWhenRoaming parameter specifies whether the mobile device must synchronize manually while roaming. Valid input for this parameter is $true or $false. The default value is $false.
 
@@ -1153,7 +1153,7 @@ Accept wildcard characters: False
 
 ### -RequireSignedSMIMEAlgorithm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RequireSignedSMIMEAlgorithm parameter specifies the algorithm that's used to sign S/MIME messages on the mobile device.
 
@@ -1173,7 +1173,7 @@ Accept wildcard characters: False
 
 ### -RequireSignedSMIMEMessages
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RequireSignedSMIMEMessages parameter specifies whether the mobile device must send signed S/MIME messages. Valid input for this parameter is $true or $false. The default value is $false.
 
@@ -1191,7 +1191,7 @@ Accept wildcard characters: False
 
 ### -RequireStorageCardEncryption
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RequireStorageCardEncryption parameter specifies whether storage card encryption is required on the mobile device. Valid input for this parameter is $true or $false. The default value is $false.
 
@@ -1211,7 +1211,7 @@ Accept wildcard characters: False
 
 ### -UnapprovedInROMApplicationList
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The UnapprovedInROMApplicationList parameter specifies a list of applications that can't be run in ROM on the mobile device.
 
@@ -1229,7 +1229,7 @@ Accept wildcard characters: False
 
 ### -UNCAccessEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The UNCAccessEnabled parameter specifies whether access to Microsoft Windows file shares is enabled from the mobile device. In on-premises Exchange organizations, access to specific shares is configured on the Exchange ActiveSync virtual directory.
 
@@ -1247,7 +1247,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
@@ -1265,7 +1265,7 @@ Accept wildcard characters: False
 
 ### -WSSAccessEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WSSAccessEnabled parameter specifies whether access to Microsoft Windows SharePoint Services is enabled from the mobile device. In on-premises Exchange organizations, access to specific shares is configured on the Exchange ActiveSync virtual directory.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-MoveRequest.md b/exchange/exchange-ps/ExchangePowerShell/New-MoveRequest.md
index f6067d134f..82a5bb8174 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-MoveRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-MoveRequest.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -285,7 +285,7 @@ This example creates a batch move request for all mailboxes on the database DB01
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the identity of the mailbox or mail user. You can use the following values:
 
@@ -311,7 +311,7 @@ Accept wildcard characters: False
 
 ### -Outbound
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Outbound switch specifies that this mailbox move is a cross-forest move and is being initiated from the source forest. You don't need to specify a value with this switch.
 
@@ -331,7 +331,7 @@ Accept wildcard characters: False
 
 ### -Remote
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Remote switch specifies that the move is outside of your organization and is being initiated from the target forest. You don't need to specify a value with this switch.
 
@@ -351,7 +351,7 @@ Accept wildcard characters: False
 
 ### -RemoteCredential
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RemoteCredential parameter specifies the username and password of an administrator who has permission to perform the mailbox move.
 
@@ -371,7 +371,7 @@ Accept wildcard characters: False
 
 ### -RemoteGlobalCatalog
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RemoteGlobalCatalog parameter specifies the fully qualified domain name (FQDN) of the global catalog server for the remote forest.
 
@@ -389,7 +389,7 @@ Accept wildcard characters: False
 
 ### -RemoteHostName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RemoteHostName parameter specifies the FQDN of the cross-forest organization from which you're moving the mailbox.
 
@@ -407,7 +407,7 @@ Accept wildcard characters: False
 
 ### -RemoteLegacy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -427,7 +427,7 @@ Accept wildcard characters: False
 
 ### -TargetDeliveryDomain
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The TargetDeliveryDomain parameter specifies the FQDN of the external email address created in the source forest for the mail-enabled user when the move request is complete. This parameter is allowed only when performing remote moves with the Remote, RemoteLegacy, or Outbound parameter.
 
@@ -445,7 +445,7 @@ Accept wildcard characters: False
 
 ### -AcceptLargeDataLoss
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AcceptLargeDataLoss switch specifies the request should continue even if a large number of items in the source mailbox can't be copied to the target mailbox. You don't need to specify a value with this switch.
 
@@ -467,7 +467,7 @@ Accept wildcard characters: False
 
 ### -AllowLargeItems
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -489,7 +489,7 @@ Accept wildcard characters: False
 
 ### -ArchiveDomain
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ArchiveDomain parameter specifies the FQDN of the external domain to which you're moving the archive. This parameter is used for moving the archive to a cloud-based service.
 
@@ -507,7 +507,7 @@ Accept wildcard characters: False
 
 ### -ArchiveOnly
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ArchiveOnly switch specifies that you're moving only the personal archive associated with the mailbox. You don't need to specify a value with this switch.
 
@@ -527,7 +527,7 @@ Accept wildcard characters: False
 
 ### -ArchiveTargetDatabase
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -553,7 +553,7 @@ Accept wildcard characters: False
 
 ### -BadItemLimit
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The BadItemLimit parameter specifies the maximum number of bad items that are allowed before the request fails. A bad item is a corrupt item in the source mailbox that can't be copied to the target mailbox. Also included in the bad item limit are missing items. Missing items are items in the source mailbox that can't be found in the target mailbox when the request is ready to complete.
 
@@ -577,7 +577,7 @@ Accept wildcard characters: False
 
 ### -BatchName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The BatchName parameter specifies a descriptive name for moving a batch of mailboxes. You can then use the name in the BatchName parameter as a search string when you use the Get-MoveRequest cmdlet.
 
@@ -595,7 +595,7 @@ Accept wildcard characters: False
 
 ### -CompleteAfter
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The CompleteAfter parameter specifies a delay before the request is completed. The request is started, but not completed until the date/time you specify with this parameter.
 
@@ -622,7 +622,7 @@ Accept wildcard characters: False
 
 ### -CompletedRequestAgeLimit
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The CompletedRequestAgeLimit parameter specifies how long the request are kept after it has completed before being automatically removed. The default CompletedRequestAgeLimit parameter value is 30 days.
 
@@ -640,7 +640,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -661,7 +661,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -681,7 +681,7 @@ Accept wildcard characters: False
 
 ### -DoNotPreserveMailboxSignature
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -703,7 +703,7 @@ Accept wildcard characters: False
 
 ### -ForceOffline
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ForceOffline switch forces the mailbox move to be performed in offline mode. You don't need to specify a value with this switch.
 
@@ -723,7 +723,7 @@ Accept wildcard characters: False
 
 ### -ForcePull
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -745,7 +745,7 @@ Accept wildcard characters: False
 
 ### -ForcePush
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -787,7 +787,7 @@ Accept wildcard characters: False
 
 ### -IncrementalSyncInterval
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IncrementalSyncInterval parameter specifies the wait time between incremental syncs. Use this parameter with the CompleteAfter parameter to create a move request that does periodic incremental syncs after the initial sync is complete.
 
@@ -809,7 +809,7 @@ Accept wildcard characters: False
 
 ### -InternalFlags
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -829,7 +829,7 @@ Accept wildcard characters: False
 
 ### -LargeItemLimit
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The LargeItemLimit parameter specifies the maximum number of large items that are allowed before the request fails. A large item is a message in the source mailbox that exceeds the maximum message size that's allowed in the target mailbox. If the target mailbox doesn't have a specifically configured maximum message size value, the organization-wide value is used.
 
@@ -858,7 +858,7 @@ Accept wildcard characters: False
 
 ### -MoveOptions
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MoveOptions parameter specifies the stages of the move that you want to skip for debugging purposes. Don't use this parameter unless you're directed to do so by Microsoft Customer Service and Support or specific documentation.
 
@@ -898,7 +898,7 @@ Accept wildcard characters: False
 
 ### -PreventCompletion
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The PreventCompletion switch specifies whether to run the move request, but not allow it to complete. You don't need to specify a value with this switch.
 
@@ -918,7 +918,7 @@ Accept wildcard characters: False
 
 ### -PrimaryOnly
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The PrimaryOnly switch specifies that the command should only move the primary mailbox (the personal archive isn't moved). You don't need to specify a value with this switch.
 
@@ -940,7 +940,7 @@ Accept wildcard characters: False
 
 ### -Priority
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -969,7 +969,7 @@ Accept wildcard characters: False
 
 ### -Protect
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1020,7 +1020,7 @@ Accept wildcard characters: False
 
 ### -RemoteArchiveTargetDatabase
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RemoteArchiveTargetDatabase parameter specifies the name of the target database in the remote forest to which you're moving the personal archive. Use this parameter when moving users with archives from the local forest to a remote forest. For moves from a remote forest to the local forest, use the ArchiveTargetDatabase parameter.
 
@@ -1058,7 +1058,7 @@ Accept wildcard characters: False
 
 ### -RemoteTargetDatabase
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RemoteTargetDatabase parameter specifies the name of the target database in the remote forest. Use this parameter when moving mailboxes from the local forest to a remote forest. For moves from a remote forest to the local forest, use the TargetDatabase parameter.
 
@@ -1078,7 +1078,7 @@ Accept wildcard characters: False
 
 ### -RequestExpiryInterval
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RequestExpiryInterval parameter specifies an age limit for a completed or failed request. When you use this parameter, the completed or failed request is automatically removed after the specified interval expires. If you don't use this parameter:
 
@@ -1103,7 +1103,7 @@ Accept wildcard characters: False
 
 ### -SkipMoving
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is replaced by the MoveOptions parameter.
 
@@ -1143,7 +1143,7 @@ Accept wildcard characters: False
 
 ### -StartAfter
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The StartAfter parameter specifies a delay before the request is started. The request isn't started until the date/time you specify with this parameter.
 
@@ -1170,7 +1170,7 @@ Accept wildcard characters: False
 
 ### -Suspend
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Suspend switch specifies whether to suspend the request. You don't need to specify a value with this switch.
 
@@ -1190,7 +1190,7 @@ Accept wildcard characters: False
 
 ### -SuspendComment
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SuspendComment parameter specifies a description about why the request was suspended. You can only use this parameter if you specify the Suspend parameter.
 
@@ -1208,7 +1208,7 @@ Accept wildcard characters: False
 
 ### -SuspendWhenReadyToComplete
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SuspendWhenReadyToComplete switch specifies whether to suspend the move request before it reaches the status of CompletionInProgress. You don't need to specify a value with this switch.
 
@@ -1228,7 +1228,7 @@ Accept wildcard characters: False
 
 ### -TargetDatabase
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1254,7 +1254,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
@@ -1274,7 +1274,7 @@ Accept wildcard characters: False
 
 ### -WorkloadType
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-OabVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/New-OabVirtualDirectory.md
index e521394787..33a5604517 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-OabVirtualDirectory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-OabVirtualDirectory.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -60,7 +60,7 @@ This example creates an OAB virtual directory on CASServer01 and configures the
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -81,7 +81,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -99,7 +99,7 @@ Accept wildcard characters: False
 
 ### -ExtendedProtectionFlags
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExtendedProtectionFlags parameter specifies custom settings for Extended Protection for Authentication on the virtual directory. Valid values are:
 
@@ -123,7 +123,7 @@ Accept wildcard characters: False
 
 ### -ExtendedProtectionSPNList
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExtendedProtectionSPNList parameter specifies a list of valid Service Principal Names (SPNs) if you're using Extended Protection for Authentication on the virtual directory. Valid values are:
 
@@ -144,7 +144,7 @@ Accept wildcard characters: False
 
 ### -ExtendedProtectionTokenChecking
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExtendedProtectionTokenChecking parameter defines how you want to use Extended Protection for Authentication on the virtual directory. Extended Protection for Authentication isn't enabled by default. Valid values are:
 
@@ -168,7 +168,7 @@ Accept wildcard characters: False
 
 ### -ExternalUrl
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExternalURL parameter specifies the URL that's used to connect to the virtual directory from outside the firewall.
 
@@ -186,7 +186,7 @@ Accept wildcard characters: False
 
 ### -InternalUrl
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The InternalURL parameter specifies the URL that's used to connect to the virtual directory from inside the firewall.
 
@@ -204,7 +204,7 @@ Accept wildcard characters: False
 
 ### -Path
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Path parameter specifies the file system path of the virtual directory. We recommend using this parameter only when you need to use a custom location for the virtual directory files. The default value is blank ($null), which indicates the default location is used.
 
@@ -222,7 +222,7 @@ Accept wildcard characters: False
 
 ### -PollInterval
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PollInterval parameter specifies the time interval in minutes that the distribution service polls the offline address book generation server for updates. The default value is 480 minutes (8 hours).
 
@@ -240,7 +240,7 @@ Accept wildcard characters: False
 
 ### -Recovery
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -258,7 +258,7 @@ Accept wildcard characters: False
 
 ### -RequireSSL
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RequireSSL parameter specifies whether the client connection to the virtual directory requires Secure Sockets Layer (SSL) encryption. Valid values are:
 
@@ -279,7 +279,7 @@ Accept wildcard characters: False
 
 ### -Role
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Role parameter species the configuration for the virtual directory. Valid values are:
 
@@ -302,7 +302,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Exchange server that hosts the virtual directory. You can use any value that uniquely identifies the server. For example:
 
@@ -325,7 +325,7 @@ Accept wildcard characters: False
 
 ### -WebSiteName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WebSiteName parameter specifies the name of the IIS website under which the virtual directory is created. You don't need to use this parameter to create the virtual directory under the default website.
 
@@ -343,7 +343,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-OfflineAddressBook.md b/exchange/exchange-ps/ExchangePowerShell/New-OfflineAddressBook.md
index 02ba871661..b2ca657dd6 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-OfflineAddressBook.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-OfflineAddressBook.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -91,7 +91,7 @@ If you configure OABs to use public folder distribution, but your organization d
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Name parameter specifies the unique name of the OAB. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks.
 
@@ -109,7 +109,7 @@ Accept wildcard characters: False
 
 ### -AddressLists
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AddressLists parameter specifies the address lists or global address lists that are included in the OAB. You can use any value that uniquely identifies the address list. For example:
 
@@ -135,7 +135,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -156,7 +156,7 @@ Accept wildcard characters: False
 
 ### -DiffRetentionPeriod
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DiffRetentionPeriod parameter specifies the number of days that the OAB difference files are stored on the server. Valid values are integers from 7 to 1825, or the value unlimited. The default value is 30.
 
@@ -174,7 +174,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -194,7 +194,7 @@ Accept wildcard characters: False
 
 ### -GeneratingMailbox
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -229,7 +229,7 @@ Accept wildcard characters: False
 
 ### -GlobalWebDistributionEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -254,7 +254,7 @@ Accept wildcard characters: False
 
 ### -IsDefault
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IsDefault parameter specifies whether the OAB is used by all mailboxes and mailbox databases that don't have an OAB specified. Valid values are:
 
@@ -388,7 +388,7 @@ Accept wildcard characters: False
 
 ### -ShadowMailboxDistributionEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -459,7 +459,7 @@ Accept wildcard characters: False
 
 ### -VirtualDirectories
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -493,7 +493,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-OrganizationRelationship.md b/exchange/exchange-ps/ExchangePowerShell/New-OrganizationRelationship.md
index 976f4da310..2bacdcf096 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-OrganizationRelationship.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-OrganizationRelationship.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
 Locale: en-US
@@ -93,7 +93,7 @@ The requesting organization only receives free/busy information with the time.
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Name parameter specifies the unique name of the organization relationship. The maximum length is 64 characters.
 
@@ -111,7 +111,7 @@ Accept wildcard characters: False
 
 ### -DomainNames
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The DomainNames parameter specifies the SMTP domains of the external organization. You can specify multiple domains separated by commas (for example, "contoso.com","northamerica.contoso.com"), limited to 238 domains in one request.
 
@@ -129,7 +129,7 @@ Accept wildcard characters: False
 
 ### -ArchiveAccessEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ArchiveAccessEnabled parameter specifies whether the organization relationship is configured to provide remote archive access. Valid values are:
 
@@ -150,7 +150,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -171,7 +171,7 @@ Accept wildcard characters: False
 
 ### -DeliveryReportEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The DeliveryReportEnabled parameter specifies whether Delivery Reports should be shared over the organization relationship. Valid values are:
 
@@ -194,7 +194,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -214,7 +214,7 @@ Accept wildcard characters: False
 
 ### -Enabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Enabled parameter specifies whether to enable the organization relationship. Valid values are:
 
@@ -235,7 +235,7 @@ Accept wildcard characters: False
 
 ### -FreeBusyAccessEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The FreeBusyAccessEnabled parameter specifies whether the organization relationship should be used to retrieve free/busy information from the external organization. Valid values are:
 
@@ -258,7 +258,7 @@ Accept wildcard characters: False
 
 ### -FreeBusyAccessLevel
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The FreeBusyAccessLevel parameter specifies the maximum amount of detail returned to the requesting organization. Valid values are:
 
@@ -282,7 +282,7 @@ Accept wildcard characters: False
 
 ### -FreeBusyAccessScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The FreeBusyAccessScope parameter specifies an internal mail-enabled security group where member free/busy information is accessible by the external organization. For best performance, the group should have less than 10,000 members. You can use any value that uniquely identifies the group. For example:
 
@@ -334,7 +334,7 @@ Accept wildcard characters: False
 
 ### -MailboxMoveEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The MailboxMoveEnabled parameter specifies whether the organization relationship enables moving mailboxes to or from the external organization. Valid values are:
 
@@ -384,7 +384,7 @@ Accept wildcard characters: False
 
 ### -MailTipsAccessEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The MailTipsAccessEnabled parameter specifies whether MailTips for users in this organization are returned over this organization relationship. Valid values are:
 
@@ -407,7 +407,7 @@ Accept wildcard characters: False
 
 ### -MailTipsAccessLevel
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The MailTipsAccessLevel parameter specifies the level of MailTips data that's externally shared over this organization relationship. This parameter can have the following values:
 
@@ -431,7 +431,7 @@ Accept wildcard characters: False
 
 ### -MailTipsAccessScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The MailTipsAccessScope parameter specifies a mail-enabled security group in the internal organization that contains users whose free/busy information is accessible by an external organization. You can use any value that uniquely identifies the group. For example:
 
@@ -486,7 +486,7 @@ Accept wildcard characters: False
 
 ### -OrganizationContact
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The OrganizationContact parameter specifies the email address that can be used to contact the external organization (for example, administrator@fourthcoffee.com).
 
@@ -504,7 +504,7 @@ Accept wildcard characters: False
 
 ### -PhotosEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The PhotosEnabled parameter specifies whether photos for users in the internal organization are returned over the organization relationship. Valid values are:
 
@@ -525,7 +525,7 @@ Accept wildcard characters: False
 
 ### -TargetApplicationUri
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The TargetApplicationUri parameter specifies the target Uniform Resource Identifier (URI) of the external organization. The TargetApplicationUri parameter is specified by Exchange when requesting a delegated token for the external organization to fetch free and busy information, for example, mail.contoso.com.
 
@@ -543,7 +543,7 @@ Accept wildcard characters: False
 
 ### -TargetAutodiscoverEpr
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The TargetAutodiscoverEpr parameter specifies the Autodiscover URL of Exchange Web Services for the external organization, for example, `https://contoso.com/autodiscover/autodiscover.svc/wssecurity`. Exchange uses the Autodiscover service to automatically detect the correct Exchange server endpoint to use for external requests.
 
@@ -561,7 +561,7 @@ Accept wildcard characters: False
 
 ### -TargetOwaURL
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The TargetOwaURL parameter specifies the Outlook on the web (formerly Outlook Web App) URL of the external organization defined in the organization relationship. It's used for Outlook on the web redirection in a cross-premise Exchange scenario. Configuring this attribute enables users in the organization to use their current Outlook on the web URL to access Outlook on the web in the external organization.
 
@@ -579,7 +579,7 @@ Accept wildcard characters: False
 
 ### -TargetSharingEpr
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The TargetSharingEpr parameter specifies the URL of the target Exchange Web Services for the external organization.
 
@@ -599,7 +599,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-OutlookProtectionRule.md b/exchange/exchange-ps/ExchangePowerShell/New-OutlookProtectionRule.md
index 05485cdd9b..a315c1af86 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-OutlookProtectionRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-OutlookProtectionRule.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -60,7 +60,7 @@ This example applies the AD RMS template named Template-Contoso to messages sent
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Name parameter specifies a name for the rule.
 
@@ -78,7 +78,7 @@ Accept wildcard characters: False
 
 ### -ApplyRightsProtectionTemplate
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ApplyRightsProtectionTemplate parameter specifies the AD RMS template to apply to the message. An AD RMS template can be specified using the template name. Use the Get-RMSTemplate cmdlet to retrieve templates from your AD RMS server.
 
@@ -96,7 +96,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -117,7 +117,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -137,7 +137,7 @@ Accept wildcard characters: False
 
 ### -Enabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Enabled parameter specifies whether the Outlook protection rules are enabled. New Outlook protection rules are enabled by default. To create a rule without enabling it, set the Enabled parameter to $false.
 
@@ -155,7 +155,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -175,7 +175,7 @@ Accept wildcard characters: False
 
 ### -FromDepartment
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The FromDepartment parameter specifies the sender's department as a condition. The user's department property is compared with the value specified.
 
@@ -193,7 +193,7 @@ Accept wildcard characters: False
 
 ### -Priority
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Priority parameter specifies whether to set the order of processing of Outlook protection rules. Rules with a lower priority value are executed first.
 
@@ -211,7 +211,7 @@ Accept wildcard characters: False
 
 ### -SentTo
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SentTo parameter specifies one or more recipients as a rule condition. You can use any value that uniquely identifies the internal recipient. For example:
 
@@ -244,7 +244,7 @@ Accept wildcard characters: False
 
 ### -SentToScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SentToScope parameter specifies the message scope as a condition. You can use one of the following values:
 
@@ -265,7 +265,7 @@ Accept wildcard characters: False
 
 ### -UserCanOverride
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The UserCanOverride parameter specifies whether users can override actions taken by Outlook protection rules. By default, users can override actions taken by Outlook protection rules. When set to $false, the UserCanOverride parameter prevents the user from overriding the rule when sending the message.
 
@@ -283,7 +283,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-OutlookProvider.md b/exchange/exchange-ps/ExchangePowerShell/New-OutlookProvider.md
index 9e7a811556..c3553a8334 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-OutlookProvider.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-OutlookProvider.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -54,7 +54,7 @@ This example creates the AutoDiscoverConfig object Autodiscover1 and the specifi
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Name parameter provides the common name of the AutoDiscoverConfig object. This can be a user-friendly name for identification.
 
@@ -72,7 +72,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -93,7 +93,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -111,7 +111,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-OwaMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-OwaMailboxPolicy.md
index c0311a932d..af02008a4c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-OwaMailboxPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-OwaMailboxPolicy.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.WebClient-Help.xml
 Locale: en-US
@@ -50,7 +50,7 @@ This example creates the Outlook on the web mailbox policy named Corporate.
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Name parameter specifies a name for the new policy.
 
@@ -68,7 +68,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -89,7 +89,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -131,7 +131,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-OwaVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/New-OwaVirtualDirectory.md
index e051fb1584..e8751f9b9f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-OwaVirtualDirectory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-OwaVirtualDirectory.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.WebClient-Help.xml
 Locale: en-US
@@ -80,7 +80,7 @@ Accept wildcard characters: False
 
 ### -ApplicationRoot
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ApplicationRoot parameter specifies the metabase path of the virtual directory. By default, this path is the same as the website in which the virtual directory is created.
 
@@ -98,7 +98,7 @@ Accept wildcard characters: False
 
 ### -AppPoolId
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AppPoolId parameter specifies the IIS application pool in which the virtual directory runs. We recommend that you leave this parameter at its default setting.
 
@@ -116,7 +116,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -137,7 +137,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -155,7 +155,7 @@ Accept wildcard characters: False
 
 ### -ExtendedProtectionFlags
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExtendedProtectionFlags parameter specifies custom settings for Extended Protection for Authentication on the virtual directory. Valid values are:
 
@@ -179,7 +179,7 @@ Accept wildcard characters: False
 
 ### -ExtendedProtectionSPNList
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExtendedProtectionSPNList parameter specifies a list of valid Service Principal Names (SPNs) if you're using Extended Protection for Authentication on the virtual directory. Valid values are:
 
@@ -200,7 +200,7 @@ Accept wildcard characters: False
 
 ### -ExtendedProtectionTokenChecking
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExtendedProtectionTokenChecking parameter defines how you want to use Extended Protection for Authentication on the virtual directory. Extended Protection for Authentication isn't enabled by default. Valid values are:
 
@@ -224,7 +224,7 @@ Accept wildcard characters: False
 
 ### -ExternalAuthenticationMethods
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExternalAuthenticationMethods parameter restricts the authentication methods that can be used to connect to the virtual directory from outside the firewall. Valid values are:
 
@@ -265,7 +265,7 @@ Accept wildcard characters: False
 
 ### -ExternalUrl
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExternalURL parameter specifies the URL that's used to connect to the virtual directory from outside the firewall. This setting is important when Secure Sockets Layer (SSL) is used.
 
@@ -283,7 +283,7 @@ Accept wildcard characters: False
 
 ### -InternalUrl
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The InternalURL parameter specifies the URL that's used to connect to the virtual directory from inside the firewall. This setting is important when SSL is used.
 
@@ -301,7 +301,7 @@ Accept wildcard characters: False
 
 ### -Path
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Path parameter specifies the file system path of the virtual directory. We recommend using this parameter only when you need to use a custom location for the virtual directory files. The default value is blank ($null), which indicates the default location is used.
 
@@ -319,7 +319,7 @@ Accept wildcard characters: False
 
 ### -Role
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Role parameter species the configuration for the virtual directory. Valid values are:
 
@@ -342,7 +342,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Exchange server that hosts the virtual directory. You can use any value that uniquely identifies the server. For example:
 
@@ -365,7 +365,7 @@ Accept wildcard characters: False
 
 ### -WebSiteName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WebSiteName parameter specifies the name of the IIS website under which the virtual directory is created. You don't need to use this parameter to create the virtual directory under the default website.
 
@@ -383,7 +383,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-PartnerApplication.md b/exchange/exchange-ps/ExchangePowerShell/New-PartnerApplication.md
index af5db2924b..272bdff3c4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-PartnerApplication.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-PartnerApplication.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -75,7 +75,7 @@ This example creates a new HRApp partner application named HRApp.
 
 ### -Name
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Name parameter specifies a name for the partner application.
 
@@ -93,7 +93,7 @@ Accept wildcard characters: False
 
 ### -ApplicationIdentifier
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ApplicationIdentifier parameter specifies a unique application identifier for the partner application that uses an authorization server. When specifying a value for the ApplicationIdentifier parameter, you must also use the UseAuthServer parameter.
 
@@ -111,7 +111,7 @@ Accept wildcard characters: False
 
 ### -AuthMetadataUrl
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -131,7 +131,7 @@ Accept wildcard characters: False
 
 ### -AcceptSecurityIdentifierInformation
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AcceptSecurityIdentifierInformation parameter specifies whether Exchange should accept security identifiers (SIDs) from another trusted Active Directory forest for the partner application. By default, new partner applications are configured to not accept SIDs from another forest. If you're in deployment with a trusted forest, set the parameter to $true.
 
@@ -149,7 +149,7 @@ Accept wildcard characters: False
 
 ### -AccountType
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AccountType parameter specifies the type of Microsoft account that's required for the partner application. Valid values are:
 
@@ -210,7 +210,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -231,7 +231,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -251,7 +251,7 @@ Accept wildcard characters: False
 
 ### -Enabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Enabled parameter specifies whether the partner application is enabled. By default, new partner applications are enabled. Set the parameter to $false to create the application configuration in a disabled state.
 
@@ -289,7 +289,7 @@ Accept wildcard characters: False
 
 ### -LinkedAccount
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The LinkedAccount parameter specifies a linked Active Directory user account for the application. Exchange evaluates Role Based Access Control (RBAC) permissions for the linked account when authorizing a token used to perform a task.
 
@@ -307,7 +307,7 @@ Accept wildcard characters: False
 
 ### -Realm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -327,7 +327,7 @@ Accept wildcard characters: False
 
 ### -TrustAnySSLCertificate
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -349,7 +349,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-PolicyTipConfig.md b/exchange/exchange-ps/ExchangePowerShell/New-PolicyTipConfig.md
index 0eb6102ca0..8fbaed382c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-PolicyTipConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-PolicyTipConfig.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -56,7 +56,7 @@ This example sets the informational URL in Policy Tips to the value `https://www
 
 ### -Name
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Name parameter specifies the custom Policy Tip you want to modify. Valid input for this parameter is one of the following values:
 
@@ -79,7 +79,7 @@ Accept wildcard characters: False
 
 ### -Value
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Value parameter specifies the text that's displayed by the Policy Tip. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -97,7 +97,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -118,7 +118,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -138,7 +138,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-PowerShellVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/New-PowerShellVirtualDirectory.md
index b79b93eb6b..e81c361881 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-PowerShellVirtualDirectory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-PowerShellVirtualDirectory.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -57,7 +57,7 @@ This example creates a Windows PowerShell virtual directory and configures it to
 
 ### -Name
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Name parameter specifies the name of the new PowerShell virtual directory. The name you provide has the name of the website it's created under appended to it. If the name you provide contains spaces, enclose the name in quotation marks (").
 
@@ -75,7 +75,7 @@ Accept wildcard characters: False
 
 ### -BasicAuthentication
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The BasicAuthentication parameter specifies whether Basic authentication is enabled on the PowerShell virtual directory. The valid values are $true and $false. The default value is $true.
 
@@ -93,7 +93,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -114,7 +114,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -132,7 +132,7 @@ Accept wildcard characters: False
 
 ### -ExtendedProtectionFlags
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExtendedProtectionFlags parameter specifies custom settings for Extended Protection for Authentication on the virtual directory. Valid values are:
 
@@ -156,7 +156,7 @@ Accept wildcard characters: False
 
 ### -ExtendedProtectionSPNList
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExtendedProtectionSPNList parameter specifies a list of valid Service Principal Names (SPNs) if you're using Extended Protection for Authentication on the virtual directory. Valid values are:
 
@@ -177,7 +177,7 @@ Accept wildcard characters: False
 
 ### -ExtendedProtectionTokenChecking
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExtendedProtectionTokenChecking parameter defines how you want to use Extended Protection for Authentication on the virtual directory. Extended Protection for Authentication isn't enabled by default. Valid values are:
 
@@ -201,7 +201,7 @@ Accept wildcard characters: False
 
 ### -ExternalUrl
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExternalUrl parameter specifies the external URL that the PowerShell virtual directory points to.
 
@@ -219,7 +219,7 @@ Accept wildcard characters: False
 
 ### -InternalUrl
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The InternalUrl parameter specifies the internal URL that the PowerShell virtual directory points to.
 
@@ -237,7 +237,7 @@ Accept wildcard characters: False
 
 ### -RequireSSL
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RequireSSL parameter specifies whether the PowerShell virtual directory should require that the client connection be made using Secure Sockets Layer (SSL). The valid values are $true and $false. The default value is $true.
 
@@ -255,7 +255,7 @@ Accept wildcard characters: False
 
 ### -Role
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Role parameter species the configuration for the virtual directory. Valid values are:
 
@@ -278,7 +278,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Exchange server that hosts the virtual directory. You can use any value that uniquely identifies the server. For example:
 
@@ -301,7 +301,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
@@ -319,7 +319,7 @@ Accept wildcard characters: False
 
 ### -WindowsAuthentication
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WindowsAuthentication parameter specifies whether Integrated Windows authentication is enabled on the PowerShell virtual directory. The valid values are $true and $false. The default value is $true.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-PublicFolder.md b/exchange/exchange-ps/ExchangePowerShell/New-PublicFolder.md
index 77226a0eca..736e45e5a7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-PublicFolder.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-PublicFolder.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.WebClient-Help.xml
 Locale: en-US
@@ -70,7 +70,7 @@ This example creates the public folder Support in the North\_America hierarchy p
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Name parameter specifies the name for the public folder.
 
@@ -88,7 +88,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -109,7 +109,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -129,7 +129,7 @@ Accept wildcard characters: False
 
 ### -EformsLocaleId
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The EformsLocaleId parameter specifies the locale-specific version of the e-forms library. The valid input for the EformsLocaleId parameter is the string names listed in the Culture Name column in the Microsoft .NET Class Library class reference available at [CultureInfo Class](https://learn.microsoft.com/dotnet/api/system.globalization.cultureinfo).
 
@@ -147,7 +147,7 @@ Accept wildcard characters: False
 
 ### -Mailbox
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Mailbox parameter specifies the hierarchy public folder mailbox where you want this public folder created. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -176,7 +176,7 @@ Accept wildcard characters: False
 
 ### -Path
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Path parameter specifies the location of the folder in the folder hierarchy, for example, \\Legal\\Cases.
 
@@ -221,7 +221,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-PublicFolderMigrationRequest.md b/exchange/exchange-ps/ExchangePowerShell/New-PublicFolderMigrationRequest.md
index e096e2cdf4..9aaa4ac222 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-PublicFolderMigrationRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-PublicFolderMigrationRequest.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -65,7 +65,7 @@ This example creates a public folder migration request from the Exchange 2010 so
 
 ### -Name
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Name parameter specifies the name of the public folder migration request. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -83,7 +83,7 @@ Accept wildcard characters: False
 
 ### -SourceDatabase
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SourceDatabase parameter specifies the target database for the public folders. You can use any value that uniquely identifies the database. For example:
 
@@ -105,7 +105,7 @@ Accept wildcard characters: False
 
 ### -AcceptLargeDataLoss
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AcceptLargeDataLoss switch specifies the request should continue even if a large number of items in the source mailbox can't be copied to the target mailbox. You don't need to specify a value with this switch.
 
@@ -125,7 +125,7 @@ Accept wildcard characters: False
 
 ### -BadItemLimit
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The BadItemLimit parameter specifies the maximum number of bad items that are allowed before the request fails. A bad item is a corrupt item in the source mailbox that can't be copied to the target mailbox. Also included in the bad item limit are missing items. Missing items are items in the source mailbox that can't be found in the target mailbox when the request is ready to complete.
 
@@ -145,7 +145,7 @@ Accept wildcard characters: False
 
 ### -BatchName
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The BatchName parameter specifies a descriptive name for the public folder migration batch. You can use the BatchName parameter as a search string when you use the Get-PublicFolderMigrationRequest cmdlet.
 
@@ -163,7 +163,7 @@ Accept wildcard characters: False
 
 ### -CompletedRequestAgeLimit
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The CompletedRequestAgeLimit parameter specifies how long the request is kept after it has completed before being automatically removed. The default CompletedRequestAgeLimit parameter value is 30 days.
 
@@ -181,7 +181,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -202,7 +202,7 @@ Accept wildcard characters: False
 
 ### -CSVData
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The CSVData parameter specifies the mapping file output generated by the PublicFoldertoMailboxMapGenerator.ps1 script. Use this parameter for local migrations.
 
@@ -224,7 +224,7 @@ Accept wildcard characters: False
 
 ### -CSVStream
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The CSVStream parameter specifies the mapping file output generated by the PublicFoldertoMailboxMapGenerator.ps1 script. Use this parameter for remote migrations.
 
@@ -244,7 +244,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -262,7 +262,7 @@ Accept wildcard characters: False
 
 ### -InternalFlags
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The InternalFlags parameter specifies the optional steps in the request. This parameter is used primarily for debugging purposes.
 
@@ -280,7 +280,7 @@ Accept wildcard characters: False
 
 ### -LargeItemLimit
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The LargeItemLimit parameter specifies the maximum number of large items that are allowed before the request fails. A large item is a message in the source mailbox that exceeds the maximum message size that's allowed in the target mailbox. If the target mailbox doesn't have a specifically configured maximum message size value, the organization-wide value is used.
 
@@ -307,7 +307,7 @@ Accept wildcard characters: False
 
 ### -MigrationMailbox
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -325,7 +325,7 @@ Accept wildcard characters: False
 
 ### -Priority
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Priority parameter specifies the order in which the request should be processed in the request queue. Requests are processed in order, based on server health, status, priority, and last update time. Valid priority values are:
 
@@ -352,7 +352,7 @@ Accept wildcard characters: False
 
 ### -RequestExpiryInterval
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RequestExpiryInterval parameter specifies an age limit for a completed or failed request. When you use this parameter, the completed or failed request is automatically removed after the specified interval expires. If you don't use this parameter:
 
@@ -377,7 +377,7 @@ Accept wildcard characters: False
 
 ### -SkipMerging
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SkipMerging parameter specifies whether certain stages of a public folder migration are skipped for debugging purposes. Don't use this parameter unless directed to do so by a Microsoft Customer Service and Support or specific documentation.
 
@@ -395,7 +395,7 @@ Accept wildcard characters: False
 
 ### -SourceEndpoint
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -413,7 +413,7 @@ Accept wildcard characters: False
 
 ### -Suspend
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Suspend switch specifies whether to suspend the request. You don't need to specify a value with this switch.
 
@@ -433,7 +433,7 @@ Accept wildcard characters: False
 
 ### -SuspendComment
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SuspendComment parameter specifies a description about why the request was suspended. You can only use this parameter if you specify the Suspend parameter.
 
@@ -451,7 +451,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
@@ -469,7 +469,7 @@ Accept wildcard characters: False
 
 ### -WorkloadType
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-PublicFolderMoveRequest.md b/exchange/exchange-ps/ExchangePowerShell/New-PublicFolderMoveRequest.md
index 94bd9c8323..49ddc0d274 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-PublicFolderMoveRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-PublicFolderMoveRequest.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -82,7 +82,7 @@ This example moves all public folders from public folder mailbox Pub1 to public
 
 ### -Folders
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Folders parameter specifies the public folders that you want to move. If the public folder has child public folders, these child public folders aren't moved unless you explicitly state them in the command. You can move multiple public folders by separating them with a comma, for example, \\Dev\\CustomerEngagements,\\Dev\\RequestsforChange,\\Dev\\Usability.
 
@@ -100,7 +100,7 @@ Accept wildcard characters: False
 
 ### -TargetMailbox
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The TargetMailbox parameter specifies the target public folder mailbox that you want to move the public folders to. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -129,7 +129,7 @@ Accept wildcard characters: False
 
 ### -AcceptLargeDataLoss
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AcceptLargeDataLoss switch specifies that the request should continue even if a large number of items in the source mailbox can't be copied to the target mailbox. You don't need to specify a value with this switch.
 
@@ -149,7 +149,7 @@ Accept wildcard characters: False
 
 ### -AllowLargeItems
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowLargeItems switch specifies that you can move large items only when they're encountered. You don't need to specify a value with this switch.
 
@@ -169,7 +169,7 @@ Accept wildcard characters: False
 
 ### -BadItemLimit
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The BadItemLimit parameter specifies the maximum number of bad items that are allowed before the request fails. A bad item is a corrupt item in the source mailbox that can't be copied to the target mailbox. Also included in the bad item limit are missing items. Missing items are items in the source mailbox that can't be found in the target mailbox when the request is ready to be completed.
 
@@ -189,7 +189,7 @@ Accept wildcard characters: False
 
 ### -CompletedRequestAgeLimit
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The CompletedRequestAgeLimit parameter specifies how long the request is kept after completion before being automatically removed. The default value for this parameter is 30 days.
 
@@ -207,7 +207,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -228,7 +228,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is functional only in on-premises Exchange.
 
@@ -248,7 +248,7 @@ Accept wildcard characters: False
 
 ### -InternalFlags
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The InternalFlags parameter specifies the optional steps in the request. This parameter is used primarily for debugging purposes.
 
@@ -266,7 +266,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Name parameter specifies the name of the public folder move request. If you don't specify a name, the default name is PublicFolderMove.
 
@@ -304,7 +304,7 @@ Accept wildcard characters: False
 
 ### -Priority
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Priority parameter specifies the order in which the request should be processed in the request queue. Requests are processed in order, based on server health, status, priority, and last update time. Valid priority values are:
 
@@ -331,7 +331,7 @@ Accept wildcard characters: False
 
 ### -RequestExpiryInterval
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RequestExpiryInterval parameter specifies an age limit for a completed or failed request. When you use this parameter, the completed or failed request is automatically removed after the specified interval expires. If you don't use this parameter:
 
@@ -356,7 +356,7 @@ Accept wildcard characters: False
 
 ### -Suspend
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Suspend switch specifies whether to suspend the request. You don't need to specify a value with this switch.
 
@@ -376,7 +376,7 @@ Accept wildcard characters: False
 
 ### -SuspendComment
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SuspendComment parameter specifies a description about why the request was suspended. You can only use this parameter if you specify the Suspend parameter.
 
@@ -394,7 +394,7 @@ Accept wildcard characters: False
 
 ### -SuspendWhenReadyToComplete
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -416,7 +416,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
@@ -434,7 +434,7 @@ Accept wildcard characters: False
 
 ### -WorkloadType
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WorkloadType parameter is reserved for internal Microsoft use.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ReceiveConnector.md b/exchange/exchange-ps/ExchangePowerShell/New-ReceiveConnector.md
index 99f534f8f4..62c23c91b2 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-ReceiveConnector.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-ReceiveConnector.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -403,7 +403,7 @@ It accepts incoming SMTP connections only from the IP range 192.168.0.1-192.168.
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Name parameter specifies the unique name for the Receive connector. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks.
 
@@ -421,7 +421,7 @@ Accept wildcard characters: False
 
 ### -Bindings
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Bindings parameter specifies the local IP address and TCP port number that's used by the Receive connector. This parameter uses the syntax `"IPv4Address:TCPPort","IPv6Address:TCPPort"`. You can specify an IPv4 address and port, an IPv6 address and port, or both. The IP address values 0.0.0.0 or `[::]` indicate that the Receive connector uses all available local IPv4 or all IPv6 addresses.
 
@@ -457,7 +457,7 @@ Accept wildcard characters: False
 
 ### -Client
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Client switch specifies the Client usage type for the Receive connector. You don't need to specify a value with this switch.
 
@@ -484,7 +484,7 @@ Accept wildcard characters: False
 
 ### -Internal
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Internal switch specifies the Internal usage type for the Receive connector. You don't need to specify a value with this switch.
 
@@ -511,7 +511,7 @@ Accept wildcard characters: False
 
 ### -Internet
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Internet switch specifies the Internet usage type for the Receive connector. You don't need to specify a value with this switch.
 
@@ -538,7 +538,7 @@ Accept wildcard characters: False
 
 ### -Partner
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Partner switch specifies the Partner usage type for the Receive connector. You don't need to specify a value with this switch.
 
@@ -565,7 +565,7 @@ Accept wildcard characters: False
 
 ### -RemoteIPRanges
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RemoteIPRanges parameter specifies the remote IP addresses that the Receive connector accepts messages from. Valid values are:
 
@@ -606,7 +606,7 @@ Accept wildcard characters: False
 
 ### -Usage
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Usage parameter specifies the default permission groups and authentication methods that are assigned to the Receive connector. Valid values are:
 
@@ -647,7 +647,7 @@ Accept wildcard characters: False
 
 ### -AdvertiseClientSettings
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AdvertiseClientSettings parameter specifies whether the SMTP server name, port number, and authentication settings for the Receive connector are displayed to users in the options of Outlook on the web. Valid values are:
 
@@ -668,7 +668,7 @@ Accept wildcard characters: False
 
 ### -AuthMechanism
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AuthMechanism parameter specifies the advertised and accepted authentication mechanisms for the Receive connector. Valid values are:
 
@@ -702,7 +702,7 @@ Accept wildcard characters: False
 
 ### -AuthTarpitInterval
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AuthTarpitInterval parameter specifies the period of time to delay responses to failed authentication attempts from remote servers that might be abusing the connection. The default value is 5 seconds.
 
@@ -726,7 +726,7 @@ Accept wildcard characters: False
 
 ### -Banner
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Banner parameter specifies a custom SMTP 220 banner that's displayed to remote messaging servers that connect to the Receive connector. When you specify a value, enclose the value in quotation marks, and start the value with 220 (the default "Service ready" SMTP response code).
 
@@ -748,7 +748,7 @@ Accept wildcard characters: False
 
 ### -BinaryMimeEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The BinaryMimeEnabled parameter specifies whether the BINARYMIME Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are:
 
@@ -771,7 +771,7 @@ Accept wildcard characters: False
 
 ### -ChunkingEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ChunkingEnabled parameter specifies whether the CHUNKING Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are:
 
@@ -794,7 +794,7 @@ Accept wildcard characters: False
 
 ### -Comment
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Comment parameter specifies an optional comment. If you specify a value that contains spaces, enclose the value in quotation marks ("), for example: "This is an admin note".
 
@@ -812,7 +812,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -833,7 +833,7 @@ Accept wildcard characters: False
 
 ### -ConnectionInactivityTimeout
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ConnectionInactivityTimeout parameter specifies the maximum amount of idle time before a connection to the Receive connector is closed.
 
@@ -859,7 +859,7 @@ Accept wildcard characters: False
 
 ### -ConnectionTimeout
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ConnectionTimeout parameter specifies the maximum time that the connection to the Receive connector can remain open, even if the connection is actively transmitting data.
 
@@ -885,7 +885,7 @@ Accept wildcard characters: False
 
 ### -Custom
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Custom switch specifies the Custom usage type for the Receive connector. You don't need to specify a value with this switch.
 
@@ -914,7 +914,7 @@ Accept wildcard characters: False
 
 ### -DefaultDomain
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DefaultDomain parameter specifies the default accepted domain to use for the Exchange organization. You can use any value that uniquely identifies the accepted domain. For example:
 
@@ -942,7 +942,7 @@ Accept wildcard characters: False
 
 ### -DeliveryStatusNotificationEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DeliveryStatusNotificationEnabled parameter specifies whether the DSN (delivery status notification) Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are:
 
@@ -965,7 +965,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -985,7 +985,7 @@ Accept wildcard characters: False
 
 ### -DomainSecureEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainSecureEnabled parameter specifies whether to enable or disable mutual Transport Layer Security (TLS) authentication (also known as Domain Secure) for the domains that are serviced by the Receive connector. Valid values are:
 
@@ -1014,7 +1014,7 @@ Accept wildcard characters: False
 
 ### -EightBitMimeEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The EightBitMimeEnabled parameter specifies whether the 8BITMIME Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are:
 
@@ -1037,7 +1037,7 @@ Accept wildcard characters: False
 
 ### -EnableAuthGSSAPI
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The EnableAuthGSSAPI parameter enables or disables Kerberos when Integrated Windows authentication is available on the Receive connector (the AuthMechanism parameter contains the value Integrated). Valid values are:
 
@@ -1060,7 +1060,7 @@ Accept wildcard characters: False
 
 ### -Enabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Enabled parameter specifies whether to enable or disable the Receive connector. Valid values are:
 
@@ -1081,7 +1081,7 @@ Accept wildcard characters: False
 
 ### -EnhancedStatusCodesEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The EnhancedStatusCodesEnabled parameter specifies whether the ENHANCEDSTATUSCODES Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are:
 
@@ -1104,7 +1104,7 @@ Accept wildcard characters: False
 
 ### -ExtendedProtectionPolicy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExtendedProtectionPolicy parameter specifies how Extended Protection for Authentication is implemented on the Receive connector. Valid values are:
 
@@ -1128,7 +1128,7 @@ Accept wildcard characters: False
 
 ### -Fqdn
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Fqdn parameter specifies the destination FQDN that's shown to connected messaging servers. This value is used in the following locations:
 
@@ -1153,7 +1153,7 @@ Accept wildcard characters: False
 
 ### -LongAddressesEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The LongAddressesEnabled parameter specifies whether the Receive connector accepts long X.400 email addresses. The X.400 email addresses are encapsulated in SMTP email addresses by using the Internet Mail Connector Encapsulated Address (IMCEA) encapsulation method. Valid values are
 
@@ -1182,7 +1182,7 @@ Accept wildcard characters: False
 
 ### -MaxAcknowledgementDelay
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter isn't used by Exchange Server 2016. It's used only by Exchange 2010 servers in coexistence environments.
 
@@ -1206,7 +1206,7 @@ Accept wildcard characters: False
 
 ### -MaxHeaderSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MaxHeaderSize parameter specifies the maximum size of the SMTP message header before the Receive connector closes the connection. The default value is 256 kilobytes (262144 bytes).
 
@@ -1235,7 +1235,7 @@ Accept wildcard characters: False
 
 ### -MaxHopCount
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MaxHopCount parameter specifies the maximum number of hops that a message can take before the message is rejected by the Receive connector. The maximum number of hops is determined by the number of Received header fields that exist in a submitted message.
 
@@ -1255,7 +1255,7 @@ Accept wildcard characters: False
 
 ### -MaxInboundConnection
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MaxInboundConnection parameter specifies the maximum number of inbound connections that this Receive connector serves at the same time.
 
@@ -1277,7 +1277,7 @@ Accept wildcard characters: False
 
 ### -MaxInboundConnectionPercentagePerSource
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MaxInboundConnectionPercentagePerSource parameter specifies the maximum number of connections that a Receive connector serves at the same time from a single IP address, expressed as the percentage of available remaining connections on a Receive connector.
 
@@ -1297,7 +1297,7 @@ Accept wildcard characters: False
 
 ### -MaxInboundConnectionPerSource
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MaxInboundConnectionPerSource parameter specifies the maximum number of connections that this Receive connector serves at the same time from a single IP address.
 
@@ -1319,7 +1319,7 @@ Accept wildcard characters: False
 
 ### -MaxLocalHopCount
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MaxLocalHopCount parameter specifies the maximum number of local hops that a message can take before the message is rejected by the Receive connector. The maximum number of local hops is determined by the number of Received headers with local server addresses in a submitted message.
 
@@ -1341,7 +1341,7 @@ Accept wildcard characters: False
 
 ### -MaxLogonFailures
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MaxLogonFailures parameter specifies the number of logon failures that the Receive connector retries before it closes the connection.
 
@@ -1363,7 +1363,7 @@ Accept wildcard characters: False
 
 ### -MaxMessageSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MaxMessageSize parameter specifies the maximum size of a message that's allowed through the Receive connector. The default value is 36 MB, which results in a realistic maximum message size of 25 MB.
 
@@ -1394,7 +1394,7 @@ Accept wildcard characters: False
 
 ### -MaxProtocolErrors
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MaxProtocolErrors parameter specifies the maximum number of SMTP protocol errors that the Receive connector accepts before closing the connection.
 
@@ -1416,7 +1416,7 @@ Accept wildcard characters: False
 
 ### -MaxRecipientsPerMessage
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MaxRecipientsPerMessage parameter specifies the maximum number of recipients per message that the Receive connector accepts before closing the connection.
 
@@ -1436,7 +1436,7 @@ Accept wildcard characters: False
 
 ### -MessageRateLimit
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MessageRateLimit parameter specifies the maximum number of messages that can be sent by a single client IP address per minute.
 
@@ -1460,7 +1460,7 @@ Accept wildcard characters: False
 
 ### -MessageRateSource
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MessageRateSource parameter specifies how the message submission rate is calculated. Valid values are:
 
@@ -1483,7 +1483,7 @@ Accept wildcard characters: False
 
 ### -OrarEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The OrarEnabled parameter enables or disables Originator Requested Alternate Recipient (ORAR) on the Receive connector. Valid values are:
 
@@ -1506,7 +1506,7 @@ Accept wildcard characters: False
 
 ### -PermissionGroups
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PermissionGroups parameter specifies the well-known security principals who are authorized to use the Receive connector, and the permissions that are assigned to them. Valid values are:
 
@@ -1538,7 +1538,7 @@ Accept wildcard characters: False
 
 ### -PipeliningEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PipeliningEnabled parameter specifies whether the PIPELINING Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are:
 
@@ -1561,7 +1561,7 @@ Accept wildcard characters: False
 
 ### -ProtocolLoggingLevel
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ProtocolLoggingLevel parameter specifies whether to enable or disable protocol logging for the Receive connector. Valid values are:
 
@@ -1584,7 +1584,7 @@ Accept wildcard characters: False
 
 ### -RejectReservedSecondLevelRecipientDomains
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RejectReservedSecondLevelRecipientDomains parameter specifies whether to reject connections that contain recipients in reserved second-level domains as specified in RFC 2606 (example.com, example.net, or example.org). Valid value are:
 
@@ -1605,7 +1605,7 @@ Accept wildcard characters: False
 
 ### -RejectReservedTopLevelRecipientDomains
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RejectReservedTopLevelRecipientDomains parameter specifies whether to reject connections that contain recipients in reserved top-level domains (TLDs) as specified in RFC 2606 (.test, .example, .invalid, or .localhost). Valid value are:
 
@@ -1626,7 +1626,7 @@ Accept wildcard characters: False
 
 ### -RejectSingleLabelRecipientDomains
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RejectSingleLabelRecipientDomains parameter specifies whether to reject connections that contain recipients in single-label domains (for example, chris@contoso instead of chris@contoso.com). Valid values are:
 
@@ -1647,7 +1647,7 @@ Accept wildcard characters: False
 
 ### -RequireEHLODomain
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RequireEHLODomain parameter specifies whether the client must provide a domain name in the EHLO handshake after the SMTP connection is established. Valid values are:
 
@@ -1668,7 +1668,7 @@ Accept wildcard characters: False
 
 ### -RequireTLS
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RequireTLS parameter specifies whether to require TLS transmission for inbound messages on the Receive connector. Valid values are:
 
@@ -1689,7 +1689,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
 
@@ -1714,7 +1714,7 @@ Accept wildcard characters: False
 
 ### -ServiceDiscoveryFqdn
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ServiceDiscoveryFqdn parameter specifies the service discovery fully-qualified domain name (FQDN) for the Receive connector.
 
@@ -1732,7 +1732,7 @@ Accept wildcard characters: False
 
 ### -SizeEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SizeEnabled parameter specifies how the SIZE Extended SMTP extension is used on the Receive connector. Valid values are:
 
@@ -1756,7 +1756,7 @@ Accept wildcard characters: False
 
 ### -SuppressXAnonymousTls
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SuppressXAnonymousTls parameter specifies whether the X-ANONYMOUSTLS Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are:
 
@@ -1779,7 +1779,7 @@ Accept wildcard characters: False
 
 ### -TarpitInterval
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TarpitInterval parameter specifies the amount of time to delay an SMTP response to a remote server that might be abusing the connection. The default value is 00:00:05 (5 seconds).
 
@@ -1803,7 +1803,7 @@ Accept wildcard characters: False
 
 ### -TlsCertificateName
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TlsCertificateName parameter specifies the X.509 certificate to use for TLS encryption. A valid value for this parameter is `"<I>X.500Issuer<S>X.500Subject"`. The X.500Issuer value is found in the certificate's Issuer field, and the X.500Subject value is found in the certificate's Subject field. You can find these values by running the Get-ExchangeCertificate cmdlet. Or, after you run Get-ExchangeCertificate to find the thumbprint value of the certificate, run the command `$TLSCert = Get-ExchangeCertificate -Thumbprint <Thumbprint>`, run the command `$TLSCertName = "<I>$($TLSCert.Issuer)<S>$($TLSCert.Subject)"`, and then use the value $TLSCertName for this parameter.
 
@@ -1821,7 +1821,7 @@ Accept wildcard characters: False
 
 ### -TlsDomainCapabilities
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TlsDomainCapabilities parameter specifies the capabilities that the Receive connector makes available to specific hosts outside of the organization. Remote hosts are authenticated with TLS with certificate validation before these capabilities are offered.
 
@@ -1854,7 +1854,7 @@ Accept wildcard characters: False
 
 ### -TransportRole
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TransportRole parameter specifies the transport service on the Mailbox server where the Receive connector is created. Valid values are:
 
@@ -1875,7 +1875,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-RemoteDomain.md b/exchange/exchange-ps/ExchangePowerShell/New-RemoteDomain.md
index 2b47aa2592..3a98055162 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-RemoteDomain.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-RemoteDomain.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -45,7 +45,7 @@ This example creates the remote domain named Contoso for the domain contoso.com
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Name parameter specifies a unique name for the remote domain object. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -63,7 +63,7 @@ Accept wildcard characters: False
 
 ### -DomainName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DomainName parameter specifies the SMTP domain that you want to establish as a remote domain. A valid value is an SMTP domain (for example, contoso.com). The maximum length is 256 characters.
 
@@ -83,7 +83,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -104,7 +104,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -126,7 +126,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-RemoteMailbox.md b/exchange/exchange-ps/ExchangePowerShell/New-RemoteMailbox.md
index ad9e5e75d8..f6ce23c884 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-RemoteMailbox.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-RemoteMailbox.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -196,7 +196,7 @@ As in Example 1, this example assumes that mail flow and directory synchronizati
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Name parameter specifies the unique name of the on-premises mail user and the associated mailbox in the service. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -214,7 +214,7 @@ Accept wildcard characters: False
 
 ### -AccountDisabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AccountDisabled switch specifies whether to create the mail user in a disabled state. You don't need to specify a value with this switch.
 
@@ -232,7 +232,7 @@ Accept wildcard characters: False
 
 ### -Equipment
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Equipment switch specifies that the mailbox in the service should be created as an equipment resource mailbox. You don't need to specify a value with this switch.
 
@@ -254,7 +254,7 @@ Accept wildcard characters: False
 
 ### -Password
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Password parameter specifies the password used by the mail user to secure his or her account and associated mailbox in the service.
 
@@ -278,7 +278,7 @@ Accept wildcard characters: False
 
 ### -Room
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Room switch specifies that the mailbox in the service should be created as a room resource mailbox. You don't need to specify a value with this switch.
 
@@ -298,7 +298,7 @@ Accept wildcard characters: False
 
 ### -Shared
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 **Note**: This switch is available only in Exchange 2013 CU21 or later and Exchange 2016 CU10 or later. To use this switch, you also need to run setup.exe /PrepareAD. For more information, see [KB4133605](https://support.microsoft.com/help/4133605).
 
@@ -320,7 +320,7 @@ Accept wildcard characters: False
 
 ### -UserPrincipalName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The UserPrincipalName parameter specifies the logon name for the user account. The UPN uses an email address format: `username@domain`. Typically, the domain value is the domain where the user account resides.
 
@@ -338,7 +338,7 @@ Accept wildcard characters: False
 
 ### -ACLableSyncedObjectEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ACLableSyncedObjectEnabled switch specifies whether the remote mailbox is an ACLableSyncedMailboxUser. You don't need to specify a value with this switch.
 
@@ -356,7 +356,7 @@ Accept wildcard characters: False
 
 ### -Alias
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Alias parameter specifies the Exchange alias (also known as the mail nickname) for the recipient. This value identifies the recipient as a mail-enabled object, and shouldn't be confused with multiple email addresses for the same recipient (also known as proxy addresses). A recipient can have only one Alias value. The maximum length is 64 characters.
 
@@ -392,7 +392,7 @@ Accept wildcard characters: False
 
 ### -Archive
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Archive switch specifies whether to also create an archive mailbox in the service. You don't need to specify a value with this switch.
 
@@ -410,7 +410,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -431,7 +431,7 @@ Accept wildcard characters: False
 
 ### -DisplayName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DisplayName parameter specifies the display name of the mail user and the associated mailbox in the service. The display name is visible in the Exchange admin center, in address lists, and in Outlook. The maximum length is 256 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -451,7 +451,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -469,7 +469,7 @@ Accept wildcard characters: False
 
 ### -FirstName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The FirstName parameter specifies the user's first name.
 
@@ -487,7 +487,7 @@ Accept wildcard characters: False
 
 ### -ImmutableId
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ImmutableId parameter is used by GAL synchronization (GALSync) and specifies a unique and immutable identifier in the form of an SMTP address for an Exchange mailbox used for federated delegation when requesting Security Assertion Markup Language (SAML) tokens. If federation is configured for this mailbox and you don't set this parameter when you create the mailbox, Exchange creates the value for the immutable ID based upon the mailbox's ExchangeGUID and the federated account namespace, for example, 7a78e7c8-620e-4d85-99d3-c90d90f29699@mail.contoso.com.
 
@@ -507,7 +507,7 @@ Accept wildcard characters: False
 
 ### -Initials
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Initials parameter specifies the user's middle initials.
 
@@ -525,7 +525,7 @@ Accept wildcard characters: False
 
 ### -LastName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The LastName parameter specifies the user's last name.
 
@@ -543,7 +543,7 @@ Accept wildcard characters: False
 
 ### -ModeratedBy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ModeratedBy parameter specifies one or more moderators for this recipient. A moderator approves messages sent to the recipient before the messages are delivered. A moderator must be a mailbox, mail user, or mail contact in your organization. You can use any value that uniquely identifies the moderator. For example:
 
@@ -572,7 +572,7 @@ Accept wildcard characters: False
 
 ### -ModerationEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ModerationEnabled parameter specifies whether moderation is enabled for this recipient. Valid value are:
 
@@ -595,7 +595,7 @@ Accept wildcard characters: False
 
 ### -OnPremisesOrganizationalUnit
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The OnPremisesOrganizationalUnit parameter specifies the organizational unit (OU) in the on-premises organization in which the new mailbox is added (for example, redmond.contoso.com/Users).
 
@@ -622,7 +622,7 @@ Accept wildcard characters: False
 
 ### -PrimarySmtpAddress
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PrimarySmtpAddress parameter specifies the primary return email address that's used for the recipient.
 
@@ -640,7 +640,7 @@ Accept wildcard characters: False
 
 ### -RemotePowerShellEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RemotePowerShellEnabled parameter specifies whether the user has access to Exchange PowerShell. Valid values are:
 
@@ -665,7 +665,7 @@ Accept wildcard characters: False
 
 ### -RemoteRoutingAddress
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RemoteRoutingAddress parameter specifies the SMTP address of the mailbox in the service that this user is associated with. This address is created automatically when the service is initially configured in the format of `<your domain>.mail.onmicrosoft.com`.
 
@@ -685,7 +685,7 @@ Accept wildcard characters: False
 
 ### -ResetPasswordOnNextLogon
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ResetPasswordOnNextLogon parameter specifies whether the user must change their password the next time they log on. Valid values are:
 
@@ -706,7 +706,7 @@ Accept wildcard characters: False
 
 ### -SamAccountName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SamAccountName parameter (also known as the pre-Windows 2000 user account or group name) specifies an object identifier that's compatible with older versions of Microsoft Windows client and server operating systems. The value can contain letters, numbers, spaces, periods (.), and the following characters: !, #, $, %, ^, &, -, \_, {, }, and ~. The last character can't be a period. Unicode characters are allowed, but accented characters might generate collisions (for example, o and ö match). The maximum length is 20 characters.
 
@@ -724,7 +724,7 @@ Accept wildcard characters: False
 
 ### -SendModerationNotifications
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SendModerationNotifications parameter specifies when moderation notification messages are sent. Valid values are:
 
@@ -748,7 +748,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-RetentionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-RetentionPolicy.md
index e52f0a2909..de98de144a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-RetentionPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-RetentionPolicy.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
 Locale: en-US
@@ -60,7 +60,7 @@ The second retention tag, which is named Legal, is also enclosed in quotation ma
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Name parameter specifies the policy name.
 
@@ -78,7 +78,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -99,7 +99,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -170,7 +170,7 @@ Accept wildcard characters: False
 
 ### -RetentionId
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RetentionId parameter specifies the identity of the retention policy to ensure mailboxes moved from an on-premises Exchange deployment to the cloud continue to have the same retention policy applied to them. The RetentionId parameter is used in cross-premises deployments. You don't need to specify this parameter in on-premises-only deployments.
 
@@ -188,7 +188,7 @@ Accept wildcard characters: False
 
 ### -RetentionPolicyTagLinks
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RetentionPolicyTagLinks parameter specifies the names of retention policy tags to be associated with this policy.
 
@@ -206,7 +206,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-RetentionPolicyTag.md b/exchange/exchange-ps/ExchangePowerShell/New-RetentionPolicyTag.md
index cd0aad232e..3756a19d8b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-RetentionPolicyTag.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-RetentionPolicyTag.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
 Locale: en-US
@@ -101,7 +101,7 @@ This example creates the retention tag Business Critical of type Personal. When
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Name parameter specifies the name of the tag.
 
@@ -139,7 +139,7 @@ Accept wildcard characters: False
 
 ### -AgeLimitForRetention
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AgeLimitForRetention parameter specifies the age at which retention is enforced on an item. The age limit corresponds to the number of days from the date the item was delivered, or the date an item was created if it wasn't delivered. If this parameter isn't present and the RetentionEnabled parameter is set to $true, an error is returned.
 
@@ -157,7 +157,7 @@ Accept wildcard characters: False
 
 ### -Comment
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Comment parameter specifies a comment for the tag.
 
@@ -175,7 +175,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -196,7 +196,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -296,7 +296,7 @@ Accept wildcard characters: False
 
 ### -LocalizedComment
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The LocalizedComment parameter specifies localized comments and their languages. When the user's language setting matches a language specified for this parameter, Microsoft Outlook and Outlook on the web display the corresponding localized comment. Comments are specified in the form of ISO Language Code:Comment, for example, LocalizedComment EN-US:"This is a localized comment in U.S. English".
 
@@ -314,7 +314,7 @@ Accept wildcard characters: False
 
 ### -LocalizedRetentionPolicyTagName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The LocalizedRetentionPolicyTagName parameter specifies localized tag names and their languages. When the user's language setting matches a language specified for this parameter, Outlook and Outlook on the web display the corresponding localized tag name. Names are specified in the form of ISO Language Code:Name, for example, LocalizedRetentionPolicyTagName EN-US:"Business Critical".
 
@@ -332,7 +332,7 @@ Accept wildcard characters: False
 
 ### -ManagedFolderToUpgrade
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -352,7 +352,7 @@ Accept wildcard characters: False
 
 ### -MessageClass
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MessageClass parameter specifies the message type to which the tag applies. If not specified, the default value is set to \*.
 
@@ -396,7 +396,7 @@ Accept wildcard characters: False
 
 ### -MustDisplayCommentEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MustDisplayCommentEnabled parameter specifies whether the comment can be hidden. The default value is $true.
 
@@ -414,7 +414,7 @@ Accept wildcard characters: False
 
 ### -RetentionAction
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RetentionAction parameter specifies the action for the retention policy. Valid values are:
 
@@ -441,7 +441,7 @@ Accept wildcard characters: False
 
 ### -RetentionEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RetentionEnabled parameter specifies whether the tag is enabled. When set to $false, the tag is disabled, and no retention action is taken on messages that have the tag applied.
 
@@ -463,7 +463,7 @@ Accept wildcard characters: False
 
 ### -RetentionId
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RetentionId parameter specifies an alternate tag ID to make sure the retention tag found on mailbox items tagged in an on-premises deployment matches the tag when the mailbox is moved to the cloud, or mailbox items tagged in the cloud match the tag when the mailbox is moved to an on-premises Exchange server. The parameter is used in cross-premises deployments. You don't need to specify this parameter in on-premises-only deployments.
 
@@ -481,7 +481,7 @@ Accept wildcard characters: False
 
 ### -SystemTag
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SystemTag parameter specifies that the tag is created for internal Exchange functionality.
 
@@ -499,7 +499,7 @@ Accept wildcard characters: False
 
 ### -Type
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Type parameter specifies the type of retention tag being created. Valid values include:
 
@@ -541,7 +541,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-RoleAssignmentPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-RoleAssignmentPolicy.md
index fcd51b4f49..eef83073bd 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-RoleAssignmentPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-RoleAssignmentPolicy.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -76,7 +76,7 @@ Because setting the new role assignment as default applies only to new mailboxes
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Name parameter specifies the name of the new assignment policy. If the assignment policy name contains spaces, enclose the name in quotation marks ("). The maximum length of the name is 64 characters.
 
@@ -94,7 +94,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -115,7 +115,7 @@ Accept wildcard characters: False
 
 ### -Description
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Description parameter specifies the description that's displayed when the role assignment policy is viewed using the Get-RoleAssignmentPolicy cmdlet. Enclose the description in quotation marks (").
 
@@ -133,7 +133,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -155,7 +155,7 @@ Accept wildcard characters: False
 
 ### -IsDefault
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The IsDefault switch makes the assignment policy the default assignment policy. You don't need to specify a value with this switch.
 
@@ -177,7 +177,7 @@ Accept wildcard characters: False
 
 ### -Roles
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Roles parameter specifies the management roles to assign to the role assignment policy when it's created. If a role name contains spaces, enclose the name in quotation marks ("). If you want to assign more that one role, separate the role names with commas.
 
@@ -197,7 +197,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-RoleGroup.md b/exchange/exchange-ps/ExchangePowerShell/New-RoleGroup.md
index ac057d2934..35d6bdc6ef 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-RoleGroup.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-RoleGroup.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -129,7 +129,7 @@ This example removes the role assignment between the Distribution Groups managem
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The Name parameter specifies the name of the new role group. The name can have a maximum of 64 characters. If the name contains spaces, enclose the name in quotation marks (").
 
@@ -149,7 +149,7 @@ Accept wildcard characters: False
 
 ### -LinkedDomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -171,7 +171,7 @@ Accept wildcard characters: False
 
 ### -LinkedForeignGroup
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -193,7 +193,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -214,7 +214,7 @@ Accept wildcard characters: False
 
 ### -CustomConfigWriteScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -234,7 +234,7 @@ Accept wildcard characters: False
 
 ### -CustomRecipientWriteScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The CustomRecipientWriteScope parameter specifies the existing recipient-based management scope to associate with management role assignments created with this role group. If the management scope name contains spaces, enclose the name in quotation marks (").
 
@@ -256,7 +256,7 @@ Accept wildcard characters: False
 
 ### -Description
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The Description parameter specifies the description that's displayed when the role group is viewed using the Get-RoleGroup cmdlet. Enclose the description in quotation marks (").
 
@@ -274,7 +274,7 @@ Accept wildcard characters: False
 
 ### -DisplayName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The DisplayName parameter specifies the friendly name of the role group. If the name contains spaces, enclose the name in quotation marks ("). This parameter has a maximum length of 256 characters.
 
@@ -292,7 +292,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -354,7 +354,7 @@ Accept wildcard characters: False
 
 ### -LinkedCredential
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -376,7 +376,7 @@ Accept wildcard characters: False
 
 ### -ManagedBy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ManagedBy parameter specifies the users or USGs who can modify the configuration of a role group or add and remove members to or from a role group.
 
@@ -398,7 +398,7 @@ Accept wildcard characters: False
 
 ### -Members
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The Members parameter specifies the mailboxes or mail-enabled USGs to add as a member of the role group. You can identify the user or group by the name, DN, or primary SMTP address value. You can specify multiple members separated by commas (`Value1,Value2,...ValueN`). If the value contains spaces, enclose the value in quotation marks (`"Value 1","Value 2",..."Value N"`).
 
@@ -418,7 +418,7 @@ Accept wildcard characters: False
 
 ### -RecipientOrganizationalUnitScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -438,7 +438,7 @@ Accept wildcard characters: False
 
 ### -Roles
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The Roles parameter specifies the management roles to assign to the role group when it's created. If a role name contains spaces, enclose the name in quotation marks ("). If you want to assign more that one role, separate the role names with commas.
 
@@ -458,7 +458,7 @@ Accept wildcard characters: False
 
 ### -SamAccountName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -498,7 +498,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The WhatIf switch doesn't work in Security & Compliance PowerShell.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-SearchDocumentFormat.md b/exchange/exchange-ps/ExchangePowerShell/New-SearchDocumentFormat.md
index 4396c8006d..c8313cb96b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-SearchDocumentFormat.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-SearchDocumentFormat.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -50,7 +50,7 @@ This example creates a new search document format with an extension of .sct and
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter uniquely identifies the new search document format. For example, an identity of "PropSCT" might specify a proprietary document format which is supported by a custom IFilter. The Identity parameter must be unique within the search document formats.
 
@@ -68,7 +68,7 @@ Accept wildcard characters: False
 
 ### -Extension
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Extension parameter specifies the file type to be processed by the filter and is designated by the common file extension associated with the file type. Examples include .MP3, .JPG and .PNG. Note the leading period.
 
@@ -86,7 +86,7 @@ Accept wildcard characters: False
 
 ### -MimeType
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MimeType parameter specifies the MIME type of the format.
 
@@ -104,7 +104,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Name specifies a friendly name for the format, but does not need to be unique. For example, you might have several different formats (supported by custom IFilters) that are used to index output from a proprietary system called "My Business Output". You could use the Name parameter to create a category of formats called "My Business Output Formats" and uniquely identify each format within that group using the Identity parameter.
 
@@ -122,7 +122,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -143,7 +143,7 @@ Accept wildcard characters: False
 
 ### -Enabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Enabled parameter specifies whether the new format is enabled at creation.
 
@@ -163,7 +163,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
 
@@ -188,7 +188,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-SendConnector.md b/exchange/exchange-ps/ExchangePowerShell/New-SendConnector.md
index c200e2ff41..cf81fd379f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-SendConnector.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-SendConnector.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -139,7 +139,7 @@ To assign a specific authentication credential for the Send connector, you must
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Name parameter specifies a descriptive name for the connector.
 
@@ -157,7 +157,7 @@ Accept wildcard characters: False
 
 ### -AddressSpaces
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AddressSpaces parameter specifies the domain names to which the Send connector routes mail. The complete syntax for entering each address space is: `AddressSpaceType:AddressSpace;AddressSpaceCost`.
 
@@ -195,7 +195,7 @@ Accept wildcard characters: False
 
 ### -AuthenticationCredential
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AuthenticationCredential parameter specifies the username and password that's required to use the connector.
 
@@ -215,7 +215,7 @@ Accept wildcard characters: False
 
 ### -CloudServicesMailEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 **Note**: We recommend that you don't use this parameter unless you are directed to do so by Microsoft Customer Service and Support, or by specific product documentation. Instead, use the Hybrid Configuration wizard to configure mail flow between your on-premises and cloud organizations. For more information, see [Hybrid Configuration wizard](https://learn.microsoft.com/exchange/hybrid-configuration-wizard).
 
@@ -240,7 +240,7 @@ Accept wildcard characters: False
 
 ### -Comment
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Comment parameter specifies an optional comment. If you specify a value that contains spaces, enclose the value in quotation marks ("), for example: "This is an admin note".
 
@@ -258,7 +258,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -279,7 +279,7 @@ Accept wildcard characters: False
 
 ### -ConnectionInactivityTimeOut
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ConnectionInactivityTimeOut parameter specifies the maximum time an idle connection can remain open. The default value is ten minutes.
 
@@ -301,7 +301,7 @@ Accept wildcard characters: False
 
 ### -ConnectorType
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ConnectorType parameter specifies whether the connector is used in hybrid deployments to send messages to Microsoft 365. Valid values are:
 
@@ -322,7 +322,7 @@ Accept wildcard characters: False
 
 ### -Custom
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Custom switch specifies the Custom usage type. You don't need to specify a value with this switch.
 
@@ -349,7 +349,7 @@ Accept wildcard characters: False
 
 ### -DNSRoutingEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DNSRoutingEnabled parameter specifies whether the Send connector uses Domain Name System (DNS) to route mail. Valid values for this parameter are $true or $false. The default value is $true. If you specify a SmartHosts parameter, the DNSRoutingEnabled parameter must be $false.
 
@@ -367,7 +367,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -387,7 +387,7 @@ Accept wildcard characters: False
 
 ### -DomainSecureEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainSecureEnabled parameter enables mutual Transport Layer Security (TLS) authentication for the domains serviced by the Send connector when set to $true. Mutual TLS authentication functions correctly only if the following conditions are met:
 
@@ -418,7 +418,7 @@ Accept wildcard characters: False
 
 ### -Enabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Enabled parameter specifies whether to enable the Send connector to process email messages. Valid values are $true or $false. The default value is $true.
 
@@ -436,7 +436,7 @@ Accept wildcard characters: False
 
 ### -ErrorPolicies
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ErrorPolicies parameter specifies how communication errors are treated. Possible values are the following:
 
@@ -463,7 +463,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -483,7 +483,7 @@ Accept wildcard characters: False
 
 ### -ForceHELO
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ForceHELO parameter specifies whether HELO is sent instead of the default EHLO. Valid values are $true or $false. The default value is $false.
 
@@ -501,7 +501,7 @@ Accept wildcard characters: False
 
 ### -Fqdn
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Fqdn parameter specifies the FQDN used as the source server for connected messaging servers that use the Send connector to receive outgoing messages. The value of this parameter is displayed to connected messaging servers whenever a source server name is required, as in the following examples:
 
@@ -525,7 +525,7 @@ Accept wildcard characters: False
 
 ### -FrontendProxyEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The FrontendProxyEnabled parameter routes outbound messages through the CAS server, where destination specific routing, such as DNS or IP address, is set, when the parameter is set to $true.
 
@@ -543,7 +543,7 @@ Accept wildcard characters: False
 
 ### -IgnoreSTARTTLS
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IgnoreSTARTTLS parameter specifies whether to ignore the StartTLS option offered by a remote sending server. This parameter is used with remote domains. This parameter must be set to $false if the RequireTLS parameter is set to $true. Valid values for this parameter are $true or $false.
 
@@ -561,7 +561,7 @@ Accept wildcard characters: False
 
 ### -Internal
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Internal switch specifies the Internal usage type. You don't need to specify a value with this switch.
 
@@ -588,7 +588,7 @@ Accept wildcard characters: False
 
 ### -Internet
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Internet switch specifies the Internet usage type. You don't need to specify a value with this switch.
 
@@ -635,7 +635,7 @@ Accept wildcard characters: False
 
 ### -IsScopedConnector
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IsScopedConnector parameter specifies the availability of the connector to other Mailbox servers with the Transport service. When the value of this parameter is $false, the connector can be used by all Mailbox servers in the Exchange organization. When the value of this parameter is $true, the connector can only be used by Transport service on Mailbox servers in the same Active Directory site. The default value is $false.
 
@@ -686,7 +686,7 @@ Accept wildcard characters: False
 
 ### -MaxMessageSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MaxMessageSize parameter specifies the maximum size of a message that can pass through a connector. The default value is 25 MB.
 
@@ -716,7 +716,7 @@ Accept wildcard characters: False
 
 ### -Partner
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Partner switch specifies the Partner usage type. You don't need to specify a value with this switch.
 
@@ -743,7 +743,7 @@ Accept wildcard characters: False
 
 ### -Port
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Port parameter specifies the port number for smart host forwarding, if you specify a value in the SmartHosts parameter. The valid input range is an integer from 0 through 65535. The default value is 25. In most organizations, the port number is set to 25.
 
@@ -761,7 +761,7 @@ Accept wildcard characters: False
 
 ### -ProtocolLoggingLevel
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ProtocolLoggingLevel parameter specifies whether to enable protocol logging. Verbose enables protocol logging. None disables protocol logging. The location of the Send connector protocol logs for all Send connectors configured in the Transport service on a Mailbox server or on an Edge server is specified with the SendProtocolLogPath parameter of the Set-TransportService cmdlet.
 
@@ -779,7 +779,7 @@ Accept wildcard characters: False
 
 ### -RequireOorg
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -797,7 +797,7 @@ Accept wildcard characters: False
 
 ### -RequireTLS
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RequireTLS parameter specifies whether all messages sent through this connector must be transmitted using TLS. The default value is $false.
 
@@ -815,7 +815,7 @@ Accept wildcard characters: False
 
 ### -SmartHostAuthMechanism
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SmartHostAuthMechanism parameter specifies the smart host authentication mechanism to use for authentication with a remote server. Use this parameter only when a smart host is configured and the DNSRoutingEnabled parameter is set to $false. Valid values are None, BasicAuth, BasicAuthRequireTLS, ExchangeServer, and ExternalAuthoritative. All values are mutually exclusive. If you select BasicAuth or BasicAuthRequireTLS, you must use the AuthenticationCredential parameter to specify the authentication credential.
 
@@ -833,7 +833,7 @@ Accept wildcard characters: False
 
 ### -SmartHosts
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SmartHosts parameter specifies the smart hosts the Send connector uses to route mail. This parameter is required if you set the DNSRoutingEnabled parameter to $false and it must be specified on the same command line. The SmartHosts parameter takes one or more FQDNs, such as server.contoso.com, or one or more IP addresses, or a combination of both FQDNs and IP addresses. If you enter an IP address, you must enter the IP address as a literal. For example, 10.10.1.1. The smart host identity can be the FQDN of a smart-host server, a mail exchanger (MX) record, or an address (A) record. If you configure an FQDN as the smart host identity, the source server for the Send connector must be able to use DNS name resolution to locate the smart host server.
 
@@ -853,7 +853,7 @@ Accept wildcard characters: False
 
 ### -SmtpMaxMessagesPerConnection
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SmtpMaxMessagesPerConnection parameter specifies the maximum number of messages the server can send per connection.
 
@@ -871,7 +871,7 @@ Accept wildcard characters: False
 
 ### -SourceIPAddress
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SourceIPAddress parameter specifies the local IP address to use as the endpoint for an SMTP connection to a remote messaging server. The default IP address is 0.0.0.0. This value means that the server can use any available local IP address. This parameter is valid only for Send connectors configured on an Edge server.
 
@@ -889,7 +889,7 @@ Accept wildcard characters: False
 
 ### -SourceTransportServers
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SourceTransportServers parameter specifies the names of the Mailbox servers that can use this Send connector. This parameter isn't valid for Send connectors configured on an Edge server.
 
@@ -909,7 +909,7 @@ Accept wildcard characters: False
 
 ### -TlsAuthLevel
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TlsAuthLevel parameter specifies the TLS authentication level that is used for outbound TLS connections established by this Send connector. Valid values are:
 
@@ -933,7 +933,7 @@ Accept wildcard characters: False
 
 ### -TlsCertificateName
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TlsCertificateName parameter specifies the X.509 certificate to use for TLS encryption. A valid value for this parameter is `"<I>X.500Issuer<S>X.500Subject"`. The X.500Issuer value is found in the certificate's Issuer field, and the X.500Subject value is found in the certificate's Subject field. You can find these values by running the Get-ExchangeCertificate cmdlet. Or, after you run Get-ExchangeCertificate to find the thumbprint value of the certificate, run the command `$TLSCert = Get-ExchangeCertificate -Thumbprint <Thumbprint>`, run the command `$TLSCertName = "<I>$($TLSCert.Issuer)<S>$($TLSCert.Subject)"`, and then use the value $TLSCertName for this parameter.
 
@@ -951,7 +951,7 @@ Accept wildcard characters: False
 
 ### -TlsDomain
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TlsDomain parameter specifies the domain name that the Send connector uses to verify the FQDN of the target certificate when establishing a TLS secured connection.
 
@@ -976,7 +976,7 @@ Accept wildcard characters: False
 
 ### -Usage
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Usage parameter specifies the default permissions and authentication methods assigned to the Send connector. The valid values are as follows: Custom, Internal, Internet, or Partner. The default is Custom.
 
@@ -1003,7 +1003,7 @@ Accept wildcard characters: False
 
 ### -UseExternalDNSServersEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The UseExternalDNSServersEnabled parameter specifies whether this Send connector uses the external DNS list specified by the ExternalDNSServers parameter of the Set-TransportService cmdlet. The default value is $false.
 
@@ -1021,7 +1021,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-SettingOverride.md b/exchange/exchange-ps/ExchangePowerShell/New-SettingOverride.md
index cbecf3513b..1d19d09a98 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-SettingOverride.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-SettingOverride.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -64,7 +64,7 @@ For more information, see the topic [Change the offline address book generation
 
 ### -Name
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Name parameter specifies the unique name of the setting override. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -82,7 +82,7 @@ Accept wildcard characters: False
 
 ### -Component
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Component parameter specifies the component that the setting override is applied to. For example:
 
@@ -103,7 +103,7 @@ Accept wildcard characters: False
 
 ### -Parameters
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Parameters parameter specifies one or more parameters for the override that are available for the combination of the Component and Section parameter values. This parameter uses the syntax: `@("Parameter1=Value1","Parameter2=Value2"...)`. For example:
 
@@ -124,7 +124,7 @@ Accept wildcard characters: False
 
 ### -Reason
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Reason parameter specifies why you are creating the setting override. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -142,7 +142,7 @@ Accept wildcard characters: False
 
 ### -Section
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Section parameter specifies the name of the section for which the override is created. The available values for this parameter depend on the value of the Component parameter.
 
@@ -160,7 +160,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -181,7 +181,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -199,7 +199,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -219,7 +219,7 @@ Accept wildcard characters: False
 
 ### -MaxVersion
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MaxVersion parameter specifies the latest version of Exchange 2016 that this override applies to (up to and including the specified value).
 
@@ -241,7 +241,7 @@ Accept wildcard characters: False
 
 ### -MinVersion
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MinVersion parameter specifies the earliest version of Exchange 2016 that this override applies to (up to and including the specified value).
 
@@ -263,7 +263,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the name of the Exchange 2016 server where you want the override applied. You can specify a single Exchange 2016 server name, or an array of Exchange 2016 server name wildcards. For example, if you have three Exchange 2016 servers named Exchange01, Exchange02 and Exchange03, specify the value Exchange\* to apply the override to all of them.
 
@@ -283,7 +283,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-SharingPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-SharingPolicy.md
index fd98707686..ab74be08f1 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-SharingPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-SharingPolicy.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
 Locale: en-US
@@ -56,7 +56,7 @@ This example creates a default sharing policy, which is applied to all mailboxes
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Name parameter specifies the name of the new sharing policy.
 
@@ -74,7 +74,7 @@ Accept wildcard characters: False
 
 ### -Domains
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Domains parameter specifies the domains and the associated sharing options for those domains in the sharing policy. Values for this parameter use the basic syntax: `'Domain: SharingPolicyAction'`.
 
@@ -107,7 +107,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -128,7 +128,7 @@ Accept wildcard characters: False
 
 ### -Default
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Default switch specifies that this sharing policy is the default sharing policy for all mailboxes. You don't need to specify a value with this switch.
 
@@ -148,7 +148,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -168,7 +168,7 @@ Accept wildcard characters: False
 
 ### -Enabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Enabled parameter specifies whether to enable the new sharing policy. Valid input for this parameter is $true or $false. The default is $true.
 
@@ -188,7 +188,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-SiteMailbox.md b/exchange/exchange-ps/ExchangePowerShell/New-SiteMailbox.md
index 6d87b66bcf..16c70bd0be 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-SiteMailbox.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-SiteMailbox.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -53,7 +53,7 @@ You can't run this cmdlet from the Exchange Management Shell. Use SharePoint to
 
 ### -DisplayName
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DisplayName parameter specifies the display name that displays in the user's global address list and on SharePoint.
 
@@ -71,7 +71,7 @@ Accept wildcard characters: False
 
 ### -SharePointUrl
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SharePointUrl parameter specifies the SharePoint URL where the site mailbox is hosted, for example, "https://myserver/teams/edu".
 
@@ -89,7 +89,7 @@ Accept wildcard characters: False
 
 ### -Alias
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Alias parameter specifies the alias of the site mailbox.
 
@@ -107,7 +107,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -128,7 +128,7 @@ Accept wildcard characters: False
 
 ### -Database
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Database parameter specifies the mailbox database that holds the mailbox data for the site mailbox. You can use any value that uniquely identifies the database. For example:
 
@@ -150,7 +150,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -168,7 +168,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -188,7 +188,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Name parameter specifies the name of the site mailbox.
 
@@ -206,7 +206,7 @@ Accept wildcard characters: False
 
 ### -OrganizationalUnit
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The OrganizationalUnit parameter specifies the organizational unit in which the site mailbox resides.
 
@@ -224,7 +224,7 @@ Accept wildcard characters: False
 
 ### -OverrideRecipientQuotas
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -242,7 +242,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-SiteMailboxProvisioningPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-SiteMailboxProvisioningPolicy.md
index 78730144a7..34c86fc233 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-SiteMailboxProvisioningPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-SiteMailboxProvisioningPolicy.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.WebClient-Help.xml
 Locale: en-US
@@ -73,7 +73,7 @@ This example creates the default provisioning policy named SM\_DefaultPolicy and
 
 ### -Name
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Name parameter specifies the unique name of the site mailbox provisioning policy. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -91,7 +91,7 @@ Accept wildcard characters: False
 
 ### -AliasPrefix
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AliasPrefix parameter specifies the custom text prefix to add to the aliases of new site mailboxes. Valid values are:
 
@@ -112,7 +112,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -133,7 +133,7 @@ Accept wildcard characters: False
 
 ### -DefaultAliasPrefixEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DefaultAliasPrefixEnabled parameter specifies whether new site mailboxes have the default prefix text added to the alias. Valid values are:
 
@@ -156,7 +156,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -174,7 +174,7 @@ Accept wildcard characters: False
 
 ### -IsDefault
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IsDefault switch specifies that the site mailbox provisioning policy is the default policy. You don't need to specify a value with this switch.
 
@@ -194,7 +194,7 @@ Accept wildcard characters: False
 
 ### -IssueWarningQuota
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IssueWarningQuota parameter specifies the warning threshold for the size of the mailbox. If the mailbox reaches or exceeds this size, the user receives a descriptive warning message.
 
@@ -226,7 +226,7 @@ Accept wildcard characters: False
 
 ### -MaxReceiveSize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MaxReceiveSize parameter specifies the maximum size of a message that can be sent to the site mailbox. Messages larger than the maximum size are rejected.
 
@@ -255,7 +255,7 @@ Accept wildcard characters: False
 
 ### -ProhibitSendReceiveQuota
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ProhibitSendReceiveQuota parameter specifies a size limit for the mailbox. If the mailbox reaches or exceeds this size, the mailbox can't send or receive new messages. Messages sent to the mailbox are returned to the sender with a descriptive error message. This value effectively determines the maximum size of the mailbox.
 
@@ -287,7 +287,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-SweepRule.md b/exchange/exchange-ps/ExchangePowerShell/New-SweepRule.md
index a0e63f4d33..6de7b9487a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-SweepRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-SweepRule.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -68,7 +68,7 @@ This example creates a new Sweep rule named "From Jeff" in Felipe Apodaca's mail
 
 ### -Name
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Name parameter specifies the name of the Sweep rule. If the value contains spaces, enclose the value in quotation marks.
 
@@ -86,7 +86,7 @@ Accept wildcard characters: False
 
 ### -Provider
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Provider parameter specifies the provider for the Sweep rule. If the value contains spaces, enclose the value in quotation marks.
 
@@ -106,7 +106,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -127,7 +127,7 @@ Accept wildcard characters: False
 
 ### -DestinationFolder
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DestinationFolder parameter specifies an action for the Sweep rule that moves messages to the specified folder. The syntax is `MailboxID:\ParentFolder[\SubFolder]`.
 
@@ -160,7 +160,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -180,7 +180,7 @@ Accept wildcard characters: False
 
 ### -Enabled
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Enabled parameter specifies whether the Sweep rule is enabled or disabled. Valid values are:
 
@@ -203,7 +203,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfFlagged
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -240,7 +240,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfPinned
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -263,7 +263,7 @@ Accept wildcard characters: False
 
 ### -KeepForDays
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The KeepForDays parameter specifies an action for the Sweep rule that specifies the number of days to keep messages that match the conditions of the rule. After the number of days have passed, the messages are moved to the location that's specified by the DestinationFolder parameter (by default, the Deleted Items folder).
 
@@ -283,7 +283,7 @@ Accept wildcard characters: False
 
 ### -KeepLatest
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The KeepLatest parameter specifies an action for the Sweep rule that specifies the number of messages to keep that match the conditions of the rule. After the number of messages is exceeded, the oldest messages are moved to the location that's specified by the DestinationFolder parameter (by default, the Deleted Items folder).
 
@@ -303,7 +303,7 @@ Accept wildcard characters: False
 
 ### -Mailbox
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Mailbox parameter specifies the mailbox where you want to create the Sweep rule. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -332,7 +332,7 @@ Accept wildcard characters: False
 
 ### -Sender
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Sender parameter specifies a condition for the Sweep rule that looks for the specified sender in messages. For internal senders, you can use any value that uniquely identifies the sender. For example:
 
@@ -359,7 +359,7 @@ Accept wildcard characters: False
 
 ### -SourceFolder
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SourceFolder parameter specifies a condition for the Sweep rule that looks for messages in the specified folder. The syntax is `MailboxID:\ParentFolder[\SubFolder]`.
 
@@ -392,7 +392,7 @@ Accept wildcard characters: False
 
 ### -SystemCategory
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SystemCategory parameter specifies a condition for the sweep rule that looks for messages with the specified system category. System categories are available to all mailboxes in the organization. Valid values are:
 
@@ -435,7 +435,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-SyncMailPublicFolder.md b/exchange/exchange-ps/ExchangePowerShell/New-SyncMailPublicFolder.md
index 8c39847c58..26111affea 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-SyncMailPublicFolder.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-SyncMailPublicFolder.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.WebClient-Help.xml
 Locale: en-US
@@ -78,7 +78,7 @@ This cmdlet is only used by the Import-MailPublicFoldersForMigration.ps1 and Syn
 
 ### -Name
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Name parameter specifies the unique name of the mail-enabled public folder. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -98,7 +98,7 @@ Accept wildcard characters: False
 
 ### -Alias
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Alias parameter specifies the Exchange alias (also known as the mail nickname) for the recipient. This value identifies the recipient as a mail-enabled object, and shouldn't be confused with multiple email addresses for the same recipient (also known as proxy addresses). A recipient can have only one Alias value. The maximum length is 64 characters.
 
@@ -134,7 +134,7 @@ Accept wildcard characters: False
 
 ### -EntryId
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is reserved for internal Microsoft use.
 
@@ -152,7 +152,7 @@ Accept wildcard characters: False
 
 ### -AcceptMessagesOnlyFrom
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AcceptMessagesOnlyFrom parameter specifies who is allowed to send messages to this recipient. Messages from other senders are rejected.
 
@@ -185,7 +185,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -206,7 +206,7 @@ Accept wildcard characters: False
 
 ### -Contacts
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Contacts parameter specifies the contacts for the public folder. Contacts are persons about whom you can save several types of information, such as addresses, telephone numbers, and web page URLs.
 
@@ -235,7 +235,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute1
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter specifies a value for the CustomAttribute1 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -253,7 +253,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute10
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter specifies a value for the CustomAttribute10 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -271,7 +271,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute11
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter specifies a value for the CustomAttribute11 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -289,7 +289,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute12
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter specifies a value for the CustomAttribute12 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -307,7 +307,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute13
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter specifies a value for the CustomAttribute13 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -325,7 +325,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute14
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter specifies a value for the CustomAttribute14 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -343,7 +343,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute15
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter specifies a value for the CustomAttribute15 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -361,7 +361,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute2
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter specifies a value for the CustomAttribute2 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -379,7 +379,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute3
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter specifies a value for the CustomAttribute3 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -397,7 +397,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute4
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter specifies a value for the CustomAttribute4 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -415,7 +415,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute5
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter specifies a value for the CustomAttribute5 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -433,7 +433,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute6
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter specifies a value for the CustomAttribute6 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -451,7 +451,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute7
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter specifies a value for the CustomAttribute7 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -469,7 +469,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute8
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter specifies a value for the CustomAttribute8 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -487,7 +487,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute9
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter specifies a value for the CustomAttribute9 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -505,7 +505,7 @@ Accept wildcard characters: False
 
 ### -DeliverToMailboxAndForward
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DeliverToMailboxAndForward parameter specifies the message delivery behavior when a forwarding address is specified by the ForwardingAddress parameter. Valid values are:
 
@@ -528,7 +528,7 @@ Accept wildcard characters: False
 
 ### -DisplayName
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DisplayName parameter specifies the display name of the mail-enabled public folder. The display name is visible in the Exchange admin center, in address lists, and in Outlook. The maximum length is 256 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -548,7 +548,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -568,7 +568,7 @@ Accept wildcard characters: False
 
 ### -EmailAddresses
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The EmailAddresses parameter specifies all email addresses (proxy addresses) for the recipient, including the primary SMTP address. In on-premises Exchange organizations, the primary SMTP address and other proxy addresses are typically set by email address policies. However, you can use this parameter to configure other proxy addresses for the recipient. For more information, see [Email address policies in Exchange Server](https://learn.microsoft.com/Exchange/email-addresses-and-address-books/email-address-policies/email-address-policies).
 
@@ -601,7 +601,7 @@ Accept wildcard characters: False
 
 ### -ExternalEmailAddress
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ExternalEmailAddress parameter specifies an email address outside the organization.
 
@@ -619,7 +619,7 @@ Accept wildcard characters: False
 
 ### -ForwardingAddress
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ForwardingAddress parameter specifies a forwarding address for messages that are sent to this mail-enabled public folder. A valid value for this parameter is a recipient in your organization. You can use any value that uniquely identifies the recipient. For example:
 
@@ -651,7 +651,7 @@ Accept wildcard characters: False
 
 ### -GrantSendOnBehalfTo
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The GrantSendOnBehalfTo parameter specifies who can send on behalf of this mail-enabled public folder. Although messages send on behalf of the public folder clearly show the sender in the From field (`<Sender> on behalf of <PublicFolder>`), replies to these messages are delivered to the public folder, not the sender.
 
@@ -682,7 +682,7 @@ Accept wildcard characters: False
 
 ### -HiddenFromAddressListsEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The HiddenFromAddressListsEnabled switch specifies that this recipient is not visible in address lists. You don't need to specify a value with this switch.
 
@@ -700,7 +700,7 @@ Accept wildcard characters: False
 
 ### -MaxReceiveSize
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MaxReceiveSize parameter specifies the maximum size of a message that can be sent to the mail-enabled public folder. Messages larger than the maximum size are rejected.
 
@@ -731,7 +731,7 @@ Accept wildcard characters: False
 
 ### -MaxSendSize
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MaxSendSize parameter specifies the maximum size of a message that can be sent by the mail-enabled public folder.
 
@@ -762,7 +762,7 @@ Accept wildcard characters: False
 
 ### -OnPremisesObjectId
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The OnPremisesObjectId parameter specifies the GUID of the on-premises mail-enabled public folder that's used to create the mail-enabled public folder object in Exchange Online.
 
@@ -780,7 +780,7 @@ Accept wildcard characters: False
 
 ### -OverrideRecipientQuotas
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is reserved for internal Microsoft use.
 
@@ -798,7 +798,7 @@ Accept wildcard characters: False
 
 ### -RejectMessagesFrom
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RejectMessagesFrom parameter specifies who isn't allowed to send messages to this recipient. Messages from these senders are rejected.
 
@@ -831,7 +831,7 @@ Accept wildcard characters: False
 
 ### -RequireSenderAuthenticationEnabled
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RequireSenderAuthenticationEnabled parameter specifies whether to accept messages only from authenticated (internal) senders. Valid values are:
 
@@ -852,7 +852,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
@@ -870,7 +870,7 @@ Accept wildcard characters: False
 
 ### -WindowsEmailAddress
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WindowsEmailAddress parameter specifies the Windows email address for this recipient. This is a common Active Directory attribute that's present in all environments, including environments without Exchange. Using the WindowsEmailAddress parameter on a recipient has one of the following results:
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-SystemMessage.md b/exchange/exchange-ps/ExchangePowerShell/New-SystemMessage.md
index 5f57d4f5d4..5adbdc6072 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-SystemMessage.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-SystemMessage.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -64,7 +64,7 @@ This example creates a custom English quota message for mailboxes that exceed th
 
 ### -DsnCode
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DsnCode parameter specifies the enhanced status code for the custom system message.
 
@@ -90,7 +90,7 @@ Accept wildcard characters: False
 
 ### -Internal
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Internal parameter specifies whether the system message is displayed to internal or external users. Valid values are:
 
@@ -115,7 +115,7 @@ Accept wildcard characters: False
 
 ### -Language
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Language parameter specifies the language of the message (for example, en for English or ja for Japanese). For the list of supported language codes, see [Supported languages for NDRs](https://learn.microsoft.com/Exchange/mail-flow/non-delivery-reports-and-bounce-messages/ndr-procedures#supported-languages-for-ndrs).
 
@@ -135,7 +135,7 @@ Accept wildcard characters: False
 
 ### -QuotaMessageType
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The QuotaMessageType parameter specifies the quota for the custom system message. Valid values are:
 
@@ -191,7 +191,7 @@ Accept wildcard characters: False
 
 ### -Text
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Text parameter specifies the text in the custom system message. The text should explain why the system message was sent, and any actions that the user should take.
 
@@ -232,7 +232,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -253,7 +253,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -273,7 +273,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ThrottlingPolicy.md b/exchange/exchange-ps/ExchangePowerShell/New-ThrottlingPolicy.md
index d98958dff8..4cdeb36baf 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-ThrottlingPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-ThrottlingPolicy.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.WebClient-Help.xml
 Locale: en-US
@@ -235,7 +235,7 @@ This example creates a throttling policy that restricts a user to be able to onl
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Name parameter specifies the name of the object in Active Directory. The default policy is named `DefaultThrottlingPolicy<GUID>`.
 
@@ -253,7 +253,7 @@ Accept wildcard characters: False
 
 ### -AnonymousCutoffBalance
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AnonymousCutoffBalance parameter specifies the resource consumption limits for an anonymous user before the user is completely blocked from performing operations on a specific component.
 
@@ -271,7 +271,7 @@ Accept wildcard characters: False
 
 ### -AnonymousMaxBurst
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AnonymousMaxBurst parameter specifies the amount of time that an anonymous user can consume an elevated amount of resources before being throttled. This is measured in milliseconds. This value is set separately for each component.
 
@@ -289,7 +289,7 @@ Accept wildcard characters: False
 
 ### -AnonymousMaxConcurrency
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AnonymousMaxConcurrency parameter specifies how many anonymous connections can be made to a user's calendar data at the same time. A connection is held from the moment a request is received until a response is sent in its entirety to the requestor. If anonymous users attempt to make more concurrent requests than their policy allows, the new connection attempt fails. However, the existing connections remain valid. The AnonymousMaxConcurrency parameter has a valid range from 0 through 2147483647 inclusive. The default value is 1. To indicate that the number of concurrent connections should be unthrottled (no limit), this value should be set to $null.
 
@@ -367,7 +367,7 @@ Accept wildcard characters: False
 
 ### -AnonymousRechargeRate
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AnonymousRechargeRate parameter specifies the rate at which an anonymous user's budget is charged (budget grows by) during the budget time.
 
@@ -385,7 +385,7 @@ Accept wildcard characters: False
 
 ### -BookingSelfServiceCutoffBalance
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -403,7 +403,7 @@ Accept wildcard characters: False
 
 ### -BookingSelfServiceMaxBurst
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -421,7 +421,7 @@ Accept wildcard characters: False
 
 ### -BookingSelfServiceMaxConcurrency
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -439,7 +439,7 @@ Accept wildcard characters: False
 
 ### -BookingSelfServiceRechargeRate
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -457,7 +457,7 @@ Accept wildcard characters: False
 
 ### -ComplianceMaxExpansionDGRecipients
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ComplianceMaxExpansionDGRecipients parameter specifies the maximum number of recipients to expand in distribution groups when a discovery search is looking for a specified recipient.
 
@@ -475,7 +475,7 @@ Accept wildcard characters: False
 
 ### -ComplianceMaxExpansionNestedDGs
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ComplianceMaxExpansionNestedDGs parameter specifies the maximum number of nested distribution groups to expand when a discovery search is looking for a specified recipient.
 
@@ -493,7 +493,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -514,7 +514,7 @@ Accept wildcard characters: False
 
 ### -ConsensusCutoffBalance
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -532,7 +532,7 @@ Accept wildcard characters: False
 
 ### -ConsensusMaxBurst
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -550,7 +550,7 @@ Accept wildcard characters: False
 
 ### -ConsensusMaxConcurrency
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -568,7 +568,7 @@ Accept wildcard characters: False
 
 ### -ConsensusRechargeRate
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -586,7 +586,7 @@ Accept wildcard characters: False
 
 ### -CpaCutoffBalance
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The CpaCutoffBalance parameter specifies the resource consumption limits for a cross-premises user before that user is completely blocked from performing operations on a specific component.
 
@@ -604,7 +604,7 @@ Accept wildcard characters: False
 
 ### -CpaMaxBurst
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The CpaMaxBurst parameter specifies the amount of time that a cross-premises user can consume an elevated amount of resources before being throttled. This is measured in milliseconds. This value is set separately for each component.
 
@@ -622,7 +622,7 @@ Accept wildcard characters: False
 
 ### -CPAMaxConcurrency
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The CpaMaxConcurrency parameter specifies how many concurrent connections a cross-premises user can have against an Exchange server at one time. A connection is held from the moment a request is received until a response is sent in its entirety to the requestor. If users attempt to make more concurrent requests than their policy allows, the new connection attempt fails. However, the existing connections remain valid. The CpaMaxConcurrency parameter has a valid range from 0 through 2147483647 inclusive. To indicate that the number of concurrent connections should be unthrottled (no limit), this value should be set to $null.
 
@@ -678,7 +678,7 @@ Accept wildcard characters: False
 
 ### -CpaRechargeRate
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The CpaRechargeRate parameter specifies the rate at which a cross premises user budget is charged (budget grows by) during the budget time.
 
@@ -716,7 +716,7 @@ Accept wildcard characters: False
 
 ### -DiscoveryMaxConcurrency
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DiscoveryMaxConcurrency parameter specifies the number of concurrent discovery search executions that a user can have at the same time. To modify the discovery throttling parameters, create a new policy and name it "DiscoveryThrottlingPolicy".
 
@@ -734,7 +734,7 @@ Accept wildcard characters: False
 
 ### -DiscoveryMaxKeywords
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DiscoveryMaxKeywords parameter specifies the maximum number of keywords that a user can include in a discovery search. For more information, see [Search-Mailbox](https://learn.microsoft.com/powershell/module/exchangepowershell/search-mailbox).
 
@@ -752,7 +752,7 @@ Accept wildcard characters: False
 
 ### -DiscoveryMaxKeywordsPerPage
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DiscoveryMaxKeywordsPerPage parameter specifies the number of keywords for which to show statistics on a single page in the EAC.
 
@@ -770,7 +770,7 @@ Accept wildcard characters: False
 
 ### -DiscoveryMaxMailboxes
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DiscoveryMaxMailboxes parameter specifies the maximum number of source mailboxes that a user can include in a discovery search.
 
@@ -788,7 +788,7 @@ Accept wildcard characters: False
 
 ### -DiscoveryMaxPreviewSearchMailboxes
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DiscoveryMaxPreviewSearchMailboxes parameter specifies the maximum number of mailboxes that a user can include in eDiscovery Search Preview.
 
@@ -806,7 +806,7 @@ Accept wildcard characters: False
 
 ### -DiscoveryMaxRefinerResults
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -824,7 +824,7 @@ Accept wildcard characters: False
 
 ### -DiscoveryMaxSearchQueueDepth
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DiscoveryMaxSearchQueueDepth parameter specifies the maximum number of concurrent discovery search threads that can be active at the same time.
 
@@ -842,7 +842,7 @@ Accept wildcard characters: False
 
 ### -DiscoveryMaxStatsSearchMailboxes
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DiscoveryMaxStatsSearchMailboxes parameter specifies the maximum number of mailboxes that a user can search in an In-Place eDiscovery search without being able to view the statistics. When the number of mailboxes configured with the DiscoveryMaxStatsSearchMailboxes parameter is exceeded, the user must copy the search results to a discovery mailbox to view the statistics for the discovery search. For more information, see [In-Place eDiscovery in Exchange Server](https://learn.microsoft.com/Exchange/policy-and-compliance/ediscovery/ediscovery).
 
@@ -860,7 +860,7 @@ Accept wildcard characters: False
 
 ### -DiscoveryPreviewSearchResultsPageSize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DiscoveryPreviewSearchResultsPageSize parameter specifies the number of messages displayed on a single page in eDiscovery Search Preview.
 
@@ -878,7 +878,7 @@ Accept wildcard characters: False
 
 ### -DiscoverySearchTimeoutPeriod
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DiscoverySearchTimeoutPeriod parameter specifies the number of minutes that a discovery search runs before it times out.
 
@@ -896,7 +896,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -916,7 +916,7 @@ Accept wildcard characters: False
 
 ### -EasCutoffBalance
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The EasCutoffBalance parameter specifies the resource consumption limits for an Exchange ActiveSync user before that user is completely blocked from performing operations on a specific component.
 
@@ -934,7 +934,7 @@ Accept wildcard characters: False
 
 ### -EasMaxBurst
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The EasMaxBurst parameter specifies the amount of time that an Exchange ActiveSync user can consume an elevated amount of resources before being throttled. This is measured in milliseconds. This value is set separately for each component.
 
@@ -952,7 +952,7 @@ Accept wildcard characters: False
 
 ### -EASMaxConcurrency
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The EasMaxConcurrency parameter specifies how many concurrent connections an Exchange ActiveSync user can have against an Exchange server at one time. A connection is held from the moment a request is received until a response is sent in its entirety to the requestor. If users attempt to make more concurrent requests than their policy allows, the new connection attempt fails. However, the existing connections remain valid. The EasMaxConcurrency parameter has a valid range from 0 through 2147483647 inclusive. The default value is 10. To indicate that the number of concurrent connections should be unthrottled (no limit), this value should be set to $null.
 
@@ -970,7 +970,7 @@ Accept wildcard characters: False
 
 ### -EASMaxDeviceDeletesPerMonth
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The EasMaxDeviceDeletesPerMonth parameter specifies a limit to the number of Exchange ActiveSync partnerships that a user can delete per month. By default, each user can delete a maximum of 20 partnerships per calendar month. When the limit is reached, the partnership deletion attempt fails and an error message is displayed to the user.
 
@@ -988,7 +988,7 @@ Accept wildcard characters: False
 
 ### -EASMaxDevices
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The EasMaxDevices parameter specifies a limit to the number of Exchange ActiveSync partnerships that a user can have at one time. By default, each user can create 100 Exchange ActiveSync partnerships with their Exchange account. After users exceed the limit, they must delete one of their existing partnerships before they can create any more new partnerships. An email error message describing the limitation is sent to the user when the limit is exceeded. Additionally, an event is logged in the Application log when a user exceeds the limit.
 
@@ -1006,7 +1006,7 @@ Accept wildcard characters: False
 
 ### -EasMaxInactivityForDeviceCleanup
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The EasMaxInactivityForDeviceCleanup parameter specifies the length of time that a user's device partnerships remain active. By default, there is no limit to the number of days that a user's device partnerships remain active. Use this value if you want to minimize the amount of inactive device partnerships in your organization. To use this setting, specify a value in days since the user's last sync time to cause the device partnership to be removed.
 
@@ -1084,7 +1084,7 @@ Accept wildcard characters: False
 
 ### -EasRechargeRate
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The EasRechargeRate parameter specifies the rate at which an Exchange ActiveSync user's budget is charged (budget grows by) during the budget time.
 
@@ -1102,7 +1102,7 @@ Accept wildcard characters: False
 
 ### -EncryptionRecipientCutoffBalance
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -1120,7 +1120,7 @@ Accept wildcard characters: False
 
 ### -EncryptionRecipientMaxBurst
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -1138,7 +1138,7 @@ Accept wildcard characters: False
 
 ### -EncryptionRecipientMaxConcurrency
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -1156,7 +1156,7 @@ Accept wildcard characters: False
 
 ### -EncryptionRecipientRechargeRate
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -1174,7 +1174,7 @@ Accept wildcard characters: False
 
 ### -EncryptionSenderCutoffBalance
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -1192,7 +1192,7 @@ Accept wildcard characters: False
 
 ### -EncryptionSenderMaxBurst
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -1210,7 +1210,7 @@ Accept wildcard characters: False
 
 ### -EncryptionSenderMaxConcurrency
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -1228,7 +1228,7 @@ Accept wildcard characters: False
 
 ### -EncryptionSenderRechargeRate
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -1246,7 +1246,7 @@ Accept wildcard characters: False
 
 ### -EwsCostThreshold
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The EwsCostThreshold parameter specifies the cost threshold for Exchange Web Services users.
 
@@ -1264,7 +1264,7 @@ Accept wildcard characters: False
 
 ### -EwsCutoffBalance
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The EwsCutoffBalance parameter specifies the resource consumption limits for an Exchange Web Services user before that user is completely blocked from performing operations on a specific component.
 
@@ -1282,7 +1282,7 @@ Accept wildcard characters: False
 
 ### -EwsMaxBurst
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The EwsMaxBurst parameter specifies the amount of time that an Exchange Web Services user can consume an elevated amount of resources before being throttled. This is measured in milliseconds. This value is set separately for each component.
 
@@ -1340,7 +1340,7 @@ Accept wildcard characters: False
 
 ### -EWSMaxConcurrency
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The EwsMaxConcurrency parameter specifies how many concurrent connections an Exchange Web Services user can have against an Exchange server at one time. A connection is held from the moment a request is received until a response is sent in its entirety to the requestor. If users attempt to make more concurrent requests than their policy allows, the new connection attempt fails. However, the existing connections remain valid. The EwsMaxConcurrency parameter has a valid range from 0 through 2147483647 inclusive. The default value is 10. To indicate that the number of concurrent connections should be unthrottled (no limit), this value should be set to $null.
 
@@ -1358,7 +1358,7 @@ Accept wildcard characters: False
 
 ### -EWSMaxSubscriptions
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The EwsMaxSubscriptions parameter specifies the maximum number of active push and pull subscriptions that an Exchange Web Services user can have on a specified Exchange server at the same time. If a user tries to create more subscriptions than the configured maximum, the subscription fails, and an event is logged in Event Viewer.
 
@@ -1436,7 +1436,7 @@ Accept wildcard characters: False
 
 ### -EwsRechargeRate
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The EwsRechargeRate parameter specifies the rate at which an Exchange Web Services user's budget is charged (budget grows by) during the budget time.
 
@@ -1454,7 +1454,7 @@ Accept wildcard characters: False
 
 ### -ExchangeMaxCmdlets
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExchangeMaxCmdlets parameter specifies the number of cmdlets that can be executed within a specific time period before their execution is slowed down. The value specified by this parameter should be less than the value specified by the PowerShellMaxCmdlets parameter.
 
@@ -1474,7 +1474,7 @@ Accept wildcard characters: False
 
 ### -ForwardeeLimit
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ForwardeeLimit parameter specifies the limits for the number of recipients that can be configured in Inbox Rules when using the forward or redirect action. This parameter doesn't limit the number of messages that can be forwarded or redirected to the recipients that are configured.
 
@@ -1492,7 +1492,7 @@ Accept wildcard characters: False
 
 ### -ImapCutoffBalance
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ImapCutoffBalance parameter specifies the resource consumption limits for an IMAP user before that user is completely blocked from performing operations on a specific component.
 
@@ -1510,7 +1510,7 @@ Accept wildcard characters: False
 
 ### -ImapMaxBurst
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ImapMaxBurst parameter specifies the amount of time that an IMAP user can consume an elevated amount of resources before being throttled. This is measured in milliseconds. This value is set separately for each component.
 
@@ -1528,7 +1528,7 @@ Accept wildcard characters: False
 
 ### -IMAPMaxConcurrency
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ImapMaxConcurrency parameter specifies how many concurrent connections an IMAP user can have against an Exchange server at one time. A connection is held from the moment a request is received until a response is sent in its entirety to the requestor. If users attempt to make more concurrent requests than their policy allows, the new connection attempt fails. However, the existing connections remain valid. The ImapMaxConcurrency parameter has a valid range from 0 through 2147483647 inclusive. To indicate that the number of concurrent connections should be unthrottled (no limit), this value should be set to $null.
 
@@ -1606,7 +1606,7 @@ Accept wildcard characters: False
 
 ### -ImapRechargeRate
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ImapRechargeRate parameter specifies the rate at which the IMAP user's budget is charged (budget grows by) during the budget time.
 
@@ -1624,7 +1624,7 @@ Accept wildcard characters: False
 
 ### -IsServiceAccount
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IsServiceAccount switch specifies that the user accounts associated with this policy are moderated by per-user thresholds and the health of system resources (for example, overall CPU usage). You don't need to specify a value with this switch.
 
@@ -1646,7 +1646,7 @@ Accept wildcard characters: False
 
 ### -MessageRateLimit
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MessageRateLimit parameter specifies the number of messages per minute that can be submitted to transport by POP3 or IMAP4 clients that use SMTP. Clients receive a transient error if they submit messages at a rate that exceeds the value of this parameter. Exchange attempts to connect and send the messages at a later time.
 
@@ -1664,7 +1664,7 @@ Accept wildcard characters: False
 
 ### -OutlookServiceCutoffBalance
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -1682,7 +1682,7 @@ Accept wildcard characters: False
 
 ### -OutlookServiceMaxBurst
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -1700,7 +1700,7 @@ Accept wildcard characters: False
 
 ### -OutlookServiceMaxConcurrency
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -1718,7 +1718,7 @@ Accept wildcard characters: False
 
 ### -OutlookServiceMaxSocketConnectionsPerDevice
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -1736,7 +1736,7 @@ Accept wildcard characters: False
 
 ### -OutlookServiceMaxSocketConnectionsPerUser
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -1754,7 +1754,7 @@ Accept wildcard characters: False
 
 ### -OutlookServiceMaxSubscriptions
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -1772,7 +1772,7 @@ Accept wildcard characters: False
 
 ### -OutlookServiceRechargeRate
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -1790,7 +1790,7 @@ Accept wildcard characters: False
 
 ### -OwaCutoffBalance
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The OwaCutoffBalance parameter specifies the resource consumption limits for an Outlook on the web user before that user is completely blocked from performing operations on a specific component.
 
@@ -1808,7 +1808,7 @@ Accept wildcard characters: False
 
 ### -OwaMaxBurst
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The OwaMaxBurst parameter specifies the amount of time that an Outlook on the web user can consume an elevated amount of resources before being throttled. This is measured in milliseconds. This value is set separately for each component.
 
@@ -1826,7 +1826,7 @@ Accept wildcard characters: False
 
 ### -OWAMaxConcurrency
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The OwaMaxConcurrency parameter specifies how many concurrent connections an Outlook on the web user can have against an Exchange server at one time. A connection is held from the moment a request is received until a response is sent in its entirety to the requestor. If users attempt to make more concurrent requests than their policy allows, the new connection attempt fails. However, the existing connections remain valid.
 
@@ -1908,7 +1908,7 @@ Accept wildcard characters: False
 
 ### -OwaRechargeRate
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The OwaRechargeRate parameter specifies the rate at which an Outlook on the web user's budget is charged (budget grows by) during the budget time.
 
@@ -1926,7 +1926,7 @@ Accept wildcard characters: False
 
 ### -OwaVoiceCutoffBalance
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The OwaVoiceCutoffBalance parameter specifies the resource consumption limits for an Outlook on the web voice user before that user is completely blocked from performing operations on a specific component.
 
@@ -1944,7 +1944,7 @@ Accept wildcard characters: False
 
 ### -OwaVoiceMaxBurst
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The OwaVoiceMaxBurst parameter specifies the amount of time that an Outlook on the web voice user can consume an elevated amount of resources before being throttled. This is measured in milliseconds. This value is set separately for each component.
 
@@ -1962,7 +1962,7 @@ Accept wildcard characters: False
 
 ### -OwaVoiceMaxConcurrency
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The OwaVoiceMaxConcurrency parameter specifies how many concurrent connections an Outlook on the web voice user can have against an Exchange server at one time. A connection is held from the moment a request is received until a response is sent in its entirety to the requestor. If users attempt to make more concurrent requests than their policy allows, the new connection attempt fails. However, the existing connections remain valid. The OwaVoiceMaxConcurrency parameter has a valid range from 0 through 2147483647 inclusive. The default value is 5. To indicate that the number of concurrent connections should be unthrottled (no limit), this value should be set to $null.
 
@@ -1980,7 +1980,7 @@ Accept wildcard characters: False
 
 ### -OwaVoiceRechargeRate
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The OwaVoiceRechargeRate parameter specifies the rate at which an Outlook on the web voice user's budget is charged (budget grows by) during the budget time.
 
@@ -1998,7 +1998,7 @@ Accept wildcard characters: False
 
 ### -PopCutoffBalance
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PopCutoffBalance parameter specifies the resource consumption limits for a user before that user is completely blocked from performing operations on a specific component.
 
@@ -2016,7 +2016,7 @@ Accept wildcard characters: False
 
 ### -PopMaxBurst
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PopMaxBurst parameter specifies the amount of time that a user can consume an elevated amount of resources before being throttled. This is measured in milliseconds. This value is set separately for each component.
 
@@ -2034,7 +2034,7 @@ Accept wildcard characters: False
 
 ### -POPMaxConcurrency
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PopMaxConcurrency parameter specifies how many concurrent connections a POP user can have against an Exchange server at one time. A connection is held from the moment a request is received until a response is sent in its entirety to the requestor. If users attempt to make more concurrent requests than their policy allows, the new connection attempt fails. However, the existing connections remain valid. The PopMaxConcurrency parameter has a valid range from 0 through 2147483647 inclusive. The default value is 20. To indicate that the number of concurrent connections should be unthrottled (no limit), this value should be set to $null.
 
@@ -2112,7 +2112,7 @@ Accept wildcard characters: False
 
 ### -PopRechargeRate
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PopRechargeRate parameter specifies the rate at which the user budget is charged (budget grows by) during the budget time.
 
@@ -2130,7 +2130,7 @@ Accept wildcard characters: False
 
 ### -PowerShellCutoffBalance
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PowerShellCutoffBalance parameter specifies the resource consumption limits for a user before that user is completely blocked from performing operations on a specific component.
 
@@ -2148,7 +2148,7 @@ Accept wildcard characters: False
 
 ### -PowerShellMaxBurst
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PowerShellMaxBurst parameter specifies the amount of time that a user can consume an elevated amount of resources before being throttled. This is measured in milliseconds. This value is set separately for each component.
 
@@ -2166,7 +2166,7 @@ Accept wildcard characters: False
 
 ### -PowerShellMaxCmdletQueueDepth
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PowerShellMaxCmdletQueueDepth parameter specifies the number of operations allowed to be executed by the user. This value directly affects the behavior of the PowerShellMaxCmdlets and PowerShellMaxConcurrency parameters. For example, the PowerShellMaxConcurrency parameter consumes at least two operations defined by the PowerShellMaxCmdletQueueDepth parameter but additional operations are also consumed per cmdlet execution. The number of operations depends on the cmdlets executed. We recommend that the value for the PowerShellMaxCmdletQueueDepth parameter be at least three times larger than the value of the PowerShellMaxConcurrency parameter. This parameter doesn't affect Exchange admin center operations or Exchange Web Services operations.
 
@@ -2184,7 +2184,7 @@ Accept wildcard characters: False
 
 ### -PowerShellMaxCmdlets
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PowerShellMaxCmdlets parameter specifies the number of cmdlets that can be executed within a specific time period before their execution is stopped. The value specified by this parameter should be more than the value specified by the ExchangeMaxCmdlets parameter. The time period used for this limit is specified by the PowerShellMaxCmdletsTimePeriod parameter. Both values should be set at the same time.
 
@@ -2202,7 +2202,7 @@ Accept wildcard characters: False
 
 ### -PowerShellMaxCmdletsTimePeriod
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PowerShellMaxCmdletsTimePeriod parameter specifies the time period, in seconds, that the throttling policy uses to determine whether the number of cmdlets being executed exceeds the limits specified by the PowerShellMaxCmdlets and ExchangeMaxCmdlets parameters.
 
@@ -2220,7 +2220,7 @@ Accept wildcard characters: False
 
 ### -PowerShellMaxConcurrency
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PowerShellMaxConcurrency parameter specifies different information depending on context:
 
@@ -2243,7 +2243,7 @@ Accept wildcard characters: False
 
 ### -PowerShellMaxDestructiveCmdlets
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PowerShellMaxDestructiveCmdlets parameter specifies the number of destructive cmdlets that can be executed within a specific time period before their execution is stopped. Destructive cmdlets are cmdlets that can make significant changes to user data and configuration settings in your Exchange organization. Throttling these cmdlets might help prevent accidental data loss. The following cmdlets are designated as destructive:
 
@@ -2273,7 +2273,7 @@ Accept wildcard characters: False
 
 ### -PowerShellMaxDestructiveCmdletsTimePeriod
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PowerShellMaxDestructiveCmdletsTimePeriod parameter specifies the time period, in seconds, that the throttling policy uses to determine how many destructive cmdlets can be run. You set a value for this parameter when you set the PowerShellMaxDestructiveCmdlets parameter. Both values should be set at the same time. For more information, see the description for the PowerShellMaxDestructiveCmdlets parameter.
 
@@ -2291,7 +2291,7 @@ Accept wildcard characters: False
 
 ### -PowerShellMaxOperations
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PowerShellMaxOperations parameter specifies the protocol-level operations that are used to send and receive data. If the execution of a cmdlet results in a significant number of operations (for example, if there is a lot of input/output occurring), throttling might occur. The default setting is Unlimited.
 
@@ -2309,7 +2309,7 @@ Accept wildcard characters: False
 
 ### -PowerShellMaxRunspaces
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PowerShellMaxRunspaces parameter specifies the number of concurrent Windows PowerShell sessions that a user is allowed to have. The default setting is Unlimited.
 
@@ -2327,7 +2327,7 @@ Accept wildcard characters: False
 
 ### -PowerShellMaxRunspacesTimePeriod
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PowerShellMaxRunspacesTimePeriod parameter specifies the time period, in seconds, that the throttling policy uses to determine how many Windows PowerShell sessions can be run. You set this value when you set the PowerShellMaxRunspaces parameter.
 
@@ -2345,7 +2345,7 @@ Accept wildcard characters: False
 
 ### -PowerShellMaxTenantConcurrency
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PowerShellMaxTenantConcurrency parameter limits the number of concurrent Windows PowerShell connections per tenant organization. By default, the limit for concurrent Windows PowerShell connections per tenant organization is set to 9. If users in a tenant organization try to make more concurrent requests than the limit set by the PowerShellMaxTenantConcurrency parameter, the new connection attempt fails. However, the existing connections remain valid. This limit is enforced even if a single user hasn't exceeded the per-user limit set by the PowerShellMaxConcurrency parameter. The PowerShellMaxTenantConcurrency parameter has a valid range from 0 through 100 inclusive. To indicate that the number of concurrent connections should be unthrottled (no limit), this value should be set to $null.
 
@@ -2365,7 +2365,7 @@ Accept wildcard characters: False
 
 ### -PowerShellMaxTenantRunspaces
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PowerShellMaxTenantRunspaces parameter specifies the number of concurrent Windows PowerShell sessions that a tenant is allowed to have.
 
@@ -2383,7 +2383,7 @@ Accept wildcard characters: False
 
 ### -PowerShellRechargeRate
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PowerShellRechargeRate parameter specifies the rate at which the user budget is charged (budget grows by) during the budget time.
 
@@ -2401,7 +2401,7 @@ Accept wildcard characters: False
 
 ### -PswsMaxConcurrency
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PswsMaxConcurrency parameter specifies how many concurrent connections a Windows PowerShell Web Services user can have against an Exchange server at one time. A connection is held from the moment a request is received until a response is sent in its entirety to the requestor. If users attempt to make more concurrent requests than their policy allows, the new connection attempt fails. However, the existing connections remain valid.
 
@@ -2421,7 +2421,7 @@ Accept wildcard characters: False
 
 ### -PswsMaxRequest
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PswsMaxRequest parameter specifies how many requests a Windows PowerShell Web Services user can have against an Exchange server at one time. The default setting is Unlimited.
 
@@ -2439,7 +2439,7 @@ Accept wildcard characters: False
 
 ### -PswsMaxRequestTimePeriod
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PswsMaxRequestTimePeriod parameter specifies the period of time, in seconds, that the throttling policy uses to determine how many requests can be run. The default setting is Unlimited.
 
@@ -2457,7 +2457,7 @@ Accept wildcard characters: False
 
 ### -PushNotificationCutoffBalance
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -2475,7 +2475,7 @@ Accept wildcard characters: False
 
 ### -PushNotificationMaxBurst
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -2493,7 +2493,7 @@ Accept wildcard characters: False
 
 ### -PushNotificationMaxBurstPerDevice
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -2511,7 +2511,7 @@ Accept wildcard characters: False
 
 ### -PushNotificationMaxConcurrency
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -2529,7 +2529,7 @@ Accept wildcard characters: False
 
 ### -PushNotificationRechargeRate
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -2547,7 +2547,7 @@ Accept wildcard characters: False
 
 ### -PushNotificationRechargeRatePerDevice
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -2565,7 +2565,7 @@ Accept wildcard characters: False
 
 ### -PushNotificationSamplingPeriodPerDevice
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -2583,7 +2583,7 @@ Accept wildcard characters: False
 
 ### -RcaCutoffBalance
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RcaCutoffBalance parameter specifies the resource consumption limits for a user before that user is completely blocked from performing operations on a specific component.
 
@@ -2601,7 +2601,7 @@ Accept wildcard characters: False
 
 ### -RcaMaxBurst
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RcaMaxBurst parameter specifies the amount of time that a user can consume an elevated amount of resources before being throttled. This is measured in milliseconds. This value is set separately for each component.
 
@@ -2619,7 +2619,7 @@ Accept wildcard characters: False
 
 ### -RCAMaxConcurrency
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RcaMaxConcurrency parameter specifies how many concurrent connections an RPC Client Access user can have against an Exchange server at one time. A connection is held from the moment a request is received until the connection is closed or the connection is otherwise disconnected (for example, if the user goes offline). If users attempt to make more concurrent requests than their policy allows, the new connection attempt fails. However, the existing connections remain valid.
 
@@ -2701,7 +2701,7 @@ Accept wildcard characters: False
 
 ### -RcaRechargeRate
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RcaRechargeRate parameter specifies the rate at which the budget for the user is charged (how much the budget grows by) during the budget time.
 
@@ -2719,7 +2719,7 @@ Accept wildcard characters: False
 
 ### -RcaSharedCutoffBalance
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RcaSharedCutoffBalance parameter specifies the resource consumption limits for all users before they're completely blocked from performing operations on a specific component.
 
@@ -2737,7 +2737,7 @@ Accept wildcard characters: False
 
 ### -RcaSharedMaxBurst
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RcaShardMaxBurst parameter specifies the amount of time that all users can consume elevated amounts of resources before being throttled. This is measured in milliseconds. This value is set separately for each component.
 
@@ -2755,7 +2755,7 @@ Accept wildcard characters: False
 
 ### -RcaSharedMaxConcurrency
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RcaSharedMaxConcurrency parameter specifies how many concurrent connections all RPC Client Access users can have against an Exchange server at one time. A connection is held from the moment a request is received until the connection is closed or the connection is otherwise disconnected (for example, if users go offline). If there are more concurrent requests than the policy allows, new connection attempts fail. However, the existing connections remain valid.
 
@@ -2775,7 +2775,7 @@ Accept wildcard characters: False
 
 ### -RcaSharedRechargeRate
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RcaSharedRechargeRate parameter specifies the rate at which the budget for all users is charged (how much the budget grows by) during the budget time.
 
@@ -2793,7 +2793,7 @@ Accept wildcard characters: False
 
 ### -RecipientRateLimit
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RecipientRateLimit parameter specifies the limits on the number of recipients that a user can address in a 24-hour period.
 
@@ -2811,7 +2811,7 @@ Accept wildcard characters: False
 
 ### -SchedulesCutoffBalance
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -2829,7 +2829,7 @@ Accept wildcard characters: False
 
 ### -SchedulesMaxBurst
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -2847,7 +2847,7 @@ Accept wildcard characters: False
 
 ### -SchedulesMaxConcurrency
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -2865,7 +2865,7 @@ Accept wildcard characters: False
 
 ### -SchedulesRechargeRate
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -2883,7 +2883,7 @@ Accept wildcard characters: False
 
 ### -SuiteCutoffBalance
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -2901,7 +2901,7 @@ Accept wildcard characters: False
 
 ### -SuiteMaxBurst
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -2919,7 +2919,7 @@ Accept wildcard characters: False
 
 ### -SuiteMaxConcurrency
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -2937,7 +2937,7 @@ Accept wildcard characters: False
 
 ### -SuiteRechargeRate
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -2955,7 +2955,7 @@ Accept wildcard characters: False
 
 ### -ThrottlingPolicyScope
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ThrottlingPolicyScope parameter specifies the scope of the throttling policy. You can use the following values.
 
@@ -2979,7 +2979,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-TransportRule.md b/exchange/exchange-ps/ExchangePowerShell/New-TransportRule.md
index 465d011257..f05877d0a4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-TransportRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-TransportRule.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -233,7 +233,7 @@ This example creates a rule with the following settings:
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Name parameter specifies the unique name of the rule. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -251,7 +251,7 @@ Accept wildcard characters: False
 
 ### -ActivationDate
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ActivationDate parameter specifies when the rule starts processing messages. The rule doesn't take any action on messages until the specified date/time.
 
@@ -271,7 +271,7 @@ Accept wildcard characters: False
 
 ### -ADComparisonAttribute
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -325,7 +325,7 @@ Accept wildcard characters: False
 
 ### -ADComparisonOperator
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -350,7 +350,7 @@ Accept wildcard characters: False
 
 ### -AddManagerAsRecipientType
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an action or part of an action for the rule.
 
@@ -379,7 +379,7 @@ Accept wildcard characters: False
 
 ### -AddToRecipients
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an action or part of an action for the rule.
 
@@ -410,7 +410,7 @@ Accept wildcard characters: False
 
 ### -AnyOfCcHeader
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -445,7 +445,7 @@ Accept wildcard characters: False
 
 ### -AnyOfCcHeaderMemberOf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -480,7 +480,7 @@ Accept wildcard characters: False
 
 ### -AnyOfRecipientAddressContainsWords
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -506,7 +506,7 @@ Accept wildcard characters: False
 
 ### -AnyOfRecipientAddressMatchesPatterns
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -532,7 +532,7 @@ Accept wildcard characters: False
 
 ### -AnyOfToCcHeader
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -567,7 +567,7 @@ Accept wildcard characters: False
 
 ### -AnyOfToCcHeaderMemberOf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -602,7 +602,7 @@ Accept wildcard characters: False
 
 ### -AnyOfToHeader
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -637,7 +637,7 @@ Accept wildcard characters: False
 
 ### -AnyOfToHeaderMemberOf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -672,7 +672,7 @@ Accept wildcard characters: False
 
 ### -ApplyClassification
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an action or part of an action for the rule.
 
@@ -696,7 +696,7 @@ Accept wildcard characters: False
 
 ### -ApplyHtmlDisclaimerFallbackAction
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an action or part of an action for the rule.
 
@@ -731,7 +731,7 @@ Accept wildcard characters: False
 
 ### -ApplyHtmlDisclaimerLocation
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an action or part of an action for the rule.
 
@@ -758,7 +758,7 @@ Accept wildcard characters: False
 
 ### -ApplyHtmlDisclaimerText
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an action or part of an action for the rule.
 
@@ -857,7 +857,7 @@ Accept wildcard characters: False
 
 ### -ApplyRightsProtectionTemplate
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an action or part of an action for the rule.
 
@@ -885,7 +885,7 @@ Accept wildcard characters: False
 
 ### -AttachmentContainsWords
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -909,7 +909,7 @@ Accept wildcard characters: False
 
 ### -AttachmentExtensionMatchesWords
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -933,7 +933,7 @@ Accept wildcard characters: False
 
 ### -AttachmentHasExecutableContent
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -960,7 +960,7 @@ Accept wildcard characters: False
 
 ### -AttachmentIsPasswordProtected
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -985,7 +985,7 @@ Accept wildcard characters: False
 
 ### -AttachmentIsUnsupported
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -1016,7 +1016,7 @@ Accept wildcard characters: False
 
 ### -AttachmentMatchesPatterns
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -1042,7 +1042,7 @@ Accept wildcard characters: False
 
 ### -AttachmentNameMatchesPatterns
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -1064,7 +1064,7 @@ Accept wildcard characters: False
 
 ### -AttachmentProcessingLimitExceeded
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -1091,7 +1091,7 @@ Accept wildcard characters: False
 
 ### -AttachmentPropertyContainsWords
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -1132,7 +1132,7 @@ Accept wildcard characters: False
 
 ### -AttachmentSizeOver
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -1166,7 +1166,7 @@ Accept wildcard characters: False
 
 ### -BetweenMemberOf1
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -1197,7 +1197,7 @@ Accept wildcard characters: False
 
 ### -BetweenMemberOf2
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -1228,7 +1228,7 @@ Accept wildcard characters: False
 
 ### -BlindCopyTo
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an action or part of an action for the rule.
 
@@ -1259,7 +1259,7 @@ Accept wildcard characters: False
 
 ### -Comments
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Comments parameter specifies optional descriptive text for the rule (for example, what the rule is used for, or how it has changed over time). The length of the comment can't exceed 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -1277,7 +1277,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -1298,7 +1298,7 @@ Accept wildcard characters: False
 
 ### -ContentCharacterSetContainsWords
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -1322,7 +1322,7 @@ Accept wildcard characters: False
 
 ### -CopyTo
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an action or part of an action for the rule.
 
@@ -1353,7 +1353,7 @@ Accept wildcard characters: False
 
 ### -DeleteMessage
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an action or part of an action for the rule.
 
@@ -1378,7 +1378,7 @@ Accept wildcard characters: False
 
 ### -Disconnect
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter is functional only on Edge Transport servers in on-premises Exchange.
 
@@ -1403,7 +1403,7 @@ Accept wildcard characters: False
 
 ### -DlpPolicy
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 **Note**: This parameter is functional only in on-premises Exchange.
 
@@ -1423,7 +1423,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1445,7 +1445,7 @@ Accept wildcard characters: False
 
 ### -Enabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Enabled parameter specifies whether the new rule is created as enabled or disabled. Valid values are:
 
@@ -1468,7 +1468,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfADComparisonAttribute
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -1522,7 +1522,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfADComparisonOperator
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -1547,7 +1547,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfAnyOfCcHeader
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -1582,7 +1582,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfAnyOfCcHeaderMemberOf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -1617,7 +1617,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfAnyOfRecipientAddressContainsWords
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -1643,7 +1643,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfAnyOfRecipientAddressMatchesPatterns
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -1669,7 +1669,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfAnyOfToCcHeader
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -1704,7 +1704,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfAnyOfToCcHeaderMemberOf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -1739,7 +1739,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfAnyOfToHeader
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -1774,7 +1774,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfAnyOfToHeaderMemberOf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -1809,7 +1809,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfAttachmentContainsWords
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -1833,7 +1833,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfAttachmentExtensionMatchesWords
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -1857,7 +1857,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfAttachmentHasExecutableContent
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -1884,7 +1884,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfAttachmentIsPasswordProtected
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -1909,7 +1909,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfAttachmentIsUnsupported
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -1940,7 +1940,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfAttachmentMatchesPatterns
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -1966,7 +1966,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfAttachmentNameMatchesPatterns
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -1988,7 +1988,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfAttachmentProcessingLimitExceeded
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -2015,7 +2015,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfAttachmentPropertyContainsWords
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -2056,7 +2056,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfAttachmentSizeOver
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -2088,7 +2088,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfBetweenMemberOf1
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -2119,7 +2119,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfBetweenMemberOf2
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -2150,7 +2150,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfContentCharacterSetContainsWords
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -2174,7 +2174,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfFrom
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -2207,7 +2207,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfFromAddressContainsWords
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -2231,7 +2231,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfFromAddressMatchesPatterns
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -2257,7 +2257,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfFromMemberOf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -2290,7 +2290,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfFromScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -2315,7 +2315,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfHasClassification
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -2343,7 +2343,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfHasNoClassification
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -2368,7 +2368,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfHasSenderOverride
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 **Note:** This parameter is functional only in on-premises Exchange.
 
@@ -2395,7 +2395,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfHeaderContainsMessageHeader
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -2417,7 +2417,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfHeaderContainsWords
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -2443,7 +2443,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfHeaderMatchesMessageHeader
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -2465,7 +2465,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfHeaderMatchesPatterns
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -2489,7 +2489,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfManagerAddresses
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -2522,7 +2522,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfManagerForEvaluatedUser
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -2549,7 +2549,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfMessageContainsDataClassifications
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 **Note:** This parameter is functional only in on-premises Exchange.
 
@@ -2577,7 +2577,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfMessageSizeOver
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -2609,7 +2609,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfMessageTypeMatches
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -2641,7 +2641,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfRecipientADAttributeContainsWords
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -2699,7 +2699,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfRecipientADAttributeMatchesPatterns
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -2755,7 +2755,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfRecipientAddressContainsWords
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -2777,7 +2777,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfRecipientAddressMatchesPatterns
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -2801,7 +2801,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfRecipientDomainIs
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -2845,7 +2845,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfSCLOver
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -2872,7 +2872,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfSenderADAttributeContainsWords
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -2930,7 +2930,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfSenderADAttributeMatchesPatterns
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -2986,7 +2986,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfSenderDomainIs
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -3032,7 +3032,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfSenderIpRanges
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -3062,7 +3062,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfSenderManagementRelationship
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -3087,7 +3087,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfSentTo
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -3118,7 +3118,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfSentToMemberOf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -3147,7 +3147,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfSentToScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -3174,7 +3174,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfSubjectContainsWords
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -3200,7 +3200,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfSubjectMatchesPatterns
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -3222,7 +3222,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfSubjectOrBodyContainsWords
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -3248,7 +3248,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfSubjectOrBodyMatchesPatterns
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -3270,7 +3270,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfWithImportance
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -3296,7 +3296,7 @@ Accept wildcard characters: False
 
 ### -ExpiryDate
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -3318,7 +3318,7 @@ Accept wildcard characters: False
 
 ### -From
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -3351,7 +3351,7 @@ Accept wildcard characters: False
 
 ### -FromAddressContainsWords
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -3375,7 +3375,7 @@ Accept wildcard characters: False
 
 ### -FromAddressMatchesPatterns
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -3401,7 +3401,7 @@ Accept wildcard characters: False
 
 ### -FromMemberOf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -3434,7 +3434,7 @@ Accept wildcard characters: False
 
 ### -FromScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -3459,7 +3459,7 @@ Accept wildcard characters: False
 
 ### -GenerateIncidentReport
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an action or part of an action for the rule.
 
@@ -3490,7 +3490,7 @@ Accept wildcard characters: False
 
 ### -GenerateNotification
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an action or part of an action for the rule.
 
@@ -3523,7 +3523,7 @@ Accept wildcard characters: False
 
 ### -HasClassification
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -3551,7 +3551,7 @@ Accept wildcard characters: False
 
 ### -HasNoClassification
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -3576,7 +3576,7 @@ Accept wildcard characters: False
 
 ### -HasSenderOverride
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 **Note:** This parameter is functional only in on-premises Exchange.
 
@@ -3603,7 +3603,7 @@ Accept wildcard characters: False
 
 ### -HeaderContainsMessageHeader
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -3625,7 +3625,7 @@ Accept wildcard characters: False
 
 ### -HeaderContainsWords
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -3651,7 +3651,7 @@ Accept wildcard characters: False
 
 ### -HeaderMatchesMessageHeader
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -3673,7 +3673,7 @@ Accept wildcard characters: False
 
 ### -HeaderMatchesPatterns
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -3697,7 +3697,7 @@ Accept wildcard characters: False
 
 ### -IncidentReportContent
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an action or part of an action for the rule.
 
@@ -3765,7 +3765,7 @@ Accept wildcard characters: False
 
 ### -LogEventText
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter is functional only on Edge Transport servers in on-premises Exchange.
 
@@ -3795,7 +3795,7 @@ Accept wildcard characters: False
 
 ### -ManagerAddresses
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -3828,7 +3828,7 @@ Accept wildcard characters: False
 
 ### -ManagerForEvaluatedUser
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -3855,7 +3855,7 @@ Accept wildcard characters: False
 
 ### -MessageContainsDataClassifications
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 **Note:** This parameter is functional only in on-premises Exchange.
 
@@ -3885,7 +3885,7 @@ Accept wildcard characters: False
 
 ### -MessageSizeOver
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -3917,7 +3917,7 @@ Accept wildcard characters: False
 
 ### -MessageTypeMatches
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -3949,7 +3949,7 @@ Accept wildcard characters: False
 
 ### -Mode
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Mode parameter specifies how the rule operates. Valid values are:
 
@@ -3971,7 +3971,7 @@ Accept wildcard characters: False
 
 ### -ModerateMessageByManager
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an action or part of an action for the rule.
 
@@ -3998,7 +3998,7 @@ Accept wildcard characters: False
 
 ### -ModerateMessageByUser
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an action or part of an action for the rule.
 
@@ -4031,7 +4031,7 @@ Accept wildcard characters: False
 
 ### -NotifySender
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 **Note:** This parameter is functional only in on-premises Exchange.
 
@@ -4067,7 +4067,7 @@ Accept wildcard characters: False
 
 ### -PrependSubject
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an action or part of an action for the rule.
 
@@ -4091,7 +4091,7 @@ Accept wildcard characters: False
 
 ### -Priority
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Priority parameter specifies a priority value for the rule that determines the order of rule processing. A lower integer value indicates a higher priority, the value 0 is the highest priority, and rules can't have the same priority value.
 
@@ -4117,7 +4117,7 @@ Accept wildcard characters: False
 
 ### -Quarantine
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an action or part of an action for the rule.
 
@@ -4144,7 +4144,7 @@ Accept wildcard characters: False
 
 ### -RecipientADAttributeContainsWords
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -4202,7 +4202,7 @@ Accept wildcard characters: False
 
 ### -RecipientADAttributeMatchesPatterns
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -4258,7 +4258,7 @@ Accept wildcard characters: False
 
 ### -RecipientAddressContainsWords
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -4280,7 +4280,7 @@ Accept wildcard characters: False
 
 ### -RecipientAddressMatchesPatterns
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -4327,7 +4327,7 @@ Accept wildcard characters: False
 
 ### -RecipientDomainIs
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -4371,7 +4371,7 @@ Accept wildcard characters: False
 
 ### -RedirectMessageTo
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an action or part of an action for the rule.
 
@@ -4402,7 +4402,7 @@ Accept wildcard characters: False
 
 ### -RejectMessageEnhancedStatusCode
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an action or part of an action for the rule.
 
@@ -4430,7 +4430,7 @@ Accept wildcard characters: False
 
 ### -RejectMessageReasonText
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an action or part of an action for the rule.
 
@@ -4462,7 +4462,7 @@ Accept wildcard characters: False
 
 ### -RemoveHeader
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an action or part of an action for the rule.
 
@@ -4587,7 +4587,7 @@ Accept wildcard characters: False
 
 ### -RouteMessageOutboundRequireTls
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an action or part of an action for the rule.
 
@@ -4612,7 +4612,7 @@ Accept wildcard characters: False
 
 ### -RuleErrorAction
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The RuleErrorAction parameter specifies what to do if rule processing can't be completed on messages. Valid values are:
 
@@ -4633,7 +4633,7 @@ Accept wildcard characters: False
 
 ### -RuleSubType
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The RuleSubType parameter specifies the rule type. Valid values are:
 
@@ -4654,7 +4654,7 @@ Accept wildcard characters: False
 
 ### -SCLOver
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -4681,7 +4681,7 @@ Accept wildcard characters: False
 
 ### -SenderADAttributeContainsWords
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -4739,7 +4739,7 @@ Accept wildcard characters: False
 
 ### -SenderADAttributeMatchesPatterns
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -4795,7 +4795,7 @@ Accept wildcard characters: False
 
 ### -SenderAddressLocation
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The SenderAddressLocation parameter specifies where to look for sender addresses in conditions and exceptions that examine sender email addresses. Valid values are:
 
@@ -4825,7 +4825,7 @@ Accept wildcard characters: False
 
 ### -SenderDomainIs
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -4871,7 +4871,7 @@ Accept wildcard characters: False
 
 ### -SenderIpRanges
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -4901,7 +4901,7 @@ Accept wildcard characters: False
 
 ### -SenderManagementRelationship
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -4926,7 +4926,7 @@ Accept wildcard characters: False
 
 ### -SentTo
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -4957,7 +4957,7 @@ Accept wildcard characters: False
 
 ### -SentToMemberOf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -4990,7 +4990,7 @@ Accept wildcard characters: False
 
 ### -SentToScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -5017,7 +5017,7 @@ Accept wildcard characters: False
 
 ### -SetAuditSeverity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an action or part of an action for the rule.
 
@@ -5044,7 +5044,7 @@ Accept wildcard characters: False
 
 ### -SetHeaderName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an action or part of an action for the rule.
 
@@ -5066,7 +5066,7 @@ Accept wildcard characters: False
 
 ### -SetHeaderValue
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an action or part of an action for the rule.
 
@@ -5088,7 +5088,7 @@ Accept wildcard characters: False
 
 ### -SetSCL
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an action or part of an action for the rule.
 
@@ -5113,7 +5113,7 @@ Accept wildcard characters: False
 
 ### -SmtpRejectMessageRejectStatusCode
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter is functional only on Edge Transport servers in on-premises Exchange.
 
@@ -5137,7 +5137,7 @@ Accept wildcard characters: False
 
 ### -SmtpRejectMessageRejectText
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter is functional only on Edge Transport servers in on-premises Exchange.
 
@@ -5161,7 +5161,7 @@ Accept wildcard characters: False
 
 ### -StopRuleProcessing
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an action or part of an action for the rule.
 
@@ -5186,7 +5186,7 @@ Accept wildcard characters: False
 
 ### -SubjectContainsWords
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -5212,7 +5212,7 @@ Accept wildcard characters: False
 
 ### -SubjectMatchesPatterns
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -5234,7 +5234,7 @@ Accept wildcard characters: False
 
 ### -SubjectOrBodyContainsWords
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -5260,7 +5260,7 @@ Accept wildcard characters: False
 
 ### -SubjectOrBodyMatchesPatterns
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -5282,7 +5282,7 @@ Accept wildcard characters: False
 
 ### -UseLegacyRegex
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The UseLegacyRegex parameter specifies whether the rule uses regular expression syntax that's compatible with Exchange Server 2010. Valid values are:
 
@@ -5303,7 +5303,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
@@ -5321,7 +5321,7 @@ Accept wildcard characters: False
 
 ### -WithImportance
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-WebServicesVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/New-WebServicesVirtualDirectory.md
index a3d3fc0bc0..5fd6367dd4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-WebServicesVirtualDirectory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-WebServicesVirtualDirectory.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -68,7 +68,7 @@ This example creates a virtual directory under the non-default website www.conto
 
 ### -ApplicationRoot
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ApplicationRoot parameter specifies the metabase path of the virtual directory. By default, this path is the same as the website in which the virtual directory is created.
 
@@ -86,7 +86,7 @@ Accept wildcard characters: False
 
 ### -AppPoolId
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AppPoolId parameter specifies the IIS application pool in which the virtual directory runs. We recommend that you leave this parameter at its default setting.
 
@@ -104,7 +104,7 @@ Accept wildcard characters: False
 
 ### -AppPoolIdForManagement
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AppPoolIdForManagement parameter specifies the pool of programs that manages the virtual directory.
 
@@ -122,7 +122,7 @@ Accept wildcard characters: False
 
 ### -BasicAuthentication
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The BasicAuthentication parameter specifies whether Basic authentication is enabled on the virtual directory. Valid values are:
 
@@ -143,7 +143,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -164,7 +164,7 @@ Accept wildcard characters: False
 
 ### -DigestAuthentication
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DigestAuthentication parameter specifies whether Digest authentication is enabled on the virtual directory. Valid values are:
 
@@ -185,7 +185,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -203,7 +203,7 @@ Accept wildcard characters: False
 
 ### -ExtendedProtectionFlags
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExtendedProtectionFlags parameter specifies custom settings for Extended Protection for Authentication on the virtual directory. Valid values are:
 
@@ -227,7 +227,7 @@ Accept wildcard characters: False
 
 ### -ExtendedProtectionSPNList
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExtendedProtectionSPNList parameter specifies a list of valid Service Principal Names (SPNs) if you're using Extended Protection for Authentication on the virtual directory. Valid values are:
 
@@ -248,7 +248,7 @@ Accept wildcard characters: False
 
 ### -ExtendedProtectionTokenChecking
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExtendedProtectionTokenChecking parameter defines how you want to use Extended Protection for Authentication on the virtual directory. Extended Protection for Authentication isn't enabled by default. Valid values are:
 
@@ -272,7 +272,7 @@ Accept wildcard characters: False
 
 ### -ExternalUrl
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExternalURL parameter specifies the URL that's used to connect to the virtual directory from outside the firewall.
 
@@ -292,7 +292,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -312,7 +312,7 @@ Accept wildcard characters: False
 
 ### -GzipLevel
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The GzipLevel parameter sets the Gzip configuration for the Exchange Web Services virtual directory. Valid values are:
 
@@ -335,7 +335,7 @@ Accept wildcard characters: False
 
 ### -InternalNLBBypassUrl
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The InternalNLBBypassUrl parameter specifies the URL of the Exchange server that has the Client Access server role installed, regardless of whether it's behind a Network Load Balancing (NLB) array or not.
 
@@ -355,7 +355,7 @@ Accept wildcard characters: False
 
 ### -InternalUrl
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The InternalURL parameter specifies the URL that's used to connect to the virtual directory from inside the firewall.
 
@@ -375,7 +375,7 @@ Accept wildcard characters: False
 
 ### -MRSProxyEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MRSProxyEnabled parameter specifies whether to enable MRSProxy for the Mailbox server. MRSProxy is a service that runs on Mailbox servers in a remote forest and helps to proxy a mailbox move. For more information, see [Mailbox moves in Exchange Server](https://learn.microsoft.com/Exchange/recipients/mailbox-moves).
 
@@ -413,7 +413,7 @@ Accept wildcard characters: False
 
 ### -OAuthAuthentication
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The OAuthAuthentication parameter specifies whether OAuth authentication is enabled on the virtual directory. Valid values are:
 
@@ -434,7 +434,7 @@ Accept wildcard characters: False
 
 ### -Path
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Path parameter sets the path of the virtual directory in the metabase.
 
@@ -452,7 +452,7 @@ Accept wildcard characters: False
 
 ### -Role
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Role parameter species the configuration for the virtual directory. Valid values are:
 
@@ -475,7 +475,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Exchange server that hosts the virtual directory. You can use any value that uniquely identifies the server. For example:
 
@@ -498,7 +498,7 @@ Accept wildcard characters: False
 
 ### -WebSiteName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WebSiteName parameter specifies the name of the website under which to create the virtual directory. This parameter shouldn't be used when you're creating a virtual directory under the default website.
 
@@ -516,7 +516,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
@@ -534,7 +534,7 @@ Accept wildcard characters: False
 
 ### -WindowsAuthentication
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WindowsAuthentication parameter specifies whether Integrated Windows authentication is enabled on the virtual directory. Valid values are:
 
@@ -555,7 +555,7 @@ Accept wildcard characters: False
 
 ### -WSSecurityAuthentication
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WSSecurityAuthentication parameter specifies whether WS-Security (Web Services Security) authentication is enabled on the virtual directory. Valid values are:
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/New-X400AuthoritativeDomain.md b/exchange/exchange-ps/ExchangePowerShell/New-X400AuthoritativeDomain.md
index af13148098..076d4f9729 100644
--- a/exchange/exchange-ps/ExchangePowerShell/New-X400AuthoritativeDomain.md
+++ b/exchange/exchange-ps/ExchangePowerShell/New-X400AuthoritativeDomain.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -87,7 +87,7 @@ This example creates an external relay domain for the X.400 namespace Europe org
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Name parameter specifies the unique name for the X.400 authoritative domain. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -105,7 +105,7 @@ Accept wildcard characters: False
 
 ### -X400DomainName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The X400DomainName parameter specifies the X.400 namespace, which can only include the X.400 organizational components. Specifically, only the following attribute types are supported:
 
@@ -134,7 +134,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -155,7 +155,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -175,7 +175,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
@@ -193,7 +193,7 @@ Accept wildcard characters: False
 
 ### -X400ExternalRelay
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The X400ExternalRelay parameter specifies authoritative domain an external relay domain. If you set the X400ExternalRelay parameter to $true, Microsoft Exchange routes email to the external address and doesn't treat resolution failures to this subdomain as an error.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Redirect-Message.md b/exchange/exchange-ps/ExchangePowerShell/Redirect-Message.md
index 4ff9812e91..05f186c4c4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Redirect-Message.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Redirect-Message.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -50,7 +50,7 @@ This example drains the active messages from the delivery queues on the Mailbox
 
 ### -Server
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the source Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
 
@@ -73,7 +73,7 @@ Accept wildcard characters: False
 
 ### -Target
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Target parameter specifies the target Mailbox server where you want to transfer the messages from the drained delivery queues. Enter the server name as a fully qualified domain name (FQDN).
 
@@ -91,7 +91,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -112,7 +112,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ADPermission.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ADPermission.md
index 590b14b804..f51aa603d1 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-ADPermission.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ADPermission.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -88,7 +88,7 @@ This example removes the ability for anonymous users to send messages through th
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the object from which the permission should be removed.
 
@@ -108,7 +108,7 @@ Accept wildcard characters: False
 
 ### -Instance
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Instance parameter enables you to pass an entire object to the command to be processed. It's mainly used in scripts where an entire object must be passed to the command.
 
@@ -126,7 +126,7 @@ Accept wildcard characters: False
 
 ### -User
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The User parameter specifies whose permissions are being removed from the Active Directory object. You can specify the following types of users or groups:
 
@@ -166,7 +166,7 @@ Accept wildcard characters: False
 
 ### -AccessRights
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AccessRights parameter specifies the rights that you want to remove from the user on the Active Directory object. Valid values include:
 
@@ -206,7 +206,7 @@ Accept wildcard characters: False
 
 ### -ChildObjectTypes
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ChildObjectTypes parameter specifies what type of object the permission should be removed from.
 
@@ -226,7 +226,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -247,7 +247,7 @@ Accept wildcard characters: False
 
 ### -Deny
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Deny switch specifies that the permissions you're removing are Deny permissions. You don't need to specify a value with this switch.
 
@@ -265,7 +265,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -285,7 +285,7 @@ Accept wildcard characters: False
 
 ### -ExtendedRights
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExtendedRights parameter specifies the extended rights to remove.
 
@@ -303,7 +303,7 @@ Accept wildcard characters: False
 
 ### -InheritanceType
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The InheritanceType parameter specifies how permissions are inherited. Valid values are:
 
@@ -327,7 +327,7 @@ Accept wildcard characters: False
 
 ### -InheritedObjectType
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The InheritedObjectType parameter specifies what kind of object inherits this access control entry (ACE).
 
@@ -345,7 +345,7 @@ Accept wildcard characters: False
 
 ### -Properties
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Properties parameter specifies what properties the object contains.
 
@@ -365,7 +365,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-AcceptedDomain.md b/exchange/exchange-ps/ExchangePowerShell/Remove-AcceptedDomain.md
index 4d52a5ac4c..e52512ac6c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-AcceptedDomain.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-AcceptedDomain.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -45,7 +45,7 @@ This example removes the accepted domain Contoso.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the accepted domain you want to remove. Enter either the GUID or the name of the remote domain.
 
@@ -63,7 +63,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -84,7 +84,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -104,7 +104,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncDevice.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncDevice.md
index 53d507564f..e999d2e4a6 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncDevice.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncDevice.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
 Locale: en-US
@@ -63,7 +63,7 @@ This example removes the mobile device partnership for the device named Tablet\_
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter uniquely identifies the specific device partnership to be removed.
 
@@ -81,7 +81,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -102,7 +102,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -122,7 +122,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncDeviceAccessRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncDeviceAccessRule.md
index 252701126d..749904cbf9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncDeviceAccessRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncDeviceAccessRule.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
 Locale: en-US
@@ -54,7 +54,7 @@ This example removes all device access rules that have a name that starts with C
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the identity of the device access rule.
 
@@ -72,7 +72,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -93,7 +93,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -113,7 +113,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncDeviceClass.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncDeviceClass.md
index 4cb1c29820..ae96896997 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncDeviceClass.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncDeviceClass.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
 Locale: en-US
@@ -47,7 +47,7 @@ This example retrieves the list of devices connecting to Microsoft Exchange and
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the group of devices on which to scope the task.
 
@@ -65,7 +65,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -86,7 +86,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -104,7 +104,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncMailboxPolicy.md
index 529397252e..d800c7776c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncMailboxPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncMailboxPolicy.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
 Locale: en-US
@@ -57,7 +57,7 @@ This example removes the mobile device mailbox policy named Management and bypas
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the mobile device mailbox policy that you want to remove. You can use any value that uniquely identifies the policy. For example:
 
@@ -79,7 +79,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -100,7 +100,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -120,7 +120,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -140,7 +140,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncVirtualDirectory.md
index 781217db58..0d298379c4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncVirtualDirectory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ActiveSyncVirtualDirectory.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
 Locale: en-US
@@ -61,7 +61,7 @@ This example removes a custom Exchange ActiveSync virtual directory from the ser
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the Exchange ActiveSync virtual directory that you want to remove. You can use any value that uniquely identifies the virtual directory. For example:
 
@@ -85,7 +85,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -106,7 +106,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -124,7 +124,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-AddressBookPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-AddressBookPolicy.md
index e878164f2d..a074082f24 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-AddressBookPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-AddressBookPolicy.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -51,7 +51,7 @@ This example deletes the address book policy Murchison's Class.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the identity of the address book policy that you want to remove.
 
@@ -69,7 +69,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -90,7 +90,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -110,7 +110,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-AddressList.md b/exchange/exchange-ps/ExchangePowerShell/Remove-AddressList.md
index 02ce9abe28..9def5d8847 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-AddressList.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-AddressList.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -53,7 +53,7 @@ This example removes the address list named AddressList1 and all of its child ad
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the address list that you want to remove. You can use any value that uniquely identifies the address list. For example:
 
@@ -78,7 +78,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -99,7 +99,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -119,7 +119,7 @@ Accept wildcard characters: False
 
 ### -Recursive
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Recursive switch specifies whether to remove all child address lists. You don't need to specify a value for this switch.
 
@@ -139,7 +139,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-AddressRewriteEntry.md b/exchange/exchange-ps/ExchangePowerShell/Remove-AddressRewriteEntry.md
index e4e75d866f..63385b48ca 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-AddressRewriteEntry.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-AddressRewriteEntry.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
 Locale: en-US
@@ -56,7 +56,7 @@ This example removes all address rewrite entries that include contoso.com in the
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the address rewrite entry you want to remove. The Identity parameter accepts a GUID or the unique address rewrite name. You can omit the Identity parameter label.
 
@@ -74,7 +74,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -95,7 +95,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -115,7 +115,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-App.md b/exchange/exchange-ps/ExchangePowerShell/Remove-App.md
index 1c77501a84..0d998b170b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-App.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-App.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.WebClient-Help.xml
 Locale: en-US
@@ -51,7 +51,7 @@ This example removes the Finance Test app installed for user Tony.
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the AppID (GUID value) of the app that you want to remove. To find the GUID value of an app, run the command Get-App | Format-Table -Auto DisplayName,AppId.
 
@@ -89,7 +89,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -110,7 +110,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -130,7 +130,7 @@ Accept wildcard characters: False
 
 ### -Mailbox
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Mailbox parameter specifies the mailbox that you want to modify. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -159,7 +159,7 @@ Accept wildcard characters: False
 
 ### -OrganizationApp
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The OrganizationApp switch specifies that the scope of the app is organizational. You don't need to specify a value with this switch.
 
@@ -179,7 +179,7 @@ Accept wildcard characters: False
 
 ### -PrivateCatalog
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The PrivateCatalog switch specifies that the app you want to remove is located in a private catalog. You don't need to specify a value with this switch.
 
@@ -197,7 +197,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-AttachmentFilterEntry.md b/exchange/exchange-ps/ExchangePowerShell/Remove-AttachmentFilterEntry.md
index 2ba825ebe3..ea755ecb19 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-AttachmentFilterEntry.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-AttachmentFilterEntry.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
 Locale: en-US
@@ -54,7 +54,7 @@ This example removes the attachment filter entry that filters attachments that h
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the type of attachment that this filter entry removes. The Identity parameter accepts values in the format Type:Name, where Type is one of the following two values:
 
@@ -77,7 +77,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -98,7 +98,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -118,7 +118,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-AuthRedirect.md b/exchange/exchange-ps/ExchangePowerShell/Remove-AuthRedirect.md
index 42edc677b5..2b6f344d38 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-AuthRedirect.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-AuthRedirect.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -52,7 +52,7 @@ This example removes all existing OAuth redirection objects from your organizati
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the existing OAuth redirection object that you want to remove. The object name uses the syntax `AuthRedirect-Bearer-GUID`. The easiest way to find the name of the OAuth redirection object is to run Get-AuthRedirect.
 
@@ -70,7 +70,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -91,7 +91,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -109,7 +109,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-AuthServer.md b/exchange/exchange-ps/ExchangePowerShell/Remove-AuthServer.md
index a611561cbd..7fb750f295 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-AuthServer.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-AuthServer.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -45,7 +45,7 @@ This example removes the authorization server named AMC.
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the authorization server object that you want to remove. You can use any value that uniquely identifies the authorization server. For example:
 
@@ -67,7 +67,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -88,7 +88,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -106,7 +106,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-AuthenticationPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-AuthenticationPolicy.md
index 2a4e144071..c6053a0e63 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-AuthenticationPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-AuthenticationPolicy.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -53,7 +53,7 @@ In Exchange Online, this example enables legacy Exchange tokens to be issued to
 
 ### -Identity
 
-> Applicable: Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the authentication policy you want to remove. You can use any value that uniquely identifies the policy. For example:
 
@@ -106,7 +106,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -147,7 +147,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-AutodiscoverVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Remove-AutodiscoverVirtualDirectory.md
index 32c9ff50f0..d8cc8b9d69 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-AutodiscoverVirtualDirectory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-AutodiscoverVirtualDirectory.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -45,7 +45,7 @@ This example removes the Autodiscover virtual directory from the site autodiscov
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the Autodiscover virtual directory that you want to remove. You can use any value that uniquely identifies the virtual directory. For example:
 
@@ -69,7 +69,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -90,7 +90,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -108,7 +108,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-AvailabilityAddressSpace.md b/exchange/exchange-ps/ExchangePowerShell/Remove-AvailabilityAddressSpace.md
index 3f035835bd..3fb0f0cda6 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-AvailabilityAddressSpace.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-AvailabilityAddressSpace.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
 Locale: en-US
@@ -54,7 +54,7 @@ This example immediately removes the availability address space object named Con
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the availability address that you want to remove. You can use any value that uniquely identifies the object. For example:
 
@@ -76,7 +76,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -97,7 +97,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -117,7 +117,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-CalendarEvents.md b/exchange/exchange-ps/ExchangePowerShell/Remove-CalendarEvents.md
index 37af6e5b5e..bee5da9ccb 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-CalendarEvents.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-CalendarEvents.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
 Locale: en-US
@@ -64,7 +64,7 @@ This example previews the meetings that would be cancelled in Jacob Berger's cal
 
 ### -Identity
 
-> Applicable: Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the mailbox that you want to modify. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -93,7 +93,7 @@ Accept wildcard characters: False
 
 ### -QueryWindowInDays
 
-> Applicable: Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The QueryWindowInDays parameter specifies the number of days after the QueryStartDate parameter value to look for meetings that you want to cancel.
 
@@ -115,7 +115,7 @@ Accept wildcard characters: False
 
 ### -CancelOrganizedMeetings
 
-> Applicable: Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The CancelOrganizedMeetings switch specifies whether to cancel meetings in the mailbox. You don't need to specify a value with this switch.
 
@@ -135,7 +135,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -156,7 +156,7 @@ Accept wildcard characters: False
 
 ### -PreviewOnly
 
-> Applicable: Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The PreviewOnly switch specifies whether to preview the results of the command without actually cancelling any meetings. You don't need to specify a value with this switch.
 
@@ -176,7 +176,7 @@ Accept wildcard characters: False
 
 ### -QueryStartDate
 
-> Applicable: Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The QueryStartDate parameter specifies the start date to look for meetings that you want to cancel.
 
@@ -220,7 +220,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ClassificationRuleCollection.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ClassificationRuleCollection.md
index 67d123a26f..0ff6b967a2 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-ClassificationRuleCollection.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ClassificationRuleCollection.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -47,7 +47,7 @@ This example removes the classification rule collection named External Classific
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the classification rule collection you want to remove. You can use any value that uniquely identifies the classification rule collection. For example, you can specify the name, rule collection name or distinguished name (DN) of the classification rule collection.
 
@@ -65,7 +65,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -86,7 +86,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -106,7 +106,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ClientAccessRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ClientAccessRule.md
index 81d804fa9c..834cc6b4ad 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-ClientAccessRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ClientAccessRule.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.WebClient-Help.xml
 Locale: en-US
@@ -50,7 +50,7 @@ This example removes the existing client access rule named "Block Connections fr
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the client access rule that you want to remove. You can use any value that uniquely identifies the client access rule. For example:
 
@@ -72,7 +72,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -93,7 +93,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -113,7 +113,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ComplianceSearch.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ComplianceSearch.md
index 523371b286..7c9d9fe70d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-ComplianceSearch.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ComplianceSearch.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 author: chrisda
 external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
 Locale: en-US
@@ -48,7 +48,7 @@ This example removes the compliance search named Case 1234
 
 ### -Identity
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The Identity parameter specifies the compliance search that you want to remove.
 
@@ -73,7 +73,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -94,7 +94,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The WhatIf switch doesn't work in Security & Compliance PowerShell.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ComplianceSecurityFilter.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ComplianceSecurityFilter.md
index b389657e6e..c5d810d5e4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-ComplianceSecurityFilter.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ComplianceSecurityFilter.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 author: chrisda
 external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
 Locale: en-US
@@ -44,7 +44,7 @@ This example removes the compliance security filter named HR Filter.
 
 ### -FilterName
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The FilterName parameter specifies the name of the compliance security filter that you want to remove. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -62,7 +62,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -83,7 +83,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The WhatIf switch doesn't work in Security & Compliance PowerShell.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ContentFilterPhrase.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ContentFilterPhrase.md
index 8598c8c44c..70e9dfa355 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-ContentFilterPhrase.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ContentFilterPhrase.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailControl-Help.xml
 Locale: en-US
@@ -55,7 +55,7 @@ This example removes the custom phrase Free credit report from the list of phras
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies a custom word or phrase to remove. You must enclose the value of the Identity parameter in quotation marks (").
 
@@ -75,7 +75,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -96,7 +96,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -116,7 +116,7 @@ Accept wildcard characters: False
 
 ### -Phrase
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Phrase parameter specifies a custom word or phrase to remove. You must enclose the value of the Phrase parameter in quotation marks (").
 
@@ -136,7 +136,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-DataClassification.md b/exchange/exchange-ps/ExchangePowerShell/Remove-DataClassification.md
index 11847d2a17..18bff51df5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-DataClassification.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-DataClassification.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -49,7 +49,7 @@ This example removes the data classification rule named "Contoso Confidential".
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the data classification rule that you want to remove. You can use any value that uniquely identifies the data classification rule. For example:
 
@@ -71,7 +71,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -92,7 +92,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -110,7 +110,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-DatabaseAvailabilityGroup.md b/exchange/exchange-ps/ExchangePowerShell/Remove-DatabaseAvailabilityGroup.md
index d80ad23b93..5438ddd878 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-DatabaseAvailabilityGroup.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-DatabaseAvailabilityGroup.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -45,7 +45,7 @@ This example, deletes the DAG DAG1.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the name of the DAG to be removed.
 
@@ -63,7 +63,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -84,7 +84,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -102,7 +102,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-DatabaseAvailabilityGroupNetwork.md b/exchange/exchange-ps/ExchangePowerShell/Remove-DatabaseAvailabilityGroupNetwork.md
index 398452c4aa..aa5781d103 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-DatabaseAvailabilityGroupNetwork.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-DatabaseAvailabilityGroupNetwork.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -45,7 +45,7 @@ This example removes the DAG network DAGNetwork04 from the DAG DAG1.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the name of the network being removed.
 
@@ -63,7 +63,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -84,7 +84,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -102,7 +102,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-DatabaseAvailabilityGroupServer.md b/exchange/exchange-ps/ExchangePowerShell/Remove-DatabaseAvailabilityGroupServer.md
index 47cfb67982..ee1ceedf9a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-DatabaseAvailabilityGroupServer.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-DatabaseAvailabilityGroupServer.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -54,7 +54,7 @@ This example removes the configuration settings for the Mailbox server MBX4 from
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the name of the DAG from which you're removing the server.
 
@@ -72,7 +72,7 @@ Accept wildcard characters: False
 
 ### -MailboxServer
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MailboxServer parameter specifies the Mailbox server to remove from the DAG. You can use any value that uniquely identifies the server. For example:
 
@@ -95,7 +95,7 @@ Accept wildcard characters: False
 
 ### -ConfigurationOnly
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ConfigurationOnly switch remove the Mailbox server from the DAG object in Active Directory. You don't need to specify a value with this switch.
 
@@ -117,7 +117,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -138,7 +138,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -156,7 +156,7 @@ Accept wildcard characters: False
 
 ### -SkipDagValidation
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SkipDagValidation switch specifies whether to bypass the validation of the DAG's quorum model and the health check on the DAG's witness when removing members from the DAG. You don't need to specify a value with this switch.
 
@@ -174,7 +174,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-DeliveryAgentConnector.md b/exchange/exchange-ps/ExchangePowerShell/Remove-DeliveryAgentConnector.md
index f44ef1cb27..3194730264 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-DeliveryAgentConnector.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-DeliveryAgentConnector.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -47,7 +47,7 @@ This example removes the delivery agent connector named Contoso Delivery Agent C
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the GUID or name of the delivery agent connector.
 
@@ -65,7 +65,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -86,7 +86,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -106,7 +106,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-DistributionGroup.md b/exchange/exchange-ps/ExchangePowerShell/Remove-DistributionGroup.md
index cf0c056d74..383997a66e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-DistributionGroup.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-DistributionGroup.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
 Locale: en-US
@@ -47,7 +47,7 @@ This example removes the distribution group named Temporary Staff.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the distribution group or mail-enabled security group that you want to remove. You can use any value that uniquely identifies the group. For example:
 
@@ -72,7 +72,7 @@ Accept wildcard characters: False
 
 ### -BypassSecurityGroupManagerCheck
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The BypassSecurityGroupManagerCheck switch specifies whether to allow a user who isn't an owner of the group to modify or delete the group. You don't need to specify a value with this switch.
 
@@ -95,7 +95,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -116,7 +116,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -136,7 +136,7 @@ Accept wildcard characters: False
 
 ### -IgnoreDefaultScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -161,7 +161,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-DistributionGroupMember.md b/exchange/exchange-ps/ExchangePowerShell/Remove-DistributionGroupMember.md
index 4e4bc7777a..48f4e68cfb 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-DistributionGroupMember.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-DistributionGroupMember.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
 Locale: en-US
@@ -49,7 +49,7 @@ This example removes Jan Dryml from the distribution group named Technical Suppo
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the distribution group or mail-enabled security group that you want to modify. You can use any value that uniquely identifies the group. For example:
 
@@ -74,7 +74,7 @@ Accept wildcard characters: False
 
 ### -BypassSecurityGroupManagerCheck
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The BypassSecurityGroupManagerCheck switch specifies whether to allow a user who isn't an owner of the group to modify or delete the group. You don't need to specify a value with this switch.
 
@@ -97,7 +97,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -118,7 +118,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -138,7 +138,7 @@ Accept wildcard characters: False
 
 ### -Member
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Member parameter specifies the recipient that you want to remove from the group. You can use any value that uniquely identifies the recipient. For example:
 
@@ -163,7 +163,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-DlpPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-DlpPolicy.md
index 7f63c45109..95997ba529 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-DlpPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-DlpPolicy.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -47,7 +47,7 @@ This example removes the existing DLP policy named Contoso PII.
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the DLP policy that you want to remove. You can use any value that uniquely identifies the policy. For example:
 
@@ -69,7 +69,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -90,7 +90,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -108,7 +108,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-DlpPolicyTemplate.md b/exchange/exchange-ps/ExchangePowerShell/Remove-DlpPolicyTemplate.md
index bce7076d60..dad0fa5c40 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-DlpPolicyTemplate.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-DlpPolicyTemplate.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -45,7 +45,7 @@ This example removes the DLP policy template named External DLP Policy Template.
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the DLP policy template you want to remove. You can use any value that uniquely identifies the DLP policy template. For example, you can specify the name, GUID or distinguished name (DN) of the DLP policy template.
 
@@ -63,7 +63,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -84,7 +84,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -102,7 +102,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-DynamicDistributionGroup.md b/exchange/exchange-ps/ExchangePowerShell/Remove-DynamicDistributionGroup.md
index 2070951572..d39e9ff8ea 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-DynamicDistributionGroup.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-DynamicDistributionGroup.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
 Locale: en-US
@@ -46,7 +46,7 @@ This example deletes the dynamic distribution group named Test Users.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the dynamic distribution group that you want to remove. You can use any value that uniquely identifies the dynamic distribution group. For example:
 
@@ -71,7 +71,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -92,7 +92,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -112,7 +112,7 @@ Accept wildcard characters: False
 
 ### -IgnoreDefaultScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -137,7 +137,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-EcpVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Remove-EcpVirtualDirectory.md
index f38307da67..675fe966a7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-EcpVirtualDirectory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-EcpVirtualDirectory.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -47,7 +47,7 @@ This example removes the ECP virtual directory named ecp located on the default
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the ECP virtual directory that you want to remove. You can use any value that uniquely identifies the virtual directory. For example:
 
@@ -73,7 +73,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -94,7 +94,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -112,7 +112,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-EdgeSubscription.md b/exchange/exchange-ps/ExchangePowerShell/Remove-EdgeSubscription.md
index ab2e694756..be87832098 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-EdgeSubscription.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-EdgeSubscription.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -53,7 +53,7 @@ This example removes Edge Subscription for the Edge Transport server named Edge1
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the identity of the Edge Transport server for which you want to remove Edge Subscription. The identity is expressed as the host name of the Edge Transport server.
 
@@ -71,7 +71,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -92,7 +92,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -112,7 +112,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -132,7 +132,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-EmailAddressPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-EmailAddressPolicy.md
index 659c486619..6c2632e510 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-EmailAddressPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-EmailAddressPolicy.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -45,7 +45,7 @@ This example removes the email address policy named Southwest Executives.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the email address policy that you want to remove. You can use any value that uniquely identifies the policy. For example:
 
@@ -67,7 +67,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -88,7 +88,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -108,7 +108,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ExchangeCertificate.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ExchangeCertificate.md
index 759c87b53a..d0baf2ebd7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-ExchangeCertificate.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ExchangeCertificate.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -69,7 +69,7 @@ This example uses the same settings, but removes the certificate from the server
 
 ### -Thumbprint
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Thumbprint parameter specifies the certificate that you want to remove. You can find the thumbprint value by using the Get-ExchangeCertificate cmdlet.
 
@@ -89,7 +89,7 @@ Accept wildcard characters: False
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the certificate that you want to remove. Valid values are:
 
@@ -116,7 +116,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -137,7 +137,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -157,7 +157,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
 
@@ -184,7 +184,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-FederatedDomain.md b/exchange/exchange-ps/ExchangePowerShell/Remove-FederatedDomain.md
index a902c0d79e..e9808471ac 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-FederatedDomain.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-FederatedDomain.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
 Locale: en-US
@@ -52,7 +52,7 @@ This example removes the federated domain contoso.co.uk from the federated organ
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -70,7 +70,7 @@ Accept wildcard characters: False
 
 ### -DomainName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainName parameter specifies the federated domain name to be removed from the federated organization identifier.
 
@@ -88,7 +88,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -109,7 +109,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -127,7 +127,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Force switch specifies whether to suppress warning or confirmation messages when removing a federated domain. You don't need to specify a value with this switch.
 
@@ -147,7 +147,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-FederationTrust.md b/exchange/exchange-ps/ExchangePowerShell/Remove-FederationTrust.md
index 7fe23723a4..cc5b1d537f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-FederationTrust.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-FederationTrust.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
 Locale: en-US
@@ -47,7 +47,7 @@ This example removes the federation trust Microsoft Federation Gateway.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the identity of the federation trust being removed.
 
@@ -65,7 +65,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -86,7 +86,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -104,7 +104,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ForeignConnector.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ForeignConnector.md
index ec31d4ab73..96bc0488fc 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-ForeignConnector.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ForeignConnector.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -49,7 +49,7 @@ This example deletes the Foreign connector named Fax Connector.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the GUID or connector name of a specific Foreign connector. You can also include the server name by using the format ServerName\\ConnectorName.
 
@@ -67,7 +67,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -88,7 +88,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -108,7 +108,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-GlobalAddressList.md b/exchange/exchange-ps/ExchangePowerShell/Remove-GlobalAddressList.md
index aa81c3aac7..fa78078f11 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-GlobalAddressList.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-GlobalAddressList.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -47,7 +47,7 @@ This example removes the GAL named OldGAL.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the global address list that you want to remove. You can use any value that uniquely identifies the GAL. For example:
 
@@ -69,7 +69,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -90,7 +90,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -110,7 +110,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-GlobalMonitoringOverride.md b/exchange/exchange-ps/ExchangePowerShell/Remove-GlobalMonitoringOverride.md
index a2657bb1a4..c940398a59 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-GlobalMonitoringOverride.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-GlobalMonitoringOverride.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -54,7 +54,7 @@ This example removes a global monitoring override of the ExtensionAttributes pro
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the monitoring item that was overridden. The value is in the form of HealthSet\\MonitoringItem or HealthSet\\MonitoringItem\\TargetResource.
 
@@ -72,7 +72,7 @@ Accept wildcard characters: False
 
 ### -ItemType
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ItemType parameter specifies the item type that you want to remove. It can be any of the following values:
 
@@ -94,7 +94,7 @@ Accept wildcard characters: False
 
 ### -PropertyName
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PropertyName parameter specifies the property for the override you want to remove.
 
@@ -112,7 +112,7 @@ Accept wildcard characters: False
 
 ### -BuildRange
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -130,7 +130,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -151,7 +151,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -171,7 +171,7 @@ Accept wildcard characters: False
 
 ### -Roles
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -189,7 +189,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-HybridConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Remove-HybridConfiguration.md
index 612fd6ffd0..7d69254dc4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-HybridConfiguration.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-HybridConfiguration.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -46,7 +46,7 @@ This example removes the HybridConfiguration object for the hybrid deployment.
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -67,7 +67,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -87,7 +87,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-IPAllowListEntry.md b/exchange/exchange-ps/ExchangePowerShell/Remove-IPAllowListEntry.md
index 1eb3678517..2ef113d683 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-IPAllowListEntry.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-IPAllowListEntry.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailControl-Help.xml
 Locale: en-US
@@ -52,7 +52,7 @@ This example removes the IP address range 192.168.0.0/24 from the IP Allow list.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the integer value of the IP Allow list entry that you want to remove. When you add an entry to the IP Allow list, the Identity value is automatically assigned. To find the Identity value of an IP Allow list entry, use the Get-IPAllowListEntry cmdlet.
 
@@ -70,7 +70,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -91,7 +91,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
 
@@ -118,7 +118,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-IPAllowListProvider.md b/exchange/exchange-ps/ExchangePowerShell/Remove-IPAllowListProvider.md
index 59c3544dac..ee2fc3e4c7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-IPAllowListProvider.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-IPAllowListProvider.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailControl-Help.xml
 Locale: en-US
@@ -45,7 +45,7 @@ This example removes the IP Allow list provider named Contoso.com.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the IP Allow list provider that you want to remove. You can use any value that uniquely identifies the IP Allow list provider. For example:
 
@@ -67,7 +67,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -88,7 +88,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -108,7 +108,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-IPBlockListEntry.md b/exchange/exchange-ps/ExchangePowerShell/Remove-IPBlockListEntry.md
index 6fc2815694..ced2083df8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-IPBlockListEntry.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-IPBlockListEntry.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailControl-Help.xml
 Locale: en-US
@@ -52,7 +52,7 @@ This example removes the IP address range 192.168.0.0/24 from the IP Block list.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the integer value of the IP Block list entry that you want to remove. When you add an entry to the IP Block list, the Identity value is automatically assigned. To find the Identity value of an IP Block list entry, use the Get-IPBlockListEntry cmdlet.
 
@@ -70,7 +70,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -91,7 +91,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
 
@@ -118,7 +118,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-IPBlockListProvider.md b/exchange/exchange-ps/ExchangePowerShell/Remove-IPBlockListProvider.md
index d9de5066d9..b8322e65f5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-IPBlockListProvider.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-IPBlockListProvider.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailControl-Help.xml
 Locale: en-US
@@ -45,7 +45,7 @@ This example removes the IP Block list provider named Contoso.com.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the IP Block list provider that you want to remove. You can use any value that uniquely identifies the IP Block list provider. For example:
 
@@ -67,7 +67,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -88,7 +88,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -108,7 +108,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-InboxRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-InboxRule.md
index c4f3397c11..7045da5bf1 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-InboxRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-InboxRule.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -57,7 +57,7 @@ This example removes all Inbox rules from the mailbox Joe@Contoso.com.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the Inbox rule that you want to remove. You can use any value that uniquely identifies the rule. For example:
 
@@ -80,7 +80,7 @@ Accept wildcard characters: False
 
 ### -AlwaysDeleteOutlookRulesBlob
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AlwaysDeleteOutlookRulesBlob switch hides a warning message when you use Outlook on the web (formerly known as Outlook Web App) or Exchange PowerShell to modify Inbox rules. You don't need to specify a value with this switch.
 
@@ -98,7 +98,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -119,7 +119,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -139,7 +139,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -159,7 +159,7 @@ Accept wildcard characters: False
 
 ### -Mailbox
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Mailbox parameter specifies the mailbox that contains the Inbox rule. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -188,7 +188,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-IntraOrganizationConnector.md b/exchange/exchange-ps/ExchangePowerShell/Remove-IntraOrganizationConnector.md
index 426008cadc..c46d33b773 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-IntraOrganizationConnector.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-IntraOrganizationConnector.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
 Locale: en-US
@@ -49,7 +49,7 @@ This example removes the existing Intra-Organization connector named "Contoso On
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the Intra-Organization connector that you want to remove. You can use any value that uniquely identifies the connector. For example:
 
@@ -71,7 +71,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -92,7 +92,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -112,7 +112,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-JournalRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-JournalRule.md
index 58e379d9f0..c5c9c43c0b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-JournalRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-JournalRule.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailControl-Help.xml
 Locale: en-US
@@ -47,7 +47,7 @@ This example removes the journal rule Brokerage Communications that's no longer
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the rule you want to remove. Enter either name or the GUID of the journal rule. You can omit the parameter label.
 
@@ -65,7 +65,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -86,7 +86,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -106,7 +106,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-Mailbox.md b/exchange/exchange-ps/ExchangePowerShell/Remove-Mailbox.md
index 0765f501d9..a5ec1e6026 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-Mailbox.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-Mailbox.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -119,7 +119,7 @@ In Exchange Online, this example removes the specified soft-deleted mailbox.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter identifies the mailbox that you want to remove. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -150,7 +150,7 @@ Accept wildcard characters: False
 
 ### -Database
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -178,7 +178,7 @@ Accept wildcard characters: False
 
 ### -StoreMailboxIdentity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -202,7 +202,7 @@ Accept wildcard characters: False
 
 ### -Arbitration
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -226,7 +226,7 @@ Accept wildcard characters: False
 
 ### -AuditLog
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -250,7 +250,7 @@ Accept wildcard characters: False
 
 ### -AuxAuditLog
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -274,7 +274,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -295,7 +295,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -315,7 +315,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -335,7 +335,7 @@ Accept wildcard characters: False
 
 ### -IgnoreDefaultScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -360,7 +360,7 @@ Accept wildcard characters: False
 
 ### -IgnoreLegalHold
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -384,7 +384,7 @@ Accept wildcard characters: False
 
 ### -Migration
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Migration switch is required to remove migration mailboxes. You don't need to specify a value with this switch.
 
@@ -402,7 +402,7 @@ Accept wildcard characters: False
 
 ### -Permanent
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -450,7 +450,7 @@ Accept wildcard characters: False
 
 ### -PublicFolder
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The PublicFolder switch is required to remove public folder mailboxes. You don't need to specify a value with this switch.
 
@@ -470,7 +470,7 @@ Accept wildcard characters: False
 
 ### -RemoveArbitrationMailboxWithOABsAllowed
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -512,7 +512,7 @@ Accept wildcard characters: False
 
 ### -RemoveLastArbitrationMailboxAllowed
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -534,7 +534,7 @@ Accept wildcard characters: False
 
 ### -SupervisoryReviewPolicy
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -554,7 +554,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxDatabase.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxDatabase.md
index 25db72c47c..7170bc25ba 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxDatabase.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxDatabase.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -49,7 +49,7 @@ This example removes the mailbox database MailboxDatabase01.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the mailbox database that you want to remove. You can use any value that uniquely identifies the database. For example:
 
@@ -71,7 +71,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -92,7 +92,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -110,7 +110,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxDatabaseCopy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxDatabaseCopy.md
index 04f4669b42..50ce155e83 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxDatabaseCopy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxDatabaseCopy.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -54,7 +54,7 @@ This example removes a copy of mailbox database DB1 from the Mailbox server MBX3
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the name of the mailbox database whose copy is being removed. When using this parameter, specify a format of DatabaseName\\ServerName.
 
@@ -72,7 +72,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -93,7 +93,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -111,7 +111,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 

From 10b090b2152cb2099b0b44af7c1f2c0acc8273be Mon Sep 17 00:00:00 2001
From: Chris Davis <chris.davis@microsoft.com>
Date: Thu, 7 Aug 2025 14:26:35 -0700
Subject: [PATCH 133/145] Add Exchange Server SE 6

---
 .../ExchangePowerShell/Remove-MailContact.md  |  12 +-
 .../ExchangePowerShell/Remove-MailUser.md     |  14 +--
 .../Remove-MailboxExportRequest.md            |  16 +--
 .../Remove-MailboxFolderPermission.md         |  14 +--
 .../Remove-MailboxImportRequest.md            |  16 +--
 .../Remove-MailboxPermission.md               |  26 ++--
 .../Remove-MailboxRepairRequest.md            |  10 +-
 .../Remove-MailboxRestoreRequest.md           |  16 +--
 .../Remove-MailboxSearch.md                   |  10 +-
 .../Remove-MailboxUserConfiguration.md        |  12 +-
 .../Remove-MalwareFilterPolicy.md             |  12 +-
 .../Remove-MalwareFilterRule.md               |  10 +-
 .../Remove-ManagementRole.md                  |  14 +--
 .../Remove-ManagementRoleAssignment.md        |  10 +-
 .../Remove-ManagementRoleEntry.md             |  10 +-
 .../Remove-ManagementScope.md                 |  10 +-
 .../Remove-MapiVirtualDirectory.md            |  10 +-
 .../ExchangePowerShell/Remove-Message.md      |  14 +--
 .../Remove-MessageClassification.md           |  10 +-
 .../Remove-MigrationBatch.md                  |  12 +-
 .../Remove-MigrationEndpoint.md               |  10 +-
 .../Remove-MigrationUser.md                   |  12 +-
 .../ExchangePowerShell/Remove-MobileDevice.md |  10 +-
 .../Remove-MobileDeviceMailboxPolicy.md       |  12 +-
 .../ExchangePowerShell/Remove-MoveRequest.md  |  16 +--
 .../Remove-OabVirtualDirectory.md             |  12 +-
 .../Remove-OfflineAddressBook.md              |  12 +-
 .../Remove-OrganizationRelationship.md        |  10 +-
 .../Remove-OutlookProtectionRule.md           |  10 +-
 .../Remove-OutlookProvider.md                 |  10 +-
 .../Remove-OwaMailboxPolicy.md                |  12 +-
 .../Remove-OwaVirtualDirectory.md             |  10 +-
 .../Remove-PartnerApplication.md              |  10 +-
 .../Remove-PolicyTipConfig.md                 |  10 +-
 .../Remove-PowerShellVirtualDirectory.md      |  10 +-
 .../ExchangePowerShell/Remove-PublicFolder.md |  12 +-
 .../Remove-PublicFolderClientPermission.md    |  12 +-
 ...ove-PublicFolderMailboxMigrationRequest.md |  16 +--
 .../Remove-PublicFolderMigrationRequest.md    |  16 +--
 .../Remove-PublicFolderMoveRequest.md         |  16 +--
 .../Remove-ReceiveConnector.md                |  10 +-
 .../ExchangePowerShell/Remove-RemoteDomain.md |  10 +-
 .../Remove-RemoteMailbox.md                   |  14 +--
 .../Remove-ResubmitRequest.md                 |  10 +-
 .../Remove-RetentionPolicy.md                 |  12 +-
 .../Remove-RetentionPolicyTag.md              |  10 +-
 .../Remove-RoleAssignmentPolicy.md            |  10 +-
 .../ExchangePowerShell/Remove-RoleGroup.md    |  12 +-
 .../Remove-RoleGroupMember.md                 |  14 +--
 .../Remove-SearchDocumentFormat.md            |  10 +-
 .../Remove-SendConnector.md                   |  10 +-
 .../Remove-ServerMonitoringOverride.md        |  14 +--
 .../Remove-SettingOverride.md                 |  10 +-
 .../Remove-SharingPolicy.md                   |  10 +-
 .../Remove-SiteMailboxProvisioningPolicy.md   |  10 +-
 .../ExchangePowerShell/Remove-StoreMailbox.md |  12 +-
 .../ExchangePowerShell/Remove-SweepRule.md    |  12 +-
 .../Remove-SyncMailPublicFolder.md            |  10 +-
 .../Remove-SystemMessage.md                   |  10 +-
 .../Remove-ThrottlingPolicy.md                |  12 +-
 .../Remove-TransportRule.md                   |  10 +-
 .../ExchangePowerShell/Remove-UserPhoto.md    |  18 +--
 .../Remove-WebServicesVirtualDirectory.md     |  12 +-
 .../Remove-X400AuthoritativeDomain.md         |  10 +-
 .../Reset-ProvisioningCache.md                |  18 +--
 .../Restore-DatabaseAvailabilityGroup.md      |  18 +--
 .../Restore-DetailsTemplate.md                |  10 +-
 .../Restore-RecoverableItems.md               |  20 +--
 .../Resume-MailboxDatabaseCopy.md             |  16 +--
 .../Resume-MailboxExportRequest.md            |  10 +-
 .../Resume-MailboxImportRequest.md            |  10 +-
 .../Resume-MailboxRestoreRequest.md           |  10 +-
 .../ExchangePowerShell/Resume-Message.md      |  12 +-
 .../ExchangePowerShell/Resume-MoveRequest.md  |  12 +-
 .../Resume-PublicFolderMigrationRequest.md    |  10 +-
 .../Resume-PublicFolderMoveRequest.md         |  10 +-
 .../ExchangePowerShell/Resume-Queue.md        |  12 +-
 .../ExchangePowerShell/Retry-Queue.md         |  14 +--
 .../Search-AdminAuditLog.md                   |  24 ++--
 .../ExchangePowerShell/Search-Mailbox.md      |  34 ++---
 .../Search-MailboxAuditLog.md                 |  24 ++--
 .../Search-MessageTrackingReport.md           |  28 ++---
 .../Send-TextMessagingVerificationCode.md     |  10 +-
 .../Set-ADServerSettings.md                   |  20 +--
 .../ExchangePowerShell/Set-ADSite.md          |  16 +--
 .../ExchangePowerShell/Set-ADSiteLink.md      |  16 +--
 .../ExchangePowerShell/Set-AcceptedDomain.md  |  24 ++--
 .../Set-ActiveSyncDeviceAccessRule.md         |  12 +-
 .../Set-ActiveSyncDeviceAutoblockThreshold.md |  18 +--
 .../Set-ActiveSyncMailboxPolicy.md            | 116 +++++++++---------
 .../Set-ActiveSyncOrganizationSettings.md     |  22 ++--
 .../Set-ActiveSyncVirtualDirectory.md         |  56 ++++-----
 .../Set-AddressBookPolicy.md                  |  20 +--
 .../ExchangePowerShell/Set-AddressList.md     |  58 ++++-----
 .../Set-AddressRewriteEntry.md                |  20 +--
 .../Set-AdminAuditLogConfig.md                |  30 ++---
 .../exchange-ps/ExchangePowerShell/Set-App.md |  22 ++--
 .../Set-AttachmentFilterListConfig.md         |  16 +--
 98 files changed, 768 insertions(+), 768 deletions(-)

diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-MailContact.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MailContact.md
index 41677f24f9..83b6c22e1f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-MailContact.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MailContact.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -46,7 +46,7 @@ This example removes the mail contact named John.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the mail contact that you want to remove. You can use any value that uniquely identifies the mail contact. For example:
 
@@ -71,7 +71,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -92,7 +92,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -112,7 +112,7 @@ Accept wildcard characters: False
 
 ### -IgnoreDefaultScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -137,7 +137,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-MailUser.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MailUser.md
index 550a45c9ff..27bdf66632 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-MailUser.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MailUser.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -48,7 +48,7 @@ This example removes the mail user named Ed Meadows.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the mail user that you want to remove. You can use any value that uniquely identifies the mail user. For example:
 
@@ -73,7 +73,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -94,7 +94,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -114,7 +114,7 @@ Accept wildcard characters: False
 
 ### -IgnoreDefaultScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -139,7 +139,7 @@ Accept wildcard characters: False
 
 ### -IgnoreLegalHold
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -188,7 +188,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxExportRequest.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxExportRequest.md
index f4371e2ec3..672fbac9b9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxExportRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxExportRequest.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -78,7 +78,7 @@ This example cancels the export request by using the RequestGuid parameter for a
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the identity of the export request. By default, export requests are named `<alias>\MailboxExportX` (where X = 0-9). Use the following syntax: `Alias\Name`.
 
@@ -98,7 +98,7 @@ Accept wildcard characters: False
 
 ### -RequestGuid
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RequestGuid parameter specifies the unique identifier for the export request. To find the export request GUID, use the Get-MailboxExportRequest cmdlet. If you specify the RequestGuid parameter, you must also specify the RequestQueue parameter. You can't use this parameter with the Identity parameter.
 
@@ -116,7 +116,7 @@ Accept wildcard characters: False
 
 ### -RequestQueue
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RequestQueue parameter identifies the request based on the mailbox database where the request is being run. You can use any value that uniquely identifies the database. For example:
 
@@ -140,7 +140,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -161,7 +161,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -179,7 +179,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -199,7 +199,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxFolderPermission.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxFolderPermission.md
index fd615eb7b3..cf2be3023b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxFolderPermission.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxFolderPermission.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
 Locale: en-US
@@ -75,7 +75,7 @@ This example clears any corrupted delegate information from Kim's mailbox.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the target mailbox and folder. The syntax is `Mailbox:\Folder`. For the value of Mailbox, you can use any value that uniquely identifies the mailbox. For example:
 
@@ -106,7 +106,7 @@ Accept wildcard characters: False
 
 ### -User
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The User parameter specifies the mailbox, mail user, or mail-enabled security group (security principal) that's granted permission to the mailbox folder.
 
@@ -138,7 +138,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -159,7 +159,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -201,7 +201,7 @@ Accept wildcard characters: False
 
 ### -ResetDelegateUserCollection
 
-> Applicable: Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ResetDelegateUserCollection switch forces the removal of the LocalFreeBusy or the PR_FREEBUSY_ENTRYIDs files in case of corruption. You don't need to specify a value with this switch.
 
@@ -248,7 +248,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxImportRequest.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxImportRequest.md
index 4b0ccfcb1b..56619c7c57 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxImportRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxImportRequest.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -80,7 +80,7 @@ This example removes all completed import requests.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the identity of the import request. By default, import requests are named `<alias>\MailboxImportX` (where X = 0-9). If you created the request using the Name parameter, use the following syntax: `Alias\Name`.
 
@@ -100,7 +100,7 @@ Accept wildcard characters: False
 
 ### -RequestGuid
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -122,7 +122,7 @@ Accept wildcard characters: False
 
 ### -RequestQueue
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -148,7 +148,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -169,7 +169,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -189,7 +189,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -209,7 +209,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxPermission.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxPermission.md
index 49d7dc1c4e..adbba4c33c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxPermission.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxPermission.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -109,7 +109,7 @@ In Exchange Online, this example excludes the HR Project mailbox from auto-mappi
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the mailbox where you are removing permissions. You can use any value that uniquely identifies the mailbox: For example:
 
@@ -138,7 +138,7 @@ Accept wildcard characters: False
 
 ### -AccessRights
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AccessRights parameter specifies the permission that you want to remove from the user on the mailbox. Valid values are:
 
@@ -166,7 +166,7 @@ Accept wildcard characters: False
 
 ### -Instance
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -186,7 +186,7 @@ Accept wildcard characters: False
 
 ### -User
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The User parameter specifies whose permissions are being removed from the specified mailbox. You can specify the following types of users or groups (security principals) for this parameter:
 
@@ -226,7 +226,7 @@ Accept wildcard characters: False
 
 ### -ClearAutoMapping
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is functional only in the cloud-based service.
 
@@ -252,7 +252,7 @@ Accept wildcard characters: False
 
 ### -ResetDefault
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is functional only in the cloud-based service.
 
@@ -304,7 +304,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -325,7 +325,7 @@ Accept wildcard characters: False
 
 ### -Deny
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Deny switch specifies that the permissions you're removing are Deny permissions. You don't need to specify a value with this switch.
 
@@ -343,7 +343,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -383,7 +383,7 @@ Accept wildcard characters: False
 
 ### -IgnoreDefaultScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange PowerShell session, and to use the entire forest as the scope. You don't need to specify a value with this switch.
 
@@ -406,7 +406,7 @@ Accept wildcard characters: False
 
 ### -InheritanceType
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The InheritanceType parameter specifies whether permissions are inherited to folders within the mailbox. Valid values are:
 
@@ -452,7 +452,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxRepairRequest.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxRepairRequest.md
index 0f77f23c1c..59a4597166 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxRepairRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxRepairRequest.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -65,7 +65,7 @@ This example deletes a specific mailbox repair request by specifying the unique
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the mailbox repair request to remove. Mailbox repair requests are identified by a complex GUID that is created when a new mailbox repair request is created. This GUID consists of a database ID, a Request ID and a job ID. The format is `DatabaseGuid\RequestGuid\JobGuid`. Use the Get-MailboxRepairRequest cmdlet to find the identity of a mailbox repair request.
 
@@ -83,7 +83,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -104,7 +104,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -122,7 +122,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxRestoreRequest.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxRestoreRequest.md
index 3b1bd245ff..df18d3ae1e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxRestoreRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxRestoreRequest.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -74,7 +74,7 @@ This example cancels the restore request by using the RequestGuid parameter for
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the identity of the restore request. The Identity parameter consists of the alias of the mailbox to be restored and the name that was specified when the restore request was created. The identity of the restore request uses the following syntax: `Alias\Name`.
 
@@ -94,7 +94,7 @@ Accept wildcard characters: False
 
 ### -RequestGuid
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -116,7 +116,7 @@ Accept wildcard characters: False
 
 ### -RequestQueue
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -142,7 +142,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -163,7 +163,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -183,7 +183,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -203,7 +203,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxSearch.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxSearch.md
index 90b6f263d9..74941b143a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxSearch.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxSearch.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
 Locale: en-US
@@ -49,7 +49,7 @@ This example removes the mailbox search Project Contoso.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the name of the mailbox search.
 
@@ -67,7 +67,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -88,7 +88,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -108,7 +108,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxUserConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxUserConfiguration.md
index df48043dd3..96c9e86507 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxUserConfiguration.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MailboxUserConfiguration.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -45,7 +45,7 @@ This example removes the specified user configuration item from the mailbox juli
 
 ### -Identity
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the user configuration item that you want to remove. This parameter uses the syntax MailboxFolder\ItemName:
 
@@ -66,7 +66,7 @@ Accept wildcard characters: False
 
 ### -Mailbox
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Mailbox parameter specifies the mailbox that contains the user configuration items you want to remove. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -95,7 +95,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -116,7 +116,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -136,7 +136,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-MalwareFilterPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MalwareFilterPolicy.md
index c839114494..cde2352cac 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-MalwareFilterPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MalwareFilterPolicy.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -48,7 +48,7 @@ This example removes the malware filter policy named Contoso Malware Filter Poli
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the malware filter policy you want to remove. You can use any value that uniquely identifies the policy. For example, you can use the name, GUID or distinguished name (DN) of the malware filter policy.
 
@@ -66,7 +66,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -87,7 +87,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -107,7 +107,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -129,7 +129,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-MalwareFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MalwareFilterRule.md
index eea5a20e1b..c04a2ceb8f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-MalwareFilterRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MalwareFilterRule.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -45,7 +45,7 @@ This example removes the malware filter rule named Contoso Recipients.
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the malware filter rule that you want to remove. You can use any value that uniquely identifies the rule. For example, you can use the name, GUID or distinguished name (DN) of the malware filter rule.
 
@@ -63,7 +63,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -84,7 +84,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -104,7 +104,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ManagementRole.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ManagementRole.md
index 39277631d6..7c272978a2 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-ManagementRole.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ManagementRole.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -75,7 +75,7 @@ For more information about unscoped top-level management roles, see [Understandi
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the custom role to remove. If the name of the role contains spaces, enclose the name in quotation marks (").
 
@@ -93,7 +93,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -114,7 +114,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -156,7 +156,7 @@ Accept wildcard characters: False
 
 ### -Recurse
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Recurse switch removes the specified role and all child roles of the specified role. You don't need to specify a value with this switch.
 
@@ -176,7 +176,7 @@ Accept wildcard characters: False
 
 ### -UnScopedTopLevel
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -200,7 +200,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ManagementRoleAssignment.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ManagementRoleAssignment.md
index 4a4e87c6c9..e26f54ba29 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-ManagementRoleAssignment.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ManagementRoleAssignment.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -57,7 +57,7 @@ After the list of role assignments to be removed is confirmed, remove the WhatIf
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the name of the role assignment to remove. If the role assignment name contains spaces, enclose the name in quotation marks (").
 
@@ -75,7 +75,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -96,7 +96,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -138,7 +138,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ManagementRoleEntry.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ManagementRoleEntry.md
index def11dc9d1..7e6c993a43 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-ManagementRoleEntry.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ManagementRoleEntry.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -61,7 +61,7 @@ This example forces you to acknowledge the command before proceeding (we didn't
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the role entry that you want to remove. This parameter uses the syntax: `<management role>\<role entry name>` (for example, `CustomRole\Set-Mailbox`).
 
@@ -83,7 +83,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -104,7 +104,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -146,7 +146,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ManagementScope.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ManagementScope.md
index d21c285668..cbd3a39ac5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-ManagementScope.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ManagementScope.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -57,7 +57,7 @@ After you verify that the scopes to be removed are correct, run the command agai
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the scope to remove. You can't remove a scope if it's in use by a management role assignment.
 
@@ -75,7 +75,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -96,7 +96,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -138,7 +138,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-MapiVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MapiVirtualDirectory.md
index b5634346e1..89601355c0 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-MapiVirtualDirectory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MapiVirtualDirectory.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -45,7 +45,7 @@ This example removes the MAPI virtual directory from the local server named Cont
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the MAPI virtual directory that you want to remove. You can use any value that uniquely identifies the virtual directory. For example:
 
@@ -69,7 +69,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -90,7 +90,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -108,7 +108,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-Message.md b/exchange/exchange-ps/ExchangePowerShell/Remove-Message.md
index 462f8cf196..30235da2fe 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-Message.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-Message.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -60,7 +60,7 @@ This example removes all messages that meet the following criteria without gener
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the message. Valid input for this parameter uses the syntax Server\\Queue\\MessageInteger or Queue\\MessageInteger or MessageInteger, for example, Mailbox01\\contoso.com\\5 or 10. For details about message identity, see [Message identity](https://learn.microsoft.com/Exchange/mail-flow/queues/queues-and-messages-in-powershell#message-identity).
 
@@ -78,7 +78,7 @@ Accept wildcard characters: False
 
 ### -Filter
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Filter parameter specifies one or more messages by using OPATH filter syntax. The OPATH filter includes a message property name followed by a comparison operator and value (for example, `"FromAddress -like '*@contoso.com'"`). For details about filterable message properties and comparison operators, see [Properties of messages in queues](https://learn.microsoft.com/Exchange/mail-flow/queues/message-properties) and [Find queues and messages in queues in the Exchange Management Shell](https://learn.microsoft.com/Exchange/mail-flow/queues/queues-and-messages-in-powershell).
 
@@ -98,7 +98,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -119,7 +119,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
 
@@ -146,7 +146,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
@@ -164,7 +164,7 @@ Accept wildcard characters: False
 
 ### -WithNDR
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WithNDR parameter specifies whether a non-delivery report (NDR) is returned to the sender of a message. The default value is $true. This parameter can be used with both the Identity parameter and Filter parameter sets.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-MessageClassification.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MessageClassification.md
index 3ad8456773..02a6b28f61 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-MessageClassification.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MessageClassification.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -45,7 +45,7 @@ This example removes the message classification named "My Message Classification
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the message classification that you want to remove. You can use any value that uniquely identifies the message classification. For example:
 
@@ -67,7 +67,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -88,7 +88,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -110,7 +110,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-MigrationBatch.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MigrationBatch.md
index 621ad34cae..5a7633aaa7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-MigrationBatch.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MigrationBatch.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -58,7 +58,7 @@ This example removes the corrupted migration batch LocalMove1.
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter identifies the migration batch that you want to remove. The value for this parameter is the name that was specified when the migration batch was created.
 
@@ -76,7 +76,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -97,7 +97,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -117,7 +117,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -161,7 +161,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-MigrationEndpoint.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MigrationEndpoint.md
index b550b89413..2de85027b8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-MigrationEndpoint.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MigrationEndpoint.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -50,7 +50,7 @@ This example removes the migration endpoint CrossForestME01.
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the name of the migration endpoint you want to remove.
 
@@ -68,7 +68,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -89,7 +89,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -129,7 +129,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-MigrationUser.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MigrationUser.md
index 21265c4d48..38fe6a43eb 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-MigrationUser.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MigrationUser.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -47,7 +47,7 @@ This example removes the migration user Tony Smith from a migration batch.
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the user that you want to remove from the migration batch.
 
@@ -65,7 +65,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -86,7 +86,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -106,7 +106,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -148,7 +148,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-MobileDevice.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MobileDevice.md
index d47d20a69c..f4d11ef44f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-MobileDevice.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MobileDevice.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
 Locale: en-US
@@ -54,7 +54,7 @@ This example removes the mobile device partnership for the specified device and
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the mobile device partnership that you want to remove. You can use the following values that uniquely identifies the mobile device:
 
@@ -76,7 +76,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -97,7 +97,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -117,7 +117,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-MobileDeviceMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MobileDeviceMailboxPolicy.md
index 978c5c882f..c238b63ed8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-MobileDeviceMailboxPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MobileDeviceMailboxPolicy.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
 Locale: en-US
@@ -62,7 +62,7 @@ This example removes the mobile device mailbox policy named Management and bypas
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the mobile device mailbox policy that you want to remove. You can use any value that uniquely identifies the policy. For example:
 
@@ -84,7 +84,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -105,7 +105,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -125,7 +125,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -145,7 +145,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-MoveRequest.md b/exchange/exchange-ps/ExchangePowerShell/Remove-MoveRequest.md
index 3c1e58353f..b414be957f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-MoveRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-MoveRequest.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -73,7 +73,7 @@ The MailboxGuid and MoveRequestQueue parameters are for debugging purposes only.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the identity of the mailbox or mail user. You can use the following values:
 
@@ -101,7 +101,7 @@ Accept wildcard characters: False
 
 ### -MailboxGuid
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -123,7 +123,7 @@ Accept wildcard characters: False
 
 ### -MoveRequestQueue
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -149,7 +149,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -170,7 +170,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -190,7 +190,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -241,7 +241,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-OabVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Remove-OabVirtualDirectory.md
index ce326f3292..3b6d435a81 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-OabVirtualDirectory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-OabVirtualDirectory.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -55,7 +55,7 @@ This example removes the default OAB virtual directory from Server1.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the OAB virtual directory that you want to remove. You can use any value that uniquely identifies the virtual directory. For example:
 
@@ -79,7 +79,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -100,7 +100,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -118,7 +118,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -138,7 +138,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-OfflineAddressBook.md b/exchange/exchange-ps/ExchangePowerShell/Remove-OfflineAddressBook.md
index 7d7ab5b347..a4eadbf4de 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-OfflineAddressBook.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-OfflineAddressBook.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -50,7 +50,7 @@ This example removes the OAB named Contoso Executives.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the OAB that you want to remove. You can use any value that uniquely identifies the OAB. For example:
 
@@ -72,7 +72,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -93,7 +93,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -113,7 +113,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -133,7 +133,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-OrganizationRelationship.md b/exchange/exchange-ps/ExchangePowerShell/Remove-OrganizationRelationship.md
index e1a750ebb3..f60fdee79e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-OrganizationRelationship.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-OrganizationRelationship.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
 Locale: en-US
@@ -47,7 +47,7 @@ This example removes the organization relationship Contoso using the Identity pa
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the identity of the organization relationship that you want to remove. You can use one of the following values:
 
@@ -69,7 +69,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -90,7 +90,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -110,7 +110,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-OutlookProtectionRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-OutlookProtectionRule.md
index 9c740ebb31..bb92d3a648 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-OutlookProtectionRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-OutlookProtectionRule.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -56,7 +56,7 @@ This example removes all Outlook protection rules from the organization.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the name of the Outlook protection rule that you want to remove.
 
@@ -74,7 +74,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -95,7 +95,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -115,7 +115,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-OutlookProvider.md b/exchange/exchange-ps/ExchangePowerShell/Remove-OutlookProvider.md
index 963f8c71d9..7b4a6ee9a5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-OutlookProvider.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-OutlookProvider.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -47,7 +47,7 @@ This example deletes the AutoDiscoverConfig object named Test Object from Active
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the AutoDiscoverConfig object to remove from Active Directory.
 
@@ -65,7 +65,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -86,7 +86,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -104,7 +104,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-OwaMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-OwaMailboxPolicy.md
index 5b620c8bb2..af5b2cd99a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-OwaMailboxPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-OwaMailboxPolicy.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.WebClient-Help.xml
 Locale: en-US
@@ -62,7 +62,7 @@ This example removes the mailbox policy named Corporate for the tenant Contoso i
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the mailbox policy that you want to remove. You can use any value that uniquely identifies the policy. For example:
 
@@ -84,7 +84,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -105,7 +105,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -125,7 +125,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -145,7 +145,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-OwaVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Remove-OwaVirtualDirectory.md
index a124400754..d89f980954 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-OwaVirtualDirectory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-OwaVirtualDirectory.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.WebClient-Help.xml
 Locale: en-US
@@ -52,7 +52,7 @@ This example removes the specified Outlook on the web virtual directory from the
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the OWA virtual directory that you want to remove. You can use any value that uniquely identifies the virtual directory. For example:
 
@@ -76,7 +76,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -97,7 +97,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -115,7 +115,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-PartnerApplication.md b/exchange/exchange-ps/ExchangePowerShell/Remove-PartnerApplication.md
index 936b9caaf0..edeb804c3f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-PartnerApplication.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-PartnerApplication.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -49,7 +49,7 @@ This command removes the HRApp partner application.
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the identity of the partner application.
 
@@ -67,7 +67,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -88,7 +88,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -108,7 +108,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-PolicyTipConfig.md b/exchange/exchange-ps/ExchangePowerShell/Remove-PolicyTipConfig.md
index d20d920506..7c5b735090 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-PolicyTipConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-PolicyTipConfig.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -52,7 +52,7 @@ This example removes all the custom Russian Policy Tips.
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the custom Policy Tip you want to remove. You can use any value that uniquely identifies the custom Policy Tip. For example:
 
@@ -75,7 +75,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -96,7 +96,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -116,7 +116,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-PowerShellVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Remove-PowerShellVirtualDirectory.md
index 72abe8d4c1..de97083644 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-PowerShellVirtualDirectory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-PowerShellVirtualDirectory.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -49,7 +49,7 @@ Be careful when using the Remove-PowerShellVirtualDirectory cmdlet without confi
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the PowerShell virtual directory that you want to remove. You can use any value that uniquely identifies the virtual directory. For example:
 
@@ -73,7 +73,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -94,7 +94,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -112,7 +112,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolder.md b/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolder.md
index d3d0cdf444..8dfac0ab45 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolder.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolder.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.WebClient-Help.xml
 Locale: en-US
@@ -57,7 +57,7 @@ This example deletes the public folder Directory Folder and all its child public
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the name and path of the public folder you want to remove. A valid value uses the syntax: `\Level1\Level2\...\LevenN\PublicFolder`. For example, `"\Customer Discussion"` or `"\Engineering\Customer Discussion"`.
 
@@ -75,7 +75,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -96,7 +96,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -136,7 +136,7 @@ Accept wildcard characters: False
 
 ### -Recurse
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Recurse switch specifies whether all subfolders of the specified folder should also be removed. You don't need to specify a value with this switch.
 
@@ -183,7 +183,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderClientPermission.md b/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderClientPermission.md
index 4d3cc811a7..96e7dc9d38 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderClientPermission.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderClientPermission.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.WebClient-Help.xml
 Locale: en-US
@@ -53,7 +53,7 @@ This example removes permission for the user Chris to the public folder My Publi
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the GUID or public folder name that represents a specific public folder. You can also include the path by using the format \\TopLevelPublicFolder\\PublicFolder.
 
@@ -120,7 +120,7 @@ Accept wildcard characters: False
 
 ### -User
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The User parameter specifies the user whose permissions are being removed.
 
@@ -143,7 +143,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -164,7 +164,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -211,7 +211,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderMailboxMigrationRequest.md b/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderMailboxMigrationRequest.md
index 0667881178..df99edf198 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderMailboxMigrationRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderMailboxMigrationRequest.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -70,7 +70,7 @@ This example returns duplicate public folder migration requests (requests create
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the public folder mailbox migration request that you want to remove. This value uses the syntax `\PublicFolderMailboxMigration<GUID>` (for example, `\PublicFolderMailboxMigrationac6d9eb4-ee49-405f-b90d-04e9a258bd7e`).
 
@@ -90,7 +90,7 @@ Accept wildcard characters: False
 
 ### -RequestGuid
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -112,7 +112,7 @@ Accept wildcard characters: False
 
 ### -RequestQueue
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -138,7 +138,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -159,7 +159,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is functional only in on-premises Exchange.
 
@@ -179,7 +179,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -199,7 +199,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderMigrationRequest.md b/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderMigrationRequest.md
index 8d030b34ca..374dd15017 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderMigrationRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderMigrationRequest.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -69,7 +69,7 @@ The RequestGuid and RequestQueue parameters are for debugging purposes only.
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the migration request that you want to remove. You can use the following values:
 
@@ -92,7 +92,7 @@ Accept wildcard characters: False
 
 ### -RequestGuid
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RequestGuid parameter identifies the migration request to remove by its RequestGUID value. This parameter also requires the RequestQueue parameter.
 
@@ -112,7 +112,7 @@ Accept wildcard characters: False
 
 ### -RequestQueue
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RequestQueue parameter identifies the migration request by the mailbox database where the request is being run. You can use any value that uniquely identifies the database. For example:
 
@@ -138,7 +138,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -159,7 +159,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -177,7 +177,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -197,7 +197,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderMoveRequest.md b/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderMoveRequest.md
index 26486f972c..8627acb82c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderMoveRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-PublicFolderMoveRequest.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -67,7 +67,7 @@ The RequestGuid and RequestQueue parameters are for debugging purposes only.
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the identity of the public folder move request. The default identity is \\PublicFolderMove.
 
@@ -87,7 +87,7 @@ Accept wildcard characters: False
 
 ### -RequestGuid
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RequestGuid parameter specifies the GUID of the public folder move request. If you specify the RequestGuid parameter, you must also specify the RequestQueue parameter.
 
@@ -107,7 +107,7 @@ Accept wildcard characters: False
 
 ### -RequestQueue
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RequestQueue parameter identifies the request based on the mailbox database where the request is being run. You can use any value that uniquely identifies the database. For example:
 
@@ -131,7 +131,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -152,7 +152,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is functional only in on-premises Exchange.
 
@@ -172,7 +172,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -192,7 +192,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ReceiveConnector.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ReceiveConnector.md
index f8720a5197..75dbe3dc79 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-ReceiveConnector.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ReceiveConnector.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -47,7 +47,7 @@ This example removes the Receive connector named Contoso.com Receive Connector.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the Receive connector that you want to remove. You can use any value that uniquely identifies the Receive connector. For example:
 
@@ -70,7 +70,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -91,7 +91,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -111,7 +111,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-RemoteDomain.md b/exchange/exchange-ps/ExchangePowerShell/Remove-RemoteDomain.md
index a4d1dfe0c2..66d775fc09 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-RemoteDomain.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-RemoteDomain.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -45,7 +45,7 @@ This example removes the remote domain object named Contoso.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the remote domain that you want to remove. You can use any value that uniquely identifies the remote domain. For example:
 
@@ -67,7 +67,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -88,7 +88,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -110,7 +110,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-RemoteMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Remove-RemoteMailbox.md
index fd6ab9e40a..ff92a0cad0 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-RemoteMailbox.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-RemoteMailbox.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -51,7 +51,7 @@ This example removes the on-premises mail-enabled user Kim Akers and the associa
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter identifies the mail-enabled user and the associated mailbox in the service that you want to remove. You can use one of the following values:
 
@@ -78,7 +78,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -99,7 +99,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -117,7 +117,7 @@ Accept wildcard characters: False
 
 ### -IgnoreDefaultScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange PowerShell session, and to use the entire forest as the scope. You don't need to specify a value with this switch.
 
@@ -140,7 +140,7 @@ Accept wildcard characters: False
 
 ### -IgnoreLegalHold
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IgnoreLegalHold switch ignores the legal hold status of the remote user. You don't need to specify a value with this switch.
 
@@ -160,7 +160,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ResubmitRequest.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ResubmitRequest.md
index c85c142160..4ece31ad16 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-ResubmitRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ResubmitRequest.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -52,7 +52,7 @@ This example removes all resubmit requests.
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the resubmit request you want to remove. Each resubmit request is identified by an incremented integer value.
 
@@ -70,7 +70,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -91,7 +91,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
 
@@ -116,7 +116,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-RetentionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-RetentionPolicy.md
index 0475a58a8f..010d3880a8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-RetentionPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-RetentionPolicy.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
 Locale: en-US
@@ -64,7 +64,7 @@ This example removes the retention policy Business Critical, which is assigned t
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the retention policy name.
 
@@ -82,7 +82,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -103,7 +103,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -123,7 +123,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -143,7 +143,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-RetentionPolicyTag.md b/exchange/exchange-ps/ExchangePowerShell/Remove-RetentionPolicyTag.md
index d8d0bfdde8..fc50717840 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-RetentionPolicyTag.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-RetentionPolicyTag.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
 Locale: en-US
@@ -51,7 +51,7 @@ This example removes the retention tag Finance-DeletedItems.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the name of the retention policy tag.
 
@@ -69,7 +69,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -90,7 +90,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -110,7 +110,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-RoleAssignmentPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-RoleAssignmentPolicy.md
index 5b564b0d0d..ee27eb7529 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-RoleAssignmentPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-RoleAssignmentPolicy.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -69,7 +69,7 @@ For more information about the Where cmdlet and pipelining, see [Working with co
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the assignment policy to remove. If the assignment policy name has spaces, enclose the name in quotation marks (").
 
@@ -87,7 +87,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -108,7 +108,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -130,7 +130,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-RoleGroup.md b/exchange/exchange-ps/ExchangePowerShell/Remove-RoleGroup.md
index 8823aa5d8b..e70371f1c6 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-RoleGroup.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-RoleGroup.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -62,7 +62,7 @@ This example removes the Vancouver Recipient Administrators role group. Because
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The Identity parameter specifies the role group to remove. If the role group name contains spaces, enclose the name in quotation marks (").
 
@@ -80,7 +80,7 @@ Accept wildcard characters: False
 
 ### -BypassSecurityGroupManagerCheck
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The BypassSecurityGroupManagerCheck switch specifies whether to allow a user who isn't an owner of the group to modify or delete the group. You don't need to specify a value with this switch.
 
@@ -103,7 +103,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -124,7 +124,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -166,7 +166,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The WhatIf switch doesn't work in Security & Compliance PowerShell.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-RoleGroupMember.md b/exchange/exchange-ps/ExchangePowerShell/Remove-RoleGroupMember.md
index a7c39c03c7..b6fcbbf46e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-RoleGroupMember.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-RoleGroupMember.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -75,7 +75,7 @@ This example removes the Training Assistants USG from the Training Administrator
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The Identity parameter specifies the role group that you want to remove a member from. If the role group name contains spaces, enclose the name in quotation marks (").
 
@@ -93,7 +93,7 @@ Accept wildcard characters: False
 
 ### -Member
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The Member parameter specifies who to remove from the role group. You can specify the following types of users or groups (security principals) for this parameter:
 
@@ -129,7 +129,7 @@ Accept wildcard characters: False
 
 ### -BypassSecurityGroupManagerCheck
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The BypassSecurityGroupManagerCheck switch specifies whether to allow a user who isn't an owner of the group to modify or delete the group. You don't need to specify a value with this switch.
 
@@ -152,7 +152,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -173,7 +173,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -193,7 +193,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The WhatIf switch doesn't work in Security & Compliance PowerShell.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-SearchDocumentFormat.md b/exchange/exchange-ps/ExchangePowerShell/Remove-SearchDocumentFormat.md
index f0db065269..734253fba9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-SearchDocumentFormat.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-SearchDocumentFormat.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -49,7 +49,7 @@ This example removes the search document format with an identity equal to "sct".
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter uniquely identifies the format to be removed. You can use the Get-SearchDocumentFormat cmdlet to view the identities of the installed formats.
 
@@ -67,7 +67,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -88,7 +88,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
 
@@ -113,7 +113,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-SendConnector.md b/exchange/exchange-ps/ExchangePowerShell/Remove-SendConnector.md
index 731a453bec..e76cacedf7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-SendConnector.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-SendConnector.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -49,7 +49,7 @@ This example deletes the Send connector named Contoso.com Send Connector.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the name, or GUID of the Send connector. If the Identity name contains spaces, enclose the name in quotation marks ("). You can omit the Identity parameter label. You can also include the server name by using the format ServerName\\ConnectorName.
 
@@ -67,7 +67,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -88,7 +88,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -108,7 +108,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ServerMonitoringOverride.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ServerMonitoringOverride.md
index d4d2e18a65..2df2f375d2 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-ServerMonitoringOverride.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ServerMonitoringOverride.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -51,7 +51,7 @@ This example removes a server monitoring override of the ExtensionAttributes pro
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the monitoring item that was overridden. The value is in the form of HealthSet\\MonitoringItem or HealthSet\\MonitoringItem\\TargetResource.
 
@@ -69,7 +69,7 @@ Accept wildcard characters: False
 
 ### -ItemType
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ItemType parameter specifies the item type of the override that you want to remove. It can be any of the following values:
 
@@ -91,7 +91,7 @@ Accept wildcard characters: False
 
 ### -PropertyName
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PropertyName parameter specifies the property for the override you want to remove.
 
@@ -109,7 +109,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Exchange server that contains the override that you want to remove. You can use any value that uniquely identifies the server. For example:
 
@@ -132,7 +132,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -153,7 +153,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-SettingOverride.md b/exchange/exchange-ps/ExchangePowerShell/Remove-SettingOverride.md
index be10212190..3553943047 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-SettingOverride.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-SettingOverride.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -49,7 +49,7 @@ This example removes the setting override named IM Server Integration.
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the setting override that you want to remove. You can use any value that uniquely identifies the override. For example:
 
@@ -71,7 +71,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -92,7 +92,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -110,7 +110,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-SharingPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-SharingPolicy.md
index 719d9621a8..df9b839429 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-SharingPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-SharingPolicy.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
 Locale: en-US
@@ -52,7 +52,7 @@ This example removes the sharing policy Contoso and suppresses the confirmation
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the identity of the sharing policy that you want to remove. You can use one of the following values:
 
@@ -75,7 +75,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -96,7 +96,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -116,7 +116,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-SiteMailboxProvisioningPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-SiteMailboxProvisioningPolicy.md
index 78406d422b..8ce50bb76a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-SiteMailboxProvisioningPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-SiteMailboxProvisioningPolicy.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.WebClient-Help.xml
 Locale: en-US
@@ -49,7 +49,7 @@ This example deletes the site mailbox policy named Default that was created when
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the site mailbox provisioning policy that you want to remove. You can use any value that uniquely identifies the policy. For example:
 
@@ -71,7 +71,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -92,7 +92,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -110,7 +110,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-StoreMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Remove-StoreMailbox.md
index 7f22253212..0b0ae0b641 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-StoreMailbox.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-StoreMailbox.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -66,7 +66,7 @@ This example permanently purges all soft-deleted mailboxes from mailbox database
 
 ### -Database
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Database parameter specifies the mailbox database that contains the mailbox to remove. You can use any value that uniquely identifies the database. For example:
 
@@ -88,7 +88,7 @@ Accept wildcard characters: False
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the identity of the mailbox that you want to remove. Use the mailbox GUID as the value for this parameter.
 
@@ -108,7 +108,7 @@ Accept wildcard characters: False
 
 ### -MailboxState
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MailboxState parameter specifies the mailbox state on the source mailbox database. This parameter accepts the following values:
 
@@ -129,7 +129,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -150,7 +150,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-SweepRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-SweepRule.md
index 3815b75020..59f9f6fb22 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-SweepRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-SweepRule.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -53,7 +53,7 @@ This example removes all Sweep rules in the specified mailbox.
 
 ### -Identity
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the Sweep rule that you want to remove. You can use any value that uniquely identifies the rule. For example:
 
@@ -75,7 +75,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -96,7 +96,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -116,7 +116,7 @@ Accept wildcard characters: False
 
 ### -Mailbox
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Mailbox parameter specifies the mailbox that contains the rule you want to remove. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -145,7 +145,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-SyncMailPublicFolder.md b/exchange/exchange-ps/ExchangePowerShell/Remove-SyncMailPublicFolder.md
index 5b7c3b265b..820d10e781 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-SyncMailPublicFolder.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-SyncMailPublicFolder.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.WebClient-Help.xml
 Locale: en-US
@@ -47,7 +47,7 @@ This cmdlet is only used by the Sync-MailPublicFolders.ps1 script. Don't run thi
 
 ### -Identity
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the mail-enabled public folder object that you want to remove from Exchange Online. For example:
 
@@ -70,7 +70,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -91,7 +91,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -111,7 +111,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-SystemMessage.md b/exchange/exchange-ps/ExchangePowerShell/Remove-SystemMessage.md
index 159bf7e9fa..1213f6465d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-SystemMessage.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-SystemMessage.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -54,7 +54,7 @@ This example removes the specified custom quota message (combination of language
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the custom system message that you want to remove. You can use any value that uniquely identifies the system message. For example:
 
@@ -121,7 +121,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -142,7 +142,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -162,7 +162,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ThrottlingPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ThrottlingPolicy.md
index 34b4dbf066..094ae1ab94 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-ThrottlingPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ThrottlingPolicy.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.WebClient-Help.xml
 Locale: en-US
@@ -65,7 +65,7 @@ You can't remove a policy that's associated with any users. This example reassig
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter identifies the throttling policy you want to remove. Use the name that matches the name of the policy in Active Directory.
 
@@ -83,7 +83,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -104,7 +104,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -124,7 +124,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -144,7 +144,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-TransportRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-TransportRule.md
index 6efbe05339..91eb6434d2 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-TransportRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-TransportRule.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -49,7 +49,7 @@ This example removes the rule named "Redirect messages from kim@contoso.com to l
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the rule that you want to remove. You can use any value that uniquely identifies the rule. For example:
 
@@ -71,7 +71,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -92,7 +92,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -114,7 +114,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-UserPhoto.md b/exchange/exchange-ps/ExchangePowerShell/Remove-UserPhoto.md
index 7fdc01f89c..28cf153f71 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-UserPhoto.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-UserPhoto.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -67,7 +67,7 @@ This example deletes the photo associated with Ann Beebe's user account.
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the identity of the user. You can use any value that uniquely identifies the user. For example:
 
@@ -96,7 +96,7 @@ Accept wildcard characters: False
 
 ### -ClearMailboxPhotoRecord
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ClearMailboxPhoto switch specifies that a deleted mailbox photo is considered blank instead of deleted. You don't need to specify a value with this switch.
 
@@ -121,7 +121,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -142,7 +142,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -160,7 +160,7 @@ Accept wildcard characters: False
 
 ### -GroupMailbox
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The GroupMailbox switch is required to modify Microsoft 365 Groups. You don't need to specify a value with this switch.
 
@@ -178,7 +178,7 @@ Accept wildcard characters: False
 
 ### -IgnoreDefaultScope
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange PowerShell session, and to use the entire forest as the scope. You don't need to specify a value with this switch.
 
@@ -201,7 +201,7 @@ Accept wildcard characters: False
 
 ### -PhotoType
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -219,7 +219,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-WebServicesVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Remove-WebServicesVirtualDirectory.md
index 146c97aa5f..d095b5cdae 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-WebServicesVirtualDirectory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-WebServicesVirtualDirectory.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -48,7 +48,7 @@ This example removes the Exchange Web Services virtual directory named Sales fro
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the EWS virtual directory that you want to remove. You can use any value that uniquely identifies the virtual directory. For example:
 
@@ -72,7 +72,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -93,7 +93,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -111,7 +111,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -131,7 +131,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-X400AuthoritativeDomain.md b/exchange/exchange-ps/ExchangePowerShell/Remove-X400AuthoritativeDomain.md
index d15a9671e2..37a5815f57 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Remove-X400AuthoritativeDomain.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Remove-X400AuthoritativeDomain.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -45,7 +45,7 @@ This example removes the X.400 authoritative domain object for the X.400 authori
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies a string value for the X.400 authoritative domain. Enter either the GUID or the name of the X.400 authoritative domain.
 
@@ -63,7 +63,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -84,7 +84,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -104,7 +104,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Reset-ProvisioningCache.md b/exchange/exchange-ps/ExchangePowerShell/Reset-ProvisioningCache.md
index 304b16a5f9..810db51c98 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Reset-ProvisioningCache.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Reset-ProvisioningCache.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -69,7 +69,7 @@ This example runs in a multi-tenant deployment by a data center administrator to
 
 ### -Server
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the fully qualified domain name (FQDN) of the server that the application you want to reset is running on.
 
@@ -87,7 +87,7 @@ Accept wildcard characters: False
 
 ### -Application
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Application parameter specifies the specific administrative application to reset the provisioning cache for. You can use the following values:
 
@@ -112,7 +112,7 @@ Accept wildcard characters: False
 
 ### -GlobalCache
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The GlobalCache switch clears all cache keys. You don't need to specify a value with this switch.
 
@@ -130,7 +130,7 @@ Accept wildcard characters: False
 
 ### -CacheKeys
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The CacheKeys parameter specifies the value for the cache key that you want to clear. The format for the values should contain 32 digits separated by four dashes: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
 
@@ -150,7 +150,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -171,7 +171,7 @@ Accept wildcard characters: False
 
 ### -CurrentOrganization
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The CurrentOrganization switch resets the provision cache for the organization. You don't need to specify a value with this switch.
 
@@ -189,7 +189,7 @@ Accept wildcard characters: False
 
 ### -Organizations
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Organizations parameter specifies the organizations where the provisioning cache is reset. Use this parameter in multi-tenant deployments.
 
@@ -207,7 +207,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Restore-DatabaseAvailabilityGroup.md b/exchange/exchange-ps/ExchangePowerShell/Restore-DatabaseAvailabilityGroup.md
index d57df551a4..05ca97870d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Restore-DatabaseAvailabilityGroup.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Restore-DatabaseAvailabilityGroup.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -67,7 +67,7 @@ This example activates member servers in the DAG DAG1 for the Active Directory s
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the name of the DAG being manipulated.
 
@@ -85,7 +85,7 @@ Accept wildcard characters: False
 
 ### -ActiveDirectorySite
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ActiveDirectorySite parameter specifies the site containing the DAG members to be restored.
 
@@ -103,7 +103,7 @@ Accept wildcard characters: False
 
 ### -AlternateWitnessDirectory
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AlternateWitnessDirectory parameter specifies the name of an alternate directory used to store witness data. The specified directory must not be in use by any other DAGs or used for any other purpose. This value can be populated ahead by using the Set-DatabaseAvailabilityGroup cmdlet.
 
@@ -121,7 +121,7 @@ Accept wildcard characters: False
 
 ### -AlternateWitnessServer
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AlternateWitnessServer parameter specifies the name of a new witness server for the DAG as part of a site activation process. This value can be populated ahead by using the Set-DatabaseAvailabilityGroup cmdlet.
 
@@ -139,7 +139,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -162,7 +162,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -180,7 +180,7 @@ Accept wildcard characters: False
 
 ### -UsePrimaryWitnessServer
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The UsePrimaryWitnessServer switch specifies that the DAG's currently configured witness server should be used if a witness is needed by the DAG members that are being activated. You don't need to specify a value with this switch.
 
@@ -198,7 +198,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Restore-DetailsTemplate.md b/exchange/exchange-ps/ExchangePowerShell/Restore-DetailsTemplate.md
index c535b125f8..fa1f5da099 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Restore-DetailsTemplate.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Restore-DetailsTemplate.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -47,7 +47,7 @@ This example restores the default attributes to the User details template for th
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the GUID or specifies the details template type and language separated by a backslash, for example, en-us\\User. Details template types include:
 
@@ -72,7 +72,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -95,7 +95,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -113,7 +113,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Restore-RecoverableItems.md b/exchange/exchange-ps/ExchangePowerShell/Restore-RecoverableItems.md
index 7dfbf5787e..a4fa08974d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Restore-RecoverableItems.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Restore-RecoverableItems.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
 Locale: en-US
@@ -121,7 +121,7 @@ This example bulk restores all the recoverable items for administrator.
 
 ### -Identity
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the mailbox that contains the deleted items that you want to restore. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -152,7 +152,7 @@ Accept wildcard characters: False
 
 ### -EntryID
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The EntryID parameter specifies the deleted item that you want to restore. The EntryID value for the deleted item is unique in the mailbox.
 
@@ -172,7 +172,7 @@ Accept wildcard characters: False
 
 ### -FilterEndTime
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The FilterEndTime specifies the end date/time of the date range. This parameter uses the LastModifiedTime value of the item.
 
@@ -192,7 +192,7 @@ Accept wildcard characters: False
 
 ### -FilterItemType
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The FilterItemType parameter filters the results by the specified MessageClass (ItemClass) property value of the deleted item. For example:
 
@@ -216,7 +216,7 @@ Accept wildcard characters: False
 
 ### -FilterStartTime
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The FilterStartTime specifies the start date/time of the date range. This parameter uses the LastModifiedTime value of the item.
 
@@ -236,7 +236,7 @@ Accept wildcard characters: False
 
 ### -LastParentFolderID
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The LastParentFolderID parameter specifies the FolderID value of the item before it was deleted. For example, 53B93149989CA54DBC9702AE619B9CCA000062CE9397.
 
@@ -346,7 +346,7 @@ Accept wildcard characters: False
 
 ### -ResultSize
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
 
@@ -364,7 +364,7 @@ Accept wildcard characters: False
 
 ### -SourceFolder
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SourceFolder parameter specifies where to search for deleted items in the mailbox. Valid values are:
 
@@ -390,7 +390,7 @@ Accept wildcard characters: False
 
 ### -SubjectContains
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SubjectContains parameter filters the deleted items by the specified text value in the Subject field. If the value contains spaces, enclose the value in quotation marks (").
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxDatabaseCopy.md b/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxDatabaseCopy.md
index 645c002cfe..8665313ed1 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxDatabaseCopy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxDatabaseCopy.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -67,7 +67,7 @@ This example resumes replication and replay activity for the copy of the databas
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the name of the database whose copying is being resumed.
 
@@ -85,7 +85,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -106,7 +106,7 @@ Accept wildcard characters: False
 
 ### -DisableReplayLag
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DisableReplayLag switch disables any configured replay lag time for the database copy when the passive copy is resumed. You don't need to specify a value with this switch.
 
@@ -124,7 +124,7 @@ Accept wildcard characters: False
 
 ### -DisableReplayLagReason
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DisableReplayLagReason parameter is used with the DisableReplayLag parameter to specify an administrative reason for disabling replay lag time for a passive copy.
 
@@ -142,7 +142,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -160,7 +160,7 @@ Accept wildcard characters: False
 
 ### -ReplicationOnly
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ReplicationOnly switch resumes replication without affecting the activation setting (for example, the ActivationSuspended property for the database copy remains set to True). You don't need to specify a value with this switch.
 
@@ -178,7 +178,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxExportRequest.md b/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxExportRequest.md
index 9dd5908f7a..b3adf7bcd2 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxExportRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxExportRequest.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -56,7 +56,7 @@ This example resumes any failed export move requests.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the identity of the export request. By default, export requests are named `<alias>\MailboxExportX` (where X = 0-9). Use the following syntax: `Alias\Name`.
 
@@ -74,7 +74,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -95,7 +95,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -113,7 +113,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxImportRequest.md b/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxImportRequest.md
index 785786b9af..84b68f065c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxImportRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxImportRequest.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -58,7 +58,7 @@ This example resumes all failed import requests.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the identity of the import request. By default, import requests are named `<alias>\MailboxImportX` (where X = 0-9). If you created the request using the Name parameter, use the following syntax: `Alias\Name`.
 
@@ -76,7 +76,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -97,7 +97,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -117,7 +117,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxRestoreRequest.md b/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxRestoreRequest.md
index fad77ae856..e724a01e35 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxRestoreRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Resume-MailboxRestoreRequest.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -52,7 +52,7 @@ This example resumes any restore request with the status of Failed.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the identity of the restore request. The Identity parameter consists of the alias of the mailbox to be restored and the name that was specified when the restore request was created. The identity of the restore request uses the following syntax: `Alias\Name`.
 
@@ -72,7 +72,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -93,7 +93,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -113,7 +113,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Resume-Message.md b/exchange/exchange-ps/ExchangePowerShell/Resume-Message.md
index 0e3a1e81b7..8e12b6fcb9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Resume-Message.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Resume-Message.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -60,7 +60,7 @@ This example resumes delivery of all messages in a suspended state and for which
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the message. Valid input for this parameter uses the syntax Server\\Queue\\MessageInteger or Queue\\MessageInteger or MessageInteger, for example, Mailbox01\\contoso.com\\5 or 10. For details about message identity, see [Message identity](https://learn.microsoft.com/Exchange/mail-flow/queues/queues-and-messages-in-powershell#message-identity).
 
@@ -78,7 +78,7 @@ Accept wildcard characters: False
 
 ### -Filter
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Filter parameter specifies one or more messages by using OPATH filter syntax. The OPATH filter includes a message property name followed by a comparison operator and value (for example, `"FromAddress -like '*@contoso.com'"`). For details about filterable message properties and comparison operators, see [Properties of messages in queues](https://learn.microsoft.com/Exchange/mail-flow/queues/message-properties) and [Find queues and messages in queues in the Exchange Management Shell](https://learn.microsoft.com/Exchange/mail-flow/queues/queues-and-messages-in-powershell).
 
@@ -98,7 +98,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -119,7 +119,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
 
@@ -146,7 +146,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Resume-MoveRequest.md b/exchange/exchange-ps/ExchangePowerShell/Resume-MoveRequest.md
index b1659f57e9..04cf94c12d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Resume-MoveRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Resume-MoveRequest.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -61,7 +61,7 @@ This example resumes any move requests that have the suspend comment "Resume aft
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the identity of the mailbox or mail user. You can use the following values:
 
@@ -87,7 +87,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -108,7 +108,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -159,7 +159,7 @@ Accept wildcard characters: False
 
 ### -SuspendWhenReadyToComplete
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SuspendWhenReadyToComplete switch suspends the move request before it reaches the status of CompletionInProgress. You don't need to specify a value with this switch.
 
@@ -179,7 +179,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Resume-PublicFolderMigrationRequest.md b/exchange/exchange-ps/ExchangePowerShell/Resume-PublicFolderMigrationRequest.md
index bd11ab1149..be2acbe60f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Resume-PublicFolderMigrationRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Resume-PublicFolderMigrationRequest.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -54,7 +54,7 @@ This example resumes any failed migration requests.
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the migration request that you want to resume. You can use the following values:
 
@@ -75,7 +75,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -96,7 +96,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -114,7 +114,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Resume-PublicFolderMoveRequest.md b/exchange/exchange-ps/ExchangePowerShell/Resume-PublicFolderMoveRequest.md
index 3573fecc7e..829cf0927e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Resume-PublicFolderMoveRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Resume-PublicFolderMoveRequest.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -59,7 +59,7 @@ This example resumes a move request that has the suspend comment "Resume after 1
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the identity of the public folder move request. The default identity is \\PublicFolderMove.
 
@@ -77,7 +77,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -98,7 +98,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -116,7 +116,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Resume-Queue.md b/exchange/exchange-ps/ExchangePowerShell/Resume-Queue.md
index fcd4ceaf1c..8accbc01e9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Resume-Queue.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Resume-Queue.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -56,7 +56,7 @@ This example resumes processing of all queues where the NextHopDomain is Fourthc
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the queue. Valid input for this parameter uses the syntax Server\\Queue or Queue, for example, Mailbox01\\contoso.com or Unreachable. For details about queue identity, see [Queue identity](https://learn.microsoft.com/Exchange/mail-flow/queues/queues-and-messages-in-powershell#queue-identity).
 
@@ -74,7 +74,7 @@ Accept wildcard characters: False
 
 ### -Filter
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Filter parameter specifies one or more queues by using OPATH filter syntax. The OPATH filter includes a queue property name followed by a comparison operator and value (for example, `"NextHopDomain -eq 'contoso.com'"`). For details about filterable queue properties and comparison operators, see [Queue properties in Exchange Server](https://learn.microsoft.com/Exchange/mail-flow/queues/queue-properties) and [Find queues and messages in queues in the Exchange Management Shell](https://learn.microsoft.com/Exchange/mail-flow/queues/queues-and-messages-in-powershell).
 
@@ -94,7 +94,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -115,7 +115,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
 
@@ -142,7 +142,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Retry-Queue.md b/exchange/exchange-ps/ExchangePowerShell/Retry-Queue.md
index 20b8cbb918..211362d848 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Retry-Queue.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Retry-Queue.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -62,7 +62,7 @@ This example forces a connection attempt for all queues that meet the following
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the queue. Valid input for this parameter uses the syntax Server\\Queue or Queue, for example, Mailbox01\\contoso.com or Unreachable. For details about queue identity, see [Queue identity](https://learn.microsoft.com/Exchange/mail-flow/queues/queues-and-messages-in-powershell#queue-identity).
 
@@ -80,7 +80,7 @@ Accept wildcard characters: False
 
 ### -Filter
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Filter parameter specifies one or more queues by using OPATH filter syntax. The OPATH filter includes a queue property name followed by a comparison operator and value (for example, `"NextHopDomain -eq 'contoso.com'"`). For details about filterable queue properties and comparison operators, see [Queue properties in Exchange Server](https://learn.microsoft.com/Exchange/mail-flow/queues/queue-properties) and [Find queues and messages in queues in the Exchange Management Shell](https://learn.microsoft.com/Exchange/mail-flow/queues/queues-and-messages-in-powershell).
 
@@ -100,7 +100,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -121,7 +121,7 @@ Accept wildcard characters: False
 
 ### -Resubmit
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Resubmit parameter specifies whether the queue contents should be resubmitted to the categorizer before a connection is established. Valid input for this parameter is $true or $false.
 
@@ -139,7 +139,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
 
@@ -166,7 +166,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Search-AdminAuditLog.md b/exchange/exchange-ps/ExchangePowerShell/Search-AdminAuditLog.md
index a1fe3fddee..870d841fbc 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Search-AdminAuditLog.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Search-AdminAuditLog.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
 Locale: en-US
@@ -96,7 +96,7 @@ This example returns entries in the administrator audit log of an Exchange Onlin
 
 ### -Cmdlets
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The Cmdlets parameter filters the results by the cmdlets that were used. You can specify multiple cmdlets separated by commas.
 
@@ -116,7 +116,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -136,7 +136,7 @@ Accept wildcard characters: False
 
 ### -EndDate
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The EndDate parameter specifies the end date of the date range.
 
@@ -163,7 +163,7 @@ Accept wildcard characters: False
 
 ### -ExternalAccess
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The ExternalAccess parameter filters the results by changes that were made (cmdlets that were run) by users outside of your organization. Valid values are:
 
@@ -184,7 +184,7 @@ Accept wildcard characters: False
 
 ### -IsSuccess
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The IsSuccess parameter filters the results by whether the changes were successful. Valid values are:
 
@@ -207,7 +207,7 @@ Accept wildcard characters: False
 
 ### -ObjectIds
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The ObjectIds parameter filters the results by the object that was modified (the mailbox, public folder, Send connector, transport rule, accepted domain, etc. that the cmdlet operated on). A valid value depends on how the object is represented in the audit log. For example:
 
@@ -233,7 +233,7 @@ Accept wildcard characters: False
 
 ### -Parameters
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The Parameters parameter filters the results by the parameters that were used. You can only use this parameter with the Cmdlets parameter (you can't use it by itself). You can specify multiple parameters separated by commas.
 
@@ -253,7 +253,7 @@ Accept wildcard characters: False
 
 ### -ResultSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The ResultSize parameter specifies the maximum number of results to return. The default value is 1000.
 
@@ -273,7 +273,7 @@ Accept wildcard characters: False
 
 ### -StartDate
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The StartDate parameter specifies the start date of the date range.
 
@@ -300,7 +300,7 @@ Accept wildcard characters: False
 
 ### -StartIndex
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The StartIndex parameter specifies the position in the result set where the displayed results start.
 
@@ -318,7 +318,7 @@ Accept wildcard characters: False
 
 ### -UserIds
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The UserIds parameter filters the results by the user who made the change (who ran the cmdlet).
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Search-Mailbox.md b/exchange/exchange-ps/ExchangePowerShell/Search-Mailbox.md
index 31efc27c8a..f9a7bd3a44 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Search-Mailbox.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Search-Mailbox.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
 Locale: en-US
@@ -117,7 +117,7 @@ This example searches all mailboxes in your organization for messages that conta
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the identity of the mailbox to search. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -146,7 +146,7 @@ Accept wildcard characters: False
 
 ### -EstimateResultOnly
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The EstimateResultOnly switch returns only an estimate of the total number and size of messages. Messages aren't copied to the target mailbox. You don't need to specify a value with this switch.
 
@@ -166,7 +166,7 @@ Accept wildcard characters: False
 
 ### -TargetFolder
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TargetFolder parameter specifies a folder name in which search results are saved in the target mailbox. The folder is created in the target mailbox upon execution.
 
@@ -184,7 +184,7 @@ Accept wildcard characters: False
 
 ### -TargetMailbox
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TargetMailbox parameter specifies the destination mailbox where search results are copied. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -215,7 +215,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -236,7 +236,7 @@ Accept wildcard characters: False
 
 ### -DeleteContent
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 **Note**: You need to be assigned the Mailbox Import Export management role to use this switch. By default, this role isn't assigned to any role group (including Organization Management). Typically, you assign a role to a built-in or custom role group.
 
@@ -260,7 +260,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -278,7 +278,7 @@ Accept wildcard characters: False
 
 ### -DoNotIncludeArchive
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DoNotIncludeArchive switch specifies that the user's archive mailbox shouldn't be included in the search. You don't need to specify a value for this switch.
 
@@ -300,7 +300,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -320,7 +320,7 @@ Accept wildcard characters: False
 
 ### -IncludeUnsearchableItems
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IncludeUnsearchableItems switch includes items that couldn't be indexed by Exchange Search in the search results. You don't need to specify a value with this switch.
 
@@ -338,7 +338,7 @@ Accept wildcard characters: False
 
 ### -LogLevel
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The LogLevel parameter specifies the logging level for the search. It can have one of the following values:
 
@@ -364,7 +364,7 @@ Accept wildcard characters: False
 
 ### -LogOnly
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The LogOnly switch performs a search, but only generates a log. Messages returned by the search aren't copied to the target mailbox. You don't need to specify a value with this switch.
 
@@ -384,7 +384,7 @@ Accept wildcard characters: False
 
 ### -SearchDumpster
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SearchDumpster switch specifies whether to include the Recoverable Items folder in the search. The Recoverable items folder stores items that were deleted from the Deleted Items folder or items that were hard-deleted until they're purged from the mailbox database.
 
@@ -404,7 +404,7 @@ Accept wildcard characters: False
 
 ### -SearchDumpsterOnly
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SearchDumpsterOnly switch specifies that only the Recoverable Items folder of the specified mailbox is searched. You don't need to specify a value with this switch.
 
@@ -426,7 +426,7 @@ Accept wildcard characters: False
 
 ### -SearchQuery
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SearchQuery parameter specifies a search string or a query formatted using Keyword Query Language (KQL). For more information about KQL in Exchange, see [Message properties and search operators for In-Place eDiscovery](https://learn.microsoft.com/exchange/security-and-compliance/in-place-ediscovery/message-properties-and-search-operators).
 
@@ -448,7 +448,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Search-MailboxAuditLog.md b/exchange/exchange-ps/ExchangePowerShell/Search-MailboxAuditLog.md
index 8a20ce8c36..d94d150151 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Search-MailboxAuditLog.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Search-MailboxAuditLog.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
 Locale: en-US
@@ -91,7 +91,7 @@ This example retrieves mailbox audit log entries for Ken Kwok's mailbox for acti
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies a single mailbox to retrieve mailbox audit log entries from. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -120,7 +120,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -140,7 +140,7 @@ Accept wildcard characters: False
 
 ### -EndDate
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The EndDate parameter specifies the end date of the date range.
 
@@ -160,7 +160,7 @@ Accept wildcard characters: False
 
 ### -ExternalAccess
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ExternalAccess parameter specifies whether to return only audit log entries for mailbox access by users that are outside of your organization. In Exchange Online, this parameter returns audit log entries for mailbox access by Microsoft datacenter administrators. Valid values are:
 
@@ -202,7 +202,7 @@ Accept wildcard characters: False
 
 ### -HasAttachments
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The HasAttachments parameter filters the search by messages that have attachments. Valid values are:
 
@@ -243,7 +243,7 @@ Accept wildcard characters: False
 
 ### -LogonTypes
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The LogonTypes parameter specifies the type of logons. Valid values are:
 
@@ -265,7 +265,7 @@ Accept wildcard characters: False
 
 ### -Mailboxes
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Mailboxes parameter specifies the mailboxes to retrieve mailbox audit log entries from. You can use this parameter to search audit logs for multiple mailboxes.
 
@@ -287,7 +287,7 @@ Accept wildcard characters: False
 
 ### -Operations
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Operations parameter filters the search results by the mailbox actions that are logged by mailbox audit logging. Valid values are:
 
@@ -331,7 +331,7 @@ Accept wildcard characters: False
 
 ### -ResultSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ResultSize parameter specifies the maximum number of mailbox audit log entries to return. Valid values include an integer from 1 through 250000. By default, 1000 entries are returned.
 
@@ -349,7 +349,7 @@ Accept wildcard characters: False
 
 ### -ShowDetails
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ShowDetails switch retrieves the details of each log entry from the mailbox. You don't need to specify a value with this switch.
 
@@ -371,7 +371,7 @@ Accept wildcard characters: False
 
 ### -StartDate
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The StartDate parameter specifies the start date of the date range.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Search-MessageTrackingReport.md b/exchange/exchange-ps/ExchangePowerShell/Search-MessageTrackingReport.md
index 87a469ee90..6f8d6c7f06 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Search-MessageTrackingReport.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Search-MessageTrackingReport.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -81,7 +81,7 @@ This example returns the message tracking reports that the Help desk can analyze
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter scopes the search to the specified mailbox. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -114,7 +114,7 @@ Accept wildcard characters: False
 
 ### -Sender
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Sender parameter specifies the email address of the message sender for messages that are sent to the mailbox that's specified by the Identity parameter.
 
@@ -134,7 +134,7 @@ Accept wildcard characters: False
 
 ### -BypassDelegateChecking
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The BypassDelegateChecking switch allows Help desk staff and administrators to track messages for any user. You don't need to specify a value with this switch.
 
@@ -154,7 +154,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -175,7 +175,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -195,7 +195,7 @@ Accept wildcard characters: False
 
 ### -DoNotResolve
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DoNotResolve switch specifies whether to prevent the resolution of email addresses to display names. You don't need to specify a value with this switch.
 
@@ -215,7 +215,7 @@ Accept wildcard characters: False
 
 ### -MessageEntryId
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is reserved for internal Microsoft use.
 
@@ -233,7 +233,7 @@ Accept wildcard characters: False
 
 ### -MessageId
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MessageId parameter filters the results by the Message-ID header field of the message. This value is also known as the Client ID. The format of the Message-ID depends on the messaging server that sent the message. The value should be unique for each message. However, not all messaging servers create values for the Message-ID in the same way. Be sure to include the full Message ID string (which might include angle brackets) and enclose the value in quotation marks (for example, "<d9683b4c-127b-413a-ae2e-fa7dfb32c69d@contoso.com>").
 
@@ -251,7 +251,7 @@ Accept wildcard characters: False
 
 ### -Recipients
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Recipients parameter filters the results by the email addresses of the specified recipients. You can specify multiple email addresses separated by commas.
 
@@ -271,7 +271,7 @@ Accept wildcard characters: False
 
 ### -ResultSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ResultSize parameter specifies the maximum number of results to return. If you want to return all requests that match the query, use unlimited for the value of this parameter. The default value is 1000.
 
@@ -289,7 +289,7 @@ Accept wildcard characters: False
 
 ### -Subject
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Subject parameter searches for messages with the specified Subject field value. If the value contains spaces, enclosed the value in quotation marks.
 
@@ -307,7 +307,7 @@ Accept wildcard characters: False
 
 ### -TraceLevel
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TraceLevel parameter specifies the details to include in the results. Valid values are:
 
@@ -331,7 +331,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Send-TextMessagingVerificationCode.md b/exchange/exchange-ps/ExchangePowerShell/Send-TextMessagingVerificationCode.md
index af84b61d3e..6571b18577 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Send-TextMessagingVerificationCode.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Send-TextMessagingVerificationCode.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.WebClient-Help.xml
 Locale: en-US
@@ -63,7 +63,7 @@ This example sends the text messaging verification code to Tony Smith's mobile p
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the mailbox where you are trying to enable text messaging notifications. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -92,7 +92,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -113,7 +113,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -133,7 +133,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ADServerSettings.md b/exchange/exchange-ps/ExchangePowerShell/Set-ADServerSettings.md
index 537e6dd15f..f1c61d1cfa 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ADServerSettings.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ADServerSettings.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -74,7 +74,7 @@ This example sets the scope of the current session to the entire forest and desi
 
 ### -PreferredServer
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PreferredServer parameter specifies the FQDN of the domain controller to be used for this session.
 
@@ -92,7 +92,7 @@ Accept wildcard characters: False
 
 ### -RunspaceServerSettings
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RunspaceServerSettings parameter specifies whether to pass an entire configuration object to the command to be processed. This parameter is useful in scripts where an entire object must be passed to the command.
 
@@ -110,7 +110,7 @@ Accept wildcard characters: False
 
 ### -ConfigurationDomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ConfigurationDomainController parameter specifies the fully qualified domain name (FQDN) of the configuration domain controller to be used for reading Exchange configuration information in this session.
 
@@ -128,7 +128,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -149,7 +149,7 @@ Accept wildcard characters: False
 
 ### -PreferredGlobalCatalog
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PreferredGlobalCatalog parameter specifies the FQDN of the global catalog server to be used for reading recipient information in this session.
 
@@ -167,7 +167,7 @@ Accept wildcard characters: False
 
 ### -RecipientViewRoot
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RecipientViewRoot parameter specifies the organizational unit (OU) to include in the recipient scope for this session. When you specify a recipient scope with this parameter, only the recipients included in the scope are returned. To specify an OU, use the syntax `<FQDN of domain>/<OU tree>`.
 
@@ -185,7 +185,7 @@ Accept wildcard characters: False
 
 ### -SetPreferredDomainControllers
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SetPreferredDomainControllers parameter specifies the list of domain controllers used to read information from Active Directory in this session. You must specify the FQDN of the domain controllers. Separate multiple domain controllers using commas.
 
@@ -203,7 +203,7 @@ Accept wildcard characters: False
 
 ### -ViewEntireForest
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ViewEntireForest parameter specifies whether all the objects in the forest are viewed and managed in this session. Valid values are $true and $false.
 
@@ -223,7 +223,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ADSite.md b/exchange/exchange-ps/ExchangePowerShell/Set-ADSite.md
index 03b5ba59ce..d944da297f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ADSite.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ADSite.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -48,7 +48,7 @@ This example configures the Active Directory site named Default-First-Site-Name
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the identity of the Active Directory site you want to modify. You can use any value that uniquely identifies the site. For example, you can use the name, GUID or distinguished name (DN) of the Active Directory site.
 
@@ -66,7 +66,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -87,7 +87,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -105,7 +105,7 @@ Accept wildcard characters: False
 
 ### -HubSiteEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The HubSiteEnabled parameter specifies whether this site acts as a hub site. The default value is $false.
 
@@ -123,7 +123,7 @@ Accept wildcard characters: False
 
 ### -InboundMailEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The InboundMailEnabled parameter enables or disables receiving incoming messages for all Exchange servers located in the Active Directory site. Typically, you use this parameter after Active Directory site failover or maintenance. Valid values are:
 
@@ -144,7 +144,7 @@ Accept wildcard characters: False
 
 ### -PartnerId
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -162,7 +162,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ADSiteLink.md b/exchange/exchange-ps/ExchangePowerShell/Set-ADSiteLink.md
index f47a8b17c3..8714158ab8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ADSiteLink.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ADSiteLink.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -50,7 +50,7 @@ This example assigns an Exchange-specific cost of 25 to the IP site link DEFAULT
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the name or GUID of the IP site link you want to modify.
 
@@ -68,7 +68,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -89,7 +89,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -109,7 +109,7 @@ Accept wildcard characters: False
 
 ### -ExchangeCost
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExchangeCost parameter specifies an Exchange-specific cost for the IP site link. This cost is used instead of the Active Directory-assigned cost. To clear the value of the ExchangeCost parameter and revert to using the cost of the IP site link specified in Active Directory, set the value of the ExchangeCost parameter to $null.
 
@@ -127,7 +127,7 @@ Accept wildcard characters: False
 
 ### -MaxMessageSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MaxMessageSize parameter specifies the maximum size of a message that can pass across the Active Directory IP site link. The default value is unlimited.
 
@@ -157,7 +157,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Name parameter specifies a unique name for the IP site link. The name that you assign overwrites the current identity of the IP site link.
 
@@ -175,7 +175,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AcceptedDomain.md b/exchange/exchange-ps/ExchangePowerShell/Set-AcceptedDomain.md
index 6c681e1ca8..79b84fb443 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-AcceptedDomain.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-AcceptedDomain.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -57,7 +57,7 @@ This example makes the accepted domain Contoso the default accepted domain.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the accepted domain you want to modify. You can use any value that uniquely identifies the accepted domain object. For example, you can use the name, GUID or distinguished name (DN) of the accepted domain.
 
@@ -75,7 +75,7 @@ Accept wildcard characters: False
 
 ### -AddressBookEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -119,7 +119,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -140,7 +140,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -162,7 +162,7 @@ Accept wildcard characters: False
 
 ### -DomainType
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The DomainType parameter specifies the accepted domain type. Valid values are:
 
@@ -206,7 +206,7 @@ Accept wildcard characters: False
 
 ### -MakeDefault
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -233,7 +233,7 @@ Accept wildcard characters: False
 
 ### -MatchSubDomains
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The MatchSubDomains parameter enables mail to be sent by and received from users on any subdomain of this accepted domain. The default value is $false.
 
@@ -251,7 +251,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -293,7 +293,7 @@ Accept wildcard characters: False
 
 ### -PendingCompletion
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -313,7 +313,7 @@ Accept wildcard characters: False
 
 ### -PendingRemoval
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -383,7 +383,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncDeviceAccessRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncDeviceAccessRule.md
index b2dfc71570..bf13bff81e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncDeviceAccessRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncDeviceAccessRule.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
 Locale: en-US
@@ -55,7 +55,7 @@ This example changes the organization's device access rule so that all devices e
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the identity of the device access rule.
 
@@ -73,7 +73,7 @@ Accept wildcard characters: False
 
 ### -AccessLevel
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AccessLevel parameter specifies whether the devices are allowed, blocked or quarantined.
 
@@ -91,7 +91,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -112,7 +112,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -132,7 +132,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncDeviceAutoblockThreshold.md b/exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncDeviceAutoblockThreshold.md
index 8b29f977a3..7eedcada2e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncDeviceAutoblockThreshold.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncDeviceAutoblockThreshold.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
 Locale: en-US
@@ -58,7 +58,7 @@ This example sets the autoblock threshold rule RecentCommands with several setti
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the name of the autoblock threshold rule.
 
@@ -76,7 +76,7 @@ Accept wildcard characters: False
 
 ### -AdminEmailInsert
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AdminEmailInsert parameter specifies the text to include in the email sent to the user when a mobile device triggers an autoblock threshold rule.
 
@@ -94,7 +94,7 @@ Accept wildcard characters: False
 
 ### -BehaviorTypeIncidenceDuration
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The BehaviorTypeIncidenceDuration parameter specifies the interval (in minutes) within which the BehaviorType must occur to trigger the autoblock rule.
 
@@ -112,7 +112,7 @@ Accept wildcard characters: False
 
 ### -BehaviorTypeIncidenceLimit
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The BehaviorTypeIncidenceLimit parameter specifies the number of occurrences of the behavior type needed to trigger blocking.
 
@@ -130,7 +130,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -151,7 +151,7 @@ Accept wildcard characters: False
 
 ### -DeviceBlockDuration
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DeviceBlockDuration parameter specifies the length of time (in minutes) that the mobile device is blocked.
 
@@ -169,7 +169,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -187,7 +187,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncMailboxPolicy.md
index d5222a900b..eb05bd85e3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncMailboxPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncMailboxPolicy.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
 Locale: en-US
@@ -119,7 +119,7 @@ This example sets several policy settings for the Mobile Device mailbox policy D
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the Mobile Device mailbox policy.
 
@@ -157,7 +157,7 @@ Accept wildcard characters: False
 
 ### -AllowBluetooth
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowBluetooth parameter specifies whether the Bluetooth capabilities are allowed on the mobile phone. The available options are Disable, HandsfreeOnly, and Allow. The default value is Allow.
 
@@ -175,7 +175,7 @@ Accept wildcard characters: False
 
 ### -AllowBrowser
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowBrowser parameter indicates whether Microsoft Pocket Internet Explorer is allowed on the mobile phone. The default value is $true. This parameter doesn't affect non-Microsoft browsers.
 
@@ -193,7 +193,7 @@ Accept wildcard characters: False
 
 ### -AllowCamera
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowCamera parameter specifies whether the mobile phone's camera is allowed. The default value is $true.
 
@@ -211,7 +211,7 @@ Accept wildcard characters: False
 
 ### -AllowConsumerEmail
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowConsumerEmail parameter specifies whether the mobile phone user can configure a personal email account on the mobile phone. The default value is $true. This parameter doesn't control access to emails using non-Microsoft mobile phone email programs.
 
@@ -229,7 +229,7 @@ Accept wildcard characters: False
 
 ### -AllowDesktopSync
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowDesktopSync parameter specifies whether the mobile phone can synchronize with a desktop computer through a cable. The default value is $true.
 
@@ -247,7 +247,7 @@ Accept wildcard characters: False
 
 ### -AllowExternalDeviceManagement
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowExternalDeviceManagement parameter specifies whether an external device management program is allowed to manage the mobile phone.
 
@@ -265,7 +265,7 @@ Accept wildcard characters: False
 
 ### -AllowHTMLEmail
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowHTMLEmail parameter specifies whether HTML email is enabled on the mobile phone. The default value is $true. If set to $false, all email is converted to plain text before synchronization occurs.
 
@@ -283,7 +283,7 @@ Accept wildcard characters: False
 
 ### -AllowInternetSharing
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowInternetSharing parameter specifies whether the mobile phone can be used as a modem to connect a computer to the Internet. The default value is $true.
 
@@ -301,7 +301,7 @@ Accept wildcard characters: False
 
 ### -AllowIrDA
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowIrDA parameter specifies whether infrared connections are allowed to the mobile phone. The default value is $true.
 
@@ -319,7 +319,7 @@ Accept wildcard characters: False
 
 ### -AllowMobileOTAUpdate
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowMobileOTAUpdate parameter specifies whether the Exchange ActiveSync mailbox policy can be sent to the mobile phone over a cellular data connection.
 
@@ -337,7 +337,7 @@ Accept wildcard characters: False
 
 ### -AllowNonProvisionableDevices
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowNonProvisionableDevices parameter specifies whether all mobile phones can synchronize with the server running Exchange. When set to $true, the AllowNonProvisionableDevices parameter enables all mobile phones to synchronize with the Exchange server, regardless of whether the phone can enforce all the specific settings established in the Mobile Device mailbox policy. This also includes mobile phones managed by a separate device management system. When set to $false, this parameter blocks mobile phones that aren't provisioned from synchronizing with the Exchange server. The default value is $false.
 
@@ -355,7 +355,7 @@ Accept wildcard characters: False
 
 ### -AllowPOPIMAPEmail
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowPOPIMAPEmail parameter specifies whether the user can configure a POP3 or IMAP4 email account on the mobile phone. The default value is $true. This parameter doesn't control access by non-Microsoft email programs.
 
@@ -373,7 +373,7 @@ Accept wildcard characters: False
 
 ### -AllowRemoteDesktop
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowRemoteDesktop parameter specifies whether the mobile phone can initiate a remote desktop connection. The default value is $true.
 
@@ -391,7 +391,7 @@ Accept wildcard characters: False
 
 ### -AllowSimpleDevicePassword
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowSimpleDevicePassword parameter specifies whether a simple device password is allowed. A simple device password is a password that has a specific pattern, such as 1111 or 1234. The default value is $true.
 
@@ -409,7 +409,7 @@ Accept wildcard characters: False
 
 ### -AllowSMIMEEncryptionAlgorithmNegotiation
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowSMIMEEncryptionAlgorithmNegotiation parameter specifies whether the messaging application on the mobile phone can negotiate the encryption algorithm if a recipient's certificate doesn't support the specified encryption algorithm.
 
@@ -427,7 +427,7 @@ Accept wildcard characters: False
 
 ### -AllowSMIMESoftCerts
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowSMIMESoftCerts parameter specifies whether S/MIME software certificates are allowed. The default value is $true.
 
@@ -445,7 +445,7 @@ Accept wildcard characters: False
 
 ### -AllowStorageCard
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowStorageCard parameter specifies whether the mobile phone can access information stored on a storage card. The default value is $true.
 
@@ -463,7 +463,7 @@ Accept wildcard characters: False
 
 ### -AllowTextMessaging
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowTextMessaging parameter specifies whether text messaging is allowed from the mobile phone. The default value is $true.
 
@@ -481,7 +481,7 @@ Accept wildcard characters: False
 
 ### -AllowUnsignedApplications
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowUnsignedApplications parameter specifies whether unsigned applications can be installed on the mobile phone. The default value is $true.
 
@@ -499,7 +499,7 @@ Accept wildcard characters: False
 
 ### -AllowUnsignedInstallationPackages
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowUnsignedInstallationPackages parameter specifies whether unsigned installation packages can be executed on the mobile phone. The default value is $true.
 
@@ -517,7 +517,7 @@ Accept wildcard characters: False
 
 ### -AllowWiFi
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowWiFi parameter specifies whether wireless Internet access is allowed on the mobile phone. The default value is $true.
 
@@ -535,7 +535,7 @@ Accept wildcard characters: False
 
 ### -AlphanumericDevicePasswordRequired
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AlphanumericDevicePasswordRequired parameter specifies whether the password for the mobile phone must be alphanumeric. The default value is $false.
 
@@ -553,7 +553,7 @@ Accept wildcard characters: False
 
 ### -ApprovedApplicationList
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ApprovedApplicationList parameter specifies a list of approved applications for the mobile phone.
 
@@ -571,7 +571,7 @@ Accept wildcard characters: False
 
 ### -AttachmentsEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AttachmentsEnabled parameter specifies whether attachments can be downloaded. When set to $false, the AttachmentsEnabled parameter blocks the user from downloading attachments. The default value is $true.
 
@@ -589,7 +589,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -610,7 +610,7 @@ Accept wildcard characters: False
 
 ### -DeviceEncryptionEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DeviceEncryptionEnabled parameter specifies whether encryption is enabled. The DeviceEncryptionEnabled parameter, when set to $true, enables device encryption on the mobile phone. The default value is $false.
 
@@ -628,7 +628,7 @@ Accept wildcard characters: False
 
 ### -DevicePasswordEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DevicePasswordEnabled parameter specifies whether a password is required. When set to $true, the DevicePasswordEnabled parameter requires that the user set a password for the mobile phone. The default value is $false.
 
@@ -646,7 +646,7 @@ Accept wildcard characters: False
 
 ### -DevicePasswordExpiration
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DevicePasswordExpiration parameter specifies the length of time, in days, that a password can be used. After this length of time, a new password must be created. The format of the parameter is dd.hh.mm:ss, for example, 24.00:00 = 24 hours.
 
@@ -664,7 +664,7 @@ Accept wildcard characters: False
 
 ### -DevicePasswordHistory
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DevicePasswordHistory parameter specifies the number of previously used passwords to store. When a user creates a password, the user can't reuse a stored password that was previously used.
 
@@ -682,7 +682,7 @@ Accept wildcard characters: False
 
 ### -DevicePolicyRefreshInterval
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DevicePolicyRefreshInterval parameter specifies how often the policy is sent from the server to the mobile phone.
 
@@ -700,7 +700,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -720,7 +720,7 @@ Accept wildcard characters: False
 
 ### -IrmEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IrmEnabled parameter specifies whether Information Rights Management (IRM) is enabled for the mailbox policy.
 
@@ -738,7 +738,7 @@ Accept wildcard characters: False
 
 ### -IsDefault
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IsDefault parameter specifies whether this policy is the default Mobile Device mailbox policy. The default value is $false. If another policy is currently set as the default, setting this parameter replaces the old default policy with this policy.
 
@@ -756,7 +756,7 @@ Accept wildcard characters: False
 
 ### -IsDefaultPolicy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IsDefault parameter specifies whether this policy is the default Mobile Device mailbox policy. The default value is $false. If another policy is currently set as the default, setting this parameter replaces the old default policy with this policy.
 
@@ -774,7 +774,7 @@ Accept wildcard characters: False
 
 ### -MaxAttachmentSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MaxAttachmentSize parameter specifies the maximum size of attachments that can be downloaded to the mobile phone. The default value is Unlimited.
 
@@ -792,7 +792,7 @@ Accept wildcard characters: False
 
 ### -MaxCalendarAgeFilter
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MaxCalendarAgeFilter parameter specifies the maximum range of calendar days that can be synchronized to the device. The value is specified by entering one of the following values:
 
@@ -817,7 +817,7 @@ Accept wildcard characters: False
 
 ### -MaxDevicePasswordFailedAttempts
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MaxDevicePasswordFailedAttempts parameter specifies the number of attempts a user can make to enter the correct password for the mobile phone. You can enter any number from 4 through 16. The default value is 8.
 
@@ -835,7 +835,7 @@ Accept wildcard characters: False
 
 ### -MaxEmailAgeFilter
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MaxEmailAgeFilter parameter specifies the maximum number of days of email items to synchronize to the mobile phone. The value is specified by entering one of the following values.
 
@@ -860,7 +860,7 @@ Accept wildcard characters: False
 
 ### -MaxEmailBodyTruncationSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MaxEmailBodyTruncationSize parameter specifies the maximum size at which email messages are truncated when synchronized to the mobile phone. The value is specified in kilobytes (KB).
 
@@ -878,7 +878,7 @@ Accept wildcard characters: False
 
 ### -MaxEmailHTMLBodyTruncationSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MaxEmailHTMLBodyTruncationSize parameter specifies the maximum size at which HTML-formatted email messages are synchronized to the mobile phone. The value is specified in KB.
 
@@ -896,7 +896,7 @@ Accept wildcard characters: False
 
 ### -MaxInactivityTimeDeviceLock
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MaxInactivityTimeDeviceLock parameter specifies the length of time that the mobile phone can be inactive before the password is required to reactivate it. You can enter any interval between 30 seconds and 1 hour. The default value is 15 minutes. The format of the parameter is hh.mm:ss, for example, 15:00 = 15 minutes.
 
@@ -914,7 +914,7 @@ Accept wildcard characters: False
 
 ### -MinDevicePasswordComplexCharacters
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MinDevicePasswordComplexCharacters parameter specifies the minimum number of complex characters required in a mobile phone password. A complex character isn't a letter.
 
@@ -932,7 +932,7 @@ Accept wildcard characters: False
 
 ### -MinDevicePasswordLength
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MinDevicePasswordLength parameter specifies the minimum number of characters in the device password. You can enter any number from 1 through 16. The maximum length a password can be is 16 characters. The default value is 4.
 
@@ -950,7 +950,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Name parameter specifies the friendly name of the Mobile Device mailbox policy.
 
@@ -968,7 +968,7 @@ Accept wildcard characters: False
 
 ### -PasswordRecoveryEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The PasswordRecoveryEnabled parameter specifies whether the recovery password for the mobile phone is stored on an Exchange server. When set to $true, the PasswordRecoveryEnabled parameter enables you to store the recovery password for the mobile phone on an Exchange server. The default value is $false. The recovery password can be viewed from either Outlook on the web or the Exchange admin center.
 
@@ -986,7 +986,7 @@ Accept wildcard characters: False
 
 ### -RequireDeviceEncryption
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RequireDeviceEncryption parameter specifies whether encryption is required on the device. The default value is $false.
 
@@ -1004,7 +1004,7 @@ Accept wildcard characters: False
 
 ### -RequireEncryptedSMIMEMessages
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RequireEncryptedSMIMEMessages parameter specifies whether you must encrypt S/MIME messages. The default value is $false.
 
@@ -1022,7 +1022,7 @@ Accept wildcard characters: False
 
 ### -RequireEncryptionSMIMEAlgorithm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RequireEncryptionSMIMEAlgorithm parameter specifies what required algorithm must be used when encrypting a message.
 
@@ -1040,7 +1040,7 @@ Accept wildcard characters: False
 
 ### -RequireManualSyncWhenRoaming
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RequireManualSyncWhenRoaming parameter specifies whether the mobile phone must synchronize manually while roaming. The default value is $false.
 
@@ -1058,7 +1058,7 @@ Accept wildcard characters: False
 
 ### -RequireSignedSMIMEAlgorithm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RequireSignedSMIMEAlgorithm parameter specifies what required algorithm must be used when signing a message.
 
@@ -1076,7 +1076,7 @@ Accept wildcard characters: False
 
 ### -RequireSignedSMIMEMessages
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RequireSignedSMIMEMessages parameter specifies whether the mobile phone must send signed S/MIME messages.
 
@@ -1094,7 +1094,7 @@ Accept wildcard characters: False
 
 ### -RequireStorageCardEncryption
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RequireStorageCardEncryption parameter specifies whether storage card encryption is enabled for the mailbox policy. Setting this parameter to $true also sets the DeviceEncryptionEnabled parameter to $true.
 
@@ -1112,7 +1112,7 @@ Accept wildcard characters: False
 
 ### -UnapprovedInROMApplicationList
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The UnapprovedInROMApplicationList parameter contains a list of applications that can't be run in ROM.
 
@@ -1130,7 +1130,7 @@ Accept wildcard characters: False
 
 ### -UNCAccessEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The UNCAccessEnabled parameter specifies whether access to Microsoft Windows file shares is enabled. Access to specific shares is configured on the Exchange ActiveSync virtual directory.
 
@@ -1148,7 +1148,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
@@ -1166,7 +1166,7 @@ Accept wildcard characters: False
 
 ### -WSSAccessEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WSSAccessEnabled parameter specifies whether access to Microsoft Windows SharePoint Services is enabled. Access to specific shares is configured on the Exchange ActiveSync virtual directory.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncOrganizationSettings.md b/exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncOrganizationSettings.md
index c1e59f6d4b..c020f0c314 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncOrganizationSettings.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncOrganizationSettings.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
 Locale: en-US
@@ -53,7 +53,7 @@ This example sets the default access level to quarantine and sets two administra
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the ActiveSync organization settings object that you want to modify. The default name of this object is Mobile Mailbox Settings.
 
@@ -71,7 +71,7 @@ Accept wildcard characters: False
 
 ### -AdminMailRecipients
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AdminMailRecipients parameter specifies the email addresses of the administrators for reporting purposes.
 
@@ -93,7 +93,7 @@ Accept wildcard characters: False
 
 ### -AllowAccessForUnSupportedPlatform
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is reserved for internal Microsoft use.
 
@@ -111,7 +111,7 @@ Accept wildcard characters: False
 
 ### -AllowRMSSupportForUnenlightenedApps
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is functional only in the cloud-based service.
 
@@ -134,7 +134,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -155,7 +155,7 @@ Accept wildcard characters: False
 
 ### -DefaultAccessLevel
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DefaultAccessLevel parameter specifies the access level for new and existing device partnerships. Valid values are:
 
@@ -179,7 +179,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -219,7 +219,7 @@ Accept wildcard characters: False
 
 ### -OtaNotificationMailInsert
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The OtaNotificationMailInsert parameter specifies the text to include in an email message that's sent to users who need to update their older devices to use the new Exchange ActiveSync features in Microsoft Exchange.
 
@@ -259,7 +259,7 @@ Accept wildcard characters: False
 
 ### -UserMailInsert
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The UserMailInsert parameter specifies an informational footer that's added to the email message sent to users when their mobile device isn't synchronized because the device is quarantined.
 
@@ -279,7 +279,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncVirtualDirectory.md
index 676037bf7e..70e34052a8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncVirtualDirectory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ActiveSyncVirtualDirectory.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
 Locale: en-US
@@ -84,7 +84,7 @@ This example configures the external URL on the default Exchange ActiveSync virt
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the ActiveSync virtual directory that you want to modify. You can use any value that uniquely identifies the virtual directory. For example:
 
@@ -108,7 +108,7 @@ Accept wildcard characters: False
 
 ### -ActiveSyncServer
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ActiveSyncServer parameter specifies the URL of the Mailbox server. This value is in the following format: https://servername/Microsoft-Server-ActiveSync.
 
@@ -126,7 +126,7 @@ Accept wildcard characters: False
 
 ### -BadItemReportingEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The BadItemReportingEnabled parameter specifies whether items that can't be synchronized should be reported to the user. If set to $true, the user receives a notification when an item can't be synchronized to the mobile phone.
 
@@ -144,7 +144,7 @@ Accept wildcard characters: False
 
 ### -BasicAuthEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The BasicAuthentication parameter specifies whether Basic authentication is enabled on the virtual directory. Valid values are:
 
@@ -165,7 +165,7 @@ Accept wildcard characters: False
 
 ### -ClientCertAuth
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ClientCertAuth parameter specifies the status of client certificate authentication. By default, client certificate authentication is disabled. The default setting is Ignore.
 
@@ -183,7 +183,7 @@ Accept wildcard characters: False
 
 ### -CompressionEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The CompressionEnabled parameter is a Boolean value that identifies the compression applied to the specified Exchange ActiveSync virtual directory. The default setting is $true.
 
@@ -201,7 +201,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -222,7 +222,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -240,7 +240,7 @@ Accept wildcard characters: False
 
 ### -ExtendedProtectionFlags
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExtendedProtectionFlags parameter specifies custom settings for Extended Protection for Authentication on the virtual directory. Valid values are:
 
@@ -264,7 +264,7 @@ Accept wildcard characters: False
 
 ### -ExtendedProtectionSPNList
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExtendedProtectionSPNList parameter specifies a list of valid Service Principal Names (SPNs) if you're using Extended Protection for Authentication on the virtual directory. Valid values are:
 
@@ -285,7 +285,7 @@ Accept wildcard characters: False
 
 ### -ExtendedProtectionTokenChecking
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExtendedProtectionTokenChecking parameter defines how you want to use Extended Protection for Authentication on the virtual directory. Extended Protection for Authentication isn't enabled by default. Valid values are:
 
@@ -309,7 +309,7 @@ Accept wildcard characters: False
 
 ### -ExternalAuthenticationMethods
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExternalAuthenticationMethods parameter restricts the authentication methods that can be used to connect to the virtual directory from outside the firewall. Valid values are:
 
@@ -350,7 +350,7 @@ Accept wildcard characters: False
 
 ### -ExternalUrl
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExternalURL parameter specifies the URL that's used to connect to the virtual directory from outside the firewall.
 
@@ -368,7 +368,7 @@ Accept wildcard characters: False
 
 ### -InstallIsapiFilter
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The InstallIsapiFilter parameter specifies whether the Internet Server API (ISAPI) filter is installed.
 
@@ -386,7 +386,7 @@ Accept wildcard characters: False
 
 ### -InternalAuthenticationMethods
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The InternalAuthenticationMethods parameter specifies the authentication methods supported by the server that contains the virtual directory when access is requested from inside the network firewall. If this parameter isn't set, all authentication methods can be used.
 
@@ -404,7 +404,7 @@ Accept wildcard characters: False
 
 ### -InternalUrl
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The InternalURL parameter specifies the URL that's used to connect to the virtual directory from inside the firewall.
 
@@ -422,7 +422,7 @@ Accept wildcard characters: False
 
 ### -MobileClientCertificateAuthorityURL
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MobileClientCertificateAuthorityURL parameter specifies the URL for the certification authority (CA) used by the mobile phone.
 
@@ -440,7 +440,7 @@ Accept wildcard characters: False
 
 ### -MobileClientCertificateProvisioningEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MobileClientCertificateProvisioningEnabled parameter specifies whether the Autodiscover service returns the Certificate Services server URL in the XML file.
 
@@ -458,7 +458,7 @@ Accept wildcard characters: False
 
 ### -MobileClientCertTemplateName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MobileClientCertTemplateName parameter specifies the template name for the client certificate.
 
@@ -476,7 +476,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Name parameter specifies the name of the Exchange ActiveSync virtual directory.
 
@@ -494,7 +494,7 @@ Accept wildcard characters: False
 
 ### -RemoteDocumentsActionForUnknownServers
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RemoteDocumentsActionForUnknownServers parameter specifies the action that occurs when a Microsoft Windows SharePoint Services or Microsoft Windows file share request comes in via Exchange ActiveSync. When a request arrives, Exchange ActiveSync looks for the requested host name in the Allow and Block lists. If the host name isn't found in either list, the action specified in this parameter, either Block or Allow, is performed.
 
@@ -512,7 +512,7 @@ Accept wildcard characters: False
 
 ### -RemoteDocumentsAllowedServers
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RemoteDocumentsAllowedServers parameter is a multivalued property that lists all the allowed servers for remote document access.
 
@@ -530,7 +530,7 @@ Accept wildcard characters: False
 
 ### -RemoteDocumentsBlockedServers
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RemoteDocumentsBlockedServers parameter is a multivalued property that lists all the blocked servers for remote document access.
 
@@ -548,7 +548,7 @@ Accept wildcard characters: False
 
 ### -RemoteDocumentsInternalDomainSuffixList
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RemoteDocumentsInternalDomainSuffixList parameter is used in organizations that don't run Windows Internet Name Service (WINS) in their network. In these environments, you can specify one or more FQDNs that Exchange ActiveSync treats as internal when a request for remote file access is received.
 
@@ -566,7 +566,7 @@ Accept wildcard characters: False
 
 ### -SendWatsonReport
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SendWatsonReport parameter specifies whether a Watson report is sent for errors and events.
 
@@ -584,7 +584,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
@@ -602,7 +602,7 @@ Accept wildcard characters: False
 
 ### -WindowsAuthEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WindowsAuthEnabled parameter specifies whether Integrated Windows authentication is enabled. The default value is $false.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AddressBookPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-AddressBookPolicy.md
index 3ca49ee585..d9cbb93845 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-AddressBookPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-AddressBookPolicy.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -52,7 +52,7 @@ This example changes the OAB that the address book policy All Fabrikam ABP uses
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the identity of the address book policy that you want to modify.
 
@@ -70,7 +70,7 @@ Accept wildcard characters: False
 
 ### -AddressLists
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AddressLists parameter specifies the address lists for mailbox users who are assigned this address book policy. You can use any value that uniquely identifies the address list. For example:
 
@@ -96,7 +96,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -117,7 +117,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -137,7 +137,7 @@ Accept wildcard characters: False
 
 ### -GlobalAddressList
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The GlobalAddressList parameter specifies the GAL for mailbox users who are assigned this address book policy. You can use any value that uniquely identifies the GAL. For example:
 
@@ -163,7 +163,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Name parameter specifies the name that you want this address book policy to be called. Use this parameter to change the name of the address book policy.
 
@@ -181,7 +181,7 @@ Accept wildcard characters: False
 
 ### -OfflineAddressBook
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The OfflineAddressBook parameter specifies the OAB for mailbox users who are assigned this address book policy. You can use any value that uniquely identifies the OAB. For example:
 
@@ -207,7 +207,7 @@ Accept wildcard characters: False
 
 ### -RoomList
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RoomList parameter specifies an address list that used for location experiences for mailbox users who have this address book policy assigned to them.
 
@@ -237,7 +237,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AddressList.md b/exchange/exchange-ps/ExchangePowerShell/Set-AddressList.md
index 72c8d4e3e6..bb34e97f03 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-AddressList.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-AddressList.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -90,7 +90,7 @@ This example modifies the type of recipients and the department of the recipient
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the address list that you want to modify. You can use any value that uniquely identifies the address list. For example:
 
@@ -113,7 +113,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCompany
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalCompany parameter specifies a precanned filter that's based on the value of the recipient's Company property.
 
@@ -137,7 +137,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute1
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalCustomAttribute1 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute1 property. You can specify multiple values separated by commas.
 
@@ -161,7 +161,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute10
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalCustomAttribute10 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute10 property. You can specify multiple values separated by commas.
 
@@ -185,7 +185,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute11
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalCustomAttribute11 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute11 property. You can specify multiple values separated by commas.
 
@@ -209,7 +209,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute12
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalCustomAttribute12 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute12 property. You can specify multiple values separated by commas.
 
@@ -233,7 +233,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute13
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalCustomAttribute13 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute13 property. You can specify multiple values separated by commas.
 
@@ -257,7 +257,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute14
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalCustomAttribute14 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute14 property. You can specify multiple values separated by commas.
 
@@ -281,7 +281,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute15
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalCustomAttribute15 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute15 property. You can specify multiple values separated by commas.
 
@@ -305,7 +305,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute2
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalCustomAttribute2 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute2 property. You can specify multiple values separated by commas.
 
@@ -329,7 +329,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute3
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalCustomAttribute3 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute3 property. You can specify multiple values separated by commas.
 
@@ -353,7 +353,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute4
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalCustomAttribute4 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute4 property. You can specify multiple values separated by commas.
 
@@ -377,7 +377,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute5
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalCustomAttribute5 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute5 property. You can specify multiple values separated by commas.
 
@@ -401,7 +401,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute6
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalCustomAttribute6 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute6 property. You can specify multiple values separated by commas.
 
@@ -425,7 +425,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute7
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalCustomAttribute7 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute7 property. You can specify multiple values separated by commas.
 
@@ -449,7 +449,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute8
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalCustomAttribute8 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute8 property. You can specify multiple values separated by commas.
 
@@ -473,7 +473,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute9
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalCustomAttribute9 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute9 property. You can specify multiple values separated by commas.
 
@@ -497,7 +497,7 @@ Accept wildcard characters: False
 
 ### -ConditionalDepartment
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalDepartment parameter specifies a precanned filter that's based on the value of the recipient's Department property. You can specify multiple values separated by commas.
 
@@ -521,7 +521,7 @@ Accept wildcard characters: False
 
 ### -ConditionalStateOrProvince
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalStateOrProvince parameter specifies a precanned filter that's based on the value of the recipient's StateOrProvince property. You can specify multiple values separated by commas.
 
@@ -545,7 +545,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -566,7 +566,7 @@ Accept wildcard characters: False
 
 ### -DisplayName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DisplayName parameter specifies the display name of the group. The display name is visible in the Exchange admin center and in Outlook. The maximum length is 256 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -584,7 +584,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -604,7 +604,7 @@ Accept wildcard characters: False
 
 ### -ForceUpgrade
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -624,7 +624,7 @@ Accept wildcard characters: False
 
 ### -IncludedRecipients
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IncludedRecipients parameter specifies a precanned filter that's based on the recipient type. Valid values are:
 
@@ -651,7 +651,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Name parameter specifies a unique name for the address list. The maximum length is 64 characters, and it can't include a carriage return or a backslash (\\). If the value contains spaces, enclose the value in quotation marks (").
 
@@ -669,7 +669,7 @@ Accept wildcard characters: False
 
 ### -RecipientContainer
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -696,7 +696,7 @@ Accept wildcard characters: False
 
 ### -RecipientFilter
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RecipientFilter parameter specifies a custom OPATH filter that's based on the value of any available recipient property. You can use any available Windows PowerShell operator, and wildcards and partial matches are supported. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`.
 
@@ -723,7 +723,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AddressRewriteEntry.md b/exchange/exchange-ps/ExchangePowerShell/Set-AddressRewriteEntry.md
index 10e8fe26ff..8fef843742 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-AddressRewriteEntry.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-AddressRewriteEntry.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
 Locale: en-US
@@ -61,7 +61,7 @@ This example changes the existing address rewrite entry named "Address entry for
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the address rewrite entry you want to modify. You can specify the name or GUID of the address rewrite entry.
 
@@ -79,7 +79,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -100,7 +100,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -120,7 +120,7 @@ Accept wildcard characters: False
 
 ### -ExceptionList
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExceptionList parameter specifies the domain names that should be excluded from address rewriting when the InternalAddress parameter contains a value that specifies multiple domain names. You can separate multiple domain names included with the ExceptionList parameter with commas. For more information about how to add values to or remove values from multivalued properties, see [Modifying multivalued properties](https://learn.microsoft.com/exchange/modifying-multivalued-properties-exchange-2013-help).
 
@@ -138,7 +138,7 @@ Accept wildcard characters: False
 
 ### -ExternalAddress
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExternalAddress parameter specifies the final email addresses that you want. If the InternalAddress parameter specifies a single email address (chris@contoso.com), the ExternalAddress parameter must also specify a single email address (support@contoso.com). If the InternalAddress parameter specifies a single domain (contoso.com) or a domain and all subdomains (\*.contoso.com), the ExternalAddress parameter must specify a single domain (fabrikam.com).
 
@@ -158,7 +158,7 @@ Accept wildcard characters: False
 
 ### -InternalAddress
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The InternalAddress parameter specifies the original email addresses that you want to change. You can use the following values:
 
@@ -180,7 +180,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Name parameter specifies a unique name for this address rewrite entry.
 
@@ -198,7 +198,7 @@ Accept wildcard characters: False
 
 ### -OutboundOnly
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The OutboundOnly parameter enables or disables outbound-only address rewriting. Valid input for this parameter is $true or $false. The value $true means address rewriting occurs in outbound mail only. The value $false means address rewriting occurs on outbound mail and also on inbound mail (rewritten email addresses are changed back to the original email addresses in inbound mail). The default value is $false.
 
@@ -220,7 +220,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AdminAuditLogConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-AdminAuditLogConfig.md
index 42c5b5bdfa..0a6ed0dac7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-AdminAuditLogConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-AdminAuditLogConfig.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
 Locale: en-US
@@ -77,7 +77,7 @@ This example enables administrator audit logging only for specific parameters th
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -97,7 +97,7 @@ Accept wildcard characters: False
 
 ### -AdminAuditLogAgeLimit
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -125,7 +125,7 @@ Accept wildcard characters: False
 
 ### -AdminAuditLogCmdlets
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -145,7 +145,7 @@ Accept wildcard characters: False
 
 ### -AdminAuditLogEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -172,7 +172,7 @@ Accept wildcard characters: False
 
 ### -AdminAuditLogExcludedCmdlets
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -196,7 +196,7 @@ Accept wildcard characters: False
 
 ### -AdminAuditLogParameters
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -216,7 +216,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -236,7 +236,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -256,7 +256,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -275,7 +275,7 @@ Accept wildcard characters: False
 
 ### -LogLevel
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -298,7 +298,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -320,7 +320,7 @@ Accept wildcard characters: False
 
 ### -TestCmdletLoggingEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -345,7 +345,7 @@ Accept wildcard characters: False
 
 ### -UnifiedAuditLogIngestionEnabled
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter is functional only in the cloud-based service.
 
@@ -367,7 +367,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-App.md b/exchange/exchange-ps/ExchangePowerShell/Set-App.md
index 4fe9357f89..ac6e743d11 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-App.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-App.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.WebClient-Help.xml
 Locale: en-US
@@ -66,7 +66,7 @@ This example disables the organization app named FinanceTestApp across the organ
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the AppID (GUID value) of the app that you want to modify. To find the GUID value of an app, run the command Get-App | Format-Table -Auto DisplayName,AppId.
 
@@ -84,7 +84,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -105,7 +105,7 @@ Accept wildcard characters: False
 
 ### -DefaultStateForUser
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DefaultStateForUser parameter specifies the default initial state of the organization app for the specified users. Valid values are:
 
@@ -129,7 +129,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -149,7 +149,7 @@ Accept wildcard characters: False
 
 ### -Enabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Enabled parameter specifies whether the app is available to users in the organization. Valid values are:
 
@@ -172,7 +172,7 @@ Accept wildcard characters: False
 
 ### -OrganizationApp
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The OrganizationApp switch specifies that the scope of the app is organizational (not bound to a specific user). You don't need to specify a value with this switch.
 
@@ -190,7 +190,7 @@ Accept wildcard characters: False
 
 ### -PrivateCatalog
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The PrivateCatalog switch specifies that the app you want to modify is located in a private catalog. You don't need to specify a value with this switch.
 
@@ -208,7 +208,7 @@ Accept wildcard characters: False
 
 ### -ProvidedTo
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ProvidedTo parameter specifies the availability of the app in your organization. Valid value are:
 
@@ -231,7 +231,7 @@ Accept wildcard characters: False
 
 ### -UserList
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The UserList parameter specifies who can use an organizational app. This parameter is limited to 1000 users. In the cloud-based service, this value is less relevant as Office Add-in management is moving to [Centralized Deployment](https://learn.microsoft.com/office/dev/add-ins/publish/centralized-deployment).
 
@@ -266,7 +266,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AttachmentFilterListConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-AttachmentFilterListConfig.md
index 40c8190235..87b10a0fa8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-AttachmentFilterListConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-AttachmentFilterListConfig.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
 Locale: en-US
@@ -51,7 +51,7 @@ This example modifies the action that the Attachment Filtering agent takes on an
 
 ### -Action
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Action parameter specifies how the Attachment Filtering agent handles an attachment that matches an entry on the attachment filter list. Valid values are:
 
@@ -73,7 +73,7 @@ Accept wildcard characters: False
 
 ### -AdminMessage
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AdminMessage parameter specifies the content of a text file that replaces attachments removed by the Attachment Filtering agent. The AdminMessage parameter only appears when the Attachment Filtering agent is configured to remove an attachment that's been identified as bad.
 
@@ -91,7 +91,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -112,7 +112,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -132,7 +132,7 @@ Accept wildcard characters: False
 
 ### -ExceptionConnectors
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExceptionConnectors parameter specifies a list of connectors that should be excluded from attachment filtering. Attachment filters aren't applied to email messages received through these connectors. You must use the connector GUID to specify the ExceptionConnectors parameter value.
 
@@ -150,7 +150,7 @@ Accept wildcard characters: False
 
 ### -RejectResponse
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RejectResponse parameter specifies the message body that you want delivered in the NDR to senders whose messages contain an attachment that's blocked. The RejectResponse parameter is required only if you set the Action parameter to Reject. Don't exceed 240 characters in the parameter argument. When you pass an argument, you must enclose the RejectResponse parameter value in quotation marks (") if the phrase contains spaces, for example: "Message rejected". The default setting is Message rejected due to unacceptable attachments.
 
@@ -168,7 +168,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 

From c82edf6bf5c3422612c36d4a4e807d28d34d6288 Mon Sep 17 00:00:00 2001
From: Chris Davis <chris.davis@microsoft.com>
Date: Thu, 7 Aug 2025 14:44:48 -0700
Subject: [PATCH 134/145] Add Exchange Server SE 7

---
 .../ExchangePowerShell/Set-AuthConfig.md      |  28 +-
 .../ExchangePowerShell/Set-AuthRedirect.md    |  12 +-
 .../ExchangePowerShell/Set-AuthServer.md      |  26 +-
 .../Set-AuthenticationPolicy.md               |  40 +-
 .../Set-AutodiscoverVirtualDirectory.md       |  26 +-
 .../Set-AvailabilityConfig.md                 |  12 +-
 .../ExchangePowerShell/Set-CASMailbox.md      | 100 ++---
 .../Set-CalendarNotification.md               |  26 +-
 .../Set-CalendarProcessing.md                 |  76 ++--
 .../Set-ClassificationRuleCollection.md       |  10 +-
 .../Set-ClientAccessRule.md                   |  32 +-
 .../Set-ClientAccessServer.md                 |  22 +-
 .../Set-ClientAccessService.md                |  22 +-
 .../Set-CmdletExtensionAgent.md               |  14 +-
 .../Set-ComplianceSearch.md                   |  32 +-
 .../Set-ComplianceSearchAction.md             |  10 +-
 .../Set-ComplianceSecurityFilter.md           |  18 +-
 .../ExchangePowerShell/Set-Contact.md         |  86 ++---
 .../Set-ContentFilterConfig.md                |  38 +-
 .../Set-DataClassification.md                 |  20 +-
 .../Set-DatabaseAvailabilityGroup.md          |  70 ++--
 .../Set-DatabaseAvailabilityGroupNetwork.md   |  20 +-
 .../Set-DeliveryAgentConnector.md             |  32 +-
 .../ExchangePowerShell/Set-DetailsTemplate.md |  12 +-
 .../Set-DistributionGroup.md                  | 134 +++----
 .../ExchangePowerShell/Set-DlpPolicy.md       |  18 +-
 .../Set-DynamicDistributionGroup.md           | 166 ++++----
 .../Set-EcpVirtualDirectory.md                |  40 +-
 .../Set-EdgeSyncServiceConfig.md              |  38 +-
 .../Set-EmailAddressPolicy.md                 |  64 ++--
 .../ExchangePowerShell/Set-EventLogLevel.md   |  10 +-
 .../Set-ExchangeAssistanceConfig.md           |  44 +--
 .../ExchangePowerShell/Set-ExchangeFeature.md |  14 +-
 .../ExchangePowerShell/Set-ExchangeServer.md  |  40 +-
 .../Set-ExchangeSettings.md                   |  62 +--
 .../Set-FederatedOrganizationIdentifier.md    |  20 +-
 .../ExchangePowerShell/Set-FederationTrust.md |  22 +-
 .../Set-ForeignConnector.md                   |  32 +-
 .../Set-FrontendTransportService.md           |  90 ++---
 .../Set-GlobalAddressList.md                  |  56 +--
 .../ExchangePowerShell/Set-Group.md           |  34 +-
 .../Set-HybridConfiguration.md                |  30 +-
 .../Set-IPAllowListConfig.md                  |  14 +-
 .../Set-IPAllowListProvider.md                |  24 +-
 .../Set-IPAllowListProvidersConfig.md         |  14 +-
 .../Set-IPBlockListConfig.md                  |  18 +-
 .../Set-IPBlockListProvider.md                |  26 +-
 .../Set-IPBlockListProvidersConfig.md         |  16 +-
 .../Set-IRMConfiguration.md                   |  28 +-
 .../ExchangePowerShell/Set-ImapSettings.md    |  64 ++--
 .../ExchangePowerShell/Set-InboxRule.md       | 140 +++----
 .../Set-IntraOrganizationConnector.md         |  16 +-
 .../ExchangePowerShell/Set-JournalRule.md     |  22 +-
 .../ExchangePowerShell/Set-MailContact.md     | 132 +++----
 .../Set-MailPublicFolder.md                   | 118 +++---
 .../ExchangePowerShell/Set-MailUser.md        | 154 ++++----
 .../ExchangePowerShell/Set-Mailbox.md         | 362 +++++++++---------
 .../Set-MailboxAuditBypassAssociation.md      |  12 +-
 .../Set-MailboxAutoReplyConfiguration.md      |  38 +-
 .../Set-MailboxCalendarConfiguration.md       |  44 +--
 .../Set-MailboxCalendarFolder.md              |  26 +-
 .../ExchangePowerShell/Set-MailboxDatabase.md |  74 ++--
 .../Set-MailboxDatabaseCopy.md                |  20 +-
 .../Set-MailboxExportRequest.md               |  34 +-
 .../Set-MailboxFolderPermission.md            |  14 +-
 .../Set-MailboxImportRequest.md               |  30 +-
 .../Set-MailboxJunkEmailConfiguration.md      |  24 +-
 .../Set-MailboxMessageConfiguration.md        |  86 ++---
 .../Set-MailboxRegionalConfiguration.md       |  20 +-
 .../Set-MailboxRestoreRequest.md              |  32 +-
 .../ExchangePowerShell/Set-MailboxSearch.md   |  56 +--
 .../ExchangePowerShell/Set-MailboxServer.md   |  82 ++--
 .../Set-MailboxSpellingConfiguration.md       |  18 +-
 .../Set-MailboxTransportService.md            |  90 ++---
 .../Set-MalwareFilterPolicy.md                |  48 +--
 .../Set-MalwareFilterRule.md                  |  30 +-
 .../Set-MalwareFilteringServer.md             |  32 +-
 .../Set-ManagedFolderMailboxPolicy.md         |   8 +-
 .../Set-ManagementRoleAssignment.md           |  26 +-
 .../Set-ManagementRoleEntry.md                |  18 +-
 .../ExchangePowerShell/Set-ManagementScope.md |  20 +-
 .../Set-MapiVirtualDirectory.md               |  24 +-
 .../Set-MessageClassification.md              |  26 +-
 .../ExchangePowerShell/Set-MigrationBatch.md  |  44 +--
 .../ExchangePowerShell/Set-MigrationConfig.md |  14 +-
 .../Set-MigrationEndpoint.md                  |  20 +-
 .../ExchangePowerShell/Set-MigrationUser.md   |  16 +-
 .../Set-MobileDeviceMailboxPolicy.md          | 114 +++---
 .../ExchangePowerShell/Set-MoveRequest.md     |  52 +--
 .../ExchangePowerShell/Set-Notification.md    |  14 +-
 .../Set-OabVirtualDirectory.md                |  30 +-
 .../Set-OfflineAddressBook.md                 |  50 +--
 .../Set-OrganizationConfig.md                 | 170 ++++----
 .../Set-OrganizationRelationship.md           |  48 +--
 .../ExchangePowerShell/Set-OutlookAnywhere.md |  36 +-
 .../Set-OutlookProtectionRule.md              |  26 +-
 .../ExchangePowerShell/Set-OutlookProvider.md |  22 +-
 97 files changed, 2219 insertions(+), 2215 deletions(-)

diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AuthConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-AuthConfig.md
index 8bdf7d268b..08daf7b0f5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-AuthConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-AuthConfig.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -92,7 +92,7 @@ This example immediately rolls over the certificate configured as the next certi
 
 ### -CertificateThumbprint
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The CertificateThumbprint parameter specifies the thumbprint of the certificate to be used by Exchange for server-to-server authentication.
 
@@ -110,7 +110,7 @@ Accept wildcard characters: False
 
 ### -ClearPreviousCertificate
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ClearPreviousCertificate switch clears the certificate that was saved as the previous certificate in the authorization configuration. You don't need to specify a value with this switch.
 
@@ -128,7 +128,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -149,7 +149,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -167,7 +167,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -187,7 +187,7 @@ Accept wildcard characters: False
 
 ### -NewCertificateEffectiveDate
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The NewCertificateEffectiveDate parameter specifies a date when the certificate configured as the next certificate should be used.
 
@@ -205,7 +205,7 @@ Accept wildcard characters: False
 
 ### -NewCertificateThumbprint
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The NewCertificateThumbprint parameter specifies the thumbprint of the new certificate to be used as the next certificate in the authorization configuration.
 
@@ -223,7 +223,7 @@ Accept wildcard characters: False
 
 ### -PublishCertificate
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PublishCertificate switch immediately rolls over the specified certificate as the current certificate. You don't need to specify a value with this switch.
 
@@ -243,7 +243,7 @@ Accept wildcard characters: False
 
 ### -Realm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Realm parameter specifies a security realm for partner applications. If a service or user presents a token from a domain that's not an accepted domain in the Exchange organization, the token must contain the specified realm to gain access to resources.
 
@@ -261,7 +261,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter isn't available in this release.
 
@@ -279,7 +279,7 @@ Accept wildcard characters: False
 
 ### -ServiceName
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ServiceName parameter identifies Microsoft Exchange to other partner applications such as SharePoint 2013.
 
@@ -299,7 +299,7 @@ Accept wildcard characters: False
 
 ### -SkipImmediateCertificateDeployment
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SkipImmediateCertificateDeployment switch specifies that the certificate shouldn't be used immediately. You don't need to specify a value with this switch.
 
@@ -319,7 +319,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AuthRedirect.md b/exchange/exchange-ps/ExchangePowerShell/Set-AuthRedirect.md
index f23fcfa6f2..0629cf6d1d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-AuthRedirect.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-AuthRedirect.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -53,7 +53,7 @@ This example sets the TargetURL value for all existing OAuth redirection objects
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the existing OAuth redirection object that you want to modify. The object name uses the syntax `AuthRedirect-Bearer-GUID`. The easiest way to find the name of the OAuth redirection object is to run Get-AuthRedirect.
 
@@ -71,7 +71,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -92,7 +92,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -110,7 +110,7 @@ Accept wildcard characters: False
 
 ### -TargetUrl
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TargetUrl parameter specifies the FQDN of the Exchange 2013 Client Access server that processes the Oauth request.
 
@@ -128,7 +128,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AuthServer.md b/exchange/exchange-ps/ExchangePowerShell/Set-AuthServer.md
index 5419f5f7de..ad946cfe01 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-AuthServer.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-AuthServer.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -96,7 +96,7 @@ This command disables the authorization server ACS.
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the authorization server object that you want to modify. You can use any value that uniquely identifies the authorization server. For example:
 
@@ -118,7 +118,7 @@ Accept wildcard characters: False
 
 ### -ApplicationIdentifier
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available in the April 18, 2025 Hotfix update (HU) for Exchange 2019 CU15 and Exchange 2016 CU23.
 
@@ -138,7 +138,7 @@ Accept wildcard characters: False
 
 ### -AuthMetadataUrl
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AuthMetadataUrl parameter specifies the URL of the authorization server. This can be the AuthMetadataUrl of your Exchange Online organization.
 
@@ -156,7 +156,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -177,7 +177,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -195,7 +195,7 @@ Accept wildcard characters: False
 
 ### -DomainName
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in Exchange Server 2016 (CU18 or higher) and Exchange Server 2019 (CU7 or higher).
 
@@ -217,7 +217,7 @@ Accept wildcard characters: False
 
 ### -Enabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Enabled parameter specifies whether the authorization server is enabled. Only enabled authorization servers can issue and accept tokens. Disabling the authorization server prevents any partner applications configured to use the authorization server from getting a token.
 
@@ -240,7 +240,7 @@ Accept wildcard characters: False
 
 ### -IsDefaultAuthorizationEndpoint
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IsDefaultAuthorizationEndpoint parameter specifies whether this server is the default authorization endpoint. Valid values are:
 
@@ -262,7 +262,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Name parameter specifies a unique name for the authorization server object. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -280,7 +280,7 @@ Accept wildcard characters: False
 
 ### -RefreshAuthMetadata
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RefreshAuthMetadata switch specifies whether Exchange should refresh the auth metadata from the specified URL. You don't need to specify a value with this switch.
 
@@ -298,7 +298,7 @@ Accept wildcard characters: False
 
 ### -TrustAnySSLCertificate
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TrustAnySSLCertificate switch allows Exchange to accept certificates from untrusted certification authorities (CAs). You don't need to specify a value with this switch.
 
@@ -318,7 +318,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AuthenticationPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-AuthenticationPolicy.md
index cf7790c298..41d628b916 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-AuthenticationPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-AuthenticationPolicy.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -89,7 +89,7 @@ In Exchange Online, this example blocks legacy Exchange tokens from being issued
 
 ### -Identity
 
-> Applicable: Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the authentication policy you want to modify. You can use any value that uniquely identifies the policy. For example:
 
@@ -417,7 +417,7 @@ Accept wildcard characters: False
 
 ### -BlockLegacyAuthActiveSync
 
-> Applicable: Exchange Server 2019
+> Applicable: Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -440,7 +440,7 @@ Accept wildcard characters: False
 
 ### -BlockLegacyAuthAutodiscover
 
-> Applicable: Exchange Server 2019
+> Applicable: Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -463,7 +463,7 @@ Accept wildcard characters: False
 
 ### -BlockLegacyAuthImap
 
-> Applicable: Exchange Server 2019
+> Applicable: Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -486,7 +486,7 @@ Accept wildcard characters: False
 
 ### -BlockLegacyAuthMapi
 
-> Applicable: Exchange Server 2019
+> Applicable: Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -509,7 +509,7 @@ Accept wildcard characters: False
 
 ### -BlockLegacyAuthOfflineAddressBook
 
-> Applicable: Exchange Server 2019
+> Applicable: Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -532,7 +532,7 @@ Accept wildcard characters: False
 
 ### -BlockLegacyAuthPop
 
-> Applicable: Exchange Server 2019
+> Applicable: Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -555,7 +555,7 @@ Accept wildcard characters: False
 
 ### -BlockLegacyAuthRpc
 
-> Applicable: Exchange Server 2019
+> Applicable: Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -578,7 +578,7 @@ Accept wildcard characters: False
 
 ### -BlockLegacyAuthWebServices
 
-> Applicable: Exchange Server 2019
+> Applicable: Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -633,7 +633,7 @@ Accept wildcard characters: False
 
 ### -BlockModernAuthActiveSync
 
-> Applicable: Exchange Server 2019
+> Applicable: Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -653,7 +653,7 @@ Accept wildcard characters: False
 
 ### -BlockModernAuthAutodiscover
 
-> Applicable: Exchange Server 2019
+> Applicable: Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -673,7 +673,7 @@ Accept wildcard characters: False
 
 ### -BlockModernAuthImap
 
-> Applicable: Exchange Server 2019
+> Applicable: Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -693,7 +693,7 @@ Accept wildcard characters: False
 
 ### -BlockModernAuthMapi
 
-> Applicable: Exchange Server 2019
+> Applicable: Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -713,7 +713,7 @@ Accept wildcard characters: False
 
 ### -BlockModernAuthOfflineAddressBook
 
-> Applicable: Exchange Server 2019
+> Applicable: Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -733,7 +733,7 @@ Accept wildcard characters: False
 
 ### -BlockModernAuthPop
 
-> Applicable: Exchange Server 2019
+> Applicable: Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -753,7 +753,7 @@ Accept wildcard characters: False
 
 ### -BlockModernAuthRpc
 
-> Applicable: Exchange Server 2019
+> Applicable: Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -773,7 +773,7 @@ Accept wildcard characters: False
 
 ### -BlockModernAuthWebServices
 
-> Applicable: Exchange Server 2019
+> Applicable: Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -793,7 +793,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -834,7 +834,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AutodiscoverVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Set-AutodiscoverVirtualDirectory.md
index ca01c30e74..1691eb2ac3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-AutodiscoverVirtualDirectory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-AutodiscoverVirtualDirectory.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -69,7 +69,7 @@ This example sets Integrated Windows authentication for the Autodiscover virtual
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the Autodiscover virtual directory that you want to modify. You can use any value that uniquely identifies the virtual directory. For example:
 
@@ -93,7 +93,7 @@ Accept wildcard characters: False
 
 ### -BasicAuthentication
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The BasicAuthentication parameter specifies whether Basic authentication is enabled on the virtual directory. Valid values are:
 
@@ -114,7 +114,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -135,7 +135,7 @@ Accept wildcard characters: False
 
 ### -DigestAuthentication
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DigestAuthentication parameter specifies whether Digest authentication is enabled on the virtual directory. Valid values are:
 
@@ -156,7 +156,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -174,7 +174,7 @@ Accept wildcard characters: False
 
 ### -ExtendedProtectionFlags
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExtendedProtectionFlags parameter specifies custom settings for Extended Protection for Authentication on the virtual directory. Valid values are:
 
@@ -198,7 +198,7 @@ Accept wildcard characters: False
 
 ### -ExtendedProtectionSPNList
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExtendedProtectionSPNList parameter specifies a list of valid Service Principal Names (SPNs) if you're using Extended Protection for Authentication on the virtual directory. Valid values are:
 
@@ -219,7 +219,7 @@ Accept wildcard characters: False
 
 ### -ExtendedProtectionTokenChecking
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExtendedProtectionTokenChecking parameter defines how you want to use Extended Protection for Authentication on the virtual directory. Extended Protection for Authentication isn't enabled by default. Valid values are:
 
@@ -283,7 +283,7 @@ Accept wildcard characters: False
 
 ### -OAuthAuthentication
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The OAuthAuthentication parameter specifies whether OAuth authentication is enabled on the virtual directory. Valid values are:
 
@@ -304,7 +304,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
@@ -322,7 +322,7 @@ Accept wildcard characters: False
 
 ### -WindowsAuthentication
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WindowsAuthentication parameter specifies whether Integrated Windows authentication is enabled on the virtual directory. Valid values are:
 
@@ -343,7 +343,7 @@ Accept wildcard characters: False
 
 ### -WSSecurityAuthentication
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WSSecurityAuthentication parameter specifies whether WS-Security (Web Services Security) authentication is enabled on the virtual directory. Valid values are:
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AvailabilityConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-AvailabilityConfig.md
index 1eb3727049..dad6108eeb 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-AvailabilityConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-AvailabilityConfig.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
 Locale: en-US
@@ -92,7 +92,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -113,7 +113,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -133,7 +133,7 @@ Accept wildcard characters: False
 
 ### -OrgWideAccount
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is functional only in on-premises Exchange.
 
@@ -170,7 +170,7 @@ Accept wildcard characters: False
 
 ### -PerUserAccount
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -203,7 +203,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-CASMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Set-CASMailbox.md
index e4545c1e31..07ac50c1d5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-CASMailbox.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-CASMailbox.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.WebClient-Help.xml
 Locale: en-US
@@ -110,7 +110,7 @@ This example sets the display name and disables Outlook Anywhere access for the
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the mailbox that you want to configure. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -139,7 +139,7 @@ Accept wildcard characters: False
 
 ### -ActiveSyncAllowedDeviceIDs
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 TheActiveSyncAllowedDeviceIDs parameter specifies one or more Exchange ActiveSync device IDs that are allowed to synchronize with the mailbox. A device ID is a text string that uniquely identifies the device. Use the Get-MobileDevice cmdlet to see the devices that have Exchange ActiveSync partnerships with the mailbox.
 
@@ -163,7 +163,7 @@ Accept wildcard characters: False
 
 ### -ActiveSyncBlockedDeviceIDs
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ActiveSyncBlockedDeviceIDs parameter specifies one or more Exchange ActiveSync device IDs that aren't allowed to synchronize with the mailbox. A device ID is a text string that uniquely identifies the device. Use the Get-MobileDevice cmdlet to see the devices that have Exchange ActiveSync partnerships with the mailbox.
 
@@ -187,7 +187,7 @@ Accept wildcard characters: False
 
 ### -ActiveSyncDebugLogging
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ActiveSyncDebugLogging parameter enables or disables Exchange ActiveSync debug logging for the mailbox. Valid values are:
 
@@ -208,7 +208,7 @@ Accept wildcard characters: False
 
 ### -ActiveSyncEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ActiveSyncEnabled parameter enables or disables access to the mailbox using Exchange ActiveSync. Valid values are:
 
@@ -231,7 +231,7 @@ Accept wildcard characters: False
 
 ### -ActiveSyncMailboxPolicy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ActiveSyncMailboxPolicy parameter specifies the Exchange ActiveSync mailbox policy for the mailbox. You can use any value that uniquely identifies the Exchange ActiveSync mailbox policy. For example:
 
@@ -255,7 +255,7 @@ Accept wildcard characters: False
 
 ### -ActiveSyncSuppressReadReceipt
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ActiveSyncSuppressReadReceipt parameter controls the behavior of read receipts for Exchange ActiveSync clients that access the mailbox. Valid values are:
 
@@ -276,7 +276,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -297,7 +297,7 @@ Accept wildcard characters: False
 
 ### -DisplayName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -317,7 +317,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -337,7 +337,7 @@ Accept wildcard characters: False
 
 ### -ECPEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -360,7 +360,7 @@ Accept wildcard characters: False
 
 ### -EmailAddresses
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -399,7 +399,7 @@ Accept wildcard characters: False
 
 ### -EwsAllowEntourage
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The EwsAllowEntourage parameter enables or disables access to the mailbox by Microsoft Entourage clients that use Exchange Web Services (for example, Entourage 2008 for Mac, Web Services Edition).
 
@@ -420,7 +420,7 @@ Accept wildcard characters: False
 
 ### -EwsAllowList
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The EwsAllowList parameter specifies the Exchange Web Services applications (user agent strings) that are allowed to access the mailbox.
 
@@ -444,7 +444,7 @@ Accept wildcard characters: False
 
 ### -EwsAllowMacOutlook
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The EwsAllowMacOutlook parameter enables or disables access to the mailbox by Outlook for Mac clients that use Exchange Web Services (for example, Outlook for Mac 2011 or later). Valid values are:
 
@@ -467,7 +467,7 @@ Accept wildcard characters: False
 
 ### -EwsAllowOutlook
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The EwsAllowOutlook parameter enables or disables access to the mailbox by Outlook clients that use Exchange Web Services. Outlook uses Exchange Web Services for free/busy, out-of-office settings, and calendar sharing. Valid values are:
 
@@ -488,7 +488,7 @@ Accept wildcard characters: False
 
 ### -EwsApplicationAccessPolicy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The EwsApplicationAccessPolicy parameter controls access to the mailbox using Exchange Web Services applications.
 
@@ -513,7 +513,7 @@ Accept wildcard characters: False
 
 ### -EwsBlockList
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The EwsBlockList parameter specifies the Exchange Web Services applications (user agent strings) that aren't allowed to access the mailbox using Exchange Web Services.
 
@@ -537,7 +537,7 @@ Accept wildcard characters: False
 
 ### -EwsEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The EwsEnabled parameter enables or disables access to the mailbox using Exchange Web Services clients. Valid values are:
 
@@ -583,7 +583,7 @@ Accept wildcard characters: False
 
 ### -IgnoreDefaultScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -608,7 +608,7 @@ Accept wildcard characters: False
 
 ### -ImapEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ImapEnabled parameter enables or disables access to the mailbox using IMAP4 clients. Valid values are:
 
@@ -631,7 +631,7 @@ Accept wildcard characters: False
 
 ### -ImapEnableExactRFC822Size
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -656,7 +656,7 @@ Accept wildcard characters: False
 
 ### -ImapForceICalForCalendarRetrievalOption
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ImapForceICalForCalendarRetrievalOption parameter specifies how meeting requests are presented to IMAP4 clients that access the mailbox. Valid values are:
 
@@ -679,7 +679,7 @@ Accept wildcard characters: False
 
 ### -ImapMessagesRetrievalMimeFormat
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ImapMessagesRetrievalMimeFormat parameter specifies the message format for IMAP4 clients that access the mailbox. You can use an integer or a text value. Valid values are:
 
@@ -707,7 +707,7 @@ Accept wildcard characters: False
 
 ### -ImapSuppressReadReceipt
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ImapSuppressReadReceipt parameter controls the behavior of read receipts for IMAP4 clients that access the mailbox. Valid values are:
 
@@ -730,7 +730,7 @@ Accept wildcard characters: False
 
 ### -ImapUseProtocolDefaults
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ImapUseProtocolDefaults parameter specifies whether to use the IMAP4 protocol defaults for the mailbox. Valid values are:
 
@@ -758,7 +758,7 @@ Accept wildcard characters: False
 
 ### -IsOptimizedForAccessibility
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is functional only in on-premises Exchange.
 
@@ -806,7 +806,7 @@ Accept wildcard characters: False
 
 ### -MAPIBlockOutlookNonCachedMode
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -829,7 +829,7 @@ Accept wildcard characters: False
 
 ### -MAPIBlockOutlookExternalConnectivity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -854,7 +854,7 @@ Accept wildcard characters: False
 
 ### -MAPIBlockOutlookRpcHttp
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -877,7 +877,7 @@ Accept wildcard characters: False
 
 ### -MAPIBlockOutlookVersions
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -901,7 +901,7 @@ Accept wildcard characters: False
 
 ### -MAPIEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MAPIEnabled parameter enables or disables access to the mailbox using MAPI clients (for example, Outlook). Valid values are:
 
@@ -924,7 +924,7 @@ Accept wildcard characters: False
 
 ### -MapiHttpEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -948,7 +948,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1015,7 +1015,7 @@ Accept wildcard characters: False
 
 ### -OWAEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The OWAEnabled parameter enables or disables access to the mailbox using Outlook on the web (formerly known as Outlook Web App or OWA) and the new Outlook for Windows. Valid values are:
 
@@ -1038,7 +1038,7 @@ Accept wildcard characters: False
 
 ### -OWAforDevicesEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The OWAforDevicesEnabled parameter enables or disables access to the mailbox using the older Outlook Web App (OWA) app on iOS and Android devices. Valid values are:
 
@@ -1059,7 +1059,7 @@ Accept wildcard characters: False
 
 ### -OwaMailboxPolicy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The OwaMailboxPolicy parameter specifies the Outlook on the web mailbox policy for the mailbox. You can use any value that uniquely identifies the Outlook on the web mailbox policy. For example:
 
@@ -1083,7 +1083,7 @@ Accept wildcard characters: False
 
 ### -PopEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The PopEnabled parameter enables or disables access to the mailbox using POP3 clients. Valid values are:
 
@@ -1106,7 +1106,7 @@ Accept wildcard characters: False
 
 ### -PopEnableExactRFC822Size
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1131,7 +1131,7 @@ Accept wildcard characters: False
 
 ### -PopForceICalForCalendarRetrievalOption
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The PopForceICalForCalendarRetrievalOption parameter specifies how meeting requests are presented to POP3 clients that access the mailbox. Valid values are:
 
@@ -1154,7 +1154,7 @@ Accept wildcard characters: False
 
 ### -PopMessagesRetrievalMimeFormat
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The PopMessagesRetrievalMimeFormat parameter specifies the message format for POP3 clients that access the mailbox. You can use an integer or a text value. Valid values are:
 
@@ -1182,7 +1182,7 @@ Accept wildcard characters: False
 
 ### -PopSuppressReadReceipt
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The PopSuppressReadReceipt parameter controls the behavior of read receipts for POP3 clients that access the mailbox. Valid values are:
 
@@ -1205,7 +1205,7 @@ Accept wildcard characters: False
 
 ### -PopUseProtocolDefaults
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The PopUseProtocolDefaults parameter specifies whether to use the POP3 protocol defaults for the mailbox. Valid values are:
 
@@ -1233,7 +1233,7 @@ Accept wildcard characters: False
 
 ### -PrimarySmtpAddress
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1253,7 +1253,7 @@ Accept wildcard characters: False
 
 ### -PublicFolderClientAccess
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The PublicFolderClientAccess parameter enables or disables access to public folders in Microsoft Outlook. Valid values are:
 
@@ -1274,7 +1274,7 @@ Accept wildcard characters: False
 
 ### -ResetAutoBlockedDevices
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1294,7 +1294,7 @@ Accept wildcard characters: False
 
 ### -SamAccountName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1314,7 +1314,7 @@ Accept wildcard characters: False
 
 ### -ShowGalAsDefaultView
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ShowGalAsDefaultView parameter specifies whether the global address list (GAL) is the default recipient picker for messages. Valid values are:
 
@@ -1391,7 +1391,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-CalendarNotification.md b/exchange/exchange-ps/ExchangePowerShell/Set-CalendarNotification.md
index c20aafc1af..f2b894c1dd 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-CalendarNotification.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-CalendarNotification.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.WebClient-Help.xml
 Locale: en-US
@@ -61,7 +61,7 @@ This example configures the calendar in Tony's mailbox to send the following tex
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the mailbox that you want to modify. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -90,7 +90,7 @@ Accept wildcard characters: False
 
 ### -CalendarUpdateNotification
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The CalendarUpdateNotification parameter specifies whether calendar update text message notifications are sent to the user's mobile device. Valid values are:
 
@@ -111,7 +111,7 @@ Accept wildcard characters: False
 
 ### -CalendarUpdateSendDuringWorkHour
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The CalendarUpdateSendDuringWorkHour parameter specifies whether calendar update text notifications are sent to the user's mobile device during working hours only. Valid values are:
 
@@ -132,7 +132,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -153,7 +153,7 @@ Accept wildcard characters: False
 
 ### -DailyAgendaNotification
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DailyAgendaNotification parameter specifies whether daily agenda text message notifications are sent to the user's mobile device. Valid values are:
 
@@ -174,7 +174,7 @@ Accept wildcard characters: False
 
 ### -DailyAgendaNotificationSendTime
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DailyAgendaNotificationSendTime parameter specifies the time to send daily agenda text message notifications to the user's mobile device.
 
@@ -196,7 +196,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -214,7 +214,7 @@ Accept wildcard characters: False
 
 ### -IgnoreDefaultScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -232,7 +232,7 @@ Accept wildcard characters: False
 
 ### -MeetingReminderNotification
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MeetingReminderNotification parameter specifies whether meeting reminder text message notifications are sent to the user's mobile device. Valid values are:
 
@@ -253,7 +253,7 @@ Accept wildcard characters: False
 
 ### -MeetingReminderSendDuringWorkHour
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MeetingReminderSendDuringWorkHour parameter specifies whether meeting reminder text message notifications are sent to the user's mobile device during working hours only. Valid values are:
 
@@ -274,7 +274,7 @@ Accept wildcard characters: False
 
 ### -NextDays
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The NextDays parameter specifies how many days should be sent in the daily agenda text message notification to the user's mobile device. A valid value is an integer between 1 and 7. The default value is 1.
 
@@ -292,7 +292,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-CalendarProcessing.md b/exchange/exchange-ps/ExchangePowerShell/Set-CalendarProcessing.md
index da0a5b0cfd..2412c29cdc 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-CalendarProcessing.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-CalendarProcessing.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
 Locale: en-US
@@ -158,7 +158,7 @@ This example rejects meeting requests from any user who isn't a member of the Ex
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the resource mailbox that you want to modify. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -187,7 +187,7 @@ Accept wildcard characters: False
 
 ### -AddAdditionalResponse
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AddAdditionalResponse parameter specifies whether additional information (the value of the AdditionalResponse parameter) is added to meeting request responses. Valid values are:
 
@@ -210,7 +210,7 @@ Accept wildcard characters: False
 
 ### -AdditionalResponse
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AdditionalResponse parameter specifies the additional information to be included in responses to meeting requests when the value of the AddAdditionalResponse parameter is $true. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -228,7 +228,7 @@ Accept wildcard characters: False
 
 ### -AddNewRequestsTentatively
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AddNewRequestsTentatively parameter specifies whether new meeting requests are added to the calendar as tentative. Valid values are:
 
@@ -249,7 +249,7 @@ Accept wildcard characters: False
 
 ### -AddOrganizerToSubject
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AddOrganizerToSubject parameter specifies whether the meeting organizer's name is used as the subject of the meeting request. Valid values are:
 
@@ -274,7 +274,7 @@ Accept wildcard characters: False
 
 ### -AllBookInPolicy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllBookInPolicy parameter specifies whether to automatically approve in-policy requests from all users to the resource mailbox. Valid values are:
 
@@ -295,7 +295,7 @@ Accept wildcard characters: False
 
 ### -AllowConflicts
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowConflicts parameter specifies whether to allow conflicting meeting requests. Valid values are:
 
@@ -320,7 +320,7 @@ Accept wildcard characters: False
 
 ### -AllowRecurringMeetings
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowRecurringMeetings parameter specifies whether to allow recurring meetings in meeting requests. Valid values are:
 
@@ -341,7 +341,7 @@ Accept wildcard characters: False
 
 ### -AllRequestInPolicy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllRequestInPolicy parameter specifies whether to allow all users to submit in-policy requests to the resource mailbox. Valid values are:
 
@@ -362,7 +362,7 @@ Accept wildcard characters: False
 
 ### -AllRequestOutOfPolicy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllRequestOutOfPolicy parameter specifies whether to allow all users to submit out-of-policy requests to the resource mailbox. Valid values are:
 
@@ -383,7 +383,7 @@ Accept wildcard characters: False
 
 ### -AutomateProcessing
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AutomateProcessing parameter enables or disables calendar processing on the mailbox. Valid values are:
 
@@ -434,7 +434,7 @@ Accept wildcard characters: False
 
 ### -BookingWindowInDays
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The BookingWindowInDays parameter specifies the maximum number of days in advance that the resource can be reserved. A valid value is an integer from 0 through 1080. The default value is 180 days. The value 0 means today.
 
@@ -452,7 +452,7 @@ Accept wildcard characters: False
 
 ### -BookInPolicy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The BookInPolicy parameter specifies users or groups who are allowed to submit in-policy meeting requests to the resource mailbox that are automatically approved. You can use any value that uniquely identifies the user or group. For example:
 
@@ -485,7 +485,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -506,7 +506,7 @@ Accept wildcard characters: False
 
 ### -ConflictPercentageAllowed
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConflictPercentageAllowed parameter specifies the maximum percentage of meeting conflicts for new recurring meeting requests. A valid value is an integer from 0 through 100. The default value is 0.
 
@@ -526,7 +526,7 @@ Accept wildcard characters: False
 
 ### -DeleteAttachments
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DeleteAttachments parameter specifies whether to remove attachments from all incoming messages. Valid values are:
 
@@ -549,7 +549,7 @@ Accept wildcard characters: False
 
 ### -DeleteComments
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DeleteComments parameter specifies whether to remove or keep any text in the message body of incoming meeting requests. Valid values are:
 
@@ -572,7 +572,7 @@ Accept wildcard characters: False
 
 ### -DeleteNonCalendarItems
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DeleteNonCalendarItems parameter specifies whether to remove or keep all non-calendar-related messages that are received by the resource mailbox. Valid values are:
 
@@ -593,7 +593,7 @@ Accept wildcard characters: False
 
 ### -DeleteSubject
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DeleteSubject parameter specifies whether to remove or keep the subject of incoming meeting requests. Valid values are:
 
@@ -616,7 +616,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -656,7 +656,7 @@ Accept wildcard characters: False
 
 ### -EnableResponseDetails
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The EnableResponseDetails parameter specifies whether to include the reasons for accepting or declining a meeting in the response email message. Valid values are:
 
@@ -700,7 +700,7 @@ Accept wildcard characters: False
 
 ### -EnforceSchedulingHorizon
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The EnforceSchedulingHorizon parameter controls the behavior of recurring meetings that extend beyond the date specified by the BookingWindowInDays parameter. Valid values are:
 
@@ -721,7 +721,7 @@ Accept wildcard characters: False
 
 ### -ForwardRequestsToDelegates
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ForwardRequestsToDelegates parameter specifies whether to forward incoming meeting requests to the delegates that are configured for the resource mailbox. Valid values are:
 
@@ -742,7 +742,7 @@ Accept wildcard characters: False
 
 ### -IgnoreDefaultScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange PowerShell session, and to use the entire forest as the scope. You don't need to specify a value with this switch.
 
@@ -765,7 +765,7 @@ Accept wildcard characters: False
 
 ### -MaximumConflictInstances
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MaximumConflictInstances parameter specifies the maximum number of conflicts for new recurring meeting requests when the AllowRecurringMeetings parameter is set to $true. A valid value is an integer from 0 through INT32 (2147483647). The default value is 0.
 
@@ -785,7 +785,7 @@ Accept wildcard characters: False
 
 ### -MaximumDurationInMinutes
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MaximumDurationInMinutes parameter specifies the maximum duration in minutes for meeting requests. A valid value is an integer from 0 through INT32 (2147483647). The default value is 1440 (24 hours).
 
@@ -829,7 +829,7 @@ Accept wildcard characters: False
 
 ### -OrganizerInfo
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The OrganizerInfo parameter specifies whether the resource mailbox sends organizer information when a meeting request is declined because of conflicts. Valid values are:
 
@@ -870,7 +870,7 @@ Accept wildcard characters: False
 
 ### -ProcessExternalMeetingMessages
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ProcessExternalMeetingMessages parameter specifies whether to process meeting requests that originate outside the Exchange organization. Valid values are:
 
@@ -914,7 +914,7 @@ Accept wildcard characters: False
 
 ### -RemoveForwardedMeetingNotifications
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RemoveForwardedMeetingNotifications parameter specifies whether forwarded meeting notifications are moved to the Deleted Items folder after they're processed by the Calendar Attendant. Valid values are:
 
@@ -935,7 +935,7 @@ Accept wildcard characters: False
 
 ### -RemoveOldMeetingMessages
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RemoveOldMeetingMessages parameter specifies whether the Calendar Attendant removes old and redundant updates and responses. Valid values are:
 
@@ -956,7 +956,7 @@ Accept wildcard characters: False
 
 ### -RemovePrivateProperty
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RemovePrivateProperty parameter specifies whether to clear the private flag for incoming meetings that were sent by the organizer in the original requests. Valid values are:
 
@@ -977,7 +977,7 @@ Accept wildcard characters: False
 
 ### -RequestInPolicy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RequestInPolicy parameter specifies users who are allowed to submit in-policy meeting requests to the resource mailbox that require approval by a resource mailbox delegate. You can use any value that uniquely identifies the user. For example:
 
@@ -1004,7 +1004,7 @@ Accept wildcard characters: False
 
 ### -RequestOutOfPolicy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RequestOutOfPolicy parameter specifies users who are allowed to submit out-of-policy requests that require approval by a resource mailbox delegate. You can use any value that uniquely identifies the user. For example:
 
@@ -1031,7 +1031,7 @@ Accept wildcard characters: False
 
 ### -ResourceDelegates
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ResourceDelegates parameter specifies users can approve or reject requests that are sent to the resource mailbox. You can use any value that uniquely identifies the user. For example:
 
@@ -1058,7 +1058,7 @@ Accept wildcard characters: False
 
 ### -ScheduleOnlyDuringWorkHours
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ScheduleOnlyDuringWorkHours parameter specifies whether to allow meetings to be scheduled outside of the working hours that are defined for the resource mailbox. Valid values are:
 
@@ -1081,7 +1081,7 @@ Accept wildcard characters: False
 
 ### -TentativePendingApproval
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The TentativePendingApproval parameter specifies whether to mark pending requests as tentative on the calendar. Valid values are:
 
@@ -1102,7 +1102,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ClassificationRuleCollection.md b/exchange/exchange-ps/ExchangePowerShell/Set-ClassificationRuleCollection.md
index 53a24290a9..2d0a4b5f89 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ClassificationRuleCollection.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ClassificationRuleCollection.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -47,7 +47,7 @@ This example imports the classification rule collection file C:\\My Documents\\E
 
 ### -FileData
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The FileData parameter specifies the classification rule collection file you want to import.
 
@@ -67,7 +67,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -90,7 +90,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -110,7 +110,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessRule.md
index c608194cb5..35a73dec35 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessRule.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.WebClient-Help.xml
 Locale: en-US
@@ -88,7 +88,7 @@ This example adds the IP address range 172.17.17.27/16 to the existing client ac
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the client access rule that you want to modify. You can use any value that uniquely identifies the client access rule. For example:
 
@@ -110,7 +110,7 @@ Accept wildcard characters: False
 
 ### -Action
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Action parameter specifies the action for the client access rule. Valid values for this parameter are AllowAccess and DenyAccess.
 
@@ -162,7 +162,7 @@ Accept wildcard characters: False
 
 ### -AnyOfClientIPAddressesOrRanges
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The AnyOfClientIPAddressesOrRanges parameter specifies a condition for the client access rule that's based on the client's IPv4 or IPv6 address. Valid values are:
 
@@ -190,7 +190,7 @@ Accept wildcard characters: False
 
 ### -AnyOfProtocols
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The AnyOfProtocols parameter specifies a condition for the client access rule that's based on the client's protocol.
 
@@ -247,7 +247,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -268,7 +268,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -288,7 +288,7 @@ Accept wildcard characters: False
 
 ### -Enabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Enabled parameter specifies whether the client access rule is enabled or disabled. Valid values for this parameter are $true or $false.
 
@@ -340,7 +340,7 @@ Accept wildcard characters: False
 
 ### -ExceptAnyOfClientIPAddressesOrRanges
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ExceptAnyOfClientIPAddressesOrRanges parameter specifies an exception for the client access rule that's based on the client's IPv4 or IPv6 address. Valid values are:
 
@@ -443,7 +443,7 @@ Accept wildcard characters: False
 
 ### -ExceptUsernameMatchesAnyOfPatterns
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter is functional only in the cloud-based service.
 
@@ -467,7 +467,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Name parameter specifies a unique name for the client access rule.
 
@@ -485,7 +485,7 @@ Accept wildcard characters: False
 
 ### -Priority
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Priority parameter specifies a priority value for the client access rule. A lower integer value indicates a higher priority, and a higher priority rule is evaluated before a lower priority rule. The default value is 1.
 
@@ -503,7 +503,7 @@ Accept wildcard characters: False
 
 ### -Scope
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Scope parameter specifies the scope of the client access rule. Valid values are:
 
@@ -542,7 +542,7 @@ Accept wildcard characters: False
 
 ### -UsernameMatchesAnyOfPatterns
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter is functional only in the cloud-based service.
 
@@ -566,7 +566,7 @@ Accept wildcard characters: False
 
 ### -UserRecipientFilter
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter is functional only in the cloud-based service.
 
@@ -617,7 +617,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessServer.md b/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessServer.md
index c508f745f4..0c106a7e10 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessServer.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessServer.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.WebClient-Help.xml
 Locale: en-US
@@ -75,7 +75,7 @@ This example configures the internal Autodiscover URL for the Active Directory s
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the server that you want to modify. You can use any value that uniquely identifies the server. For example:
 
@@ -98,7 +98,7 @@ Accept wildcard characters: False
 
 ### -AlternateServiceAccountCredential
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AlternateServiceAccountCredential parameter specifies an alternative service account username and password that's typically used for Kerberos authentication in Exchange Server 2010 coexistence environments. You can specify multiple values separated by commas.
 
@@ -118,7 +118,7 @@ Accept wildcard characters: False
 
 ### -Array
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -136,7 +136,7 @@ Accept wildcard characters: False
 
 ### -AutoDiscoverServiceInternalUri
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AutoDiscoverServiceInternalUri parameter specifies the internal URL of the Autodiscover service.
 
@@ -154,7 +154,7 @@ Accept wildcard characters: False
 
 ### -AutoDiscoverSiteScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AutoDiscoverSiteScope parameter specifies the Active Directory site that the Autodiscover service is authoritative for. Clients that connect to the Autodiscover service by using the internal URL need to exist in the specified site.
 
@@ -176,7 +176,7 @@ Accept wildcard characters: False
 
 ### -CleanUpInvalidAlternateServiceAccountCredentials
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The CleanUpInvalidAlternateServiceAccountCredentials switch specifies whether to remove a previously configured alternate service account that's no longer valid. You don't need to specify a value with this switch.
 
@@ -194,7 +194,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -215,7 +215,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -384,7 +384,7 @@ Accept wildcard characters: False
 
 ### -RemoveAlternateServiceAccountCredentials
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RemoveAlternateServiceAccountCredentials switch specifies whether to remove a previously distributed alternate service account. You don't need to specify a value with this switch.
 
@@ -402,7 +402,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessService.md b/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessService.md
index 054020ca76..67d8e44f47 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessService.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessService.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.WebClient-Help.xml
 Locale: en-US
@@ -61,7 +61,7 @@ This example configures the internal Autodiscover URL for the Active Directory s
 
 ### -Identity
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the server that you want to modify. You can use any value that uniquely identifies the server. For example:
 
@@ -84,7 +84,7 @@ Accept wildcard characters: False
 
 ### -AlternateServiceAccountCredential
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AlternateServiceAccountCredential parameter specifies an alternative service account that's typically used for Kerberos authentication in Exchange Server 2010 coexistence environments.
 
@@ -104,7 +104,7 @@ Accept wildcard characters: False
 
 ### -Array
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -122,7 +122,7 @@ Accept wildcard characters: False
 
 ### -AutoDiscoverServiceInternalUri
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AutoDiscoverServiceInternalUri parameter specifies the internal URL of the Autodiscover service.
 
@@ -140,7 +140,7 @@ Accept wildcard characters: False
 
 ### -AutoDiscoverSiteScope
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AutoDiscoverSiteScope parameter specifies the Active Directory site that the Autodiscover service is authoritative for. Clients that connect to the Autodiscover service by using the internal URL need to exist in the specified site.
 
@@ -162,7 +162,7 @@ Accept wildcard characters: False
 
 ### -CleanUpInvalidAlternateServiceAccountCredentials
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The CleanUpInvalidAlternateServiceAccountCredentials switch specifies whether to remove a previously configured alternate service account that's no longer valid. You don't need to specify a value with this switch.
 
@@ -180,7 +180,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -201,7 +201,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -219,7 +219,7 @@ Accept wildcard characters: False
 
 ### -RemoveAlternateServiceAccountCredentials
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RemoveAlternateServiceAccountCredentials switch specifies whether to remove a previously distributed alternate service account. You don't need to specify a value with this switch.
 
@@ -237,7 +237,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-CmdletExtensionAgent.md b/exchange/exchange-ps/ExchangePowerShell/Set-CmdletExtensionAgent.md
index 1076192f9a..4ce86eaea0 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-CmdletExtensionAgent.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-CmdletExtensionAgent.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -51,7 +51,7 @@ This example changes the priority of the fictitious "Validation Agent" cmdlet ex
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the cmdlet extension agent that you want to modify. You can use any value that uniquely identifies the agent. For example:
 
@@ -73,7 +73,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -94,7 +94,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -112,7 +112,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Name parameter specifies the unique name of the cmdlet extension agent. The maximum length of the agent name is 64 characters. If the name contains spaces, enclose the name in quotation marks (").
 
@@ -130,7 +130,7 @@ Accept wildcard characters: False
 
 ### -Priority
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Priority parameter specifies the priority of the cmdlet extension agent. Higher priority agents are applied before lower priority agents. A valid value is an integer from 0 to 255. Lower integer values indicate higher priority.
 
@@ -148,7 +148,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceSearch.md b/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceSearch.md
index 77914d94f0..1cc1cdb8a1 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceSearch.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceSearch.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 author: chrisda
 external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
 Locale: en-US
@@ -88,7 +88,7 @@ You might have to change the language setting if you're using non-English keywor
 
 ### -Identity
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The Identity parameter specifies the compliance search that you want to modify.
 
@@ -113,7 +113,7 @@ Accept wildcard characters: False
 
 ### -AddExchangeLocation
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The AddExchangeLocation parameter specifies the mailboxes to add to the list of included mailboxes when you aren't using the value All for the ExchangeLocation parameter. Valid values are:
 
@@ -136,7 +136,7 @@ Accept wildcard characters: False
 
 ### -AddExchangeLocationExclusion
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 This parameter is functional only in on-premises Exchange.
 
@@ -203,7 +203,7 @@ Accept wildcard characters: False
 
 ### -AllowNotFoundExchangeLocationsEnabled
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The AllowNotFoundExchangeLocationsEnabled parameter specifies whether to include mailboxes other than regular user mailboxes in the compliance search. Valid values are:
 
@@ -231,7 +231,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -252,7 +252,7 @@ Accept wildcard characters: False
 
 ### -ContentMatchQuery
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The ContentMatchQuery parameter specifies a content search filter.
 
@@ -272,7 +272,7 @@ Accept wildcard characters: False
 
 ### -Description
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The Description parameter specifies a description for the compliance search. If the value contains spaces, enclose the value in quotation marks.
 
@@ -290,7 +290,7 @@ Accept wildcard characters: False
 
 ### -ExchangeLocation
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The ExchangeLocation parameter specifies the mailboxes to include. Valid values are:
 
@@ -316,7 +316,7 @@ Accept wildcard characters: False
 
 ### -ExchangeLocationExclusion
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 This parameter is functional only in on-premises Exchange.
 
@@ -341,7 +341,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -426,7 +426,7 @@ Accept wildcard characters: False
 
 ### -Language
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The Language parameter specifies the language for the compliance search.
 
@@ -446,7 +446,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 This parameter is reserved for internal Microsoft use.
 
@@ -504,7 +504,7 @@ Accept wildcard characters: False
 
 ### -RemoveExchangeLocation
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The RemoveExchangeLocation parameter specifies the mailboxes to remove from the list of included mailboxes when you aren't using the value All for the ExchangeLocation parameter. Valid values are:
 
@@ -527,7 +527,7 @@ Accept wildcard characters: False
 
 ### -RemoveExchangeLocationExclusion
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 This parameter is functional only in on-premises Exchange.
 
@@ -656,7 +656,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The WhatIf switch doesn't work in Security & Compliance PowerShell.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceSearchAction.md b/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceSearchAction.md
index 7b3b7caae8..60be06c85d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceSearchAction.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceSearchAction.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 author: chrisda
 external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
 Locale: en-US
@@ -51,7 +51,7 @@ This example changes the export key on the export compliance search action named
 
 ### -Identity
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The Identity parameter specifies the compliance search action that you want to modify. You can use any value that uniquely identifies the compliance search action. For example:
 
@@ -72,7 +72,7 @@ Accept wildcard characters: False
 
 ### -ChangeExportKey
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The ChangeExportKey switch creates a new export key for the compliance search action. You don't need to specify a value with this switch.
 
@@ -92,7 +92,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -131,7 +131,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceSecurityFilter.md b/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceSecurityFilter.md
index 40742de678..f69d0441f0 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceSecurityFilter.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceSecurityFilter.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 author: chrisda
 external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
 Locale: en-US
@@ -64,7 +64,7 @@ This example removes user annb@contoso.com to the compliance security filter nam
 
 ### -FilterName
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The FilterName parameter specifies the name of the compliance security filter that you want to modify. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -82,7 +82,7 @@ Accept wildcard characters: False
 
 ### -Action
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The Action parameter specifies that type of search action that the filter is applied to. A valid value for this parameter is All, which means the filter is applied to all search actions.
 
@@ -106,7 +106,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -127,7 +127,7 @@ Accept wildcard characters: False
 
 ### -Description
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The Description parameter specifies a description for the compliance security filter. The maximum length is 256 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -145,7 +145,7 @@ Accept wildcard characters: False
 
 ### -Filters
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The Filters parameter specifies the search criteria for the compliance security filter. You can create three different types of filters:
 
@@ -169,7 +169,7 @@ Accept wildcard characters: False
 
 ### -Region
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The Region parameter specifies the satellite location for multi-geo tenants to conduct eDiscovery searches in. Valid values are:
 
@@ -200,7 +200,7 @@ Accept wildcard characters: False
 
 ### -Users
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The Users parameter specifies the user who gets this filter applied to their searches. Valid values are:
 
@@ -226,7 +226,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The WhatIf switch doesn't work in Security & Compliance PowerShell.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-Contact.md b/exchange/exchange-ps/ExchangePowerShell/Set-Contact.md
index cfd2ce2f56..835d80fec1 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-Contact.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-Contact.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -87,7 +87,7 @@ Change the Company parameter value to Contoso.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the contact that you want to modify. You can use any value that uniquely identifies the contact. For example:
 
@@ -110,7 +110,7 @@ Accept wildcard characters: False
 
 ### -AllowUMCallsFromNonUsers
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -130,7 +130,7 @@ Accept wildcard characters: False
 
 ### -AssistantName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The AssistantName parameter specifies the name of the contact's assistant.
 
@@ -148,7 +148,7 @@ Accept wildcard characters: False
 
 ### -City
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The City parameter specifies the contact's city.
 
@@ -166,7 +166,7 @@ Accept wildcard characters: False
 
 ### -Company
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Company parameter specifies the contact's company.
 
@@ -184,7 +184,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -205,7 +205,7 @@ Accept wildcard characters: False
 
 ### -CountryOrRegion
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The CountryOrRegion parameter specifies the contact's country or region. A valid value is a valid ISO 3166-1 two-letter country code (for example, AU for Australia) or the corresponding friendly name for the country (which might be different from the official ISO 3166 Maintenance Agency short name).
 
@@ -227,7 +227,7 @@ Accept wildcard characters: False
 
 ### -CreateDTMFMap
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -250,7 +250,7 @@ Accept wildcard characters: False
 
 ### -Department
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Department parameter specifies the contact's department.
 
@@ -268,7 +268,7 @@ Accept wildcard characters: False
 
 ### -DisplayName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The DisplayName parameter specifies the display name of the contact. The display name is visible in the Exchange admin center and in address lists. The maximum length is 256 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -288,7 +288,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -308,7 +308,7 @@ Accept wildcard characters: False
 
 ### -Fax
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Fax parameter specifies the contact's fax number.
 
@@ -326,7 +326,7 @@ Accept wildcard characters: False
 
 ### -FirstName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The FirstName parameter specifies the user's first name.
 
@@ -344,7 +344,7 @@ Accept wildcard characters: False
 
 ### -GeoCoordinates
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The GeoCoordinates parameter specifies the contact's location in latitude, longitude and (optionally) altitude coordinates. A valid value for this parameter uses one of the following formats:
 
@@ -367,7 +367,7 @@ Accept wildcard characters: False
 
 ### -HomePhone
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The HomePhone parameter specifies the contact's home telephone number.
 
@@ -385,7 +385,7 @@ Accept wildcard characters: False
 
 ### -IgnoreDefaultScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -410,7 +410,7 @@ Accept wildcard characters: False
 
 ### -Initials
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Initials parameter specifies the user's middle initials.
 
@@ -428,7 +428,7 @@ Accept wildcard characters: False
 
 ### -LastName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The LastName parameter specifies the user's last name.
 
@@ -446,7 +446,7 @@ Accept wildcard characters: False
 
 ### -Manager
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Manager parameter specifies the contact's manager.
 
@@ -464,7 +464,7 @@ Accept wildcard characters: False
 
 ### -MobilePhone
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The MobilePhone parameter specifies the contact's primary mobile phone number.
 
@@ -482,7 +482,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Name parameter specifies the unique name of the contact. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -500,7 +500,7 @@ Accept wildcard characters: False
 
 ### -Notes
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Notes parameters specifies additional information about the object. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -518,7 +518,7 @@ Accept wildcard characters: False
 
 ### -Office
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Office parameter specifies the user's physical office name or number.
 
@@ -536,7 +536,7 @@ Accept wildcard characters: False
 
 ### -OtherFax
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The OtherFax parameter specifies the contact's alternative fax number.
 
@@ -554,7 +554,7 @@ Accept wildcard characters: False
 
 ### -OtherHomePhone
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The OtherHomePhone parameter specifies the contact's alternative home telephone number.
 
@@ -572,7 +572,7 @@ Accept wildcard characters: False
 
 ### -OtherTelephone
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The OtherTelephone parameter specifies the contact's alternative office telephone number.
 
@@ -590,7 +590,7 @@ Accept wildcard characters: False
 
 ### -Pager
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Pager parameter specifies the contact's pager number.
 
@@ -608,7 +608,7 @@ Accept wildcard characters: False
 
 ### -Phone
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Phone parameter specifies the contact's office telephone number.
 
@@ -626,7 +626,7 @@ Accept wildcard characters: False
 
 ### -PhoneticDisplayName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The PhoneticDisplayName parameter specifies an alternate spelling of the user's name that's used for text to speech in Unified Messaging (UM) environments. Typically, you use this parameter when the pronunciation and spelling of the user's name don't match. The maximum length is 256 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -644,7 +644,7 @@ Accept wildcard characters: False
 
 ### -PostalCode
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The PostalCode parameter specifies the contact's postal code.
 
@@ -662,7 +662,7 @@ Accept wildcard characters: False
 
 ### -PostOfficeBox
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The PostOfficeBox parameter specifies the contact's post office box number.
 
@@ -680,7 +680,7 @@ Accept wildcard characters: False
 
 ### -SeniorityIndex
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The SeniorityIndex parameter specifies the order in which this contact displays in a hierarchical address book. A contact with a value of 2 displays higher in an address book than a contact with a value of 1.
 
@@ -698,7 +698,7 @@ Accept wildcard characters: False
 
 ### -SimpleDisplayName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The SimpleDisplayName parameter is used to display an alternative description of the object when only a limited set of characters is permitted. Valid characters are:
 
@@ -724,7 +724,7 @@ Accept wildcard characters: False
 
 ### -StateOrProvince
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The StateOrProvince parameter specifies the contact's state or province.
 
@@ -742,7 +742,7 @@ Accept wildcard characters: False
 
 ### -StreetAddress
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The StreetAddress parameter specifies the contact's physical address.
 
@@ -760,7 +760,7 @@ Accept wildcard characters: False
 
 ### -TelephoneAssistant
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The TelephoneAssistant parameter specifies the telephone number of the contact's assistant.
 
@@ -778,7 +778,7 @@ Accept wildcard characters: False
 
 ### -Title
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Title parameter specifies the contact's title.
 
@@ -796,7 +796,7 @@ Accept wildcard characters: False
 
 ### -UMCallingLineIds
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -816,7 +816,7 @@ Accept wildcard characters: False
 
 ### -UMDtmfMap
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -848,7 +848,7 @@ Accept wildcard characters: False
 
 ### -WebPage
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WebPage parameter specifies the contact's web page.
 
@@ -866,7 +866,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
@@ -884,7 +884,7 @@ Accept wildcard characters: False
 
 ### -WindowsEmailAddress
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WindowsEmailAddress parameter specifies the Windows email address for this recipient. This is a common Active Directory attribute that's present in all environments, including environments without Exchange. Using the WindowsEmailAddress parameter on a recipient has one of the following results:
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ContentFilterConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-ContentFilterConfig.md
index e16cf78246..a7340abe9d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ContentFilterConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ContentFilterConfig.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailControl-Help.xml
 Locale: en-US
@@ -72,7 +72,7 @@ It defines two users for whom the Content Filter doesn't process messages.
 
 ### -BypassedRecipients
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The BypassedRecipients parameter specifies the SMTP addresses of recipients who skip processing by the Content Filter agent.
 
@@ -92,7 +92,7 @@ Accept wildcard characters: False
 
 ### -BypassedSenderDomains
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The BypassedSenderDomains parameter specifies the sender email address domains of senders who skip processing by the Content Filter agent.
 
@@ -112,7 +112,7 @@ Accept wildcard characters: False
 
 ### -BypassedSenders
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The BypassedSenders parameter specifies the SMTP addresses of senders who skip processing by the Content Filter agent.
 
@@ -132,7 +132,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -153,7 +153,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -173,7 +173,7 @@ Accept wildcard characters: False
 
 ### -Enabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Enabled parameter enables or disables the Content Filter agent on the computer on which you're running the command. Valid values are:
 
@@ -194,7 +194,7 @@ Accept wildcard characters: False
 
 ### -ExternalMailEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExternalMailEnabled parameter specifies whether all messages from unauthenticated connections from sources external to your Exchange organization are processed by the Content Filter agent. Valid values are:
 
@@ -215,7 +215,7 @@ Accept wildcard characters: False
 
 ### -InternalMailEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The InternalMailEnabled parameter specifies whether all messages from authenticated connections and from authoritative domains in your enterprise are processed by the Content Filter agent. Valid values are:
 
@@ -236,7 +236,7 @@ Accept wildcard characters: False
 
 ### -OutlookEmailPostmarkValidationEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The OutlookEmailPostmarkValidationEnabled parameter specifies whether Outlook Email Postmark validation is enabled.
 
@@ -262,7 +262,7 @@ Accept wildcard characters: False
 
 ### -QuarantineMailbox
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The QuarantineMailbox parameter specifies an SMTP address to be used as a spam quarantine mailbox. A spam quarantine mailbox is required when you set the SCLQuarantineEnabled parameter to $true. All messages that meet or exceed the value set in the SCLQuarantineThreshold parameter are sent to the SMTP address that you set in this parameter.
 
@@ -280,7 +280,7 @@ Accept wildcard characters: False
 
 ### -RejectionResponse
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RejectionResponse parameter specifies the message body that you want delivered in the non-delivery report (NDR) to senders whose messages meet or exceed the SCLRejectThreshold value. The RejectionResponse parameter is required if you set the SCLRejectEnabled parameter to $true. The RejectionResponse parameter takes a string. Don't exceed 240 characters in the argument. When you pass an argument, you must enclose the RejectionResponse parameter in quotation marks (") if the phrase contains spaces, for example: "Message rejected". The default setting is Message rejected due to content restrictions.
 
@@ -298,7 +298,7 @@ Accept wildcard characters: False
 
 ### -SCLDeleteEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SCLDeleteEnabled parameter specifies whether all messages that meet or exceed the value set in the SCLDeleteThreshold parameter are deleted. Valid values are:
 
@@ -319,7 +319,7 @@ Accept wildcard characters: False
 
 ### -SCLDeleteThreshold
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SCLDeleteThreshold parameter specifies an integer value from 1 through 9. This value represents the SCL rating that a particular message must meet or exceed for the Content Filter agent to delete the message and not send an NDR. To enable this functionality, you must set the SCLDeleteEnabled parameter to $true. The default setting is 9.
 
@@ -337,7 +337,7 @@ Accept wildcard characters: False
 
 ### -SCLQuarantineEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SCLQuarantineEnabled parameter specifies whether all messages that meet or exceed the value set in the SCLQuarantineThreshold parameter are sent to the spam quarantine mailbox specified in the QuarantineMailbox parameter. Valid values are:
 
@@ -358,7 +358,7 @@ Accept wildcard characters: False
 
 ### -SCLQuarantineThreshold
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SCLQuarantineThreshold parameter specifies an integer value from 1 through 9. This value represents the SCL rating that a particular message must meet or exceed for the Content Filter agent to quarantine the message. To enable quarantine functionality, you must set the SCLQuarantineEnabled parameter to $true, and provide a valid SMTP address in the QuarantineMailbox parameter. The default setting is 9.
 
@@ -376,7 +376,7 @@ Accept wildcard characters: False
 
 ### -SCLRejectEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SCLRejectEnabled parameter specifies whether all messages that meet or exceed the value set in the SCLRejectThreshold parameter are rejected in an NDR to the sender. Valid values are:
 
@@ -397,7 +397,7 @@ Accept wildcard characters: False
 
 ### -SCLRejectThreshold
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SCLRejectThreshold parameter specifies an integer value from 1 through 9. This value represents the SCL rating that a particular message must meet or exceed for the Content Filter agent to reject the message and send an NDR to the sender. To enable the delete functionality, you must set the SCLDeleteEnabled parameter to $true. Also, you can revise the default NDR message by editing the RejectionResponse parameter. The default setting is 7.
 
@@ -415,7 +415,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-DataClassification.md b/exchange/exchange-ps/ExchangePowerShell/Set-DataClassification.md
index 96da55616a..eb9441e324 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-DataClassification.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-DataClassification.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -95,7 +95,7 @@ The first three commands return the list of document fingerprints in the data cl
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the data classification rule that you want to modify. You can use any value that uniquely identifies the data classification rule. For example:
 
@@ -117,7 +117,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -138,7 +138,7 @@ Accept wildcard characters: False
 
 ### -Description
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Description parameter specifies a description for the data classification rule. You use the Description parameter with the Locale and Name parameters to specify descriptions for the data classification rule in different languages. The localized values of Description appear in the AllLocalizedDescriptions property of the data classification rule.
 
@@ -156,7 +156,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -174,7 +174,7 @@ Accept wildcard characters: False
 
 ### -Fingerprints
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Fingerprints parameter specifies the byte-encoded document files that are used as fingerprints by the data classification rule. For instructions on how to import documents to use as templates for fingerprints, see [New-Fingerprint](https://learn.microsoft.com/powershell/module/exchangepowershell/new-fingerprint) or the Examples section. For instructions on how to add and remove document fingerprints from an existing data classification rule, see the Examples section.
 
@@ -192,7 +192,7 @@ Accept wildcard characters: False
 
 ### -IsDefault
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IsDefault switch is used with the Locale parameter to specify the default language for the data classification rule. You don't need to specify a value with this switch.
 
@@ -214,7 +214,7 @@ Accept wildcard characters: False
 
 ### -Locale
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Locale parameter adds or removes languages that are associated with the data classification rule.
 
@@ -236,7 +236,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Name parameter specifies a name for the data classification rule. The value must be less than 256 characters.
 
@@ -258,7 +258,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-DatabaseAvailabilityGroup.md b/exchange/exchange-ps/ExchangePowerShell/Set-DatabaseAvailabilityGroup.md
index 050d159a8c..1e2ff17c90 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-DatabaseAvailabilityGroup.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-DatabaseAvailabilityGroup.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -135,7 +135,7 @@ This example configures the DAG DAG1 for AutoReseed using custom mount point pat
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the name of the DAG that you want to modify.
 
@@ -153,7 +153,7 @@ Accept wildcard characters: False
 
 ### -ActivityState
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -171,7 +171,7 @@ Accept wildcard characters: False
 
 ### -AllowCrossSiteRpcClientAccess
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -189,7 +189,7 @@ Accept wildcard characters: False
 
 ### -AlternateWitnessDirectory
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AlternateWitnessDirectory parameter specifies the name of an alternate directory that's used to store file share witness data. The specified directory must not be in use by any other DAGs or used for any other purpose. This parameter is used only as part of a datacenter switchover process. If the DAG is extended across multiple datacenters in a site resilience configuration, we recommend preconfiguring the alternate witness server and directory.
 
@@ -207,7 +207,7 @@ Accept wildcard characters: False
 
 ### -AlternateWitnessServer
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AlternateWitnessServer parameter specifies the name of an alternate server that's used to store file share witness data. The specified server must not be a member of the DAG that's configured to use it. This parameter is used only as part of a datacenter switchover process. If the DAG is extended across multiple datacenters in a site resilience configuration, we recommend preconfiguring the alternate witness server and directory.
 
@@ -225,7 +225,7 @@ Accept wildcard characters: False
 
 ### -AutoDagAllServersInstalled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -243,7 +243,7 @@ Accept wildcard characters: False
 
 ### -AutoDagAutoRedistributeEnabled
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AutoDagAutoRedistributeEnabled parameter specifies whether automatic DAG redistribution is enabled or disabled during AutoReseed. The default value is $true (enabled).
 
@@ -261,7 +261,7 @@ Accept wildcard characters: False
 
 ### -AutoDagAutoReseedEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AutoDagAutoReseedEnabled is used to enable or disable Autoreseed. The default value is $true (enabled).
 
@@ -279,7 +279,7 @@ Accept wildcard characters: False
 
 ### -AutoDagBitlockerEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AutoDagBitlockerEnabled parameter ensures that Disk Reclaimer handles spare disks correctly and encrypts them with BitLocker. If Bitlocker is used to encrypt database disks, set the value of this parameter to $true on all Mailbox servers in the DAG after they are all running Exchange 2013 CU13 or later, or Exchange 2016 CU2 or later.
 
@@ -297,7 +297,7 @@ Accept wildcard characters: False
 
 ### -AutoDagDatabaseCopiesPerDatabase
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -315,7 +315,7 @@ Accept wildcard characters: False
 
 ### -AutoDagDatabaseCopiesPerVolume
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AutoDagDatabaseCopiesPerVolume parameter is used to specify the configured number of database copies per volume. This parameter is used only with AutoReseed.
 
@@ -333,7 +333,7 @@ Accept wildcard characters: False
 
 ### -AutoDagDatabasesRootFolderPath
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AutoDagDatabasesRootFolderPath parameter specifies the directory containing the database mount points when using AutoReseed. This parameter is required when using AutoReseed. AutoReseed uses a default path of C:\\ExchangeDatabases.
 
@@ -351,7 +351,7 @@ Accept wildcard characters: False
 
 ### -AutoDagDiskReclaimerEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AutoDagDiskReclaimerEnabled is used to enable or disable the volume formatting functions used by Autoreseed. The default value is $true (enabled). If you set this to $false, you need to manually format the volume before the database(s) can be reseeded.
 
@@ -369,7 +369,7 @@ Accept wildcard characters: False
 
 ### -AutoDagTotalNumberOfDatabases
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -387,7 +387,7 @@ Accept wildcard characters: False
 
 ### -AutoDagTotalNumberOfServers
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -405,7 +405,7 @@ Accept wildcard characters: False
 
 ### -AutoDagVolumesRootFolderPath
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AutoDagVolumesRootFolderPath parameter specifies the volume containing the mount points for all disks, including spare disks, when using the AutoReseed feature of the DAG. This parameter is required when using AutoReseed. AutoReseed uses a default path of C:\\ExchangeVolumes.
 
@@ -423,7 +423,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -444,7 +444,7 @@ Accept wildcard characters: False
 
 ### -DagConfiguration
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -462,7 +462,7 @@ Accept wildcard characters: False
 
 ### -DatabaseAvailabilityGroupIpAddresses
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DatabaseAvailabilityGroupIpAddresses parameter specifies one or more static IP addresses to the DAG when a Mailbox server is added to a DAG. If you omit the DatabaseAvailabilityGroupIpAddresses parameter when creating a DAG, the system attempts to lease one or more IP addresses from a Dynamic Host Configuration Protocol (DHCP) server in your organization to assign to the DAG. You must specify this parameter each time an additional IP address is added to the DAG, such as in the case of multi-subnet DAGs. You must also specify all IP addresses previously assigned to the DAG each time the DatabaseAvailabilityGroupIpAddresses parameter is used. Setting the DatabaseAvailabilityGroupIpAddresses parameter to a value of 0.0.0.0 automatically configures the DAG to use DHCP.
 
@@ -480,7 +480,7 @@ Accept wildcard characters: False
 
 ### -DatacenterActivationMode
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DatacenterActivationMode parameter specifies the datacenter activation mode for the DAG. Valid values are:
 
@@ -501,7 +501,7 @@ Accept wildcard characters: False
 
 ### -DiscoverNetworks
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DiscoverNetworks switch specifies whether to force a rediscovery of the network and network interfaces. You don't need to specify a value with this switch.
 
@@ -521,7 +521,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -539,7 +539,7 @@ Accept wildcard characters: False
 
 ### -FileSystem
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The FileSystem parameter specifies the file system that's used for the DAG. Valid values are:
 
@@ -560,7 +560,7 @@ Accept wildcard characters: False
 
 ### -ManualDagNetworkConfiguration
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ManualDagNetworkConfiguration parameter specifies whether DAG networks should be automatically configured. If this parameter is set to $false, DAG networks are automatically configured. If this parameter is set to $true, you must manually configure DAG networks.
 
@@ -578,7 +578,7 @@ Accept wildcard characters: False
 
 ### -MetaCacheDatabaseVolumesPerServer
 
-> Applicable: Exchange Server 2019
+> Applicable: Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -596,7 +596,7 @@ Accept wildcard characters: False
 
 ### -NetworkCompression
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The NetworkCompression parameter specifies the network compression option for the DAG. Valid values are:
 
@@ -619,7 +619,7 @@ Accept wildcard characters: False
 
 ### -NetworkEncryption
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The NetworkEncryption parameter specifies the network encryption option for the DAG. Valid values are:
 
@@ -642,7 +642,7 @@ Accept wildcard characters: False
 
 ### -PreferenceMoveFrequency
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PreferenceMoveFrequency parameter specifies how frequently the Microsoft Exchange Replication service inspects and automatically rebalances the database copies. If the most preferred database copy (ActivationPreference value of 1) isn't the active copy, the most preferred database copy is activated by performing a lossless switchover.
 
@@ -666,7 +666,7 @@ Accept wildcard characters: False
 
 ### -ReplayLagManagerEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ReplayLagManagerEnabled parameter specifies whether to disable the automatic playdown of log files for a lagged database copy.
 
@@ -684,7 +684,7 @@ Accept wildcard characters: False
 
 ### -ReplicationPort
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ReplicationPort parameter specifies a Transmission Control Protocol (TCP) port for replication (log shipping and seeding) activity. If this parameter isn't specified, the default port for replication is TCP 64327.
 
@@ -702,7 +702,7 @@ Accept wildcard characters: False
 
 ### -SkipDagValidation
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SkipDagValidation switch specifies whether to bypass the validation of the DAG's quorum model and the health check on the DAG's witness when configuring the DAG. You don't need to specify a value with this switch.
 
@@ -720,7 +720,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
@@ -738,7 +738,7 @@ Accept wildcard characters: False
 
 ### -WitnessDirectory
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WitnessDirectory parameter specifies the name of the directory on the server that's used to store file share witness data. The specified directory must not be in use by any other DAGs.
 
@@ -756,7 +756,7 @@ Accept wildcard characters: False
 
 ### -WitnessServer
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WitnessServer parameter specifies the name of a server that acts as a witness for the DAG. The server specified can't be a member of the DAG.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-DatabaseAvailabilityGroupNetwork.md b/exchange/exchange-ps/ExchangePowerShell/Set-DatabaseAvailabilityGroupNetwork.md
index 26432fbd03..0679873a53 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-DatabaseAvailabilityGroupNetwork.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-DatabaseAvailabilityGroupNetwork.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -59,7 +59,7 @@ This example disables the DAG network DAGNetwork02 in the DAG DAG2 for replicati
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the DAG network being configured.
 
@@ -77,7 +77,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -98,7 +98,7 @@ Accept wildcard characters: False
 
 ### -Description
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Description parameter specifies an optional description for the DAG network.
 
@@ -116,7 +116,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -134,7 +134,7 @@ Accept wildcard characters: False
 
 ### -IgnoreNetwork
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IgnoreNetwork parameter indicates that the specified network should be ignored and not used by the DAG.
 
@@ -152,7 +152,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Name parameter provides a name for the DAG network.
 
@@ -170,7 +170,7 @@ Accept wildcard characters: False
 
 ### -ReplicationEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ReplicationEnabled parameter specifies whether the network can be used for replication activity. If this parameter isn't specified, the default behavior is to enable the network for replication.
 
@@ -188,7 +188,7 @@ Accept wildcard characters: False
 
 ### -Subnets
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Subnets parameter specifies one or more subnets that are associated with the DAG network.
 
@@ -206,7 +206,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-DeliveryAgentConnector.md b/exchange/exchange-ps/ExchangePowerShell/Set-DeliveryAgentConnector.md
index 4996845f35..dd3062b215 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-DeliveryAgentConnector.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-DeliveryAgentConnector.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -75,7 +75,7 @@ This example uses the temporary variable $ConnectorConfig to add the address spa
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the GUID or name of the delivery agent connector.
 
@@ -93,7 +93,7 @@ Accept wildcard characters: False
 
 ### -AddressSpaces
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AddressSpaces parameter specifies the domain names that the delivery agent connector is responsible for. The complete syntax for entering an address space is: `AddressSpaceType:AddressSpace;AddressSpaceCost`. Enclose each address space in quotation marks (").
 
@@ -111,7 +111,7 @@ Accept wildcard characters: False
 
 ### -Comment
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Comment parameter specifies an optional comment. If you specify a value that contains spaces, enclose the value in quotation marks ("), for example: "This is an admin note".
 
@@ -129,7 +129,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -150,7 +150,7 @@ Accept wildcard characters: False
 
 ### -DeliveryProtocol
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DeliveryProtocol parameter specifies the communication protocol that determines which delivery agents are responsible for servicing the connector.
 
@@ -168,7 +168,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -188,7 +188,7 @@ Accept wildcard characters: False
 
 ### -Enabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Enabled parameter specifies whether the delivery agent connector is enabled.
 
@@ -208,7 +208,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -228,7 +228,7 @@ Accept wildcard characters: False
 
 ### -IsScopedConnector
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IsScopedConnector parameter specifies the availability of the connector to other Mailbox servers. If the value of this parameter is $false, the connector can be used by all Mailbox servers in your organization. If the value of this parameter is $true, the connector can only be used by Mailbox servers in the same Active Directory site.
 
@@ -248,7 +248,7 @@ Accept wildcard characters: False
 
 ### -MaxConcurrentConnections
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MaxConcurrentConnections parameter specifies the maximum number of concurrent connections this connector accepts from a specific IP address.
 
@@ -268,7 +268,7 @@ Accept wildcard characters: False
 
 ### -MaxMessageSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MaxMessageSize parameter specifies the maximum size of a message that's allowed to pass through this connector. When you enter a value, qualify the value with one of the following units:
 
@@ -295,7 +295,7 @@ Accept wildcard characters: False
 
 ### -MaxMessagesPerConnection
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MaxMessagesPerConnection parameter specifies the maximum number of messages this connector accepts per connection. The connector terminates the connection after this limit is reached and the sending server has to initiate a new connection to send more messages.
 
@@ -315,7 +315,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Name parameter specifies the name of this delivery agent connector. The value for the Name parameter can't exceed 64 characters.
 
@@ -333,7 +333,7 @@ Accept wildcard characters: False
 
 ### -SourceTransportServers
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SourceTransportServers parameter specifies the list of Mailbox servers that host this connector. You can specify more than one server by separating their names with commas.
 
@@ -353,7 +353,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-DetailsTemplate.md b/exchange/exchange-ps/ExchangePowerShell/Set-DetailsTemplate.md
index 95bb18e238..3afb7ff226 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-DetailsTemplate.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-DetailsTemplate.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -46,7 +46,7 @@ This example sets attributes for the User details template for the U.S. English
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the details template using a GUID or specifies a template type and language separated by a slash. The following is an example of the user template type and U.S. English language: en-us\\User. Details template types include:
 
@@ -71,7 +71,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -92,7 +92,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -110,7 +110,7 @@ Accept wildcard characters: False
 
 ### -Pages
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -128,7 +128,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-DistributionGroup.md b/exchange/exchange-ps/ExchangePowerShell/Set-DistributionGroup.md
index 01e017c678..0a06420b0c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-DistributionGroup.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-DistributionGroup.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
 Locale: en-US
@@ -128,7 +128,7 @@ This example changes the name of an existing distribution group from Ed\_DirectR
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the distribution group or mail-enabled security group that you want to modify. You can use any value that uniquely identifies the group. For example:
 
@@ -153,7 +153,7 @@ Accept wildcard characters: False
 
 ### -AcceptMessagesOnlyFrom
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The AcceptMessagesOnlyFrom parameter specifies who is allowed to send messages to this recipient. Messages from other senders are rejected.
 
@@ -188,7 +188,7 @@ Accept wildcard characters: False
 
 ### -AcceptMessagesOnlyFromDLMembers
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The AcceptMessagesOnlyFromDLMembers parameter specifies who is allowed to send messages to this recipient. Messages from other senders are rejected.
 
@@ -223,7 +223,7 @@ Accept wildcard characters: False
 
 ### -AcceptMessagesOnlyFromSendersOrMembers
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The AcceptMessagesOnlyFromSendersOrMembers parameter specifies who is allowed to send messages to this recipient. Messages from other senders are rejected.
 
@@ -260,7 +260,7 @@ Accept wildcard characters: False
 
 ### -Alias
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Alias parameter specifies the Exchange alias (also known as the mail nickname) for the recipient. This value identifies the recipient as a mail-enabled object, and shouldn't be confused with multiple email addresses for the same recipient (also known as proxy addresses). A recipient can have only one Alias value. The maximum length is 64 characters.
 
@@ -296,7 +296,7 @@ Accept wildcard characters: False
 
 ### -ArbitrationMailbox
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -350,7 +350,7 @@ Accept wildcard characters: False
 
 ### -BypassModerationFromSendersOrMembers
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The BypassModerationFromSendersOrMembers parameter specifies who is allowed to send messages to this moderated recipient without approval from a moderator. Valid values for this parameter are individual senders and groups in your organization. Specifying a group means all members of the group are allowed to send messages to this recipient without approval from a moderator.
 
@@ -383,7 +383,7 @@ Accept wildcard characters: False
 
 ### -BypassNestedModerationEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ByPassNestedModerationEnabled parameter specifies how to handle message approval when a moderated group contains other moderated groups as members. Valid values are:
 
@@ -404,7 +404,7 @@ Accept wildcard characters: False
 
 ### -BypassSecurityGroupManagerCheck
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The BypassSecurityGroupManagerCheck switch specifies whether to allow a user who isn't an owner of the group to modify or delete the group. You don't need to specify a value with this switch.
 
@@ -427,7 +427,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -448,7 +448,7 @@ Accept wildcard characters: False
 
 ### -CreateDTMFMap
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -471,7 +471,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute1
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the CustomAttribute1 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -489,7 +489,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute10
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the CustomAttribute10 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -507,7 +507,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute11
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the CustomAttribute11 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -525,7 +525,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute12
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the CustomAttribute12 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -543,7 +543,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute13
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the CustomAttribute13 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -561,7 +561,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute14
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the CustomAttribute14 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -579,7 +579,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute15
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the CustomAttribute15 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -597,7 +597,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute2
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the CustomAttribute2 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -615,7 +615,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute3
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the CustomAttribute3 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -633,7 +633,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute4
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the CustomAttribute4 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -651,7 +651,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute5
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the CustomAttribute5 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -669,7 +669,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute6
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the CustomAttribute6 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -687,7 +687,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute7
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the CustomAttribute7 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -705,7 +705,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute8
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the CustomAttribute8 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -723,7 +723,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute9
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the CustomAttribute9 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -761,7 +761,7 @@ Accept wildcard characters: False
 
 ### -DisplayName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The DisplayName parameter specifies the display name of the group. The display name is visible in the Exchange admin center and in address lists. The maximum length is 256 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -781,7 +781,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -801,7 +801,7 @@ Accept wildcard characters: False
 
 ### -EmailAddresses
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The EmailAddresses parameter specifies all email addresses (proxy addresses) for the recipient, including the primary SMTP address. In on-premises Exchange organizations, the primary SMTP address and other proxy addresses are typically set by email address policies. However, you can use this parameter to configure other proxy addresses for the recipient. For more information, see [Email address policies in Exchange Server](https://learn.microsoft.com/Exchange/email-addresses-and-address-books/email-address-policies/email-address-policies).
 
@@ -840,7 +840,7 @@ Accept wildcard characters: False
 
 ### -EmailAddressPolicyEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -863,7 +863,7 @@ Accept wildcard characters: False
 
 ### -ExpansionServer
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -890,7 +890,7 @@ Accept wildcard characters: False
 
 ### -ExtensionCustomAttribute1
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the ExtensionCustomAttribute1 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas.
 
@@ -914,7 +914,7 @@ Accept wildcard characters: False
 
 ### -ExtensionCustomAttribute2
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the ExtensionCustomAttribute2 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas.
 
@@ -938,7 +938,7 @@ Accept wildcard characters: False
 
 ### -ExtensionCustomAttribute3
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the ExtensionCustomAttribute3 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas.
 
@@ -962,7 +962,7 @@ Accept wildcard characters: False
 
 ### -ExtensionCustomAttribute4
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the ExtensionCustomAttribute4 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas.
 
@@ -986,7 +986,7 @@ Accept wildcard characters: False
 
 ### -ExtensionCustomAttribute5
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the ExtensionCustomAttribute5 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas.
 
@@ -1010,7 +1010,7 @@ Accept wildcard characters: False
 
 ### -ForceUpgrade
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ForceUpgrade switch suppresses the confirmation message that appears if the object was created in a previous version of Exchange. You don't need to specify a value with this switch.
 
@@ -1028,7 +1028,7 @@ Accept wildcard characters: False
 
 ### -GrantSendOnBehalfTo
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The GrantSendOnBehalfTo parameter specifies who can send on behalf of this group. Although messages send on behalf of the group clearly show the sender in the From field (`<Sender> on behalf of <Group>`), replies to these messages are delivered to the group, not the sender.
 
@@ -1065,7 +1065,7 @@ Accept wildcard characters: False
 
 ### -HiddenFromAddressListsEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The HiddenFromAddressListsEnabled parameter specifies whether this recipient is visible in address lists. Valid values are:
 
@@ -1110,7 +1110,7 @@ Accept wildcard characters: False
 
 ### -IgnoreDefaultScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1135,7 +1135,7 @@ Accept wildcard characters: False
 
 ### -IgnoreNamingPolicy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The IgnoreNamingPolicy switch specifies whether to prevent this group from being affected by your organization's group naming policy. You don't need to specify a value with this switch.
 
@@ -1155,7 +1155,7 @@ Accept wildcard characters: False
 
 ### -MailTip
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The MailTip parameter specifies the custom MailTip text for this recipient. The MailTip is shown to senders when they start drafting an email message to this recipient. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -1178,7 +1178,7 @@ Accept wildcard characters: False
 
 ### -MailTipTranslations
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The MailTipTranslations parameter specifies additional languages for the custom MailTip text that's defined by the MailTip parameter. HTML tags are automatically added to the MailTip translation, additional HTML tags aren't supported, and the length of the MailTip translation can't exceed 175 displayed characters.
 
@@ -1204,7 +1204,7 @@ Accept wildcard characters: False
 
 ### -ManagedBy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ManagedBy parameter specifies an owner for the group. A group must have at least one owner. If you don't use this parameter to specify the owner when you create the group, the user account that created the group is the owner. The group owner is able to:
 
@@ -1254,7 +1254,7 @@ Accept wildcard characters: False
 
 ### -MaxReceiveSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1287,7 +1287,7 @@ Accept wildcard characters: False
 
 ### -MaxSendSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1320,7 +1320,7 @@ Accept wildcard characters: False
 
 ### -MemberDepartRestriction
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The MemberDepartRestriction parameter specifies the restrictions that you put on requests to leave the group. Valid values are:
 
@@ -1341,7 +1341,7 @@ Accept wildcard characters: False
 
 ### -MemberJoinRestriction
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The MemberJoinRestriction parameter specifies the restrictions that you put on requests to join the group. Valid values are:
 
@@ -1363,7 +1363,7 @@ Accept wildcard characters: False
 
 ### -ModeratedBy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ModeratedBy parameter specifies one or more moderators for this recipient. A moderator approves messages sent to the recipient before the messages are delivered. A moderator must be a mailbox, mail user, or mail contact in your organization. You can use any value that uniquely identifies the moderator. For example:
 
@@ -1396,7 +1396,7 @@ Accept wildcard characters: False
 
 ### -ModerationEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ModerationEnabled parameter specifies whether moderation is enabled for this recipient. Valid value are:
 
@@ -1419,7 +1419,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Name parameter specifies the unique name of the group. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -1437,7 +1437,7 @@ Accept wildcard characters: False
 
 ### -PrimarySmtpAddress
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The PrimarySmtpAddress parameter specifies the primary return email address that's used for the recipient. You can't use the EmailAddresses and PrimarySmtpAddress parameters in the same command.
 
@@ -1459,7 +1459,7 @@ Accept wildcard characters: False
 
 ### -RejectMessagesFrom
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The RejectMessagesFrom parameter specifies who isn't allowed to send messages to this recipient. Messages from these senders are rejected.
 
@@ -1494,7 +1494,7 @@ Accept wildcard characters: False
 
 ### -RejectMessagesFromDLMembers
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The RejectMessagesFromDLMembers parameter specifies who isn't allowed to send messages to this recipient. Messages from these senders are rejected.
 
@@ -1529,7 +1529,7 @@ Accept wildcard characters: False
 
 ### -RejectMessagesFromSendersOrMembers
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The RejectMessagesFromSendersOrMembers parameter specifies who isn't allowed to send messages to this recipient. Messages from these senders are rejected.
 
@@ -1566,7 +1566,7 @@ Accept wildcard characters: False
 
 ### -ReportToManagerEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ReportToManagerEnabled parameter specifies whether delivery status notifications (also known as DSNs, non-delivery reports, NDRs, or bounce messages) are sent to the owner (first one listed if more than one) of the group (defined by the ManagedBy property). Valid values are:
 
@@ -1589,7 +1589,7 @@ Accept wildcard characters: False
 
 ### -ReportToOriginatorEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ReportToOriginatorEnabled parameter specifies whether delivery status notifications (also known as DSNs, non-delivery reports, NDRs, or bounce messages) are sent to senders who send messages to this group. Valid values are:
 
@@ -1612,7 +1612,7 @@ Accept wildcard characters: False
 
 ### -RequireSenderAuthenticationEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The RequireSenderAuthenticationEnabled parameter specifies whether to accept messages only from authenticated (internal) senders. Valid values are:
 
@@ -1653,7 +1653,7 @@ Accept wildcard characters: False
 
 ### -RoomList
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The RoomList switch specifies that all members of this distribution group are room mailboxes. You don't need to specify a value with this switch.
 
@@ -1673,7 +1673,7 @@ Accept wildcard characters: False
 
 ### -SamAccountName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1693,7 +1693,7 @@ Accept wildcard characters: False
 
 ### -SendModerationNotifications
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The SendModerationNotifications parameter specifies when moderation notification messages are sent. Valid values are:
 
@@ -1717,7 +1717,7 @@ Accept wildcard characters: False
 
 ### -SendOofMessageToOriginatorEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The SendOofMessageToOriginatorEnabled parameter specifies how to handle out of office (OOF) messages for members of the group. Valid values are:
 
@@ -1738,7 +1738,7 @@ Accept wildcard characters: False
 
 ### -SimpleDisplayName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The SimpleDisplayName parameter is used to display an alternative description of the object when only a limited set of characters is permitted. Valid characters are:
 
@@ -1762,7 +1762,7 @@ Accept wildcard characters: False
 
 ### -UMDtmfMap
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1814,7 +1814,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
@@ -1832,7 +1832,7 @@ Accept wildcard characters: False
 
 ### -WindowsEmailAddress
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WindowsEmailAddress parameter specifies the Windows email address for this recipient. This is a common Active Directory attribute that's present in all environments, including environments without Exchange. Using the WindowsEmailAddress parameter on a recipient has one of the following results:
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-DlpPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-DlpPolicy.md
index 5229b5b8b3..40a9e4886b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-DlpPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-DlpPolicy.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -51,7 +51,7 @@ This example disables the DLP policy named Employee Numbers.
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the DLP policy that you want to modify. You can use any value that uniquely identifies the policy. For example:
 
@@ -73,7 +73,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -94,7 +94,7 @@ Accept wildcard characters: False
 
 ### -Description
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Description parameter specifies an optional description for the DLP policy.
 
@@ -112,7 +112,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -130,7 +130,7 @@ Accept wildcard characters: False
 
 ### -Mode
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Mode parameter specifies the action and notification level of the DLP policy. Valid values for this parameter are:
 
@@ -154,7 +154,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Name parameter specifies a unique name for the DLP policy.
 
@@ -172,7 +172,7 @@ Accept wildcard characters: False
 
 ### -State
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The State parameter enables or disables the DLP policy. Valid input for this parameter is Enabled or Disabled.
 
@@ -190,7 +190,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-DynamicDistributionGroup.md b/exchange/exchange-ps/ExchangePowerShell/Set-DynamicDistributionGroup.md
index 66ffc8fef1..436da59675 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-DynamicDistributionGroup.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-DynamicDistributionGroup.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
 Locale: en-US
@@ -153,7 +153,7 @@ This example applies the following changes to the existing dynamic distribution
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the dynamic distribution group that you want to modify. You can use any value that uniquely identifies the dynamic distribution group. For example:
 
@@ -178,7 +178,7 @@ Accept wildcard characters: False
 
 ### -AcceptMessagesOnlyFrom
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The AcceptMessagesOnlyFrom parameter specifies who is allowed to send messages to this recipient. Messages from other senders are rejected.
 
@@ -213,7 +213,7 @@ Accept wildcard characters: False
 
 ### -AcceptMessagesOnlyFromDLMembers
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The AcceptMessagesOnlyFromDLMembers parameter specifies who is allowed to send messages to this recipient. Messages from other senders are rejected.
 
@@ -248,7 +248,7 @@ Accept wildcard characters: False
 
 ### -AcceptMessagesOnlyFromSendersOrMembers
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The AcceptMessagesOnlyFromSendersOrMembers parameter specifies who is allowed to send messages to this recipient. Messages from other senders are rejected.
 
@@ -285,7 +285,7 @@ Accept wildcard characters: False
 
 ### -Alias
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Alias parameter specifies the Exchange alias (also known as the mail nickname) for the recipient. This value identifies the recipient as a mail-enabled object, and shouldn't be confused with multiple email addresses for the same recipient (also known as proxy addresses). A recipient can have only one Alias value. The maximum length is 64 characters.
 
@@ -321,7 +321,7 @@ Accept wildcard characters: False
 
 ### -ArbitrationMailbox
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -352,7 +352,7 @@ Accept wildcard characters: False
 
 ### -BypassModerationFromSendersOrMembers
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The BypassModerationFromSendersOrMembers parameter specifies who is allowed to send messages to this moderated recipient without approval from a moderator. Valid values for this parameter are individual senders and groups in your organization. Specifying a group means all members of the group are allowed to send messages to this recipient without approval from a moderator.
 
@@ -385,7 +385,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCompany
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ConditionalCompany parameter specifies a precanned filter that's based on the value of the recipient's Company property.
 
@@ -409,7 +409,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute1
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ConditionalCustomAttribute1 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute1 property. You can specify multiple values separated by commas.
 
@@ -433,7 +433,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute10
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ConditionalCustomAttribute10 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute10 property. You can specify multiple values separated by commas.
 
@@ -457,7 +457,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute11
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ConditionalCustomAttribute11 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute11 property. You can specify multiple values separated by commas.
 
@@ -481,7 +481,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute12
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ConditionalCustomAttribute12 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute12 property. You can specify multiple values separated by commas.
 
@@ -505,7 +505,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute13
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ConditionalCustomAttribute13 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute13 property. You can specify multiple values separated by commas.
 
@@ -529,7 +529,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute14
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ConditionalCustomAttribute14 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute14 property. You can specify multiple values separated by commas.
 
@@ -553,7 +553,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute15
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ConditionalCustomAttribute15 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute15 property. You can specify multiple values separated by commas.
 
@@ -577,7 +577,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute2
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ConditionalCustomAttribute2 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute2 property. You can specify multiple values separated by commas.
 
@@ -601,7 +601,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute3
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ConditionalCustomAttribute3 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute3 property. You can specify multiple values separated by commas.
 
@@ -625,7 +625,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute4
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ConditionalCustomAttribute4 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute4 property. You can specify multiple values separated by commas.
 
@@ -649,7 +649,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute5
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ConditionalCustomAttribute5 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute5 property. You can specify multiple values separated by commas.
 
@@ -673,7 +673,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute6
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ConditionalCustomAttribute6 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute6 property. You can specify multiple values separated by commas.
 
@@ -697,7 +697,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute7
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ConditionalCustomAttribute7 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute7 property. You can specify multiple values separated by commas.
 
@@ -721,7 +721,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute8
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ConditionalCustomAttribute8 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute8 property. You can specify multiple values separated by commas.
 
@@ -745,7 +745,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute9
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ConditionalCustomAttribute9 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute9 property. You can specify multiple values separated by commas.
 
@@ -769,7 +769,7 @@ Accept wildcard characters: False
 
 ### -ConditionalDepartment
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ConditionalDepartment parameter specifies a precanned filter that's based on the value of the recipient's Department property. You can specify multiple values separated by commas.
 
@@ -793,7 +793,7 @@ Accept wildcard characters: False
 
 ### -ConditionalStateOrProvince
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ConditionalStateOrProvince parameter specifies a precanned filter that's based on the value of the recipient's StateOrProvince property. You can specify multiple values separated by commas.
 
@@ -817,7 +817,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -838,7 +838,7 @@ Accept wildcard characters: False
 
 ### -CreateDTMFMap
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -861,7 +861,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute1
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the CustomAttribute1 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -879,7 +879,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute10
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the CustomAttribute10 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -897,7 +897,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute11
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the CustomAttribute11 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -915,7 +915,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute12
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the CustomAttribute12 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -933,7 +933,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute13
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the CustomAttribute13 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -951,7 +951,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute14
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the CustomAttribute14 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -969,7 +969,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute15
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the CustomAttribute15 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -987,7 +987,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute2
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the CustomAttribute2 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -1005,7 +1005,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute3
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the CustomAttribute3 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -1023,7 +1023,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute4
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the CustomAttribute4 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -1041,7 +1041,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute5
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the CustomAttribute5 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -1059,7 +1059,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute6
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the CustomAttribute6 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -1077,7 +1077,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute7
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the CustomAttribute7 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -1095,7 +1095,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute8
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the CustomAttribute8 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -1113,7 +1113,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute9
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the CustomAttribute9 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -1151,7 +1151,7 @@ Accept wildcard characters: False
 
 ### -DisplayName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The DisplayName parameter specifies the display name of the dynamic distribution group. The display name is visible in the Exchange admin center and in address lists. The maximum length is 256 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -1169,7 +1169,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1189,7 +1189,7 @@ Accept wildcard characters: False
 
 ### -EmailAddresses
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The EmailAddresses parameter specifies all email addresses (proxy addresses) for the recipient, including the primary SMTP address. In on-premises Exchange organizations, the primary SMTP address and other proxy addresses are typically set by email address policies. However, you can use this parameter to configure other proxy addresses for the recipient. For more information, see [Email address policies in Exchange Server](https://learn.microsoft.com/Exchange/email-addresses-and-address-books/email-address-policies/email-address-policies).
 
@@ -1228,7 +1228,7 @@ Accept wildcard characters: False
 
 ### -EmailAddressPolicyEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1251,7 +1251,7 @@ Accept wildcard characters: False
 
 ### -ExpansionServer
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1278,7 +1278,7 @@ Accept wildcard characters: False
 
 ### -ExtensionCustomAttribute1
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the ExtensionCustomAttribute1 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas.
 
@@ -1302,7 +1302,7 @@ Accept wildcard characters: False
 
 ### -ExtensionCustomAttribute2
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the ExtensionCustomAttribute2 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas.
 
@@ -1326,7 +1326,7 @@ Accept wildcard characters: False
 
 ### -ExtensionCustomAttribute3
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the ExtensionCustomAttribute3 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas.
 
@@ -1350,7 +1350,7 @@ Accept wildcard characters: False
 
 ### -ExtensionCustomAttribute4
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the ExtensionCustomAttribute4 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas.
 
@@ -1374,7 +1374,7 @@ Accept wildcard characters: False
 
 ### -ExtensionCustomAttribute5
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the ExtensionCustomAttribute5 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas.
 
@@ -1418,7 +1418,7 @@ Accept wildcard characters: False
 
 ### -ForceUpgrade
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ForceUpgrade switch suppresses the confirmation message that appears if the object was created in a previous version of Exchange. You don't need to specify a value with this switch.
 
@@ -1436,7 +1436,7 @@ Accept wildcard characters: False
 
 ### -GrantSendOnBehalfTo
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The GrantSendOnBehalfTo parameter specifies who can send on behalf of this dynamic distribution group. Although messages send on behalf of the group clearly show the sender in the From field (`<Sender> on behalf of <Group>`), replies to these messages are delivered to the group, not the sender.
 
@@ -1473,7 +1473,7 @@ Accept wildcard characters: False
 
 ### -HiddenFromAddressListsEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The HiddenFromAddressListsEnabled parameter specifies whether this recipient is visible in address lists. Valid values are:
 
@@ -1494,7 +1494,7 @@ Accept wildcard characters: False
 
 ### -IgnoreDefaultScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1519,7 +1519,7 @@ Accept wildcard characters: False
 
 ### -IncludedRecipients
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The IncludedRecipients parameter specifies a precanned filter that's based on the recipient type. Valid values are:
 
@@ -1546,7 +1546,7 @@ Accept wildcard characters: False
 
 ### -MailTip
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The MailTip parameter specifies the custom MailTip text for this recipient. The MailTip is shown to senders when they start drafting an email message to this recipient. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -1569,7 +1569,7 @@ Accept wildcard characters: False
 
 ### -MailTipTranslations
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The MailTipTranslations parameter specifies additional languages for the custom MailTip text that's defined by the MailTip parameter. HTML tags are automatically added to the MailTip translation, additional HTML tags aren't supported, and the length of the MailTip translation can't exceed 175 displayed characters.
 
@@ -1595,7 +1595,7 @@ Accept wildcard characters: False
 
 ### -ManagedBy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ManagedBy parameter specifies an owner for the group. A dynamic group can only have one owner. The group owner is able to:
 
@@ -1630,7 +1630,7 @@ Accept wildcard characters: False
 
 ### -MaxReceiveSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1663,7 +1663,7 @@ Accept wildcard characters: False
 
 ### -MaxSendSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1696,7 +1696,7 @@ Accept wildcard characters: False
 
 ### -ModeratedBy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ModeratedBy parameter specifies one or more moderators for this recipient. A moderator approves messages sent to the recipient before the messages are delivered. A moderator must be a mailbox, mail user, or mail contact in your organization. You can use any value that uniquely identifies the moderator. For example:
 
@@ -1727,7 +1727,7 @@ Accept wildcard characters: False
 
 ### -ModerationEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ModerationEnabled parameter specifies whether moderation is enabled for this recipient. Valid value are:
 
@@ -1750,7 +1750,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Name parameter specifies the unique name of the dynamic distribution group. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -1768,7 +1768,7 @@ Accept wildcard characters: False
 
 ### -Notes
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Notes parameters specifies additional information about the object. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -1786,7 +1786,7 @@ Accept wildcard characters: False
 
 ### -PhoneticDisplayName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The PhoneticDisplayName parameter specifies an alternate spelling of the user's name that's used for text to speech in Unified Messaging (UM) environments. Typically, you use this parameter when the pronunciation and spelling of the user's name don't match. The maximum length is 256 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -1804,7 +1804,7 @@ Accept wildcard characters: False
 
 ### -PrimarySmtpAddress
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The PrimarySmtpAddress parameter specifies the primary return email address that's used for the recipient. You can't use the EmailAddresses and PrimarySmtpAddress parameters in the same command.
 
@@ -1826,7 +1826,7 @@ Accept wildcard characters: False
 
 ### -RecipientContainer
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The RecipientContainer parameter specifies a filter that's based on the recipient's location in Active Directory. Valid input for this parameter is an organizational unit (OU) or domain that's returned by the Get-OrganizationalUnit cmdlet. You can use any value that uniquely identifies the OU or domain. For example:
 
@@ -1853,7 +1853,7 @@ Accept wildcard characters: False
 
 ### -RecipientFilter
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The RecipientFilter parameter specifies a custom OPATH filter that's based on the value of any available recipient property. You can use any available Windows PowerShell operator, and wildcards and partial matches are supported. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`.
 
@@ -1880,7 +1880,7 @@ Accept wildcard characters: False
 
 ### -RejectMessagesFrom
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The RejectMessagesFrom parameter specifies who isn't allowed to send messages to this recipient. Messages from these senders are rejected.
 
@@ -1915,7 +1915,7 @@ Accept wildcard characters: False
 
 ### -RejectMessagesFromDLMembers
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The RejectMessagesFromDLMembers parameter specifies who isn't allowed to send messages to this recipient. Messages from these senders are rejected.
 
@@ -1950,7 +1950,7 @@ Accept wildcard characters: False
 
 ### -RejectMessagesFromSendersOrMembers
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The RejectMessagesFromSendersOrMembers parameter specifies who isn't allowed to send messages to this recipient. Messages from these senders are rejected.
 
@@ -1987,7 +1987,7 @@ Accept wildcard characters: False
 
 ### -ReportToManagerEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ReportToManagerEnabled parameter specifies whether delivery status notifications (also known as DSNs, non-delivery reports, NDRs, or bounce messages) are sent to the owners of the group (defined by the ManagedBy property). Valid values are:
 
@@ -2010,7 +2010,7 @@ Accept wildcard characters: False
 
 ### -ReportToOriginatorEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ReportToOriginatorEnabled parameter specifies whether delivery status notifications (also known as DSNs, non-delivery reports, NDRs, or bounce messages) are sent to senders who send messages to this group. Valid values are:
 
@@ -2033,7 +2033,7 @@ Accept wildcard characters: False
 
 ### -RequireSenderAuthenticationEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The RequireSenderAuthenticationEnabled parameter specifies whether to accept messages only from authenticated (internal) senders. Valid values are:
 
@@ -2054,7 +2054,7 @@ Accept wildcard characters: False
 
 ### -SendModerationNotifications
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The SendModerationNotifications parameter specifies when moderation notification messages are sent. Valid values are:
 
@@ -2078,7 +2078,7 @@ Accept wildcard characters: False
 
 ### -SendOofMessageToOriginatorEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The SendOofMessageToOriginatorEnabled parameter specifies how to handle out of office (OOF) messages for members of the group. Valid values are:
 
@@ -2099,7 +2099,7 @@ Accept wildcard characters: False
 
 ### -SimpleDisplayName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The SimpleDisplayName parameter is used to display an alternative description of the object when only a limited set of characters is permitted. Valid characters are:
 
@@ -2123,7 +2123,7 @@ Accept wildcard characters: False
 
 ### -UMDtmfMap
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -2175,7 +2175,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
@@ -2193,7 +2193,7 @@ Accept wildcard characters: False
 
 ### -WindowsEmailAddress
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WindowsEmailAddress parameter specifies the Windows email address for this recipient. This is a common Active Directory attribute that's present in all environments, including environments without Exchange. Using the WindowsEmailAddress parameter on a recipient has one of the following results:
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-EcpVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Set-EcpVirtualDirectory.md
index dfc2e8dfb3..7ef6fa85ed 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-EcpVirtualDirectory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-EcpVirtualDirectory.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -69,7 +69,7 @@ This example turns off the Internet access to the EAC on server named Server01.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the ECP virtual directory that you want to modify. You can use any value that uniquely identifies the virtual directory. For example:
 
@@ -95,7 +95,7 @@ Accept wildcard characters: False
 
 ### -AdfsAuthentication
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AdfsAuthentication parameter specifies that the ECP virtual directory allows users to authenticate through Active Directory Federation Services (AD FS) authentication. This parameter accepts $true or $false. The default value is $false.
 
@@ -115,7 +115,7 @@ Accept wildcard characters: False
 
 ### -AdminEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AdminEnabled parameter specifies that the EAC isn't able to be accessed through the Internet. For more information, see [Turn off access to the Exchange admin center](https://learn.microsoft.com/Exchange/architecture/client-access/disable-exchange-admin-center-access). This parameter accepts $true or $false.
 
@@ -133,7 +133,7 @@ Accept wildcard characters: False
 
 ### -BasicAuthentication
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The BasicAuthentication parameter specifies whether Basic authentication is enabled on the virtual directory. Valid values are:
 
@@ -156,7 +156,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -177,7 +177,7 @@ Accept wildcard characters: False
 
 ### -DigestAuthentication
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DigestAuthentication parameter specifies whether Digest authentication is enabled on the virtual directory. Valid values are:
 
@@ -198,7 +198,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -216,7 +216,7 @@ Accept wildcard characters: False
 
 ### -ExtendedProtectionFlags
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExtendedProtectionFlags parameter specifies custom settings for Extended Protection for Authentication on the virtual directory. Valid values are:
 
@@ -240,7 +240,7 @@ Accept wildcard characters: False
 
 ### -ExtendedProtectionSPNList
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExtendedProtectionSPNList parameter specifies a list of valid Service Principal Names (SPNs) if you're using Extended Protection for Authentication on the virtual directory. Valid values are:
 
@@ -261,7 +261,7 @@ Accept wildcard characters: False
 
 ### -ExtendedProtectionTokenChecking
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExtendedProtectionTokenChecking parameter defines how you want to use Extended Protection for Authentication on the virtual directory. Extended Protection for Authentication isn't enabled by default. Valid values are:
 
@@ -285,7 +285,7 @@ Accept wildcard characters: False
 
 ### -ExternalAuthenticationMethods
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExternalAuthenticationMethods parameter specifies the authentication methods supported on the Exchange server from outside the firewall.
 
@@ -303,7 +303,7 @@ Accept wildcard characters: False
 
 ### -ExternalUrl
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExternalURL parameter specifies the URL that's used to connect to the virtual directory from outside the firewall.
 
@@ -323,7 +323,7 @@ Accept wildcard characters: False
 
 ### -FormsAuthentication
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The FormsAuthentication parameter specifies whether forms-based authentication is enabled on the ECP virtual directory. Valid values are:
 
@@ -344,7 +344,7 @@ Accept wildcard characters: False
 
 ### -GzipLevel
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The GzipLevel parameter sets Gzip configuration information for the ECP virtual directory.
 
@@ -362,7 +362,7 @@ Accept wildcard characters: False
 
 ### -InternalUrl
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The InternalURL parameter specifies the URL that's used to connect to the virtual directory from inside the firewall.
 
@@ -382,7 +382,7 @@ Accept wildcard characters: False
 
 ### -OAuthAuthentication
 
-> Applicable: Exchange Server 2019
+> Applicable: Exchange Server 2019, Exchange Server SE
 
 {{ Fill OAuthAuthentication Description }}
 
@@ -400,7 +400,7 @@ Accept wildcard characters: False
 
 ### -OwaOptionsEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The OwaOptionsEnabled parameter specifies that Outlook on the web Options is enabled for end users. If this parameter is set to $false, users aren't able to access Outlook on the web Options. You might want to disable access if your organization uses non-Microsoft provider tools. This parameter accepts $true or $false.
 
@@ -418,7 +418,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
@@ -436,7 +436,7 @@ Accept wildcard characters: False
 
 ### -WindowsAuthentication
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WindowsAuthentication parameter specifies whether Integrated Windows authentication is enabled on the virtual directory. Valid values are:
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-EdgeSyncServiceConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-EdgeSyncServiceConfig.md
index 46b76be6cb..12e35df0ce 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-EdgeSyncServiceConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-EdgeSyncServiceConfig.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -67,7 +67,7 @@ The log files are kept for 3 days.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the name of the Microsoft Exchange EdgeSync service you want to configure.
 
@@ -85,7 +85,7 @@ Accept wildcard characters: False
 
 ### -ConfigurationSyncInterval
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ConfigurationSyncInterval parameter specifies how frequently the Microsoft Exchange EdgeSync service synchronizes configuration data. The default value is 3 minutes.
 
@@ -105,7 +105,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -126,7 +126,7 @@ Accept wildcard characters: False
 
 ### -CookieValidDuration
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The CookieValidDuration parameter specifies how long a cookie record is valid. The default value is 21 days.
 
@@ -146,7 +146,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -164,7 +164,7 @@ Accept wildcard characters: False
 
 ### -FailoverDCInterval
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The FailoverDCInterval parameter specifies how long EdgeSync waits before failing over to another domain controller if it can't read configuration data from Active Directory. The default value is 5 minutes.
 
@@ -184,7 +184,7 @@ Accept wildcard characters: False
 
 ### -LockDuration
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The LockDuration parameter specifies how long an instance of the Microsoft Exchange EdgeSync service can maintain an exclusive lock on the synchronization rights. While an EdgeSync service maintains an exclusive lock on synchronization rights, no other EdgeSync service can take over synchronization. The default value is 6 minutes.
 
@@ -204,7 +204,7 @@ Accept wildcard characters: False
 
 ### -LockRenewalDuration
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The LockRenewalDuration parameter specifies how long before the expiry of an exclusive lock an EdgeSync service can renew the lock. The default value is 4 minutes.
 
@@ -224,7 +224,7 @@ Accept wildcard characters: False
 
 ### -LogEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The LogEnabled parameter specifies enables or disables the EdgeSyncLog. Valid input for this parameter is $true or $false. The default value is $true.
 
@@ -242,7 +242,7 @@ Accept wildcard characters: False
 
 ### -LogLevel
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The LogLevel parameter specifies the EdgeSync logging level. Valid values are:
 
@@ -265,7 +265,7 @@ Accept wildcard characters: False
 
 ### -LogMaxAge
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The LogMaxAge parameter specifies the maximum duration in days to keep the EdgeSyncLog files. Log files older than the specified value can be overwritten. The default value is 30 days.
 
@@ -285,7 +285,7 @@ Accept wildcard characters: False
 
 ### -LogMaxDirectorySize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The LogMaxDirectorySize specifies the maximum amount of disk space the EdgeSyncLog directory can use. The default value is 250 MB.
 
@@ -315,7 +315,7 @@ Accept wildcard characters: False
 
 ### -LogMaxFileSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The LogMaxFileSize parameter specifies the maximum log file size for the EdgeSyncLog files. The default value is 10 MB.
 
@@ -345,7 +345,7 @@ Accept wildcard characters: False
 
 ### -LogPath
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The LogPath parameter specifies the disk location to store the EdgeSyncLog files. The default value is TransportRoles\\Logs\\EdgeSync\\.
 
@@ -363,7 +363,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Name parameter specifies a unique name for the EdgeSync service configuration.
 
@@ -381,7 +381,7 @@ Accept wildcard characters: False
 
 ### -OptionDuration
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The OptionDuration parameter specifies how long an instance of the Microsoft Exchange EdgeSync service can maintain an optional lock on the synchronization rights. While an EdgeSync service maintains an optional lock on synchronization rights, another EdgeSync service can take over synchronization after the optional lock has expired if it's initiated using the Start-EdgeSynchronization command. The default value is 30 minutes.
 
@@ -401,7 +401,7 @@ Accept wildcard characters: False
 
 ### -RecipientSyncInterval
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RecipientSyncInterval parameter specifies how frequently the Microsoft Exchange EdgeSync service synchronizes recipient data from the global catalog. The default value is 5 minutes.
 
@@ -421,7 +421,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-EmailAddressPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-EmailAddressPolicy.md
index 1c7aeb2dd0..0e369a50c4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-EmailAddressPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-EmailAddressPolicy.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -98,7 +98,7 @@ In Exchange Online, this example modifies the existing email address policy name
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the email address policy that you want to modify. You can use any value that uniquely identifies the policy. For example:
 
@@ -120,7 +120,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCompany
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -146,7 +146,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute1
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -172,7 +172,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute10
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -198,7 +198,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute11
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -224,7 +224,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute12
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -250,7 +250,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute13
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -276,7 +276,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute14
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -302,7 +302,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute15
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -328,7 +328,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute2
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -354,7 +354,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute3
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -380,7 +380,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute4
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -406,7 +406,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute5
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -432,7 +432,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute6
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -458,7 +458,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute7
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -484,7 +484,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute8
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -510,7 +510,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute9
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -536,7 +536,7 @@ Accept wildcard characters: False
 
 ### -ConditionalDepartment
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -562,7 +562,7 @@ Accept wildcard characters: False
 
 ### -ConditionalStateOrProvince
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -588,7 +588,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -609,7 +609,7 @@ Accept wildcard characters: False
 
 ### -DisabledEmailAddressTemplates
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -638,7 +638,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -658,7 +658,7 @@ Accept wildcard characters: False
 
 ### -EnabledEmailAddressTemplates
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The EnabledEmailAddressTemplates parameter specifies the rules in the email address policy that are used to generate email addresses for recipients.
 
@@ -689,7 +689,7 @@ Accept wildcard characters: False
 
 ### -EnabledPrimarySMTPAddressTemplate
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The EnabledPrimarySMTPAddressTemplate parameter specifies the rule in the email address policy that's used to generate the primary SMTP email addresses for recipients. You can use this parameter instead of the EnabledEmailAddressTemplates if the policy only applies the primary email address and no additional proxy addresses.
 
@@ -713,7 +713,7 @@ Accept wildcard characters: False
 
 ### -ForceUpgrade
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ForceUpgrade switch suppresses the confirmation message that appears if the object was created in a previous version of Exchange. You don't need to specify a value with this switch.
 
@@ -731,7 +731,7 @@ Accept wildcard characters: False
 
 ### -IncludedRecipients
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -760,7 +760,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Name parameter specifies the unique name for the email address policy. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -778,7 +778,7 @@ Accept wildcard characters: False
 
 ### -Priority
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Priority parameter specifies the order that the email address policies are evaluated. By default, every time that you add a new email address policy, the policy is assigned a priority of N+1, where N is the number of email address policies that you've created.
 
@@ -800,7 +800,7 @@ Accept wildcard characters: False
 
 ### -RecipientContainer
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -827,7 +827,7 @@ Accept wildcard characters: False
 
 ### -RecipientFilter
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -855,7 +855,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-EventLogLevel.md b/exchange/exchange-ps/ExchangePowerShell/Set-EventLogLevel.md
index 79703e4588..cf382d401a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-EventLogLevel.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-EventLogLevel.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -46,7 +46,7 @@ This example sets the event log level to High for the MSExchangeTransport\\SmtpR
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the name of the event logging category for which you want to set the event logging level.
 
@@ -64,7 +64,7 @@ Accept wildcard characters: False
 
 ### -Level
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Level parameter specifies the log level for the specific event logging category. The valid values are:
 
@@ -88,7 +88,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -109,7 +109,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeAssistanceConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeAssistanceConfig.md
index c8d43e777b..42f439b1a1 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeAssistanceConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeAssistanceConfig.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -62,7 +62,7 @@ This example changes the Help location for the Exchange admin center.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -80,7 +80,7 @@ Accept wildcard characters: False
 
 ### -CommunityLinkDisplayEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -98,7 +98,7 @@ Accept wildcard characters: False
 
 ### -CommunityURL
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -116,7 +116,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -137,7 +137,7 @@ Accept wildcard characters: False
 
 ### -ControlPanelFeedbackEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -155,7 +155,7 @@ Accept wildcard characters: False
 
 ### -ControlPanelFeedbackURL
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -173,7 +173,7 @@ Accept wildcard characters: False
 
 ### -ControlPanelHelpURL
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ControlPanelHelpURL parameter specifies the URL where help for the Exchange admin center (EAC) is hosted.
 
@@ -191,7 +191,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -211,7 +211,7 @@ Accept wildcard characters: False
 
 ### -ExchangeHelpAppOnline
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExchangeHelpAppOnline specifies whether your organization uses the public help that's hosted by Microsoft. Valid values are:
 
@@ -232,7 +232,7 @@ Accept wildcard characters: False
 
 ### -ManagementConsoleFeedbackEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -250,7 +250,7 @@ Accept wildcard characters: False
 
 ### -ManagementConsoleFeedbackURL
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -268,7 +268,7 @@ Accept wildcard characters: False
 
 ### -ManagementConsoleHelpURL
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ManagementConsoleHelpURL parameter specifies the URL where help for the Exchange Management Console (EMC) is hosted.
 
@@ -286,7 +286,7 @@ Accept wildcard characters: False
 
 ### -OWAFeedbackEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -304,7 +304,7 @@ Accept wildcard characters: False
 
 ### -OWAFeedbackURL
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -322,7 +322,7 @@ Accept wildcard characters: False
 
 ### -OWAHelpURL
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The OWAHelpURL parameter specifies the URL for where help for the standard version of Outlook on the web is hosted.
 
@@ -340,7 +340,7 @@ Accept wildcard characters: False
 
 ### -OWALightFeedbackEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -358,7 +358,7 @@ Accept wildcard characters: False
 
 ### -OWALightFeedbackURL
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -376,7 +376,7 @@ Accept wildcard characters: False
 
 ### -OWALightHelpURL
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The OWALightHelpURL parameter specifies the URL for where help for the light version of Outlook on the web is hosted.
 
@@ -394,7 +394,7 @@ Accept wildcard characters: False
 
 ### -PrivacyLinkDisplayEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -412,7 +412,7 @@ Accept wildcard characters: False
 
 ### -PrivacyStatementURL
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -430,7 +430,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeFeature.md b/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeFeature.md
index fd7e59be88..a2e2cc0c75 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeFeature.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeFeature.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2019
+applicable: Exchange Server 2019, Exchange Server SE
 author: lusassl-msft
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -64,7 +64,7 @@ This example blocks the features F1.1.1, F1.2.1, and F2.1.1 on the computer name
 
 ### -Identity
 
-> Applicable: Exchange Server 2019
+> Applicable: Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the Exchange server that you want to modify. You can use any value that uniquely identifies the server. For example:
 
@@ -87,7 +87,7 @@ Accept wildcard characters: False
 
 ### -Approve
 
-> Applicable: Exchange Server 2019
+> Applicable: Exchange Server 2019, Exchange Server SE
 
 The Approve switch approves the feature specified by the FeatureID parameter. You don't need to specify a value with this switch.
 
@@ -105,7 +105,7 @@ Accept wildcard characters: False
 
 ### -Block
 
-> Applicable: Exchange Server 2019
+> Applicable: Exchange Server 2019, Exchange Server SE
 
 The Block switch blocks the feature specified by the FeatureID parameter. You don't need to specify a value with this switch.
 
@@ -123,7 +123,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2019
+> Applicable: Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -144,7 +144,7 @@ Accept wildcard characters: False
 
 ### -FeatureID
 
-> Applicable: Exchange Server 2019
+> Applicable: Exchange Server 2019, Exchange Server SE
 
 The FeatureID parameter specifies the feature you want to control.
 
@@ -162,7 +162,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2019
+> Applicable: Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeServer.md b/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeServer.md
index d57443c90a..81bec36dcd 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeServer.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeServer.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -76,7 +76,7 @@ This example removes an Exchange server from the Customer Experience Improvement
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the Exchange server that you want to modify. You can use any value that uniquely identifies the server. For example:
 
@@ -99,7 +99,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -120,7 +120,7 @@ Accept wildcard characters: False
 
 ### -CustomerFeedbackEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The CustomerFeedbackEnabled parameter specifies whether the Exchange server is enrolled in the Microsoft Customer Experience Improvement Program (CEIP). The CEIP collects anonymous information about how you use Exchange and problems that you might encounter. If you decide not to participate in the CEIP, the servers are opted-out automatically.
 
@@ -138,7 +138,7 @@ Accept wildcard characters: False
 
 ### -DataCollectionEnabled
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DataCollectionEnabled parameter specifies whether the EM Service collects and send diagnostic data to Microsoft using OCS. Valid values are:
 
@@ -159,7 +159,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -179,7 +179,7 @@ Accept wildcard characters: False
 
 ### -ErrorReportingEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ErrorReportingEnabled parameter specifies whether error reporting is enabled.
 
@@ -197,7 +197,7 @@ Accept wildcard characters: False
 
 ### -InternetWebProxy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The InternetWebProxy parameter specifies the web proxy server that the Exchange server uses to reach the internet. A valid value for this parameter is the URL of the web proxy server.
 
@@ -217,7 +217,7 @@ Accept wildcard characters: False
 
 ### -InternetWebProxyBypassList
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The InternetWebProxyBypassList parameter specifies a list of servers that bypass the web proxy server specified by the InternetWebProxy parameter. You identify the servers by their FQDN (for example, server01.contoso.com).
 
@@ -239,7 +239,7 @@ Accept wildcard characters: False
 
 ### -MitigationsApplied
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 Do not use this parameter. The EM service uses this parameter to store and track mitigation status.
 
@@ -257,7 +257,7 @@ Accept wildcard characters: False
 
 ### -MitigationsBlocked
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MitigationsBlocked parameter specifies a list of mitigations that are blocked. The Mitigation IDs present in this list are not applied by EM service in its hourly run.
 
@@ -277,7 +277,7 @@ Accept wildcard characters: False
 
 ### -MitigationsEnabled
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MitigationsEnabled parameter specifies whether the Exchange Emergency Mitigation service (EM service) automatically applies mitigations on the Exchange server. Valid values are:
 
@@ -300,7 +300,7 @@ Accept wildcard characters: False
 
 ### -MonitoringGroup
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MonitoringGroup parameter specifies how to add your Exchange servers to monitoring groups. You can add your servers to an existing group or create a monitoring group based on location or deployment, or to partition monitoring responsibility among your servers.
 
@@ -318,7 +318,7 @@ Accept wildcard characters: False
 
 ### -ProductKey
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ProductKey parameter specifies the server product key.
 
@@ -336,7 +336,7 @@ Accept wildcard characters: False
 
 ### -RingLevel
 
-> Applicable: Exchange Server 2019
+> Applicable: Exchange Server 2019, Exchange Server SE
 
 The RingLevel parameter specifies the server ring level that's used by the Feature Flighting feature.
 
@@ -354,7 +354,7 @@ Accept wildcard characters: False
 
 ### -StaticConfigDomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The StaticConfigDomainController parameter specifies whether to configure a domain controller to be used by the server via Directory Service Access (DSAccess).
 
@@ -372,7 +372,7 @@ Accept wildcard characters: False
 
 ### -StaticDomainControllers
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The StaticDomainControllers parameter specifies whether to configure a list of domain controllers to be used by the server via DSAccess.
 
@@ -390,7 +390,7 @@ Accept wildcard characters: False
 
 ### -StaticExcludedDomainControllers
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The StaticExcludedDomainControllers parameter specifies whether to exclude a list of domain controllers from being used by the server.
 
@@ -408,7 +408,7 @@ Accept wildcard characters: False
 
 ### -StaticGlobalCatalogs
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The StaticGlobalCatalogs parameter specifies whether to configure a list of global catalogs to be used by the server via DSAccess.
 
@@ -426,7 +426,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeSettings.md b/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeSettings.md
index 82fde1fc28..844d0b9c78 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeSettings.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeSettings.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -209,7 +209,7 @@ This example allows users to see the results of Unified Audit Logging. This exam
 
 ### -Identity
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the name of the existing Exchange settings object that contains the Exchange settings that you want to configure.
 
@@ -229,7 +229,7 @@ Accept wildcard characters: False
 
 ### -ClearHistory
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ClearHistory switch specifies that you want to clear the entries in the modification history for the Exchange setting object. You don't need to specify a value with this switch.
 
@@ -247,7 +247,7 @@ Accept wildcard characters: False
 
 ### -ConfigName
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ConfigName parameter specifies the available Exchange setting that you want to add, remove, or update in the Exchange settings object. Valid values for this parameter are determined by the configuration schema that was specified by the Name parameter on the New-ExchangeSettings cmdlet.
 
@@ -267,7 +267,7 @@ Accept wildcard characters: False
 
 ### -ConfigPairs
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ConfigName parameter specifies the available Exchange setting that you want to add, remove, or update in the Exchange settings object. Valid values for this parameter are determined by the configuration schema that was specified by the Name parameter on the New-ExchangeSettings cmdlet. The syntax for a value is `<Key>=<Value>`. You can separate multiple values separated by commas.
 
@@ -287,7 +287,7 @@ Accept wildcard characters: False
 
 ### -ConfigValue
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ConfigValue parameter specifies the value for the Exchange setting that you specified with the ConfigName parameter. The values are determined by the type of setting (a number, a timespan, $true or $false, etc.).
 
@@ -307,7 +307,7 @@ Accept wildcard characters: False
 
 ### -CreateSettingsGroup
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The CreateSettingsGroup switch specifies that you're creating an Exchange settings group, which is a group of related Exchange settings. You don't need to specify a value with this switch.
 
@@ -327,7 +327,7 @@ Accept wildcard characters: False
 
 ### -ExpirationDate
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExpirationDate parameter specifies the end date/time of the Exchange settings that are defined by the specified Exchange settings group.
 
@@ -349,7 +349,7 @@ Accept wildcard characters: False
 
 ### -GuidMatch
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The GuidMatch parameter specifies the scope of an Exchange settings group based on the GUID of the object (for example, the GUID of the mailbox database). This parameter is available for use with all Scope parameter values other than Forest.
 
@@ -371,7 +371,7 @@ Accept wildcard characters: False
 
 ### -Reason
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Reason parameter specifies a description for why the Exchange setting or settings group was created or modified. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -389,7 +389,7 @@ Accept wildcard characters: False
 
 ### -RemoveSetting
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RemoveSetting switch specifies that you're removing an existing Exchange setting from an Exchange settings object. You don't need to specify a value with this switch.
 
@@ -409,7 +409,7 @@ Accept wildcard characters: False
 
 ### -RemoveSettingsGroup
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RemoveSettingsGroup switch specifies that you're removing an Exchange settings group. You don't need to specify a value with this switch.
 
@@ -429,7 +429,7 @@ Accept wildcard characters: False
 
 ### -SettingsGroup
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SettingsGroup parameter specifies an existing Exchange settings group that's used to create a new settings group, or modify an existing settings group.
 
@@ -449,7 +449,7 @@ Accept wildcard characters: False
 
 ### -UpdateSetting
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The UpdateSetting switch specifies that you're updating an Exchange setting in an existing Exchange settings object. You don't need to specify a value with this switch.
 
@@ -469,7 +469,7 @@ Accept wildcard characters: False
 
 ### -UpdateSettingsGroup
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The UpdateSettingsGroup switch specifies that you're modifying an Exchange settings group. You don't need to specify a value with this switch.
 
@@ -489,7 +489,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -512,7 +512,7 @@ Accept wildcard characters: False
 
 ### -Disable
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Disable switch specifies that the Exchange settings group is disabled. You don't need to specify a value with this switch.
 
@@ -534,7 +534,7 @@ Accept wildcard characters: False
 
 ### -DisableGroup
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DisableGroup parameter specifies the name of the enabled Exchange settings group that you want to disable. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -554,7 +554,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -572,7 +572,7 @@ Accept wildcard characters: False
 
 ### -EnableGroup
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The EnableGroup parameter specifies the name of the disabled Exchange settings group that you want to enable. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -592,7 +592,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -612,7 +612,7 @@ Accept wildcard characters: False
 
 ### -GenericScopeName
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The GenericScopeName parameter specifies the name of the scope. The available values are determined by the schema of the Exchange setting object.
 
@@ -630,7 +630,7 @@ Accept wildcard characters: False
 
 ### -GenericScopeValue
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The GenericScopeValue parameter specifies the value of the scope specified by the GenericScopeName parameter. The available values are determined by the schema of the Exchange setting object.
 
@@ -648,7 +648,7 @@ Accept wildcard characters: False
 
 ### -GroupName
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The GroupName parameter specifies the name of the Exchange settings group in group operations. For example:
 
@@ -673,7 +673,7 @@ Accept wildcard characters: False
 
 ### -MaxVersion
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MaxVersion parameter specifies the scope of an Exchange settings group based on the version of the object (for example, the version of Exchange that's installed on the server). This parameter is available for use with all Scope parameter values other than Forest.
 
@@ -695,7 +695,7 @@ Accept wildcard characters: False
 
 ### -MinVersion
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MinVersion parameter specifies the scope of an Exchange settings group based on the version of the object (for example, the version of Exchange that's installed on the server). This parameter is available for use with all Scope parameter values other than Forest.
 
@@ -717,7 +717,7 @@ Accept wildcard characters: False
 
 ### -NameMatch
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The NameMatch parameter specifies the scope of an Exchange settings group based on the name of the object (for example, the process name). This parameter is available for use with all Scope parameter values other than Forest.
 
@@ -739,7 +739,7 @@ Accept wildcard characters: False
 
 ### -Priority
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Priority parameter specifies the priority of an Exchange settings group. The priority value for every group must be unique. A lower priority value indicates a higher priority.
 
@@ -757,7 +757,7 @@ Accept wildcard characters: False
 
 ### -Scope
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Scope parameter specifies the scope of the Exchange settings object. Valid values are:
 
@@ -784,7 +784,7 @@ Accept wildcard characters: False
 
 ### -ScopeFilter
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ScopeFilter parameter uses OPATH filter syntax to specify the scope of an Exchange settings group based. The syntax is `"Property -ComparisonOperator 'Value'"` (for example, `"ServerRole -like 'Mailbox*'"`).
 
@@ -815,7 +815,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-FederatedOrganizationIdentifier.md b/exchange/exchange-ps/ExchangePowerShell/Set-FederatedOrganizationIdentifier.md
index 2f88fa08ee..3af3c01013 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-FederatedOrganizationIdentifier.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-FederatedOrganizationIdentifier.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
 Locale: en-US
@@ -70,7 +70,7 @@ This example enables the organization identifier. This enables federation for th
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the federated organization identifier.
 
@@ -88,7 +88,7 @@ Accept wildcard characters: False
 
 ### -AccountNamespace
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The AccountNamespace parameter specifies the federated domain to be used to establish the organization identifier with the Microsoft Federation Gateway.
 
@@ -106,7 +106,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -127,7 +127,7 @@ Accept wildcard characters: False
 
 ### -DefaultDomain
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The DefaultDomain parameter specifies the federated domain used for delegation tokens issued by the Microsoft Federation Gateway for user accounts in the Exchange organization. If the DefaultDomain parameter isn't set, the primary SMTP domain for each user account is used in delegation tokens issued by the Microsoft Federation Gateway. Only a single domain or subdomain for the Exchange organization should be configured, and it applies to all delegation tokens issued for the Exchange organization, for example, contoso.com.
 
@@ -145,7 +145,7 @@ Accept wildcard characters: False
 
 ### -DelegationFederationTrust
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The DelegationFederationTrust parameter specifies the identity of the federation trust to be used by the organization identifier.
 
@@ -163,7 +163,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -183,7 +183,7 @@ Accept wildcard characters: False
 
 ### -Enabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Enabled parameter specifies whether the organization identifier is enabled. Valid values include $true or $false.
 
@@ -203,7 +203,7 @@ Accept wildcard characters: False
 
 ### -OrganizationContact
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The OrganizationContact parameter specifies the SMTP address of the federation contact.
 
@@ -221,7 +221,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-FederationTrust.md b/exchange/exchange-ps/ExchangePowerShell/Set-FederationTrust.md
index 9906bb2479..1f2bdd24ad 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-FederationTrust.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-FederationTrust.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
 Locale: en-US
@@ -90,7 +90,7 @@ Before you configure a federation trust to use the next certificate as the curre
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the name of the federation trust being modified.
 
@@ -110,7 +110,7 @@ Accept wildcard characters: False
 
 ### -ApplicationUri
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ApplicationUri parameter specifies the primary domain used for the federation organization identifier.
 
@@ -128,7 +128,7 @@ Accept wildcard characters: False
 
 ### -PublishFederationCertificate
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PublishFederationCertificate switch specifies the next certificate as the current certificate for the federation trust and publishes it to the Microsoft Federation Gateway. You don't need to specify a value with this switch.
 
@@ -150,7 +150,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -171,7 +171,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -189,7 +189,7 @@ Accept wildcard characters: False
 
 ### -MetadataUrl
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MetadataUrl parameter specifies the URL where WS-FederationMetadata is published by the Microsoft Federation Gateway.
 
@@ -207,7 +207,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Name parameter specifies a name for the federation trust.
 
@@ -225,7 +225,7 @@ Accept wildcard characters: False
 
 ### -RefreshMetadata
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RefreshMetadata switch specifies that the metadata document and certificate is retrieved again from the Microsoft Federation Gateway. You don't need to specify a value with this switch.
 
@@ -243,7 +243,7 @@ Accept wildcard characters: False
 
 ### -Thumbprint
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Thumbprint parameter specifies the thumbprint of the X.509 certificate to be configured as the next certificate for the federation trust. After the certificate is deployed on all Exchange servers in the organization, you can use the PublishFederationCertificate switch to configure the trust to use this certificate.
 
@@ -261,7 +261,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ForeignConnector.md b/exchange/exchange-ps/ExchangePowerShell/Set-ForeignConnector.md
index 39b7e32309..6c5fbc08ee 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ForeignConnector.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ForeignConnector.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -58,7 +58,7 @@ This example configures a 10 MB message size limit on the existing Foreign conne
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the Foreign connector that you want to modify. The Identity parameter can take any of the following values for the Foreign connector object:
 
@@ -80,7 +80,7 @@ Accept wildcard characters: False
 
 ### -AddressSpaces
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AddressSpaces parameter specifies the domain names to which the Foreign connector sends messages. The complete syntax for entering each address space is: `AddressSpaceType:AddressSpace;AddressSpaceCost`.
 
@@ -113,7 +113,7 @@ Accept wildcard characters: False
 
 ### -Comment
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Comment parameter specifies an optional comment. If you specify a value that contains spaces, enclose the value in quotation marks ("), for example: "This is an admin note".
 
@@ -131,7 +131,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -152,7 +152,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -172,7 +172,7 @@ Accept wildcard characters: False
 
 ### -DropDirectory
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DropDirectory parameter specifies the name of the Drop directory used by this Foreign connector. All outbound messages sent to address spaces defined by this Foreign connector are put in the specified Drop directory. The location of the Drop directory for each Foreign connector is controlled by the following two items:
 
@@ -205,7 +205,7 @@ Accept wildcard characters: False
 
 ### -DropDirectoryQuota
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DropDirectoryQuota parameter specifies the maximum size of all message files in the Drop directory. When the specified value is reached, no new message files can be copied into the Drop directory until the existing messages are delivered and deleted.
 
@@ -235,7 +235,7 @@ Accept wildcard characters: False
 
 ### -Enabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Enabled parameter specifies whether to enable the Foreign connector. The valid values are $true or $false. The default value is $true.
 
@@ -253,7 +253,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -273,7 +273,7 @@ Accept wildcard characters: False
 
 ### -IsScopedConnector
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IsScopedConnector parameter specifies the availability of the connector to other Mailbox servers. When the value of this parameter is $false, the connector can be used by all Mailbox servers in the Exchange organization. When the value of this parameter is $true, the connector can be used only by Mailbox servers in the same Active Directory site. The default value is $false.
 
@@ -291,7 +291,7 @@ Accept wildcard characters: False
 
 ### -MaxMessageSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MaxMessageSize parameter specifies the maximum size of a message that can pass through this Foreign connector.
 
@@ -321,7 +321,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Name parameter specifies a descriptive name for the Foreign connector.
 
@@ -339,7 +339,7 @@ Accept wildcard characters: False
 
 ### -RelayDsnRequired
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RelayDsnRequired parameter specifies whether a Relay delivery status notification (DSN) is required by the Foreign connector when messages are written to the Drop directory. The valid input values for this parameter are $true or $false. The default value is $false.
 
@@ -357,7 +357,7 @@ Accept wildcard characters: False
 
 ### -SourceTransportServers
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SourceTransportServers parameter specifies the names of the Mailbox servers that use this Foreign connector. Having a single Foreign connector homed on multiple Mailbox servers running the Transport service provides fault tolerance and high availability if one of the servers fails. The default value of this parameter is the name of the Mailbox server on which this Foreign connector was first installed.
 
@@ -379,7 +379,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-FrontendTransportService.md b/exchange/exchange-ps/ExchangePowerShell/Set-FrontendTransportService.md
index d9a3a5221e..bdbf2666e0 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-FrontendTransportService.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-FrontendTransportService.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -94,7 +94,7 @@ This example sets the ReceiveProtocolLogPath parameter to C:\\SMTP Protocol Logs
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the server that you want to modify.
 
@@ -112,7 +112,7 @@ Accept wildcard characters: False
 
 ### -AgentLogEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AgentLogEnabled parameter specifies whether the agent log is enabled. The default value is $true.
 
@@ -130,7 +130,7 @@ Accept wildcard characters: False
 
 ### -AgentLogMaxAge
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AgentLogMaxAge parameter specifies the maximum age for the agent log file. Log files older than the specified value are deleted. The default value is 7.00:00:00 or 7 days.
 
@@ -152,7 +152,7 @@ Accept wildcard characters: False
 
 ### -AgentLogMaxDirectorySize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AgentLogMaxDirectorySize parameter specifies the maximum size of all agent logs in the agent log directory. When a directory reaches its maximum file size, the server deletes the oldest log files first. The default value is 250 MB.
 
@@ -182,7 +182,7 @@ Accept wildcard characters: False
 
 ### -AgentLogMaxFileSize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AgentLogMaxFileSize parameter specifies the maximum size of each agent log file. When a log file reaches its maximum file size, a new log file is created. The default value is 10 MB.
 
@@ -212,7 +212,7 @@ Accept wildcard characters: False
 
 ### -AgentLogPath
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AgentLogPath parameter specifies the default agent log directory location. The default location is %ExchangeInstallPath%TransportRoles\\Logs\\FrontEnd\\AgentLog. Setting the value of this parameter to $null disables agent logging. However, setting this parameter to $null when the value of the AgentLogEnabled attribute is $true generates event log errors.
 
@@ -230,7 +230,7 @@ Accept wildcard characters: False
 
 ### -AntispamAgentsEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AntispamAgentsEnabled parameter specifies whether anti-spam agents are installed on the server specified with the Identity parameter. The default value is $false for the Front End Transport service.
 
@@ -250,7 +250,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -271,7 +271,7 @@ Accept wildcard characters: False
 
 ### -ConnectivityLogEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ConnectivityLogEnabled parameter specifies whether the connectivity log is enabled. The default value is $true.
 
@@ -289,7 +289,7 @@ Accept wildcard characters: False
 
 ### -ConnectivityLogMaxAge
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ConnectivityLogMaxAge parameter specifies the maximum age for the connectivity log file. Log files older than the specified value are deleted. The default value is 30 days.
 
@@ -311,7 +311,7 @@ Accept wildcard characters: False
 
 ### -ConnectivityLogMaxDirectorySize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ConnectivityLogMaxDirectorySize parameter specifies the maximum size of all connectivity logs in the connectivity log directory. When a directory reaches its maximum file size, the server deletes the oldest log files first. The default value is 1000 MB.
 
@@ -341,7 +341,7 @@ Accept wildcard characters: False
 
 ### -ConnectivityLogMaxFileSize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ConnectivityLogMaxFileSize parameter specifies the maximum size of each connectivity log file. When a log file reaches its maximum file size, a new log file is created. The default value is 10 MB.
 
@@ -371,7 +371,7 @@ Accept wildcard characters: False
 
 ### -ConnectivityLogPath
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ConnectivityLogPath parameter specifies the default connectivity log directory location. The default location is %ExchangeInstallPath%TransportRoles\\Logs\\FrontEnd\\Connectivity. Setting the value of this parameter to $null disables connectivity logging. However, setting this parameter to $null when the value of the ConnectivityLogEnabled attribute is $true generates event log errors.
 
@@ -389,7 +389,7 @@ Accept wildcard characters: False
 
 ### -DnsLogEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DnsLogEnabled parameter specifies whether the DNS log is enabled. The default value is $false.
 
@@ -407,7 +407,7 @@ Accept wildcard characters: False
 
 ### -DnsLogMaxAge
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DnsLogMaxAge parameter specifies the maximum age for the DNS log file. Log files older than the specified value are deleted. The default value is 7.00:00:00 or 7 days.
 
@@ -429,7 +429,7 @@ Accept wildcard characters: False
 
 ### -DnsLogMaxDirectorySize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DnsLogMaxDirectorySize parameter specifies the maximum size of all DNS logs in the DNS log directory. When a directory reaches its maximum file size, the server deletes the oldest log files first. The default value is 100 MB.
 
@@ -459,7 +459,7 @@ Accept wildcard characters: False
 
 ### -DnsLogMaxFileSize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DnsLogMaxFileSize parameter specifies the maximum size of each DNS log file. When a log file reaches its maximum file size, a new log file is created. The default value is 10 MB.
 
@@ -489,7 +489,7 @@ Accept wildcard characters: False
 
 ### -DnsLogPath
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DnsLogPath parameter specifies the DNS log directory location. The default value is blank ($null), which indicates no location is configured. If you enable DNS logging, you need to specify a local file path for the DNS log files by using this parameter. If the path contains spaces, enclose the entire path value in quotation marks (").
 
@@ -507,7 +507,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -525,7 +525,7 @@ Accept wildcard characters: False
 
 ### -ExternalDNSAdapterEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExternalDNSAdapterEnabled parameter specifies one or more Domain Name System (DNS) servers that Exchange uses for external DNS lookups. When the ExternalDNSAdapterEnabled parameter is set to $true, DNS lookups of destinations outside the Exchange organization are performed by using the DNS settings of the external network adapter specified by the value of the ExternalDNSAdapterGuid parameter. If you want to specify a custom list of DNS servers used for external Exchange DNS lookups only, you must specify the DNS servers by using the ExternalDNSServers parameter, and you must also set the value of the ExternalDNSAdapterEnabled parameter to $false. The default value of the ExternalDNSAdapterEnabled parameter is $true.
 
@@ -543,7 +543,7 @@ Accept wildcard characters: False
 
 ### -ExternalDNSAdapterGuid
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExternalDNSAdapterGuid parameter specifies the network adapter that has the DNS settings used for DNS lookups of destinations that exist outside the Exchange organization. The concept of an external network adapter and an internal network adapter is only applicable in a multi-homed Exchange server environment. When no particular network adapter is specified as the network adapter for external DNS lookups, the value of the ExternalDNSAdapterGuid parameter is 00000000-0000-0000-0000-000000000000, and external DNS lookups are performed by using the DNS settings of any available network adapter. You might enter the GUID of a specific network adapter to use for external DNS lookups. The default value of the ExternalDNSAdapterGuid parameter is 00000000-0000-0000-0000-000000000000.
 
@@ -563,7 +563,7 @@ Accept wildcard characters: False
 
 ### -ExternalDNSProtocolOption
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExternalDNSProtocolOption parameter specifies which protocol to use when querying external DNS servers. The valid options for this parameter are Any, UseTcpOnly, and UseUdpOnly. The default value is Any.
 
@@ -581,7 +581,7 @@ Accept wildcard characters: False
 
 ### -ExternalDNSServers
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExternalDNSServers parameter specifies the list of external DNS servers that the server queries when resolving a remote domain. You must separate IP addresses by using commas. The default value is an empty list ({}).
 
@@ -601,7 +601,7 @@ Accept wildcard characters: False
 
 ### -ExternalIPAddress
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExternalIPAddress parameter specifies the IP address used in the Received message header field for every message that travels through the Front End Transport service. The IP address in the Received header field is used for hop count and routing loop detection. The IP address specified by the ExternalIPAddress parameter overrides the external network adapter's actual IP address. Typically, you would want to set the value of the ExternalIPAddress parameter to match the value of your domain's public MX record. The default value of the ExternalIPAddress parameter is blank. This means the actual IP address of the external network adapter is used in the Received header field.
 
@@ -619,7 +619,7 @@ Accept wildcard characters: False
 
 ### -InternalDNSAdapterEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The InternalDNSAdapterEnabled parameter specifies one or more DNS servers that Exchange uses for internal DNS lookups. When the InternalDNSAdapterEnabled parameter is set to $true, DNS lookups of destinations inside the Exchange organization are performed by using the DNS settings of the internal network adapter specified by the value of the InternalDNSAdapterGuid parameter. If you want to specify a custom list of DNS servers used for internal Exchange DNS lookups only, you must specify the DNS servers by using the InternalDNSServers parameter, and you must also set the value of the InternalDNSAdapterEnabled parameter to $false. The default value of the InternalDNSAdapterEnabled parameter is $true.
 
@@ -637,7 +637,7 @@ Accept wildcard characters: False
 
 ### -InternalDNSAdapterGuid
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The InternalDNSAdapterGuid parameter specifies the network adapter that has the DNS settings used for DNS lookups of servers that exist inside the Exchange organization. The concept of an internal network adapter and an external network adapter is only applicable in a multi-homed Exchange server environment. When no particular network adapter is specified as the network adapter for external DNS lookups, the value of the InternalDNSAdapterGuid parameter is 00000000-0000-0000-0000-000000000000, and internal DNS lookups are performed by using the DNS settings of any available network adapter. You might enter the GUID of a specific network adapter to use for internal DNS lookups. The default value of the InternalDNSAdapterGuid parameter is 00000000-0000-0000-0000-000000000000.
 
@@ -657,7 +657,7 @@ Accept wildcard characters: False
 
 ### -InternalDNSProtocolOption
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The InternalDNSProtocolOption parameter specifies which protocol to use when you query internal DNS servers. Valid options for this parameter are Any, UseTcpOnly, or UseUdpOnly.
 
@@ -677,7 +677,7 @@ Accept wildcard characters: False
 
 ### -InternalDNSServers
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The InternalDNSServers parameter specifies the list of DNS servers that should be used when resolving a domain name. DNS servers are specified by IP address and are separated by commas. The default value is any empty list ({}).
 
@@ -697,7 +697,7 @@ Accept wildcard characters: False
 
 ### -IntraOrgConnectorProtocolLoggingLevel
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IntraOrgConnectorProtocolLoggingLevel parameter enables or disables SMTP protocol logging on the implicit and invisible intra-organization Send connector In the Front End Transport service. Valid values are:
 
@@ -718,7 +718,7 @@ Accept wildcard characters: False
 
 ### -MaxConnectionRatePerMinute
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MaxConnectionRatePerMinute parameter specifies the maximum rate that connections are allowed to be opened with the transport service. If many connections are attempted with the transport service at the same time, the MaxConnectionRatePerMinute parameter limits the rate that the connections are opened so that the server's resources aren't overwhelmed. The default value is 1200 connections per minute. The valid input range for this parameter is from 1 through 2147483647.
 
@@ -736,7 +736,7 @@ Accept wildcard characters: False
 
 ### -ReceiveProtocolLogMaxAge
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ReceiveProtocolLogMaxAge parameter specifies the maximum age of a protocol log file that's shared by all Receive connectors in the Transport service on the server. Log files that are older than the specified value are automaticallydeleted.
 
@@ -760,7 +760,7 @@ Accept wildcard characters: False
 
 ### -ReceiveProtocolLogMaxDirectorySize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ReceiveProtocolLogMaxDirectorySize parameter specifies the maximum size of the protocol log directory that's shared by all Receive connectors in the Front End Transport service on the server. When the maximum directory size is reached, the server deletes the oldest log files first.
 
@@ -794,7 +794,7 @@ Accept wildcard characters: False
 
 ### -ReceiveProtocolLogMaxFileSize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ReceiveProtocolLogMaxFileSize parameter specifies the maximum size of a protocol log file that's shared by all Receive connectors in the Front End Transport service on the server. When a log file reaches its maximum file size, a new log file is created.
 
@@ -828,7 +828,7 @@ Accept wildcard characters: False
 
 ### -ReceiveProtocolLogPath
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ReceiveProtocolLogPath parameter specifies the location of the protocol log directory for all Receive connectors in the Front End Transport service on the server. The default location is %ExchangeInstallPath%TransportRoles\\Logs\\FrontEnd\\ProtocolLog\\SmtpReceive.
 
@@ -848,7 +848,7 @@ Accept wildcard characters: False
 
 ### -RoutingTableLogMaxAge
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RoutingTableLogMaxAge parameter specifies the maximum routing table log age. Log files older than the specified value are deleted. The default value is 7 days.
 
@@ -870,7 +870,7 @@ Accept wildcard characters: False
 
 ### -RoutingTableLogMaxDirectorySize
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RoutingTableLogMaxDirectorySize parameter specifies the maximum size of the routing table log directory. When the maximum directory size is reached, the server deletes the oldest log files first. The default value is 250 MB.
 
@@ -900,7 +900,7 @@ Accept wildcard characters: False
 
 ### -RoutingTableLogPath
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RoutingTableLogPath parameter specifies the directory location where routing table log files should be stored. The default location is %ExchangeInstallPath%TransportRoles\\Logs\\FrontEnd\\Routing. Setting this parameter to $null disables routing table logging.
 
@@ -918,7 +918,7 @@ Accept wildcard characters: False
 
 ### -SendProtocolLogMaxAge
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SendProtocolLogMaxAge parameter specifies the maximum age of a protocol log file that's shared by all Send connectors in the Front End Transport service that have this server configured as a source server. Log files that are older than the specified value are deleted.
 
@@ -942,7 +942,7 @@ Accept wildcard characters: False
 
 ### -SendProtocolLogMaxDirectorySize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SendProtocolLogMaxDirectorySize parameter specifies the maximum size of the protocol log directory that's shared by all Send connectors in the Front End Transport service that have this server configured as a source server. When the maximum directory size is reached, the server deletes the oldest log files first.
 
@@ -976,7 +976,7 @@ Accept wildcard characters: False
 
 ### -SendProtocolLogMaxFileSize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SendProtocolLogMaxFileSize parameter specifies the maximum size of a protocol log file that's shared by all the Send connectors in the Front End Transport service that have this server configured as a source server. When a log file reaches its maximum file size, a new log file is created.
 
@@ -1010,7 +1010,7 @@ Accept wildcard characters: False
 
 ### -SendProtocolLogPath
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SendProtocolLogPath parameter specifies the location of the protocol log directory for all Send connectors in the Front End Transport service that have this server configured as a source server. The default location is %ExchangeInstallPath%TransportRoles\\Logs\\FrontEnd\\ProtocolLog\\SmtpSend.
 
@@ -1033,7 +1033,7 @@ Accept wildcard characters: False
 
 ### -TransientFailureRetryCount
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TransientFailureRetryCount parameter specifies the maximum number of immediate connection retries attempted when the server encounters a connection failure with a remote server. The default value is 6. The valid input range for this parameter is from 0 through 15. When the value of this parameter is set to 0, the server doesn't immediately attempt to retry an unsuccessful connection.
 
@@ -1051,7 +1051,7 @@ Accept wildcard characters: False
 
 ### -TransientFailureRetryInterval
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TransientFailureRetryInterval parameter controls the connection interval between each connection attempt specified by the TransientFailureRetryCount parameter. For the Front End Transport service, the default value of the TransientFailureRetryInterval parameter is 5 minutes.
 
@@ -1073,7 +1073,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-GlobalAddressList.md b/exchange/exchange-ps/ExchangePowerShell/Set-GlobalAddressList.md
index 1b6156bcc7..427add54fe 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-GlobalAddressList.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-GlobalAddressList.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -80,7 +80,7 @@ This example assigns a new name, GALwithNewName, to the GAL with the GUID 96d0c5
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the global address list that you want to modify. You can use any value that uniquely identifies the GAL. For example:
 
@@ -102,7 +102,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCompany
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalCompany parameter specifies a precanned filter that's based on the value of the recipient's Company property.
 
@@ -126,7 +126,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute1
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalCustomAttribute1 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute1 property. You can specify multiple values separated by commas.
 
@@ -150,7 +150,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute10
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalCustomAttribute10 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute10 property. You can specify multiple values separated by commas.
 
@@ -174,7 +174,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute11
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalCustomAttribute11 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute11 property. You can specify multiple values separated by commas.
 
@@ -198,7 +198,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute12
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalCustomAttribute12 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute12 property. You can specify multiple values separated by commas.
 
@@ -222,7 +222,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute13
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalCustomAttribute13 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute13 property. You can specify multiple values separated by commas.
 
@@ -246,7 +246,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute14
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalCustomAttribute14 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute14 property. You can specify multiple values separated by commas.
 
@@ -270,7 +270,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute15
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalCustomAttribute15 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute15 property. You can specify multiple values separated by commas.
 
@@ -294,7 +294,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute2
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalCustomAttribute2 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute2 property. You can specify multiple values separated by commas.
 
@@ -318,7 +318,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute3
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalCustomAttribute3 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute3 property. You can specify multiple values separated by commas.
 
@@ -342,7 +342,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute4
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalCustomAttribute4 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute4 property. You can specify multiple values separated by commas.
 
@@ -366,7 +366,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute5
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalCustomAttribute5 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute5 property. You can specify multiple values separated by commas.
 
@@ -390,7 +390,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute6
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalCustomAttribute6 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute6 property. You can specify multiple values separated by commas.
 
@@ -414,7 +414,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute7
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalCustomAttribute7 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute7 property. You can specify multiple values separated by commas.
 
@@ -438,7 +438,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute8
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalCustomAttribute8 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute8 property. You can specify multiple values separated by commas.
 
@@ -462,7 +462,7 @@ Accept wildcard characters: False
 
 ### -ConditionalCustomAttribute9
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalCustomAttribute9 parameter specifies a precanned filter that's based on the value of the recipient's CustomAttribute9 property. You can specify multiple values separated by commas.
 
@@ -486,7 +486,7 @@ Accept wildcard characters: False
 
 ### -ConditionalDepartment
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalDepartment parameter specifies a precanned filter that's based on the value of the recipient's Department property. You can specify multiple values separated by commas.
 
@@ -510,7 +510,7 @@ Accept wildcard characters: False
 
 ### -ConditionalStateOrProvince
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConditionalStateOrProvince parameter specifies a precanned filter that's based on the value of the recipient's StateOrProvince property. You can specify multiple values separated by commas.
 
@@ -534,7 +534,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -555,7 +555,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -575,7 +575,7 @@ Accept wildcard characters: False
 
 ### -ForceUpgrade
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -595,7 +595,7 @@ Accept wildcard characters: False
 
 ### -IncludedRecipients
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IncludedRecipients parameter specifies a precanned filter that's based on the recipient type. Valid values are:
 
@@ -622,7 +622,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Name parameter specifies the unique name of the GAL. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -640,7 +640,7 @@ Accept wildcard characters: False
 
 ### -RecipientContainer
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -667,7 +667,7 @@ Accept wildcard characters: False
 
 ### -RecipientFilter
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RecipientFilter parameter specifies an OPATH filter that's based on the value of any available recipient property. You can use any available Windows PowerShell operator, and wildcards and partial matches are supported. The search criteria uses the syntax `"Property -ComparisonOperator 'Value'"`.
 
@@ -694,7 +694,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-Group.md b/exchange/exchange-ps/ExchangePowerShell/Set-Group.md
index 0d12511a23..3e23d3c7be 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-Group.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-Group.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
 Locale: en-US
@@ -71,7 +71,7 @@ This example specifies that the group Human Resources is a hierarchical group an
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the group that you want to modify. You can use any value that uniquely identifies the group. For example:
 
@@ -94,7 +94,7 @@ Accept wildcard characters: False
 
 ### -BypassSecurityGroupManagerCheck
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The BypassSecurityGroupManagerCheck switch specifies whether to allow a user who isn't an owner of the group to modify or delete the group. You don't need to specify a value with this switch.
 
@@ -117,7 +117,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -158,7 +158,7 @@ Accept wildcard characters: False
 
 ### -DisplayName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The DisplayName parameter specifies the display name of the group. The display name is visible in the Exchange admin center and in address lists. The maximum length is 256 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -178,7 +178,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -200,7 +200,7 @@ Accept wildcard characters: False
 
 ### -IgnoreDefaultScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -225,7 +225,7 @@ Accept wildcard characters: False
 
 ### -IsHierarchicalGroup
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The IsHierarchicalGroup parameter specifies whether the group is part of a hierarchical address book. Valid values are $true or $false. The default value is $false.
 
@@ -243,7 +243,7 @@ Accept wildcard characters: False
 
 ### -ManagedBy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ManagedBy parameter specifies an owner for the group. A group must have at least one owner. If you don't use this parameter to specify the owner when you create the group, the user account that created the group is the owner. The group owner is able to:
 
@@ -288,7 +288,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Name parameter specifies the unique name of the group. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -306,7 +306,7 @@ Accept wildcard characters: False
 
 ### -Notes
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Notes parameters specifies additional information about the object. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -324,7 +324,7 @@ Accept wildcard characters: False
 
 ### -PhoneticDisplayName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The PhoneticDisplayName parameter specifies an alternate spelling of the user's name that's used for text to speech in Unified Messaging (UM) environments. Typically, you use this parameter when the pronunciation and spelling of the user's name don't match. The maximum length is 256 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -342,7 +342,7 @@ Accept wildcard characters: False
 
 ### -SeniorityIndex
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The SeniorityIndex parameter specifies the order in which this group displays in a hierarchical address book. A group with a value of 2 displays higher in an address book than a group with a value of 1.
 
@@ -360,7 +360,7 @@ Accept wildcard characters: False
 
 ### -SimpleDisplayName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The SimpleDisplayName parameter is used to display an alternative description of the object when only a limited set of characters is permitted. Valid characters are:
 
@@ -386,7 +386,7 @@ Accept wildcard characters: False
 
 ### -Universal
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Universal switch changes the scope of the group from Global or DomainLocal to Universal. You don't need to specify a value with this switch.
 
@@ -404,7 +404,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
@@ -422,7 +422,7 @@ Accept wildcard characters: False
 
 ### -WindowsEmailAddress
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WindowsEmailAddress parameter specifies the Windows email address for this recipient. This is a common Active Directory attribute that's present in all environments, including environments without Exchange. Using the WindowsEmailAddress parameter on a recipient has one of the following results:
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-HybridConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Set-HybridConfiguration.md
index 6e76762288..020664f802 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-HybridConfiguration.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-HybridConfiguration.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -74,7 +74,7 @@ This example specifies that the hybrid deployment uses a defined TLS certificate
 
 ### -ClientAccessServers
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in Exchange Server 2010.
 
@@ -100,7 +100,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -121,7 +121,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -139,7 +139,7 @@ Accept wildcard characters: False
 
 ### -Domains
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Domains parameter specifies the domain namespaces used in the hybrid deployment. These domains must be configured as accepted domains in either on-premises Exchange or Exchange Online. The domains are used in configuring the organization relationships and Send and Receive connectors used by the hybrid configuration.
 
@@ -159,7 +159,7 @@ Accept wildcard characters: False
 
 ### -ExternalIPAddresses
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExternalIPAddresses parameter is a legacy parameter that specifies the publicly accessible inbound IP address of Microsoft Exchange Server 2010 Hub Transport servers.
 
@@ -179,7 +179,7 @@ Accept wildcard characters: False
 
 ### -Features
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Features parameter specifies the features that are enabled for the hybrid configuration. Valid values are:
 
@@ -208,7 +208,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is deprecated and no longer used.
 
@@ -228,7 +228,7 @@ Accept wildcard characters: False
 
 ### -OnPremisesSmartHost
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The OnPremisesSmartHost parameter specifies the FQDN of the on-premises Exchange Mailbox server used for secure mail transport between on-premises Exchange and Exchange Online.
 
@@ -246,7 +246,7 @@ Accept wildcard characters: False
 
 ### -ReceivingTransportServers
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ReceivingTransportServers parameter specifies the Mailbox servers defined in the outbound connector configuration in Exchange Online. Valid values are:
 
@@ -293,7 +293,7 @@ Accept wildcard characters: False
 
 ### -SendingTransportServers
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SendingTransportServers parameter specifies the Mailbox servers defined in the inbound connector configuration in Exchange Online. Valid values are:
 
@@ -320,7 +320,7 @@ Accept wildcard characters: False
 
 ### -ServiceInstance
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is meaningful only in Office 365 operated by 21Vianet in China.
 
@@ -342,7 +342,7 @@ Accept wildcard characters: False
 
 ### -TlsCertificateName
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TlsCertificateName parameter specifies the X.509 certificate to use for TLS encryption. Valid syntax for this parameter is `"<I>X.500Issuer<S>X.500Subject"`:
 
@@ -391,7 +391,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
@@ -409,7 +409,7 @@ Accept wildcard characters: False
 
 ### -EdgeTransportServers
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The EdgeTransportServers parameter specifies the Edge Transport servers that are configured to support the hybrid deployment features. The Edge Transport server must be externally accessible from the Internet on port 25. The accepted values for the EdgeTransportServers parameter are either the full or short computer name of an Edge Transport server, for example, either edge.corp.contoso.com or EDGE. Separate server names with a comma if defining more than one Edge Transport server.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-IPAllowListConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-IPAllowListConfig.md
index 98ff7468b6..1d6d73bd21 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-IPAllowListConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-IPAllowListConfig.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailControl-Help.xml
 Locale: en-US
@@ -49,7 +49,7 @@ This example configures connection filtering to use the IP Allow list on message
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -70,7 +70,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -90,7 +90,7 @@ Accept wildcard characters: False
 
 ### -Enabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Enabled parameter specifies whether the IP Allow list is used for content filtering. Valid input for this parameter is $true or $false. The default value is $true. By default, the IP Allow list is used for content filtering.
 
@@ -108,7 +108,7 @@ Accept wildcard characters: False
 
 ### -ExternalMailEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExternalMailEnabled parameter specifies whether messages from connections outside of the Exchange organization are evaluated by the IP Allow list. Valid input for this parameter is $true or $false. The default value is $true. By default, messages from external connections are evaluated by the IP Allow list.
 
@@ -126,7 +126,7 @@ Accept wildcard characters: False
 
 ### -InternalMailEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The InternalMailEnabled parameter specifies whether messages from connections inside the Exchange organization are evaluated by the IP Allow list. Valid input for this parameter is $true or $false. The default value is $false. By default, messages from internal connections are not evaluated by the IP Allow list. Authenticated partner messages aren't considered internal mail.
 
@@ -144,7 +144,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-IPAllowListProvider.md b/exchange/exchange-ps/ExchangePowerShell/Set-IPAllowListProvider.md
index af75586dea..ef60d3134a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-IPAllowListProvider.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-IPAllowListProvider.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailControl-Help.xml
 Locale: en-US
@@ -59,7 +59,7 @@ This example sets the priority to 1 for the existing IP Allow list provider name
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the IP Allow list provider that you want to modify. You can use any value that uniquely identifies the IP Allow list provider. For example:
 
@@ -81,7 +81,7 @@ Accept wildcard characters: False
 
 ### -AnyMatch
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AnyMatch parameter specifies whether any response by the allow list provider is treated as a match. Valid input for this parameter is $true or $false. The default value is $false. When this parameter is set to $true, and connection filtering sends the IP address of the connecting SMTP server to the allow list provider, any response code returned by the allow list provider causes connection filtering to allow messages from that source.
 
@@ -99,7 +99,7 @@ Accept wildcard characters: False
 
 ### -BitmaskMatch
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The BitmaskMatch parameter specifies the bit mask status code that's returned by the allow list provider. Use this parameter if the allow list provider returns bitmask responses. Valid input for this parameter is a single IP address in the format 127.0.0.1.
 
@@ -117,7 +117,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -138,7 +138,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -158,7 +158,7 @@ Accept wildcard characters: False
 
 ### -Enabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Enabled parameter specifies whether the Connection Filtering agent queries the IP Allow list provider according to the priority set for this IP Allow list provider configuration. Valid input for this parameter is $true or $false. The default value is $true. By default, the Connection Filtering agent queries the IP Allow list provider according to the priority set for this IP Allow list provider configuration.
 
@@ -176,7 +176,7 @@ Accept wildcard characters: False
 
 ### -IPAddressesMatch
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IPAddressesMatch parameter specifies the IP address status codes that are returned by the allow list provider. Use this parameter if the allow list provider returns IP address or A record responses. Valid input for this parameter one or more IP addresses in the format 127.0.0.1.
 
@@ -198,7 +198,7 @@ Accept wildcard characters: False
 
 ### -LookupDomain
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The LookupDomain parameter specifies the host name that's required to use the allow list provider. Connection filtering sends the IP address of the connecting SMTP server to the host name value that you specify. An example value is allowlist.spamservice.com. The actual value you need to use is provided by the allow list provider.
 
@@ -216,7 +216,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Name parameter specifies a descriptive name for the IP Allow list provider.
 
@@ -234,7 +234,7 @@ Accept wildcard characters: False
 
 ### -Priority
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Priority parameter specifies the order that the Connection Filtering agent queries the IP Allow list providers that you've configured. By default, every time that you add a new IP Allow list provider, the entry is assigned a priority of N+1, where N is the number of IP Allow list providers you've configured.
 
@@ -254,7 +254,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-IPAllowListProvidersConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-IPAllowListProvidersConfig.md
index 02de75f25d..b302367695 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-IPAllowListProvidersConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-IPAllowListProvidersConfig.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailControl-Help.xml
 Locale: en-US
@@ -49,7 +49,7 @@ This example configures connection filtering to use IP Allow list providers on m
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -70,7 +70,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -90,7 +90,7 @@ Accept wildcard characters: False
 
 ### -Enabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Enabled parameter specifies whether IP Allow list providers are used for content filtering. Valid input for this parameter is $true or $false. The default value is $true. The default value is $true. By default, IP Allow list providers are used for content filtering.
 
@@ -108,7 +108,7 @@ Accept wildcard characters: False
 
 ### -ExternalMailEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExternalMailEnabled parameter specifies whether messages from connections outside of the Exchange organization are evaluated by IP Allow list providers. Valid input for this parameter is $true or $false. The default value is $true. By default, messages from external connections are evaluated by IP Allow list providers.
 
@@ -126,7 +126,7 @@ Accept wildcard characters: False
 
 ### -InternalMailEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The InternalMailEnabled parameter specifies whether messages from connections inside the Exchange organization are evaluated by IP Allow list providers. Valid input for this parameter is $true or $false. The default value is $false. By default, messages from internal connections are not evaluated by IP Allow list providers. Authenticated partner messages aren't considered internal mail.
 
@@ -144,7 +144,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-IPBlockListConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-IPBlockListConfig.md
index 07b5a80820..52a84ea0f0 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-IPBlockListConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-IPBlockListConfig.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailControl-Help.xml
 Locale: en-US
@@ -51,7 +51,7 @@ This example configures connection filtering to use the IP Block list on message
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -72,7 +72,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -92,7 +92,7 @@ Accept wildcard characters: False
 
 ### -Enabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Enabled parameter specifies whether the IP Block list is used for content filtering. Valid input for this parameter is $true or $false. The default value is $true. By default, the IP Block list is used for content filtering.
 
@@ -110,7 +110,7 @@ Accept wildcard characters: False
 
 ### -ExternalMailEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExternalMailEnabled parameter specifies whether messages from connections outside of the Exchange organization are evaluated by the IP Block list. Valid input for this parameter is $true or $false. The default value is $true. By default, messages from external connections are evaluated by the IP Block list.
 
@@ -128,7 +128,7 @@ Accept wildcard characters: False
 
 ### -InternalMailEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The InternalMailEnabled parameter specifies whether messages from connections inside the Exchange organization are evaluated by the IP Block list. Valid input for this parameter is $true or $false. The default value is $false. By default, messages from internal connections are not evaluated by the IP Block list. Authenticated partner messages aren't considered internal mail.
 
@@ -146,7 +146,7 @@ Accept wildcard characters: False
 
 ### -MachineEntryRejectionResponse
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MachineEntryRejectionResponse parameter specifies customized text in the non-delivery report (NDR) for messages that are blocked by connection filtering due to IP addresses in the IP Block list that were added by sender reputation. The value can't exceed 240 characters. If the value contains spaces, enclose the value in double quotation marks (").
 
@@ -164,7 +164,7 @@ Accept wildcard characters: False
 
 ### -StaticEntryRejectionResponse
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The StaticEntryRejectionResponse parameter specifies a customized text in the NDR for messages that are blocked by connection filtering due to IP addresses in the IP Block list. The value can't exceed 240 characters. If the value contains spaces, enclose the value in double quotation marks (").
 
@@ -182,7 +182,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-IPBlockListProvider.md b/exchange/exchange-ps/ExchangePowerShell/Set-IPBlockListProvider.md
index 7768c0863f..cbfed7d8a3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-IPBlockListProvider.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-IPBlockListProvider.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailControl-Help.xml
 Locale: en-US
@@ -60,7 +60,7 @@ This example sets the priority value to 1 for the IP Block list provider named C
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the IP Block list provider that you want to modify. You can use any value that uniquely identifies the IP Block list provider. For example:
 
@@ -82,7 +82,7 @@ Accept wildcard characters: False
 
 ### -AnyMatch
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AnyMatch parameter specifies whether any response by the block list provider is treated as a match. Valid input for this parameter is $true or $false. The default value is $false. When this parameter is set to $true and connection filtering sends the IP address of the connecting SMTP server to the block list provider, any response code returned by the block list provider causes connection filtering to block messages from that source.
 
@@ -100,7 +100,7 @@ Accept wildcard characters: False
 
 ### -BitmaskMatch
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The BitmaskMatch parameter specifies the bit mask status code that's returned by the block list provider. Use this parameter if the block list provider returns bitmask responses. Valid input for this parameter is a single IP address in the format 127.0.0.1.
 
@@ -118,7 +118,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -139,7 +139,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -159,7 +159,7 @@ Accept wildcard characters: False
 
 ### -Enabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Enabled parameter specifies whether the connection filtering uses this IP Block list provider. Valid input for this parameter is $true or $false. The default value is $true. By default, connection filtering uses new IP Block list providers that you create.
 
@@ -177,7 +177,7 @@ Accept wildcard characters: False
 
 ### -IPAddressesMatch
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IPAddressesMatch parameter specifies the IP address status codes that are returned by the block list provider. Use this parameter if the block list provider returns IP address or A record responses. Valid input for this parameter one or more IP addresses in the format 127.0.0.1.
 
@@ -199,7 +199,7 @@ Accept wildcard characters: False
 
 ### -LookupDomain
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The LookupDomain parameter specifies the host name that's required to use the block list provider. Connection filtering sends the IP address of the connecting SMTP server to the host name value that you specify. An example value is blocklist.spamservice.com. The actual value you need to use is provided by the block list provider.
 
@@ -217,7 +217,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Name parameter specifies a descriptive name for the IP Block list provider.
 
@@ -235,7 +235,7 @@ Accept wildcard characters: False
 
 ### -Priority
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Priority parameter specifies the order that the Connection Filtering agent queries the IP Block list providers. A lower priority integer value indicates a higher priority. By default, every time that you add a new IP Block list provider, the entry is assigned a priority of N+1, where N is the number of IP Block list provider services that you have configured.
 
@@ -255,7 +255,7 @@ Accept wildcard characters: False
 
 ### -RejectionResponse
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RejectionResponse parameter specifies the text that you want to include in the SMTP rejection response when messages are blocked by connection filtering. The argument can't exceed 240 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -275,7 +275,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-IPBlockListProvidersConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-IPBlockListProvidersConfig.md
index 6ff657f659..2fcbad285d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-IPBlockListProvidersConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-IPBlockListProvidersConfig.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailControl-Help.xml
 Locale: en-US
@@ -60,7 +60,7 @@ This example makes the following changes to the list of bypassed recipients:
 
 ### -BypassedRecipients
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The BypassedRecipients parameter specifies the email addresses of internal recipients that are exempted from filtering by IP Block list providers.
 
@@ -82,7 +82,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -103,7 +103,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -123,7 +123,7 @@ Accept wildcard characters: False
 
 ### -Enabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Enabled parameter specifies whether IP Block list providers are used for content filtering. Valid input for this parameter is $true or $false. The default value is $true. The default value is $true. By default, IP Block list providers are used for content filtering.
 
@@ -141,7 +141,7 @@ Accept wildcard characters: False
 
 ### -ExternalMailEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExternalMailEnabled parameter specifies whether messages from connections outside of the Exchange organization are evaluated by IP Block list providers. Valid input for this parameter is $true or $false. The default value is $true. By default, messages from external connections are evaluated by IP Bock list providers.
 
@@ -159,7 +159,7 @@ Accept wildcard characters: False
 
 ### -InternalMailEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The InternalMailEnabled parameter specifies whether messages from connections inside the Exchange organization are evaluated by IP Block list providers. Valid input for this parameter is $true or $false. The default value is $false. By default, messages from internal connections are not evaluated by IP Block list providers. Authenticated partner messages aren't considered internal mail.
 
@@ -177,7 +177,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-IRMConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Set-IRMConfiguration.md
index 31c494d89b..5c112c0342 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-IRMConfiguration.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-IRMConfiguration.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailControl-Help.xml
 Locale: en-US
@@ -149,7 +149,7 @@ Accept wildcard characters: False
 
 ### -ClientAccessServerEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -172,7 +172,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -218,7 +218,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -238,7 +238,7 @@ Accept wildcard characters: False
 
 ### -EDiscoverySuperUserEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The EDiscoverySuperUserEnabled parameter specifies whether members of the Discovery Management role group can access IRM-protected messages in a discovery mailbox that were returned by a discovery search. Valid values are:
 
@@ -309,7 +309,7 @@ Accept wildcard characters: False
 
 ### -ExternalLicensingEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -334,7 +334,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -354,7 +354,7 @@ Accept wildcard characters: False
 
 ### -InternalLicensingEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 **Note**: In Exchange Online, this parameter affects both internal and external messages. In on-premises Exchange, this parameter only affects internal messages.
 
@@ -377,7 +377,7 @@ Accept wildcard characters: False
 
 ### -JournalReportDecryptionEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The JournalReportDecryptionEnabled parameter specifies whether to enable journal report decryption. Valid values are:
 
@@ -398,7 +398,7 @@ Accept wildcard characters: False
 
 ### -LicensingLocation
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The LicensingLocation parameter specifies the RMS licensing URLs. You can specify multiple URL values separated by commas.
 
@@ -420,7 +420,7 @@ Accept wildcard characters: False
 
 ### -RefreshServerCertificates
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -482,7 +482,7 @@ Accept wildcard characters: False
 
 ### -SearchEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The SearchEnabled parameter specifies whether to enable searching of IRM-encrypted messages in Outlook on the web (formerly known as Outlook Web App). Valid values are:
 
@@ -572,7 +572,7 @@ Accept wildcard characters: False
 
 ### -TransportDecryptionSetting
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The TransportDecryptionSetting parameter specifies the transport decryption configuration. Valid values are:
 
@@ -594,7 +594,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ImapSettings.md b/exchange/exchange-ps/ExchangePowerShell/Set-ImapSettings.md
index c596ae4a64..7dbf537398 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ImapSettings.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ImapSettings.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -104,7 +104,7 @@ This example specifies the certificate that contains mail.contoso.com is used to
 
 ### -AuthenticatedConnectionTimeout
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AuthenticatedConnectionTimeout parameter specifies the period of time to wait before closing an idle authenticated connection.
 
@@ -126,7 +126,7 @@ Accept wildcard characters: False
 
 ### -Banner
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Banner parameter specifies the text string that's displayed to connecting IMAP4 clients. The default value is: The Microsoft Exchange IMAP4 service is ready.
 
@@ -144,7 +144,7 @@ Accept wildcard characters: False
 
 ### -CalendarItemRetrievalOption
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The CalendarItemRetrievalOption parameter specifies how calendar items are presented to IMAP4 clients. Valid values are:
 
@@ -169,7 +169,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -190,7 +190,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -208,7 +208,7 @@ Accept wildcard characters: False
 
 ### -EnableExactRFC822Size
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The EnableExactRFC822Size parameter specifies how message sizes are presented to IMAP4 clients. Valid values are:
 
@@ -229,7 +229,7 @@ Accept wildcard characters: False
 
 ### -EnableGSSAPIAndNTLMAuth
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The EnableGSSAPIAndNTLMAuth parameter specifies whether connections can use Integrated Windows authentication (NTLM) using the Generic Security Services application programming interface (GSSAPI). This setting applies to connections where Transport Layer Security (TLS) is disabled. Valid values are:
 
@@ -250,7 +250,7 @@ Accept wildcard characters: False
 
 ### -EnforceCertificateErrors
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The EnforceCertificateErrors parameter specifies whether to enforce valid Secure Sockets Layer (SSL) certificate validation failures. Valid values are:
 
@@ -273,7 +273,7 @@ Accept wildcard characters: False
 
 ### -ExtendedProtectionPolicy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExtendedProtectionPolicy parameter specifies how Extended Protection for Authentication is used. Valid values are:
 
@@ -297,7 +297,7 @@ Accept wildcard characters: False
 
 ### -ExternalConnectionSettings
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExternalConnectionSettings parameter specifies the host name, port, and encryption method that's used by external IMAP4 clients (IMAP4 connections from outside your corporate network).
 
@@ -325,7 +325,7 @@ Accept wildcard characters: False
 
 ### -InternalConnectionSettings
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The InternalConnectionSettings parameter specifies the host name, port, and encryption method that's used by internal IMAP4 clients (IMAP4 connections from inside your corporate network). This setting is also used when a IMAP4 connection is forwarded to another Exchange server that's running the Microsoft Exchange IMAP4 service.
 
@@ -353,7 +353,7 @@ Accept wildcard characters: False
 
 ### -LogFileLocation
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The LogFileLocation parameter specifies the location for the IMAP4 protocol log files. The default location is %ExchangeInstallPath%Logging\\Imap4.
 
@@ -373,7 +373,7 @@ Accept wildcard characters: False
 
 ### -LogFileRollOverSettings
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The LogFileRollOverSettings parameter specifies how frequently IMAP4 protocol logging creates a new log file. Valid values are:
 
@@ -398,7 +398,7 @@ Accept wildcard characters: False
 
 ### -LoginType
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The LoginType parameter specifies the authentication method for IMAP4 connections. Valid values are:
 
@@ -420,7 +420,7 @@ Accept wildcard characters: False
 
 ### -LogPerFileSizeQuota
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The LogPerFileSizeQuota parameter specifies the maximum size of a IMAP4 protocol log file.
 
@@ -452,7 +452,7 @@ Accept wildcard characters: False
 
 ### -MaxCommandSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MaxCommandSize parameter specifies the maximum size in bytes of a single IMAP4 command. Valid values are from 1024 through 16384. The default value is 10240.
 
@@ -470,7 +470,7 @@ Accept wildcard characters: False
 
 ### -MaxConnectionFromSingleIP
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MaxConnectionFromSingleIP parameter specifies the maximum number of IMAP4 connections that are accepted by the Exchange server from a single IP address. Valid values are from 1 through 2147483647. The default value is 2147483647.
 
@@ -488,7 +488,7 @@ Accept wildcard characters: False
 
 ### -MaxConnections
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MaxConnections parameter specifies the maximum number of IMAP4 connections that are accepted by the Exchange server. Valid values are from 1 through 2147483647. The default value is 2147483647.
 
@@ -506,7 +506,7 @@ Accept wildcard characters: False
 
 ### -MaxConnectionsPerUser
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MaxConnectionsPerUser parameter specifies the maximum number of IMAP4 connections that are allowed for each user. Valid values are from 1 through 2147483647. The default value is 16.
 
@@ -524,7 +524,7 @@ Accept wildcard characters: False
 
 ### -MessageRetrievalMimeFormat
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MessageRetrievalMimeFormat parameter specifies the MIME encoding of messages. Valid values are:
 
@@ -550,7 +550,7 @@ Accept wildcard characters: False
 
 ### -OwaServerUrl
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The OwaServerUrl parameter specifies the URL that's used to retrieve calendar information for instances of custom Outlook on the web calendar items.
 
@@ -568,7 +568,7 @@ Accept wildcard characters: False
 
 ### -PreAuthenticatedConnectionTimeout
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PreAuthenticatedConnectionTimeout parameter specifies the period of time to wait before closing an idle IMAP4 connection that isn't authenticated.
 
@@ -590,7 +590,7 @@ Accept wildcard characters: False
 
 ### -ProtocolLogEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ProtocolLogEnabled parameter specifies whether to enable protocol logging for IMAP4. Valid values are:
 
@@ -611,7 +611,7 @@ Accept wildcard characters: False
 
 ### -ProxyTargetPort
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ProxyTargetPort parameter specifies the port on the Microsoft Exchange IMAP4 Backend service that listens for client connections that are proxied from the Microsoft Exchange IMAP4 service. The default value is 1993.
 
@@ -629,7 +629,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
 
@@ -654,7 +654,7 @@ Accept wildcard characters: False
 
 ### -ShowHiddenFoldersEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ShowHiddenFoldersEnabled parameter specifies whether hidden mailbox folders are visible. Valid values are:
 
@@ -675,7 +675,7 @@ Accept wildcard characters: False
 
 ### -SSLBindings
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SSLBindings parameter specifies the IP address and TCP port that's used for IMAP4 connection that's always encrypted by SSL/TLS. This parameter uses the syntax `IPv4OrIPv6Address:Port`.
 
@@ -699,7 +699,7 @@ Accept wildcard characters: False
 
 ### -SuppressReadReceipt
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SuppressReadReceipt parameter specifies whether to stop duplicate read receipts from being sent to IMAP4 clients that have the Send read receipts for messages I send setting configured in their IMAP4 email program. Valid values are:
 
@@ -720,7 +720,7 @@ Accept wildcard characters: False
 
 ### -UnencryptedOrTLSBindings
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The UnencryptedOrTLSBindings parameter specifies the IP address and TCP port that's used for unencrypted IMAP4 connections, or IMAP4 connections that are encrypted by using opportunistic TLS (STARTTLS) after the initial unencrypted protocol handshake. This parameter uses the syntax `IPv4OrIPv6Address:Port`.
 
@@ -744,7 +744,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
@@ -762,7 +762,7 @@ Accept wildcard characters: False
 
 ### -X509CertificateName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The X509CertificateName parameter specifies the certificate that's used for encrypting IMAP4 client connections.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-InboxRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-InboxRule.md
index a9d14c5d20..88e296d6ef 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-InboxRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-InboxRule.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -115,7 +115,7 @@ This example modifies the action of the existing Inbox rule ProjectContoso. The
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the Inbox rule that you want to modify. You can use any value that uniquely identifies the rule. For example:
 
@@ -138,7 +138,7 @@ Accept wildcard characters: False
 
 ### -AlwaysDeleteOutlookRulesBlob
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AlwaysDeleteOutlookRulesBlob switch hides a warning message when you use Outlook on the web (formerly known as Outlook Web App) or Exchange PowerShell to modify Inbox rules. You don't need to specify a value with this switch.
 
@@ -156,7 +156,7 @@ Accept wildcard characters: False
 
 ### -ApplyCategory
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ApplyCategory parameter specifies an action for the Inbox rule that applies the specified category to messages. A valid value is any text value that you want to define as a category. You can specify multiple categories separated by commas. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -176,7 +176,7 @@ Accept wildcard characters: False
 
 ### -ApplySystemCategory
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ApplySystemCategory parameter specifies an action for the Inbox rule that applies the specified system category to messages. System categories are available to all mailboxes in the organization. Valid values are:
 
@@ -223,7 +223,7 @@ Accept wildcard characters: False
 
 ### -BodyContainsWords
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The BodyContainsWords parameter specifies a condition for the Inbox rule that looks for the specified words or phrases in the body of messages.
 
@@ -249,7 +249,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -270,7 +270,7 @@ Accept wildcard characters: False
 
 ### -CopyToFolder
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The CopyToFolder parameter specifies an action for the Inbox rule that copies messages to the specified mailbox folder. The syntax is `MailboxID:\ParentFolder[\SubFolder]`.
 
@@ -303,7 +303,7 @@ Accept wildcard characters: False
 
 ### -DeleteSystemCategory
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DeleteSystemCategory parameter specifies an action for the Inbox rule that deletes the specified system category from messages. System categories are available to all mailboxes in the organization. Valid values are:
 
@@ -348,7 +348,7 @@ Accept wildcard characters: False
 
 ### -DeleteMessage
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DeleteMessage parameter specifies an action for the Inbox rule that sends messages to the Deleted Items folder. Valid values are:
 
@@ -369,7 +369,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -389,7 +389,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfBodyContainsWords
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ExceptIfBodyContainsWords parameter specifies an exception for the Inbox rule that looks for the specified words or phrases in the body of messages.
 
@@ -415,7 +415,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfFlaggedForAction
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ExceptIfFlaggedForAction parameter specifies an exception for the Inbox rule that looks messages with the specified message flag. Valid values are:
 
@@ -447,7 +447,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfFrom
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ExceptIfFrom parameter specifies an exception for the Inbox rule that looks for the specified sender in messages. You can use any value that uniquely identifies the sender. For example:
 
@@ -476,7 +476,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfFromAddressContainsWords
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ExceptIfFromAddressContainsWords parameter specifies an exception for the Inbox rule that looks for messages where the specified words are in the sender's email address.
 
@@ -502,7 +502,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfHasAttachment
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ExceptIfHasAttachment parameter specifies an exception for the Inbox rule that looks for messages with attachments. Valid values are:
 
@@ -525,7 +525,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfHasClassification
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ExceptIfHasClassification parameter specifies an exception for the Inbox rule that looks for messages with the specified message classification. You can find message classifications by using the Get-MessageClassification cmdlet. You can specify multiple message classifications separated by commas.
 
@@ -545,7 +545,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfHeaderContainsWords
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The HeaderContainsWords parameter specifies an exception for the Inbox rule that looks for the specified words or phrases in the header fields of messages.
 
@@ -571,7 +571,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfMessageTypeMatches
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ExceptIfMessageTypeMatches parameter specifies an exception for the Inbox rule that looks for messages of the specified type. Valid values are:
 
@@ -603,7 +603,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfMyNameInCcBox
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ExceptIfMyNameInCcBox parameter specifies an exception for the Inbox rule that looks for messages where the mailbox owner is in the Cc field. Valid values are:
 
@@ -626,7 +626,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfMyNameInToBox
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ExceptIfMyNameInToBox parameter specifies an exception for the Inbox rule that looks for messages where the mailbox owner is in the To field. Valid values are:
 
@@ -649,7 +649,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfMyNameInToOrCcBox
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ExceptIfMyNameInToOrCcBox parameter specifies an exception for the Inbox rule that looks for messages where the mailbox owner is in the To or Cc fields Valid values are.
 
@@ -672,7 +672,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfMyNameNotInToBox
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ExceptIfMyNameNotInToBox parameter specifies an exception for the Inbox rule that looks for messages where the mailbox owner isn't in the To field. Valid values are:
 
@@ -695,7 +695,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfReceivedAfterDate
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ExceptIfReceivedAfterDate parameter specifies an exception for the Inbox rule that looks for messages received after the specified date.
 
@@ -717,7 +717,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfReceivedBeforeDate
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ExceptIfReceivedBeforeDate parameter specifies an exception for the Inbox rule that looks for messages received before the specified date.
 
@@ -739,7 +739,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfRecipientAddressContainsWords
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ExceptIfRecipientAddressContainsWords parameter specifies an exception for the Inbox rule that looks for messages where the specified words are in recipient email addresses.
 
@@ -765,7 +765,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfSentOnlyToMe
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ExceptIfSentOnlyToMe parameter specifies an exception for the Inbox rule that looks for messages where the only recipient is the mailbox owner. Valid values are:
 
@@ -788,7 +788,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfSentTo
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ExceptIfSentTo parameter specifies an exception that looks for recipients in messages. You can use any value that uniquely identifies the recipient. For example:
 
@@ -817,7 +817,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfSubjectContainsWords
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ExceptIfSubjectContainsWords parameter specifies an exception for the Inbox rule that looks for the specified words or phrases in the Subject field of messages.
 
@@ -843,7 +843,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfSubjectOrBodyContainsWords
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ExceptIfSubjectOrBodyContainsWords parameter specifies an exception for the Inbox rule that looks for the specified words or phrases in the Subject field or body of messages.
 
@@ -869,7 +869,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfWithImportance
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ExceptIfWithImportance parameter specifies an exception for the Inbox rule that looks for messages with the specified importance level. Valid values are:
 
@@ -893,7 +893,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfWithinSizeRangeMaximum
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ExceptIfWithinSizeRangeMaximum parameter specifies part of an exception for the Inbox rule that looks for messages that smaller than specified maximum size.
 
@@ -925,7 +925,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfWithinSizeRangeMinimum
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ExceptIfWithinSizeRangeMinimum parameter specifies part of an exception for the Inbox rule that looks for messages that are larger than the specified minimum size.
 
@@ -957,7 +957,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfWithSensitivity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ExceptIfWithSensitivity parameter specifies an exception for the Inbox rule that looks for messages with the specified sensitivity level. Valid values are:
 
@@ -982,7 +982,7 @@ Accept wildcard characters: False
 
 ### -FlaggedForAction
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The FlaggedForAction parameter specifies a condition for the Inbox rule that looks for messages with the specified message flag. Valid values are:
 
@@ -1012,7 +1012,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -1032,7 +1032,7 @@ Accept wildcard characters: False
 
 ### -ForwardAsAttachmentTo
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ForwardAsAttachmentTo parameter specifies an action for the Inbox rule that forwards the message to the specified recipient as an attachment. You can use any value that uniquely identifies the recipient. For example:
 
@@ -1059,7 +1059,7 @@ Accept wildcard characters: False
 
 ### -ForwardTo
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ForwardTo parameter specifies an action for the Inbox rule that forwards the message to the specified recipient. You can use any value that uniquely identifies the recipient. For example:
 
@@ -1086,7 +1086,7 @@ Accept wildcard characters: False
 
 ### -From
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The From parameter specifies a condition for the Inbox rule that looks for the specified sender in messages. You can use any value that uniquely identifies the sender. For example:
 
@@ -1115,7 +1115,7 @@ Accept wildcard characters: False
 
 ### -FromAddressContainsWords
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The FromAddressContainsWords parameter specifies a condition for the Inbox rule that looks for messages where the specified words are in the sender's email address.
 
@@ -1141,7 +1141,7 @@ Accept wildcard characters: False
 
 ### -HasAttachment
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The HasAttachment parameter specifies a condition for the Inbox rule that looks for messages with attachments. Valid values are:
 
@@ -1164,7 +1164,7 @@ Accept wildcard characters: False
 
 ### -HasClassification
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The HasClassification parameter specifies a condition for the Inbox rule that looks for messages with the specified message classification. You can find message classifications by using the Get-MessageClassification cmdlet. You can specify multiple message classifications separated by commas.
 
@@ -1184,7 +1184,7 @@ Accept wildcard characters: False
 
 ### -HeaderContainsWords
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The HeaderContainsWords parameter specifies a condition for the Inbox rule that looks for the specified words or phrases in the header fields of messages.
 
@@ -1210,7 +1210,7 @@ Accept wildcard characters: False
 
 ### -Mailbox
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Mailbox parameter specifies the mailbox that contains the Inbox rule. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -1239,7 +1239,7 @@ Accept wildcard characters: False
 
 ### -MarkAsRead
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MarkAsRead parameter specifies an action for the Inbox rule that marks messages as read. Valid values are:
 
@@ -1260,7 +1260,7 @@ Accept wildcard characters: False
 
 ### -MarkImportance
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MarkImportance parameter specifies an action for the Inbox rule that marks messages with the specified importance flag. Valid values are:
 
@@ -1282,7 +1282,7 @@ Accept wildcard characters: False
 
 ### -MessageTypeMatches
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MessageTypeMatches parameter specifies a condition for the Inbox rule that looks for messages of the specified type. Valid values are:
 
@@ -1314,7 +1314,7 @@ Accept wildcard characters: False
 
 ### -MoveToFolder
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MoveToFolder parameter specifies an action for the Inbox rule that moves messages to the specified mailbox folder. The syntax is `MailboxID:\ParentFolder[\SubFolder]`.
 
@@ -1347,7 +1347,7 @@ Accept wildcard characters: False
 
 ### -MyNameInCcBox
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MyNameInCcBox parameter specifies a condition for the Inbox rule that looks for messages where the mailbox owner is in the Cc field. Valid values are:
 
@@ -1370,7 +1370,7 @@ Accept wildcard characters: False
 
 ### -MyNameInToBox
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MyNameInToBox parameter specifies a condition for the Inbox rule that looks for messages where the mailbox owner is in the To field. Valid values are:
 
@@ -1393,7 +1393,7 @@ Accept wildcard characters: False
 
 ### -MyNameInToOrCcBox
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MyNameInToOrCcBox parameter specifies a condition for the Inbox rule that looks for messages where the mailbox owner is in the To or Cc fields Valid values are.
 
@@ -1416,7 +1416,7 @@ Accept wildcard characters: False
 
 ### -MyNameNotInToBox
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MyNameNotInToBox parameter specifies a condition for the Inbox rule that looks for messages where the mailbox owner isn't in the To field. Valid values are:
 
@@ -1439,7 +1439,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Name parameter specifies a name for the Inbox rule. The maximum length is 512 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -1457,7 +1457,7 @@ Accept wildcard characters: False
 
 ### -PinMessage
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The PinMessage parameter specifies an action for the Inbox rule that pins messages to the top of the Inbox. Valid values are:
 
@@ -1478,7 +1478,7 @@ Accept wildcard characters: False
 
 ### -Priority
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Priority parameter specifies a priority for the Inbox rule that determines the order of rule processing. A lower integer value indicates a higher priority,
 
@@ -1496,7 +1496,7 @@ Accept wildcard characters: False
 
 ### -ReceivedAfterDate
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ReceivedAfterDate parameter specifies a condition for the Inbox rule that looks for messages received after the specified date.
 
@@ -1518,7 +1518,7 @@ Accept wildcard characters: False
 
 ### -ReceivedBeforeDate
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ReceivedBeforeDate parameter specifies a condition for the Inbox rule that looks for messages received before the specified date.
 
@@ -1540,7 +1540,7 @@ Accept wildcard characters: False
 
 ### -RecipientAddressContainsWords
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RecipientAddressContainsWords parameter specifies a condition for the Inbox rule that looks for messages where the specified words are in recipient email addresses.
 
@@ -1566,7 +1566,7 @@ Accept wildcard characters: False
 
 ### -RedirectTo
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RedirectTo parameter specifies an action for the Inbox rule that redirects the message to the specified recipient. You can use any value that uniquely identifies the recipient. For example:
 
@@ -1593,7 +1593,7 @@ Accept wildcard characters: False
 
 ### -SendTextMessageNotificationTo
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1617,7 +1617,7 @@ Accept wildcard characters: False
 
 ### -SentOnlyToMe
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SentOnlyToMe parameter specifies a condition for the Inbox rule that looks for messages where the only recipient is the mailbox owner. Valid values are:
 
@@ -1640,7 +1640,7 @@ Accept wildcard characters: False
 
 ### -SentTo
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SentTo parameter specifies a condition for the Inbox rule that looks for messages with the specified recipients. You can use any value that uniquely identifies the recipient. For example:
 
@@ -1689,7 +1689,7 @@ Accept wildcard characters: False
 
 ### -StopProcessingRules
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The StopProcessingRules parameter specifies an action for the Inbox rule that stops processing additional rules if the conditions of this Inbox rule are met. Valid values are:If set to $true, the StopProcessingRules parameter instructs Exchange to stop processing additional rules if the conditions of this Inbox rule are met.
 
@@ -1710,7 +1710,7 @@ Accept wildcard characters: False
 
 ### -SubjectContainsWords
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SubjectContainsWords parameter specifies a condition for the Inbox rule that looks for the specified words or phrases in the Subject field of messages.
 
@@ -1736,7 +1736,7 @@ Accept wildcard characters: False
 
 ### -SubjectOrBodyContainsWords
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SubjectOrBodyContainsWords parameter specifies a condition for the Inbox rule that looks for the specified words or phrases in the Subject field or body of messages.
 
@@ -1762,7 +1762,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
@@ -1780,7 +1780,7 @@ Accept wildcard characters: False
 
 ### -WithImportance
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WithImportance parameter specifies a condition for the Inbox rule that looks for messages with the specified importance level. Valid values are:
 
@@ -1804,7 +1804,7 @@ Accept wildcard characters: False
 
 ### -WithinSizeRangeMaximum
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WithinSizeRangeMaximum parameter specifies part of a condition for the Inbox rule that looks for messages that are smaller than specified maximum size.
 
@@ -1836,7 +1836,7 @@ Accept wildcard characters: False
 
 ### -WithinSizeRangeMinimum
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WithinSizeRangeMinimum parameter specifies part of a condition for the Inbox rule that looks for messages that are larger than the specified minimum size.
 
@@ -1868,7 +1868,7 @@ Accept wildcard characters: False
 
 ### -WithSensitivity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WithSensitivity parameter specifies a condition for the Inbox rule that looks for messages with the specified sensitivity level. Valid values are:
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-IntraOrganizationConnector.md b/exchange/exchange-ps/ExchangePowerShell/Set-IntraOrganizationConnector.md
index 54ac46f17a..a1f7a1c74d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-IntraOrganizationConnector.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-IntraOrganizationConnector.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
 Locale: en-US
@@ -51,7 +51,7 @@ This example disables the Intra-Organization connector named "MainCloudConnector
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the Intra-Organization connector that you want to modify. You can use any value that uniquely identifies the connector. For example:
 
@@ -73,7 +73,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -94,7 +94,7 @@ Accept wildcard characters: False
 
 ### -DiscoveryEndpoint
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DiscoveryEndpoint parameter specifies the externally accessible URL used for the Autodiscover service for the domain configured in the IntraOrganization Connector. This parameter is automatically populated with the TargetAutodiscoverEpr value from the Get-FederationInformation cmdlet for the defined domain.
 
@@ -112,7 +112,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -132,7 +132,7 @@ Accept wildcard characters: False
 
 ### -Enabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Enabled parameter enables or disabled the Intra-organization connector. The valid values for this parameter are $true or $false. The default value is $true.
 
@@ -152,7 +152,7 @@ Accept wildcard characters: False
 
 ### -TargetAddressDomains
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The TargetAddressDomains parameter specifies the domain namespaces to be used in the Intra-Organization connector. The domains must have valid Autodiscover endpoints defined in their organizations. The domains and their associated Autodiscover endpoints are used by the Intra-Organization connector for feature and service connectivity.
 
@@ -190,7 +190,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-JournalRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-JournalRule.md
index f0a36d4384..05448cdeb4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-JournalRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-JournalRule.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailControl-Help.xml
 Locale: en-US
@@ -47,6 +47,8 @@ Set-JournalRule "Consolidated Messenger" -JournalEmailAddress "ArchiveMailbox@co
 
 This example modifies the journal email address to which journal reports are sent by the existing journal rule Consolidated Messenger.
 
+The Identity parameter is positional, which means you can use it without the -Identity label in the supported location in the command (in this case, first).  For more information about positional parameters, see [About Parameters](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_parameters).
+
 ### Example 2
 ```powershell
 Get-JournalRule | Set-JournalRule -JournalEmailAddress "Archive Mailbox"
@@ -58,12 +60,10 @@ This example modifies the journal email address for all journal rules. The Get-J
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the name or GUID of the rule you want to modify.
 
-The Identity parameter is a positional parameter. When using positional parameters in a command, you can omit the parameter label.
-
 ```yaml
 Type: RuleIdParameter
 Parameter Sets: (All)
@@ -78,7 +78,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -99,7 +99,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -119,7 +119,7 @@ Accept wildcard characters: False
 
 ### -JournalEmailAddress
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The JournalEmailAddress parameter specifies a journal recipient. Journal reports for the specified rule are sent to the journal recipient. You can use any value that uniquely identifies the recipient. For example:
 
@@ -144,7 +144,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Name parameter specifies the name of the journal rule. The name of the rule can be up to 64 characters.
 
@@ -162,7 +162,7 @@ Accept wildcard characters: False
 
 ### -Recipient
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Recipient parameter specifies the SMTP address of a mailbox, contact, or distribution group to journal. If you specify a distribution group, all recipients in that distribution group are journaled. All messages sent to or received from a recipient are journaled.
 
@@ -182,7 +182,7 @@ Accept wildcard characters: False
 
 ### -Scope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Scope parameter specifies the scope of email messages to which the journal rule is applied. You can use the following values:
 
@@ -204,7 +204,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailContact.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailContact.md
index 35488447ff..2b06f8b281 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-MailContact.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailContact.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -108,7 +108,7 @@ This example sets John Rodman's external email address to john@contoso.com.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the mail contact that you want to modify. You can use any value that uniquely identifies the mail contact. For example:
 
@@ -133,7 +133,7 @@ Accept wildcard characters: False
 
 ### -AcceptMessagesOnlyFrom
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The AcceptMessagesOnlyFrom parameter specifies who is allowed to send messages to this recipient. Messages from other senders are rejected.
 
@@ -168,7 +168,7 @@ Accept wildcard characters: False
 
 ### -AcceptMessagesOnlyFromDLMembers
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The AcceptMessagesOnlyFromDLMembers parameter specifies who is allowed to send messages to this recipient. Messages from other senders are rejected.
 
@@ -203,7 +203,7 @@ Accept wildcard characters: False
 
 ### -AcceptMessagesOnlyFromSendersOrMembers
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The AcceptMessagesOnlyFromSendersOrMembers parameter specifies who is allowed to send messages to this recipient. Messages from other senders are rejected.
 
@@ -240,7 +240,7 @@ Accept wildcard characters: False
 
 ### -Alias
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Alias parameter specifies the Exchange alias (also known as the mail nickname) for the recipient. This value identifies the recipient as a mail-enabled object, and shouldn't be confused with multiple email addresses for the same recipient (also known as proxy addresses). A recipient can have only one Alias value. The maximum length is 64 characters.
 
@@ -276,7 +276,7 @@ Accept wildcard characters: False
 
 ### -ArbitrationMailbox
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -307,7 +307,7 @@ Accept wildcard characters: False
 
 ### -BypassModerationFromSendersOrMembers
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The BypassModerationFromSendersOrMembers parameter specifies who is allowed to send messages to this moderated recipient without approval from a moderator. Valid values for this parameter are individual senders and groups in your organization. Specifying a group means all members of the group are allowed to send messages to this recipient without approval from a moderator.
 
@@ -340,7 +340,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -361,7 +361,7 @@ Accept wildcard characters: False
 
 ### -CreateDTMFMap
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -384,7 +384,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute1
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the CustomAttribute1 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -402,7 +402,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute10
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the CustomAttribute10 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -420,7 +420,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute11
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the CustomAttribute11 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -438,7 +438,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute12
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the CustomAttribute12 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -456,7 +456,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute13
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the CustomAttribute13 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -474,7 +474,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute14
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the CustomAttribute14 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -492,7 +492,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute15
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the CustomAttribute15 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -510,7 +510,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute2
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the CustomAttribute2 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -528,7 +528,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute3
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the CustomAttribute3 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -546,7 +546,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute4
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the CustomAttribute4 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -564,7 +564,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute5
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the CustomAttribute5 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -582,7 +582,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute6
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the CustomAttribute6 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -600,7 +600,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute7
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the CustomAttribute7 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -618,7 +618,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute8
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the CustomAttribute8 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -636,7 +636,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute9
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the CustomAttribute9 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -654,7 +654,7 @@ Accept wildcard characters: False
 
 ### -DisplayName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The DisplayName parameter specifies the display name of the mail contact. The display name is visible in the Exchange admin center (EAC) and in address lists. The maximum length is 256 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -672,7 +672,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -692,7 +692,7 @@ Accept wildcard characters: False
 
 ### -EmailAddresses
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The EmailAddresses parameter specifies all email addresses (proxy addresses) for the recipient, including the primary SMTP address. In on-premises Exchange organizations, the primary SMTP address and other proxy addresses are typically set by email address policies. However, you can use this parameter to configure other proxy addresses for the recipient. For more information, see [Email address policies in Exchange Server](https://learn.microsoft.com/Exchange/email-addresses-and-address-books/email-address-policies/email-address-policies).
 
@@ -731,7 +731,7 @@ Accept wildcard characters: False
 
 ### -EmailAddressPolicyEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -754,7 +754,7 @@ Accept wildcard characters: False
 
 ### -ExtensionCustomAttribute1
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the ExtensionCustomAttribute1 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas.
 
@@ -778,7 +778,7 @@ Accept wildcard characters: False
 
 ### -ExtensionCustomAttribute2
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the ExtensionCustomAttribute2 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas.
 
@@ -802,7 +802,7 @@ Accept wildcard characters: False
 
 ### -ExtensionCustomAttribute3
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the ExtensionCustomAttribute3 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas.
 
@@ -826,7 +826,7 @@ Accept wildcard characters: False
 
 ### -ExtensionCustomAttribute4
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the ExtensionCustomAttribute4 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas.
 
@@ -850,7 +850,7 @@ Accept wildcard characters: False
 
 ### -ExtensionCustomAttribute5
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the ExtensionCustomAttribute5 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas.
 
@@ -874,7 +874,7 @@ Accept wildcard characters: False
 
 ### -ExternalEmailAddress
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ExternalEmailAddress parameter specifies the target email address of the mail contact or mail user. By default, this value is used as the primary email address of the mail contact or mail user.
 
@@ -896,7 +896,7 @@ Accept wildcard characters: False
 
 ### -ForceUpgrade
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ForceUpgrade switch suppresses the confirmation message that appears if the object was created in a previous version of Exchange. You don't need to specify a value with this switch.
 
@@ -914,7 +914,7 @@ Accept wildcard characters: False
 
 ### -GrantSendOnBehalfTo
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The GrantSendOnBehalfTo parameter specifies who can send on behalf of this mail contact. Although messages sent on behalf of the mail contact clearly show the sender in the From field (`<Sender> on behalf of <Mail contact>`), replies to these messages are delivered to the mail contact, not the sender.
 
@@ -951,7 +951,7 @@ Accept wildcard characters: False
 
 ### -HiddenFromAddressListsEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The HiddenFromAddressListsEnabled parameter specifies whether this recipient is visible in address lists. Valid values are:
 
@@ -972,7 +972,7 @@ Accept wildcard characters: False
 
 ### -IgnoreDefaultScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -997,7 +997,7 @@ Accept wildcard characters: False
 
 ### -MacAttachmentFormat
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The MacAttachmentFormat parameter specifies the Apple Macintosh operating system attachment format to use for messages sent to the mail contact or mail user. Valid values are:
 
@@ -1025,7 +1025,7 @@ Accept wildcard characters: False
 
 ### -MailTip
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The MailTip parameter specifies the custom MailTip text for this recipient. The MailTip is shown to senders when they start drafting an email message to this recipient. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -1048,7 +1048,7 @@ Accept wildcard characters: False
 
 ### -MailTipTranslations
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The MailTipTranslations parameter specifies additional languages for the custom MailTip text that's defined by the MailTip parameter. HTML tags are automatically added to the MailTip translation, additional HTML tags aren't supported, and the length of the MailTip translation can't exceed 175 displayed characters.
 
@@ -1074,7 +1074,7 @@ Accept wildcard characters: False
 
 ### -MaxReceiveSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1109,7 +1109,7 @@ Accept wildcard characters: False
 
 ### -MaxRecipientPerMessage
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1133,7 +1133,7 @@ Accept wildcard characters: False
 
 ### -MaxSendSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1168,7 +1168,7 @@ Accept wildcard characters: False
 
 ### -MessageBodyFormat
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The MessageBodyFormat parameter specifies the message body format for messages sent to the mail contact or mail user. Valid values are:
 
@@ -1195,7 +1195,7 @@ Accept wildcard characters: False
 
 ### -MessageFormat
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The MessageFormat parameter specifies the message format for messages sent to the mail contact or mail user. Valid values are:
 
@@ -1223,7 +1223,7 @@ Accept wildcard characters: False
 
 ### -ModeratedBy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ModeratedBy parameter specifies one or more moderators for this recipient. A moderator approves messages sent to the recipient before the messages are delivered. A moderator must be a mailbox, mail user, or mail contact in your organization. You can use any value that uniquely identifies the moderator. For example:
 
@@ -1254,7 +1254,7 @@ Accept wildcard characters: False
 
 ### -ModerationEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ModerationEnabled parameter specifies whether moderation is enabled for this recipient. Valid value are:
 
@@ -1277,7 +1277,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Name parameter specifies the unique name of the mail contact. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -1295,7 +1295,7 @@ Accept wildcard characters: False
 
 ### -PrimarySmtpAddress
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1321,7 +1321,7 @@ Accept wildcard characters: False
 
 ### -RejectMessagesFrom
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The RejectMessagesFrom parameter specifies who isn't allowed to send messages to this recipient. Messages from these senders are rejected.
 
@@ -1356,7 +1356,7 @@ Accept wildcard characters: False
 
 ### -RejectMessagesFromDLMembers
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The RejectMessagesFromDLMembers parameter specifies who isn't allowed to send messages to this recipient. Messages from these senders are rejected.
 
@@ -1391,7 +1391,7 @@ Accept wildcard characters: False
 
 ### -RejectMessagesFromSendersOrMembers
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The RejectMessagesFromSendersOrMembers parameter specifies who isn't allowed to send messages to this recipient. Messages from these senders are rejected.
 
@@ -1428,7 +1428,7 @@ Accept wildcard characters: False
 
 ### -RemovePicture
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1450,7 +1450,7 @@ Accept wildcard characters: False
 
 ### -RemoveSpokenName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1472,7 +1472,7 @@ Accept wildcard characters: False
 
 ### -RequireSenderAuthenticationEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The RequireSenderAuthenticationEnabled parameter specifies whether to accept messages only from authenticated (internal) senders. Valid values are:
 
@@ -1493,7 +1493,7 @@ Accept wildcard characters: False
 
 ### -SecondaryAddress
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1513,7 +1513,7 @@ Accept wildcard characters: False
 
 ### -SecondaryDialPlan
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1533,7 +1533,7 @@ Accept wildcard characters: False
 
 ### -SendModerationNotifications
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The SendModerationNotifications parameter specifies when moderation notification messages are sent. Valid values are:
 
@@ -1557,7 +1557,7 @@ Accept wildcard characters: False
 
 ### -SimpleDisplayName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The SimpleDisplayName parameter is used to display an alternative description of the object when only a limited set of characters is permitted. Valid characters are:
 
@@ -1581,7 +1581,7 @@ Accept wildcard characters: False
 
 ### -UMDtmfMap
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1613,7 +1613,7 @@ Accept wildcard characters: False
 
 ### -UseMapiRichTextFormat
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The UseMapiRichTextFormat parameter specifies what to do with messages that are sent to the mail user or mail contact in MAPI rich text format, also known as Outlook Rich Text or Transport Neutral Encapsulation Format (TNEF). Valid values are:
 
@@ -1637,7 +1637,7 @@ Accept wildcard characters: False
 
 ### -UsePreferMessageFormat
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The UsePreferMessageFormat specifies whether the message format settings configured for the mail user or mail contact override the global settings configured for the remote domain or configured by the message sender. Valid value are:
 
@@ -1698,7 +1698,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
@@ -1716,7 +1716,7 @@ Accept wildcard characters: False
 
 ### -WindowsEmailAddress
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WindowsEmailAddress parameter specifies the Windows email address for this recipient. This is a common Active Directory attribute that's present in all environments, including environments without Exchange. Using the WindowsEmailAddress parameter on a recipient has one of the following results:
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailPublicFolder.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailPublicFolder.md
index 08ae62604e..1b5c034778 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-MailPublicFolder.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailPublicFolder.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.WebClient-Help.xml
 Locale: en-US
@@ -122,7 +122,7 @@ This example removes the secondary email address MyPublicFolder@fabrikam.com fro
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the GUID or public folder name that represents a specific public folder. You can also include the path using the format \\TopLevelPublicFolder\\PublicFolder.
 
@@ -142,7 +142,7 @@ Accept wildcard characters: False
 
 ### -AcceptMessagesOnlyFrom
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AcceptMessagesOnlyFrom parameter specifies who is allowed to send messages to this recipient. Messages from other senders are rejected.
 
@@ -177,7 +177,7 @@ Accept wildcard characters: False
 
 ### -AcceptMessagesOnlyFromDLMembers
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AcceptMessagesOnlyFromDLMembers parameter specifies who is allowed to send messages to this recipient. Messages from other senders are rejected.
 
@@ -212,7 +212,7 @@ Accept wildcard characters: False
 
 ### -AcceptMessagesOnlyFromSendersOrMembers
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AcceptMessagesOnlyFromSendersOrMembers parameter specifies who is allowed to send messages to this recipient. Messages from other senders are rejected.
 
@@ -249,7 +249,7 @@ Accept wildcard characters: False
 
 ### -Alias
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Alias parameter specifies the Exchange alias (also known as the mail nickname) for the recipient. This value identifies the recipient as a mail-enabled object, and shouldn't be confused with multiple email addresses for the same recipient (also known as proxy addresses). A recipient can have only one Alias value. The maximum length is 64 characters.
 
@@ -316,7 +316,7 @@ Accept wildcard characters: False
 
 ### -BypassModerationFromSendersOrMembers
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The BypassModerationFromSendersOrMembers parameter specifies who is allowed to send messages to this moderated recipient without approval from a moderator. Valid values for this parameter are individual senders and groups in your organization. Specifying a group means all members of the group are allowed to send messages to this recipient without approval from a moderator.
 
@@ -349,7 +349,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -370,7 +370,7 @@ Accept wildcard characters: False
 
 ### -Contacts
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Contacts parameter specifies the contacts for the public folder. Contacts are persons about whom you can save several types of information, such as addresses, telephone numbers, and web page URLs.
 
@@ -417,7 +417,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute1
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter specifies a value for the CustomAttribute1 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -435,7 +435,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute10
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter specifies a value for the CustomAttribute10 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -453,7 +453,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute11
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter specifies a value for the CustomAttribute11 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -471,7 +471,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute12
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter specifies a value for the CustomAttribute12 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -489,7 +489,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute13
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter specifies a value for the CustomAttribute13 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -507,7 +507,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute14
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter specifies a value for the CustomAttribute14 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -525,7 +525,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute15
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter specifies a value for the CustomAttribute15 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -543,7 +543,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute2
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter specifies a value for the CustomAttribute2 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -561,7 +561,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute3
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter specifies a value for the CustomAttribute3 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -579,7 +579,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute4
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter specifies a value for the CustomAttribute4 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -597,7 +597,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute5
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter specifies a value for the CustomAttribute5 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -615,7 +615,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute6
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter specifies a value for the CustomAttribute6 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -633,7 +633,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute7
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter specifies a value for the CustomAttribute7 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -651,7 +651,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute8
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter specifies a value for the CustomAttribute8 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -669,7 +669,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute9
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter specifies a value for the CustomAttribute9 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -687,7 +687,7 @@ Accept wildcard characters: False
 
 ### -DeliverToMailboxAndForward
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DeliverToMailboxAndForward parameter specifies the message delivery behavior when a forwarding address is specified by the ForwardingAddress or ForwardingSmtpAddress parameters. Valid values are:
 
@@ -710,7 +710,7 @@ Accept wildcard characters: False
 
 ### -DisplayName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DisplayName parameter specifies the display name of the Public Folder Proxy object. The display name is visible in the Exchange admin center, address lists, and Outlook. The maximum length is 256 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -728,7 +728,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -748,7 +748,7 @@ Accept wildcard characters: False
 
 ### -EmailAddresses
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The EmailAddresses parameter specifies all email addresses (proxy addresses) for the recipient, including the primary SMTP address. In on-premises Exchange organizations, the primary SMTP address and other proxy addresses are typically set by email address policies. However, you can use this parameter to configure other proxy addresses for the recipient. For more information, see [Email address policies in Exchange Server](https://learn.microsoft.com/Exchange/email-addresses-and-address-books/email-address-policies/email-address-policies).
 
@@ -787,7 +787,7 @@ Accept wildcard characters: False
 
 ### -EmailAddressPolicyEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The EmailAddressPolicyEnabled parameter specifies whether to apply email address policies to this recipient. Valid values are:
 
@@ -808,7 +808,7 @@ Accept wildcard characters: False
 
 ### -EntryId
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The EntryId parameter specifies the EntryID value for the public folder. You use this parameter to correct an existing EntryID that points to a folder that can't be found.
 
@@ -826,7 +826,7 @@ Accept wildcard characters: False
 
 ### -ExtensionCustomAttribute1
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter specifies a value for the ExtensionCustomAttribute1 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas.
 
@@ -850,7 +850,7 @@ Accept wildcard characters: False
 
 ### -ExtensionCustomAttribute2
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter specifies a value for the ExtensionCustomAttribute2 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas.
 
@@ -874,7 +874,7 @@ Accept wildcard characters: False
 
 ### -ExtensionCustomAttribute3
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter specifies a value for the ExtensionCustomAttribute3 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas.
 
@@ -898,7 +898,7 @@ Accept wildcard characters: False
 
 ### -ExtensionCustomAttribute4
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter specifies a value for the ExtensionCustomAttribute4 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas.
 
@@ -922,7 +922,7 @@ Accept wildcard characters: False
 
 ### -ExtensionCustomAttribute5
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter specifies a value for the ExtensionCustomAttribute5 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas.
 
@@ -946,7 +946,7 @@ Accept wildcard characters: False
 
 ### -ExternalEmailAddress
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ExternalEmailAddress parameter specifies an email address outside the organization.
 
@@ -964,7 +964,7 @@ Accept wildcard characters: False
 
 ### -ForwardingAddress
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ForwardingAddress parameter specifies a forwarding address for messages that are sent to this public folder. A valid value for this parameter is a recipient in your organization. You can use any value that uniquely identifies the recipient. For example:
 
@@ -996,7 +996,7 @@ Accept wildcard characters: False
 
 ### -GrantSendOnBehalfTo
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The GrantSendOnBehalfTo parameter specifies who can send on behalf of this public folder. Although messages sent on behalf of the mail user clearly show the sender in the From field (`<Sender> on behalf of <PublicFolder>`), replies to these messages are delivered to the public folder, not the sender.
 
@@ -1033,7 +1033,7 @@ Accept wildcard characters: False
 
 ### -HiddenFromAddressListsEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The HiddenFromAddressListsEnabled parameter specifies whether this recipient is visible in address lists. Valid values are:
 
@@ -1054,7 +1054,7 @@ Accept wildcard characters: False
 
 ### -IgnoreDefaultScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange PowerShell session, and to use the entire forest as the scope. You don't need to specify a value with this switch.
 
@@ -1077,7 +1077,7 @@ Accept wildcard characters: False
 
 ### -IgnoreMissingFolderLink
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IgnoreMissingFolderLink parameter specifies whether to exclude the mail-enabled public folder from a specific validation check that's used during a public folder migration. Valid values are:
 
@@ -1098,7 +1098,7 @@ Accept wildcard characters: False
 
 ### -MailTip
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MailTip parameter specifies the custom MailTip text for this recipient. The MailTip is shown to senders when they start drafting an email message to this recipient. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -1121,7 +1121,7 @@ Accept wildcard characters: False
 
 ### -MailTipTranslations
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MailTipTranslations parameter specifies additional languages for the custom MailTip text that's defined by the MailTip parameter. HTML tags are automatically added to the MailTip translation, additional HTML tags aren't supported, and the length of the MailTip translation can't exceed 175 displayed characters.
 
@@ -1147,7 +1147,7 @@ Accept wildcard characters: False
 
 ### -MaxReceiveSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MaxReceiveSize parameter specifies the maximum size of a message that can be sent to the public folder. Messages larger than the maximum size are rejected.
 
@@ -1178,7 +1178,7 @@ Accept wildcard characters: False
 
 ### -MaxSendSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MaxSendSize parameter specifies the maximum size of a message that can be sent by the public folder.
 
@@ -1209,7 +1209,7 @@ Accept wildcard characters: False
 
 ### -ModeratedBy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ModeratedBy parameter specifies one or more moderators for this recipient. A moderator approves messages sent to the recipient before the messages are delivered. A moderator must be a mailbox, mail user, or mail contact in your organization. You can use any value that uniquely identifies the moderator. For example:
 
@@ -1240,7 +1240,7 @@ Accept wildcard characters: False
 
 ### -ModerationEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ModerationEnabled parameter specifies whether moderation is enabled for this recipient. Valid value are:
 
@@ -1263,7 +1263,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Name parameter specifies the unique name of the public folder. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -1281,7 +1281,7 @@ Accept wildcard characters: False
 
 ### -OnPremisesObjectId
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The OnPremisesObjectId parameter specifies the ObjectID (GUID) value of the mail-enabled public folder from the on-premises environment.
 
@@ -1299,7 +1299,7 @@ Accept wildcard characters: False
 
 ### -PhoneticDisplayName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The PhoneticDisplayName parameter specifies an alternate spelling of the user's name that's used for text to speech in Unified Messaging (UM) environments. Typically, you use this parameter when the pronunciation and spelling of the user's name don't match. The maximum length is 256 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -1317,7 +1317,7 @@ Accept wildcard characters: False
 
 ### -PrimarySmtpAddress
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The PrimarySmtpAddress parameter specifies the primary return email address that's used for the recipient. You can't use the EmailAddresses and PrimarySmtpAddress parameters in the same command.
 
@@ -1362,7 +1362,7 @@ Accept wildcard characters: False
 
 ### -RejectMessagesFrom
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RejectMessagesFrom parameter specifies who isn't allowed to send messages to this recipient. Messages from these senders are rejected.
 
@@ -1397,7 +1397,7 @@ Accept wildcard characters: False
 
 ### -RejectMessagesFromDLMembers
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RejectMessagesFromDLMembers parameter specifies who isn't allowed to send messages to this recipient. Messages from these senders are rejected.
 
@@ -1432,7 +1432,7 @@ Accept wildcard characters: False
 
 ### -RejectMessagesFromSendersOrMembers
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RejectMessagesFromSendersOrMembers parameter specifies who isn't allowed to send messages to this recipient. Messages from these senders are rejected.
 
@@ -1469,7 +1469,7 @@ Accept wildcard characters: False
 
 ### -RequireSenderAuthenticationEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RequireSenderAuthenticationEnabled parameter specifies whether to accept messages only from authenticated (internal) senders. Valid values are:
 
@@ -1490,7 +1490,7 @@ Accept wildcard characters: False
 
 ### -SendModerationNotifications
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SendModerationNotifications parameter specifies when moderation notification messages are sent. Valid values are:
 
@@ -1539,7 +1539,7 @@ Accept wildcard characters: False
 
 ### -SimpleDisplayName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SimpleDisplayName parameter is used to display an alternative description of the object when only a limited set of characters is permitted. Valid characters are:
 
@@ -1583,7 +1583,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
@@ -1601,7 +1601,7 @@ Accept wildcard characters: False
 
 ### -WindowsEmailAddress
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WindowsEmailAddress parameter specifies the Windows email address for this recipient. This is a common Active Directory attribute that's present in all environments, including environments without Exchange. Using the WindowsEmailAddress parameter on a recipient has one of the following results:
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailUser.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailUser.md
index 8ecd9e7617..fcdc2c27d6 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-MailUser.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailUser.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -960,7 +960,7 @@ This example modifies the external email address for the mail user named John Wo
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the mail user that you want to modify. You can use any value that uniquely identifies the mail user. For example:
 
@@ -985,7 +985,7 @@ Accept wildcard characters: False
 
 ### -AcceptMessagesOnlyFrom
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The AcceptMessagesOnlyFrom parameter specifies who is allowed to send messages to this recipient. Messages from other senders are rejected.
 
@@ -1020,7 +1020,7 @@ Accept wildcard characters: False
 
 ### -AcceptMessagesOnlyFromDLMembers
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The AcceptMessagesOnlyFromDLMembers parameter specifies who is allowed to send messages to this recipient. Messages from other senders are rejected.
 
@@ -1055,7 +1055,7 @@ Accept wildcard characters: False
 
 ### -AcceptMessagesOnlyFromSendersOrMembers
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The AcceptMessagesOnlyFromSendersOrMembers parameter specifies who is allowed to send messages to this recipient. Messages from other senders are rejected.
 
@@ -1092,7 +1092,7 @@ Accept wildcard characters: False
 
 ### -Alias
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Alias parameter specifies the Exchange alias (also known as the mail nickname) for the recipient. This value identifies the recipient as a mail-enabled object, and shouldn't be confused with multiple email addresses for the same recipient (also known as proxy addresses). A recipient can have only one Alias value. The maximum length is 64 characters.
 
@@ -1128,7 +1128,7 @@ Accept wildcard characters: False
 
 ### -ArbitrationMailbox
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1159,7 +1159,7 @@ Accept wildcard characters: False
 
 ### -ArchiveGuid
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter is reserved for internal Microsoft use.
 
@@ -1177,7 +1177,7 @@ Accept wildcard characters: False
 
 ### -ArchiveName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1197,7 +1197,7 @@ Accept wildcard characters: False
 
 ### -BypassModerationFromSendersOrMembers
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The BypassModerationFromSendersOrMembers parameter specifies who is allowed to send messages to this moderated recipient without approval from a moderator. Valid values for this parameter are individual senders and groups in your organization. Specifying a group means all members of the group are allowed to send messages to this recipient without approval from a moderator.
 
@@ -1230,7 +1230,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -1251,7 +1251,7 @@ Accept wildcard characters: False
 
 ### -CreateDTMFMap
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1274,7 +1274,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute1
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the CustomAttribute1 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -1292,7 +1292,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute10
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the CustomAttribute10 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -1310,7 +1310,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute11
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the CustomAttribute11 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -1328,7 +1328,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute12
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the CustomAttribute12 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -1346,7 +1346,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute13
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the CustomAttribute13 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -1364,7 +1364,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute14
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the CustomAttribute14 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -1382,7 +1382,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute15
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the CustomAttribute15 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -1400,7 +1400,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute2
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the CustomAttribute2 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -1418,7 +1418,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute3
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the CustomAttribute3 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -1436,7 +1436,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute4
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the CustomAttribute4 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -1454,7 +1454,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute5
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the CustomAttribute5 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -1472,7 +1472,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute6
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the CustomAttribute6 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -1490,7 +1490,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute7
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the CustomAttribute7 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -1508,7 +1508,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute8
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the CustomAttribute8 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -1526,7 +1526,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute9
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the CustomAttribute9 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -1570,7 +1570,7 @@ Accept wildcard characters: False
 
 ### -DisplayName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The DisplayName parameter specifies the display name of the mail user. The display name is visible in the Exchange admin center, address lists, and Outlook. The maximum length is 256 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -1588,7 +1588,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1608,7 +1608,7 @@ Accept wildcard characters: False
 
 ### -EmailAddresses
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The EmailAddresses parameter specifies all email addresses (proxy addresses) for the recipient, including the primary SMTP address. In on-premises Exchange organizations, the primary SMTP address and other proxy addresses are typically set by email address policies. However, you can use this parameter to configure other proxy addresses for the recipient. For more information, see [Email address policies in Exchange Server](https://learn.microsoft.com/Exchange/email-addresses-and-address-books/email-address-policies/email-address-policies).
 
@@ -1647,7 +1647,7 @@ Accept wildcard characters: False
 
 ### -EmailAddressPolicyEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1692,7 +1692,7 @@ Accept wildcard characters: False
 
 ### -ExchangeGuid
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter is reserved for internal Microsoft use.
 
@@ -1756,7 +1756,7 @@ Accept wildcard characters: False
 
 ### -ExtensionCustomAttribute1
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the ExtensionCustomAttribute1 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas.
 
@@ -1780,7 +1780,7 @@ Accept wildcard characters: False
 
 ### -ExtensionCustomAttribute2
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the ExtensionCustomAttribute2 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas.
 
@@ -1804,7 +1804,7 @@ Accept wildcard characters: False
 
 ### -ExtensionCustomAttribute3
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the ExtensionCustomAttribute3 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas.
 
@@ -1828,7 +1828,7 @@ Accept wildcard characters: False
 
 ### -ExtensionCustomAttribute4
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the ExtensionCustomAttribute4 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas.
 
@@ -1852,7 +1852,7 @@ Accept wildcard characters: False
 
 ### -ExtensionCustomAttribute5
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a value for the ExtensionCustomAttribute5 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas.
 
@@ -1876,7 +1876,7 @@ Accept wildcard characters: False
 
 ### -ExternalEmailAddress
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ExternalEmailAddress parameter specifies the target email address of the mail contact or mail user. By default, this value is used as the primary email address of the mail contact or mail user.
 
@@ -1918,7 +1918,7 @@ Accept wildcard characters: False
 
 ### -ForceUpgrade
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ForceUpgrade switch suppresses the confirmation message that appears if the object was created in a previous version of Exchange. You don't need to specify a value with this switch.
 
@@ -1936,7 +1936,7 @@ Accept wildcard characters: False
 
 ### -GrantSendOnBehalfTo
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The GrantSendOnBehalfTo parameter specifies who can send on behalf of this mail user. Although messages sent on behalf of the mail user clearly show the sender in the From field (`<Sender> on behalf of <Mail user>`, replies to these messages are delivered to the mail user, not the sender.
 
@@ -1973,7 +1973,7 @@ Accept wildcard characters: False
 
 ### -HiddenFromAddressListsEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The HiddenFromAddressListsEnabled parameter specifies whether this recipient is visible in address lists. Valid values are:
 
@@ -2014,7 +2014,7 @@ Accept wildcard characters: False
 
 ### -IgnoreDefaultScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -2039,7 +2039,7 @@ Accept wildcard characters: False
 
 ### -ImmutableId
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ImmutableId parameter is used by GAL synchronization (GALSync) and specifies a unique and immutable identifier in the form of an SMTP address for an Exchange mailbox used for federated delegation when requesting Security Assertion Markup Language (SAML) tokens. If federation is configured for this mailbox and you don't set this parameter when you create the mailbox, Exchange creates the value for the immutable ID based upon the mailbox's ExchangeGUID and the federated account namespace, for example, 7a78e7c8-620e-4d85-99d3-c90d90f29699@mail.contoso.com.
 
@@ -2099,7 +2099,7 @@ Accept wildcard characters: False
 
 ### -MacAttachmentFormat
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The MacAttachmentFormat parameter specifies the Apple Macintosh operating system attachment format to use for messages sent to the mail contact or mail user. Valid values are:
 
@@ -2147,7 +2147,7 @@ Accept wildcard characters: False
 
 ### -MailTip
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The MailTip parameter specifies the custom MailTip text for this recipient. The MailTip is shown to senders when they start drafting an email message to this recipient. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -2170,7 +2170,7 @@ Accept wildcard characters: False
 
 ### -MailTipTranslations
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The MailTipTranslations parameter specifies additional languages for the custom MailTip text that's defined by the MailTip parameter. HTML tags are automatically added to the MailTip translation, additional HTML tags aren't supported, and the length of the MailTip translation can't exceed 175 displayed characters.
 
@@ -2196,7 +2196,7 @@ Accept wildcard characters: False
 
 ### -MaxReceiveSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MaxReceiveSize parameter specifies the maximum size of a message that can be sent to the mail user. Messages larger than the maximum size are rejected.
 
@@ -2227,7 +2227,7 @@ Accept wildcard characters: False
 
 ### -MaxSendSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MaxSendSize parameter specifies the maximum size of a message that can be sent by the mail user.
 
@@ -2258,7 +2258,7 @@ Accept wildcard characters: False
 
 ### -MessageBodyFormat
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The MessageBodyFormat parameter specifies the message body format for messages sent to the mail contact or mail user. Valid values are:
 
@@ -2285,7 +2285,7 @@ Accept wildcard characters: False
 
 ### -MessageFormat
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The MessageFormat parameter specifies the message format for messages sent to the mail contact or mail user. Valid values are:
 
@@ -2333,7 +2333,7 @@ Accept wildcard characters: False
 
 ### -ModeratedBy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ModeratedBy parameter specifies one or more moderators for this recipient. A moderator approves messages sent to the recipient before the messages are delivered. A moderator must be a mailbox, mail user, or mail contact in your organization. You can use any value that uniquely identifies the moderator. For example:
 
@@ -2364,7 +2364,7 @@ Accept wildcard characters: False
 
 ### -ModerationEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ModerationEnabled parameter specifies whether moderation is enabled for this recipient. Valid value are:
 
@@ -2387,7 +2387,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Name parameter specifies the unique name of the mail user. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -2431,7 +2431,7 @@ Accept wildcard characters: False
 
 ### -PrimarySmtpAddress
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter is functional only in on-premises Exchange.
 
@@ -2477,7 +2477,7 @@ Accept wildcard characters: False
 
 ### -RecipientLimits
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is functional only in on-premises Exchange.
 
@@ -2501,7 +2501,7 @@ Accept wildcard characters: False
 
 ### -RecoverableItemsQuota
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -2535,7 +2535,7 @@ Accept wildcard characters: False
 
 ### -RecoverableItemsWarningQuota
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -2569,7 +2569,7 @@ Accept wildcard characters: False
 
 ### -RejectMessagesFrom
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The RejectMessagesFrom parameter specifies who isn't allowed to send messages to this recipient. Messages from these senders are rejected.
 
@@ -2604,7 +2604,7 @@ Accept wildcard characters: False
 
 ### -RejectMessagesFromDLMembers
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The RejectMessagesFromDLMembers parameter specifies who isn't allowed to send messages to this recipient. Messages from these senders are rejected.
 
@@ -2639,7 +2639,7 @@ Accept wildcard characters: False
 
 ### -RejectMessagesFromSendersOrMembers
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The RejectMessagesFromSendersOrMembers parameter specifies who isn't allowed to send messages to this recipient. Messages from these senders are rejected.
 
@@ -2818,7 +2818,7 @@ Accept wildcard characters: False
 
 ### -RemovePicture
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -2840,7 +2840,7 @@ Accept wildcard characters: False
 
 ### -RemoveSpokenName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -2862,7 +2862,7 @@ Accept wildcard characters: False
 
 ### -RequireSenderAuthenticationEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The RequireSenderAuthenticationEnabled parameter specifies whether to accept messages only from authenticated (internal) senders. Valid values are:
 
@@ -2908,7 +2908,7 @@ Accept wildcard characters: False
 
 ### -SamAccountName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -2928,7 +2928,7 @@ Accept wildcard characters: False
 
 ### -SecondaryAddress
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE Online Protection
 
 This parameter is available only in on-premises Exchange.
 
@@ -2948,7 +2948,7 @@ Accept wildcard characters: False
 
 ### -SecondaryDialPlan
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -2968,7 +2968,7 @@ Accept wildcard characters: False
 
 ### -SendModerationNotifications
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The SendModerationNotifications parameter specifies when moderation notification messages are sent. Valid values are:
 
@@ -2992,7 +2992,7 @@ Accept wildcard characters: False
 
 ### -SimpleDisplayName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The SimpleDisplayName parameter is used to display an alternative description of the object when only a limited set of characters is permitted. Valid characters are:
 
@@ -3016,7 +3016,7 @@ Accept wildcard characters: False
 
 ### -SkipDualWrite
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in Exchange 2016 or later.
 
@@ -3036,7 +3036,7 @@ Accept wildcard characters: False
 
 ### -UMDtmfMap
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -3088,7 +3088,7 @@ Accept wildcard characters: False
 
 ### -UseMapiRichTextFormat
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The UseMapiRichTextFormat parameter specifies what to do with messages that are sent to the mail user or mail contact in MAPI rich text format, also known as Outlook Rich Text or Transport Neutral Encapsulation Format (TNEF). Valid values are:
 
@@ -3112,7 +3112,7 @@ Accept wildcard characters: False
 
 ### -UsePreferMessageFormat
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The UsePreferMessageFormat specifies whether the message format settings configured for the mail user or mail contact override the global settings configured for the remote domain or configured by the message sender. Valid value are:
 
@@ -3133,7 +3133,7 @@ Accept wildcard characters: False
 
 ### -UserCertificate
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The UserCertificate parameter specifies the digital certificate used to sign a user's email messages.
 
@@ -3151,7 +3151,7 @@ Accept wildcard characters: False
 
 ### -UserPrincipalName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -3171,7 +3171,7 @@ Accept wildcard characters: False
 
 ### -UserSMimeCertificate
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The UserSMimeCertificate parameter specifies the S/MIME certificate that's used to sign a user's email messages.
 
@@ -3189,7 +3189,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
@@ -3207,7 +3207,7 @@ Accept wildcard characters: False
 
 ### -WindowsEmailAddress
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WindowsEmailAddress parameter specifies the Windows email address for this recipient. This is a common Active Directory attribute that's present in all environments, including environments without Exchange. Using the WindowsEmailAddress parameter on a recipient has one of the following results:
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-Mailbox.md b/exchange/exchange-ps/ExchangePowerShell/Set-Mailbox.md
index 0af9d1bc47..0ecd97ae8d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-Mailbox.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-Mailbox.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -1192,7 +1192,7 @@ In Exchange Online, this example removes the delay hold that's applied to Asraf'
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the mailbox that you want to modify. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -1221,7 +1221,7 @@ Accept wildcard characters: False
 
 ### -AcceptMessagesOnlyFrom
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AcceptMessagesOnlyFrom parameter specifies who is allowed to send messages to this recipient. Messages from other senders are rejected.
 
@@ -1256,7 +1256,7 @@ Accept wildcard characters: False
 
 ### -AcceptMessagesOnlyFromDLMembers
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AcceptMessagesOnlyFromDLMembers parameter specifies who is allowed to send messages to this recipient. Messages from other senders are rejected.
 
@@ -1291,7 +1291,7 @@ Accept wildcard characters: False
 
 ### -AcceptMessagesOnlyFromSendersOrMembers
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AcceptMessagesOnlyFromSendersOrMembers parameter specifies who is allowed to send messages to this recipient. Messages from other senders are rejected.
 
@@ -1328,7 +1328,7 @@ Accept wildcard characters: False
 
 ### -AccountDisabled
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter is functional only in the cloud-based service.
 
@@ -1351,7 +1351,7 @@ Accept wildcard characters: False
 
 ### -AddressBookPolicy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AddressBookPolicy parameter specifies the address book policy that's applied to the mailbox. You can use any value that uniquely identifies the address book policy. For example:
 
@@ -1375,7 +1375,7 @@ Accept wildcard characters: False
 
 ### -Alias
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Alias parameter specifies the Exchange alias (also known as the mail nickname) for the recipient. This value identifies the recipient as a mail-enabled object, and shouldn't be confused with multiple email addresses for the same recipient (also known as proxy addresses). A recipient can have only one Alias value. The maximum length is 64 characters.
 
@@ -1411,7 +1411,7 @@ Accept wildcard characters: False
 
 ### -AntispamBypassEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1434,7 +1434,7 @@ Accept wildcard characters: False
 
 ### -ApplyMandatoryProperties
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ApplyMandatoryProperties switch specifies whether to update the msExchVersion attribute of the mailbox. You don't need to specify a value with this switch.
 
@@ -1454,7 +1454,7 @@ Accept wildcard characters: False
 
 ### -Arbitration
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1478,7 +1478,7 @@ Accept wildcard characters: False
 
 ### -ArbitrationMailbox
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1509,7 +1509,7 @@ Accept wildcard characters: False
 
 ### -ArchiveDatabase
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1533,7 +1533,7 @@ Accept wildcard characters: False
 
 ### -ArchiveDomain
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1555,7 +1555,7 @@ Accept wildcard characters: False
 
 ### -ArchiveName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ArchiveName parameter specifies the name of the archive mailbox. This is the name displayed to users in Outlook on the web (formerly known as Outlook Web App). If the value contains spaces, enclose the value in quotation marks (").
 
@@ -1583,7 +1583,7 @@ Accept wildcard characters: False
 
 ### -ArchiveQuota
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1615,7 +1615,7 @@ Accept wildcard characters: False
 
 ### -ArchiveStatus
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This cmdlet is available only in on-premises Exchange.
 
@@ -1635,7 +1635,7 @@ Accept wildcard characters: False
 
 ### -ArchiveWarningQuota
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1667,7 +1667,7 @@ Accept wildcard characters: False
 
 ### -AttributesToClear
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1687,7 +1687,7 @@ Accept wildcard characters: False
 
 ### -AuditAdmin
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AuditAdmin parameter specifies the mailbox operations to log for administrators as part of mailbox audit logging. Valid values are:
 
@@ -1732,7 +1732,7 @@ Accept wildcard characters: False
 
 ### -AuditDelegate
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AuditDelegate parameter specifies the mailbox operations to log for delegate users as part of mailbox audit logging. Valid values are:
 
@@ -1774,7 +1774,7 @@ Accept wildcard characters: False
 
 ### -AuditEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AuditEnabled parameter specifies whether to enable or disable mailbox audit logging for the mailbox. If auditing is enabled, actions specified in the AuditAdmin, AuditDelegate, and AuditOwner parameters are logged. Valid values are:
 
@@ -1797,7 +1797,7 @@ Accept wildcard characters: False
 
 ### -AuditLog
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1821,7 +1821,7 @@ Accept wildcard characters: False
 
 ### -AuditLogAgeLimit
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AuditLogAgeLimit parameter specifies the maximum age of audit log entries for the mailbox. Log entries older than the specified value are removed. The default value is 90 days.
 
@@ -1843,7 +1843,7 @@ Accept wildcard characters: False
 
 ### -AuditOwner
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AuditOwner parameter specifies the mailbox operations to log for mailbox owners as part of mailbox audit logging. Valid values include:
 
@@ -1886,7 +1886,7 @@ Accept wildcard characters: False
 
 ### -AuxAuditLog
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1910,7 +1910,7 @@ Accept wildcard characters: False
 
 ### -BypassModerationFromSendersOrMembers
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The BypassModerationFromSendersOrMembers parameter specifies who is allowed to send messages to this moderated recipient without approval from a moderator. Valid values for this parameter are individual senders and groups in your organization. Specifying a group means all members of the group are allowed to send messages to this recipient without approval from a moderator.
 
@@ -1943,7 +1943,7 @@ Accept wildcard characters: False
 
 ### -CalendarLoggingQuota
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1979,7 +1979,7 @@ Accept wildcard characters: False
 
 ### -CalendarRepairDisabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The CalendarRepairDisabled parameter specifies whether to prevent calendar items in the mailbox from being repaired by the Calendar Repair Assistant. Valid values are:
 
@@ -2000,7 +2000,7 @@ Accept wildcard characters: False
 
 ### -CalendarVersionStoreDisabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The CalendarVersionStoreDisabled parameter specifies whether to prevent calendar changes in the mailbox from being logged. Valid values are:
 
@@ -2043,7 +2043,7 @@ Accept wildcard characters: False
 
 ### -ClientExtensions
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -2065,7 +2065,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -2086,7 +2086,7 @@ Accept wildcard characters: False
 
 ### -CreateDTMFMap
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -2109,7 +2109,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute1
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter specifies a value for the CustomAttribute1 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -2127,7 +2127,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute10
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter specifies a value for the CustomAttribute10 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -2145,7 +2145,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute11
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter specifies a value for the CustomAttribute11 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -2163,7 +2163,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute12
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter specifies a value for the CustomAttribute12 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -2181,7 +2181,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute13
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter specifies a value for the CustomAttribute13 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -2199,7 +2199,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute14
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter specifies a value for the CustomAttribute14 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -2217,7 +2217,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute15
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter specifies a value for the CustomAttribute15 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -2235,7 +2235,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute2
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter specifies a value for the CustomAttribute2 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -2253,7 +2253,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute3
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter specifies a value for the CustomAttribute3 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -2271,7 +2271,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute4
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter specifies a value for the CustomAttribute4 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -2289,7 +2289,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute5
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter specifies a value for the CustomAttribute5 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -2307,7 +2307,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute6
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter specifies a value for the CustomAttribute6 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -2325,7 +2325,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute7
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter specifies a value for the CustomAttribute7 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -2343,7 +2343,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute8
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter specifies a value for the CustomAttribute8 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -2361,7 +2361,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute9
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter specifies a value for the CustomAttribute9 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -2379,7 +2379,7 @@ Accept wildcard characters: False
 
 ### -Database
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -2457,7 +2457,7 @@ Accept wildcard characters: False
 
 ### -DefaultPublicFolderMailbox
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DefaultPublicFolderMailbox parameter assigns a specific public folder mailbox to the user. You can use any value that uniquely identifies the public folder mailbox. For example:
 
@@ -2484,7 +2484,7 @@ Accept wildcard characters: False
 
 ### -DeliverToMailboxAndForward
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DeliverToMailboxAndForward parameter specifies the message delivery behavior when a forwarding address is specified by the ForwardingAddress or ForwardingSmtpAddress parameters. Valid values are:
 
@@ -2507,7 +2507,7 @@ Accept wildcard characters: False
 
 ### -DisableThrottling
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -2530,7 +2530,7 @@ Accept wildcard characters: False
 
 ### -DisplayName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DisplayName parameter specifies the display name of the mailbox. The display name is visible in the Exchange admin center, in address lists, and in Outlook. The maximum length is 256 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -2548,7 +2548,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -2568,7 +2568,7 @@ Accept wildcard characters: False
 
 ### -DowngradeHighPriorityMessagesEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -2591,7 +2591,7 @@ Accept wildcard characters: False
 
 ### -DumpsterMessagesPerFolderCountReceiveQuota
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -2613,7 +2613,7 @@ Accept wildcard characters: False
 
 ### -DumpsterMessagesPerFolderCountWarningQuota
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -2678,7 +2678,7 @@ Accept wildcard characters: False
 
 ### -EmailAddresses
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The EmailAddresses parameter specifies all email addresses (proxy addresses) for the recipient, including the primary SMTP address. In on-premises Exchange organizations, the primary SMTP address and other proxy addresses are typically set by email address policies. However, you can use this parameter to configure other proxy addresses for the recipient. For more information, see [Email address policies in Exchange Server](https://learn.microsoft.com/Exchange/email-addresses-and-address-books/email-address-policies/email-address-policies).
 
@@ -2717,7 +2717,7 @@ Accept wildcard characters: False
 
 ### -EmailAddressPolicyEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -2740,7 +2740,7 @@ Accept wildcard characters: False
 
 ### -EnableRoomMailboxAccount
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is functional only in on-premises Exchange.
 
@@ -2767,7 +2767,7 @@ Accept wildcard characters: False
 
 ### -EndDateForRetentionHold
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The EndDateForRetentionHold parameter specifies the end date for retention hold for messaging records management (MRM). To use this parameter, you need to set the RetentionHoldEnabled parameter to the value $true.
 
@@ -2855,7 +2855,7 @@ Accept wildcard characters: False
 
 ### -ExtendedPropertiesCountQuota
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -2875,7 +2875,7 @@ Accept wildcard characters: False
 
 ### -ExtensionCustomAttribute1
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter specifies a value for the ExtensionCustomAttribute1 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas.
 
@@ -2899,7 +2899,7 @@ Accept wildcard characters: False
 
 ### -ExtensionCustomAttribute2
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter specifies a value for the ExtensionCustomAttribute2 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas.
 
@@ -2923,7 +2923,7 @@ Accept wildcard characters: False
 
 ### -ExtensionCustomAttribute3
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter specifies a value for the ExtensionCustomAttribute3 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas.
 
@@ -2947,7 +2947,7 @@ Accept wildcard characters: False
 
 ### -ExtensionCustomAttribute4
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter specifies a value for the ExtensionCustomAttribute4 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas.
 
@@ -2971,7 +2971,7 @@ Accept wildcard characters: False
 
 ### -ExtensionCustomAttribute5
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter specifies a value for the ExtensionCustomAttribute5 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas.
 
@@ -2995,7 +2995,7 @@ Accept wildcard characters: False
 
 ### -ExternalOofOptions
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ExternalOofOptions parameter specifies the automatic replies or Out of Office (also known OOF) message options that are available for the mailbox. Valid values are:
 
@@ -3016,7 +3016,7 @@ Accept wildcard characters: False
 
 ### -FolderHierarchyChildrenCountReceiveQuota
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -3038,7 +3038,7 @@ Accept wildcard characters: False
 
 ### -FolderHierarchyChildrenCountWarningQuota
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -3060,7 +3060,7 @@ Accept wildcard characters: False
 
 ### -FolderHierarchyDepthReceiveQuota
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -3082,7 +3082,7 @@ Accept wildcard characters: False
 
 ### -FolderHierarchyDepthWarningQuota
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -3104,7 +3104,7 @@ Accept wildcard characters: False
 
 ### -FoldersCountReceiveQuota
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -3126,7 +3126,7 @@ Accept wildcard characters: False
 
 ### -FoldersCountWarningQuota
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -3148,7 +3148,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -3168,7 +3168,7 @@ Accept wildcard characters: False
 
 ### -ForwardingAddress
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ForwardingAddress parameter specifies a forwarding address in your organization for messages that are sent to this mailbox. You can use any value that uniquely identifies the internal recipient. For example:
 
@@ -3202,7 +3202,7 @@ Accept wildcard characters: False
 
 ### -ForwardingSmtpAddress
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ForwardingSmtpAddress parameter specifies a forwarding SMTP address for messages that are sent to this mailbox. Typically, you use this parameter to specify external email addresses that aren't validated.
 
@@ -3229,7 +3229,7 @@ Accept wildcard characters: False
 
 ### -GMGen
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -3251,7 +3251,7 @@ Accept wildcard characters: False
 
 ### -GrantSendOnBehalfTo
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The GrantSendOnBehalfTo parameter specifies who can send on behalf of this mailbox. Although messages send on behalf of the mailbox clearly show the sender in the From field (`<Sender> on behalf of <Mailbox>`), replies to these messages are delivered to the mailbox, not the sender.
 
@@ -3308,7 +3308,7 @@ Accept wildcard characters: False
 
 ### -HiddenFromAddressListsEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The HiddenFromAddressListsEnabled parameter specifies whether this recipient is visible in address lists. Valid values are:
 
@@ -3329,7 +3329,7 @@ Accept wildcard characters: False
 
 ### -IgnoreDefaultScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -3354,7 +3354,7 @@ Accept wildcard characters: False
 
 ### -ImListMigrationCompleted
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -3383,7 +3383,7 @@ Accept wildcard characters: False
 
 ### -ImmutableId
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ImmutableId parameter is used by GAL synchronization (GALSync) and specifies a unique and immutable identifier in the form of an SMTP address for an Exchange mailbox used for federated delegation when requesting Security Assertion Markup Language (SAML) tokens. If federation is configured for this mailbox and you don't set this parameter when you create the mailbox, Exchange creates the value for the immutable ID based upon the mailbox's ExchangeGUID and the federated account namespace, for example, 7a78e7c8-620e-4d85-99d3-c90d90f29699@mail.contoso.com.
 
@@ -3431,7 +3431,7 @@ Accept wildcard characters: False
 
 ### -IsExcludedFromServingHierarchy
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IsExcludedFromServingHierarchy parameter prevents users from accessing the public folder hierarchy on this public folder mailbox. For load-balancing purposes, users are equally distributed across public folder mailboxes by default. When this parameter is set on a public folder mailbox, that mailbox isn't included in this automatic load-balancing and can't be accessed by users to retrieve the public folder hierarchy. However, if an administrator has set the DefaultPublicFolderMailbox property on a user mailbox to a specific public folder mailbox, the user can still access the specified public folder mailbox even if the IsExcludedFromServingHierarchy parameter is set for that public folder mailbox.
 
@@ -3451,7 +3451,7 @@ Accept wildcard characters: False
 
 ### -IsHierarchyReady
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -3471,7 +3471,7 @@ Accept wildcard characters: False
 
 ### -IsHierarchySyncEnabled
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -3491,7 +3491,7 @@ Accept wildcard characters: False
 
 ### -IssueWarningQuota
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IssueWarningQuota parameter specifies the warning threshold for the size of the mailbox. If the mailbox reaches or exceeds this size, the user receives a descriptive warning message.
 
@@ -3545,7 +3545,7 @@ Accept wildcard characters: False
 
 ### -Languages
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Languages parameter specifies the language preferences for this mailbox, in order of preference. Several Exchange components display information to a mailbox user in the preferred language, if that language is supported. Some of those components include quota messages, non-delivery reports (NDRs), the Outlook on the web user interface, and Unified Messaging (UM) voice prompts.
 
@@ -3569,7 +3569,7 @@ Accept wildcard characters: False
 
 ### -LinkedCredential
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -3591,7 +3591,7 @@ Accept wildcard characters: False
 
 ### -LinkedDomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -3611,7 +3611,7 @@ Accept wildcard characters: False
 
 ### -LinkedMasterAccount
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -3636,7 +3636,7 @@ Accept wildcard characters: False
 
 ### -LitigationHoldDate
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The LitigationHoldDate parameter specifies the date that the mailbox is placed on litigation hold. The parameter is populated automatically when you place a mailbox on litigation hold. The date you specify can be used for informational or reporting purposes.
 
@@ -3656,7 +3656,7 @@ Accept wildcard characters: False
 
 ### -LitigationHoldDuration
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The LitigationHoldDuration parameter specifies how long mailbox items are held if the mailbox is placed on litigation hold. The duration is calculated from the date a mailbox item is received or created.
 
@@ -3676,7 +3676,7 @@ Accept wildcard characters: False
 
 ### -LitigationHoldEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The LitigationHoldEnabled parameter specifies whether to place the mailbox on litigation hold. Valid values are:
 
@@ -3701,7 +3701,7 @@ Accept wildcard characters: False
 
 ### -LitigationHoldOwner
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The LitigationHoldOwner parameter specifies the user who placed the mailbox on litigation hold. If you don't use this parameter when you place the mailbox on litigation hold, the value is populated automatically. If you use this parameter when you place the mailbox on litigation hold, you can specify a text value. If the value contains spaces, include the value in quotation marks ("). You can use this value for informational and reporting purposes.
 
@@ -3719,7 +3719,7 @@ Accept wildcard characters: False
 
 ### -MailboxMessagesPerFolderCountReceiveQuota
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is an available only in on-premises Exchange.
 
@@ -3743,7 +3743,7 @@ Accept wildcard characters: False
 
 ### -MailboxMessagesPerFolderCountWarningQuota
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is an available only in on-premises Exchange.
 
@@ -3791,7 +3791,7 @@ Accept wildcard characters: False
 
 ### -MailTip
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MailTip parameter specifies the custom MailTip text for this recipient. The MailTip is shown to senders when they start drafting an email message to this recipient. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -3814,7 +3814,7 @@ Accept wildcard characters: False
 
 ### -MailTipTranslations
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MailTipTranslations parameter specifies additional languages for the custom MailTip text that's defined by the MailTip parameter. HTML tags are automatically added to the MailTip translation, additional HTML tags aren't supported, and the length of the MailTip translation can't exceed 175 displayed characters.
 
@@ -3884,7 +3884,7 @@ Accept wildcard characters: False
 
 ### -Management
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -3906,7 +3906,7 @@ Accept wildcard characters: False
 
 ### -MaxBlockedSenders
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -3926,7 +3926,7 @@ Accept wildcard characters: False
 
 ### -MaxReceiveSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MaxReceiveSize parameter specifies the maximum size of a message that can be sent to the mailbox. Messages larger than the maximum size are rejected.
 
@@ -3963,7 +3963,7 @@ Accept wildcard characters: False
 
 ### -MaxSafeSenders
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -3983,7 +3983,7 @@ Accept wildcard characters: False
 
 ### -MaxSendSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MaxSendSize parameter specifies the maximum size of a message that can be sent by the mailbox.
 
@@ -4020,7 +4020,7 @@ Accept wildcard characters: False
 
 ### -MessageCopyForSendOnBehalfEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 **Note**: Previously, this parameter was available only for shared mailboxes. In Exchange Online or Exchange 2016 CU6 or later, this parameter is also available for user mailboxes. This parameter is not available for linked user mailboxes.
 
@@ -4045,7 +4045,7 @@ Accept wildcard characters: False
 
 ### -MessageCopyForSentAsEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 **Note**: Previously, this parameter was available only for shared mailboxes. In Exchange Online or Exchange 2016 CU6 or later, this parameter is also available for user mailboxes. This parameter is not available for linked user mailboxes.
 
@@ -4095,7 +4095,7 @@ Accept wildcard characters: False
 
 ### -MessageTracking
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -4117,7 +4117,7 @@ Accept wildcard characters: False
 
 ### -MessageTrackingReadStatusEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MessageTrackingReadStatusEnabled parameter specifies whether to include detailed information in delivery reports for messages sent to the mailbox. Valid values are:
 
@@ -4158,7 +4158,7 @@ Accept wildcard characters: False
 
 ### -Migration
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -4178,7 +4178,7 @@ Accept wildcard characters: False
 
 ### -ModeratedBy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ModeratedBy parameter specifies one or more moderators for this recipient. A moderator approves messages sent to the recipient before the messages are delivered. A moderator must be a mailbox, mail user, or mail contact in your organization. You can use any value that uniquely identifies the moderator. For example:
 
@@ -4209,7 +4209,7 @@ Accept wildcard characters: False
 
 ### -ModerationEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ModerationEnabled parameter specifies whether moderation is enabled for this recipient. Valid value are:
 
@@ -4232,7 +4232,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Name parameter specifies the unique name of the mailbox. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -4252,7 +4252,7 @@ Accept wildcard characters: False
 
 ### -NewPassword
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -4298,7 +4298,7 @@ Accept wildcard characters: False
 
 ### -OABGen
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -4320,7 +4320,7 @@ Accept wildcard characters: False
 
 ### -Office
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Office parameter specifies the user's physical office name or number.
 
@@ -4338,7 +4338,7 @@ Accept wildcard characters: False
 
 ### -OfflineAddressBook
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -4364,7 +4364,7 @@ Accept wildcard characters: False
 
 ### -OldPassword
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -4390,7 +4390,7 @@ Accept wildcard characters: False
 
 ### -OMEncryption
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -4410,7 +4410,7 @@ Accept wildcard characters: False
 
 ### -OMEncryptionStore
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -4430,7 +4430,7 @@ Accept wildcard characters: False
 
 ### -Password
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Password parameter resets the password of the user account that's associated with the mailbox to the value you specify. To use this parameter on a mailbox other than your own, consider the following options:
 
@@ -4457,7 +4457,7 @@ Accept wildcard characters: False
 
 ### -PrimarySmtpAddress
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -4481,7 +4481,7 @@ Accept wildcard characters: False
 
 ### -ProhibitSendQuota
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ProhibitSendQuota parameter specifies a size limit for the mailbox. If the mailbox reaches or exceeds this size, the mailbox can't send new messages, and the user receives a descriptive warning message.
 
@@ -4515,7 +4515,7 @@ Accept wildcard characters: False
 
 ### -ProhibitSendReceiveQuota
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ProhibitSendReceiveQuota parameter specifies a size limit for the mailbox. If the mailbox reaches or exceeds this size, the mailbox can't send or receive new messages. Messages sent to the mailbox are returned to the sender with a descriptive error message. This value effectively determines the maximum size of the mailbox.
 
@@ -4569,7 +4569,7 @@ Accept wildcard characters: False
 
 ### -PstProvider
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -4589,7 +4589,7 @@ Accept wildcard characters: False
 
 ### -PublicFolder
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The PublicFolder switch is required to modify public folder mailboxes. You don't need to specify a value with this switch.
 
@@ -4609,7 +4609,7 @@ Accept wildcard characters: False
 
 ### -QueryBaseDN
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -4653,7 +4653,7 @@ Accept wildcard characters: False
 
 ### -RecipientLimits
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RecipientLimits parameter specifies the maximum number of recipients allowed in messages sent by the mailbox.
 
@@ -4675,7 +4675,7 @@ Accept wildcard characters: False
 
 ### -RecoverableItemsQuota
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -4711,7 +4711,7 @@ Accept wildcard characters: False
 
 ### -RecoverableItemsWarningQuota
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -4747,7 +4747,7 @@ Accept wildcard characters: False
 
 ### -RejectMessagesFrom
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RejectMessagesFrom parameter specifies who isn't allowed to send messages to this recipient. Messages from these senders are rejected.
 
@@ -4782,7 +4782,7 @@ Accept wildcard characters: False
 
 ### -RejectMessagesFromDLMembers
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RejectMessagesFromDLMembers parameter specifies who isn't allowed to send messages to this recipient. Messages from these senders are rejected.
 
@@ -4817,7 +4817,7 @@ Accept wildcard characters: False
 
 ### -RejectMessagesFromSendersOrMembers
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RejectMessagesFromSendersOrMembers parameter specifies who isn't allowed to send messages to this recipient. Messages from these senders are rejected.
 
@@ -4854,7 +4854,7 @@ Accept wildcard characters: False
 
 ### -RemoteRecipientType
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -4965,7 +4965,7 @@ Accept wildcard characters: False
 
 ### -RemoveManagedFolderAndPolicy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -5009,7 +5009,7 @@ Accept wildcard characters: False
 
 ### -RemovePicture
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -5031,7 +5031,7 @@ Accept wildcard characters: False
 
 ### -RemoveSpokenName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -5053,7 +5053,7 @@ Accept wildcard characters: False
 
 ### -RequireSenderAuthenticationEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RequireSenderAuthenticationEnabled parameter specifies whether to accept messages only from authenticated (internal) senders. Valid values are:
 
@@ -5074,7 +5074,7 @@ Accept wildcard characters: False
 
 ### -ResetPasswordOnNextLogon
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -5099,7 +5099,7 @@ Accept wildcard characters: False
 
 ### -ResourceCapacity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ResourceCapacity parameter specifies the capacity of the resource mailbox. For example, you can use this parameter to identify the number of seats in a conference room (room mailbox) or in a vehicle (equipment mailbox). A valid value is an integer.
 
@@ -5117,7 +5117,7 @@ Accept wildcard characters: False
 
 ### -ResourceCustom
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ResourceCustom parameter specifies one or more custom resource properties to add to the resource mailbox. You can use this parameter only on resource mailboxes.
 
@@ -5143,7 +5143,7 @@ Accept wildcard characters: False
 
 ### -RetainDeletedItemsFor
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RetainDeletedItemsFor parameter specifies the length of time to keep soft-deleted items for the mailbox. Soft-deleted items are items that have been deleted by using any of these methods:
 
@@ -5177,7 +5177,7 @@ Accept wildcard characters: False
 
 ### -RetainDeletedItemsUntilBackup
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -5204,7 +5204,7 @@ Accept wildcard characters: False
 
 ### -RetentionComment
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The RetentionComment parameter specifies a comment that's displayed in Outlook regarding the user's retention hold status.
 
@@ -5228,7 +5228,7 @@ Accept wildcard characters: False
 
 ### -RetentionHoldEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RetentionHoldEnabled parameter specifies whether the mailbox is placed on retention hold. Placing the mailbox on retention hold temporarily suspends the processing of retention policies or managed folder mailbox policies for the mailbox (for example, when the user is on vacation). Valid values are:
 
@@ -5251,7 +5251,7 @@ Accept wildcard characters: False
 
 ### -RetentionPolicy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RetentionPolicy parameter specifies the retention policy that you want applied to this mailbox. You can use any value that uniquely identifies the policy. For example:
 
@@ -5277,7 +5277,7 @@ Accept wildcard characters: False
 
 ### -RetentionUrl
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The RetentionUrl parameter specifies the URL or an external web page with additional details about the organization's messaging retention policies.
 
@@ -5297,7 +5297,7 @@ Accept wildcard characters: False
 
 ### -RoleAssignmentPolicy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RoleAssignmentPolicy parameter specifies the role assignment policy that's assigned to the mailbox. You can use any value that uniquely identifies the role assignment policy. For example:
 
@@ -5323,7 +5323,7 @@ Accept wildcard characters: False
 
 ### -RoomMailboxPassword
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is functional only in on-premises Exchange.
 
@@ -5359,7 +5359,7 @@ Accept wildcard characters: False
 
 ### -RulesQuota
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RulesQuota parameter specifies the limit for the size of Inbox rules for the mailbox. When you enter a value, qualify the value with one of the following:
 
@@ -5390,7 +5390,7 @@ Accept wildcard characters: False
 
 ### -SamAccountName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -5430,7 +5430,7 @@ Accept wildcard characters: False
 
 ### -SCLDeleteEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -5454,7 +5454,7 @@ Accept wildcard characters: False
 
 ### -SCLDeleteThreshold
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -5476,7 +5476,7 @@ Accept wildcard characters: False
 
 ### -SCLJunkEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -5500,7 +5500,7 @@ Accept wildcard characters: False
 
 ### -SCLJunkThreshold
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -5522,7 +5522,7 @@ Accept wildcard characters: False
 
 ### -SCLQuarantineEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -5548,7 +5548,7 @@ Accept wildcard characters: False
 
 ### -SCLQuarantineThreshold
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -5570,7 +5570,7 @@ Accept wildcard characters: False
 
 ### -SCLRejectEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -5594,7 +5594,7 @@ Accept wildcard characters: False
 
 ### -SCLRejectThreshold
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -5616,7 +5616,7 @@ Accept wildcard characters: False
 
 ### -SecondaryAddress
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -5636,7 +5636,7 @@ Accept wildcard characters: False
 
 ### -SecondaryDialPlan
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -5656,7 +5656,7 @@ Accept wildcard characters: False
 
 ### -SendModerationNotifications
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SendModerationNotifications parameter specifies when moderation notification messages are sent. Valid values are:
 
@@ -5680,7 +5680,7 @@ Accept wildcard characters: False
 
 ### -SharingPolicy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SharingPolicy parameter specifies the sharing policy that's assigned to the mailbox. You can use any value that uniquely identifies the sharing policy. For example:
 
@@ -5704,7 +5704,7 @@ Accept wildcard characters: False
 
 ### -SimpleDisplayName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SimpleDisplayName parameter is used to display an alternative description of the object when only a limited set of characters is permitted. Valid characters are:
 
@@ -5728,7 +5728,7 @@ Accept wildcard characters: False
 
 ### -SingleItemRecoveryEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SingleItemRecoveryEnabled parameter specifies whether to prevent the Recoverable Items folder from being purged. Valid values are:
 
@@ -5749,7 +5749,7 @@ Accept wildcard characters: False
 
 ### -SkipDualWrite
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange
 
@@ -5769,7 +5769,7 @@ Accept wildcard characters: False
 
 ### -StartDateForRetentionHold
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The StartDateForRetentionHold parameter specifies the start date for the retention hold that's placed on the mailbox.
 
@@ -5791,7 +5791,7 @@ Accept wildcard characters: False
 
 ### -StsRefreshTokensValidFrom
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter is reserved for internal Microsoft use.
 
@@ -5809,7 +5809,7 @@ Accept wildcard characters: False
 
 ### -SystemMessageSizeShutoffQuota
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -5829,7 +5829,7 @@ Accept wildcard characters: False
 
 ### -SystemMessageSizeWarningQuota
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -5849,7 +5849,7 @@ Accept wildcard characters: False
 
 ### -ThrottlingPolicy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -5875,7 +5875,7 @@ Accept wildcard characters: False
 
 ### -Type
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Type parameter specifies the mailbox type for the mailbox. Valid values are:
 
@@ -5900,7 +5900,7 @@ Accept wildcard characters: False
 
 ### -UMDataStorage
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -5922,7 +5922,7 @@ Accept wildcard characters: False
 
 ### -UMDtmfMap
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -5954,7 +5954,7 @@ Accept wildcard characters: False
 
 ### -UMGrammar
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -5996,7 +5996,7 @@ Accept wildcard characters: False
 
 ### -UseDatabaseQuotaDefaults
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The UseDatabaseQuotaDefaults parameter specifies whether applicable quotas for the mailbox are determined by the quota values on the mailbox or the corresponding quota values on the mailbox database (not all mailbox quotas are configurable on the mailbox database). Valid values are:
 
@@ -6026,7 +6026,7 @@ Accept wildcard characters: False
 
 ### -UseDatabaseRetentionDefaults
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is functional only in on-premises Exchange.
 
@@ -6059,7 +6059,7 @@ Accept wildcard characters: False
 
 ### -UserCertificate
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The UserCertificate parameter specifies the digital certificate used to sign a user's email messages.
 
@@ -6077,7 +6077,7 @@ Accept wildcard characters: False
 
 ### -UserPrincipalName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -6097,7 +6097,7 @@ Accept wildcard characters: False
 
 ### -UserSMimeCertificate
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The UserSMimeCertificate parameter specifies the S/MIME certificate that's used to sign a user's email messages.
 
@@ -6115,7 +6115,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
@@ -6133,7 +6133,7 @@ Accept wildcard characters: False
 
 ### -WindowsEmailAddress
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WindowsEmailAddress parameter specifies the Windows email address for this recipient. This is a common Active Directory attribute that's present in all environments, including environments without Exchange. Using the WindowsEmailAddress parameter on a recipient has one of the following results:
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxAuditBypassAssociation.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxAuditBypassAssociation.md
index 727665ecc5..e902549d46 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxAuditBypassAssociation.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxAuditBypassAssociation.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
 Locale: en-US
@@ -56,7 +56,7 @@ This example removes the bypass association for the Svc-MyApplication account.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies a user or computer account to be bypassed from mailbox audit logging.
 
@@ -74,7 +74,7 @@ Accept wildcard characters: False
 
 ### -AuditBypassEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AuditBypassEnabled parameter specifies whether audit bypass is enabled for the user or computer. Valid values include the following:
 
@@ -95,7 +95,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -116,7 +116,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -136,7 +136,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxAutoReplyConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxAutoReplyConfiguration.md
index 8e5570733c..eae06dedc4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxAutoReplyConfiguration.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxAutoReplyConfiguration.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -69,7 +69,7 @@ This example configures Automatic Replies for Tony's mailbox to be sent, specifi
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the mailbox that you want to modify. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -98,7 +98,7 @@ Accept wildcard characters: False
 
 ### -AutoDeclineFutureRequestsWhenOOF
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is functional only in the cloud-based service.
 
@@ -123,7 +123,7 @@ Accept wildcard characters: False
 
 ### -AutoReplyState
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AutoReplyState parameter specifies whether the mailbox is enabled for Automatic Replies. Valid values are:
 
@@ -150,7 +150,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -171,7 +171,7 @@ Accept wildcard characters: False
 
 ### -CreateOOFEvent
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is functional only in the cloud-based service.
 
@@ -194,7 +194,7 @@ Accept wildcard characters: False
 
 ### -DeclineAllEventsForScheduledOOF
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is functional only in the cloud-based service.
 
@@ -221,7 +221,7 @@ Accept wildcard characters: False
 
 ### -DeclineEventsForScheduledOOF
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is functional only in the cloud-based service.
 
@@ -249,7 +249,7 @@ Accept wildcard characters: False
 
 ### -DeclineMeetingMessage
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is functional only in the cloud-based service.
 
@@ -276,7 +276,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -296,7 +296,7 @@ Accept wildcard characters: False
 
 ### -EndTime
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The EndTime parameter specifies the end date and time that Automatic Replies are sent for the mailbox. You use this parameter only when the AutoReplyState parameter is set to Scheduled, and the value of this parameter is meaningful only when AutoReplyState is Scheduled.
 
@@ -316,7 +316,7 @@ Accept wildcard characters: False
 
 ### -EventsToDeleteIDs
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is functional only in the cloud-based service.
 
@@ -340,7 +340,7 @@ Accept wildcard characters: False
 
 ### -ExternalAudience
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ExternalAudience parameter specifies whether Automatic Replies are sent to external senders. Valid values are:
 
@@ -364,7 +364,7 @@ Accept wildcard characters: False
 
 ### -ExternalMessage
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ExternalMessage parameter specifies the Automatic Replies message that's sent to external senders or senders outside the organization. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -391,7 +391,7 @@ Accept wildcard characters: False
 
 ### -IgnoreDefaultScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange PowerShell session, and to use the entire forest as the scope. You don't need to specify a value with this switch.
 
@@ -414,7 +414,7 @@ Accept wildcard characters: False
 
 ### -InternalMessage
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The InternalMessage parameter specifies the Automatic Replies message that's sent to internal senders or senders within the organization. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -438,7 +438,7 @@ Accept wildcard characters: False
 
 ### -OOFEventSubject
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is functional only in the cloud-based service.
 
@@ -460,7 +460,7 @@ Accept wildcard characters: False
 
 ### -StartTime
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The StartTime parameter specifies the start date and time that Automatic Replies are sent for the specified mailbox. You use this parameter only when the AutoReplyState parameter is set to Scheduled, and the value of this parameter is meaningful only when AutoReplyState is Scheduled.
 
@@ -480,7 +480,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxCalendarConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxCalendarConfiguration.md
index d0f4c94bb5..3c37bb9ac5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxCalendarConfiguration.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxCalendarConfiguration.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -187,7 +187,7 @@ This example sets the working day's starting hour to 7 A.M. for the calendar of
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the mailbox that you want to modify. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -216,7 +216,7 @@ Accept wildcard characters: False
 
 ### -AgendaMailEnabled
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is reserved for internal Microsoft use.
 
@@ -356,7 +356,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -377,7 +377,7 @@ Accept wildcard characters: False
 
 ### -ConversationalSchedulingEnabled
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConversationalSchedulingEnabled parameter specifies whether to enable or disable conversational scheduling. Valid values are:
 
@@ -421,7 +421,7 @@ Accept wildcard characters: False
 
 ### -DailyAgendaMailSchedule
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is reserved for internal Microsoft use.
 
@@ -439,7 +439,7 @@ Accept wildcard characters: False
 
 ### -DefaultMeetingDuration
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is reserved for internal Microsoft use.
 
@@ -534,7 +534,7 @@ Accept wildcard characters: False
 
 ### -DefaultReminderTime
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DefaultReminderTime parameter specifies the length of time before a meeting or appointment when the reminder is first displayed.
 
@@ -620,7 +620,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -697,7 +697,7 @@ Accept wildcard characters: False
 
 ### -FirstWeekOfYear
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The FirstWeekOfYear parameter specifies the first week of the year. Valid values are:
 
@@ -912,7 +912,7 @@ Accept wildcard characters: False
 
 ### -RemindersEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RemindersEnabled parameter enables or disables reminders for calendar items. Valid values are:
 
@@ -935,7 +935,7 @@ Accept wildcard characters: False
 
 ### -ReminderSoundEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ReminderSoundEnabled parameter specifies whether a sound is played along with the reminder. Valid values are:
 
@@ -1023,7 +1023,7 @@ Accept wildcard characters: False
 
 ### -ShowWeekNumbers
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ShowWeekNumbers parameter specifies whether the week number is displayed in the Outlook on the web calendar. Valid values are:
 
@@ -1044,7 +1044,7 @@ Accept wildcard characters: False
 
 ### -SkipAgendaMailOnFreeDays
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is reserved for internal Microsoft use.
 
@@ -1062,7 +1062,7 @@ Accept wildcard characters: False
 
 ### -TimeIncrement
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The TimeIncrement parameter specifies the scale that the Outlook on the web calendar uses to show time. Valid values are:
 
@@ -1083,7 +1083,7 @@ Accept wildcard characters: False
 
 ### -UseBrightCalendarColorThemeInOwa
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The UseBrightCalendarColorThemeInOwa parameter specifies whether to use light colors or bright colors for the calendar in Outlook on the web. Valid values are:
 
@@ -1204,7 +1204,7 @@ Accept wildcard characters: False
 
 ### -WeekStartDay
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WeekStartDay parameter specifies the first day of the week. Valid values are:
 
@@ -1230,7 +1230,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
@@ -1248,7 +1248,7 @@ Accept wildcard characters: False
 
 ### -WorkDays
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WorkDays parameter specifies the work days in the calendar. Valid values are:
 
@@ -1280,7 +1280,7 @@ Accept wildcard characters: False
 
 ### -WorkingHoursEndTime
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WorkingHoursEndTime parameter specifies the time that the work day ends.
 
@@ -1302,7 +1302,7 @@ Accept wildcard characters: False
 
 ### -WorkingHoursStartTime
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WorkingHoursStartTime parameter specifies the time that the work day starts.
 
@@ -1324,7 +1324,7 @@ Accept wildcard characters: False
 
 ### -WorkingHoursTimeZone
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WorkingHoursTimeZone parameter specifies the time zone that's used by the WorkingHoursStartTime and WorkingHoursEndTime parameters.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxCalendarFolder.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxCalendarFolder.md
index 7ad33e450c..dd3821709f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxCalendarFolder.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxCalendarFolder.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
 Locale: en-US
@@ -68,7 +68,7 @@ This example enables the calendar in Kai's mailbox to be searchable on the web.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the calendar folder that you want to modify. The syntax is `MailboxID:\ParentFolder[\SubFolder]`.
 
@@ -101,7 +101,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -122,7 +122,7 @@ Accept wildcard characters: False
 
 ### -DetailLevel
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DetailLevel parameter specifies the level of calendar detail that's published and available to anonymous users. Valid values are:
 
@@ -146,7 +146,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -166,7 +166,7 @@ Accept wildcard characters: False
 
 ### -PublishDateRangeFrom
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The PublishDateRangeFrom parameter specifies the start date of calendar information to publish (past information). Valid values are:
 
@@ -194,7 +194,7 @@ Accept wildcard characters: False
 
 ### -PublishDateRangeTo
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The PublishDateRangeTo parameter specifies the end date of calendar information to publish (future information). Valid values are:
 
@@ -222,7 +222,7 @@ Accept wildcard characters: False
 
 ### -PublishEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The PublishEnabled parameter specifies whether to publish the specified calendar information. Valid values are:
 
@@ -243,7 +243,7 @@ Accept wildcard characters: False
 
 ### -ResetUrl
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ResetUrl switch replaces the existing non-public URL with a new URL for a calendar that is published without being publicly searchable. You don't need to specify a value with this switch.
 
@@ -261,7 +261,7 @@ Accept wildcard characters: False
 
 ### -SearchableUrlEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SearchableUrlEnabled parameter specifies whether the published calendar URL is discoverable on the web.
 
@@ -284,7 +284,7 @@ Accept wildcard characters: False
 
 ### -SetAsSharingSource
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SetAsSharingSource switch specifies whether to set the calendar folder as a sharing source. You don't need to specify a value with this switch.
 
@@ -336,7 +336,7 @@ Accept wildcard characters: False
 
 ### -UseHttps
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The UseHttps switch specifies whether to use HTTPS for the published URL of the calendar folder. You don't need to specify a value with this switch.
 
@@ -356,7 +356,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxDatabase.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxDatabase.md
index e700a98c53..2512649f93 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxDatabase.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxDatabase.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -87,7 +87,7 @@ For more information about RPC access through Client Access servers, see [Set-Rp
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the mailbox database that you want to modify. You can use any value that uniquely identifies the database. For example:
 
@@ -109,7 +109,7 @@ Accept wildcard characters: False
 
 ### -AllowFileRestore
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AllowFileRestore parameter specifies whether to allow a database to be restored from a backup. Valid values are:
 
@@ -130,7 +130,7 @@ Accept wildcard characters: False
 
 ### -AutoDagExcludeFromMonitoring
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AutoDagExcludedFromMonitoring parameter specifies whether to exclude the mailbox database from the ServerOneCopyMonitor, which alerts an administrator when a replicated database has only one healthy copy available. Valid values are:
 
@@ -151,7 +151,7 @@ Accept wildcard characters: False
 
 ### -AutoDatabaseMountDial
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -169,7 +169,7 @@ Accept wildcard characters: False
 
 ### -BackgroundDatabaseMaintenance
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The BackgroundDatabaseMaintenance parameter specifies whether the Extensible Storage Engine (ESE) performs database maintenance. Valid values are:
 
@@ -190,7 +190,7 @@ Accept wildcard characters: False
 
 ### -CalendarLoggingQuota
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The CalendarLoggingQuota parameter specifies the maximum size of the log in the Recoverable Items folder of the mailbox that stores changes to calendar items. When the log exceeds this size, calendar logging is disabled until messaging records management (MRM) removes older calendar logs to free up more space.
 
@@ -224,7 +224,7 @@ Accept wildcard characters: False
 
 ### -CircularLoggingEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The CircularLoggingEnabled parameter specifies whether circular logging is enabled for the database. Valid values are:
 
@@ -247,7 +247,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -268,7 +268,7 @@ Accept wildcard characters: False
 
 ### -DatabaseGroup
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -286,7 +286,7 @@ Accept wildcard characters: False
 
 ### -DataMoveReplicationConstraint
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DataMoveReplicationConstraint parameter specifies the throttling behavior for high availability mailbox moves. Valid values are:
 
@@ -315,7 +315,7 @@ Accept wildcard characters: False
 
 ### -DeletedItemRetention
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DeletedItemRetention parameter specifies the length of time to keep deleted items in the Recoverable Items\\Deletions folder in mailboxes. Items are moved to this folder when the user deletes items from the Deleted Items folder, empties the Deleted Items folder, or deletes items by using Shift+Delete.
 
@@ -341,7 +341,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -359,7 +359,7 @@ Accept wildcard characters: False
 
 ### -EventHistoryRetentionPeriod
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The EventHistoryRetentionPeriod parameter specifies the length of time to keep event data. This event data is stored in the event history table in the Exchange store. It includes information about changes to various objects in the mailbox database. You can use this parameter to prevent the event history table from becoming too large and using too much disk space.
 
@@ -381,7 +381,7 @@ Accept wildcard characters: False
 
 ### -IndexEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is functional only in Exchange 2016 or earlier.
 
@@ -404,7 +404,7 @@ Accept wildcard characters: False
 
 ### -IsExcludedFromInitialProvisioning
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -422,7 +422,7 @@ Accept wildcard characters: False
 
 ### -IsExcludedFromProvisioning
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IsExcludedFromProvisioning parameter specifies whether to exclude the database from the mailbox provisioning load balancer that distributes new mailboxes randomly and evenly across the available databases. Valid values are:
 
@@ -445,7 +445,7 @@ Accept wildcard characters: False
 
 ### -IsExcludedFromProvisioningByOperator
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IIsExcludedFromProvisioningByOperator parameter specifies whether to exclude the database from the mailbox provisioning load balancer that distributes new mailboxes randomly and evenly across the available databases.
 
@@ -473,7 +473,7 @@ Accept wildcard characters: False
 
 ### -IsExcludedFromProvisioningDueToLogicalCorruption
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IsExcludedFromProvisioningDueToLogicalCorruption parameter specifies whether to exclude the database from the mailbox provisioning load balancer that distributes new mailboxes randomly and evenly across the available databases.
 
@@ -502,7 +502,7 @@ Accept wildcard characters: False
 
 ### -IsExcludedFromProvisioningReason
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IsExcludedFromProvisioningReason parameter specifies the reason why you excluded the mailbox database from the mailbox provisioning load balancer. If the value contains spaces, enclose the value in quotation marks ("). The value must contain at least 10 characters.
 
@@ -526,7 +526,7 @@ Accept wildcard characters: False
 
 ### -IssueWarningQuota
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IssueWarningQuota parameter specifies the warning threshold for the size of the mailbox. If the mailbox reaches or exceeds this size, the user receives a descriptive warning message.
 
@@ -558,7 +558,7 @@ Accept wildcard characters: False
 
 ### -IsSuspendedFromProvisioning
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IsSuspendedFromProvisioning parameter specifies whether to exclude the database from the mailbox provisioning load balancer that distributes new mailboxes randomly and evenly across the available databases. Valid values are:
 
@@ -584,7 +584,7 @@ Accept wildcard characters: False
 
 ### -JournalRecipient
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The JournalRecipient parameter specifies the journal recipient to use for per-database journaling for all mailboxes on the database. You can use any value that uniquely identifies the recipient. For example:
 
@@ -609,7 +609,7 @@ Accept wildcard characters: False
 
 ### -MailboxRetention
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MailboxRetention parameter specifies the length of time to keep deleted mailboxes before they are permanently deleted or purged.
 
@@ -631,7 +631,7 @@ Accept wildcard characters: False
 
 ### -MaintenanceSchedule
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is functional only in Exchange Server 2010.
 
@@ -671,7 +671,7 @@ Accept wildcard characters: False
 
 ### -MetaCacheDatabaseMaxCapacityInBytes
 
-> Applicable: Exchange Server 2019
+> Applicable: Exchange Server 2019, Exchange Server SE
 
 The MetaCacheDatabaseMaxCapacityInBytes parameter specifies the size of the metacache database in bytes. To convert gigabytes to bytes, multiply the value by 1024^3. For terabytes to bytes, multiply by 1024^4.
 
@@ -691,7 +691,7 @@ Accept wildcard characters: False
 
 ### -MountAtStartup
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MountAtStartup parameter specifies whether to mount the mailbox database when the Microsoft Exchange Information Store service starts. Valid values are:
 
@@ -712,7 +712,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Name parameter specifies the unique name of the mailbox database. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -730,7 +730,7 @@ Accept wildcard characters: False
 
 ### -OfflineAddressBook
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The OfflineAddressBook parameter specifies the offline address book that's associated with the mailbox database. You can use any value that uniquely identifies the offline address book. For example:
 
@@ -754,7 +754,7 @@ Accept wildcard characters: False
 
 ### -ProhibitSendQuota
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ProhibitSendQuota parameter specifies a size limit for the mailbox. If the mailbox reaches or exceeds this size, the mailbox can't send new messages, and the user receives a descriptive warning message.
 
@@ -786,7 +786,7 @@ Accept wildcard characters: False
 
 ### -ProhibitSendReceiveQuota
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ProhibitSendReceiveQuota parameter specifies a size limit for the mailbox. If the mailbox reaches or exceeds this size, the mailbox can't send or receive new messages. Messages sent to the mailbox are returned to the sender with a descriptive error message. This value effectively determines the maximum size of the mailbox.
 
@@ -818,7 +818,7 @@ Accept wildcard characters: False
 
 ### -PublicFolderDatabase
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is functional only in Exchange Server 2010.
 
@@ -842,7 +842,7 @@ Accept wildcard characters: False
 
 ### -QuotaNotificationSchedule
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is functional only in Exchange Server 2010.
 
@@ -882,7 +882,7 @@ Accept wildcard characters: False
 
 ### -RecoverableItemsQuota
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RecoverableItemsQuota parameter specifies the maximum size for the Recoverable Items folder of the mailbox. If the Recoverable Items folder reaches or exceeds this size, it no longer accepts messages.
 
@@ -916,7 +916,7 @@ Accept wildcard characters: False
 
 ### -RecoverableItemsWarningQuota
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RecoverableItemsWarningQuota parameter specifies the warning threshold for the size of the Recoverable Items folder for the mailbox. If the Recoverable Items folder reaches or exceeds this size, Exchange logs an event to the application event log.
 
@@ -950,7 +950,7 @@ Accept wildcard characters: False
 
 ### -RetainDeletedItemsUntilBackup
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RetainDeletedItemsUntilBackup parameter specifies whether to keep items in the Recoverable Items\\Deletions folder of the mailbox until the next database backup occurs. Valid values are:
 
@@ -1002,7 +1002,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxDatabaseCopy.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxDatabaseCopy.md
index 91532aaab8..e85cf0fabf 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxDatabaseCopy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxDatabaseCopy.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -59,7 +59,7 @@ This example configures an activation preference of 3 for the copy of the databa
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the name of the database whose copy is being modified.
 
@@ -77,7 +77,7 @@ Accept wildcard characters: False
 
 ### -ActivationPreference
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ActivationPreference parameter value is used as part of Active Manager's best copy selection process and to redistribute active mailbox databases throughout the database availability group (DAG) when using the RedistributeActiveDatabases.ps1 script. The value for the ActivationPreference parameter is a number equal to or greater than 1, where 1 is at the top of the preference order. The position number can't be larger than the number of database copies of the mailbox database.
 
@@ -95,7 +95,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -116,7 +116,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -134,7 +134,7 @@ Accept wildcard characters: False
 
 ### -ReplayLagTime
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ReplayLagTime parameter specifies the amount of time that the Microsoft Exchange Replication service should wait before replaying log files that have been copied to the passive database copy. Setting this parameter to a value greater than 0 creates a lagged database copy.
 
@@ -158,7 +158,7 @@ Accept wildcard characters: False
 
 ### -TruncationLagTime
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TruncationLagTime parameter specifies the amount of time that the Microsoft Exchange Replication service should wait before truncating log files that have replayed into the passive copy of the database. The time period begins after the log is successfully replayed into the copy of the database.
 
@@ -180,7 +180,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
@@ -198,7 +198,7 @@ Accept wildcard characters: False
 
 ### -DatabaseCopyAutoActivationPolicy
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -216,7 +216,7 @@ Accept wildcard characters: False
 
 ### -ReplayLagMaxDelay
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ReplayLagMaxDelay parameter specifies the maximum delay for lagged database copy play down (also known as deferred lagged copy play down). If the disk read IO latency is greater than 25 ms, lagged copy play down is delayed up to the value of this parameter.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxExportRequest.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxExportRequest.md
index b81f0286db..fe5b9cea85 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxExportRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxExportRequest.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -72,7 +72,7 @@ This example changes the second export request Ayla\\MailboxExport1 to accept up
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the identity of the export request. By default, export requests are named `<alias>\MailboxExportX` (where X = 0-9). If you specify a name for the export request, use the following syntax: `Alias\Name`.
 
@@ -90,7 +90,7 @@ Accept wildcard characters: False
 
 ### -AcceptLargeDataLoss
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AcceptLargeDataLoss switch specifies the request should continue even if a large number of items in the source mailbox can't be copied to the target mailbox. You don't need to specify a value with this switch.
 
@@ -112,7 +112,7 @@ Accept wildcard characters: False
 
 ### -BadItemLimit
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The BadItemLimit parameter specifies the maximum number of bad items that are allowed before the request fails. A bad item is a corrupt item in the source mailbox that can't be copied to the target mailbox. Also included in the bad item limit are missing items. Missing items are items in the source mailbox that can't be found in the target mailbox when the request is ready to complete.
 
@@ -134,7 +134,7 @@ Accept wildcard characters: False
 
 ### -BatchName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The BatchName parameter specifies the name of the batch.
 
@@ -152,7 +152,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -173,7 +173,7 @@ Accept wildcard characters: False
 
 ### -CompletedRequestAgeLimit
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The CompletedRequestAgeLimit parameter specifies how long the request is kept after it has completed before being automatically removed. The default value is 30 days.
 
@@ -191,7 +191,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -209,7 +209,7 @@ Accept wildcard characters: False
 
 ### -InternalFlags
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The InternalFlags parameter specifies the optional steps in the request. This parameter is used primarily for debugging purposes.
 
@@ -227,7 +227,7 @@ Accept wildcard characters: False
 
 ### -LargeItemLimit
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The LargeItemLimit parameter specifies the maximum number of large items that are allowed before the request fails. A large item is a message in the source mailbox that exceeds the maximum message size that's allowed in the target mailbox. If the target mailbox doesn't have a specifically configured maximum message size value, the organization-wide value is used.
 
@@ -254,7 +254,7 @@ Accept wildcard characters: False
 
 ### -Priority
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Priority parameter specifies the order in which the request should be processed in the request queue. Requests are processed in order, based on server health, status, priority, and last update time. Valid priority values are:
 
@@ -281,7 +281,7 @@ Accept wildcard characters: False
 
 ### -RehomeRequest
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RehomeRequest switch tells the Microsoft Exchange Mailbox Replication service (MRS) that the request needs to be moved to the same database as the mailbox that's being exported. You don't need to specify a value with this switch.
 
@@ -301,7 +301,7 @@ Accept wildcard characters: False
 
 ### -RemoteCredential
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -319,7 +319,7 @@ Accept wildcard characters: False
 
 ### -RemoteHostName
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -337,7 +337,7 @@ Accept wildcard characters: False
 
 ### -SkipMerging
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SkipMerging parameter specifies steps in the export that should be skipped. This parameter is used primarily for debugging purposes.
 
@@ -355,7 +355,7 @@ Accept wildcard characters: False
 
 ### -RequestExpiryInterval
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RequestExpiryInterval parameter specifies an age limit for a completed or failed request. When you use this parameter, the completed or failed request is automatically removed after the specified interval expires. If you don't use this parameter:
 
@@ -380,7 +380,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxFolderPermission.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxFolderPermission.md
index 223ac5f5c3..72c6e76489 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxFolderPermission.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxFolderPermission.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
 Locale: en-US
@@ -84,7 +84,7 @@ In Exchange Online, this example changes an existing user's permissions to Edito
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the target mailbox and folder. The syntax is `MailboxID:\ParentFolder[\SubFolder]`.
 
@@ -117,7 +117,7 @@ Accept wildcard characters: False
 
 ### -AccessRights
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AccessRights parameter specifies the permissions that you want to modify for the user on the mailbox folder. The values that you specify replace the existing permissions for the user on the folder.
 
@@ -169,7 +169,7 @@ Accept wildcard characters: False
 
 ### -User
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The User parameter specifies the mailbox, mail user, or mail-enabled security group (security principal) that's granted permission to the mailbox folder.
 
@@ -201,7 +201,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -222,7 +222,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -298,7 +298,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxImportRequest.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxImportRequest.md
index 86bba500cd..fb66c38f42 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxImportRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxImportRequest.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -80,7 +80,7 @@ This example finds all import requests that have a status of Suspended, and then
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the identity of the import request. By default, import requests are named `<alias>\MailboxImportX` (where X = 0-9). If you specified a name for the import request with the New-MailboxImportRequest cmdlet, use the following syntax: `Alias\Name`.
 
@@ -118,7 +118,7 @@ Accept wildcard characters: False
 
 ### -AcceptLargeDataLoss
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AcceptLargeDataLoss switch specifies the request should continue even if a large number of items in the source mailbox can't be copied to the target mailbox. You don't need to specify a value with this switch.
 
@@ -140,7 +140,7 @@ Accept wildcard characters: False
 
 ### -BadItemLimit
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The BadItemLimit parameter specifies the maximum number of bad items that are allowed before the request fails. A bad item is a corrupt item in the source mailbox that can't be copied to the target mailbox. Also included in the bad item limit are missing items. Missing items are items in the source mailbox that can't be found in the target mailbox when the request is ready to complete.
 
@@ -164,7 +164,7 @@ Accept wildcard characters: False
 
 ### -BatchName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The BatchName parameter specifies the name of the batch.
 
@@ -182,7 +182,7 @@ Accept wildcard characters: False
 
 ### -CompletedRequestAgeLimit
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The CompletedRequestAgeLimit parameter specifies how long the request is kept after it has completed before being automatically removed. The default CompletedRequestAgeLimit parameter value is 30 days.
 
@@ -200,7 +200,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -221,7 +221,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -241,7 +241,7 @@ Accept wildcard characters: False
 
 ### -InternalFlags
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -261,7 +261,7 @@ Accept wildcard characters: False
 
 ### -LargeItemLimit
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The LargeItemLimit parameter specifies the maximum number of large items that are allowed before the request fails. A large item is a message in the source mailbox that exceeds the maximum message size that's allowed in the target mailbox. If the target mailbox doesn't have a specifically configured maximum message size value, the organization-wide value is used.
 
@@ -290,7 +290,7 @@ Accept wildcard characters: False
 
 ### -Priority
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -319,7 +319,7 @@ Accept wildcard characters: False
 
 ### -RehomeRequest
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -341,7 +341,7 @@ Accept wildcard characters: False
 
 ### -RequestExpiryInterval
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RequestExpiryInterval parameter specifies an age limit for a completed or failed request. When you use this parameter, the completed or failed request is automatically removed after the specified interval expires. If you don't use this parameter:
 
@@ -386,7 +386,7 @@ Accept wildcard characters: False
 
 ### -SkipMerging
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SkipMerging parameter specifies the steps in the import that should be skipped. This parameter is used primarily for debugging purposes.
 
@@ -424,7 +424,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxJunkEmailConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxJunkEmailConfiguration.md
index 7c763e94da..264b0132ca 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxJunkEmailConfiguration.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxJunkEmailConfiguration.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -83,7 +83,7 @@ This example identifies mailboxes where contacts are treated as trusted senders
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the mailbox that you want to modify. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -112,7 +112,7 @@ Accept wildcard characters: False
 
 ### -BlockedSendersAndDomains
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The BlockedSendersAndDomains parameter specifies the Blocked Senders list, which is a list of sender email addresses and domains whose messages are automatically sent to the Junk Email folder. This parameter corresponds to the Outlook on the web setting: Move email from these senders or domains to my Junk Email folder.
 
@@ -134,7 +134,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -155,7 +155,7 @@ Accept wildcard characters: False
 
 ### -ContactsTrusted
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ContactsTrusted parameter specifies whether the contacts in the Contacts folder are treated as trusted senders. This parameter corresponds to the Outlook on the web setting: Trust email from my contacts. Valid values are:
 
@@ -176,7 +176,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -196,7 +196,7 @@ Accept wildcard characters: False
 
 ### -Enabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Enabled parameter enables or disables the junk email rule on the mailbox (a hidden Inbox rule named Junk E-mail Rule). Valid values are:
 
@@ -253,7 +253,7 @@ Accept wildcard characters: False
 
 ### -IgnoreDefaultScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange PowerShell session, and to use the entire forest as the scope. You don't need to specify a value with this switch.
 
@@ -296,7 +296,7 @@ Accept wildcard characters: False
 
 ### -TrustedListsOnly
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The TrustedListsOnly parameter specifies that only messages from senders in the Safe Senders list are delivered to the Inbox. All other messages are treated as junk email. This parameter corresponds to the Outlook on the web setting: Don't trust email unless it comes from someone in my Safe Senders and Recipients list. Valid values are:
 
@@ -317,7 +317,7 @@ Accept wildcard characters: False
 
 ### -TrustedRecipientsAndDomains
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is reserved for internal Microsoft use.
 
@@ -335,7 +335,7 @@ Accept wildcard characters: False
 
 ### -TrustedSendersAndDomains
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The TrustedSendersAndDomains parameter specifies the Safe Senders list and Safe Recipients list, which are lists of email addresses and domains. Messages from these senders that reach the mailbox are never delivered to the Junk Email folder, regardless of the content. This parameter corresponds to the Outlook on the web setting: Don't move email from these senders or domains to my Junk Email folder.
 
@@ -365,7 +365,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxMessageConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxMessageConfiguration.md
index 40134436a3..22c5f6ec9a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxMessageConfiguration.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxMessageConfiguration.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -116,7 +116,7 @@ This example sets the compose email message form to always show the Bcc field in
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the mailbox that you want to modify. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -145,7 +145,7 @@ Accept wildcard characters: False
 
 ### -AfterMoveOrDeleteBehavior
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AfterMoveOrDeleteBehavior parameter specifies the behavior after moving or deleting an email item in Outlook on the web. You can use the following values:
 
@@ -169,7 +169,7 @@ Accept wildcard characters: False
 
 ### -AlwaysShowBcc
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AlwaysShowBcc parameter shows or hides the blind carbon copy (Bcc) field when the user creates messages in Outlook on the web.
 
@@ -189,7 +189,7 @@ Accept wildcard characters: False
 
 ### -AlwaysShowFrom
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AlwaysShowFrom parameter shows or hides the From field when the user creates messages in Outlook on the web.
 
@@ -209,7 +209,7 @@ Accept wildcard characters: False
 
 ### -AutoAddSignature
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 **Note**: This parameter doesn't work if the Outlook roaming signatures feature is enabled in your cloud-based organization. Admins can now temporarily disable roaming signatures without opening a support ticket by using the PostponeRoamingSignaturesUntilLater parameter on the Set-OrganizationConfig cmdlet.
 
@@ -234,7 +234,7 @@ Accept wildcard characters: False
 
 ### -AutoAddSignatureOnMobile
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 **Note**: This parameter doesn't work if the Outlook roaming signatures feature is enabled in your cloud-based organization. Admins can now temporarily disable roaming signatures without opening a support ticket by using the PostponeRoamingSignaturesUntilLater parameter on the Set-OrganizationConfig cmdlet.
 
@@ -256,7 +256,7 @@ Accept wildcard characters: False
 
 ### -AutoAddSignatureOnReply
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AutoAddSignature parameter specifies whether to automatically add signatures to reply email messages created in Outlook on the web. Valid values are:
 
@@ -279,7 +279,7 @@ Accept wildcard characters: False
 
 ### -CheckForForgottenAttachments
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The CheckForForgottenAttachments parameter shows or hides the attachment warning prompt when the user creates messages in Outlook on the web.
 
@@ -321,7 +321,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -342,7 +342,7 @@ Accept wildcard characters: False
 
 ### -ConversationSortOrder
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConversationSortOrder parameter specifies the sorting of messages in the reading pane in Conversation view for the user in Outlook on the web. You can use the following values:
 
@@ -370,7 +370,7 @@ Accept wildcard characters: False
 
 ### -DefaultFontColor
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DefaultFontColor parameter specifies the default text color when the user creates messages in Outlook on the web. This parameter accepts a hexadecimal color code value in the format #xxxxxx. The default value is #000000.
 
@@ -390,7 +390,7 @@ Accept wildcard characters: False
 
 ### -DefaultFontFlags
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DefaultFontFlags parameter specifies the default text effect when the user creates messages in Outlook on the web. You can use the following values:
 
@@ -416,7 +416,7 @@ Accept wildcard characters: False
 
 ### -DefaultFontName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DefaultFontName parameter specifies the default font when the user creates messages in Outlook on the web.
 
@@ -436,7 +436,7 @@ Accept wildcard characters: False
 
 ### -DefaultFontSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DefaultFontSize parameter specifies the default text size when the user creates messages in Outlook on the web.
 
@@ -456,7 +456,7 @@ Accept wildcard characters: False
 
 ### -DefaultFormat
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DefaultFormat parameter specifies the default message format when the user creates messages in Outlook on the web. Accepted values are Html and PlainText. The default value is Html.
 
@@ -554,7 +554,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -597,7 +597,7 @@ Accept wildcard characters: False
 
 ### -EmailComposeMode
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is functional only in on-premises Exchange.
 
@@ -620,7 +620,7 @@ Accept wildcard characters: False
 
 ### -EmptyDeletedItemsOnLogoff
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The EmptyDeletedItemsOnLogoff parameter specifies whether to delete items from the Deleted Items folder when the user logs out of Outlook on the web.
 
@@ -660,7 +660,7 @@ Accept wildcard characters: False
 
 ### -GlobalReadingPanePosition
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is functional only in Exchange 2016 or later. It doesn't work in Exchange Online.
 
@@ -684,7 +684,7 @@ Accept wildcard characters: False
 
 ### -HideDeletedItems
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The HideDeletedItems parameter shows or hides deleted messages in Conversation view for the user in Outlook on the web.
 
@@ -704,7 +704,7 @@ Accept wildcard characters: False
 
 ### -IgnoreDefaultScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange PowerShell session, and to use the entire forest as the scope. You don't need to specify a value with this switch.
 
@@ -747,7 +747,7 @@ Accept wildcard characters: False
 
 ### -IsFavoritesFolderTreeCollapsed
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IsFavoritesFolderTreeCollapsed parameter specifies whether to collapse the Favorites folder tree by default in Outlook on the web. Valid values are:
 
@@ -788,7 +788,7 @@ Accept wildcard characters: False
 
 ### -IsMailRootFolderTreeCollapsed
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IsMailRootFolderTreeCollapsed parameter specifies whether to collapse the Mail root folder tree by default in Outlook on the web. Valid values are:
 
@@ -809,7 +809,7 @@ Accept wildcard characters: False
 
 ### -IsReplyAllTheDefaultResponse
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IsReplyAllTheDefaultResponse parameter specifies whether Reply All is the default response for messages in Outlook on the web. Valid values are:
 
@@ -830,7 +830,7 @@ Accept wildcard characters: False
 
 ### -LinkPreviewEnabled
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The LinkPreviewEnabled parameter specifies whether link preview of URLs in email messages is enabled for the user in Outlook on the web. Valid values are:
 
@@ -853,7 +853,7 @@ Accept wildcard characters: False
 
 ### -MailFolderPaneExpanded
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MailFolderPaneExpanded parameter specifies whether the Mail folder pane is expanded by default in Outlook on the web. Valid values are:
 
@@ -934,7 +934,7 @@ Accept wildcard characters: False
 
 ### -NavigationPaneViewOption
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The NavigationPaneViewOption parameter specifies the default navigation pane view in Outlook on the web. Valid values are:
 
@@ -978,7 +978,7 @@ Accept wildcard characters: False
 
 ### -NewItemNotification
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The NewItemNotification parameter specifies how to provide notification for the arrival of new items for the user in Outlook on the web. You can use the following values:
 
@@ -1005,7 +1005,7 @@ Accept wildcard characters: False
 
 ### -PreferAccessibleContent
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The PreferAccessibleContent parameter specifies whether to prefer accessible content in Outlook on the web. Valid values are:
 
@@ -1026,7 +1026,7 @@ Accept wildcard characters: False
 
 ### -PreviewMarkAsReadBehavior
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The PreviewMarkAsReadBehavior parameter specifies the options for marking an item as Read in the reading pane for the user in Outlook on the web. You can use the following values:
 
@@ -1050,7 +1050,7 @@ Accept wildcard characters: False
 
 ### -PreviewMarkAsReadDelaytime
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The PreviewMarkAsReadDelaytime parameter specifies the time in seconds to wait before marking an item as Read for the user in Outlook on the web.
 
@@ -1072,7 +1072,7 @@ Accept wildcard characters: False
 
 ### -ReadReceiptResponse
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ReadReceiptResponse parameter specifies how to respond to requests for read receipts for the user in Outlook on the web. You can use the following values:
 
@@ -1149,7 +1149,7 @@ Accept wildcard characters: False
 
 ### -ShowConversationAsTree
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ShowConversationAsTree parameter specifies how to sort messages in the list view in an expanded conversation for the user in Outlook on the web.
 
@@ -1209,7 +1209,7 @@ Accept wildcard characters: False
 
 ### -ShowPreviewTextInListView
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ShowPreviewTextInListView parameter specifies whether to show preview text for messages in list view in Outlook on the web. Valid values are:
 
@@ -1230,7 +1230,7 @@ Accept wildcard characters: False
 
 ### -ShowReadingPaneOnFirstLoad
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ShowReadingPaneOnFirstLoad parameter specifies whether to show the reading pane when the user opens in Outlook on the web for the first time. Valid values are:
 
@@ -1251,7 +1251,7 @@ Accept wildcard characters: False
 
 ### -ShowSenderOnTopInListView
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ShowSenderOnTopInListView parameter specifies whether to show the message sender on top in list view in Outlook on the web. Valid values are:
 
@@ -1272,7 +1272,7 @@ Accept wildcard characters: False
 
 ### -ShowUpNext
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ShowUpNext parameter specifies whether the next upcoming event should be shown above the mail list view in Outlook on the web. Valid values are:
 
@@ -1293,7 +1293,7 @@ Accept wildcard characters: False
 
 ### -SignatureHtml
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 **Note**: This parameter doesn't work if the Outlook roaming signatures feature is enabled in your cloud-based organization. Admins can now temporarily disable roaming signatures without opening a support ticket by using the PostponeRoamingSignaturesUntilLater parameter on the Set-OrganizationConfig cmdlet.
 
@@ -1355,7 +1355,7 @@ Accept wildcard characters: False
 
 ### -SignatureText
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 **Note**: This parameter doesn't work if the Outlook roaming signatures feature is enabled in your cloud-based organization. Admins can now temporarily disable roaming signatures without opening a support ticket by using the PostponeRoamingSignaturesUntilLater parameter on the Set-OrganizationConfig cmdlet.
 
@@ -1377,7 +1377,7 @@ Accept wildcard characters: False
 
 ### -SignatureTextOnMobile
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 **Note**: This parameter doesn't work if the Outlook roaming signatures feature is enabled in your cloud-based organization. Admins can now temporarily disable roaming signatures without opening a support ticket by using the PostponeRoamingSignaturesUntilLater parameter on the Set-OrganizationConfig cmdlet.
 
@@ -1479,7 +1479,7 @@ Accept wildcard characters: False
 
 ### -UseDefaultSignatureOnMobile
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The UseDefaultSignatureOnMobile parameter specifies whether to add the default email signature to messages created by the user in Outlook on the web for devices. The user configures the default signature in Outlook.
 
@@ -1519,7 +1519,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxRegionalConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxRegionalConfiguration.md
index d9fdf8c9c0..ba7752e06d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxRegionalConfiguration.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxRegionalConfiguration.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -106,7 +106,7 @@ This example sets Megan Bowen mailbox language to Spanish Argentina, sets the da
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the mailbox that you want to modify. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -155,7 +155,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -176,7 +176,7 @@ Accept wildcard characters: False
 
 ### -DateFormat
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DateFormat parameter specifies a valid date format based on the current or specified language for the mailbox. For example, if the language is set to en-US, valid DateFormat parameter values include:
 
@@ -204,7 +204,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -224,7 +224,7 @@ Accept wildcard characters: False
 
 ### -Language
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Language parameter specifies the language for the mailbox.
 
@@ -264,7 +264,7 @@ Accept wildcard characters: False
 
 ### -LocalizeDefaultFolderName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The LocalizeDefaultFolderName switch localizes the default folder names of the mailbox in the current or specified language. You don't need to specify a value with this switch.
 
@@ -282,7 +282,7 @@ Accept wildcard characters: False
 
 ### -TimeFormat
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The TimeFormat parameter specifies a valid time format based on the current or specified language value for the mailbox. For example, if the language is set to en-us, valid TimeFormat parameter values include:
 
@@ -307,7 +307,7 @@ Accept wildcard characters: False
 
 ### -TimeZone
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The TimeZone parameter specifies the time zone for the mailbox.
 
@@ -351,7 +351,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxRestoreRequest.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxRestoreRequest.md
index fc864e68e8..699f3b7b49 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxRestoreRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxRestoreRequest.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -83,7 +83,7 @@ This example changes the first restore request for Kweku's mailbox to skip 100 c
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the identity of the restore request. The Identity parameter consists of the alias of the mailbox to be restored and the name that was specified when the restore request was created. The identity of the restore request uses the following syntax: `Alias\Name`
 
@@ -103,7 +103,7 @@ Accept wildcard characters: False
 
 ### -AcceptLargeDataLoss
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AcceptLargeDataLoss switch specifies the request should continue even if a large number of items in the source mailbox can't be copied to the target mailbox. You don't need to specify a value with this switch.
 
@@ -125,7 +125,7 @@ Accept wildcard characters: False
 
 ### -BadItemLimit
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The BadItemLimit parameter specifies the maximum number of bad items that are allowed before the request fails. A bad item is a corrupt item in the source mailbox that can't be copied to the target mailbox. Also included in the bad item limit are missing items. Missing items are items in the source mailbox that can't be found in the target mailbox when the request is ready to complete.
 
@@ -149,7 +149,7 @@ Accept wildcard characters: False
 
 ### -BatchName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The BatchName parameter specifies the name of the batch. Use this parameter to change, create, or remove a batch name.
 
@@ -169,7 +169,7 @@ Accept wildcard characters: False
 
 ### -CompletedRequestAgeLimit
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The CompletedRequestAgeLimit parameter specifies how long the status of a completed restore request is set to Completed. If this parameter is set to a value of 0, the status is cleared immediately instead of changing it to Completed.
 
@@ -187,7 +187,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -208,7 +208,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is functional only in on-premises Exchange.
 
@@ -228,7 +228,7 @@ Accept wildcard characters: False
 
 ### -InternalFlags
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is functional only in on-premises Exchange.
 
@@ -248,7 +248,7 @@ Accept wildcard characters: False
 
 ### -LargeItemLimit
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The LargeItemLimit parameter specifies the maximum number of large items that are allowed before the request fails. A large item is a message in the source mailbox that exceeds the maximum message size that's allowed in the target mailbox. If the target mailbox doesn't have a specifically configured maximum message size value, the organization-wide value is used.
 
@@ -277,7 +277,7 @@ Accept wildcard characters: False
 
 ### -Priority
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is functional only in on-premises Exchange.
 
@@ -306,7 +306,7 @@ Accept wildcard characters: False
 
 ### -RehomeRequest
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is functional only in on-premises Exchange.
 
@@ -328,7 +328,7 @@ Accept wildcard characters: False
 
 ### -RemoteHostName
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is reserved for internal Microsoft use.
 
@@ -346,7 +346,7 @@ Accept wildcard characters: False
 
 ### -RequestExpiryInterval
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RequestExpiryInterval parameter specifies an age limit for a completed or failed request. When you use this parameter, the completed or failed request is automatically removed after the specified interval expires. If you don't use this parameter:
 
@@ -391,7 +391,7 @@ Accept wildcard characters: False
 
 ### -SkipMerging
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SkipMerging parameter specifies folder-related items to skip when restoring the mailbox. Use one of the following values:
 
@@ -476,7 +476,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxSearch.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxSearch.md
index 0e5035c4d9..7506c5c6b8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxSearch.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxSearch.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
 Locale: en-US
@@ -89,7 +89,7 @@ In on-premises Exchange, this example adds all public folders to the existing ma
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the name of the mailbox search that you want to modify. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -107,7 +107,7 @@ Accept wildcard characters: False
 
 ### -AllPublicFolderSources
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllPublicFolderSources parameter specifies whether to include all public folders in the organization in the search. Valid values are:
 
@@ -128,7 +128,7 @@ Accept wildcard characters: False
 
 ### -AllSourceMailboxes
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllSourceMailboxes parameter specifies whether to include all mailboxes in the search. Valid values are:
 
@@ -149,7 +149,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -170,7 +170,7 @@ Accept wildcard characters: False
 
 ### -Description
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Description parameter specifies a description for the search. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -188,7 +188,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -230,7 +230,7 @@ Accept wildcard characters: False
 
 ### -EndDate
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The EndDate parameter specifies the end date of the date range.
 
@@ -252,7 +252,7 @@ Accept wildcard characters: False
 
 ### -EstimateOnly
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The EstimateOnly switch provides only an estimate of the number of items that will be returned without copying message to the target mailbox. You don't need to specify a value with this switch.
 
@@ -270,7 +270,7 @@ Accept wildcard characters: False
 
 ### -ExcludeDuplicateMessages
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ExcludeDuplicateMessages parameter eliminates duplication of messages across mailboxes in an In-Place eDiscovery search. Valid values are:
 
@@ -291,7 +291,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -311,7 +311,7 @@ Accept wildcard characters: False
 
 ### -IncludeKeywordStatistics
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IncludeKeywordStatistics switch returns keyword statistics (number of instances for each keyword). You don't need to specify a value with this switch.
 
@@ -329,7 +329,7 @@ Accept wildcard characters: False
 
 ### -IncludeUnsearchableItems
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IncludeUnsearchableItems parameter specifies whether items that couldn't be indexed by Exchange Search should be included in the results. Valid values are:
 
@@ -352,7 +352,7 @@ Accept wildcard characters: False
 
 ### -InPlaceHoldEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The InPlaceHoldEnabled parameter specifies whether to set an In-Place Hold on items in the search results. Valid values are:
 
@@ -377,7 +377,7 @@ Accept wildcard characters: False
 
 ### -ItemHoldPeriod
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ItemHoldPeriod parameter specifies the number of days for the In-Place Hold onthe mailbox items (all items or the mailbox items that are returned in the search query results). You use this parameter with the InPlaceHoldEnabled parameter to set an In-Place Hold. The duration is calculated from the time the item is received or created in the mailbox. Valid values are:
 
@@ -398,7 +398,7 @@ Accept wildcard characters: False
 
 ### -Language
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Language parameter specifies a locale for the mailbox search.
 
@@ -418,7 +418,7 @@ Accept wildcard characters: False
 
 ### -LogLevel
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The LogLevel parameter specifies a logging level for the mailbox search. Valid values are:
 
@@ -440,7 +440,7 @@ Accept wildcard characters: False
 
 ### -MessageTypes
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MessageTypes parameter specifies the message types to include in the search query. Valid values are:
 
@@ -471,7 +471,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Name parameter specifies a name for the search. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -491,7 +491,7 @@ Accept wildcard characters: False
 
 ### -Recipients
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Recipients parameter specifies one or more recipients include in the search query. Messages that have the specified recipients in the To, Cc, and Bcc fields are returned in the search results.
 
@@ -535,7 +535,7 @@ Accept wildcard characters: False
 
 ### -SearchQuery
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SearchQuery parameter specifies keywords for the search query by using the Keyword Query Language (KQL). For more information, see [Keyword Query Language (KQL) syntax reference](https://learn.microsoft.com/sharepoint/dev/general-development/keyword-query-language-kql-syntax-reference) and [Keyword queries and search conditions for eDiscovery](https://learn.microsoft.com/purview/ediscovery-keyword-queries-and-search-conditions).
 
@@ -563,7 +563,7 @@ Accept wildcard characters: False
 
 ### -Senders
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Senders parameter specifies one or more senders to include in the search query. Messages that have the specified sender are returned in the search results. Senders can include users, distribution groups (messages sent by members of the group), SMTP addresses, or domains.
 
@@ -585,7 +585,7 @@ Accept wildcard characters: False
 
 ### -SourceMailboxes
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SourceMailboxes parameter specifies the mailboxes to be searched. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -621,7 +621,7 @@ Accept wildcard characters: False
 
 ### -StartDate
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The StartDate parameter specifies the start date of the date range.
 
@@ -643,7 +643,7 @@ Accept wildcard characters: False
 
 ### -StatisticsStartIndex
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The StatisticsStartIndex parameter is used by the Exchange admin center (EAC) to retrieve keyword statistics in a paged operation.
 
@@ -661,7 +661,7 @@ Accept wildcard characters: False
 
 ### -StatusMailRecipients
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The StatusMailRecipients parameter specifies one or more recipients to receive a status email message upon completion of the search. You can use any value that uniquely identifies the recipient. For example:
 
@@ -688,7 +688,7 @@ Accept wildcard characters: False
 
 ### -TargetMailbox
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The TargetMailbox parameter specifies the destination mailbox where the search results are copied. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -717,7 +717,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxServer.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxServer.md
index 7748bd0a40..3b965ef2fd 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxServer.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxServer.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -195,7 +195,7 @@ In Exchange 2010, this example throttles the TopN Words Assistant and the Unifie
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the Mailbox server that you want to modify. You can use any value that uniquely identifies the server. For example:
 
@@ -217,7 +217,7 @@ Accept wildcard characters: False
 
 ### -AutoDagServerConfigured
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -235,7 +235,7 @@ Accept wildcard characters: False
 
 ### -AutoDatabaseMountDial
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AutoDatabaseMountDial parameter specifies the automatic database mount behavior for a continuous replication environment after a database failover on the Mailbox server. You can use the following values:
 
@@ -259,7 +259,7 @@ Accept wildcard characters: False
 
 ### -CalendarRepairIntervalEndWindow
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The CalendarRepairIntervalEndWindow parameter specifies the number of days into the future to repair calendar items in mailboxes on the Mailbox server.
 
@@ -281,7 +281,7 @@ Accept wildcard characters: False
 
 ### -CalendarRepairLogDirectorySizeLimit
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The CalendarRepairLogDirectorySizeLimit parameter specifies the maximum size of calendar repair log directory on the Mailbox server. When the directory reaches its maximum size, the server deletes the oldest log files first.
 
@@ -315,7 +315,7 @@ Accept wildcard characters: False
 
 ### -CalendarRepairLogEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The CalendarRepairLogEnabled parameter specifies whether the Calendar Repair Attendant logs items that it repairs on the Mailbox server. The repair log doesn't contain failed repair attempts.
 
@@ -342,7 +342,7 @@ Accept wildcard characters: False
 
 ### -CalendarRepairLogFileAgeLimit
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The CalendarRepairLogFileAgeLimit parameter specifies the calendar repair log maximum file age on the Mailbox server. Log files older than the specified value are deleted. The default value is 10 days.
 
@@ -364,7 +364,7 @@ Accept wildcard characters: False
 
 ### -CalendarRepairLogPath
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The CalendarRepairLogPath parameter specifies the location of the calendar repair log files on the Mailbox server. The default value is %ExchangeInstallPath%Logging\\Calendar Repair Assistant.
 
@@ -382,7 +382,7 @@ Accept wildcard characters: False
 
 ### -CalendarRepairLogSubjectLoggingEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The CalendarRepairLogSubjectLoggingEnabled parameter specifies whether to include the subject of repaired calendar items in the calendar repair log on the Mailbox server. Valid input for this parameter is $true or $false. The default value is $true.
 
@@ -400,7 +400,7 @@ Accept wildcard characters: False
 
 ### -CalendarRepairMissingItemFixDisabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The CalendarRepairMissingItemFixDisabled parameter specifies whether the Calendar Repair Assistant fixes missing calendar items in mailboxes on the Mailbox server.Valid input for this parameter is $true or $false. The default value is $false.
 
@@ -418,7 +418,7 @@ Accept wildcard characters: False
 
 ### -CalendarRepairMode
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The CalendarRepairMode parameter specifies the Calendar Repair Assistant mode on the Mailbox server. Valid values for this parameter are ValidateOnly or RepairAndValidate. The default value is RepairAndValidate.
 
@@ -527,7 +527,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -588,7 +588,7 @@ Accept wildcard characters: False
 
 ### -DatabaseCopyActivationDisabledAndMoveNow
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DatabaseCopyActivationDisabledAndMoveNow parameter specifies whether to prevent databases from being mounted on this Mailbox server if there are other healthy copies of the databases on other Mailbox servers. It also immediately moves any mounted databases on the server to other servers if copies exist and are healthy.
 
@@ -610,7 +610,7 @@ Accept wildcard characters: False
 
 ### -DatabaseCopyAutoActivationPolicy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DatabaseCopyAutoActivationPolicy parameter specifies the type of automatic activation available for mailbox database copies on the specified Mailbox server. Valid values for this parameter are:
 
@@ -672,7 +672,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -690,7 +690,7 @@ Accept wildcard characters: False
 
 ### -FaultZone
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -708,7 +708,7 @@ Accept wildcard characters: False
 
 ### -FolderLogForManagedFoldersEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is used for coexistence with Exchange 2010. Specifically, this parameter works with messaging records management (MRM) 1.0 (managed folders). This parameter doesn't work with MRM 2.0 (retention policies) that were introduced in Exchange 2010 Service Pack 1 (SP1).
 
@@ -740,7 +740,7 @@ Accept wildcard characters: False
 
 ### -ForceGroupMetricsGeneration
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ForceGroupMetricsGeneration parameter specifies that group metrics information must be generated on the Mailbox server regardless of whether that server generates an offline address book (OAB). Valid input for this parameter is $true or $false. The default value is $false.
 
@@ -1027,7 +1027,7 @@ Accept wildcard characters: False
 
 ### -IsExcludedFromProvisioning
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IsExcludedFromProvisioning parameter specifies that the Mailbox server isn't considered by the OAB provisioning load balancer. Valid values are:
 
@@ -1048,7 +1048,7 @@ Accept wildcard characters: False
 
 ### -JournalingLogForManagedFoldersEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The JournalingLogForManagedFoldersEnabled parameter specifies whether journaling activity is recorded in the managed folder log on the Mailbox server.Valid input for this parameter is$true or $false. The default value is $false.
 
@@ -1088,7 +1088,7 @@ Accept wildcard characters: False
 
 ### -Locale
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Locale parameter specifies the locale of the Mailbox server. A locale is a collection of language-related user preferences such as writing system, calendar, and date format. The following are examples:
 
@@ -1116,7 +1116,7 @@ Accept wildcard characters: False
 
 ### -LogDirectorySizeLimitForManagedFolders
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is used for coexistence with Exchange 2010. Specifically, this parameter works with messaging records management (MRM) 1.0 (managed folders). This parameter doesn't work with MRM 2.0 (retention policies) that were introduced in Exchange 2010 Service Pack 1 (SP1).
 
@@ -1150,7 +1150,7 @@ Accept wildcard characters: False
 
 ### -LogFileAgeLimitForManagedFolders
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is used for coexistence with Exchange 2010. Specifically, this parameter works with messaging records management (MRM) 1.0 (managed folders). This parameter doesn't work with MRM 2.0 (retention policies) that were introduced in Exchange 2010 Service Pack 1 (SP1).
 
@@ -1174,7 +1174,7 @@ Accept wildcard characters: False
 
 ### -LogFileSizeLimitForManagedFolders
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is used for coexistence with Exchange 2010. Specifically, this parameter works with messaging records management (MRM) 1.0 (managed folders). This parameter doesn't work with MRM 2.0 (retention policies) that were introduced in Exchange 2010 Service Pack 1 (SP1).
 
@@ -1206,7 +1206,7 @@ Accept wildcard characters: False
 
 ### -LogPathForManagedFolders
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is used for coexistence with Exchange 2010. Specifically, this parameter works with messaging records management (MRM) 1.0 (managed folders). This parameter doesn't work with MRM 2.0 (retention policies) that were introduced in Exchange 2010 Service Pack 1 (SP1).
 
@@ -1288,7 +1288,7 @@ Accept wildcard characters: False
 
 ### -ManagedFolderAssistantSchedule
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 **Note**: Although this parameter is available in Exchange 2016 and Exchange 2019, it's only used for coexistence with previous versions of Exchange. For more information, see [Configure and run the Managed Folder Assistant in Exchange Server](https://learn.microsoft.com/Exchange/policy-and-compliance/mrm/configure-managed-folder-assistant).
 
@@ -1383,7 +1383,7 @@ Accept wildcard characters: False
 
 ### -MAPIEncryptionRequired
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MAPIEncryptionRequired parameter specifies whether Exchange blocks MAPI client connections to the Mailbox server that don't use encrypted remote procedure calls (RPCs). Valid input for this parameter is$true or $false. The default value is $false.
 
@@ -1401,7 +1401,7 @@ Accept wildcard characters: False
 
 ### -MaximumActiveDatabases
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MaximumActiveDatabases parameter specifies the maximum number of databases that can be mounted on the Mailbox server.
 
@@ -1423,7 +1423,7 @@ Accept wildcard characters: False
 
 ### -MaximumPreferredActiveDatabases
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MaximumPreferredActiveDatabases parameter specifies a preferred maximum number of databases that theMailbox server should have. This value is different from the actual maximum, which is configured using the MaximumActiveDatabases parameter. The value of MaximumPreferredActiveDatabases is only honored during best copy and server selection, database and server switchovers, and when rebalancing the DAG.
 
@@ -1588,7 +1588,7 @@ Accept wildcard characters: False
 
 ### -MigrationLogFilePath
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -1606,7 +1606,7 @@ Accept wildcard characters: False
 
 ### -MigrationLogLoggingLevel
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -1624,7 +1624,7 @@ Accept wildcard characters: False
 
 ### -MigrationLogMaxAge
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -1642,7 +1642,7 @@ Accept wildcard characters: False
 
 ### -MigrationLogMaxDirectorySize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -1660,7 +1660,7 @@ Accept wildcard characters: False
 
 ### -MigrationLogMaxFileSize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -1890,7 +1890,7 @@ Accept wildcard characters: False
 
 ### -RetentionLogForManagedFoldersEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is used for coexistence with Exchange 2010. Specifically, this parameter works with messaging records management (MRM) 1.0 (managed folders). This parameter doesn't work with MRM 2.0 (retention policies) that were introduced in Exchange 2010 Service Pack 1 (SP1).
 
@@ -1992,7 +1992,7 @@ Accept wildcard characters: False
 
 ### -SharingPolicySchedule
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SharingPolicySchedule parameter specifies the intervals each week during which the sharing policy runs on the Mailbox server. The Sharing Policy Assistant checks permissions on shared calendar items and contact folders in users' mailboxes against the assigned sharing policy. The assistant lowers or removes permissions according to the policy.
 
@@ -2383,7 +2383,7 @@ Accept wildcard characters: False
 
 ### -SubjectLogForManagedFoldersEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is used for coexistence with Exchange 2010. Specifically, this parameter works with messaging records management (MRM) 1.0 (managed folders). This parameter doesn't work with MRM 2.0 (retention policies) that were introduced in Exchange 2010 Service Pack 1 (SP1).
 
@@ -2405,7 +2405,7 @@ Accept wildcard characters: False
 
 ### -SubmissionServerOverrideList
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -2527,7 +2527,7 @@ Accept wildcard characters: False
 
 ### -WacDiscoveryEndpoint
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WacDiscoveryEndpoint parameter specifies the discovery endpoint for Office Online Server (formerly known as Office Web Apps Server and Web Access Companion Server) for all mailboxes on the server. For example, `https://oos.internal.contoso.com/hosting/discovery`.
 
@@ -2547,7 +2547,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxSpellingConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxSpellingConfiguration.md
index ad74531f90..21303b2650 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxSpellingConfiguration.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxSpellingConfiguration.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -56,7 +56,7 @@ This example sets the spelling checker to ignore words containing numbers for me
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the mailbox that you want to modify. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -85,7 +85,7 @@ Accept wildcard characters: False
 
 ### -CheckBeforeSend
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The CheckBeforeSend parameter specifies whether Outlook on the web checks the spelling for every message when the user clicks Send in the new message form. Valid values are$true or $false. The default value is $false.
 
@@ -103,7 +103,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -124,7 +124,7 @@ Accept wildcard characters: False
 
 ### -DictionaryLanguage
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DictionaryLanguage parameter specifies the dictionary language to use when the spelling checker checks the spelling in messages. Valid values are:
 
@@ -164,7 +164,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -184,7 +184,7 @@ Accept wildcard characters: False
 
 ### -IgnoreMixedDigits
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IgnoreMixedDigits parameter specifies whether the spelling checker ignores words that contain numbers. Valid values are $true or $false. The default value is $false.
 
@@ -202,7 +202,7 @@ Accept wildcard characters: False
 
 ### -IgnoreUppercase
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IgnoreUppercase parameter specifies whether the spelling checker ignores words that contain only uppercase letters, for example, acronyms.
 
@@ -222,7 +222,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxTransportService.md b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxTransportService.md
index 98eb1644f0..d36117eb6e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-MailboxTransportService.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-MailboxTransportService.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -87,7 +87,7 @@ This example sets the ReceiveProtocolLogPath parameter to C:\\SMTP Protocol Logs
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the server that you want to modify.
 
@@ -105,7 +105,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -126,7 +126,7 @@ Accept wildcard characters: False
 
 ### -ConnectivityLogEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ConnectivityLogEnabled parameter specifies whether the connectivity log is enabled. The default value is $true.
 
@@ -144,7 +144,7 @@ Accept wildcard characters: False
 
 ### -ConnectivityLogMaxAge
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ConnectivityLogMaxAge parameter specifies the maximum age for the connectivity log file. Log files older than the specified value are deleted. The default value is 30 days.
 
@@ -166,7 +166,7 @@ Accept wildcard characters: False
 
 ### -ConnectivityLogMaxDirectorySize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ConnectivityLogMaxDirectorySize parameter specifies the maximum size of all connectivity logs in the connectivity log directory. When a directory reaches its maximum file size, the server deletes the oldest log files first. The default value is 1000 MB.
 
@@ -196,7 +196,7 @@ Accept wildcard characters: False
 
 ### -ConnectivityLogMaxFileSize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ConnectivityLogMaxFileSize parameter specifies the maximum size of each connectivity log file. When a log file reaches its maximum file size, a new log file is created. The default value is 10 MB.
 
@@ -226,7 +226,7 @@ Accept wildcard characters: False
 
 ### -ConnectivityLogPath
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ConnectivityLogPath parameter specifies the default connectivity log directory location. The default location is %ExchangeInstallPath%TransportRoles\\Logs\\Mailbox\\Connectivity. Setting the value of this parameter to $null disables connectivity logging. However, setting this parameter to $null when the value of the ConnectivityLogEnabled attribute is $true generates event log errors.
 
@@ -244,7 +244,7 @@ Accept wildcard characters: False
 
 ### -ContentConversionTracingEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ContentConversionTracingEnabled parameter specifies whether content conversion tracing is enabled. Content conversion tracing captures content conversion failures that occur in the Transport service or in the Mailbox Transport service on the Mailbox server. The default value is $false. Content conversion tracing captures a maximum of 128 MB of content conversion failures. When the 128 MB limit is reached, no more content conversion failures are captured. Content conversion tracing captures the complete contents of email messages to the path specified by the PipelineTracingPath parameter. Make sure that you restrict access to this directory. The permissions required on the directory specified by the PipelineTracingPath parameter are as follows:
 
@@ -266,7 +266,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -284,7 +284,7 @@ Accept wildcard characters: False
 
 ### -MailboxDeliveryAgentLogEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MailboxDeliveryAgentLogEnabled parameter specifies whether the agent log for the Mailbox Transport Delivery service is enabled. The default value is $true.
 
@@ -302,7 +302,7 @@ Accept wildcard characters: False
 
 ### -MailboxDeliveryAgentLogMaxAge
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MailboxDeliveryAgentLogMaxAge parameter specifies the maximum age for the agent log file of the Mailbox Transport Delivery service. Log files older than the specified value are deleted. The default value is 7.00:00:00 or 7 days.
 
@@ -324,7 +324,7 @@ Accept wildcard characters: False
 
 ### -MailboxDeliveryAgentLogMaxDirectorySize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MailboxDeliveryAgentLogMaxDirectorySize parameter specifies the maximum size of all Mailbox Transport Delivery service agent logs in the agent log directory. When a directory reaches its maximum file size, the server deletes the oldest log files first. The default value is 250 MB.
 
@@ -354,7 +354,7 @@ Accept wildcard characters: False
 
 ### -MailboxDeliveryAgentLogMaxFileSize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MailboxDeliveryAgentLogMaxFileSize parameter specifies the maximum size of each agent log file for the Mailbox Transport Delivery service. When a log file reaches its maximum file size, a new log file is created. The default value is 10 MB.
 
@@ -384,7 +384,7 @@ Accept wildcard characters: False
 
 ### -MailboxDeliveryAgentLogPath
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MailboxDeliveryAgentLogPath parameter specifies the default agent log directory location for the Mailbox Transport Delivery service. The default location is %ExchangeInstallPath%TransportRoles\\Logs\\Mailbox\\AgentLog\\Delivery. Setting the value of this parameter to $null disables agent logging. However, setting this parameter to $null when the value of the MailboxDeliveryAgentLogEnabled attribute is $true generates event log errors.
 
@@ -402,7 +402,7 @@ Accept wildcard characters: False
 
 ### -MailboxDeliveryConnectorMaxInboundConnection
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MailboxDeliveryConnectorMaxInboundConnection parameter specifies the maximum number of inbound connections for the implicit and invisible mailbox delivery Receive connector in the Mailbox Transport Delivery service. The default value is 5000. If you enter the value unlimited, no connection limit is imposed on the mailbox delivery Receive connector.
 
@@ -420,7 +420,7 @@ Accept wildcard characters: False
 
 ### -MailboxDeliveryConnectorProtocolLoggingLevel
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MailboxDeliveryConnectorProtocolLoggingLevel parameter enables or disables SMTP protocol logging for the implicit and invisible mailbox delivery Receive connector in the Mailbox Transport Delivery service. Valid values are:
 
@@ -441,7 +441,7 @@ Accept wildcard characters: False
 
 ### -MailboxDeliveryConnectorSmtpUtf8Enabled
 
-> Applicable: Exchange Server 2019
+> Applicable: Exchange Server 2019, Exchange Server SE
 
 The MailboxDeliveryConnectorSmtpUtf8Enabled parameters or disables email address internationalization (EAI) support for the implicit and invisible mailbox delivery Receive connector in the Mailbox Transport Delivery service. Valid values are:
 
@@ -462,7 +462,7 @@ Accept wildcard characters: False
 
 ### -MailboxDeliveryThrottlingLogEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MailboxDeliveryThrottlingLogEnabled parameter specifies whether the mailbox delivery throttling log is enabled. The default value is $true.
 
@@ -480,7 +480,7 @@ Accept wildcard characters: False
 
 ### -MailboxDeliveryThrottlingLogMaxAge
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MailboxDeliveryThrottlingLogMaxAge parameter specifies the maximum age for the mailbox delivery throttling log file. Log files older than the specified value are deleted. The default value is 7.00:00:00 or 7 days.
 
@@ -502,7 +502,7 @@ Accept wildcard characters: False
 
 ### -MailboxDeliveryThrottlingLogMaxDirectorySize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MailboxDeliveryThrottlingLogMaxDirectorySize parameter specifies the maximum size of all mailbox delivery throttling logs in the mailbox delivery throttling log directory. When a directory reaches its maximum file size, the server deletes the oldest log files first. The default value is 200 MB.
 
@@ -532,7 +532,7 @@ Accept wildcard characters: False
 
 ### -MailboxDeliveryThrottlingLogMaxFileSize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MailboxDeliveryThrottlingLogMaxFileSize parameter specifies the maximum size of each mailbox delivery throttling log file. When a log file reaches its maximum file size, a new log file is created. The default value is 10 MB.
 
@@ -562,7 +562,7 @@ Accept wildcard characters: False
 
 ### -MailboxDeliveryThrottlingLogPath
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MailboxDeliveryThrottlingLogPath parameter specifies the default mailbox delivery throttling log directory location. The default location is %ExchangeInstallPath%TransportRoles\\Logs\\Throttling\\Delivery. Setting the value of this parameter to $null disables mailbox delivery throttling logging. However, setting this parameter to $null when the value of the MailboxDeliveryThrottlingLogEnabled attribute is $true generates event log errors.
 
@@ -580,7 +580,7 @@ Accept wildcard characters: False
 
 ### -MailboxSubmissionAgentLogEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MailboxSubmissionAgentLogEnabled parameter specifies whether the agent log is enabled for the Mailbox Transport Submission service. The default value is $true.
 
@@ -598,7 +598,7 @@ Accept wildcard characters: False
 
 ### -MailboxSubmissionAgentLogMaxAge
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MailboxSubmissionAgentLogMaxAge parameter specifies the maximum age for the agent log file of the Mailbox Transport Submission service. Log files older than the specified value are deleted. The default value is 7.00:00:00 or 7 days.
 
@@ -620,7 +620,7 @@ Accept wildcard characters: False
 
 ### -MailboxSubmissionAgentLogMaxDirectorySize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MailboxSubmissionAgentLogMaxDirectorySize parameter specifies the maximum size of all Mailbox Transport Submission service agent logs in the agent log directory. When a directory reaches its maximum file size, the server deletes the oldest log files first. The default value is 250 MB.
 
@@ -650,7 +650,7 @@ Accept wildcard characters: False
 
 ### -MailboxSubmissionAgentLogMaxFileSize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MailboxSubmissionAgentLogMaxFileSize parameter specifies the maximum size of each agent log file for the Mailbox Transport Submission service. When a log file reaches its maximum file size, a new log file is created. The default value is 10 MB.
 
@@ -680,7 +680,7 @@ Accept wildcard characters: False
 
 ### -MailboxSubmissionAgentLogPath
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MailboxSubmissionAgentLogPath parameter specifies the default agent log directory location for the Mailbox Transport Submission service. The default location is %ExchangeInstallPath%TransportRoles\\Logs\\Mailbox\\AgentLog\\Submission. Setting the value of this parameter to $null disables agent logging. However, setting this parameter to $null when the value of the MailboxSubmissionAgentLogEnabled attribute is $true generates event log errors.
 
@@ -698,7 +698,7 @@ Accept wildcard characters: False
 
 ### -MaxConcurrentMailboxDeliveries
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MaxConcurrentMailboxDeliveries parameter specifies the maximum number of delivery threads that the transport service can have open at the same time to deliver messages to mailboxes. The default value is 20. The valid input range for this parameter is from 1 through 256. We recommend that you don't modify the default value unless Microsoft Customer Service and Support advises you to do this.
 
@@ -716,7 +716,7 @@ Accept wildcard characters: False
 
 ### -MaxConcurrentMailboxSubmissions
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MaxConcurrentMailboxSubmissions parameter specifies the maximum number of submission threads that the transport service can have open at the same time to send messages from mailboxes. The default value is 20. The valid input range for this parameter is from 1 through 256.
 
@@ -734,7 +734,7 @@ Accept wildcard characters: False
 
 ### -PipelineTracingEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PipelineTracingEnabled parameter specifies whether to enable pipeline tracing. Pipeline tracing captures message snapshot files that record the changes made to the message by each transport agent configured in the transport service on the server. Pipeline tracing creates verbose log files that accumulate quickly. Pipeline tracing should only be enabled for a short time to provide in-depth diagnostic information that enables you to troubleshoot problems. In addition to troubleshooting, you can use pipeline tracing to validate changes that you make to the configuration of the transport service where you enable pipeline tracing. The default value is $false.
 
@@ -752,7 +752,7 @@ Accept wildcard characters: False
 
 ### -PipelineTracingPath
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PipelineTracingPath parameter specifies the location of the pipeline tracing logs. The default location is %ExchangeInstallPath%TransportRoles\\Logs\\Mailbox\\PipelineTracing. The path must be local to the Exchange server.
 
@@ -778,7 +778,7 @@ Accept wildcard characters: False
 
 ### -PipelineTracingSenderAddress
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PipelineTracingSenderAddress parameter specifies the sender email address that invokes pipeline tracing. Only messages from this address generate pipeline tracing output. The address can be either inside or outside the Exchange organization. Depending on your requirements, you might have to set this parameter to different sender addresses and send new messages to start the transport agents or routes that you want to test. The default value of this parameter is $null.
 
@@ -796,7 +796,7 @@ Accept wildcard characters: False
 
 ### -ReceiveProtocolLogMaxAge
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ReceiveProtocolLogMaxAge parameter specifies the maximum age of a protocol log file for the implicit and invisible mailbox delivery Receive connector in the Mailbox Transport Delivery service. Log files that are older than the specified value are automatically deleted.
 
@@ -822,7 +822,7 @@ Accept wildcard characters: False
 
 ### -ReceiveProtocolLogMaxDirectorySize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ReceiveProtocolLogMaxDirectorySize parameter specifies the maximum size of the protocol log directory for the implicit and invisible mailbox delivery Receive connector in the Mailbox Transport Delivery service. When the maximum directory size is reached, the server deletes the oldest log files first.
 
@@ -856,7 +856,7 @@ Accept wildcard characters: False
 
 ### -ReceiveProtocolLogMaxFileSize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ReceiveProtocolLogMaxFileSize parameter specifies the maximum size of a protocol log file for the implicit and invisible mailbox delivery Receive connector in the Mailbox Transport Delivery service. When a log file reaches its maximum file size, a new log file is created.
 
@@ -890,7 +890,7 @@ Accept wildcard characters: False
 
 ### -ReceiveProtocolLogPath
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ReceiveProtocolLogPath parameter specifies the location of the protocol log directory for the implicit and invisible mailbox delivery Receive connector in the Mailbox Transport Delivery service. The default location is %ExchangeInstallPath%TransportRoles\\Logs\\Mailbox\\ProtocolLog\\SmtpReceive. The log files are automatically stored in the Delivery subdirectory.
 
@@ -910,7 +910,7 @@ Accept wildcard characters: False
 
 ### -RoutingTableLogMaxAge
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RoutingTableLogMaxAge parameter specifies the maximum routing table log age. Log files older than the specified value are deleted. The default value is 7 days.
 
@@ -932,7 +932,7 @@ Accept wildcard characters: False
 
 ### -RoutingTableLogMaxDirectorySize
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RoutingTableLogMaxDirectorySize parameter specifies the maximum size of the routing table log directory. When the maximum directory size is reached, the server deletes the oldest log files first. The default value is 250 MB.
 
@@ -962,7 +962,7 @@ Accept wildcard characters: False
 
 ### -RoutingTableLogPath
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RoutingTableLogPath parameter specifies the directory location where routing table log files should be stored. The default location is %ExchangeInstallPath%TransportRoles\\Logs\\Mailbox\\Routing. Setting this parameter to $null disables routing table logging.
 
@@ -980,7 +980,7 @@ Accept wildcard characters: False
 
 ### -SendProtocolLogMaxAge
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SendProtocolLogMaxAge parameter specifies the maximum age of a protocol log file for the implicit and invisible intra-organization Send connector in the Mailbox Transport Submission service. Log files that are older than the specified value are automatically deleted.
 
@@ -1004,7 +1004,7 @@ Accept wildcard characters: False
 
 ### -SendProtocolLogMaxDirectorySize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SendProtocolLogMaxDirectorySize parameter specifies the maximum size of the protocol log directory for the implicit and invisible intra-organization Send connector in the Mailbox Transport Submission service. When the maximum directory size is reached, the server deletes the oldest log files first.
 
@@ -1038,7 +1038,7 @@ Accept wildcard characters: False
 
 ### -SendProtocolLogMaxFileSize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SendProtocolLogMaxFileSize parameter specifies the maximum size of a protocol log file for the implicit and invisible intra-organization Send connector in the Mailbox Transport Submission service. When a log file reaches its maximum file size, a new log file is created.
 
@@ -1072,7 +1072,7 @@ Accept wildcard characters: False
 
 ### -SendProtocolLogPath
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SendProtocolLogPath parameter specifies the location of the protocol log directory for the implicit and invisible intra-organization Send connector in the Mailbox Transport Submission service. The default location is %ExchangeInstallPath%TransportRoles\\Logs\\Mailbox\\ProtocolLog\\SmtpSend. Log files are automatically stored in the following subdirectories:
 
@@ -1095,7 +1095,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MalwareFilterPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-MalwareFilterPolicy.md
index d697405ee3..4bcf5151bb 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-MalwareFilterPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-MalwareFilterPolicy.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -104,7 +104,7 @@ The last two commands remove the seventh file type that's displayed in the list.
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the malware filter policy you want to modify. You can use any value that uniquely identifies the policy. For example:
 
@@ -126,7 +126,7 @@ Accept wildcard characters: False
 
 ### -Action
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -150,7 +150,7 @@ Accept wildcard characters: False
 
 ### -AdminDisplayName
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The AdminDisplayName parameter specifies a description for the policy. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -168,7 +168,7 @@ Accept wildcard characters: False
 
 ### -BypassInboundMessages
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -191,7 +191,7 @@ Accept wildcard characters: False
 
 ### -BypassOutboundMessages
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -214,7 +214,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -235,7 +235,7 @@ Accept wildcard characters: False
 
 ### -CustomAlertText
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -257,7 +257,7 @@ Accept wildcard characters: False
 
 ### -CustomExternalBody
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The CustomExternalBody parameter specifies the custom body to use in notification messages for malware detections in messages from external senders. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -280,7 +280,7 @@ Accept wildcard characters: False
 
 ### -CustomExternalSubject
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The CustomExternalSubject parameter specifies the custom subject to use in notification messages for malware detections in messages from external senders. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -303,7 +303,7 @@ Accept wildcard characters: False
 
 ### -CustomFromAddress
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The CustomFromAddress parameter specifies the custom From address to use in notification messages for malware detections in messages from internal or external senders.
 
@@ -328,7 +328,7 @@ Accept wildcard characters: False
 
 ### -CustomFromName
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The CustomFromName parameter specifies the custom From name to use in notification messages for malware detections in messages from internal or external senders. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -353,7 +353,7 @@ Accept wildcard characters: False
 
 ### -CustomInternalBody
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The CustomInternalBody parameter specifies the custom body to use in notification messages for malware detections in messages from internal senders. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -376,7 +376,7 @@ Accept wildcard characters: False
 
 ### -CustomInternalSubject
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The CustomInternalSubject parameter specifies the custom subject to use in notification messages for malware detections in messages from internal senders. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -399,7 +399,7 @@ Accept wildcard characters: False
 
 ### -CustomNotifications
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The CustomNotifications parameter enables or disables the customization of notification messages for malware detections. Valid values are:
 
@@ -427,7 +427,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -447,7 +447,7 @@ Accept wildcard characters: False
 
 ### -EnableExternalSenderAdminNotifications
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The EnableExternalSenderAdminNotifications parameter enables or disables sending notification messages to an administrator for malware detections in messages from internal senders. Valid values are:
 
@@ -470,7 +470,7 @@ Accept wildcard characters: False
 
 ### -EnableExternalSenderNotifications
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -520,7 +520,7 @@ Accept wildcard characters: False
 
 ### -EnableInternalSenderAdminNotifications
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The EnableInternalSenderAdminNotifications parameter enables or disables sending notification messages to an administrator for malware detections in messages from internal senders. Valid values are:
 
@@ -543,7 +543,7 @@ Accept wildcard characters: False
 
 ### -EnableInternalSenderNotifications
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -566,7 +566,7 @@ Accept wildcard characters: False
 
 ### -ExternalSenderAdminAddress
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ExternalSenderAdminAddress parameter specifies the email address of the administrator who receives notifications messages for malware detections in messages from external senders.
 
@@ -641,7 +641,7 @@ Accept wildcard characters: False
 
 ### -InternalSenderAdminAddress
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The InternalSenderAdminAddress parameter specifies the email address of the administrator who receives notifications messages for malware detections in messages from internal senders.
 
@@ -679,7 +679,7 @@ Accept wildcard characters: False
 
 ### -MakeDefault
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The MakeDefault switch makes this malware filter policy the default policy. You don't need to specify a value with this switch.
 
@@ -729,7 +729,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MalwareFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-MalwareFilterRule.md
index c9a8199c78..4d1d9b9479 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-MalwareFilterRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-MalwareFilterRule.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -58,7 +58,7 @@ This example adds an exception to the malware filter rule named Contoso Recipien
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the malware filter rule that you want to view. You can use any value that uniquely identifies the rule. For example, you can use the name, GUID, or distinguished name (DN) of the malware filter rule.
 
@@ -76,7 +76,7 @@ Accept wildcard characters: False
 
 ### -Comments
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Comments parameter specifies informative comments for the rule, such as what the rule is used for or how it has changed over time. The length of the comment can't exceed 1024 characters.
 
@@ -94,7 +94,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -115,7 +115,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -135,7 +135,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfRecipientDomainIs
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ExceptIfRecipientDomainIs parameter specifies an exception that looks for recipients with email addresses in the specified domains. You can specify multiple domains separated by commas.
 
@@ -153,7 +153,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfSentTo
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ExceptIfSentTo parameter specifies an exception that looks for recipients in messages. You can use any value that uniquely identifies the recipient. For example:
 
@@ -180,7 +180,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfSentToMemberOf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ExceptIfSentToMemberOf parameter specifies an exception that looks for messages sent to members of distribution groups, mail-enabled security groups, or sent to Microsoft 365 Groups. You can use any value that uniquely identifies the group. For example:
 
@@ -209,7 +209,7 @@ Accept wildcard characters: False
 
 ### -MalwareFilterPolicy
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The MalwareFilterPolicy parameter specifies the malware filter policy that's associated with the malware filter rule.
 
@@ -235,7 +235,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Name parameter specifies a unique name for the malware filter rule.
 
@@ -253,7 +253,7 @@ Accept wildcard characters: False
 
 ### -Priority
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Priority parameter specifies a priority value for the rule that determines the order of rule processing. A lower integer value indicates a higher priority, the value 0 is the highest priority, and rules can't have the same priority value.
 
@@ -279,7 +279,7 @@ Accept wildcard characters: False
 
 ### -RecipientDomainIs
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The RecipientDomainIs parameter specifies a condition that looks for recipients with email addresses in the specified domains. You can specify multiple domains separated by commas.
 
@@ -297,7 +297,7 @@ Accept wildcard characters: False
 
 ### -SentTo
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The SentTo parameter specifies a condition that looks for recipients in messages. You can use any value that uniquely identifies the recipient. For example:
 
@@ -324,7 +324,7 @@ Accept wildcard characters: False
 
 ### -SentToMemberOf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The SentToMemberOf parameter specifies a condition that looks for messages sent to members of distribution groups, mail-enabled security groups, or sent to Microsoft 365 Groups. You can use any value that uniquely identifies the group. For example:
 
@@ -353,7 +353,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MalwareFilteringServer.md b/exchange/exchange-ps/ExchangePowerShell/Set-MalwareFilteringServer.md
index 3f204ae47a..fa0f636452 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-MalwareFilteringServer.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-MalwareFilteringServer.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -59,7 +59,7 @@ This example sets the following Malware agent settings on the Mailbox server nam
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the server where you want to configure the anti-malware settings. You can use any value that uniquely identifies the server. For example:
 
@@ -82,7 +82,7 @@ Accept wildcard characters: False
 
 ### -BypassFiltering
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The BypassFiltering parameter temporarily bypasses malware filtering without disabling the Malware agent on the server. The Malware agent is still active, and the agent is still called for every message, but no malware filtering is actually performed. This allows you to temporarily disable and then enable malware filtering on the server without disrupting mail flow by restarting the Microsoft Exchange Transport service. Valid input for this parameter is $true or $false. The default value is $false.
 
@@ -100,7 +100,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -121,7 +121,7 @@ Accept wildcard characters: False
 
 ### -DeferAttempts
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DeferAttempts parameter specifies the maximum number of times to defer a message that can't be scanned by the Malware agent. Valid input for this parameter is an integer between 1 and 5. The default value is 3.
 
@@ -141,7 +141,7 @@ Accept wildcard characters: False
 
 ### -DeferWaitTime
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DeferWaitTime parameter specifies the time period in minutes to increase the interval to resubmit messages for malware filtering in an effort to reduce the workload on the server.
 
@@ -163,7 +163,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -183,7 +183,7 @@ Accept wildcard characters: False
 
 ### -ForceRescan
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ForceRescan parameter specifies that messages should be scanned by the malware agent, even if the message was already scanned by cloud-based protection. Valid values are:
 
@@ -204,7 +204,7 @@ Accept wildcard characters: False
 
 ### -MinimumSuccessfulEngineScans
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -222,7 +222,7 @@ Accept wildcard characters: False
 
 ### -PrimaryUpdatePath
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PrimaryUpdatePath parameter specifies where to download malware scanning engine updates. The default value is `http://forefrontdl.microsoft.com/server/scanengineupdate`. The location specified by the PrimaryUpdatePath parameter is always tried first.
 
@@ -240,7 +240,7 @@ Accept wildcard characters: False
 
 ### -ScanErrorAction
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ScanErrorAction parameter specifies the action to take when a message can't be scanned by the malware filter. Valid values for this parameter are Block or Allow. The default value is Block.
 
@@ -258,7 +258,7 @@ Accept wildcard characters: False
 
 ### -ScanTimeout
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ScanTimeout parameter specifies the timeout interval in seconds for messages that can't be scanned by the malware filter. Valid input for this parameter is an integer between 10 and 900. The default value is 300 (5 minutes).
 
@@ -276,7 +276,7 @@ Accept wildcard characters: False
 
 ### -SecondaryUpdatePath
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SecondaryUpdatePath parameter specifies an alternate download location for malware scanning engine updates. The default values is blank ($null). This means no alternate download location is specified.
 
@@ -296,7 +296,7 @@ Accept wildcard characters: False
 
 ### -UpdateFrequency
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The UpdateFrequency parameter specifies the frequency interval in minutes to check for malware scanning engine updates. Valid input for this parameter is an integer between 1 and 38880 (27 days). The default value is 60 (one hour). The locations to check for updates are specified by the PrimaryUpdatePath and SecondaryUpdatePath parameters.
 
@@ -314,7 +314,7 @@ Accept wildcard characters: False
 
 ### -UpdateTimeout
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The UpdateTimeout parameter specifies the timeout interval in seconds to use when checking for malware scanning engine updates. Valid input for this parameter is an integer between 60 and 300. The default value is 150 seconds (2.5 minutes).
 
@@ -334,7 +334,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ManagedFolderMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-ManagedFolderMailboxPolicy.md
index e42e17a347..171f044fc0 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ManagedFolderMailboxPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ManagedFolderMailboxPolicy.md
@@ -43,7 +43,7 @@ Set-ManagedFolderMailboxPolicy "PM Storage Template1" -Name "PM Storage Template
 
 This example changes the name of the managed folder mailbox policy PM Storage Template1 to PM Storage Template2.
 
-The Identity parameter is a positional parameter. Positional parameters can be used without the label (Identity). For more information about positional parameters, see [About Parameters](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_parameters).
+The Identity parameter is positional, which means you can use it without the -Identity label in the supported location in the command (in this case, first).  For more information about positional parameters, see [About Parameters](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_parameters).
 
 ### Example 2
 ```powershell
@@ -58,7 +58,11 @@ This example links the managed custom folders Custom Folder 1 and Custom Folder
 
 > Applicable: Exchange Server 2010
 
-The Identity parameter specifies the name, distinguished name (DN), or GUID of the managed folder mailbox policy.
+The Identity parameter specifies the managed folder mailbox policy that you want to modify. You can use any value that uniquely identifies the policy. For example:
+
+- Name
+- Distinguished name (DN)
+- GUID
 
 ```yaml
 Type: MailboxPolicyIdParameter
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ManagementRoleAssignment.md b/exchange/exchange-ps/ExchangePowerShell/Set-ManagementRoleAssignment.md
index a0c404aed0..3b5d137088 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ManagementRoleAssignment.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ManagementRoleAssignment.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -142,7 +142,7 @@ This example restricts the Distribution Groups\_Cairns Admins role assignment us
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the name of the management role assignment to modify. If the name of the management role contains spaces, enclose it in quotation marks (").
 
@@ -160,7 +160,7 @@ Accept wildcard characters: False
 
 ### -RecipientAdministrativeUnitScope
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter is functional only in the cloud-based service.
 
@@ -204,7 +204,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -225,7 +225,7 @@ Accept wildcard characters: False
 
 ### -CustomConfigWriteScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -249,7 +249,7 @@ Accept wildcard characters: False
 
 ### -CustomRecipientWriteScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The CustomRecipientWriteScope parameter specifies the existing recipient-based management scope to associate with this management role assignment. If the management scope name contains spaces, enclose it in quotation marks (").
 
@@ -299,7 +299,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -319,7 +319,7 @@ Accept wildcard characters: False
 
 ### -Enabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Enabled parameter specifies whether the management role assignment is enabled or disabled. The valid values are $true and $false.
 
@@ -337,7 +337,7 @@ Accept wildcard characters: False
 
 ### -ExclusiveConfigWriteScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -361,7 +361,7 @@ Accept wildcard characters: False
 
 ### -ExclusiveRecipientWriteScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ExclusiveRecipientWriteScope parameter specifies the existing recipient-based exclusive management scope to associate with this management role assignment. If the management scope name contains spaces, enclose it in quotation marks (").
 
@@ -405,7 +405,7 @@ Accept wildcard characters: False
 
 ### -RecipientOrganizationalUnitScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The RecipientOrganizationalUnitScope parameter specifies the OU to scope the new role assignment to. If the OU name contains spaces, enclose the domain and OU in quotation marks (").
 
@@ -427,7 +427,7 @@ Accept wildcard characters: False
 
 ### -RecipientRelativeWriteScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The RecipientRelativeWriteScope parameter specifies the type of restriction to apply to a recipient scope.
 
@@ -451,7 +451,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ManagementRoleEntry.md b/exchange/exchange-ps/ExchangePowerShell/Set-ManagementRoleEntry.md
index 5ab67ee695..d44f3a41d9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ManagementRoleEntry.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ManagementRoleEntry.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -75,7 +75,7 @@ In on-premises Exchange, this example adds the Location parameter to the Mailbox
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the role entry that you want to modify. This parameter uses the syntax: `<management role>\<role entry name>` (for example, `CustomRole\Set-Mailbox`).
 
@@ -97,7 +97,7 @@ Accept wildcard characters: False
 
 ### -AddParameter
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The AddParameter switch specifies that you're adding parameters to the specified role entry. You don't need to specify a value with this switch.
 
@@ -119,7 +119,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -140,7 +140,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -182,7 +182,7 @@ Accept wildcard characters: False
 
 ### -Parameters
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Parameters parameter specifies the parameters to be added to or removed from the role entry.
 
@@ -208,7 +208,7 @@ Accept wildcard characters: False
 
 ### -RemoveParameter
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The RemoveParameter switch specifies that you're removing parameters to the specified role entry. You don't need to specify a value with this switch.
 
@@ -230,7 +230,7 @@ Accept wildcard characters: False
 
 ### -UnScopedTopLevel
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -254,7 +254,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ManagementScope.md b/exchange/exchange-ps/ExchangePowerShell/Set-ManagementScope.md
index 8b671cdcef..cb4707ab96 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ManagementScope.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ManagementScope.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -90,7 +90,7 @@ This example changes the Active Directory site used in the server restriction fi
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the name of the management scope to modify. If the name contains spaces, enclose it in quotation marks (").
 
@@ -108,7 +108,7 @@ Accept wildcard characters: False
 
 ### -DatabaseRestrictionFilter
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -139,7 +139,7 @@ Accept wildcard characters: False
 
 ### -ServerRestrictionFilter
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -170,7 +170,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -191,7 +191,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -233,7 +233,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Name parameter specifies the name of the management scope. The management scope name can be a maximum of 64 characters. If the name contains spaces, enclose it in quotation marks (").
 
@@ -251,7 +251,7 @@ Accept wildcard characters: False
 
 ### -RecipientRestrictionFilter
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The RecipientRestrictionFilter parameter uses OPATH filter syntax to specify the recipients that are included in the scope. The syntax is `"Property -ComparisonOperator 'Value'"`.
 
@@ -280,7 +280,7 @@ Accept wildcard characters: False
 
 ### -RecipientRoot
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The RecipientRoot parameter specifies the organizational unit (OU) under which the filter specified with the RecipientRestrictionFilter parameter should be applied. Valid input for this parameter is an OU or domain that's returned by the Get-OrganizationalUnit cmdlet. You can use any value that uniquely identifies the OU or domain. For example:
 
@@ -305,7 +305,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MapiVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Set-MapiVirtualDirectory.md
index bd261af787..cd48e72f02 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-MapiVirtualDirectory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-MapiVirtualDirectory.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -55,7 +55,7 @@ This example makes the following configuration changes to the MAPI virtual direc
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the MAPI virtual directory that you want to modify. You can use any value that uniquely identifies the virtual directory. For example:
 
@@ -79,7 +79,7 @@ Accept wildcard characters: False
 
 ### -ApplyDefaults
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ApplyDefaults switch specifies whether to apply the correct defaults to the related internal IIS application settings. Typically, this switch is used only by Exchange Setup during the installation of Exchange Cumulative Updates or Service Packs and you shouldn't need to use it.
 
@@ -99,7 +99,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -120,7 +120,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -138,7 +138,7 @@ Accept wildcard characters: False
 
 ### -ExtendedProtectionFlags
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExtendedProtectionFlags parameter specifies custom settings for Extended Protection for Authentication on the virtual directory. Valid values are:
 
@@ -162,7 +162,7 @@ Accept wildcard characters: False
 
 ### -ExtendedProtectionSPNList
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExtendedProtectionSPNList parameter specifies a list of valid Service Principal Names (SPNs) if you're using Extended Protection for Authentication on the virtual directory. Valid values are:
 
@@ -183,7 +183,7 @@ Accept wildcard characters: False
 
 ### -ExtendedProtectionTokenChecking
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExtendedProtectionTokenChecking parameter defines how you want to use Extended Protection for Authentication on the virtual directory. Extended Protection for Authentication isn't enabled by default. Valid values are:
 
@@ -207,7 +207,7 @@ Accept wildcard characters: False
 
 ### -ExternalUrl
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExternalURL parameter specifies the URL that's used to connect to the virtual directory from outside the firewall.
 
@@ -229,7 +229,7 @@ Accept wildcard characters: False
 
 ### -IISAuthenticationMethods
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IISAuthenticationMethods parameter specifies the authentication methods that are enabled on the virtual directory in Internet Information Services (IIS). Valid values are:
 
@@ -258,7 +258,7 @@ Accept wildcard characters: False
 
 ### -InternalUrl
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The InternalURL parameter specifies the URL that's used to connect to the virtual directory from inside the firewall.
 
@@ -280,7 +280,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MessageClassification.md b/exchange/exchange-ps/ExchangePowerShell/Set-MessageClassification.md
index c5de61e4a9..c2760e2c2a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-MessageClassification.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-MessageClassification.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -56,7 +56,7 @@ This example makes the following configuration changes to the message classifica
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the message classification that you want to modify. You can use any value that uniquely identifies the message classification. For example:
 
@@ -78,7 +78,7 @@ Accept wildcard characters: False
 
 ### -ClassificationID
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ClassificationID parameter specifies the classification ID (GUID) of an existing message classification that you want to import and use in your Exchange organization. Use this parameter if you're configuring message classifications that span two Exchange forests in the same organization.
 
@@ -98,7 +98,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -119,7 +119,7 @@ Accept wildcard characters: False
 
 ### -DisplayName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DisplayName parameter specifies the title of the message classification that's displayed in Outlook and selected by users. The maximum length is 256 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -139,7 +139,7 @@ Accept wildcard characters: False
 
 ### -DisplayPrecedence
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DisplayPrecedence parameter specifies the relative precedence of the message classification to other message classifications that might be applied to a specified message. Valid values are:
 
@@ -169,7 +169,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -191,7 +191,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Name parameter specifies the unique name for the message classification. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -209,7 +209,7 @@ Accept wildcard characters: False
 
 ### -PermissionMenuVisible
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The PermissionMenuVisible parameter specifies whether the values that you entered for the DisplayName and RecipientDescription parameters are displayed in Outlook as the user composes a message. Valid values are:
 
@@ -230,7 +230,7 @@ Accept wildcard characters: False
 
 ### -RecipientDescription
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RecipientDescription parameter specifies the detailed text that's shown to Outlook recipient when they receive a message that has the message classification applied. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -248,7 +248,7 @@ Accept wildcard characters: False
 
 ### -RetainClassificationEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RetainClassificationEnabled parameter specifies whether the message classification should persist with the message if the message is forwarded or replied to.
 
@@ -268,7 +268,7 @@ Accept wildcard characters: False
 
 ### -SenderDescription
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SenderDescription parameter specifies the detailed text that's shown to Outlook senders when they select a message classification to apply to a message before they send the message. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -286,7 +286,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MigrationBatch.md b/exchange/exchange-ps/ExchangePowerShell/Set-MigrationBatch.md
index f6ae4c00ee..16801ba5be 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-MigrationBatch.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-MigrationBatch.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -77,7 +77,7 @@ This example updates MigrationBatch01 by approving all of the skipped items for
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the migration batch that you want to modify. You can use any value that uniquely identifies the migration batch. For example:
 
@@ -118,7 +118,7 @@ Accept wildcard characters: False
 
 ### -AllowIncrementalSyncs
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -141,7 +141,7 @@ Accept wildcard characters: False
 
 ### -AllowUnknownColumnsInCsv
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowUnknownColumnsInCsv parameter specifies whether to allow extra columns in the CSV file that aren't used by migration. Valid values are:
 
@@ -186,7 +186,7 @@ Accept wildcard characters: False
 
 ### -AutoRetryCount
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -206,7 +206,7 @@ Accept wildcard characters: False
 
 ### -BadItemLimit
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The BadItemLimit parameter specifies the maximum number of bad items that are allowed before the migration request fails. A bad item is a corrupt item in the source mailbox that can't be copied to the target mailbox. Also included in the bad item limit are missing items. Missing items are items in the source mailbox that can't be found in the target mailbox when the migration request is ready to complete.
 
@@ -228,7 +228,7 @@ Accept wildcard characters: False
 
 ### -CompleteAfter
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is functional only in the cloud-based service.
 
@@ -255,7 +255,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -276,7 +276,7 @@ Accept wildcard characters: False
 
 ### -CSVData
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The CSVData parameter specifies the CSV file that contains information about the user mailboxes to be moved or migrated. The required attributes in the header row of the CSV file vary depending on the type of migration.
 
@@ -298,7 +298,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -318,7 +318,7 @@ Accept wildcard characters: False
 
 ### -LargeItemLimit
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The LargeItemLimit parameter specifies the maximum number of large items that are allowed before the migration request fails. A large item is a message in the source mailbox that exceeds the maximum message size that's allowed in the target mailbox. If the target mailbox doesn't have a specifically configured maximum message size value, the organization-wide value is used.
 
@@ -345,7 +345,7 @@ Accept wildcard characters: False
 
 ### -MoveOptions
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MoveOptions parameter specifies the stages of the migration that you want to skip for debugging purposes. Don't use this parameter unless you're directed to do so by Microsoft Customer Service and Support or specific documentation.
 
@@ -365,7 +365,7 @@ Accept wildcard characters: False
 
 ### -NotificationEmails
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The NotificationEmails parameter specifies one or more email addresses that migration status reports are sent to.
 
@@ -407,7 +407,7 @@ Accept wildcard characters: False
 
 ### -ReportInterval
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ReportInterval parameter specifies how frequently emailed reports should be sent to the email addresses listed within NotificationEmails.
 
@@ -429,7 +429,7 @@ Accept wildcard characters: False
 
 ### -SkipMerging
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SkipMerging parameter specifies the stages of the migration that you want to skip for debugging purposes. Don't use this parameter unless you're directed to do so by Microsoft Customer Service and Support or specific documentation.
 
@@ -447,7 +447,7 @@ Accept wildcard characters: False
 
 ### -SkipMoving
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is replaced by the MoveOptions parameter.
 
@@ -467,7 +467,7 @@ Accept wildcard characters: False
 
 ### -SkipReports
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SkipReports switch specifies that you want to skip automatic reporting for the migration. You don't need to specify a value with this switch.
 
@@ -485,7 +485,7 @@ Accept wildcard characters: False
 
 ### -SourcePublicFolderDatabase
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -509,7 +509,7 @@ Accept wildcard characters: False
 
 ### -StartAfter
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The StartAfter parameter specifies a delay before the data migration for the users within the batch is started. The migration is prepared, but the actual data migration for users within the batch doesn't start until the date/time you specify with this parameter.
 
@@ -534,7 +534,7 @@ Accept wildcard characters: False
 
 ### -SyncNow
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SyncNow switch starts an immediate sync for users that have already reached Synced status, but doesn't resume any Failed users. You don't need to specify a value with this switch.
 
@@ -554,7 +554,7 @@ Accept wildcard characters: False
 
 ### -Update
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Update switch sets the Update flag on the migration batch. You don't need to specify a value with this switch.
 
@@ -574,7 +574,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MigrationConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-MigrationConfig.md
index 605b6fd87b..cfcd6935cd 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-MigrationConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-MigrationConfig.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -56,7 +56,7 @@ This example sets the migration system to only allow 100 concurrent migrations.
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -77,7 +77,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -97,7 +97,7 @@ Accept wildcard characters: False
 
 ### -Features
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -122,7 +122,7 @@ Accept wildcard characters: False
 
 ### -MaxConcurrentMigrations
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -142,7 +142,7 @@ Accept wildcard characters: False
 
 ### -MaxNumberOfBatches
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -182,7 +182,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MigrationEndpoint.md b/exchange/exchange-ps/ExchangePowerShell/Set-MigrationEndpoint.md
index ff7cf2b290..be05400cb8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-MigrationEndpoint.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-MigrationEndpoint.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -89,7 +89,7 @@ This example changes the MaxConcurrentMigrations setting to 10 on the Onboarding
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the name of the migration endpoint you want to configure.
 
@@ -187,7 +187,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -208,7 +208,7 @@ Accept wildcard characters: False
 
 ### -Credentials
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Credentials parameter specifies the username and password for connecting to the remote endpoint. Credentials should be used when creating either a staged or cutover Exchange endpoint or a RemoteMove endpoint.
 
@@ -228,7 +228,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -293,7 +293,7 @@ Accept wildcard characters: False
 
 ### -MaxConcurrentIncrementalSyncs
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MaxConcurrentIncrementalSyncs parameter specifies the maximum number of incremental syncs allowed for this endpoint at a specified time. This value must be less or equal to MaxConcurrentMigrations parameter.
 
@@ -311,7 +311,7 @@ Accept wildcard characters: False
 
 ### -MaxConcurrentMigrations
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MaxConcurrentMigrations parameter specifies the maximum number of migrated mailboxes for this endpoint at a specified time. This parameter is applicable for all migration types.
 
@@ -409,7 +409,7 @@ Accept wildcard characters: False
 
 ### -RemoteServer
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RemoteServer parameter specifies the remote server depending on the protocol type for moves:
 
@@ -492,7 +492,7 @@ Accept wildcard characters: False
 
 ### -SkipVerification
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SkipVerification switch skips verifying that the remote server is reachable when creating a migration endpoint. You don't need to specify a value with this switch.
 
@@ -550,7 +550,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MigrationUser.md b/exchange/exchange-ps/ExchangePowerShell/Set-MigrationUser.md
index 9e26ca12a5..b5bd1e1a1a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-MigrationUser.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-MigrationUser.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -61,7 +61,7 @@ This example approves all of the skipped items encountered for the user laura@co
 
 ### -Identity
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the email address of the user that's being migrated.
 
@@ -107,7 +107,7 @@ Accept wildcard characters: False
 
 ### -BadItemLimit
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The BadItemLimit parameter specifies the maximum number of bad items that are allowed before the migration request fails. A bad item is a corrupt item in the source mailbox that can't be copied to the target mailbox. Also included in the bad item limit are missing items. Missing items are items in the source mailbox that can't be found in the target mailbox when the migration request is ready to complete.
 
@@ -158,7 +158,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -179,7 +179,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -199,7 +199,7 @@ Accept wildcard characters: False
 
 ### -LargeItemLimit
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The LargeItemLimit parameter specifies the maximum number of large items that are allowed before the migration request fails. A large item is a message in the source mailbox that exceeds the maximum message size that's allowed in the target mailbox. If the target mailbox doesn't have a specifically configured maximum message size value, the organization-wide value is used.
 
@@ -275,7 +275,7 @@ Accept wildcard characters: False
 
 ### -SyncNow
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SyncNow switch specifies whether to trigger an incremental sync for the migrated user. You don't need to specify a value with this switch.
 
@@ -295,7 +295,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MobileDeviceMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-MobileDeviceMailboxPolicy.md
index 1418931139..4a8c96d67e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-MobileDeviceMailboxPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-MobileDeviceMailboxPolicy.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
 Locale: en-US
@@ -120,7 +120,7 @@ This example sets several policy settings for the mobile device mailbox policy D
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the mobile device mailbox policy. You can use any value that uniquely identifies the policy. For example:
 
@@ -164,7 +164,7 @@ Accept wildcard characters: False
 
 ### -AllowBluetooth
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowBluetooth parameter specifies whether the Bluetooth capabilities are allowed on the mobile device. Valid values are:
 
@@ -190,7 +190,7 @@ Accept wildcard characters: False
 
 ### -AllowBrowser
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowBrowser parameter specifies whether Microsoft Pocket Internet Explorer is allowed on the mobile device. Valid input for this parameter is $true or $false. The default value is $true. This parameter doesn't affect non-Microsoft browsers.
 
@@ -208,7 +208,7 @@ Accept wildcard characters: False
 
 ### -AllowCamera
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowCamera parameter specifies whether the mobile device's camera is allowed. Valid input for this parameter is $true or $false. The default value is $true.
 
@@ -226,7 +226,7 @@ Accept wildcard characters: False
 
 ### -AllowConsumerEmail
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowConsumerEmail parameter specifies whether the user can configure a personal email account on the mobile device. Valid input for this parameter is $true or $false. The default value is $true. This parameter doesn't control access to email accounts using non-Microsoft mobile device email programs.
 
@@ -244,7 +244,7 @@ Accept wildcard characters: False
 
 ### -AllowDesktopSync
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowDesktopSync parameter specifies whether the mobile device can synchronize with a desktop computer through a cable. Valid input for this parameter is $true or $false. The default value is $true.
 
@@ -262,7 +262,7 @@ Accept wildcard characters: False
 
 ### -AllowExternalDeviceManagement
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowExternalDeviceManagement parameter specifies whether an external device management program is allowed to manage the mobile device. Valid input for this parameter is $true or $false. The default value is $false.
 
@@ -300,7 +300,7 @@ Accept wildcard characters: False
 
 ### -AllowHTMLEmail
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowHTMLEmail parameter specifies whether HTML-formatted email is enabled on the mobile device. Valid input for this parameter is $true or $false. The default value is $true. If set to $false, all email is converted to plain text before synchronization occurs.
 
@@ -318,7 +318,7 @@ Accept wildcard characters: False
 
 ### -AllowInternetSharing
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowInternetSharing parameter specifies whether the mobile device can be used as a modem to connect a computer to the Internet. This process is also known as tethering. Valid input for this parameter is $true or $false. The default value is $true.
 
@@ -336,7 +336,7 @@ Accept wildcard characters: False
 
 ### -AllowIrDA
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowIrDA parameter specifies whether infrared connections are allowed to the mobile device. Valid input for this parameter is $true or $false. The default value is $true.
 
@@ -374,7 +374,7 @@ Accept wildcard characters: False
 
 ### -AllowMobileOTAUpdate
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowMobileOTAUpdate parameter specifies whether the policy can be sent to the mobile device over a cellular data connection. Valid input for this parameter is $true or $false. The default value is $true.
 
@@ -392,7 +392,7 @@ Accept wildcard characters: False
 
 ### -AllowNonProvisionableDevices
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowNonProvisionableDevices parameter specifies whether all mobile devices can synchronize with Exchange. Valid input for this parameter is $true or $false. The default value is $true.
 
@@ -412,7 +412,7 @@ Accept wildcard characters: False
 
 ### -AllowPOPIMAPEmail
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowPOPIMAPEmail parameter specifies whether the user can configure a POP3 or IMAP4 email account on the mobile device. Valid input for this parameter is $true or $false. The default value is $true. This parameter doesn't control access by non-Microsoft email programs.
 
@@ -430,7 +430,7 @@ Accept wildcard characters: False
 
 ### -AllowRemoteDesktop
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowRemoteDesktop parameter specifies whether the mobile device can initiate a remote desktop connection. Valid input for this parameter is $true or $false. The default value is $true.
 
@@ -448,7 +448,7 @@ Accept wildcard characters: False
 
 ### -AllowSimplePassword
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowSimplePassword parameter specifies whether a simple password is allowed on the mobile device. A simple password is a password that has a specific pattern, such as 1111 or 1234. Valid input for this parameter is $true or $false. The default value is $true.
 
@@ -466,7 +466,7 @@ Accept wildcard characters: False
 
 ### -AllowSMIMEEncryptionAlgorithmNegotiation
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowSMIMEEncryptionAlgorithmNegotiation parameter specifies whether the messaging application on the mobile device can negotiate the encryption algorithm if a recipient's certificate doesn't support the specified encryption algorithm. Valid values for this parameter are:
 
@@ -490,7 +490,7 @@ Accept wildcard characters: False
 
 ### -AllowSMIMESoftCerts
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowSMIMESoftCerts parameter specifies whether S/MIME software certificates are allowed on the mobile device. Valid input for this parameter is $true or $false. The default value is $true.
 
@@ -508,7 +508,7 @@ Accept wildcard characters: False
 
 ### -AllowStorageCard
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowStorageCard parameter specifies whether the mobile device can access information stored on a storage card. Valid input for this parameter is $true or $false. The default value is $true.
 
@@ -526,7 +526,7 @@ Accept wildcard characters: False
 
 ### -AllowTextMessaging
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowTextMessaging parameter specifies whether text messaging is allowed from the mobile device. Valid input for this parameter is $true or $false. The default value is $true.
 
@@ -544,7 +544,7 @@ Accept wildcard characters: False
 
 ### -AllowUnsignedApplications
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowUnsignedApplications parameter specifies whether unsigned applications can be installed on the mobile device. Valid input for this parameter is $true or $false. The default value is $true.
 
@@ -562,7 +562,7 @@ Accept wildcard characters: False
 
 ### -AllowUnsignedInstallationPackages
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowUnsignedInstallationPackages parameter specifies whether unsigned installation packages can be executed on the mobile device. Valid input for this parameter is $true or $false. The default value is $true.
 
@@ -580,7 +580,7 @@ Accept wildcard characters: False
 
 ### -AllowWiFi
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowWiFi parameter specifies whether wireless Internet access is allowed on the mobile device. Valid input for this parameter is $true or $false. The default value is $true.
 
@@ -598,7 +598,7 @@ Accept wildcard characters: False
 
 ### -AlphanumericPasswordRequired
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AlphanumericPasswordRequired parameter specifies whether the password for the mobile device must be alphanumeric. Valid input for this parameter is $true or $false. The default value is $false.
 
@@ -616,7 +616,7 @@ Accept wildcard characters: False
 
 ### -ApprovedApplicationList
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ApprovedApplicationList parameter specifies a configured list of approved applications for the device.
 
@@ -634,7 +634,7 @@ Accept wildcard characters: False
 
 ### -AttachmentsEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AttachmentsEnabled parameter specifies whether attachments can be downloaded on the mobile device. Valid input for this parameter is $true or $false. The default value is $true.
 
@@ -654,7 +654,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -675,7 +675,7 @@ Accept wildcard characters: False
 
 ### -DeviceEncryptionEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 **Note**: This setting is supported by Outlook for iOS and Android.
 
@@ -697,7 +697,7 @@ Accept wildcard characters: False
 
 ### -DevicePolicyRefreshInterval
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DevicePolicyRefreshInterval parameter specifies how often the policy is sent to the mobile device.
 
@@ -719,7 +719,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -739,7 +739,7 @@ Accept wildcard characters: False
 
 ### -IrmEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IrmEnabled parameter specifies whether Information Rights Management (IRM) is enabled for the mobile device. Valid input for this parameter is $true or $false. The default value is $true.
 
@@ -757,7 +757,7 @@ Accept wildcard characters: False
 
 ### -IsDefault
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IsDefault parameter specifies whether this policy is the default mobile device mailbox policy. Valid input for this parameter is $true or $false. The default value for the built-in mobile device mailbox policy named Default is $true. The default value for new mobile device mailbox policies that you create is $false.
 
@@ -777,7 +777,7 @@ Accept wildcard characters: False
 
 ### -MaxAttachmentSize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MaxAttachmentSize parameter specifies the maximum size of attachments that can be downloaded to the mobile device. Valid input for this parameter is a size value between 0 and 2147482624 bytes (approximately 2 GB), or the value Unlimited. The default value is Unlimited.
 
@@ -803,7 +803,7 @@ Accept wildcard characters: False
 
 ### -MaxCalendarAgeFilter
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MaxCalendarAgeFilter parameter specifies the maximum range of calendar days that can be synchronized to the mobile device. Valid values for this parameter are:
 
@@ -829,7 +829,7 @@ Accept wildcard characters: False
 
 ### -MaxEmailAgeFilter
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MaxEmailAgeFilter parameter specifies the maximum number of days of email items to synchronize to the mobile device. Valid values for this parameter are:
 
@@ -856,7 +856,7 @@ Accept wildcard characters: False
 
 ### -MaxEmailBodyTruncationSize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MaxEmailBodyTruncationSize parameter specifies the maximum size at which email messages are truncated when synchronized to the mobile device. Valid input for this parameter is an integer between 0 and 2147483647 (Int32) or the value Unlimited. The default value is Unlimited.
 
@@ -876,7 +876,7 @@ Accept wildcard characters: False
 
 ### -MaxEmailHTMLBodyTruncationSize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MaxEmailHTMLBodyTruncationSize parameter specifies the maximum size at which HTML-formatted email messages are truncated when synchronized to the mobile device. Valid input for this parameter is an integer between 0 and 2147483647 (Int32) or the value Unlimited. The default value is Unlimited.
 
@@ -896,7 +896,7 @@ Accept wildcard characters: False
 
 ### -MaxInactivityTimeLock
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MaxInactivityTimeLock parameter specifies the length of time that the mobile device can be inactive before the password is required to reactivate it. Valid values are:
 
@@ -917,7 +917,7 @@ Accept wildcard characters: False
 
 ### -MaxPasswordFailedAttempts
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MaxPasswordFailedAttempts parameter specifies the number of attempts a user can make to enter the correct password for the mobile device.
 
@@ -937,7 +937,7 @@ Accept wildcard characters: False
 
 ### -MinPasswordComplexCharacters
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MinPasswordComplexCharacters parameter specifies the character sets that are required in the password of the mobile device. The character sets are:
 
@@ -971,7 +971,7 @@ Accept wildcard characters: False
 
 ### -MinPasswordLength
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 **Note**: This setting is supported by Outlook for Android.
 
@@ -993,7 +993,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Name parameter specifies the friendly name of the mobile device mailbox policy.
 
@@ -1011,7 +1011,7 @@ Accept wildcard characters: False
 
 ### -PasswordEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The PasswordEnabled parameter specifies whether a password is required on the mobile device. Valid input for this parameter is $true or $false. The default value is $false.
 
@@ -1031,7 +1031,7 @@ Accept wildcard characters: False
 
 ### -PasswordExpiration
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The PasswordExpiration parameter specifies how long a password can be used on a mobile device before the user is forced to change the password. Valid values are:
 
@@ -1052,7 +1052,7 @@ Accept wildcard characters: False
 
 ### -PasswordHistory
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The PasswordHistory parameter specifies the number of unique new passwords that need to be created on the mobile device before an old password can be reused.
 
@@ -1072,7 +1072,7 @@ Accept wildcard characters: False
 
 ### -PasswordRecoveryEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The PasswordRecoveryEnabled parameter specifies whether the recovery password for the mobile device is stored in Exchange. Valid input for this parameter is $true or $false. The default value is $false.
 
@@ -1092,7 +1092,7 @@ Accept wildcard characters: False
 
 ### -RequireDeviceEncryption
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RequireDeviceEncryption parameter specifies whether encryption is required on the mobile device. Valid input for this parameter is $true or $false. The default value is $false.
 
@@ -1110,7 +1110,7 @@ Accept wildcard characters: False
 
 ### -RequireEncryptedSMIMEMessages
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RequireEncryptedSMIMEMessages parameter specifies whether the mobile device must send encrypted S/MIME messages. Valid input for this parameter is $true or $false. The default value is $false.
 
@@ -1128,7 +1128,7 @@ Accept wildcard characters: False
 
 ### -RequireEncryptionSMIMEAlgorithm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RequireEncryptionSMIMEAlgorithm parameter specifies the algorithm that's required to encrypt S/MIME messages on a mobile device. The valid values for this parameter are:
 
@@ -1154,7 +1154,7 @@ Accept wildcard characters: False
 
 ### -RequireManualSyncWhenRoaming
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RequireManualSyncWhenRoaming parameter specifies whether the mobile device must synchronize manually while roaming. Valid input for this parameter is $true or $false. The default value is $false.
 
@@ -1172,7 +1172,7 @@ Accept wildcard characters: False
 
 ### -RequireSignedSMIMEAlgorithm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RequireSignedSMIMEAlgorithm parameter specifies the algorithm that's used to sign S/MIME messages on the mobile device.
 
@@ -1192,7 +1192,7 @@ Accept wildcard characters: False
 
 ### -RequireSignedSMIMEMessages
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RequireSignedSMIMEMessages parameter specifies whether the mobile device must send signed S/MIME messages. Valid input for this parameter is $true or $false. The default value is $false.
 
@@ -1210,7 +1210,7 @@ Accept wildcard characters: False
 
 ### -RequireStorageCardEncryption
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RequireStorageCardEncryption parameter specifies whether storage card encryption is required on the mobile device. Valid input for this parameter is $true or $false. The default value is $false.
 
@@ -1230,7 +1230,7 @@ Accept wildcard characters: False
 
 ### -UnapprovedInROMApplicationList
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The UnapprovedInROMApplicationList parameter specifies a list of applications that can't be run in ROM on the mobile device.
 
@@ -1248,7 +1248,7 @@ Accept wildcard characters: False
 
 ### -UNCAccessEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The UNCAccessEnabled parameter specifies whether access to Microsoft Windows file shares is enabled from the mobile device. In on-premises Exchange organizations, access to specific shares is configured on the Exchange ActiveSync virtual directory.
 
@@ -1266,7 +1266,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
@@ -1284,7 +1284,7 @@ Accept wildcard characters: False
 
 ### -WSSAccessEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WSSAccessEnabled parameter specifies whether access to Microsoft Windows SharePoint Services is enabled from the mobile device. In on-premises Exchange organizations, access to specific shares is configured on the Exchange ActiveSync virtual directory.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-MoveRequest.md b/exchange/exchange-ps/ExchangePowerShell/Set-MoveRequest.md
index ea5a7779aa..47f81b815c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-MoveRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-MoveRequest.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -79,7 +79,7 @@ This example changes the move request for Sruthi to approve all skipped items en
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the identity of the mailbox or mail user. You can use the following values:
 
@@ -105,7 +105,7 @@ Accept wildcard characters: False
 
 ### -AcceptLargeDataLoss
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AcceptLargeDataLoss switch specifies the request should continue even if a large number of items in the source mailbox can't be copied to the target mailbox. You don't need to specify a value with this switch.
 
@@ -127,7 +127,7 @@ Accept wildcard characters: False
 
 ### -ArchiveTargetDatabase
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -153,7 +153,7 @@ Accept wildcard characters: False
 
 ### -BadItemLimit
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The BadItemLimit parameter specifies the maximum number of bad items that are allowed before the request fails. A bad item is a corrupt item in the source mailbox that can't be copied to the target mailbox. Also included in the bad item limit are missing items. Missing items are items in the source mailbox that can't be found in the target mailbox when the request is ready to complete.
 
@@ -177,7 +177,7 @@ Accept wildcard characters: False
 
 ### -BatchName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The BatchName parameter specifies a different name for a batch.
 
@@ -195,7 +195,7 @@ Accept wildcard characters: False
 
 ### -CompleteAfter
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The CompleteAfter parameter specifies a delay before the request is completed. The request is started, but not completed until the date/time you specify with this parameter.
 
@@ -222,7 +222,7 @@ Accept wildcard characters: False
 
 ### -CompletedRequestAgeLimit
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The CompletedRequestAgeLimit parameter specifies how long the request is kept after it has completed before being automatically removed. The default CompletedRequestAgeLimit parameter value is 30 days.
 
@@ -240,7 +240,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -261,7 +261,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -299,7 +299,7 @@ Accept wildcard characters: False
 
 ### -IncrementalSyncInterval
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IncrementalSyncInterval parameter specifies the wait time between incremental syncs. Use this parameter with the CompleteAfter parameter to create a move request that does periodic incremental syncs after the initial sync is complete.
 
@@ -321,7 +321,7 @@ Accept wildcard characters: False
 
 ### -InternalFlags
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -341,7 +341,7 @@ Accept wildcard characters: False
 
 ### -LargeItemLimit
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The LargeItemLimit parameter specifies the maximum number of large items that are allowed before the request fails. A large item is a message in the source mailbox that exceeds the maximum message size that's allowed in the target mailbox. If the target mailbox doesn't have a specifically configured maximum message size value, the organization-wide value is used.
 
@@ -370,7 +370,7 @@ Accept wildcard characters: False
 
 ### -MoveOptions
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MoveOptions parameter specifies the stages of the move that you want to skip for debugging purposes. Don't use this parameter unless you're directed to do so by Microsoft Customer Service and Support or specific documentation.
 
@@ -390,7 +390,7 @@ Accept wildcard characters: False
 
 ### -PreventCompletion
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The PreventCompletion parameter specifies whether to run the move request, but not allow it to complete. Valid values are:
 
@@ -411,7 +411,7 @@ Accept wildcard characters: False
 
 ### -Priority
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -440,7 +440,7 @@ Accept wildcard characters: False
 
 ### -Protect
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -491,7 +491,7 @@ Accept wildcard characters: False
 
 ### -RemoteCredential
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RemoteCredential parameter specifies the username and password an administrator who has permission to perform the mailbox move.
 
@@ -511,7 +511,7 @@ Accept wildcard characters: False
 
 ### -RemoteGlobalCatalog
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RemoteGlobalCatalog parameter specifies the FQDN of the global catalog server for the remote forest.
 
@@ -529,7 +529,7 @@ Accept wildcard characters: False
 
 ### -RemoteHostName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RemoteHostName parameter specifies the FQDN of the cross-forest organization from which you're moving the mailbox.
 
@@ -547,7 +547,7 @@ Accept wildcard characters: False
 
 ### -RequestExpiryInterval
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RequestExpiryInterval parameter specifies an age limit for a completed or failed request. When you use this parameter, the completed or failed request is automatically removed after the specified interval expires. If you don't use this parameter:
 
@@ -572,7 +572,7 @@ Accept wildcard characters: False
 
 ### -SkipMoving
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is replaced by the MoveOptions parameter.
 
@@ -612,7 +612,7 @@ Accept wildcard characters: False
 
 ### -StartAfter
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The StartAfter parameter specifies a delay before the request is started. The request isn't started until the date/time you specify with this parameter.
 
@@ -666,7 +666,7 @@ Accept wildcard characters: False
 
 ### -SuspendWhenReadyToComplete
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SuspendWhenReadyToComplete parameter specifies whether to suspend the move request before it reaches the status of CompletionInProgress. Instead of this parameter, we recommend using CompleteAfter parameter.
 
@@ -684,7 +684,7 @@ Accept wildcard characters: False
 
 ### -TargetDatabase
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -710,7 +710,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-Notification.md b/exchange/exchange-ps/ExchangePowerShell/Set-Notification.md
index 55cdd0e679..d128aa3891 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-Notification.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-Notification.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.WebClient-Help.xml
 Locale: en-US
@@ -71,7 +71,7 @@ This example configures the specified notification event to send notification em
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the notification event that you want to modify. You identify the notification event by its AlternativeID property value (a GUID). You can find this value by running the command: `Get-Notification | Format-List DisplayName,AlternativeID,StartTime,Status,Type`.
 
@@ -93,7 +93,7 @@ Accept wildcard characters: False
 
 ### -NotificationEmails
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The NotificationEmails parameter specifies the recipients for notification emails related to notification events. You can specify multiple recipients separated by commas.
 
@@ -118,7 +118,7 @@ Accept wildcard characters: False
 
 ### -ProcessType
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -140,7 +140,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -161,7 +161,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -181,7 +181,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-OabVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Set-OabVirtualDirectory.md
index b5baa5d5b7..c998400e9a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-OabVirtualDirectory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-OabVirtualDirectory.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -55,7 +55,7 @@ This example changes the external URL of the OAB virtual directory OAB (Default
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the OAB virtual directory that you want to modify. You can use any value that uniquely identifies the virtual directory. For example:
 
@@ -79,7 +79,7 @@ Accept wildcard characters: False
 
 ### -BasicAuthentication
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The BasicAuthentication parameter specifies whether Basic authentication is enabled on the virtual directory. Valid values are:
 
@@ -102,7 +102,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -123,7 +123,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -141,7 +141,7 @@ Accept wildcard characters: False
 
 ### -ExtendedProtectionFlags
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExtendedProtectionFlags parameter specifies custom settings for Extended Protection for Authentication on the virtual directory. Valid values are:
 
@@ -165,7 +165,7 @@ Accept wildcard characters: False
 
 ### -ExtendedProtectionSPNList
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExtendedProtectionSPNList parameter specifies a list of valid Service Principal Names (SPNs) if you're using Extended Protection for Authentication on the virtual directory. Valid values are:
 
@@ -186,7 +186,7 @@ Accept wildcard characters: False
 
 ### -ExtendedProtectionTokenChecking
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExtendedProtectionTokenChecking parameter defines how you want to use Extended Protection for Authentication on the virtual directory. Extended Protection for Authentication isn't enabled by default. Valid values are:
 
@@ -210,7 +210,7 @@ Accept wildcard characters: False
 
 ### -ExternalUrl
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExternalURL parameter specifies the URL that's used to connect to the virtual directory from outside the firewall.
 
@@ -228,7 +228,7 @@ Accept wildcard characters: False
 
 ### -InternalUrl
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The InternalURL parameter specifies the URL that's used to connect to the virtual directory from inside the firewall.
 
@@ -246,7 +246,7 @@ Accept wildcard characters: False
 
 ### -OAuthAuthentication
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -264,7 +264,7 @@ Accept wildcard characters: False
 
 ### -PollInterval
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is functional only in Exchange 2010.
 
@@ -284,7 +284,7 @@ Accept wildcard characters: False
 
 ### -RequireSSL
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RequireSSL parameter specifies whether the client connection to the virtual directory requires Secure Sockets Layer (SSL) encryption. Valid values are:
 
@@ -305,7 +305,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
@@ -323,7 +323,7 @@ Accept wildcard characters: False
 
 ### -WindowsAuthentication
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WindowsAuthentication parameter specifies whether Integrated Windows authentication is enabled on the virtual directory. Valid values are:
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-OfflineAddressBook.md b/exchange/exchange-ps/ExchangePowerShell/Set-OfflineAddressBook.md
index 9aa1ab5a32..985662bed9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-OfflineAddressBook.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-OfflineAddressBook.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -75,7 +75,7 @@ This example changes the organization mailbox that's responsible for generating
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the OAB that you want to modify. You can use any value that uniquely identifies the OAB. For example:
 
@@ -97,7 +97,7 @@ Accept wildcard characters: False
 
 ### -AddressLists
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AddressLists parameter specifies the address lists or global address lists that are included in the OAB. You can use any value that uniquely identifies the address list. For example:
 
@@ -123,7 +123,7 @@ Accept wildcard characters: False
 
 ### -ApplyMandatoryProperties
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ApplyMandatoryProperties switch specifies whether to update the mandatory properties of a legacy OAB. You don't need to specify a value with this switch.
 
@@ -143,7 +143,7 @@ Accept wildcard characters: False
 
 ### -ConfiguredAttributes
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConfiguredAttributes parameter specifies the recipient MAPI properties that are available in the OAB. This parameter uses the syntax: `"Name1,Type1","Name2,Type2",..."NameN,TypeN"` where Name is the name of the MAPI property (for example, MobileTelephoneNumber), and Type is the value ANR (ambiguous name resolution), Value, or Indicator.
 
@@ -163,7 +163,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -184,7 +184,7 @@ Accept wildcard characters: False
 
 ### -DiffRetentionPeriod
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DiffRetentionPeriod parameter specifies the number of days that the OAB difference files are stored on the server. Valid values are integers from 7 to 1825, or the value unlimited. The default value is 30.
 
@@ -202,7 +202,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -222,7 +222,7 @@ Accept wildcard characters: False
 
 ### -FullOabDownloadPreventionThreshold
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is reserved for internal Microsoft use.
 
@@ -240,7 +240,7 @@ Accept wildcard characters: False
 
 ### -GeneratingMailbox
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -275,7 +275,7 @@ Accept wildcard characters: False
 
 ### -GlobalWebDistributionEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -300,7 +300,7 @@ Accept wildcard characters: False
 
 ### -IsDefault
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IsDefault parameter specifies whether the OAB is used by all mailboxes and mailbox databases that don't have an OAB specified. Valid values are:
 
@@ -321,7 +321,7 @@ Accept wildcard characters: False
 
 ### -MaxBinaryPropertySize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -341,7 +341,7 @@ Accept wildcard characters: False
 
 ### -MaxMultivaluedBinaryPropertySize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -361,7 +361,7 @@ Accept wildcard characters: False
 
 ### -MaxMultivaluedStringPropertySize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -381,7 +381,7 @@ Accept wildcard characters: False
 
 ### -MaxStringPropertySize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -401,7 +401,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Name parameter specifies the unique name of the OAB. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks.
 
@@ -439,7 +439,7 @@ Accept wildcard characters: False
 
 ### -Schedule
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is functional only in Exchange 2010.
 
@@ -483,7 +483,7 @@ Accept wildcard characters: False
 
 ### -ShadowMailboxDistributionEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -508,7 +508,7 @@ Accept wildcard characters: False
 
 ### -UpgradeFromE14
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is reserved for internal Microsoft use.
 
@@ -526,7 +526,7 @@ Accept wildcard characters: False
 
 ### -UseDefaultAttributes
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The UseDefaultAttributes switch specifies whether to revert the recipient MAPI properties that are available in the OAB to the default list. You don't need to specify a value with this switch.
 
@@ -546,7 +546,7 @@ Accept wildcard characters: False
 
 ### -Versions
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Versions parameter specifies the OAB versions that are generated for client download. Valid values are:
 
@@ -568,7 +568,7 @@ Accept wildcard characters: False
 
 ### -VirtualDirectories
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -602,7 +602,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
@@ -620,7 +620,7 @@ Accept wildcard characters: False
 
 ### -ZipOabFilesBeforeUploading
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ZipOabFilesBeforeUploading specifies whether to use ZIP file compression on the OAB files before uploading them to the server. Valid values are:
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-OrganizationConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-OrganizationConfig.md
index 35f5f42bd8..76d5771931 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-OrganizationConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-OrganizationConfig.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -605,7 +605,7 @@ Accept wildcard characters: False
 
 ### -ACLableSyncedObjectEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -645,7 +645,7 @@ Accept wildcard characters: False
 
 ### -ActivityBasedAuthenticationTimeoutEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ActivityBasedAuthenticationTimeoutEnabled parameter enables or disables the inactivity interval for automatic logoff in Outlook on the web (formerly known as Outlook Web App). Valid values are:
 
@@ -668,7 +668,7 @@ Accept wildcard characters: False
 
 ### -ActivityBasedAuthenticationTimeoutInterval
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ActivityBasedAuthenticationTimeoutInterval parameter specifies the period of inactivity that causes an automatic logoff in Outlook on the web.
 
@@ -694,7 +694,7 @@ Accept wildcard characters: False
 
 ### -ActivityBasedAuthenticationTimeoutWithSingleSignOnEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ActivityBasedAuthenticationTimeoutWithSingleSignOnEnabled parameter enables or disables the inactivity interval for automatic logoff for single sign-on in Outlook on the Web. Valid values are:
 
@@ -717,7 +717,7 @@ Accept wildcard characters: False
 
 ### -AdfsAudienceUris
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -743,7 +743,7 @@ Accept wildcard characters: False
 
 ### -AdfsAuthenticationConfiguration
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -763,7 +763,7 @@ Accept wildcard characters: False
 
 ### -AdfsEncryptCertificateThumbprint
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -783,7 +783,7 @@ Accept wildcard characters: False
 
 ### -AdfsIssuer
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -805,7 +805,7 @@ Accept wildcard characters: False
 
 ### -AdfsSignCertificateThumbprints
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -831,7 +831,7 @@ Accept wildcard characters: False
 
 ### -AppsForOfficeEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AppsForOfficeEnabled parameter specifies whether to enable apps for Outlook features. By default, the parameter is set to $true. If the flag is set to $false, no new apps can be activated for any user in the organization.
 
@@ -849,7 +849,7 @@ Accept wildcard characters: False
 
 ### -AsyncSendEnabled
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AsyncSendEnabled parameter specifies whether to enable or disable async send in Outlook on the web. Valid values are:
 
@@ -1409,7 +1409,7 @@ Accept wildcard characters: False
 
 ### -ByteEncoderTypeFor7BitCharsets
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ByteEncoderTypeFor7BitCharsets parameter specifies the 7-bit transfer encoding method for MIME format for messages sent to this remote domain. The valid values for this parameter are:
 
@@ -1477,7 +1477,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -1498,7 +1498,7 @@ Accept wildcard characters: False
 
 ### -ConnectorsActionableMessagesEnabled
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConnectorsActionableMessagesEnabled parameter specifies whether to enable or disable actionable buttons in messages (connector cards) from connected apps on Outlook on the web. Valid values are:
 
@@ -1521,7 +1521,7 @@ Accept wildcard characters: False
 
 ### -ConnectorsEnabled
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConnectorsEnabled parameter specifies whether to enable or disable all connected apps in organization. Valid values are:
 
@@ -1640,7 +1640,7 @@ Accept wildcard characters: False
 
 ### -CustomerFeedbackEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1680,7 +1680,7 @@ Accept wildcard characters: False
 
 ### -DataClassifications
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1700,7 +1700,7 @@ Accept wildcard characters: False
 
 ### -DefaultAuthenticationPolicy
 
-> Applicable: Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The DefaultAuthenticationPolicy parameter specifies the authentication policy that's used for the whole organization. You can use any value that uniquely identifies the policy. For example:
 
@@ -1795,7 +1795,7 @@ Accept wildcard characters: False
 
 ### -DefaultPublicFolderAgeLimit
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DefaultPublicFolderAgeLimit parameter specifies the default age limit for the contents of public folders across the entire organization. Content in a public folder is automatically deleted when this age limit is exceeded. This attribute applies to all public folders in the organization that don't have their own AgeLimit setting.
 
@@ -1815,7 +1815,7 @@ Accept wildcard characters: False
 
 ### -DefaultPublicFolderDeletedItemRetention
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DefaultPublicFolderDeletedItemRetention parameter specifies the default value of the length of time to retain deleted items for public folders across the entire organization. This attribute applies to all public folders in the organization that don't have their own RetainDeletedItemsFor attribute set.
 
@@ -1833,7 +1833,7 @@ Accept wildcard characters: False
 
 ### -DefaultPublicFolderIssueWarningQuota
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DefaultPublicFolderIssueWarningQuota parameter specifies the default value across the entire organization for the public folder size at which a warning message is sent to this folder's owners, warning that the public folder is almost full. This attribute applies to all public folders within the organization that don't have their own warning quota attribute set. The default value of this attribute is unlimited.
 
@@ -1863,7 +1863,7 @@ Accept wildcard characters: False
 
 ### -DefaultPublicFolderMaxItemSize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DefaultPublicFolderMaxItemSize parameter specifies the default maximum size for posted items within public folders across the entire organization. Items larger than the value of the DefaultPublicFolderMaxItemSize parameter are rejected. This attribute applies to all public folders within the organization that don't have their own MaxItemSize attribute set. The default value of this attribute is unlimited.
 
@@ -1893,7 +1893,7 @@ Accept wildcard characters: False
 
 ### -DefaultPublicFolderMovedItemRetention
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DefaultPublicFolderMovedItemRetention parameter specifies how long items that have been moved between mailboxes are kept in the source mailbox for recovery purposes before being removed by the Public Folder Assistant.
 
@@ -1913,7 +1913,7 @@ Accept wildcard characters: False
 
 ### -DefaultPublicFolderProhibitPostQuota
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DefaultPublicFolderProhibitPostQuota parameter specifies the size of a public folder at which users are notified that the public folder is full. Users can't post to a folder whose size is larger than the DefaultPublicFolderProhibitPostQuota parameter value. The default value of this attribute is unlimited.
 
@@ -2026,7 +2026,7 @@ Accept wildcard characters: False
 
 ### -DistributionGroupDefaultOU
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DistributionGroupDefaultOU parameter specifies the container where distribution groups are created by default.
 
@@ -2044,7 +2044,7 @@ Accept wildcard characters: False
 
 ### -DistributionGroupNameBlockedWordsList
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DistributionGroupNameBlockedWordsList parameter specifies words that can't be included in the Display Name values of distribution groups that are created by users. Separate multiple values with commas.
 
@@ -2062,7 +2062,7 @@ Accept wildcard characters: False
 
 ### -DistributionGroupNamingPolicy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DistributionGroupNamingPolicy parameter specifies the additional text that's applied to the Display Name value of distribution groups created by users. You can require a prefix, a suffix, or both. The prefix and suffix can be text strings, user attribute values from the person who created the group, or a combination of text strings and attributes.
 
@@ -2097,7 +2097,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -2142,7 +2142,7 @@ Accept wildcard characters: False
 
 ### -EmptyAddressBookForNonExchangeUsers
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -2162,7 +2162,7 @@ Accept wildcard characters: False
 
 ### -EnableAuthAdminReadSession
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -2182,7 +2182,7 @@ Accept wildcard characters: False
 
 ### -EnableDownloadDomains
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -2227,7 +2227,7 @@ Accept wildcard characters: False
 
 ### -EnableOrgWidePermissionOnScopedRoles
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -2320,7 +2320,7 @@ Accept wildcard characters: False
 
 ### -EwsAllowEntourage
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The EwsAllowEntourage parameter specifies whether to enable or disable Entourage 2008 to access Exchange Web Services (EWS) for the entire organization. The default value is $true.
 
@@ -2338,7 +2338,7 @@ Accept wildcard characters: False
 
 ### -EwsAllowList
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The EwsAllowList parameter specifies the applications that are allowed to access EWS or REST when the EwsApplicationAccessPolicy parameter is set to EwsAllowList. Other applications that aren't specified by this parameter aren't allowed to access EWS or REST. You identify the application by its user agent string value. Wildcard characters (\*) are supported.
 
@@ -2362,7 +2362,7 @@ Accept wildcard characters: False
 
 ### -EwsAllowMacOutlook
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The EwsAllowMacOutlook parameter enables or disables access to mailboxes by Outlook for Mac clients that use Exchange Web Services (for example, Outlook for Mac 2011 or later).
 
@@ -2380,7 +2380,7 @@ Accept wildcard characters: False
 
 ### -EwsAllowOutlook
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The EwsAllowOutlook parameter enables or disables access to mailboxes by Outlook clients that use Exchange Web Services. Outlook uses Exchange Web Services for free/busy, out-of-office settings, and calendar sharing.
 
@@ -2398,7 +2398,7 @@ Accept wildcard characters: False
 
 ### -EwsApplicationAccessPolicy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The EwsApplicationAccessPolicy parameter specifies the client applications that have access to EWS and REST. Valid values are:
 
@@ -2421,7 +2421,7 @@ Accept wildcard characters: False
 
 ### -EwsBlockList
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The EwsBlockList parameter specifies the applications that aren't allowed to access EWS or REST when the EwsApplicationAccessPolicy parameter is set to EnforceBlockList. All other applications that aren't specified by this parameter are allowed to access EWS or REST. You identify the application by its user agent string value. Wildcard characters (\*) are supported.
 
@@ -2443,7 +2443,7 @@ Accept wildcard characters: False
 
 ### -EwsEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The EwsEnabled parameter specifies whether to globally enable or disable EWS access for the entire organization, regardless of what application is making the request. Valid values are:
 
@@ -2664,7 +2664,7 @@ Accept wildcard characters: False
 
 ### -HierarchicalAddressBookRoot
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The HierarchicalAddressBookRoot parameter specifies the user, contact, or group to be used as the root organization for a hierarchical address book in the Exchange organization. You can use any value that uniquely identifies the recipient. For example:
 
@@ -2714,7 +2714,7 @@ Accept wildcard characters: False
 
 ### -Industry
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -2768,7 +2768,7 @@ Accept wildcard characters: False
 
 ### -IsAgendaMailEnabled
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is reserved for internal Microsoft use.
 
@@ -2786,7 +2786,7 @@ Accept wildcard characters: False
 
 ### -IsExcludedFromOffboardMigration
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -2806,7 +2806,7 @@ Accept wildcard characters: False
 
 ### -IsExcludedFromOnboardMigration
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -2826,7 +2826,7 @@ Accept wildcard characters: False
 
 ### -IsFfoMigrationInProgress
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -2909,7 +2909,7 @@ Accept wildcard characters: False
 
 ### -LeanPopoutEnabled
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The LeanPopoutEnabled parameter specifies whether to enable faster loading of pop-out messages in Outlook on the web for Internet Explorer and Microsoft Edge. Valid values are:
 
@@ -2935,7 +2935,7 @@ Accept wildcard characters: False
 
 ### -LinkPreviewEnabled
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The LinkPreviewEnabled parameter specifies whether link preview of URLs in email messages is allowed for the organization. Valid values are:
 
@@ -2956,7 +2956,7 @@ Accept wildcard characters: False
 
 ### -MailboxDataEncryptionEnabled
 
-> Applicable: Exchange Server 2019
+> Applicable: Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -2976,7 +2976,7 @@ Accept wildcard characters: False
 
 ### -MailTipsAllTipsEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MailTipsAllTipsEnabled parameter specifies whether MailTips are enabled. The default value is $true.
 
@@ -2994,7 +2994,7 @@ Accept wildcard characters: False
 
 ### -MailTipsExternalRecipientsTipsEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MailTipsExternalRecipientsTipsEnabled parameter specifies whether MailTips for external recipients are enabled. The default value is $false.
 
@@ -3012,7 +3012,7 @@ Accept wildcard characters: False
 
 ### -MailTipsGroupMetricsEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MailTipsGroupMetricsEnabled parameter specifies whether MailTips that rely on group metrics data are enabled. The default value is $true.
 
@@ -3030,7 +3030,7 @@ Accept wildcard characters: False
 
 ### -MailTipsLargeAudienceThreshold
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MailTipsLargeAudienceThreshold parameter specifies what a large audience is. The default value is 25.
 
@@ -3048,7 +3048,7 @@ Accept wildcard characters: False
 
 ### -MailTipsMailboxSourcedTipsEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MailTipsMailboxSourcedTipsEnabled parameter specifies whether MailTips that rely on mailbox data (out-of-office or full mailbox) are enabled.
 
@@ -3066,7 +3066,7 @@ Accept wildcard characters: False
 
 ### -ManagedFolderHomepage
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -3086,7 +3086,7 @@ Accept wildcard characters: False
 
 ### -MapiHttpEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -3151,7 +3151,7 @@ Accept wildcard characters: False
 
 ### -MaxConcurrentMigrations
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -3292,7 +3292,7 @@ Accept wildcard characters: False
 
 ### -MicrosoftExchangeRecipientEmailAddresses
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -3314,7 +3314,7 @@ Accept wildcard characters: False
 
 ### -MicrosoftExchangeRecipientEmailAddressPolicyEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -3336,7 +3336,7 @@ Accept wildcard characters: False
 
 ### -MicrosoftExchangeRecipientPrimarySmtpAddress
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -3360,7 +3360,7 @@ Accept wildcard characters: False
 
 ### -MicrosoftExchangeRecipientReplyRecipient
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -3387,7 +3387,7 @@ Accept wildcard characters: False
 
 ### -MitigationsEnabled
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -3435,7 +3435,7 @@ Accept wildcard characters: False
 
 ### -OabShadowDistributionOldestFileAgeLimit
 
-> Applicable: Exchange Server 2019
+> Applicable: Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -3455,7 +3455,7 @@ Accept wildcard characters: False
 
 ### -OAuth2ClientProfileEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The OAuth2ClientProfileEnabled parameter enables or disables modern authentication in the Exchange organization. Valid values are:
 
@@ -3506,7 +3506,7 @@ Accept wildcard characters: False
 
 ### -OrganizationSummary
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -3740,7 +3740,7 @@ Accept wildcard characters: False
 
 ### -PreferredInternetCodePageForShiftJis
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is reserved for internal Microsoft use.
 
@@ -3758,7 +3758,7 @@ Accept wildcard characters: False
 
 ### -PublicComputersDetectionEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The PublicComputersDetectionEnabled parameter specifies whether Outlook on the web detects when a user signs from a public or private computer or network, and then enforces the attachment handling settings from public networks. The default is $false. However, if you set this parameter to $true, Outlook on the web determines if the user is signing in from a public computer, and all public attachment handling rules are applied and enforced.
 
@@ -3796,7 +3796,7 @@ Accept wildcard characters: False
 
 ### -PublicFolderMailboxesLockedForNewConnections
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -3819,7 +3819,7 @@ Accept wildcard characters: False
 
 ### -PublicFolderMailboxesMigrationComplete
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -3842,7 +3842,7 @@ Accept wildcard characters: False
 
 ### -PublicFolderMigrationComplete
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -3862,7 +3862,7 @@ Accept wildcard characters: False
 
 ### -PublicFoldersEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The PublicFoldersEnabled parameter specifies how public folders are deployed in your organization. Valid values are:
 
@@ -3884,7 +3884,7 @@ Accept wildcard characters: False
 
 ### -PublicFolderShowClientControl
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The PublicFolderShowClientControl parameter enables or disables the control access feature for public folders in Microsoft Outlook. Valid values are:
 
@@ -3905,7 +3905,7 @@ Accept wildcard characters: False
 
 ### -PublicFoldersLockedForMigration
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -3925,7 +3925,7 @@ Accept wildcard characters: False
 
 ### -ReadTrackingEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ReadTrackingEnabled parameter specifies whether the tracking for read status for messages in an organization is enabled. The default value is $false.
 
@@ -3963,7 +3963,7 @@ Accept wildcard characters: False
 
 ### -RefreshSessionEnabled
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is reserved for internal Microsoft use.
 
@@ -4001,7 +4001,7 @@ Accept wildcard characters: False
 
 ### -RemotePublicFolderMailboxes
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RemotePublicFolderMailboxes parameter specifies the identities of the public folder objects (represented as mail user objects locally) corresponding to the public folder mailboxes created in the remote forest. The public folder values set here are used only if the public folder deployment is a remote deployment.
 
@@ -4019,7 +4019,7 @@ Accept wildcard characters: False
 
 ### -RequiredCharsetCoverage
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is reserved for internal Microsoft use.
 
@@ -4037,7 +4037,7 @@ Accept wildcard characters: False
 
 ### -SCLJunkThreshold
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -4102,7 +4102,7 @@ Accept wildcard characters: False
 
 ### -SiteMailboxCreationURL
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SiteMailboxCreationURL parameter specifies the URL that's used to create site mailboxes. Site mailboxes improve collaboration and user productivity by allowing access to both SharePoint documents and Exchange email in Outlook 2013 or later.
 
@@ -4120,7 +4120,7 @@ Accept wildcard characters: False
 
 ### -SmtpActionableMessagesEnabled
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SmtpActionableMessagesEnabled parameter specifies whether to enable or disable action buttons in email messages in Outlook on the web. Valid values are:
 
@@ -4190,7 +4190,7 @@ Accept wildcard characters: False
 
 ### -UMAvailableLanguages
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -4210,7 +4210,7 @@ Accept wildcard characters: False
 
 ### -UnblockUnsafeSenderPromptEnabled
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is reserved for internal Microsoft use.
 
@@ -4228,7 +4228,7 @@ Accept wildcard characters: False
 
 ### -UseIcsSyncStateStreaming
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -4295,7 +4295,7 @@ Accept wildcard characters: False
 
 ### -WACDiscoveryEndpoint
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -4363,7 +4363,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-OrganizationRelationship.md b/exchange/exchange-ps/ExchangePowerShell/Set-OrganizationRelationship.md
index 2e0b8862f8..34afdbd64c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-OrganizationRelationship.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-OrganizationRelationship.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
 Locale: en-US
@@ -74,7 +74,7 @@ This example disables the organization relationship with Contoso
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the organization relationship that you want to modify. You can use any value that uniquely identifies the organization relationship. For example:
 
@@ -96,7 +96,7 @@ Accept wildcard characters: False
 
 ### -ArchiveAccessEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ArchiveAccessEnabled parameter specifies whether the organization relationship is configured to provide remote archive access. Valid values are:
 
@@ -117,7 +117,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -138,7 +138,7 @@ Accept wildcard characters: False
 
 ### -DeliveryReportEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The DeliveryReportEnabled parameter specifies whether Delivery Reports should be shared over the organization relationship. Valid values are:
 
@@ -161,7 +161,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -181,7 +181,7 @@ Accept wildcard characters: False
 
 ### -DomainNames
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The DomainNames parameter specifies the SMTP domains of the external organization. You can specify multiple domains separated by commas (for example, "contoso.com","northamerica.contoso.com").
 
@@ -199,7 +199,7 @@ Accept wildcard characters: False
 
 ### -Enabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Enabled parameter specifies whether to enable the organization relationship. Valid values are:
 
@@ -220,7 +220,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -240,7 +240,7 @@ Accept wildcard characters: False
 
 ### -FreeBusyAccessEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The FreeBusyAccessEnabled parameter specifies whether the organization relationship should be used to retrieve free/busy information from the external organization. Valid values are:
 
@@ -263,7 +263,7 @@ Accept wildcard characters: False
 
 ### -FreeBusyAccessLevel
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The FreeBusyAccessLevel parameter specifies the maximum amount of detail returned to the requesting organization. Valid values are:
 
@@ -287,7 +287,7 @@ Accept wildcard characters: False
 
 ### -FreeBusyAccessScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The FreeBusyAccessScope parameter specifies a mail-enabled security group in the internal organization that contains users whose free/busy information is accessible by an external organization. You can use any value that uniquely identifies the group. For example:
 
@@ -339,7 +339,7 @@ Accept wildcard characters: False
 
 ### -MailboxMoveEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The MailboxMoveEnabled parameter specifies whether the organization relationship enables moving mailboxes to or from the external organization. Valid values are:
 
@@ -391,7 +391,7 @@ Accept wildcard characters: False
 
 ### -MailTipsAccessEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The MailTipsAccessEnabled parameter specifies whether MailTips for users in this organization are returned over this organization relationship. Valid values are:
 
@@ -414,7 +414,7 @@ Accept wildcard characters: False
 
 ### -MailTipsAccessLevel
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The MailTipsAccessLevel parameter specifies the level of MailTips data externally shared over this organization relationship. This parameter can have the following values:
 
@@ -438,7 +438,7 @@ Accept wildcard characters: False
 
 ### -MailTipsAccessScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The MailTipsAccessScope parameter specifies a mail-enabled security group in the internal organization that contains users whose free/busy information is accessible by an external organization. You can use any value that uniquely identifies the group. For example:
 
@@ -473,7 +473,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Name parameter specifies the unique name of the organization relationship. The maximum length is 64 characters.
 
@@ -511,7 +511,7 @@ Accept wildcard characters: False
 
 ### -OrganizationContact
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The OrganizationContact parameter specifies the email address that can be used to contact the external organization (for example, administrator@fourthcoffee.com).
 
@@ -529,7 +529,7 @@ Accept wildcard characters: False
 
 ### -PhotosEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The PhotosEnabled parameter specifies whether photos for users in the internal organization are returned over the organization relationship. Valid values are:
 
@@ -550,7 +550,7 @@ Accept wildcard characters: False
 
 ### -TargetApplicationUri
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The TargetApplicationUri parameter specifies the target Uniform Resource Identifier (URI) of the external organization. The TargetApplicationUri parameter is specified by Exchange when requesting a delegated token to retrieve free and busy information, for example, mail.contoso.com.
 
@@ -568,7 +568,7 @@ Accept wildcard characters: False
 
 ### -TargetAutodiscoverEpr
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The TargetAutodiscoverEpr parameter specifies the Autodiscover URL of Exchange Web Services for the external organization, for example, `https://contoso.com/autodiscover/autodiscover.svc/wssecurity`. Exchange uses Autodiscover to automatically detect the correct Exchange server endpoint to use for external requests.
 
@@ -586,7 +586,7 @@ Accept wildcard characters: False
 
 ### -TargetOwaURL
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The TargetOwaURL parameter specifies the Outlook on the web (formerly Outlook Web App) URL of the external organization that's defined in the organization relationship. It is used for Outlook on the web redirection in a cross-premise Exchange scenario. Configuring this attribute enables users in the organization to use their current Outlook on the web URL to access Outlook on the web in the external organization.
 
@@ -604,7 +604,7 @@ Accept wildcard characters: False
 
 ### -TargetSharingEpr
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The TargetSharingEpr parameter specifies the URL of the target Exchange Web Services for the external organization.
 
@@ -624,7 +624,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-OutlookAnywhere.md b/exchange/exchange-ps/ExchangePowerShell/Set-OutlookAnywhere.md
index ac591d7859..a4498d90ac 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-OutlookAnywhere.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-OutlookAnywhere.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -89,7 +89,7 @@ In Exchange 2010 and Exchange 2013, this example sets the available authenticati
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the Outlook Anywhere virtual directory that you want to modify. You can use any value that uniquely identifies the virtual directory. For example:
 
@@ -138,7 +138,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -159,7 +159,7 @@ Accept wildcard characters: False
 
 ### -DefaultAuthenticationMethod
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DefaultAuthenticationMethod parameter specifies the default authentication method for Outlook Anywhere. This parameter replaces the existing ExternalClientAuthenticationMethod, InternalClientAuthenticationMethod and IISAuthenticationMethods property values with the value you specify. Valid values are:
 
@@ -183,7 +183,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -201,7 +201,7 @@ Accept wildcard characters: False
 
 ### -ExtendedProtectionFlags
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExtendedProtectionFlags parameter specifies custom settings for Extended Protection for Authentication on the virtual directory. Valid values are:
 
@@ -225,7 +225,7 @@ Accept wildcard characters: False
 
 ### -ExtendedProtectionSPNList
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExtendedProtectionSPNList parameter specifies a list of valid Service Principal Names (SPNs) if you're using Extended Protection for Authentication on the virtual directory. Valid values are:
 
@@ -246,7 +246,7 @@ Accept wildcard characters: False
 
 ### -ExtendedProtectionTokenChecking
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExtendedProtectionTokenChecking parameter defines how you want to use Extended Protection for Authentication on the virtual directory. Extended Protection for Authentication isn't enabled by default. Valid values are:
 
@@ -270,7 +270,7 @@ Accept wildcard characters: False
 
 ### -ExternalClientAuthenticationMethod
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExternalClientAuthenticationMethod parameter specifies the authentication method that's used to authenticate external Outlook Anywhere clients. Valid values are:
 
@@ -294,7 +294,7 @@ Accept wildcard characters: False
 
 ### -ExternalClientsRequireSsl
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExternalClientsRequireSsl parameter specifies whether external Outlook Anywhere clients are required to use Secure Sockets Layer (SSL). Valid values are:
 
@@ -317,7 +317,7 @@ Accept wildcard characters: False
 
 ### -ExternalHostname
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExternalHostname parameter specifies the external hostname for the Outlook Anywhere virtual directory. For example, mail.contoso.com.
 
@@ -335,7 +335,7 @@ Accept wildcard characters: False
 
 ### -IISAuthenticationMethods
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IISAuthenticationMethods parameter specifies the authentication method that's used on the Outlook Anywhere virtual directory in IIS. Valid values are:
 
@@ -361,7 +361,7 @@ Accept wildcard characters: False
 
 ### -InternalClientAuthenticationMethod
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The InternalClientAuthenticationMethod parameter specifies the authentication method that's used to authenticate internal Outlook Anywhere clients. Valid values are:
 
@@ -385,7 +385,7 @@ Accept wildcard characters: False
 
 ### -InternalClientsRequireSsl
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The InternalClientsRequireSsl parameter specifies whether internal Outlook Anywhere clients are required to use SSL. Valid values are:
 
@@ -408,7 +408,7 @@ Accept wildcard characters: False
 
 ### -InternalHostname
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The InternalHostname parameter specifies the internal hostname for the Outlook Anywhere virtual directory. For example, mail.contoso.com.
 
@@ -426,7 +426,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Name parameter specifies the name of the Outlook Anywhere virtual directory. The default value is Rpc (Default Web Site). If the value you specify contains spaces, enclose the value in quotation marks (").
 
@@ -444,7 +444,7 @@ Accept wildcard characters: False
 
 ### -SSLOffloading
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SSLOffloading parameter specifies whether a network device accepts SSL connections and decrypts them before proxying the connections to the Outlook Anywhere virtual directory on the Exchange server. Valid values are:
 
@@ -471,7 +471,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-OutlookProtectionRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-OutlookProtectionRule.md
index e7bc6acefb..69da8ab7fc 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-OutlookProtectionRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-OutlookProtectionRule.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -66,7 +66,7 @@ This example sets the priority of the Outlook protection rule OPR-DG-Finance to
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the rule.
 
@@ -84,7 +84,7 @@ Accept wildcard characters: False
 
 ### -ApplyRightsProtectionTemplate
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ApplyRightsProtectionTemplate parameter specifies an RMS template to be applied to messages matching the conditions.
 
@@ -102,7 +102,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -123,7 +123,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -143,7 +143,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -163,7 +163,7 @@ Accept wildcard characters: False
 
 ### -FromDepartment
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The FromDepartment parameter specifies a department name. The rule is applied to messages where the sender's department attribute matches this value.
 
@@ -181,7 +181,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Name parameter specifies a name for the rule.
 
@@ -199,7 +199,7 @@ Accept wildcard characters: False
 
 ### -Priority
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Priority parameter specifies a priority for the Outlook protection rule. Rule priority values can range from 0 through n-1, where n is the total number of existing Outlook protection rules.
 
@@ -219,7 +219,7 @@ Accept wildcard characters: False
 
 ### -SentTo
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SentTo parameter specifies one or more recipients. External recipients can be specified using the SMTP address.
 
@@ -246,7 +246,7 @@ Accept wildcard characters: False
 
 ### -SentToScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SentToScope parameter specifies the scope of messages to which the rule applies. Valid values include:
 
@@ -269,7 +269,7 @@ Accept wildcard characters: False
 
 ### -UserCanOverride
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The UserCanOverride parameter specifies whether the Outlook user can override the rule behavior, either by using a different RMS template, or by removing rights protection before sending the message. Valid values include:
 
@@ -290,7 +290,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-OutlookProvider.md b/exchange/exchange-ps/ExchangePowerShell/Set-OutlookProvider.md
index aa50953b25..166c2ab25e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-OutlookProvider.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-OutlookProvider.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -53,7 +53,7 @@ This example changes the duration that the Autodiscover service settings are val
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the ADIDParameter value of the MAPI protocol for which you want to set global settings.
 
@@ -71,7 +71,7 @@ Accept wildcard characters: False
 
 ### -CertPrincipalName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The CertPrincipalName parameter specifies the Secure Sockets Layer (SSL) certificate principal name required for connecting to Exchange from an external location.
 
@@ -91,7 +91,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -112,7 +112,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -130,7 +130,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Name parameter specifies a common name for the Outlook Provider Configuration object. This can be a user-friendly name for identification.
 
@@ -148,7 +148,7 @@ Accept wildcard characters: False
 
 ### -OutlookProviderFlags
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The OutlookProviderFlags parameter specifies how Outlook clients should connect to the Exchange server. The value can be set to ServerExclusiveConnect, ExternalClientsRequireSSL, InternalClientsRequireSSL or to None to clear the flags. The recommended value is None, which is also the default setting.
 
@@ -166,7 +166,7 @@ Accept wildcard characters: False
 
 ### -RequiredClientVersions
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RequiredClientVersions parameter specifies the minimum version of Microsoft Outlook that's allowed to connect to the Exchange server. This information is in the Autodiscover response to the client connection request. This parameter uses the syntax `"MinimumVersion, ExpirationDate"`.
 
@@ -190,7 +190,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Mailbox server to use for Outlook Anywhere clients.
 
@@ -208,7 +208,7 @@ Accept wildcard characters: False
 
 ### -TTL
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TTL parameter specifies the duration (in hours) that the specified settings are valid.
 
@@ -228,7 +228,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 

From bf5782c8f6d20b2f37c7c821b53584098ab2cb47 Mon Sep 17 00:00:00 2001
From: Chris Davis <chris.davis@microsoft.com>
Date: Thu, 7 Aug 2025 15:43:15 -0700
Subject: [PATCH 135/145] Add Exchange Server SE 8

---
 .../Set-OwaMailboxPolicy.md                   | 176 +++++-----
 .../Set-OwaVirtualDirectory.md                | 228 ++++++------
 .../Set-PartnerApplication.md                 |  32 +-
 .../Set-PendingFederatedDomain.md             |  14 +-
 .../ExchangePowerShell/Set-PolicyTipConfig.md |  12 +-
 .../ExchangePowerShell/Set-PopSettings.md     |  64 ++--
 .../Set-PowerShellVirtualDirectory.md         |  28 +-
 .../ExchangePowerShell/Set-PublicFolder.md    |  36 +-
 .../Set-PublicFolderMigrationRequest.md       |  32 +-
 .../Set-PublicFolderMoveRequest.md            |  26 +-
 .../Set-ReceiveConnector.md                   | 116 +++---
 .../Set-RecipientFilterConfig.md              |  20 +-
 .../ExchangePowerShell/Set-RemoteDomain.md    |  56 +--
 .../ExchangePowerShell/Set-RemoteMailbox.md   | 122 +++----
 .../ExchangePowerShell/Set-ResourceConfig.md  |  10 +-
 .../ExchangePowerShell/Set-ResubmitRequest.md |  12 +-
 .../ExchangePowerShell/Set-RetentionPolicy.md |  20 +-
 .../Set-RetentionPolicyTag.md                 |  40 +--
 .../Set-RoleAssignmentPolicy.md               |  16 +-
 .../ExchangePowerShell/Set-RoleGroup.md       |  26 +-
 .../ExchangePowerShell/Set-RpcClientAccess.md |  18 +-
 .../Set-SearchDocumentFormat.md               |  12 +-
 .../ExchangePowerShell/Set-SendConnector.md   |  72 ++--
 .../Set-SenderFilterConfig.md                 |  26 +-
 .../ExchangePowerShell/Set-SenderIdConfig.md  |  22 +-
 .../Set-SenderReputationConfig.md             |  28 +-
 .../Set-ServerComponentState.md               |  22 +-
 .../ExchangePowerShell/Set-ServerMonitor.md   |  14 +-
 .../ExchangePowerShell/Set-SettingOverride.md |  22 +-
 .../ExchangePowerShell/Set-SharingPolicy.md   |  18 +-
 .../ExchangePowerShell/Set-SiteMailbox.md     |  28 +-
 .../Set-SiteMailboxProvisioningPolicy.md      |  24 +-
 .../ExchangePowerShell/Set-SmimeConfig.md     |  58 +--
 .../ExchangePowerShell/Set-SweepRule.md       |  34 +-
 .../ExchangePowerShell/Set-SystemMessage.md   |  16 +-
 .../Set-TextMessagingAccount.md               |  18 +-
 .../Set-ThrottlingPolicy.md                   | 248 ++++++-------
 .../Set-ThrottlingPolicyAssociation.md        |  12 +-
 .../ExchangePowerShell/Set-TransportAgent.md  |  14 +-
 .../ExchangePowerShell/Set-TransportConfig.md | 114 +++---
 .../ExchangePowerShell/Set-TransportRule.md   | 330 +++++++++---------
 .../ExchangePowerShell/Set-TransportServer.md | 192 +++++-----
 .../Set-TransportService.md                   | 280 +++++++--------
 .../ExchangePowerShell/Set-User.md            | 112 +++---
 .../ExchangePowerShell/Set-UserPhoto.md       |  26 +-
 .../Set-WebServicesVirtualDirectory.md        |  40 +--
 .../Set-X400AuthoritativeDomain.md            |  16 +-
 .../Start-ComplianceSearch.md                 |  12 +-
 .../Start-DatabaseAvailabilityGroup.md        |  16 +-
 .../Start-EdgeSynchronization.md              |  14 +-
 .../Start-MailboxAssistant.md                 |  16 +-
 .../ExchangePowerShell/Start-MailboxSearch.md |  16 +-
 .../Start-ManagedFolderAssistant.md           |  14 +-
 .../Start-MigrationBatch.md                   |  12 +-
 .../ExchangePowerShell/Start-MigrationUser.md |  10 +-
 .../Stop-ComplianceSearch.md                  |   8 +-
 .../Stop-DatabaseAvailabilityGroup.md         |  16 +-
 .../ExchangePowerShell/Stop-MailboxSearch.md  |  10 +-
 .../Stop-ManagedFolderAssistant.md            |  10 +-
 .../ExchangePowerShell/Stop-MigrationBatch.md |  10 +-
 60 files changed, 1535 insertions(+), 1531 deletions(-)

diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-OwaMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-OwaMailboxPolicy.md
index fa861191a0..164572be01 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-OwaMailboxPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-OwaMailboxPolicy.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.WebClient-Help.xml
 Locale: en-US
@@ -201,7 +201,7 @@ This example disables Outlook UserVoice for the default mailbox policy in Micros
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the Outlook on the web mailbox policy that you want to modify. You can use any value that uniquely identifies the policy. For example:
 
@@ -243,7 +243,7 @@ Accept wildcard characters: False
 
 ### -ActionForUnknownFileAndMIMETypes
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ActionForUnknownFileAndMIMETypes parameter specifies how to handle file types that aren't specified in the Allow, Block, and Force Save lists for file types and MIME types. Valid values are:
 
@@ -288,7 +288,7 @@ Accept wildcard characters: False
 
 ### -ActiveSyncIntegrationEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ActiveSyncIntegrationEnabled parameter specifies whether to enable or disable Exchange ActiveSync settings in Outlook on the web. Valid values are:
 
@@ -331,7 +331,7 @@ Accept wildcard characters: False
 
 ### -AllAddressListsEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllAddressListsEnabled parameter specifies which address lists are available in Outlook on the web. Valid values are:
 
@@ -352,7 +352,7 @@ Accept wildcard characters: False
 
 ### -AllowCopyContactsToDeviceAddressBook
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowCopyContactsToDeviceAddressBook parameter specifies whether users can copy the contents of their Contacts folder to a mobile device's native address book when using Outlook on the web for devices. Valid values are:
 
@@ -373,7 +373,7 @@ Accept wildcard characters: False
 
 ### -AllowedFileTypes
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowedFileTypes parameter specifies the attachment file types (file extensions) that can be saved locally or viewed from Outlook on the web. The default values are:
 
@@ -402,7 +402,7 @@ Accept wildcard characters: False
 
 ### -AllowedMimeTypes
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowedMimeTypes parameter specifies the MIME extensions of attachments that allow the attachments to be saved locally or viewed from Outlook on the web. The default values are:
 
@@ -454,7 +454,7 @@ Accept wildcard characters: False
 
 ### -AllowOfflineOn
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is functional only in on-premises Exchange.
 
@@ -500,7 +500,7 @@ Accept wildcard characters: False
 
 ### -BlockedFileTypes
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The BlockedFileTypes parameter specifies a list of attachment file types (file extensions) that can't be saved locally or viewed from Outlook on the web. The default values are:
 
@@ -529,7 +529,7 @@ Accept wildcard characters: False
 
 ### -BlockedMimeTypes
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The BlockedMimeTypes parameter specifies MIME extensions in attachments that prevent the attachments from being saved locally or viewed from Outlook on the web. The default values are:
 
@@ -605,7 +605,7 @@ Accept wildcard characters: False
 
 ### -BoxAttachmentsEnabled
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -625,7 +625,7 @@ Accept wildcard characters: False
 
 ### -CalendarEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is functional only in on-premises Exchange.
 
@@ -648,7 +648,7 @@ Accept wildcard characters: False
 
 ### -ChangePasswordEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is functional only in on-premises Exchange.
 
@@ -696,7 +696,7 @@ Accept wildcard characters: False
 
 ### -ClassicAttachmentsEnabled
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ClassicAttachmentsEnabled parameter specifies whether users can attach local files as regular email attachments in Outlook on the web. Valid values are:
 
@@ -745,7 +745,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -766,7 +766,7 @@ Accept wildcard characters: False
 
 ### -ContactsEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is functional only in on-premises Exchange.
 
@@ -789,7 +789,7 @@ Accept wildcard characters: False
 
 ### -DefaultClientLanguage
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is deprecated and no longer used.
 
@@ -807,7 +807,7 @@ Accept wildcard characters: False
 
 ### -DefaultTheme
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DefaultTheme parameter specifies the default theme that's used in Outlook on the web when the user hasn't selected a theme. The default value is blank ($null). For more information about the built-in themes that are available in Outlook on the web, see [Default Outlook on the web themes in Exchange](https://learn.microsoft.com/Exchange/clients/outlook-on-the-web/themes#default-outlook-on-the-web-themes-in-exchange-2016).
 
@@ -827,7 +827,7 @@ Accept wildcard characters: False
 
 ### -DelegateAccessEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is functional only in on-premises Exchange.
 
@@ -850,7 +850,7 @@ Accept wildcard characters: False
 
 ### -DirectFileAccessOnPrivateComputersEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DirectFileAccessOnPrivateComputersEnabled parameter specifies the left-click options for attachments in Outlook on the web for private computer sessions. Valid values are:
 
@@ -873,7 +873,7 @@ Accept wildcard characters: False
 
 ### -DirectFileAccessOnPublicComputersEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DirectFileAccessOnPublicComputersEnabled parameter specifies the left-click options for attachments in Outlook on the web for public computer sessions. Valid values are:
 
@@ -923,7 +923,7 @@ Accept wildcard characters: False
 
 ### -DisplayPhotosEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DisplayPhotosEnabled parameter specifies whether users see sender photos in Outlook on the web. Valid values are:
 
@@ -944,7 +944,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -964,7 +964,7 @@ Accept wildcard characters: False
 
 ### -DropboxAttachmentsEnabled
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1004,7 +1004,7 @@ Accept wildcard characters: False
 
 ### -ExplicitLogonEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is functional only in on-premises Exchange.
 
@@ -1050,7 +1050,7 @@ Accept wildcard characters: False
 
 ### -ExternalSPMySiteHostURL
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ExternalSPMySiteHostURL specifies the My Site Host URL for external users (for example, `https://sp01.contoso.com`).
 
@@ -1095,7 +1095,7 @@ Accept wildcard characters: False
 
 ### -ForceSaveAttachmentFilteringEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ForceSaveAttachmentFilteringEnabled parameter specifies whether files are filtered before they can be saved from Outlook on the web. Valid values are:
 
@@ -1116,7 +1116,7 @@ Accept wildcard characters: False
 
 ### -ForceSaveFileTypes
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ForceSaveFileTypes parameter specifies the attachment file types (file extensions) that can only be saved from Outlook on the web (not opened). The default values are:
 
@@ -1145,7 +1145,7 @@ Accept wildcard characters: False
 
 ### -ForceSaveMimeTypes
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ForceSaveMimeTypes parameter specifies the MIME extensions in attachments that only allow the attachments to be saved locally (not opened). The default values are:
 
@@ -1178,7 +1178,7 @@ Accept wildcard characters: False
 
 ### -ForceWacViewingFirstOnPrivateComputers
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ForceWacViewingFirstOnPrivateComputers parameter specifies whether private computers must first preview an Office file as a web page in Office Online Server (formerly known as Office Web Apps Server and Web Access Companion Server) before opening the file in the local application. Valid values are:
 
@@ -1201,7 +1201,7 @@ Accept wildcard characters: False
 
 ### -ForceWacViewingFirstOnPublicComputers
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ForceWacViewingFirstOnPublicComputers parameter specifies whether public computers must first preview an Office file as a web page in Office Online Server before opening the file in the local application. Valid values are:
 
@@ -1274,7 +1274,7 @@ Accept wildcard characters: False
 
 ### -FreCardsEnabled
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is functional only in on-premises Exchange.
 
@@ -1294,7 +1294,7 @@ Accept wildcard characters: False
 
 ### -GlobalAddressListEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The GlobalAddressListEnabled parameter specifies whether the global address list is available in Outlook on the web. Valid values are:
 
@@ -1315,7 +1315,7 @@ Accept wildcard characters: False
 
 ### -GoogleDriveAttachmentsEnabled
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1335,7 +1335,7 @@ Accept wildcard characters: False
 
 ### -GroupCreationEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is functional only in the cloud-based service.
 
@@ -1381,7 +1381,7 @@ Accept wildcard characters: False
 
 ### -InstantMessagingEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The InstantMessagingEnabled parameter specifies whether instant messaging is available in Outlook on the web. This does not affect chat capabilities provided by Skype for Business or Teams. Valid values are:
 
@@ -1402,7 +1402,7 @@ Accept wildcard characters: False
 
 ### -InstantMessagingType
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The InstantMessagingType parameter specifies the type of instant messaging provider in Outlook on the web. Valid values are:
 
@@ -1446,7 +1446,7 @@ Accept wildcard characters: False
 
 ### -InternalSPMySiteHostURL
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The InternalSPMySiteHostURL specifies the My Site Host URL for internal users (for example, `https://sp01.contoso.com`).
 
@@ -1466,7 +1466,7 @@ Accept wildcard characters: False
 
 ### -IRMEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IRMEnabled parameter specifies whether Information Rights Management (IRM) features are available in Outlook on the web. Valid values are:
 
@@ -1487,7 +1487,7 @@ Accept wildcard characters: False
 
 ### -IsDefault
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IsDefault switch specifies whether the Outlook on the web policy is the default policy that's used to configure the Outlook on the web settings for new mailboxes. You don't need to specify a value with this switch.
 
@@ -1534,7 +1534,7 @@ Accept wildcard characters: False
 
 ### -JournalEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The JournalEnabled parameter specifies whether the Journal folder is available in Outlook on the web. Valid values are:
 
@@ -1555,7 +1555,7 @@ Accept wildcard characters: False
 
 ### -JunkEmailEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1621,7 +1621,7 @@ Accept wildcard characters: False
 
 ### -LogonAndErrorLanguage
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The LogonAndErrorLanguage parameter specifies the language that used in Outlook on the web for forms-based authentication and for error messages when a user's current language setting can't be read.
 
@@ -1683,7 +1683,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Name parameter specifies the unique name for the policy. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks.
 
@@ -1701,7 +1701,7 @@ Accept wildcard characters: False
 
 ### -NotesEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The NotesEnabled parameter specifies whether the Notes folder is available in Outlook on the web. Valid values are:
 
@@ -1795,7 +1795,7 @@ Accept wildcard characters: False
 
 ### -OneDriveAttachmentsEnabled
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is deprecated and no longer used.
 
@@ -1837,7 +1837,7 @@ Accept wildcard characters: False
 
 ### -OnSendAddinsEnabled
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The OnSendAddinsEnabled parameter specifies whether a mail item can be edited while an on-send add-in is processing it in Outlook on the web or the new Outlook on Windows. Valid values are:
 
@@ -1858,7 +1858,7 @@ Accept wildcard characters: False
 
 ### -OrganizationEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 When the OrganizationEnabled parameter is set to $false, the Automatic Reply option doesn't include external and internal options, the address book doesn't show the organization hierarchy, and the Resources tab in Calendar forms is disabled. The default value is $true.
 
@@ -1876,7 +1876,7 @@ Accept wildcard characters: False
 
 ### -OutboundCharset
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The OutboundCharset parameter specifies the character set that's used for outgoing messages in Outlook on the web. Valid values are:
 
@@ -2025,7 +2025,7 @@ Accept wildcard characters: False
 
 ### -OWALightEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The OWALightEnabled parameter controls the availability of the light version of Outlook on the web. Valid values are:
 
@@ -2115,7 +2115,7 @@ Accept wildcard characters: False
 
 ### -PhoneticSupportEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The PhoneticSupportEnabled parameter specifies phonetically spelled entries in the address book. This parameter is available for use in Japan.
 
@@ -2156,7 +2156,7 @@ Accept wildcard characters: False
 
 ### -PremiumClientEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The PremiumClientEnabled parameter controls the availability of the full version of Outlook Web App. Valid values are:
 
@@ -2225,7 +2225,7 @@ Accept wildcard characters: False
 
 ### -PublicFoldersEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is functional only in Exchange Server 2010.
 
@@ -2248,7 +2248,7 @@ Accept wildcard characters: False
 
 ### -RecoverDeletedItemsEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is functional only in Exchange Server 2010.
 
@@ -2271,7 +2271,7 @@ Accept wildcard characters: False
 
 ### -ReferenceAttachmentsEnabled
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ReferenceAttachmentsEnabled parameter specifies whether users can attach files from the cloud as linked attachments in Outlook on the web. Valid values are:
 
@@ -2292,7 +2292,7 @@ Accept wildcard characters: False
 
 ### -RemindersAndNotificationsEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RemindersAndNotificationsEnabled parameter specifies whether notifications and reminders are enabled in Outlook on the web. Valid values are:
 
@@ -2315,7 +2315,7 @@ Accept wildcard characters: False
 
 ### -ReportJunkEmailEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 **Note**: In Exchange Online, this parameter does not affect the ability of users to report messages. Whether a user is able to report messages and where is controlled in the Microsoft Defender portal as described in [User reported message settings](https://learn.microsoft.com/defender-office-365/submissions-user-reported-messages-custom-mailbox).
 
@@ -2340,7 +2340,7 @@ Accept wildcard characters: False
 
 ### -RulesEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RulesEnabled parameter specifies whether a user can view, create, or modify server-side rules in Outlook on the web. Valid values are:
 
@@ -2361,7 +2361,7 @@ Accept wildcard characters: False
 
 ### -SatisfactionEnabled
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SatisfactionEnabled parameter specifies whether to enable or disable the satisfaction survey. Valid values are:
 
@@ -2382,7 +2382,7 @@ Accept wildcard characters: False
 
 ### -SaveAttachmentsToCloudEnabled
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SaveAttachmentsToCloudEnabled parameter specifies whether users can save regular email attachments to the cloud. Valid values are:
 
@@ -2403,7 +2403,7 @@ Accept wildcard characters: False
 
 ### -SearchFoldersEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SearchFoldersEnabled parameter specifies whether Search Folders are available in Outlook on the web. Valid values are:
 
@@ -2424,7 +2424,7 @@ Accept wildcard characters: False
 
 ### -SetPhotoEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SetPhotoEnabled parameter specifies whether users can add, change, and remove their sender photo in Outlook on the web. Valid values are:
 
@@ -2447,7 +2447,7 @@ Accept wildcard characters: False
 
 ### -SetPhotoURL
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SetPhotoURL parameter controls where users go to select their photo. You can't specify a URL that contains one or more picture files, as there's no mechanism to copy a URL photo to the properties of Exchange Online mailboxes.
 
@@ -2485,7 +2485,7 @@ Accept wildcard characters: False
 
 ### -SignaturesEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SignaturesEnabled parameter specifies whether to enable or disable the use of signatures in Outlook on the web. Valid values are:
 
@@ -2506,7 +2506,7 @@ Accept wildcard characters: False
 
 ### -SilverlightEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is functional only in Exchange Server 2010.
 
@@ -2529,7 +2529,7 @@ Accept wildcard characters: False
 
 ### -SkipCreateUnifiedGroupCustomSharepointClassification
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is functional only in the cloud-based service.
 
@@ -2552,7 +2552,7 @@ Accept wildcard characters: False
 
 ### -SMimeEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is functional only in Exchange Server 2010.
 
@@ -2597,7 +2597,7 @@ Accept wildcard characters: False
 
 ### -SpellCheckerEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is functional only in Exchange Server 2010.
 
@@ -2622,7 +2622,7 @@ Accept wildcard characters: False
 
 ### -TasksEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is functional only in on-premises Exchange.
 
@@ -2670,7 +2670,7 @@ Accept wildcard characters: False
 
 ### -TextMessagingEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The TextMessagingEnabled parameter specifies whether users can send and receive text messages in Outlook on the web. Valid values are:
 
@@ -2693,7 +2693,7 @@ Accept wildcard characters: False
 
 ### -ThemeSelectionEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ThemeSelectionEnabled parameter specifies whether users can change the theme in Outlook on the web. Valid values are:
 
@@ -2714,7 +2714,7 @@ Accept wildcard characters: False
 
 ### -ThirdPartyAttachmentsEnabled
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -2734,7 +2734,7 @@ Accept wildcard characters: False
 
 ### -UMIntegrationEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The UMIntegrationEnabled parameter specifies whether Unified Messaging (UM) integration is enabled in Outlook on the web. Valid values are:
 
@@ -2759,7 +2759,7 @@ Accept wildcard characters: False
 
 ### -UNCAccessOnPrivateComputersEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -2779,7 +2779,7 @@ Accept wildcard characters: False
 
 ### -UNCAccessOnPublicComputersEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -2799,7 +2799,7 @@ Accept wildcard characters: False
 
 ### -UseGB18030
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The UseGB18030 parameter specifies whether to use the GB18030 character set instead of GB2312 in Outlook on the web. Valid values are:
 
@@ -2820,7 +2820,7 @@ Accept wildcard characters: False
 
 ### -UseISO885915
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The UseISO885915 parameter specifies whether to use the character set ISO8859-15 instead of ISO8859-1 in Outlook on the web. Valid values are:
 
@@ -2841,7 +2841,7 @@ Accept wildcard characters: False
 
 ### -UserVoiceEnabled
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is functional only in the cloud-based service.
 
@@ -2864,7 +2864,7 @@ Accept wildcard characters: False
 
 ### -WacEditingEnabled
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WacEditingEnabled parameter specifies whether to enable or disable editing documents in Outlook on the web by using Office Online Server (formerly known as Office Web Apps Server and Web Access Companion Server). Valid values are:
 
@@ -2885,7 +2885,7 @@ Accept wildcard characters: False
 
 ### -WacExternalServicesEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WacExternalServicesEnabled parameter specifies whether to enable or disable external services when viewing documents in Outlook on the web (for example, machine translation) by using Office Online Server. Valid values are:
 
@@ -2906,7 +2906,7 @@ Accept wildcard characters: False
 
 ### -WacOMEXEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WacOMEXEnabled parameter specifies whether to enable or disable apps for Outlook in Outlook on the web in Office Online Server. Valid values are:
 
@@ -2927,7 +2927,7 @@ Accept wildcard characters: False
 
 ### -WacViewingOnPrivateComputersEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WacViewingOnPrivateComputersEnabled parameter specifies whether to enable or disable web viewing of supported Office documents private computer sessions in Office Online Server (formerly known as Office Web Apps Server and Web Access Companion Server). By default, all Outlook on the web sessions are considered to be on private computers. Valid values are:
 
@@ -2950,7 +2950,7 @@ Accept wildcard characters: False
 
 ### -WacViewingOnPublicComputersEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WacViewingOnPublicComputersEnabled parameter specifies whether to enable or disable web viewing of supported Office documents in public computer sessions in Office Online Server. Valid values are:
 
@@ -2996,7 +2996,7 @@ Accept wildcard characters: False
 
 ### -WebPartsFrameOptionsType
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WebPartsFrameOptionsType parameter specifies what sources can access web parts in IFRAME or FRAME elements in Outlook on the web. Valid values are:
 
@@ -3208,7 +3208,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
@@ -3225,7 +3225,7 @@ Accept wildcard characters: False
 ```
 
 ### -WSSAccessOnPrivateComputersEnabled
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is deprecated and no longer used.
 
@@ -3243,7 +3243,7 @@ Accept wildcard characters: False
 
 ### -WSSAccessOnPublicComputersEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is deprecated and no longer used.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-OwaVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Set-OwaVirtualDirectory.md
index f60879da83..921ca5f56c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-OwaVirtualDirectory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-OwaVirtualDirectory.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.WebClient-Help.xml
 Locale: en-US
@@ -184,7 +184,7 @@ This example sets the ActionForUnknownFileAndMIMETypes parameter to Block on the
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the OWA virtual directory that you want to modify. You can use any value that uniquely identifies the virtual directory. For example:
 
@@ -208,7 +208,7 @@ Accept wildcard characters: False
 
 ### -ActionForUnknownFileAndMIMETypes
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ActionForUnknownFileAndMIMETypes parameter specifies how to handle file types that aren't specified in the Allow, Block, and Force Save lists for file types and MIME types. Valid values are:
 
@@ -230,7 +230,7 @@ Accept wildcard characters: False
 
 ### -ActiveSyncIntegrationEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ActiveSyncIntegrationEnabled parameter specifies whether to enable or disable Exchange ActiveSync settings in Outlook on the web. Valid values are:
 
@@ -251,7 +251,7 @@ Accept wildcard characters: False
 
 ### -AdfsAuthentication
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AdfsAuthentication parameter enables or disables Active Directory Federation Services (ADFS) authentication on the Outlook on the web virtual directory. Valid values are:
 
@@ -272,7 +272,7 @@ Accept wildcard characters: False
 
 ### -AllAddressListsEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AllAddressListsEnabled parameter specifies which address lists are available in Outlook on the web. Valid values are:
 
@@ -293,7 +293,7 @@ Accept wildcard characters: False
 
 ### -AllowCopyContactsToDeviceAddressBook
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AllowCopyContactsToDeviceAddressBook parameter specifies whether users can copy the contents of their Contacts folder to a mobile device's native address book when using Outlook on the web for devices. Valid values are:
 
@@ -314,7 +314,7 @@ Accept wildcard characters: False
 
 ### -AllowedFileTypes
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AllowedFileTypes parameter specifies the attachment file types (file extensions) that can be saved locally or viewed from Outlook on the web. The default values are:
 
@@ -343,7 +343,7 @@ Accept wildcard characters: False
 
 ### -AllowedMimeTypes
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AllowedMimeTypes parameter specifies the MIME extensions of attachments that allow the attachments to be saved locally or viewed from Outlook on the web. The default values are:
 
@@ -375,7 +375,7 @@ Accept wildcard characters: False
 
 ### -AllowOfflineOn
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AllowOfflineOn parameter specifies when Outlook on the web in offline mode is available for supported web browsers. Valid values are:
 
@@ -399,7 +399,7 @@ Accept wildcard characters: False
 
 ### -AnonymousFeaturesEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AnonymousFeaturesEnabled parameter specifies whether you want to allow Outlook on the web users that are logged on anonymously to access specific features. Valid values are:
 
@@ -420,7 +420,7 @@ Accept wildcard characters: False
 
 ### -BasicAuthentication
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The BasicAuthentication parameter specifies whether Basic authentication is enabled on the virtual directory. Valid values are:
 
@@ -443,7 +443,7 @@ Accept wildcard characters: False
 
 ### -BlockedFileTypes
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The BlockedFileTypes parameter specifies a list of attachment file types (file extensions) that can't be saved locally or viewed from Outlook on the web. The default values are:
 
@@ -472,7 +472,7 @@ Accept wildcard characters: False
 
 ### -BlockedMimeTypes
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The BlockedMimeTypes parameter specifies MIME extensions in attachments that prevent the attachments from being saved locally or viewed from Outlook on the web. The default values are:
 
@@ -508,7 +508,7 @@ Accept wildcard characters: False
 
 ### -BoxAttachmentsEnabled
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -526,7 +526,7 @@ Accept wildcard characters: False
 
 ### -CalendarEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The CalendarEnabled parameter specifies whether to enable or disable the calendar in Outlook on the web. Valid values are:
 
@@ -570,7 +570,7 @@ Accept wildcard characters: False
 
 ### -ChangePasswordEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ChangePasswordEnabled parameter specifies whether users can change their passwords from inside Outlook on the web. Valid values are:
 
@@ -591,7 +591,7 @@ Accept wildcard characters: False
 
 ### -ClassicAttachmentsEnabled
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ClassicAttachmentsEnabled parameter specifies whether users can attach local files as regular email attachments in Outlook on the web. Valid values are:
 
@@ -612,7 +612,7 @@ Accept wildcard characters: False
 
 ### -ClientAuthCleanupLevel
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ClientAuthCleanupLevel parameter specifies how much of the cache is cleared when the user logs off from Outlook on the web. Valid values are:
 
@@ -635,7 +635,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -656,7 +656,7 @@ Accept wildcard characters: False
 
 ### -ContactsEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ContactsEnabled parameter specifies whether to enable or disable Contacts in Outlook on the web. Valid values are:
 
@@ -702,7 +702,7 @@ Accept wildcard characters: False
 
 ### -DefaultClientLanguage
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is deprecated and no longer used.
 
@@ -720,7 +720,7 @@ Accept wildcard characters: False
 
 ### -DefaultDomain
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DefaultDomain parameter specifies which domain to use when the LogonFormat parameter is set to UserName (for example, contoso.com).
 
@@ -738,7 +738,7 @@ Accept wildcard characters: False
 
 ### -DefaultTheme
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DefaultTheme parameter specifies the default theme that's used in Outlook on the web when the user hasn't selected a theme. The default value is blank ($null). For more information about the built-in themes that are available in Outlook on the web, see [Default Outlook on the web themes in Exchange](https://learn.microsoft.com/Exchange/clients/outlook-on-the-web/themes#default-outlook-on-the-web-themes-in-exchange-2016).
 
@@ -758,7 +758,7 @@ Accept wildcard characters: False
 
 ### -DelegateAccessEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is functional only in Exchange Server 2010.
 
@@ -781,7 +781,7 @@ Accept wildcard characters: False
 
 ### -DigestAuthentication
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DigestAuthentication parameter specifies whether Digest authentication is enabled on the virtual directory. Valid values are:
 
@@ -804,7 +804,7 @@ Accept wildcard characters: False
 
 ### -DirectFileAccessOnPrivateComputersEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DirectFileAccessOnPrivateComputersEnabled parameter specifies the left-click options for attachments in Outlook on the web for private computer sessions. Valid values are:
 
@@ -827,7 +827,7 @@ Accept wildcard characters: False
 
 ### -DirectFileAccessOnPublicComputersEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DirectFileAccessOnPrivateComputersEnabled parameter specifies the left-click options for attachments in Outlook on the web for public computer sessions. Valid values are:
 
@@ -850,7 +850,7 @@ Accept wildcard characters: False
 
 ### -DisplayPhotosEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DisplayPhotosEnabled parameter specifies whether users see sender photos in Outlook on the web. Valid values are:
 
@@ -871,7 +871,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -889,7 +889,7 @@ Accept wildcard characters: False
 
 ### -DropboxAttachmentsEnabled
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -907,7 +907,7 @@ Accept wildcard characters: False
 
 ### -Exchange2003Url
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is functional only in Exchange Server 2010.
 
@@ -927,7 +927,7 @@ Accept wildcard characters: False
 
 ### -ExchwebProxyDestination
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is deprecated and no longer used.
 
@@ -945,7 +945,7 @@ Accept wildcard characters: False
 
 ### -ExplicitLogonEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExplicitLogonEnabled parameter specifies whether to allow a user to open someone else's mailbox in Outlook on the web (provided that user has permissions to the mailbox). Valid values are:
 
@@ -966,7 +966,7 @@ Accept wildcard characters: False
 
 ### -ExtendedProtectionFlags
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExtendedProtectionFlags parameter specifies custom settings for Extended Protection for Authentication on the virtual directory. Valid values are:
 
@@ -994,7 +994,7 @@ Accept wildcard characters: False
 
 ### -ExtendedProtectionSPNList
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExtendedProtectionSPNList parameter specifies a list of valid Service Principal Names (SPNs) if you're using Extended Protection for Authentication on the virtual directory. Valid values are:
 
@@ -1019,7 +1019,7 @@ Accept wildcard characters: False
 
 ### -ExtendedProtectionTokenChecking
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExtendedProtectionTokenChecking parameter defines how you want to use Extended Protection for Authentication on the virtual directory. Extended Protection for Authentication isn't enabled by default. Valid values are:
 
@@ -1043,7 +1043,7 @@ Accept wildcard characters: False
 
 ### -ExternalAuthenticationMethods
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExternalAuthenticationMethods parameter restricts the authentication methods that can be used to connect to the virtual directory from outside the firewall. Valid values are:
 
@@ -1084,7 +1084,7 @@ Accept wildcard characters: False
 
 ### -ExternalDownloadHostName
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExternalDownloadHostName parameter specifies the download location for files in Outlook on the web for external users (for example, in-line image files).
 
@@ -1102,7 +1102,7 @@ Accept wildcard characters: False
 
 ### -ExternalSPMySiteHostURL
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExternalSPMySiteHostURL specifies the My Site Host URL for external users (for example, `https://sp01.contoso.com`).
 
@@ -1122,7 +1122,7 @@ Accept wildcard characters: False
 
 ### -ExternalUrl
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExternalURL parameter specifies the URL that's used to connect to the virtual directory from outside the firewall.
 
@@ -1142,7 +1142,7 @@ Accept wildcard characters: False
 
 ### -FailbackUrl
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The FailbackUrl parameter specifies the URL that Outlook on the web uses to connect to the server after failback in a site resilience process and requires a separate DNS entry pointing to the original server's IP address.
 
@@ -1162,7 +1162,7 @@ Accept wildcard characters: False
 
 ### -FilterWebBeaconsAndHtmlForms
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The FilterWebBeaconsAndHtmlForms parameter specifies how web beacons are handled in Outlook on the web. Valid values are:
 
@@ -1184,7 +1184,7 @@ Accept wildcard characters: False
 
 ### -ForceSaveAttachmentFilteringEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ForceSaveAttachmentFilteringEnabled parameter specifies whether files are filtered before they can be saved from Outlook on the web. Valid values are:
 
@@ -1205,7 +1205,7 @@ Accept wildcard characters: False
 
 ### -ForceSaveFileTypes
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ForceSaveFileTypes parameter specifies the attachment file types (file extensions) that can only be saved from Outlook on the web (not opened). The default values are:
 
@@ -1234,7 +1234,7 @@ Accept wildcard characters: False
 
 ### -ForceSaveMimeTypes
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ForceSaveMimeTypes parameter specifies the MIME extensions in attachments that only allow the attachments to be saved locally (not opened). The default values are:
 
@@ -1267,7 +1267,7 @@ Accept wildcard characters: False
 
 ### -ForceWacViewingFirstOnPrivateComputers
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ForceWacViewingFirstOnPrivateComputers parameter specifies whether private computers must first preview an Office file as a web page in Office Online Server (formerly known as Office Web Apps Server and Web Access Companion Server) before opening the file in the local application. Valid values are:
 
@@ -1290,7 +1290,7 @@ Accept wildcard characters: False
 
 ### -ForceWacViewingFirstOnPublicComputers
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ForceWacViewingFirstOnPublicComputers parameter specifies whether public computers must first preview an Office file as a web page in Office Online Server before opening the file in the local application. Valid values are:
 
@@ -1363,7 +1363,7 @@ Accept wildcard characters: False
 
 ### -FormsAuthentication
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The FormsAuthentication parameter enables or disables forms-based authentication on the Outlook on the web virtual directory. Valid values are:
 
@@ -1384,7 +1384,7 @@ Accept wildcard characters: False
 
 ### -FreCardsEnabled
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -1402,7 +1402,7 @@ Accept wildcard characters: False
 
 ### -GlobalAddressListEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The GlobalAddressListEnabled parameter specifies whether the global address list is available in Outlook on the web. Valid values are:
 
@@ -1423,7 +1423,7 @@ Accept wildcard characters: False
 
 ### -GoogleDriveAttachmentsEnabled
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -1441,7 +1441,7 @@ Accept wildcard characters: False
 
 ### -GzipLevel
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The GzipLevel parameter sets Gzip configuration information for the Outlook on the web virtual directory. Valid values are:
 
@@ -1464,7 +1464,7 @@ Accept wildcard characters: False
 
 ### -InstantMessagingCertificateThumbprint
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The InstantMessagingCertificateThumbprint parameter specifies the trusted certificate used to communicate between the instant messaging server and the Mailbox server. Use the Get-ExchangeCertificate cmdlet to find the thumbprint of the certificate.
 
@@ -1482,7 +1482,7 @@ Accept wildcard characters: False
 
 ### -InstantMessagingEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The InstantMessagingEnabled parameter specifies whether instant messaging is available in Outlook on the web. This does not affect chat capabilities provided by Skype for Business or Teams. Valid values are:
 
@@ -1503,7 +1503,7 @@ Accept wildcard characters: False
 
 ### -InstantMessagingServerName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The InstantMessagingServerName parameter specifies the fully qualified domain name (FQDN) of the instant messaging server or set of servers behind a load balancing device.
 
@@ -1521,7 +1521,7 @@ Accept wildcard characters: False
 
 ### -InstantMessagingType
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The InstantMessagingType parameter specifies the type of instant messaging provider in Outlook on the web. Valid values are:
 
@@ -1542,7 +1542,7 @@ Accept wildcard characters: False
 
 ### -IntegratedFeaturesEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IntegratedFeaturesEnabled parameter specifies whether to allow Outlook on the web users who are logged on using Integrated Windows authentication to access specific features. Valid values are:
 
@@ -1563,7 +1563,7 @@ Accept wildcard characters: False
 
 ### -InternalDownloadHostName
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The InternalDownloadHostName parameter specifies the download location for files in Outlook on the web for internal users (for example, in-line image files). The default value is blank ($null).
 
@@ -1581,7 +1581,7 @@ Accept wildcard characters: False
 
 ### -InternalSPMySiteHostURL
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The InternalSPMySiteHostURL specifies the My Site Host URL for internal users (for example, `https://sp01.contoso.com`).
 
@@ -1601,7 +1601,7 @@ Accept wildcard characters: False
 
 ### -InternalUrl
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The InternalURL parameter specifies the URL that's used to connect to the virtual directory from inside the firewall.
 
@@ -1621,7 +1621,7 @@ Accept wildcard characters: False
 
 ### -IRMEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IRMEnabled parameter specifies whether Information Rights Management (IRM) features are available in Outlook on the web. Valid values are:
 
@@ -1642,7 +1642,7 @@ Accept wildcard characters: False
 
 ### -IsPublic
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IsPublic parameter specifies whether external users use the virtual directory for Outlook on the web in multiple virtual directory environments (you've configured separate virtual directories on the same server for internal vs. external Outlook on the web connections). Valid values are:
 
@@ -1663,7 +1663,7 @@ Accept wildcard characters: False
 
 ### -JournalEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The JournalEnabled parameter specifies whether the Journal folder is available in Outlook on the web. Valid values are:
 
@@ -1684,7 +1684,7 @@ Accept wildcard characters: False
 
 ### -JunkEmailEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The JunkEmailEnabled parameter specifies whether the Junk Email folder and junk email management are available in Outlook on the web. Valid values are:
 
@@ -1728,7 +1728,7 @@ Accept wildcard characters: False
 
 ### -LogonAndErrorLanguage
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The LogonAndErrorLanguage parameter specifies the language that used in Outlook on the web for forms-based authentication and for error messages when a user's current language setting can't be read.
 
@@ -1750,7 +1750,7 @@ Accept wildcard characters: False
 
 ### -LogonFormat
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The LogonFormat parameter specifies the type of logon format that's required for forms-based authentication on the Outlook on the web sign-in page. Valid values are:
 
@@ -1772,7 +1772,7 @@ Accept wildcard characters: False
 
 ### -LogonPageLightSelectionEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The LogonPageLightSelectionEnabled parameter specifies whether the Outlook on the web sign-in page includes the option to sign in to the light version of Outlook on the web. Valid values are:
 
@@ -1795,7 +1795,7 @@ Accept wildcard characters: False
 
 ### -LogonPagePublicPrivateSelectionEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The LogonPagePublicPrivateSelectionEnabled parameter specifies whether the Outlook on the web sign-in page includes the public/private computer session option at sign-in. Valid values are:
 
@@ -1820,7 +1820,7 @@ Accept wildcard characters: False
 
 ### -NotesEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The NotesEnabled parameter specifies whether the Notes folder is available in Outlook on the web. Valid values are:
 
@@ -1841,7 +1841,7 @@ Accept wildcard characters: False
 
 ### -NotificationInterval
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is functional only in Exchange Server 2010.
 
@@ -1865,7 +1865,7 @@ Accept wildcard characters: False
 
 ### -OAuthAuthentication
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -1883,7 +1883,7 @@ Accept wildcard characters: False
 
 ### -OneDriveAttachmentsEnabled
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -1901,7 +1901,7 @@ Accept wildcard characters: False
 
 ### -OrganizationEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 When the OrganizationEnabled parameter is set to $false, the Automatic Reply option doesn't include external and internal options, the address book doesn't show the organization hierarchy, and the Resources tab in Calendar forms is disabled. The default value is $true.
 
@@ -1919,7 +1919,7 @@ Accept wildcard characters: False
 
 ### -OutboundCharset
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The OutboundCharset parameter specifies the character set that's used for outgoing messages in Outlook on the web. Valid values are:
 
@@ -1941,7 +1941,7 @@ Accept wildcard characters: False
 
 ### -OWALightEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The OWALightEnabled parameter controls the availability of the light version of Outlook on the web. Valid values are:
 
@@ -1985,7 +1985,7 @@ Accept wildcard characters: False
 
 ### -PremiumClientEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PremiumClientEnabled parameter controls the availability of the full version of Outlook Web App. Valid values are:
 
@@ -2006,7 +2006,7 @@ Accept wildcard characters: False
 
 ### -PublicFoldersEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is functional only in Exchange Server 2010.
 
@@ -2029,7 +2029,7 @@ Accept wildcard characters: False
 
 ### -RecoverDeletedItemsEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is functional only in Exchange Server 2010.
 
@@ -2052,7 +2052,7 @@ Accept wildcard characters: False
 
 ### -RedirectToOptimalOWAServer
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RedirectToOptimalOWAServer parameter specifies whether to find the optimal server for Outlook on the web. Valid values are:
 
@@ -2073,7 +2073,7 @@ Accept wildcard characters: False
 
 ### -ReferenceAttachmentsEnabled
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ReferenceAttachmentsEnabled parameter specifies whether users can attach files from the cloud as linked attachments in Outlook on the web. Valid values are:
 
@@ -2094,7 +2094,7 @@ Accept wildcard characters: False
 
 ### -RemindersAndNotificationsEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RemindersAndNotificationsEnabled parameter specifies whether notifications and reminders are enabled in Outlook on the web. Valid values are:
 
@@ -2117,7 +2117,7 @@ Accept wildcard characters: False
 
 ### -RemoteDocumentsActionForUnknownServers
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is functional only in Exchange Server 2010.
 
@@ -2137,7 +2137,7 @@ Accept wildcard characters: False
 
 ### -RemoteDocumentsAllowedServers
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is functional only in Exchange Server 2010.
 
@@ -2157,7 +2157,7 @@ Accept wildcard characters: False
 
 ### -RemoteDocumentsBlockedServers
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is functional only in Exchange Server 2010.
 
@@ -2177,7 +2177,7 @@ Accept wildcard characters: False
 
 ### -RemoteDocumentsInternalDomainSuffixList
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is functional only in Exchange Server 2010.
 
@@ -2197,7 +2197,7 @@ Accept wildcard characters: False
 
 ### -ReportJunkEmailEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ReportJunkEmailEnabled parameter specifies whether users can report messages as junk or not junk to Microsoft in Outlook on the web. Valid values are:
 
@@ -2220,7 +2220,7 @@ Accept wildcard characters: False
 
 ### -RulesEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RulesEnabled parameter specifies whether a user can view, create, or modify server-side rules in Outlook on the web. Valid values are:
 
@@ -2241,7 +2241,7 @@ Accept wildcard characters: False
 
 ### -SaveAttachmentsToCloudEnabled
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SaveAttachmentsToCloudEnabled parameter specifies whether users can save regular email attachments to the cloud. Valid values are:
 
@@ -2262,7 +2262,7 @@ Accept wildcard characters: False
 
 ### -SearchFoldersEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is functional only in Exchange Server 2010.
 
@@ -2285,7 +2285,7 @@ Accept wildcard characters: False
 
 ### -SetPhotoEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SetPhotoEnabled parameter specifies whether users can add, change, and remove their sender photo in Outlook on the web. Valid values are:
 
@@ -2306,7 +2306,7 @@ Accept wildcard characters: False
 
 ### -SetPhotoURL
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SetPhotoURL parameter specifies the location (URL) of user photos. The default value of this parameter is blank ($null).
 
@@ -2324,7 +2324,7 @@ Accept wildcard characters: False
 
 ### -SignaturesEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SignaturesEnabled parameter specifies whether to enable or disable the use of signatures in Outlook on the web. Valid values are:
 
@@ -2345,7 +2345,7 @@ Accept wildcard characters: False
 
 ### -SilverlightEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is functional only in Exchange Server 2010.
 
@@ -2368,7 +2368,7 @@ Accept wildcard characters: False
 
 ### -SMimeEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is functional only in Exchange Server 2010.
 
@@ -2393,7 +2393,7 @@ Accept wildcard characters: False
 
 ### -SpellCheckerEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is functional only in Exchange Server 2010.
 
@@ -2418,7 +2418,7 @@ Accept wildcard characters: False
 
 ### -TasksEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TasksEnabled parameter specifies whether Tasks folder is available in Outlook on the web. Valid values are:
 
@@ -2441,7 +2441,7 @@ Accept wildcard characters: False
 
 ### -TextMessagingEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TextMessagingEnabled parameter specifies whether users can send and receive text messages in Outlook on the web. Valid values are:
 
@@ -2464,7 +2464,7 @@ Accept wildcard characters: False
 
 ### -ThemeSelectionEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ThemeSelectionEnabled parameter specifies whether users can change the theme in Outlook on the web. Valid values are:
 
@@ -2485,7 +2485,7 @@ Accept wildcard characters: False
 
 ### -UMIntegrationEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The UMIntegrationEnabled parameter specifies whether Unified Messaging (UM) integration is enabled in Outlook on the web. Valid values are:
 
@@ -2510,7 +2510,7 @@ Accept wildcard characters: False
 
 ### -UNCAccessOnPrivateComputersEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is deprecated and no longer used.
 
@@ -2528,7 +2528,7 @@ Accept wildcard characters: False
 
 ### -UNCAccessOnPublicComputersEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is deprecated and no longer used.
 
@@ -2546,7 +2546,7 @@ Accept wildcard characters: False
 
 ### -UseGB18030
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The UseGB18030 parameter specifies whether to use the GB18030 character set instead of GB2312 in Outlook on the web. Valid values are:
 
@@ -2567,7 +2567,7 @@ Accept wildcard characters: False
 
 ### -UseISO885915
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The UseISO885915 parameter specifies whether to use the character set ISO8859-15 instead of ISO8859-1 in Outlook on the web. Valid values are:
 
@@ -2588,7 +2588,7 @@ Accept wildcard characters: False
 
 ### -UserContextTimeout
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The UserContextTimeout parameter specifies the time-out setting in minutes for a user context object. This parameter doesn't limit public and private forms-based authentication time-out settings.
 
@@ -2608,7 +2608,7 @@ Accept wildcard characters: False
 
 ### -VirtualDirectoryType
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is deprecated and no longer used.
 
@@ -2626,7 +2626,7 @@ Accept wildcard characters: False
 
 ### -WacEditingEnabled
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WacEditingEnabled parameter specifies whether to enable or disable editing documents in Outlook on the web by using Office Online Server (formerly known as Office Web Apps Server and Web Access Companion Server). Valid values are:
 
@@ -2647,7 +2647,7 @@ Accept wildcard characters: False
 
 ### -WacViewingOnPrivateComputersEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WacViewingOnPrivateComputersEnabled parameter specifies whether to enable or disable web viewing of supported Office documents private computer sessions in Office Online Server (formerly known as Office Web Apps Server and Web Access Companion Server). By default, all Outlook on the web sessions are considered to be on private computers. Valid values are:
 
@@ -2670,7 +2670,7 @@ Accept wildcard characters: False
 
 ### -WacViewingOnPublicComputersEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WacViewingOnPublicComputersEnabled parameter specifies whether to enable or disable web viewing of supported Office documents in public computer sessions in Office Online Server. Valid values are:
 
@@ -2693,7 +2693,7 @@ Accept wildcard characters: False
 
 ### -WebPartsFrameOptionsType
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WebPartsFrameOptionsType parameter specifies what sources can access web parts in IFRAME or FRAME elements in Outlook on the web. Valid values are:
 
@@ -2905,7 +2905,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
@@ -2923,7 +2923,7 @@ Accept wildcard characters: False
 
 ### -WindowsAuthentication
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WindowsAuthentication parameter enables or disables Integrated Windows authentication on the virtual directory. Valid values are:
 
@@ -2944,7 +2944,7 @@ Accept wildcard characters: False
 
 ### -WSSAccessOnPrivateComputersEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is deprecated and no longer used.
 
@@ -2962,7 +2962,7 @@ Accept wildcard characters: False
 
 ### -WSSAccessOnPublicComputersEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is deprecated and no longer used.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-PartnerApplication.md b/exchange/exchange-ps/ExchangePowerShell/Set-PartnerApplication.md
index 5be97a4965..85dddd2094 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-PartnerApplication.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-PartnerApplication.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -95,7 +95,7 @@ This example refreshes the auth metadata for the HRApp partner application.
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the partner application you want to modify. You can use any value that uniquely identifies the partner application. For example:
 
@@ -118,7 +118,7 @@ Accept wildcard characters: False
 
 ### -AcceptSecurityIdentifierInformation
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AcceptSecurityIdentifierInformation parameter specifies whether Exchange should accept security identifiers (SIDs) from another trusted Active Directory forest for the partner application. By default, new partner applications are configured to not accept SIDs from another forest. If you're in deployment with a trusted forest, set the parameter to $true.
 
@@ -136,7 +136,7 @@ Accept wildcard characters: False
 
 ### -AccountType
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AccountType parameter specifies the type of Microsoft account that's required for the partner application. Valid values are:
 
@@ -157,7 +157,7 @@ Accept wildcard characters: False
 
 ### -ActAsPermissions
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ActAsPermissions parameter specifies the delegate permissions that are allowed for the partner application. You can specify multiple values separated by commas.
 
@@ -175,7 +175,7 @@ Accept wildcard characters: False
 
 ### -ApplicationIdentifier
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ApplicationIdentifier parameter specifies a unique application identifier for the partner application that uses an authorization server.
 
@@ -213,7 +213,7 @@ Accept wildcard characters: False
 
 ### -AuthMetadataUrl
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -233,7 +233,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -254,7 +254,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -274,7 +274,7 @@ Accept wildcard characters: False
 
 ### -Enabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Enabled parameter specifies whether the partner application is enabled. By default, new partner applications are enabled. Set the parameter to $false to create the application configuration in a disabled state.
 
@@ -312,7 +312,7 @@ Accept wildcard characters: False
 
 ### -LinkedAccount
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The LinkedAccount parameter specifies a linked Active Directory user account for the application. Exchange evaluates Role Based Access Control (RBAC) permissions for the linked account when authorizing a token used to perform a task.
 
@@ -330,7 +330,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Name parameter specifies a new name for the partner application.
 
@@ -348,7 +348,7 @@ Accept wildcard characters: False
 
 ### -Realm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -368,7 +368,7 @@ Accept wildcard characters: False
 
 ### -RefreshAuthMetadata
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -388,7 +388,7 @@ Accept wildcard characters: False
 
 ### -TrustAnySSLCertificate
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -410,7 +410,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-PendingFederatedDomain.md b/exchange/exchange-ps/ExchangePowerShell/Set-PendingFederatedDomain.md
index 2024688f5a..92a82fcef1 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-PendingFederatedDomain.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-PendingFederatedDomain.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
 Locale: en-US
@@ -51,7 +51,7 @@ This example adds the pending domains contoso.com and sales.contoso.com to the e
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -69,7 +69,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -90,7 +90,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -108,7 +108,7 @@ Accept wildcard characters: False
 
 ### -PendingAccountNamespace
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PendingAccountNamespace parameter specifies the pending domain that's used as the account namespace for the federation trust.
 
@@ -126,7 +126,7 @@ Accept wildcard characters: False
 
 ### -PendingDomains
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PendingDomains parameter specifies the pending federated domains that are configured for the federation trust.
 
@@ -144,7 +144,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-PolicyTipConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-PolicyTipConfig.md
index 75a9554dd4..8bf4dd3de8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-PolicyTipConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-PolicyTipConfig.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -53,7 +53,7 @@ This example replaces the text of all custom Spanish Policy Tips with the value,
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the custom Policy Tip you want to modify. You can use any value that uniquely identifies the custom Policy Tip. For example:
 
@@ -76,7 +76,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -97,7 +97,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -117,7 +117,7 @@ Accept wildcard characters: False
 
 ### -Value
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Value parameter specifies the text that's displayed by the Policy Tip. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -135,7 +135,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-PopSettings.md b/exchange/exchange-ps/ExchangePowerShell/Set-PopSettings.md
index 0f07bd405a..38da595909 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-PopSettings.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-PopSettings.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -102,7 +102,7 @@ This example specifies the certificate that contains mail.contoso.com is used to
 
 ### -AuthenticatedConnectionTimeout
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AuthenticatedConnectionTimeout parameter specifies the time to wait before closing an idle authenticated connection.
 
@@ -124,7 +124,7 @@ Accept wildcard characters: False
 
 ### -Banner
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Banner parameter specifies the text string that's displayed to connecting POP3 clients. The default value is: The Microsoft Exchange POP3 service is ready.
 
@@ -142,7 +142,7 @@ Accept wildcard characters: False
 
 ### -CalendarItemRetrievalOption
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The CalendarItemRetrievalOption parameter specifies how calendar items are presented to POP3 clients. Valid values are:
 
@@ -167,7 +167,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -188,7 +188,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -206,7 +206,7 @@ Accept wildcard characters: False
 
 ### -EnableExactRFC822Size
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The EnableExactRFC822Size parameter specifies how message sizes are presented to POP3 clients. Valid values are:
 
@@ -227,7 +227,7 @@ Accept wildcard characters: False
 
 ### -EnableGSSAPIAndNTLMAuth
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The EnableGSSAPIAndNTLMAuth parameter specifies whether connections can use Integrated Windows authentication (NTLM) by using the Generic Security Services application programming interface (GSSAPI). This setting applies to connections where Transport Layer Security (TLS) is disabled. Valid values are:
 
@@ -248,7 +248,7 @@ Accept wildcard characters: False
 
 ### -EnforceCertificateErrors
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The EnforceCertificateErrors parameter specifies whether to enforce Secure Sockets Layer (SSL) certificate validation failures. Valid values are:
 
@@ -269,7 +269,7 @@ Accept wildcard characters: False
 
 ### -ExtendedProtectionPolicy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExtendedProtectionPolicy parameter specifies how Extended Protection for Authentication is used for POP3 connections. Valid values are:
 
@@ -293,7 +293,7 @@ Accept wildcard characters: False
 
 ### -ExternalConnectionSettings
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExternalConnectionSettings parameter specifies the host name, port, and encryption method that's used by external POP3 clients (POP3 connections from outside your corporate network).
 
@@ -321,7 +321,7 @@ Accept wildcard characters: False
 
 ### -InternalConnectionSettings
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The InternalConnectionSettings parameter specifies the host name, port, and encryption method that's used by internal POP3 clients (POP3 connections from inside your corporate network). This setting is also used when a POP3 connection is forwarded to another Exchange server that's running the Microsoft Exchange POP3 service.
 
@@ -349,7 +349,7 @@ Accept wildcard characters: False
 
 ### -LogFileLocation
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The LogFileLocation parameter specifies the location for the POP3 protocol log files. The default location is%ExchangeInstallPath%Logging\\Pop3.
 
@@ -369,7 +369,7 @@ Accept wildcard characters: False
 
 ### -LogFileRollOverSettings
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The LogFileRollOverSettings parameter defines how frequently POP3 protocol logging creates a new log file. Valid values are:
 
@@ -394,7 +394,7 @@ Accept wildcard characters: False
 
 ### -LoginType
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The LoginType parameter specifies the authentication method for POP3 connections. Valid values are:
 
@@ -416,7 +416,7 @@ Accept wildcard characters: False
 
 ### -LogPerFileSizeQuota
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The LogPerFileSizeQuota parameter specifies the maximum size of a POP3 protocol log file.
 
@@ -448,7 +448,7 @@ Accept wildcard characters: False
 
 ### -MaxCommandSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MaxCommandSize parameter specifies the maximum size in bytes of a single POP3 command. Valid values are from 40 through 1024. The default value is 512.
 
@@ -466,7 +466,7 @@ Accept wildcard characters: False
 
 ### -MaxConnectionFromSingleIP
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MaxConnectionFromSingleIP parameter specifies the maximum number of POP3 connections that are accepted by the Exchange server from a single IP address. Valid values are from 1 through 2147483647. The default value is 2147483647.
 
@@ -484,7 +484,7 @@ Accept wildcard characters: False
 
 ### -MaxConnections
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MaxConnections parameter specifies the maximum number of POP3 connections that are accepted by the Exchange server. Valid values are from 1 through 2147483647. The default value is 2147483647.
 
@@ -502,7 +502,7 @@ Accept wildcard characters: False
 
 ### -MaxConnectionsPerUser
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MaxConnectionsPerUser parameter specifies the maximum number of POP3 connections that are allowed for each user. Valid values are from 1 through 2147483647. The default value is 16.
 
@@ -520,7 +520,7 @@ Accept wildcard characters: False
 
 ### -MessageRetrievalMimeFormat
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MessageRetrievalMimeFormat parameter specifies the MIME encoding of messages. Valid values are:
 
@@ -546,7 +546,7 @@ Accept wildcard characters: False
 
 ### -MessageRetrievalSortOrder
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MessageRetrievalSortOrder parameter specifies how retrieved messages are sorted. Valid values are:
 
@@ -567,7 +567,7 @@ Accept wildcard characters: False
 
 ### -OwaServerUrl
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The OwaServerUrl parameter specifies the URL that's used to retrieve calendar information for instances of custom Outlook on the web calendar items.
 
@@ -585,7 +585,7 @@ Accept wildcard characters: False
 
 ### -PreAuthenticatedConnectionTimeout
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PreAuthenticatedConnectionTimeout parameter specifies the time to wait before closing an idle POP3 connection that isn't authenticated.
 
@@ -607,7 +607,7 @@ Accept wildcard characters: False
 
 ### -ProtocolLogEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ProtocolLogEnabled parameter specifies whether to enable protocol logging for POP3. Valid values are:
 
@@ -628,7 +628,7 @@ Accept wildcard characters: False
 
 ### -ProxyTargetPort
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ProxyTargetPort parameter specifies the port on the Microsoft Exchange POP3 Backend service that listens for client connections that are proxied from the Microsoft Exchange POP3 service. The default value is 1995.
 
@@ -646,7 +646,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
 
@@ -671,7 +671,7 @@ Accept wildcard characters: False
 
 ### -SSLBindings
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SSLBindings parameter specifies the IP address and TCP port that's used for an POP3 connection that's always encrypted by SSL/TLS. This parameter uses the syntax `IPv4OrIPv6Address:Port`.
 
@@ -695,7 +695,7 @@ Accept wildcard characters: False
 
 ### -SuppressReadReceipt
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SuppressReadReceipt parameter specifies whether to stop duplicate read receipts from being sent to POP3 clients that have the Send read receipts for messages I send setting configured in their POP3 email program. Valid values are:
 
@@ -716,7 +716,7 @@ Accept wildcard characters: False
 
 ### -UnencryptedOrTLSBindings
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The UnencryptedOrTLSBindings parameter specifies the IP address and TCP port that's used for unencrypted POP3 connections, or POP3 connections that are encrypted by using opportunistic TLS (STARTTLS) after the initial unencrypted protocol handshake. This parameter uses the syntax `IPv4OrIPv6Address:Port`.
 
@@ -740,7 +740,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
@@ -758,7 +758,7 @@ Accept wildcard characters: False
 
 ### -X509CertificateName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The X509CertificateName parameter specifies the certificate that's used for encrypting POP3 client connections.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-PowerShellVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Set-PowerShellVirtualDirectory.md
index 955bf80c98..bf18ace465 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-PowerShellVirtualDirectory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-PowerShellVirtualDirectory.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -56,7 +56,7 @@ This example modifies the external URL of the Contoso Windows PowerShell virtual
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the PowerShell virtual directory that you want to modify. You can use any value that uniquely identifies the virtual directory. For example:
 
@@ -80,7 +80,7 @@ Accept wildcard characters: False
 
 ### -BasicAuthentication
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The BasicAuthentication parameter specifies whether Basic authentication is enabled on the virtual directory. Valid values are:
 
@@ -101,7 +101,7 @@ Accept wildcard characters: False
 
 ### -CertificateAuthentication
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The CertificateAuthentication parameter specifies whether certificate authentication is enabled on the Windows PowerShell virtual directory. The valid values are $true and $false. The default value is $false.
 
@@ -119,7 +119,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -140,7 +140,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -158,7 +158,7 @@ Accept wildcard characters: False
 
 ### -ExtendedProtectionFlags
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExtendedProtectionFlags parameter specifies custom settings for Extended Protection for Authentication on the virtual directory. Valid values are:
 
@@ -182,7 +182,7 @@ Accept wildcard characters: False
 
 ### -ExtendedProtectionSPNList
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExtendedProtectionSPNList parameter specifies a list of valid Service Principal Names (SPNs) if you're using Extended Protection for Authentication on the virtual directory. Valid values are:
 
@@ -203,7 +203,7 @@ Accept wildcard characters: False
 
 ### -ExtendedProtectionTokenChecking
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExtendedProtectionTokenChecking parameter defines how you want to use Extended Protection for Authentication on the virtual directory. Extended Protection for Authentication isn't enabled by default. Valid values are:
 
@@ -227,7 +227,7 @@ Accept wildcard characters: False
 
 ### -ExternalUrl
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExternalURL parameter specifies the URL that's used to connect to the virtual directory from outside the firewall.
 
@@ -245,7 +245,7 @@ Accept wildcard characters: False
 
 ### -InternalUrl
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The InternalURL parameter specifies the URL that's used to connect to the virtual directory from inside the firewall.
 
@@ -263,7 +263,7 @@ Accept wildcard characters: False
 
 ### -RequireSSL
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RequireSSL parameter specifies whether the Windows PowerShell virtual directory should require that the client connection be made using Secure Sockets Layer (SSL). The valid values are $true and $false. The default value is $true.
 
@@ -281,7 +281,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
@@ -299,7 +299,7 @@ Accept wildcard characters: False
 
 ### -WindowsAuthentication
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WindowsAuthentication parameter specifies whether Integrated Windows authentication is enabled on the virtual directory. Valid values are:
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-PublicFolder.md b/exchange/exchange-ps/ExchangePowerShell/Set-PublicFolder.md
index 1482cb835f..637254fa24 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-PublicFolder.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-PublicFolder.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.WebClient-Help.xml
 Locale: en-US
@@ -81,7 +81,7 @@ In Exchange 2010, this example sets the folder to replicate only on weekends.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the name and path of the public folder you want to modify. A valid value uses the format: `\Level1\Level2\...\LevenN\PublicFolder`. For example, `"\Customer Discussion"` or `"\Engineering\Customer Discussion"`.
 
@@ -99,7 +99,7 @@ Accept wildcard characters: False
 
 ### -AgeLimit
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AgeLimit parameter specifies the overall age limit on the folder. Items that reach the age limit are deleted from the public folder. Replicas of this public folder are automatically deleted when the age limit is exceeded.
 
@@ -119,7 +119,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -140,7 +140,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -160,7 +160,7 @@ Accept wildcard characters: False
 
 ### -EformsLocaleId
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The EformsLocaleId parameter specifies the locale-specific version of the e-forms library. The valid input for the EformsLocaleId parameter is the string names listed in the Culture Name column in the Microsoft .NET Class Library class reference available at [CultureInfo Class](https://learn.microsoft.com/dotnet/api/system.globalization.cultureinfo).
 
@@ -178,7 +178,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -218,7 +218,7 @@ Accept wildcard characters: False
 
 ### -IssueWarningQuota
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IssueWarningQuota parameter specifies the public folder size that triggers a warning to public folder owners stating that the folder is almost full.
 
@@ -270,7 +270,7 @@ Accept wildcard characters: False
 
 ### -MailEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MailEnabled parameter specifies that the public folder is mail-enabled. To do this, you use the value $true.
 
@@ -290,7 +290,7 @@ Accept wildcard characters: False
 
 ### -MailRecipientGuid
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MailRecipientGuid parameter specifies the MailRecipientGuid value of the public folder. You use this parameter to correct a mail-enabled public folder that lost its MailRecipientGuid value.
 
@@ -310,7 +310,7 @@ Accept wildcard characters: False
 
 ### -MaxItemSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MaxItemSize parameter specifies the maximum size for posted items. Items larger than the value of the MaxItemSize parameter are rejected. The default value is unlimited, which is 2 gigabytes. When you enter a value, qualify the value with one of the following units:
 
@@ -340,7 +340,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Name parameter specifies the name for the public folder.
 
@@ -358,7 +358,7 @@ Accept wildcard characters: False
 
 ### -OverrideContentMailbox
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -389,7 +389,7 @@ Accept wildcard characters: False
 
 ### -Path
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Path parameter specifies the path of the public folder, for example, \\TopLevelPublicFolder\\PublicFolder.
 
@@ -407,7 +407,7 @@ Accept wildcard characters: False
 
 ### -PerUserReadStateEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The PerUserReadStateEnabled parameter specifies whether to maintain read and unread data on a per-user basis.
 
@@ -425,7 +425,7 @@ Accept wildcard characters: False
 
 ### -ProhibitPostQuota
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ProhibitPostQuota parameter specifies the size of a public folder at which users are notified that the public folder is full. Users can't post to a folder whose size is larger than the ProhibitPostQuota parameter value. The default value is unlimited, which is 2 terabytes.
 
@@ -521,7 +521,7 @@ Accept wildcard characters: False
 
 ### -RetainDeletedItemsFor
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RetainDeletedItemsFor parameter specifies the retention time for deleted items.
 
@@ -648,7 +648,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-PublicFolderMigrationRequest.md b/exchange/exchange-ps/ExchangePowerShell/Set-PublicFolderMigrationRequest.md
index a2c4eedfb8..e02fbe8c83 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-PublicFolderMigrationRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-PublicFolderMigrationRequest.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -71,7 +71,7 @@ This example changes the setting of the PublicFolderMigration migration request
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the migration request that you want to modify. You can use the following values:
 
@@ -92,7 +92,7 @@ Accept wildcard characters: False
 
 ### -RehomeRequest
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RehomeRequest switch tells the Microsoft Exchange Mailbox Replication service (MRS) that the request needs to be moved to the same database as the public folder that's being migrated. You don't need to specify a value with this switch.
 
@@ -112,7 +112,7 @@ Accept wildcard characters: False
 
 ### -AcceptLargeDataLoss
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AcceptLargeDataLoss switch specifies the request should continue even if a large number of items in the source mailbox can't be copied to the target mailbox. You don't need to specify a value with this switch.
 
@@ -132,7 +132,7 @@ Accept wildcard characters: False
 
 ### -BadItemLimit
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The BadItemLimit parameter specifies the maximum number of bad items that are allowed before the request fails. A bad item is a corrupt item in the source mailbox that can't be copied to the target mailbox. Also included in the bad item limit are missing items. Missing items are items in the source mailbox that can't be found in the target mailbox when the request is ready to complete.
 
@@ -152,7 +152,7 @@ Accept wildcard characters: False
 
 ### -BatchName
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The BatchName parameter specifies a descriptive name for the public folder batch migration. You can use the BatchName parameter as a search string when you use the Get-PublicFolderMigrationRequest cmdlet.
 
@@ -170,7 +170,7 @@ Accept wildcard characters: False
 
 ### -CompletedRequestAgeLimit
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The CompletedRequestAgeLimit parameter specifies how long the request is kept after it has completed before being automatically removed. The default CompletedRequestAgeLimit parameter value is 30 days.
 
@@ -188,7 +188,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -209,7 +209,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -227,7 +227,7 @@ Accept wildcard characters: False
 
 ### -InternalFlags
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The InternalFlags parameter specifies the optional steps in the request. This parameter is used primarily for debugging purposes.
 
@@ -245,7 +245,7 @@ Accept wildcard characters: False
 
 ### -LargeItemLimit
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The LargeItemLimit parameter specifies the maximum number of large items that are allowed before the request fails. A large item is a message in the source mailbox that exceeds the maximum message size that's allowed in the target mailbox. If the target mailbox doesn't have a specifically configured maximum message size value, the organization-wide value is used.
 
@@ -272,7 +272,7 @@ Accept wildcard characters: False
 
 ### -PreventCompletion
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PreventCompletion parameter specifies whether to run the migration request, but not allow it to complete. Valid values are:
 
@@ -293,7 +293,7 @@ Accept wildcard characters: False
 
 ### -Priority
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Priority parameter specifies the order in which the request should be processed in the request queue. Requests are processed in order, based on server health, status, priority, and last update time. Valid priority values are:
 
@@ -320,7 +320,7 @@ Accept wildcard characters: False
 
 ### -RequestExpiryInterval
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RequestExpiryInterval parameter specifies an age limit for a completed or failed request. When you use this parameter, the completed or failed request is automatically removed after the specified interval expires. If you don't use this parameter:
 
@@ -345,7 +345,7 @@ Accept wildcard characters: False
 
 ### -SkipMerging
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SkipMerging parameter specifies whether certain stages of a migration are to be skipped for debugging purposes. Don't use this parameter unless directed to do so by Microsoft Customer Service and Support or specific documentation.
 
@@ -363,7 +363,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-PublicFolderMoveRequest.md b/exchange/exchange-ps/ExchangePowerShell/Set-PublicFolderMoveRequest.md
index d1e95ab4b5..a38c57d131 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-PublicFolderMoveRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-PublicFolderMoveRequest.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -55,7 +55,7 @@ This example changes the public folder move request \\PublicFolderMove to accept
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the identity of the public folder move request. The default identity of a public folder move request is \\PublicFolderMove.
 
@@ -73,7 +73,7 @@ Accept wildcard characters: False
 
 ### -AcceptLargeDataLoss
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AcceptLargeDataLoss switch specifies the request should continue even if a large number of items in the source mailbox can't be copied to the target mailbox. You don't need to specify a value with this switch.
 
@@ -93,7 +93,7 @@ Accept wildcard characters: False
 
 ### -BadItemLimit
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The BadItemLimit parameter specifies the maximum number of bad items that are allowed before the request fails. A bad item is a corrupt item in the source mailbox that can't be copied to the target mailbox. Also included in the bad item limit are missing items. Missing items are items in the source mailbox that can't be found in the target mailbox when the request is ready to complete.
 
@@ -113,7 +113,7 @@ Accept wildcard characters: False
 
 ### -CompletedRequestAgeLimit
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The CompletedRequestAgeLimit parameter specifies how long the request is kept after it has completed before being automatically removed. The default CompletedRequestAgeLimit parameter value is 30 days.
 
@@ -131,7 +131,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -152,7 +152,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -170,7 +170,7 @@ Accept wildcard characters: False
 
 ### -InternalFlags
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The InternalFlags parameter specifies the optional steps in the request. This parameter is used primarily for debugging purposes.
 
@@ -188,7 +188,7 @@ Accept wildcard characters: False
 
 ### -LargeItemLimit
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The LargeItemLimit parameter specifies the maximum number of large items that are allowed before the request fails. A large item is a message in the source mailbox that exceeds the maximum message size that's allowed in the target mailbox. If the target mailbox doesn't have a specifically configured maximum message size value, the organization-wide value is used.
 
@@ -215,7 +215,7 @@ Accept wildcard characters: False
 
 ### -Priority
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Priority parameter specifies the order in which the request should be processed in the request queue. Requests are processed in order, based on server health, status, priority, and last update time. Valid priority values are:
 
@@ -242,7 +242,7 @@ Accept wildcard characters: False
 
 ### -RequestExpiryInterval
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RequestExpiryInterval parameter specifies an age limit for a completed or failed request. When you use this parameter, the completed or failed request is automatically removed after the specified interval expires. If you don't use this parameter:
 
@@ -267,7 +267,7 @@ Accept wildcard characters: False
 
 ### -SuspendWhenReadyToComplete
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SuspendWhenReadyToComplete parameter specifies whether to suspend the request before it reaches the status of CompletionInProgress. After the move is suspended, it has a status of AutoSuspended. You can then manually complete the move by using the Resume-PublicFolderMoveRequest command.
 
@@ -285,7 +285,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ReceiveConnector.md b/exchange/exchange-ps/ExchangePowerShell/Set-ReceiveConnector.md
index c84552f4b2..9ac0a5b89e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ReceiveConnector.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ReceiveConnector.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -102,7 +102,7 @@ Configures the Receive connector to time out connections after 15 minutes.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the Receive connector that you want to modify. You can use any value that uniquely identifies the Receive connector. For example:
 
@@ -125,7 +125,7 @@ Accept wildcard characters: False
 
 ### -AdvertiseClientSettings
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AdvertiseClientSettings parameter specifies whether the SMTP server name, port number, and authentication settings for the Receive connector are displayed to users in the options of Outlook on the web. Valid values are:
 
@@ -146,7 +146,7 @@ Accept wildcard characters: False
 
 ### -AuthMechanism
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AuthMechanism parameter specifies the advertised and accepted authentication mechanisms for the Receive connector. Valid values are:
 
@@ -180,7 +180,7 @@ Accept wildcard characters: False
 
 ### -AuthTarpitInterval
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AuthTarpitInterval parameter specifies the period of time to delay responses to failed authentication attempts from remote servers that might be abusing the connection. The default value is 5 seconds.
 
@@ -204,7 +204,7 @@ Accept wildcard characters: False
 
 ### -Banner
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Banner parameter specifies a custom SMTP 220 banner that's displayed to remote messaging servers that connect to the Receive connector. When you specify a value, enclose the value in quotation marks, and start the value with 220 (the default "Service ready" SMTP response code).
 
@@ -226,7 +226,7 @@ Accept wildcard characters: False
 
 ### -BareLinefeedRejectionEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The BareLinefeedRejectionEnabled parameter specifies whether this Receive connector rejects messages that contain line feed (LF) characters without immediately preceding carriage return characters (CR) in the SMTP DATA stream. This condition is known as bare line feeds. Valid values are:
 
@@ -249,7 +249,7 @@ Accept wildcard characters: False
 
 ### -BinaryMimeEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The BinaryMimeEnabled parameter specifies whether the BINARYMIME Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are:
 
@@ -272,7 +272,7 @@ Accept wildcard characters: False
 
 ### -Bindings
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Bindings parameter specifies the local IP address and TCP port number that's used by the Receive connector. This parameter uses the syntax `"IPv4Address:TCPPort","IPv6Address:TCPPort"`. You can specify an IPv4 address and port, an IPv6 address and port, or both. The IP address values 0.0.0.0 or `[::]` indicate that the Receive connector uses all available local IPv4 or all IPv6 addresses.
 
@@ -297,7 +297,7 @@ Accept wildcard characters: False
 
 ### -ChunkingEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ChunkingEnabled parameter specifies whether the CHUNKING Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are:
 
@@ -320,7 +320,7 @@ Accept wildcard characters: False
 
 ### -Comment
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Comment parameter specifies an optional comment. If you specify a value that contains spaces, enclose the value in quotation marks ("), for example: "This is an admin note".
 
@@ -338,7 +338,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -359,7 +359,7 @@ Accept wildcard characters: False
 
 ### -ConnectionInactivityTimeout
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ConnectionInactivityTimeout parameter specifies the maximum amount of idle time before a connection to the Receive connector is closed.
 
@@ -385,7 +385,7 @@ Accept wildcard characters: False
 
 ### -ConnectionTimeout
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ConnectionTimeout parameter specifies the maximum time that the connection to the Receive connector can remain open, even if the connection is actively transmitting data.
 
@@ -411,7 +411,7 @@ Accept wildcard characters: False
 
 ### -DefaultDomain
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DefaultDomain parameter specifies the default accepted domain to use for the Exchange organization. You can use any value that uniquely identifies the accepted domain. For example:
 
@@ -439,7 +439,7 @@ Accept wildcard characters: False
 
 ### -DeliveryStatusNotificationEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DeliveryStatusNotificationEnabled parameter specifies whether the DSN (delivery status notification) Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are:
 
@@ -462,7 +462,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -482,7 +482,7 @@ Accept wildcard characters: False
 
 ### -DomainSecureEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainSecureEnabled parameter specifies whether to enable or disable mutual Transport Layer Security (TLS) authentication (also known as Domain Secure) for the domains that are serviced by the Receive connector. Valid values are:
 
@@ -511,7 +511,7 @@ Accept wildcard characters: False
 
 ### -EightBitMimeEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The EightBitMimeEnabled parameter specifies whether the 8BITMIME Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are:
 
@@ -534,7 +534,7 @@ Accept wildcard characters: False
 
 ### -EnableAuthGSSAPI
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The EnableAuthGSSAPI parameter enables or disables Kerberos when Integrated Windows authentication is available on the Receive connector (the AuthMechanism parameter contains the value Integrated). Valid values are:
 
@@ -557,7 +557,7 @@ Accept wildcard characters: False
 
 ### -Enabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Enabled parameter specifies whether to enable or disable the Receive connector. Valid values are:
 
@@ -578,7 +578,7 @@ Accept wildcard characters: False
 
 ### -EnhancedStatusCodesEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The EnhancedStatusCodesEnabled parameter specifies whether the ENHANCEDSTATUSCODES Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are:
 
@@ -601,7 +601,7 @@ Accept wildcard characters: False
 
 ### -ExtendedProtectionPolicy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExtendedProtectionPolicy parameter specifies how you want to use Extended Protection for Authentication on the Receive connector.Valid values are:
 
@@ -625,7 +625,7 @@ Accept wildcard characters: False
 
 ### -Fqdn
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Fqdn parameter specifies the destination FQDN that's shown to connected messaging servers. This value is used in the following locations:
 
@@ -652,7 +652,7 @@ Accept wildcard characters: False
 
 ### -LongAddressesEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The LongAddressesEnabled parameter specifies whether the Receive connector accepts long X.400 email addresses. The X.400 email addresses are encapsulated in SMTP email addresses by using the Internet Mail Connector Encapsulated Address (IMCEA) encapsulation method. Valid values are:
 
@@ -681,7 +681,7 @@ Accept wildcard characters: False
 
 ### -MaxAcknowledgementDelay
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter isn't used by Exchange Server 2016. It's used only by Exchange 2010 servers in coexistence environments.
 
@@ -703,7 +703,7 @@ Accept wildcard characters: False
 
 ### -MaxHeaderSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MaxHeaderSize parameter specifies the maximum size of the SMTP message header before the Receive connector closes the connection. The default value is 256 kilobytes (262144 bytes).
 
@@ -732,7 +732,7 @@ Accept wildcard characters: False
 
 ### -MaxHopCount
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MaxHopCount parameter specifies the maximum number of hops that a message can take before the message is rejected by the Receive connector. The maximum number of hops is determined by the number of Received header fields that exist in a submitted message.
 
@@ -752,7 +752,7 @@ Accept wildcard characters: False
 
 ### -MaxInboundConnection
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MaxInboundConnection parameter specifies the maximum number of inbound connections that this Receive connector serves at the same time.
 
@@ -774,7 +774,7 @@ Accept wildcard characters: False
 
 ### -MaxInboundConnectionPercentagePerSource
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MaxInboundConnectionPercentagePerSource parameter specifies the maximum number of connections that a Receive connector serves at the same time from a single IP address, expressed as the percentage of available remaining connections on a Receive connector.
 
@@ -794,7 +794,7 @@ Accept wildcard characters: False
 
 ### -MaxInboundConnectionPerSource
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MaxInboundConnectionPerSource parameter specifies the maximum number of connections that this Receive connector serves at the same time from a single IP address.
 
@@ -816,7 +816,7 @@ Accept wildcard characters: False
 
 ### -MaxLocalHopCount
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MaxLocalHopCount parameter specifies the maximum number of local hops that a message can take before the message is rejected by the Receive connector. The maximum number of local hops is determined by the number of Received headers with local server addresses in a submitted message.
 
@@ -838,7 +838,7 @@ Accept wildcard characters: False
 
 ### -MaxLogonFailures
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MaxLogonFailures parameter specifies the number of logon failures that the Receive connector retries before it closes the connection.
 
@@ -860,7 +860,7 @@ Accept wildcard characters: False
 
 ### -MaxMessageSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MaxMessageSize parameter specifies the maximum size of a message that's allowed through the Receive connector. The default value is 36 MB, which results in a realistic maximum message size of 25 MB.
 
@@ -892,7 +892,7 @@ Accept wildcard characters: False
 
 ### -MaxProtocolErrors
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MaxProtocolErrors parameter specifies the maximum number of SMTP protocol errors that the Receive connector accepts before closing the connection.
 
@@ -914,7 +914,7 @@ Accept wildcard characters: False
 
 ### -MaxRecipientsPerMessage
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MaxRecipientsPerMessage parameter specifies the maximum number of recipients per message that the Receive connector accepts before closing the connection.
 
@@ -934,7 +934,7 @@ Accept wildcard characters: False
 
 ### -MessageRateLimit
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MessageRateLimit parameter specifies the maximum number of messages that can be sent by a single client IP address per minute.
 
@@ -958,7 +958,7 @@ Accept wildcard characters: False
 
 ### -MessageRateSource
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MessageRateSource parameter specifies how the message submission rate is calculated. Valid values are:
 
@@ -981,7 +981,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Name parameter specifies the unique name for the Receive connector. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks.
 
@@ -999,7 +999,7 @@ Accept wildcard characters: False
 
 ### -OrarEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The OrarEnabled parameter enables or disables Originator Requested Alternate Recipient (ORAR) on the Receive connector. Valid values are:
 
@@ -1022,7 +1022,7 @@ Accept wildcard characters: False
 
 ### -PermissionGroups
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PermissionGroups parameter specifies the well-known security principals who are authorized to use the Receive connector and the permissions that are assigned to them. Valid values are:
 
@@ -1054,7 +1054,7 @@ Accept wildcard characters: False
 
 ### -PipeliningEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PipeliningEnabled parameter specifies whether the PIPELINING Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are:
 
@@ -1077,7 +1077,7 @@ Accept wildcard characters: False
 
 ### -ProtocolLoggingLevel
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ProtocolLoggingLevel parameter specifies whether to enable or disable protocol logging for the Receive connector. Valid values are:
 
@@ -1100,7 +1100,7 @@ Accept wildcard characters: False
 
 ### -RejectReservedSecondLevelRecipientDomains
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RejectReservedSecondLevelRecipientDomains parameter specifies whether to reject connections that contain recipients in reserved second-level domains as specified in RFC 2606 (example.com, example.net, or example.org). Valid value are:
 
@@ -1121,7 +1121,7 @@ Accept wildcard characters: False
 
 ### -RejectReservedTopLevelRecipientDomains
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RejectReservedTopLevelRecipientDomains parameter specifies whether to reject connections that contain recipients in reserved top-level domains (TLDs) as specified in RFC 2606 (.test, .example, .invalid, or .localhost). Valid value are:
 
@@ -1142,7 +1142,7 @@ Accept wildcard characters: False
 
 ### -RejectSingleLabelRecipientDomains
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RejectSingleLabelRecipientDomains parameter specifies whether to reject connections that contain recipients in single-label domains (for example, chris@contoso instead of chris@contoso.com). Valid values are:
 
@@ -1163,7 +1163,7 @@ Accept wildcard characters: False
 
 ### -RemoteIPRanges
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RemoteIPRanges parameter specifies the remote IP addresses that the Receive connector accepts messages from. Valid values are:
 
@@ -1195,7 +1195,7 @@ Accept wildcard characters: False
 
 ### -RequireEHLODomain
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RequireEHLODomain parameter specifies whether the client must provide a domain name in the EHLO handshake after the SMTP connection is established. Valid values are:
 
@@ -1216,7 +1216,7 @@ Accept wildcard characters: False
 
 ### -RequireTLS
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RequireTLS parameter specifies whether to require TLS transmission for inbound messages on the Receive connector. Valid values are:
 
@@ -1237,7 +1237,7 @@ Accept wildcard characters: False
 
 ### -ServiceDiscoveryFqdn
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ServiceDiscoveryFqdn parameter specifies the service discovery fully-qualified domain name (FQDN). for the Receive connector.
 
@@ -1255,7 +1255,7 @@ Accept wildcard characters: False
 
 ### -SizeEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SizeEnabled parameter specifies how the SIZE Extended SMTP extension is used on the Receive connector. Valid values are:
 
@@ -1279,7 +1279,7 @@ Accept wildcard characters: False
 
 ### -SmtpUtf8Enabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -1297,7 +1297,7 @@ Accept wildcard characters: False
 
 ### -SuppressXAnonymousTls
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SuppressXAnonymousTls parameter specifies whether the X-ANONYMOUSTLS Extended SMTP extension is enabled or disabled on the Receive connector. Valid values are:
 
@@ -1320,7 +1320,7 @@ Accept wildcard characters: False
 
 ### -TarpitInterval
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TarpitInterval parameter specifies the period of time to delay an SMTP response to a remote server that might be abusing the connection. The default value is 00:00:05 (5 seconds).
 
@@ -1344,7 +1344,7 @@ Accept wildcard characters: False
 
 ### -TlsCertificateName
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TlsCertificateName parameter specifies the X.509 certificate to use for TLS encryption. A valid value for this parameter is `"<I>X.500Issuer<S>X.500Subject"`. The X.500Issuer value is found in the certificate's Issuer field, and the X.500Subject value is found in the certificate's Subject field. You can find these values by running the Get-ExchangeCertificate cmdlet. Or, after you run Get-ExchangeCertificate to find the thumbprint value of the certificate, run the command `$TLSCert = Get-ExchangeCertificate -Thumbprint <Thumbprint>`, run the command `$TLSCertName = "<I>$($TLSCert.Issuer)<S>$($TLSCert.Subject)"` and then use the value $TLSCertName for this parameter.
 
@@ -1362,7 +1362,7 @@ Accept wildcard characters: False
 
 ### -TlsDomainCapabilities
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TlsDomainCapabilities parameter specifies the capabilities that the Receive connector makes available to specific hosts outside of the organization. Remote hosts are authenticated with TLS with certificate validation before these capabilities are offered.
 
@@ -1395,7 +1395,7 @@ Accept wildcard characters: False
 
 ### -TransportRole
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TransportRole parameter specifies the transport service on the Mailbox server where the Receive connector is created. Valid values are:
 
@@ -1418,7 +1418,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-RecipientFilterConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-RecipientFilterConfig.md
index a2b2f7d24f..04a2802d81 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-RecipientFilterConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-RecipientFilterConfig.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailControl-Help.xml
 Locale: en-US
@@ -60,7 +60,7 @@ This example makes the following changes to the Recipient Filter agent configura
 
 ### -BlockedRecipients
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The BlockedRecipients parameter specifies one or more SMTP addresses. To enter multiple SMTP addresses, separate the addresses by using a comma. The maximum number of individual SMTP addresses that you can input is 800.
 
@@ -78,7 +78,7 @@ Accept wildcard characters: False
 
 ### -BlockListEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The BlockListEnabled parameter specifies whether the Recipient Filter agent blocks messages sent to recipients listed in the BlockedRecipients parameter. Valid input for the BlockListEnabled parameter is $true or $false. The default setting is $false. When the BlockListEnabled parameter is set to $true, the Recipient Filter agent blocks messages sent to recipients listed in the BlockedRecipients parameter.
 
@@ -96,7 +96,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -117,7 +117,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -137,7 +137,7 @@ Accept wildcard characters: False
 
 ### -Enabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Enabled parameter specifies whether the Recipient Filter agent is enabled on the computer on which you're running the command. Valid input for the Enabled parameter is $true or $false. The default setting is $true. When the Enabled parameter is set to $true, the Recipient Filter agent is enabled on the computer on which you're running the command.
 
@@ -155,7 +155,7 @@ Accept wildcard characters: False
 
 ### -ExternalMailEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExternalMailEnabled parameter specifies whether all messages received from unauthenticated connections by servers external to your organization are passed through the Recipient Filter agent for processing. Valid input for the ExternalMailEnabled parameter is $true or $false. The default setting is $true. When the ExternalMailEnabled parameter is set to $true, all messages received from unauthenticated connections by servers external to your organization are passed through the Recipient Filter agent for processing.
 
@@ -173,7 +173,7 @@ Accept wildcard characters: False
 
 ### -InternalMailEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The InternalMailEnabled parameter specifies whether all messages from authenticated sender domains that belong to authoritative domains in the enterprise are passed through the Recipient Filter agent for processing. Valid input for the InternalMailEnabled parameter is $true or $false. The default setting is $false. When the InternalMailEnabled parameter is set to $true, all messages from authenticated sender domains that belong to authoritative domains in the enterprise are passed through the Recipient Filter agent for processing.
 
@@ -191,7 +191,7 @@ Accept wildcard characters: False
 
 ### -RecipientValidationEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RecipientValidationEnabled parameter specifies whether the Recipient Filter agent blocks messages addressed to recipients that don't exist in the organization. Valid input for the RecipientValidationEnabled parameter is $true or $false. The default setting is $false. When the RecipientValidationEnabled parameter is set to $true, the Recipient Filter agent blocks messages addressed to recipients that don't exist in the organization.
 
@@ -209,7 +209,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-RemoteDomain.md b/exchange/exchange-ps/ExchangePowerShell/Set-RemoteDomain.md
index ed3e25485e..2dff3a4d90 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-RemoteDomain.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-RemoteDomain.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -83,7 +83,7 @@ This example queries Active Directory for all remote domains for which auto repl
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the remote domain that you want to modify. You can use any value that uniquely identifies the remote domain. For example:
 
@@ -105,7 +105,7 @@ Accept wildcard characters: False
 
 ### -AllowedOOFType
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AllowedOOFType parameter specifies the type of automatic replies or out-of-office (also known as OOF) notifications than can be sent to recipients in the remote domain. Valid values are:
 
@@ -133,7 +133,7 @@ Accept wildcard characters: False
 
 ### -AutoForwardEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AutoForwardEnabled parameter specifies whether to allow messages that are auto-forwarded by client email programs in your organization. Valid values are:
 
@@ -154,7 +154,7 @@ Accept wildcard characters: False
 
 ### -AutoReplyEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AutoReplyEnabled parameter specifies whether to allow messages that are automatic replies from client email programs in your organization (for example, automatic reply messages that are generated by rules in Outlook). Valid values are:
 
@@ -175,7 +175,7 @@ Accept wildcard characters: False
 
 ### -ByteEncoderTypeFor7BitCharsets
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ByteEncoderTypeFor7BitCharsets parameter specifies the 7-bit transfer encoding method for MIME format for messages sent to this remote domain. Valid values are:
 
@@ -202,7 +202,7 @@ Accept wildcard characters: False
 
 ### -CharacterSet
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The CharacterSet parameter specifies a character set for MIME messages without defined character sets that are sent from your organization to recipients in the remote domain. Valid values are:
 
@@ -226,7 +226,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -247,7 +247,7 @@ Accept wildcard characters: False
 
 ### -ContentType
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ContentType parameter specifies the outbound message content type and formatting. Valid values are:
 
@@ -269,7 +269,7 @@ Accept wildcard characters: False
 
 ### -DeliveryReportEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DeliveryReportEnabled parameter specifies whether to allow delivery reports from client software in your organization to recipients in the remote domain. Valid values are:
 
@@ -290,7 +290,7 @@ Accept wildcard characters: False
 
 ### -DisplaySenderName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 **Note**: You should only modify this parameter under the direction of Microsoft Customer Service and Support.
 
@@ -313,7 +313,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -358,7 +358,7 @@ Accept wildcard characters: False
 
 ### -IsInternal
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IsInternal parameter specifies whether the recipients in the remote domain are considered to be internal recipients. Valid values are:
 
@@ -384,7 +384,7 @@ Accept wildcard characters: False
 
 ### -LineWrapSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The LineWrapSize parameter specifies the line-wrap size for messages to recipients in the remote domain. Valid values are an integer from 0 through 132 or the value to unlimited. The default value is unlimited.
 
@@ -402,7 +402,7 @@ Accept wildcard characters: False
 
 ### -MeetingForwardNotificationEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MeetingForwardNotificationEnabled parameter specifies whether to enable meeting forward notifications for recipients in the remote domain. Valid values are:
 
@@ -423,7 +423,7 @@ Accept wildcard characters: False
 
 ### -MessageCountThreshold
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -445,7 +445,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Name parameter specifies a unique name for the remote domain object. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -463,7 +463,7 @@ Accept wildcard characters: False
 
 ### -NDRDiagnosticInfoEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is functional only in on-premises Exchange.
 
@@ -488,7 +488,7 @@ Accept wildcard characters: False
 
 ### -NDREnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The NDREnabled parameter specifies whether to allow non-delivery reports (also known NDRs or bounce messages) from your organization to recipients in the remote domain. Valid values are:
 
@@ -509,7 +509,7 @@ Accept wildcard characters: False
 
 ### -NonMimeCharacterSet
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The NonMimeCharacterSet parameter specifies a character set for plain text messages without defined character sets that are sent from your organization to recipients in the remote domain. Valid values are:
 
@@ -533,7 +533,7 @@ Accept wildcard characters: False
 
 ### -PreferredInternetCodePageForShiftJis
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The PreferredInternetCodePageForShiftJis parameter specifies the specific code page to use for Shift JIS character encoding in messages that are sent to recipients in the remote domain. Valid values are:
 
@@ -556,7 +556,7 @@ Accept wildcard characters: False
 
 ### -RequiredCharsetCoverage
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RequiredCharsetCoverage parameter specifies a percentage threshold for characters in a message that must match to apply your organization's preferred character set before switching to automatic character set detection.
 
@@ -598,7 +598,7 @@ Accept wildcard characters: False
 
 ### -TargetDeliveryDomain
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The TargetDeliveryDomain parameter specifies whether the remote domain is used in cross-forest deployments to generate target email addresses for new mail users that represent users in the other organization (for example, all mailboxes hosted on Exchange Online are represented as mail users in your on-premises organization). Valid values are:
 
@@ -619,7 +619,7 @@ Accept wildcard characters: False
 
 ### -TNEFEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The TNEFEnabled parameter specifies whether Transport Neutral Encapsulation Format (TNEF) message encoding is used on messages sent to the remote domain. Valid values are:
 
@@ -641,7 +641,7 @@ Accept wildcard characters: False
 
 ### -TrustedMailInboundEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The TrustedMailInboundEnabled parameter specifies whether messages from senders in the remote domain are treated as trusted messages. Valid values are:
 
@@ -662,7 +662,7 @@ Accept wildcard characters: False
 
 ### -TrustedMailOutboundEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The TrustedMailOutboundEnabled parameter specifies whether messages sent to recipients in the remote domain are treated as trusted messages. Valid values are:
 
@@ -683,7 +683,7 @@ Accept wildcard characters: False
 
 ### -UseSimpleDisplayName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The UseSimpleDisplayName parameter specifies whether the sender's simple display name is used for the From email address in messages sent to recipients in the remote domain. Valid values are:
 
@@ -704,7 +704,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-RemoteMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Set-RemoteMailbox.md
index c561807539..8d10964e6e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-RemoteMailbox.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-RemoteMailbox.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -115,7 +115,7 @@ This example configures delivery restrictions for the mailbox in the service tha
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the remote mailbox (mail user) that you want to modify. You can use any value that uniquely identifies the mail user. For example:
 
@@ -142,7 +142,7 @@ Accept wildcard characters: False
 
 ### -AcceptMessagesOnlyFrom
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AcceptMessagesOnlyFrom parameter specifies who is allowed to send messages to this recipient. Messages from other senders are rejected.
 
@@ -177,7 +177,7 @@ Accept wildcard characters: False
 
 ### -AcceptMessagesOnlyFromDLMembers
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AcceptMessagesOnlyFromDLMembers parameter specifies who is allowed to send messages to this recipient. Messages from other senders are rejected.
 
@@ -212,7 +212,7 @@ Accept wildcard characters: False
 
 ### -AcceptMessagesOnlyFromSendersOrMembers
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AcceptMessagesOnlyFromSendersOrMembers parameter specifies who is allowed to send messages to this recipient. Messages from other senders are rejected.
 
@@ -249,7 +249,7 @@ Accept wildcard characters: False
 
 ### -ACLableSyncedObjectEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ACLableSyncedObjectEnabled switch specifies whether the remote mailbox is an ACLableSyncedMailboxUser.
 
@@ -270,7 +270,7 @@ Accept wildcard characters: False
 
 ### -Alias
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Alias parameter specifies the Exchange alias (also known as the mail nickname) for the recipient. This value identifies the recipient as a mail-enabled object, and shouldn't be confused with multiple email addresses for the same recipient (also known as proxy addresses). A recipient can have only one Alias value. The maximum length is 64 characters.
 
@@ -306,7 +306,7 @@ Accept wildcard characters: False
 
 ### -ArchiveGuid
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -324,7 +324,7 @@ Accept wildcard characters: False
 
 ### -ArchiveName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ArchiveName parameter specifies the name of the archive mailbox. This is the name displayed to users in Outlook on the web (formerly known as Outlook Web App). If the value contains spaces, enclose the value in quotation marks (").
 
@@ -350,7 +350,7 @@ Accept wildcard characters: False
 
 ### -BypassModerationFromSendersOrMembers
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The BypassModerationFromSendersOrMembers parameter specifies who is allowed to send messages to this moderated recipient without approval from a moderator. Valid values for this parameter are individual senders and groups in your organization. Specifying a group means all members of the group are allowed to send messages to this recipient without approval from a moderator.
 
@@ -383,7 +383,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -404,7 +404,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute1
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter specifies a value for the CustomAttribute1 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -422,7 +422,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute10
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter specifies a value for the CustomAttribute10 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -440,7 +440,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute11
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter specifies a value for the CustomAttribute11 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -458,7 +458,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute12
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter specifies a value for the CustomAttribute12 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -476,7 +476,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute13
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter specifies a value for the CustomAttribute13 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -494,7 +494,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute14
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter specifies a value for the CustomAttribute14 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -512,7 +512,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute15
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter specifies a value for the CustomAttribute15 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -530,7 +530,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute2
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter specifies a value for the CustomAttribute2 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -548,7 +548,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute3
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter specifies a value for the CustomAttribute3 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -566,7 +566,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute4
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter specifies a value for the CustomAttribute4 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -584,7 +584,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute5
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter specifies a value for the CustomAttribute5 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -602,7 +602,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute6
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter specifies a value for the CustomAttribute6 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -620,7 +620,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute7
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter specifies a value for the CustomAttribute7 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -638,7 +638,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute8
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter specifies a value for the CustomAttribute8 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -656,7 +656,7 @@ Accept wildcard characters: False
 
 ### -CustomAttribute9
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter specifies a value for the CustomAttribute9 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. The maximum length is 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -674,7 +674,7 @@ Accept wildcard characters: False
 
 ### -DisplayName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DisplayName parameter specifies the display name for the mail user. The display name is visible in the Exchange admin center, address lists, and Outlook. The maximum length is 256 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -692,7 +692,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -710,7 +710,7 @@ Accept wildcard characters: False
 
 ### -EmailAddresses
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The EmailAddresses parameter specifies all email addresses (proxy addresses) for the recipient, including the primary SMTP address. In on-premises Exchange organizations, the primary SMTP address and other proxy addresses are typically set by email address policies. However, you can use this parameter to configure other proxy addresses for the recipient. For more information, see [Email address policies in Exchange Server](https://learn.microsoft.com/Exchange/email-addresses-and-address-books/email-address-policies/email-address-policies).
 
@@ -749,7 +749,7 @@ Accept wildcard characters: False
 
 ### -EmailAddressPolicyEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The EmailAddressPolicyEnabled parameter specifies whether to apply email address policies to this recipient. Valid values are:
 
@@ -770,7 +770,7 @@ Accept wildcard characters: False
 
 ### -ExchangeGuid
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExchangeGuid parameter specifies the ExchangeGuid property value of the mail user, which should match the ExchangeGuid value of the corresponding cloud mailbox.
 
@@ -790,7 +790,7 @@ Accept wildcard characters: False
 
 ### -ExtensionCustomAttribute1
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter specifies a value for the ExtensionCustomAttribute1 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas.
 
@@ -814,7 +814,7 @@ Accept wildcard characters: False
 
 ### -ExtensionCustomAttribute2
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter specifies a value for the ExtensionCustomAttribute2 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas.
 
@@ -838,7 +838,7 @@ Accept wildcard characters: False
 
 ### -ExtensionCustomAttribute3
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter specifies a value for the ExtensionCustomAttribute3 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas.
 
@@ -862,7 +862,7 @@ Accept wildcard characters: False
 
 ### -ExtensionCustomAttribute4
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter specifies a value for the ExtensionCustomAttribute4 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas.
 
@@ -886,7 +886,7 @@ Accept wildcard characters: False
 
 ### -ExtensionCustomAttribute5
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter specifies a value for the ExtensionCustomAttribute5 property on the recipient. You can use this property to store custom information about the recipient, and to identify the recipient in filters. You can specify up to 1300 values separated by commas.
 
@@ -928,7 +928,7 @@ Accept wildcard characters: False
 
 ### -HiddenFromAddressListsEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The HiddenFromAddressListsEnabled parameter specifies whether this recipient is visible in address lists. Valid values are:
 
@@ -949,7 +949,7 @@ Accept wildcard characters: False
 
 ### -IgnoreDefaultScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange PowerShell session, and to use the entire forest as the scope. You don't need to specify a value with this switch.
 
@@ -972,7 +972,7 @@ Accept wildcard characters: False
 
 ### -ImmutableId
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ImmutableId parameter is used by GAL synchronization (GALSync) and specifies a unique and immutable identifier in the form of an SMTP address for an Exchange mailbox used for federated delegation when requesting Security Assertion Markup Language (SAML) tokens. If federation is configured for this mailbox and you don't set this parameter when you create the mailbox, Exchange creates the value for the immutable ID based upon the mailbox's ExchangeGUID and the federated account namespace, for example, 7a78e7c8-620e-4d85-99d3-c90d90f29699@mail.contoso.com.
 
@@ -992,7 +992,7 @@ Accept wildcard characters: False
 
 ### -MailTip
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MailTip parameter specifies the custom MailTip text for this recipient. The MailTip is shown to senders when they start drafting an email message to this recipient. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -1015,7 +1015,7 @@ Accept wildcard characters: False
 
 ### -MailTipTranslations
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MailTipTranslations parameter specifies additional languages for the custom MailTip text that's defined by the MailTip parameter. HTML tags are automatically added to the MailTip translation, additional HTML tags aren't supported, and the length of the MailTip translation can't exceed 175 displayed characters.
 
@@ -1041,7 +1041,7 @@ Accept wildcard characters: False
 
 ### -ModeratedBy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ModeratedBy parameter specifies one or more moderators for this recipient. A moderator approves messages sent to the recipient before the messages are delivered. A moderator must be a mailbox, mail user, or mail contact in your organization. You can use any value that uniquely identifies the moderator. For example:
 
@@ -1072,7 +1072,7 @@ Accept wildcard characters: False
 
 ### -ModerationEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ModerationEnabled parameter specifies whether moderation is enabled for this recipient. Valid value are:
 
@@ -1095,7 +1095,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Name parameter specifies the unique name of the mail user. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -1113,7 +1113,7 @@ Accept wildcard characters: False
 
 ### -PrimarySmtpAddress
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PrimarySmtpAddress parameter specifies the primary return email address that's used for the recipient. You can't use the EmailAddresses and PrimarySmtpAddress parameters in the same command.
 
@@ -1135,7 +1135,7 @@ Accept wildcard characters: False
 
 ### -RecoverableItemsQuota
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RecoverableItemsQuota parameter specifies the maximum size for the Recoverable Items folder of the mailbox. If the Recoverable Items folder reaches or exceeds this size, it no longer accepts messages.
 
@@ -1167,7 +1167,7 @@ Accept wildcard characters: False
 
 ### -RecoverableItemsWarningQuota
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RecoverableItemsWarningQuota parameter specifies the warning threshold for the size of the Recoverable Items folder for the mailbox. If the Recoverable Items folder reaches or exceeds this size, Exchange logs an event to the application event log.
 
@@ -1199,7 +1199,7 @@ Accept wildcard characters: False
 
 ### -RejectMessagesFrom
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RejectMessagesFrom parameter specifies who isn't allowed to send messages to this recipient. Messages from these senders are rejected.
 
@@ -1234,7 +1234,7 @@ Accept wildcard characters: False
 
 ### -RejectMessagesFromDLMembers
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RejectMessagesFromDLMembers parameter specifies who isn't allowed to send messages to this recipient. Messages from these senders are rejected.
 
@@ -1269,7 +1269,7 @@ Accept wildcard characters: False
 
 ### -RejectMessagesFromSendersOrMembers
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RejectMessagesFromSendersOrMembers parameter specifies who isn't allowed to send messages to this recipient. Messages from these senders are rejected.
 
@@ -1306,7 +1306,7 @@ Accept wildcard characters: False
 
 ### -RemoteRoutingAddress
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RemoteRoutingAddress parameter specifies the SMTP address of the mailbox in the service that's associated with this mail user.
 
@@ -1326,7 +1326,7 @@ Accept wildcard characters: False
 
 ### -RemovePicture
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RemovePicture switch removes the picture from the mail user. You don't need to specify a value with this switch.
 
@@ -1346,7 +1346,7 @@ Accept wildcard characters: False
 
 ### -RemoveSpokenName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RemoveSpokenName switch removes the spoken name from the mail user. You don't need to specify a value with this switch.
 
@@ -1366,7 +1366,7 @@ Accept wildcard characters: False
 
 ### -RequireSenderAuthenticationEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RequireSenderAuthenticationEnabled parameter specifies whether to accept messages only from authenticated (internal) senders. Valid values are:
 
@@ -1389,7 +1389,7 @@ Accept wildcard characters: False
 
 ### -ResetPasswordOnNextLogon
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ResetPasswordOnNextLogon parameter specifies whether the user must change their password the next time they log on. Valid values are:
 
@@ -1410,7 +1410,7 @@ Accept wildcard characters: False
 
 ### -SamAccountName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SamAccountName parameter (also known as the pre-Windows 2000 user account or group name) specifies an object identifier that's compatible with older versions of Microsoft Windows client and server operating systems. The value can contain letters, numbers, spaces, periods (.), and the following characters: !, #, $, %, ^, &, -, \_, {, }, and ~. The last character can't be a period. Unicode characters are allowed, but accented characters might generate collisions (for example, o and ö match). The maximum length is 20 characters.
 
@@ -1428,7 +1428,7 @@ Accept wildcard characters: False
 
 ### -SendModerationNotifications
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SendModerationNotifications parameter specifies when moderation notification messages are sent. Valid values are:
 
@@ -1454,7 +1454,7 @@ Accept wildcard characters: False
 
 ### -Type
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Type parameter specifies the type for the mailbox in the service. Valid values are:
 
@@ -1483,7 +1483,7 @@ Accept wildcard characters: False
 
 ### -UserPrincipalName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The UserPrincipalName parameter specifies the logon name for the user account. The UPN uses an email address format: `username@domain`. Typically, the domain value is the domain where the user account resides.
 
@@ -1501,7 +1501,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
@@ -1519,7 +1519,7 @@ Accept wildcard characters: False
 
 ### -WindowsEmailAddress
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WindowsEmailAddress parameter specifies the Windows email address for this recipient. This is a common Active Directory attribute that's present in all environments, including environments without Exchange. Using the WindowsEmailAddress parameter on a recipient has one of the following results:
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ResourceConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-ResourceConfig.md
index 5c934191af..b47989e46f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ResourceConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ResourceConfig.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
 Locale: en-US
@@ -54,7 +54,7 @@ This example adds the custom resource property Room/TV and removes Equipment/Lap
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -75,7 +75,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -95,7 +95,7 @@ Accept wildcard characters: False
 
 ### -ResourcePropertySchema
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ResourcePropertySchema parameter specifies the custom resource property that you want to make available to room or equipment mailboxes. This parameter uses the syntax `Room/<Text>` or `Equipment/<Text>` where the `<Text>` value doesn't contain spaces. For example, `Room/Whiteboard` or `Equipment/Van`. You can specify multiple values separated by commas.
 
@@ -117,7 +117,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ResubmitRequest.md b/exchange/exchange-ps/ExchangePowerShell/Set-ResubmitRequest.md
index ac27df96d6..6f968b3786 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ResubmitRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ResubmitRequest.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -45,7 +45,7 @@ This example disables the resubmit request with the identity 8.
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the resubmit request you want to modify. Each resubmit request is identified by an incremented integer value.
 
@@ -63,7 +63,7 @@ Accept wildcard characters: False
 
 ### -Enabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Enabled parameter enables or disables an active resubmit request. Valid input for this parameter is $true or $false. Setting the value to $false disables the resubmit request.
 
@@ -81,7 +81,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -102,7 +102,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
 
@@ -127,7 +127,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-RetentionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-RetentionPolicy.md
index be27958761..28d1b59219 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-RetentionPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-RetentionPolicy.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
 Locale: en-US
@@ -47,13 +47,13 @@ Set-RetentionPolicy "MyPolicy" -RetentionPolicyTagLinks "MyRetentionPolicyTag"
 
 This example modifies the policy MyPolicy to link the retention policy tag MyRetentionPolicyTag with it.
 
-The Identity parameter is a positional parameter. Positional parameters can be used without the label (Identity). For more information about positional parameters, see [About Parameters](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_parameters).
+The Identity parameter is positional, which means you can use it without the -Identity label in the supported location in the command (in this case, first).  For more information about positional parameters, see [About Parameters](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_parameters).
 
 ## PARAMETERS
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the name, distinguished name (DN), or GUID of the retention policy.
 
@@ -71,7 +71,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -92,7 +92,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -112,7 +112,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -185,7 +185,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Name parameter specifies a unique name for the retention policy.
 
@@ -203,7 +203,7 @@ Accept wildcard characters: False
 
 ### -RetentionId
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RetentionId parameter specifies the identity of the retention policy to make sure mailboxes moved between two Exchange organizations continue to have the same retention policy applied to them. For example, in a cross-forest deployment or in a cross-premises deployment, when a mailbox is moved from an on-premises Exchange server to the cloud, or a cloud-based mailbox is moved to an on-premises Exchange server, this parameter is used to make sure the same retention policy is applied to the mailbox.
 
@@ -223,7 +223,7 @@ Accept wildcard characters: False
 
 ### -RetentionPolicyTagLinks
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RetentionPolicyTagLinks parameter specifies the identity of retention policy tags to associate with the retention policy. Mailboxes that get a retention policy applied have retention tags linked with that retention policy.
 
@@ -241,7 +241,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-RetentionPolicyTag.md b/exchange/exchange-ps/ExchangePowerShell/Set-RetentionPolicyTag.md
index cb2e87b762..b741d5fba9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-RetentionPolicyTag.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-RetentionPolicyTag.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
 Locale: en-US
@@ -93,7 +93,7 @@ This example makes optional retention tags available to user Terry Adams using t
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the name, distinguished name (DN), or GUID of the retention policy tag to be modified.
 
@@ -111,7 +111,7 @@ Accept wildcard characters: False
 
 ### -Mailbox
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Mailbox parameter specifies a mailbox for assigning opt-in tags. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -162,7 +162,7 @@ Accept wildcard characters: False
 
 ### -AgeLimitForRetention
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AgeLimitForRetention parameter specifies the age at which retention is enforced on an item. The age limit corresponds to the number of days from the date the item was delivered, or the date an item was created if it wasn't delivered. If this parameter isn't present and the RetentionEnabled parameter is set to $true, an error is returned.
 
@@ -180,7 +180,7 @@ Accept wildcard characters: False
 
 ### -Comment
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Comment parameter specifies a comment for the retention policy tag.
 
@@ -198,7 +198,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -219,7 +219,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -239,7 +239,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -299,7 +299,7 @@ Accept wildcard characters: False
 
 ### -LegacyManagedFolder
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The LegacyManagedFolder parameter specifies the name of a managed folder. The retention tag is created by using retention settings from the managed folder and its managed content settings. You can use this parameter to create retention tags based on existing managed folders to migrate users from managed folder mailbox policies to retention policies.
 
@@ -317,7 +317,7 @@ Accept wildcard characters: False
 
 ### -LocalizedComment
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The LocalizedComment parameter specifies the localized comment and language for the retention policy tag. This comment is displayed in Microsoft Outlook based on the user's locale.
 
@@ -335,7 +335,7 @@ Accept wildcard characters: False
 
 ### -LocalizedRetentionPolicyTagName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The LocalizedRetentionPolicyTagName parameter specifies a localized name for the retention policy tag. This name is displayed in Outlook based on the user's locale.
 
@@ -353,7 +353,7 @@ Accept wildcard characters: False
 
 ### -MessageClass
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MessageClass parameter specifies the message type to which the tag applies. If not specified, the default value is set to \*.
 
@@ -397,7 +397,7 @@ Accept wildcard characters: False
 
 ### -MustDisplayCommentEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MustDisplayCommentEnabled parameter specifies whether the comment can be hidden. The default value is $true.
 
@@ -415,7 +415,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Name parameter specifies the name of the retention policy tag.
 
@@ -433,7 +433,7 @@ Accept wildcard characters: False
 
 ### -OptionalInMailbox
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The OptionalInMailbox parameter is used with the Mailbox parameter to assign personal tags to the mailbox. You can use this parameter to make available to a user a personal tag that isn't assigned to the retention policy applied to the specified mailbox. You can specify multiple personal tags separated by commas.
 
@@ -451,7 +451,7 @@ Accept wildcard characters: False
 
 ### -RetentionAction
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RetentionAction parameter specifies the action for the retention policy. Valid values are:
 
@@ -478,7 +478,7 @@ Accept wildcard characters: False
 
 ### -RetentionEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RetentionEnabled parameter specifies whether the tag is enabled. When set to $false, the tag is disabled and no retention action is taken on messages that have the tag applied.
 
@@ -500,7 +500,7 @@ Accept wildcard characters: False
 
 ### -RetentionId
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RetentionId parameter specifies an alternate tag ID to ensure the retention tag found on mailbox items tagged in one Exchange organization matches the tag when the mailbox is moved to another Exchange organization (for example, in a cross-forest deployment or in a cross-premises deployment, when a mailbox is moved from an on-premises Exchange server to the cloud, or a cloud-based mailbox is moved to an on-premises Exchange server).
 
@@ -520,7 +520,7 @@ Accept wildcard characters: False
 
 ### -SystemTag
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SystemTag parameter specifies whether the retention policy tag is created for internal Exchange functionality.
 
@@ -538,7 +538,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-RoleAssignmentPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-RoleAssignmentPolicy.md
index c7e9c8a83c..dd117830db 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-RoleAssignmentPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-RoleAssignmentPolicy.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -52,7 +52,7 @@ This example changes the default assignment policy. New mailboxes or mailboxes m
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the name of the assignment policy to modify. If the name contains spaces, enclose the name in quotation marks (").
 
@@ -70,7 +70,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -91,7 +91,7 @@ Accept wildcard characters: False
 
 ### -Description
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Description parameter specifies the description that's displayed when the role assignment policy is viewed using the Get-RoleAssignmentPolicy cmdlet. Enclose the description in quotation marks (").
 
@@ -109,7 +109,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -131,7 +131,7 @@ Accept wildcard characters: False
 
 ### -IsDefault
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IsDefault switch makes the assignment policy the default assignment policy. You don't need to specify a value with this switch.
 
@@ -151,7 +151,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Name parameter specifies the new name of the assignment policy. If the assignment policy name contains spaces, enclose the name in quotation marks ("). The maximum length of the name is 64 characters.
 
@@ -169,7 +169,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-RoleGroup.md b/exchange/exchange-ps/ExchangePowerShell/Set-RoleGroup.md
index 085ea64b34..e67458b4f8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-RoleGroup.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-RoleGroup.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -91,7 +91,7 @@ The first command retrieves the credentials using the Get-Credential cmdlet and
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The Identity parameter specifies the name of the role group to modify. If the name contains spaces, enclose the name in quotation marks (").
 
@@ -109,7 +109,7 @@ Accept wildcard characters: False
 
 ### -LinkedDomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -131,7 +131,7 @@ Accept wildcard characters: False
 
 ### -LinkedForeignGroup
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -155,7 +155,7 @@ Accept wildcard characters: False
 
 ### -BypassSecurityGroupManagerCheck
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The BypassSecurityGroupManagerCheck switch specifies whether to allow a user who isn't an owner of the group to modify or delete the group. You don't need to specify a value with this switch.
 
@@ -178,7 +178,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -199,7 +199,7 @@ Accept wildcard characters: False
 
 ### -Description
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The Description parameter specifies the description displayed when the role group is viewed using the Get-RoleGroup cmdlet. Enclose the description in quotation marks (").
 
@@ -217,7 +217,7 @@ Accept wildcard characters: False
 
 ### -DisplayName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The DisplayName parameter specifies the friendly name of the role group. If the name contains spaces, enclose the name in quotation marks ("). This parameter has a maximum length of 256 characters.
 
@@ -235,7 +235,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -277,7 +277,7 @@ Accept wildcard characters: False
 
 ### -LinkedCredential
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -299,7 +299,7 @@ Accept wildcard characters: False
 
 ### -ManagedBy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ManagedBy parameter specifies the users or USG who can modify the configuration of a role group or add or remove members to or from a role group. The list you specify with this parameter overwrites the existing ManagedBy list. To add or remove individual role group managers, and for more information about modifying multivalued properties, see [Modifying multivalued properties](https://learn.microsoft.com/exchange/modifying-multivalued-properties-exchange-2013-help).
 
@@ -321,7 +321,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The Name parameter specifies the name of the role group. The name can contain up to 64 characters. If the name contains spaces, enclose the name in quotation marks (").
 
@@ -359,7 +359,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The WhatIf switch doesn't work in Security & Compliance PowerShell.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-RpcClientAccess.md b/exchange/exchange-ps/ExchangePowerShell/Set-RpcClientAccess.md
index 0a9bafb950..f89351c27e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-RpcClientAccess.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-RpcClientAccess.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -62,7 +62,7 @@ This example prevents Outlook Anywhere connections by Outlook 2013 clients that
 
 ### -Server
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Client Access server where you want to run this command. You can use any value that uniquely identifies the server. For example:
 
@@ -85,7 +85,7 @@ Accept wildcard characters: False
 
 ### -BlockedClientVersions
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The BlockedClientVersions parameter specifies the RPC client versions that aren't allowed to connect to the specified Exchange server. For example, the Microsoft Exchange RPC Client Access service rejects an Outlook Anywhere connection if the version of Outlook is the specified value, or is in the specified range.
 
@@ -115,7 +115,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -136,7 +136,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -154,7 +154,7 @@ Accept wildcard characters: False
 
 ### -EncryptionRequired
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The EncryptionRequired parameter specifies whether encryption is required for RPC client connections. Valid values are:
 
@@ -175,7 +175,7 @@ Accept wildcard characters: False
 
 ### -MaximumConnections
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MaximumConnections parameter specifies the maximum number of concurrent client connections that are allowed by the Microsoft Exchange RPC Client Access service. The default value is 65536.
 
@@ -195,7 +195,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Name parameter specifies the name of the configuration object in Active Directory. By default, this parameter is set to RpcClientAccess.
 
@@ -213,7 +213,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-SearchDocumentFormat.md b/exchange/exchange-ps/ExchangePowerShell/Set-SearchDocumentFormat.md
index 71bbfc94b9..fe00863c4d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-SearchDocumentFormat.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-SearchDocumentFormat.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -49,7 +49,7 @@ This command disables the Zip file format for indexing by Exchange Search.
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the identity of the file format.
 
@@ -67,7 +67,7 @@ Accept wildcard characters: False
 
 ### -Enabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Enabled parameter specifies whether the file format is enabled. Set the parameter to $false to disable the format for content indexing.
 
@@ -85,7 +85,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -106,7 +106,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
 
@@ -131,7 +131,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-SendConnector.md b/exchange/exchange-ps/ExchangePowerShell/Set-SendConnector.md
index 0bf6785c3c..1fa5337f50 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-SendConnector.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-SendConnector.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -81,7 +81,7 @@ This example makes the following configuration changes to the Send connector nam
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The GUID or connector name that represents the Send connector you want to modify.
 
@@ -99,7 +99,7 @@ Accept wildcard characters: False
 
 ### -AddressSpaces
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AddressSpaces parameter specifies the domain names to which the Send connector routes mail. The complete syntax for entering each address space is: `AddressSpaceType:AddressSpace;AddressSpaceCost`.
 
@@ -137,7 +137,7 @@ Accept wildcard characters: False
 
 ### -AuthenticationCredential
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AuthenticationCredential parameter specifies the username and password that's required to use the connector.
 
@@ -157,7 +157,7 @@ Accept wildcard characters: False
 
 ### -CloudServicesMailEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 **Note**: We recommend that you don't use this parameter unless you are directed to do so by Microsoft Customer Service and Support, or by specific product documentation. Instead, use the Hybrid Configuration wizard to configure mail flow between your on-premises and cloud organizations. For more information, see [Hybrid Configuration wizard](https://learn.microsoft.com/exchange/hybrid-configuration-wizard).
 
@@ -182,7 +182,7 @@ Accept wildcard characters: False
 
 ### -Comment
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 TheComment parameter specifies an optional comment. You must enclose the Comment parameter in quotation marks ("), for example: "this is an admin note".
 
@@ -200,7 +200,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -221,7 +221,7 @@ Accept wildcard characters: False
 
 ### -ConnectorType
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ConnectorType parameter specifies whether the connector is used in hybrid deployments to send messages to Microsoft 365. Valid values are:
 
@@ -242,7 +242,7 @@ Accept wildcard characters: False
 
 ### -ConnectionInactivityTimeOut
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ConnectionInactivityTimeOut parameter specifies the maximum time an idle connection can remain open. The default value is ten minutes.
 
@@ -264,7 +264,7 @@ Accept wildcard characters: False
 
 ### -DNSRoutingEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DNSRoutingEnabled parameter specifies whether the Send connector uses Domain Name System (DNS) to route mail. Valid values for this parameter are $true or $false. The default value is $true. If you specify a SmartHosts parameter, the DNSRoutingEnabled parameter must be $false.
 
@@ -282,7 +282,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -302,7 +302,7 @@ Accept wildcard characters: False
 
 ### -DomainSecureEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainSecureEnabled parameter is part of the process to enable mutual Transport Layer Security (TLS) authentication for the domains serviced by this Send connector. Mutual TLS authentication functions correctly only when the following conditions are met:
 
@@ -333,7 +333,7 @@ Accept wildcard characters: False
 
 ### -Enabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Enabled parameter specifies whether to enable the Send connector to process email messages. Valid values are $true or $false. The default value is $true.
 
@@ -351,7 +351,7 @@ Accept wildcard characters: False
 
 ### -ErrorPolicies
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ErrorPolicies parameter specifies how communication errors are treated. Possible values are the following:
 
@@ -378,7 +378,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -398,7 +398,7 @@ Accept wildcard characters: False
 
 ### -ForceHELO
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ForceHELO parameter specifies whether HELO is sent instead of the default EHLO. Valid values are $true or $false. The default value is $false.
 
@@ -416,7 +416,7 @@ Accept wildcard characters: False
 
 ### -Fqdn
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Fqdn parameter specifies the FQDN used as the source server for connected messaging servers that use the Send connector to receive outgoing messages. The value of this parameter is displayed to connected messaging servers whenever a source server name is required, as in the following examples:
 
@@ -440,7 +440,7 @@ Accept wildcard characters: False
 
 ### -FrontendProxyEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The FrontendProxyEnabled parameter routes outbound messages through the CAS server, where destination specific routing, such as DNS or IP address, is set, when the parameter is set to $true.
 
@@ -458,7 +458,7 @@ Accept wildcard characters: False
 
 ### -IgnoreSTARTTLS
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IgnoreSTARTTLS parameter specifies whether to ignore the StartTLS option offered by a remote sending server. This parameter is used with remote domains. This parameter must be set to $false if the RequireTLS parameter is set to $true. Valid values for this parameter are $true or $false.
 
@@ -496,7 +496,7 @@ Accept wildcard characters: False
 
 ### -IsScopedConnector
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IsScopedConnector parameter specifies the availability of the connector to other Mailbox servers with the Transport service. When the value of this parameter is $false, the connector can be used by all Mailbox servers in the Exchange organization. When the value of this parameter is $true, the connector can only be used by Transport service on Mailbox servers in the same Active Directory site. The default value is $false.
 
@@ -546,7 +546,7 @@ Accept wildcard characters: False
 
 ### -MaxMessageSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MaxMessageSize parameter specifies the maximum size of a message that can pass through a connector. The default value is 25 MB.
 
@@ -576,7 +576,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Name parameter specifies the administrator-supplied name of the connector. You must enclose the Name parameter in quotation marks (") if the name contains spaces. For example, "New Send Connector".
 
@@ -594,7 +594,7 @@ Accept wildcard characters: False
 
 ### -Port
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Port parameter specifies the port number for smart host forwarding, if you specify a value in the SmartHosts parameter. The valid input range is an integer from 0 through 65535. The default value is 25. In most organizations, the port number is set to 25.
 
@@ -612,7 +612,7 @@ Accept wildcard characters: False
 
 ### -ProtocolLoggingLevel
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ProtocolLoggingLevel parameter specifies whether to enable protocol logging. Verbose enables protocol logging. None disables protocol logging. The location of the Send connector protocol logs for all Send connectors configured in the Transport service on a Mailbox server or on an Edge server is specified with the SendProtocolLogPath parameter of the Set-TransportService cmdlet.
 
@@ -630,7 +630,7 @@ Accept wildcard characters: False
 
 ### -RequireOorg
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -648,7 +648,7 @@ Accept wildcard characters: False
 
 ### -RequireTLS
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RequireTLS parameter specifies whether all messages sent through this connector must be transmitted using TLS. The default value is $false.
 
@@ -666,7 +666,7 @@ Accept wildcard characters: False
 
 ### -SmartHostAuthMechanism
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SmartHostAuthMechanism parameter specifies the smart host authentication mechanism to use for authentication with a remote server. Use this parameter only when a smart host is configured and the DNSRoutingEnabled parameter is set to $false. Valid values are None, BasicAuth, BasicAuthRequireTLS, ExchangeServer, and ExternalAuthoritative. All values are mutually exclusive. If you select BasicAuth or BasicAuthRequireTLS, you must use the AuthenticationCredential parameter to specify the authentication credential.
 
@@ -684,7 +684,7 @@ Accept wildcard characters: False
 
 ### -SmartHosts
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SmartHosts parameter specifies the smart hosts the Send connector uses to route mail. This parameter is required if you set the DNSRoutingEnabled parameter to $false and it must be specified on the same command line. The SmartHosts parameter takes one or more FQDNs, such as server.contoso.com, or one or more IP addresses, or a combination of both FQDNs and IP addresses. If you enter an IP address, you must enter the IP address as a literal. For example, 10.10.1.1. The smart host identity can be the FQDN of a smart-host server, a mail exchanger (MX) record, or an address (A) record. If you configure an FQDN as the smart host identity, the source server for the Send connector must be able to use DNS name resolution to locate the smart-host server.
 
@@ -706,7 +706,7 @@ Accept wildcard characters: False
 
 ### -SmtpMaxMessagesPerConnection
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SmtpMaxMessagesPerConnection parameter specifies the maximum number of messages the server can send per connection.
 
@@ -724,7 +724,7 @@ Accept wildcard characters: False
 
 ### -SourceIPAddress
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SourceIPAddress parameter specifies the local IP address to use as the endpoint for an SMTP connection to a remote messaging server. The default IP address is 0.0.0.0. This value means that the server can use any available local IP address. This parameter is valid only for Send connectors configured on an Edge server.
 
@@ -742,7 +742,7 @@ Accept wildcard characters: False
 
 ### -SourceTransportServers
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SourceTransportServers parameter specifies the names of the Mailbox servers that can use this Send connector. This parameter isn't valid for Send connectors configured on an Edge server.
 
@@ -764,7 +764,7 @@ Accept wildcard characters: False
 
 ### -TlsAuthLevel
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TlsAuthLevel parameter specifies the TLS authentication level that is used for outbound TLS connections established by this Send connector. Valid values are:
 
@@ -788,7 +788,7 @@ Accept wildcard characters: False
 
 ### -TlsCertificateName
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TlsCertificateName parameter specifies the X.509 certificate to use for TLS encryption. A valid value for this parameter is `"<I>X.500Issuer<S>X.500Subject"`. The X.500Issuer value is found in the certificate's Issuer field, and the X.500Subject value is found in the certificate's Subject field. You can find these values by running the Get-ExchangeCertificate cmdlet. Or, after you run Get-ExchangeCertificate to find the thumbprint value of the certificate, run the command `$TLSCert = Get-ExchangeCertificate -Thumbprint <Thumbprint>`, run the command `$TLSCertName = "<I>$($TLSCert.Issuer)<S>$($TLSCert.Subject)"`, and then use the value $TLSCertName for this parameter.
 
@@ -806,7 +806,7 @@ Accept wildcard characters: False
 
 ### -TlsDomain
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TlsDomain parameter specifies the domain name that the Send connector uses to verify the FQDN of the target certificate when establishing a TLS secured connection.
 
@@ -831,7 +831,7 @@ Accept wildcard characters: False
 
 ### -UseExternalDNSServersEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The UseExternalDNSServersEnabled parameter specifies whether this Send connector uses the external DNS list specified by the ExternalDNSServers parameter of the Set-TransportService cmdlet. The default value is $false.
 
@@ -849,7 +849,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-SenderFilterConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-SenderFilterConfig.md
index dd199ee3db..e5828cb5d1 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-SenderFilterConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-SenderFilterConfig.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailControl-Help.xml
 Locale: en-US
@@ -59,7 +59,7 @@ It adds user1@contoso.com and user2@contoso.com to the blocked senders list with
 
 ### -Action
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Action parameter specifies the action that the Sender Filter agent takes on messages from blocked senders or domains. Valid input for this parameter is StampStatus or Reject. The default value is Reject.
 
@@ -77,7 +77,7 @@ Accept wildcard characters: False
 
 ### -BlankSenderBlockingEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The BlankSenderBlockingEnabled parameter blocks or allows messages that don't contain a sender value in the SMTP command MAIL FROM. Valid input for this parameter is $true or $false. The default value is $false.
 
@@ -95,7 +95,7 @@ Accept wildcard characters: False
 
 ### -BlockedDomains
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The BlockedDomains parameter specifies the domain names to block. When the Sender Filter agent encounters a message from a domain on this list, the Sender Filter agent takes the action specified by the Action parameter.
 
@@ -121,7 +121,7 @@ Accept wildcard characters: False
 
 ### -BlockedDomainsAndSubdomains
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The BlockedDomainsAndSubdomains parameter specifies the domain names to block. When the Sender Filter agent encounters a message from a domain on this list, or from any of the domain's subdomains, the Sender Filter agent takes the action specified by the Action parameter.
 
@@ -147,7 +147,7 @@ Accept wildcard characters: False
 
 ### -BlockedSenders
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The BlockedSenders parameter specifies one or more SMTP email addresses to block. When the Sender Filter agent encounters a message from a sender on this list, the Sender Filter agent takes the action specified by the Action parameter.
 
@@ -171,7 +171,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -192,7 +192,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -212,7 +212,7 @@ Accept wildcard characters: False
 
 ### -Enabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Enabled parameter enables or disables sender filtering on your Exchange server. Valid input for this parameter is $true or $false. The default value is $true.
 
@@ -230,7 +230,7 @@ Accept wildcard characters: False
 
 ### -ExternalMailEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExternalMailEnabled parameter enables or disables sender filtering on unauthenticated connections from external messaging servers. Valid input for this parameter is $true or $false. The default value is $true.
 
@@ -248,7 +248,7 @@ Accept wildcard characters: False
 
 ### -InternalMailEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The InternalMailEnabled parameter enables or disables sender filtering on authenticated connections from authoritative domains in your organization. Valid input for this parameter is $true or $false. The default value is $false.
 
@@ -266,7 +266,7 @@ Accept wildcard characters: False
 
 ### -RecipientBlockedSenderAction
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RecipientBlockedSenderAction parameter specifies the action that the Sender Filter agent takes on messages received from blocked senders that are defined by SafeList aggregation. SafeList aggregation adds blocked senders that are defined by your users in Microsoft Outlook or Outlook on the web to the Blocked Senders list that's used by the Sender Filter agent.
 
@@ -286,7 +286,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-SenderIdConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-SenderIdConfig.md
index 92263d316d..0e2577dcff 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-SenderIdConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-SenderIdConfig.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailControl-Help.xml
 Locale: en-US
@@ -55,7 +55,7 @@ This example makes the following modifications to the Sender ID configuration:
 
 ### -BypassedRecipients
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The BypassedRecipients parameter specifies one or more SMTP email addresses. Messages bound for the email addresses listed in this parameter are excluded from processing by the Sender ID agent. You can specify multiple values separated by commas. You can enter a maximum of 100 email addresses.
 
@@ -73,7 +73,7 @@ Accept wildcard characters: False
 
 ### -BypassedSenderDomains
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The BypassedSenderDomains parameter specifies one or more domain names. Messages that originate from the domains listed in this parameter are excluded from processing by the Sender ID agent. You can specify multiple values separated by commas. You can enter a maximum of 100 domain names.
 
@@ -91,7 +91,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -112,7 +112,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -132,7 +132,7 @@ Accept wildcard characters: False
 
 ### -Enabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Enabled parameter specifies whether the Sender ID agent is enabled on the computer on which you're running the command. Valid input for the Enabled parameter is $true or $false. The default setting is $true. When the Enabled parameter is set to $true, the Sender ID agent is enabled on the computer on which you're running the command.
 
@@ -150,7 +150,7 @@ Accept wildcard characters: False
 
 ### -ExternalMailEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExternalMailEnabled parameter specifies whether all messages from unauthenticated connections external to your organization are passed through the Sender ID agent for processing. Valid input for the ExternalMailEnabled parameter is $true or $false. The default setting is $true. When the ExternalMailEnabled parameter is set to $true, all messages from unauthenticated connections external to your organization are passed through the Sender ID agent for processing.
 
@@ -168,7 +168,7 @@ Accept wildcard characters: False
 
 ### -InternalMailEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The InternalMailEnabled parameter specifies whether all messages from authenticated sender domains that belong to authoritative domains in your enterprise are passed through the Sender ID agent for processing. Valid input for the InternalMailEnabled parameter is $true or $false. The default setting is $false. When the InternalMailEnabled parameter is set to $true, all messages from authenticated sender domains that belong to authoritative domains in your enterprise are passed through the Sender ID agent for processing.
 
@@ -186,7 +186,7 @@ Accept wildcard characters: False
 
 ### -SpoofedDomainAction
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SpoofedDomainAction parameter specifies the action that the Sender ID agent takes on the message when the sender domain shows evidence of being spoofed. The SpoofedDomainAction parameter takes the following values: StampStatus, Reject or Delete. The default value is StampStatus.
 
@@ -204,7 +204,7 @@ Accept wildcard characters: False
 
 ### -TempErrorAction
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TempErrorAction parameter specifies the action that the Sender ID agent takes on the message when a Sender ID status of TempError is returned. The TempErrorAction parameter takes the following values: StampStatus, Reject or Delete. The default value is StampStatus.
 
@@ -222,7 +222,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-SenderReputationConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-SenderReputationConfig.md
index 676c164d8d..d31d0a7da9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-SenderReputationConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-SenderReputationConfig.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailControl-Help.xml
 Locale: en-US
@@ -58,7 +58,7 @@ It sets the number of hours that senders are put on the blocked senders list to
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -79,7 +79,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -99,7 +99,7 @@ Accept wildcard characters: False
 
 ### -Enabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Enabled parameter enables or disables sender reputation on the Exchange server. Valid values are:
 
@@ -120,7 +120,7 @@ Accept wildcard characters: False
 
 ### -ExternalMailEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExternalMailEnabled parameter allows or prevents sender reputation from processing messages from unauthenticated connections that are external to your Exchange organization. Valid values are:
 
@@ -141,7 +141,7 @@ Accept wildcard characters: False
 
 ### -InternalMailEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The InternalMailEnabled parameter allows or prevents sender reputation from processing messages from authenticated sender domains that are authoritative domains in your Exchange organization. Valid values are:
 
@@ -162,7 +162,7 @@ Accept wildcard characters: False
 
 ### -OpenProxyDetectionEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The OpenProxyDetectionEnabled parameter allows or prevents sender reputation from attempting to connect to the message's source IP address to send a test message back to the Exchange server. This test determines if the sender is an open proxy server. Valid values are:
 
@@ -189,7 +189,7 @@ Accept wildcard characters: False
 
 ### -ProxyServerName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ProxyServerName parameter specifies the name or IP address of your organization's proxy server. Sender reputation uses this value to connect to the Internet for open proxy server detection.
 
@@ -209,7 +209,7 @@ Accept wildcard characters: False
 
 ### -ProxyServerPort
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ProxyServerPort parameter specifies the port number that's used by your organization's proxy server. Sender reputation uses this value to connect to the Internet for open proxy server detection.
 
@@ -229,7 +229,7 @@ Accept wildcard characters: False
 
 ### -ProxyServerType
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ProxyServerType parameter specifies the type of your organization's proxy server. Sender reputation uses this value to connect to the Internet for open proxy server detection. Valid values are:
 
@@ -256,7 +256,7 @@ Accept wildcard characters: False
 
 ### -SenderBlockingEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SenderBlockingEnabled parameter allows or prevents sender reputation from blocking senders when their sender reputation level (SRL) meets or exceeds the value of the SrlBlockThreshold parameter. Valid values are:
 
@@ -281,7 +281,7 @@ Accept wildcard characters: False
 
 ### -SenderBlockingPeriod
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SenderBlockingPeriod parameter specifies the number of hours that a sender remains on the blocked senders list when their SRL meets or exceeds the value of the SrlBlockThreshold parameter. Valid input for this parameter is an integer from 0 through 48. The default value is 24.
 
@@ -299,7 +299,7 @@ Accept wildcard characters: False
 
 ### -SrlBlockThreshold
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SrlBlockThreshold specifies the SRL rating that must be met or exceeded for sender reputation to block a sender. Valid input for this parameter is an integer from 0 through 9. The default value is 7.
 
@@ -319,7 +319,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ServerComponentState.md b/exchange/exchange-ps/ExchangePowerShell/Set-ServerComponentState.md
index c0fc8e35b1..a128777da6 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ServerComponentState.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ServerComponentState.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -63,7 +63,7 @@ The second command changes the state to Active after the maintenance is over (re
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
 
@@ -86,7 +86,7 @@ Accept wildcard characters: False
 
 ### -Component
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Component parameter specifies the component or endpoint for which you want to set the state.
 
@@ -104,7 +104,7 @@ Accept wildcard characters: False
 
 ### -Requester
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Requester parameter specifies the system requesting this state change. Valid values are:
 
@@ -128,7 +128,7 @@ Accept wildcard characters: False
 
 ### -State
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The State parameter specifies the state that you want for the component. Valid values are:
 
@@ -150,7 +150,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -171,7 +171,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -191,7 +191,7 @@ Accept wildcard characters: False
 
 ### -LocalOnly
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The LocalOnly switch specifies that the changes are written to the registry of the Exchange server only and not to Active Directory. You don't need to specify a value with this switch.
 
@@ -209,7 +209,7 @@ Accept wildcard characters: False
 
 ### -RemoteOnly
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RemoteOnly switch specifies that the changes are written to Active Directory only and not to the registry of the Exchange server. You don't need to specify a value with this switch.
 
@@ -227,7 +227,7 @@ Accept wildcard characters: False
 
 ### -TimeoutInSeconds
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -245,7 +245,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ServerMonitor.md b/exchange/exchange-ps/ExchangePowerShell/Set-ServerMonitor.md
index 987756400a..a04cf496f3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ServerMonitor.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ServerMonitor.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -45,7 +45,7 @@ This example sets the maintenance monitor on the Exch01 server.
 
 ### -Server
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
 
@@ -68,7 +68,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Name parameter specifies the monitor identity.
 
@@ -86,7 +86,7 @@ Accept wildcard characters: False
 
 ### -Repairing
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Repairing parameter specifies whether to set or clear the repairing property on a monitor.
 
@@ -106,7 +106,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -127,7 +127,7 @@ Accept wildcard characters: False
 
 ### -TargetResource
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TargetResource parameter specifies the target resource that you want to set the monitor on.
 
@@ -145,7 +145,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-SettingOverride.md b/exchange/exchange-ps/ExchangePowerShell/Set-SettingOverride.md
index 99ff89a1af..440f1e77e8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-SettingOverride.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-SettingOverride.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -55,7 +55,7 @@ This example modifies the setting override named Change OAB Generation on the se
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the setting override that you want to modify. You can use any value that uniquely identifies the override. For example:
 
@@ -77,7 +77,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -98,7 +98,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -116,7 +116,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -136,7 +136,7 @@ Accept wildcard characters: False
 
 ### -MaxVersion
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MaxVersion parameter specifies the latest version of Exchange 2016 that this override applies to (up to and including the specified value).
 
@@ -158,7 +158,7 @@ Accept wildcard characters: False
 
 ### -MinVersion
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MinVersion parameter specifies the earliest version of Exchange 2016 that this override applies to (up to and including the specified value).
 
@@ -180,7 +180,7 @@ Accept wildcard characters: False
 
 ### -Parameters
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Parameters parameter specifies one or more parameters for the override that are available for the combination of the Component and Section parameter values. This parameter uses the syntax: `@("Parameter1=Value1","Parameter2=Value2"...)`. For example:
 
@@ -201,7 +201,7 @@ Accept wildcard characters: False
 
 ### -Reason
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Reason parameter is used to provide a description of why the override was created. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -219,7 +219,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the name of the Exchange 2016 server where you want the override applied. You can specify a single Exchange 2016 server name, or an array of Exchange 2016 server name wildcards. For example, if you have three Exchange 2016 servers named Exchange01, Exchange02 and Exchange03, specify the value Exchange\* to apply the override to all of them.
 
@@ -239,7 +239,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-SharingPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-SharingPolicy.md
index 029d5a0bd5..6801283c4d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-SharingPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-SharingPolicy.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
 Locale: en-US
@@ -65,7 +65,7 @@ This example disables the sharing policy SharingPolicy01.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the identity of the sharing policy that you want to modify. You can use one of the following values:
 
@@ -88,7 +88,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -109,7 +109,7 @@ Accept wildcard characters: False
 
 ### -Default
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Default switch specifies that the sharing policy is the default sharing policy for all mailboxes. You don't need to specify a value with this switch.
 
@@ -129,7 +129,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -149,7 +149,7 @@ Accept wildcard characters: False
 
 ### -Domains
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Domains parameter specifies the domains and the associated sharing options for those domains in the sharing policy. Values for this parameter use the basic syntax: `'Domain: SharingPolicyAction'`.
 
@@ -182,7 +182,7 @@ Accept wildcard characters: False
 
 ### -Enabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Enabled parameter specifies whether to enable the sharing policy. Valid values for this parameter are $true or $false. The default is $true.
 
@@ -202,7 +202,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Name parameter specifies the unique name of the sharing policy. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -220,7 +220,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-SiteMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Set-SiteMailbox.md
index a75022387e..19c2ab872a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-SiteMailbox.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-SiteMailbox.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -63,7 +63,7 @@ This example disables the duplication of email messages in the site mailbox SMO\
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the identity of the site mailbox. You can use any value that uniquely identifies the site mailbox. For example:
 
@@ -88,7 +88,7 @@ Accept wildcard characters: False
 
 ### -Active
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Active parameter specifies whether to change the site mailbox's lifecycle status. This parameter accepts $true or $false. This parameter is intended for use only by the user interface. We recommend that you don't use this parameter in the Exchange Management Shell.
 
@@ -106,7 +106,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -127,7 +127,7 @@ Accept wildcard characters: False
 
 ### -DisplayName
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DisplayName parameter specifies the display name of the site mailbox.
 
@@ -145,7 +145,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -163,7 +163,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -183,7 +183,7 @@ Accept wildcard characters: False
 
 ### -Members
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is intended for use only by the user interface. We recommend that you don't use this parameter.
 
@@ -214,7 +214,7 @@ Accept wildcard characters: False
 
 ### -Owners
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is intended for use only by the user interface. We recommend that you don't use this parameter.
 
@@ -245,7 +245,7 @@ Accept wildcard characters: False
 
 ### -RemoveDuplicateMessages
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RemoveDuplicateMessages parameter specifies that when users post messages to a site mailbox, duplicate messages are deleted. This parameter accepts the values of $true or $false. The default value is $false.
 
@@ -263,7 +263,7 @@ Accept wildcard characters: False
 
 ### -SharePointUrl
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SharePointUrl parameter specifies the URL of the SharePoint site, for example, "https://myserver/teams/edu".
 
@@ -281,7 +281,7 @@ Accept wildcard characters: False
 
 ### -ShowInMyClient
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is intended for use only by the user interface. We recommend that you don't use this parameter.
 
@@ -301,7 +301,7 @@ Accept wildcard characters: False
 
 ### -SyncEnabled
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SyncEnabled parameter specifies whether to enable or disable synchronization for the site mailbox. Valid values are:
 
@@ -322,7 +322,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-SiteMailboxProvisioningPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-SiteMailboxProvisioningPolicy.md
index 5ff1502eb6..868f1e990d 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-SiteMailboxProvisioningPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-SiteMailboxProvisioningPolicy.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.WebClient-Help.xml
 Locale: en-US
@@ -70,7 +70,7 @@ This example changes the default provisioning policy named SM\_DefaultPolicy and
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the identity of the site mailbox provisioning policy that you want to edit. You can use any value that uniquely identifies the policy. For example:
 
@@ -92,7 +92,7 @@ Accept wildcard characters: False
 
 ### -AliasPrefix
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AliasPrefix parameter specifies the custom text prefix to add to the aliases of new site mailboxes. Valid values are:
 
@@ -113,7 +113,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -134,7 +134,7 @@ Accept wildcard characters: False
 
 ### -DefaultAliasPrefixEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DefaultAliasPrefixEnabled parameter specifies whether new site mailboxes have the default prefix text added to the alias. Valid values are:
 
@@ -157,7 +157,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -175,7 +175,7 @@ Accept wildcard characters: False
 
 ### -IsDefault
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IsDefault switch specifies that the site mailbox provisioning policy is the default policy. You don't need to specify a value with this switch.
 
@@ -195,7 +195,7 @@ Accept wildcard characters: False
 
 ### -IssueWarningQuota
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IssueWarningQuota parameter specifies the warning threshold for the size of the mailbox. If the mailbox reaches or exceeds this size, the user receives a descriptive warning message.
 
@@ -227,7 +227,7 @@ Accept wildcard characters: False
 
 ### -MaxReceiveSize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MaxReceiveSize parameter specifies the maximum size of a message that can be sent to the site mailbox. Messages larger than the maximum size are rejected.
 
@@ -256,7 +256,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Name parameter specifies the unique name of the site mailbox provisioning policy. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -274,7 +274,7 @@ Accept wildcard characters: False
 
 ### -ProhibitSendReceiveQuota
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ProhibitSendReceiveQuota parameter specifies a size limit for the mailbox. If the mailbox reaches or exceeds this size, the mailbox can't send or receive new messages. Messages sent to the mailbox are returned to the sender with a descriptive error message. This value effectively determines the maximum size of the mailbox.
 
@@ -306,7 +306,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-SmimeConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-SmimeConfig.md
index a86aa867c9..b8158b73ae 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-SmimeConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-SmimeConfig.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -72,7 +72,7 @@ This example sets the S/MIME configuration to allow users the choice of signing
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is reserved for internal Microsoft use.
 
@@ -90,7 +90,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is reserved for internal Microsoft use.
 
@@ -108,7 +108,7 @@ Accept wildcard characters: False
 
 ### -OWAAllowUserChoiceOfSigningCertificate
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The OWAAllowUserChoiceOfSigningCertificate parameter specifies whether to allow users to select the certificate to use when they digitally sign email messages in Outlook on the web.
 
@@ -128,7 +128,7 @@ Accept wildcard characters: False
 
 ### -OWAAlwaysEncrypt
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The OWAAlwaysEncrypt parameter specifies whether all outgoing messages are automatically encrypted in Outlook on the web.
 
@@ -148,7 +148,7 @@ Accept wildcard characters: False
 
 ### -OWAAlwaysSign
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The OWAAlwaysSign parameter specifies whether all outgoing messages are automatically signed in Outlook on the web.
 
@@ -168,7 +168,7 @@ Accept wildcard characters: False
 
 ### -OWABCCEncryptedEmailForking
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The OWABCCEncryptedEmailForking parameter specifies how Bcc messages are encrypted in Outlook on the web. Valid values are:
 
@@ -192,7 +192,7 @@ Accept wildcard characters: False
 
 ### -OWACheckCRLOnSend
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The OWACheckCRLOnSend parameter specifies how the certificate revocation list (CRL) check is enforced when an email message is sent in Outlook on the web. Valid values are:
 
@@ -213,7 +213,7 @@ Accept wildcard characters: False
 
 ### -OWAClearSign
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The OWAClearSign parameter specifies how email messages are signed in Outlook on the web. Valid values are:
 
@@ -236,7 +236,7 @@ Accept wildcard characters: False
 
 ### -OWACopyRecipientHeaders
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is reserved for internal Microsoft use.
 
@@ -254,7 +254,7 @@ Accept wildcard characters: False
 
 ### -OWACRLConnectionTimeout
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The OWACRLConnectionTimeout parameter specifies the time in milliseconds that Outlook on the web waits while connecting to retrieve a single CRL as part of a certificate validation operation.
 
@@ -276,7 +276,7 @@ Accept wildcard characters: False
 
 ### -OWACRLRetrievalTimeout
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The OWACRLRetrievalTimeout parameter specifies the time in milliseconds that Outlook on the web waits to retrieve all CRLs when validating a certificate.
 
@@ -298,7 +298,7 @@ Accept wildcard characters: False
 
 ### -OWADisableCRLCheck
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The OWADisableCRLCheck parameter enables or disables CRL checking in Outlook on the web. Valid values are:
 
@@ -321,7 +321,7 @@ Accept wildcard characters: False
 
 ### -OWADLExpansionTimeout
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The OWADLExpansionTimeout parameter specifies the time in milliseconds that Outlook on the web waits when sending encrypted messages to members of a distribution group that requires expansion.
 
@@ -345,7 +345,7 @@ Accept wildcard characters: False
 
 ### -OWAEncryptionAlgorithms
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The OWAEncryptionAlgorithms parameter specifies a list of symmetric encryption algorithms that are used by Outlook on the web to encrypt messages. Valid values are:
 
@@ -376,7 +376,7 @@ Accept wildcard characters: False
 
 ### -OWAEncryptTemporaryBuffers
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The OWAEncryptTemporaryBuffers parameter specifies whether the Outlook on the web client-side temporary message storage buffers are encrypted. Valid values are:
 
@@ -399,7 +399,7 @@ Accept wildcard characters: False
 
 ### -OWAForceSMIMEClientUpgrade
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The OWAForceSMIMEClientUpgrade parameter specifies whether or not users are forced to upgrade an S/MIME control that's older than their current version in Outlook on the web.
 
@@ -420,7 +420,7 @@ Accept wildcard characters: False
 
 ### -OWAIncludeCertificateChainAndRootCertificate
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The OWAIncludeCertificateChainAndRootCertificate parameter specifies whether the certificate chains and root certificates of the signing or encryption certificates are included in the message in Outlook on the web.
 
@@ -440,7 +440,7 @@ Accept wildcard characters: False
 
 ### -OWAIncludeCertificateChainWithoutRootCertificate
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The OWAIncludeCertificateChainWithoutRootCertificate parameter specifies whether the certificate chains of the signing or encryption certificates are included in messages in Outlook on the web. Valid values are:
 
@@ -461,7 +461,7 @@ Accept wildcard characters: False
 
 ### -OWAIncludeSMIMECapabilitiesInMessage
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The OWAIncludeSMIMECapabilitiesInMessage parameter specifies whether signed and encrypted messages in Outlook on the web include attributes that describe the supported encryption and signing algorithms.
 
@@ -483,7 +483,7 @@ Accept wildcard characters: False
 
 ### -OWAOnlyUseSmartCard
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The OWAOnlyUseSmartCard parameter specifies whether smartcard-based certificates are required for Outlook on the web message signing and decryption. Valid values are:
 
@@ -505,7 +505,7 @@ Accept wildcard characters: False
 
 ### -OWASenderCertificateAttributesToDisplay
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The OWASenderCertificateAttributesToDisplay parameter controls which certificate attributes are displayed when signature verification proceeds despite a mismatch between the sender's email address and the email address in sender's certificate.
 
@@ -525,7 +525,7 @@ Accept wildcard characters: False
 
 ### -OWASignedEmailCertificateInclusion
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The OWASignedEmailCertificateInclusion parameter specifies whether the sender's encryption certificate is excluded from a signed email message in Outlook on the web. Valid values are:
 
@@ -548,7 +548,7 @@ Accept wildcard characters: False
 
 ### -OWASigningAlgorithms
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The OWASigningAlgorithms parameter specifies the list of symmetric encryption signing algorithms that are used by Outlook on the web to sign messages with the S/MIME control. Valid values are:
 
@@ -580,7 +580,7 @@ Accept wildcard characters: False
 
 ### -OWATripleWrapSignedEncryptedMail
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The OWATripleWrapSignedEncryptedMail parameter specifies whether signed and encrypted email messages in Outlook on the web are triple-wrapped. Valid values are:
 
@@ -603,7 +603,7 @@ Accept wildcard characters: False
 
 ### -OWAUseKeyIdentifier
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The OWAUseKeyIdentifier parameter specifies whether a certificate's key identifier is used to encode the asymmetrically encrypted token in Outlook on the web.
 
@@ -627,7 +627,7 @@ Accept wildcard characters: False
 
 ### -OWAUseSecondaryProxiesWhenFindingCertificates
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The OWAUseSecondaryProxiesWhenFindingCertificates parameter specifies whether alternative proxies are used during the certificate search in Outlook on the web.
 
@@ -674,7 +674,7 @@ Accept wildcard characters: False
 
 ### -SMIMECertificateIssuingCA
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SMIMECertificateIssuingCA parameter specifies the serialized certificate store (SST) that contains the Certificate Authority (CA) signing and intermediate certificate information.
 
@@ -696,7 +696,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-SweepRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-SweepRule.md
index 444b193a61..e28e857498 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-SweepRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-SweepRule.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -57,7 +57,7 @@ This example modifies the existing rule that has the rule ID value x2hlsdpGmUifj
 
 ### -Identity
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the Sweep rule that you want to modify. You can use any value that uniquely identifies the rule. For example:
 
@@ -81,7 +81,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -102,7 +102,7 @@ Accept wildcard characters: False
 
 ### -DestinationFolder
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DestinationFolder parameter specifies an action for the Sweep rule that moves messages to the specified folder. The syntax is `MailboxID:\ParentFolder[\SubFolder]`.
 
@@ -135,7 +135,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -155,7 +155,7 @@ Accept wildcard characters: False
 
 ### -Enabled
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is reserved for internal Microsoft use.
 
@@ -173,7 +173,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfFlagged
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -210,7 +210,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfPinned
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -233,7 +233,7 @@ Accept wildcard characters: False
 
 ### -KeepForDays
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The KeepForDays parameter specifies an action for the Sweep rule that specifies the number of days to keep messages that match the conditions of the rule. After the number of days have passed, the messages are moved to the location that's specified by the DestinationFolder parameter (by default, the Deleted Items folder).
 
@@ -253,7 +253,7 @@ Accept wildcard characters: False
 
 ### -KeepLatest
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The KeepLatest parameter specifies an action for the Sweep rule that specifies the number of messages to keep that match the conditions of the rule. After the number of messages is exceeded, the oldest messages are moved to the location that's specified by the DestinationFolder parameter (by default, the Deleted Items folder).
 
@@ -273,7 +273,7 @@ Accept wildcard characters: False
 
 ### -Mailbox
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Mailbox parameter specifies the mailbox that contains the rule you want to modify. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -302,7 +302,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Name parameter specifies the name of the Sweep rule. If the value contains spaces, enclose the value in quotation marks.
 
@@ -320,7 +320,7 @@ Accept wildcard characters: False
 
 ### -Provider
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Provider parameter specifies the provider for the Sweep rule. If the value contains spaces, enclose the value in quotation marks.
 
@@ -340,7 +340,7 @@ Accept wildcard characters: False
 
 ### -Sender
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Sender parameter specifies a condition for the Sweep rule that looks for the specified sender in messages. For internal senders, you can use any value that uniquely identifies the sender. For example:
 
@@ -367,7 +367,7 @@ Accept wildcard characters: False
 
 ### -SourceFolder
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SourceFolder parameter specifies a condition for the Sweep rule that looks for messages in the specified folder. The syntax is `MailboxID:\ParentFolder[\SubFolder]`.
 
@@ -400,7 +400,7 @@ Accept wildcard characters: False
 
 ### -SystemCategory
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SystemCategory parameter specifies a condition for the sweep rule that looks for messages with the specified system category. System categories are available to all mailboxes in the organization. Valid values are:
 
@@ -443,7 +443,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-SystemMessage.md b/exchange/exchange-ps/ExchangePowerShell/Set-SystemMessage.md
index 77c85b47e4..7b2c217f03 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-SystemMessage.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-SystemMessage.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -55,7 +55,7 @@ This example modifies the text of the custom English WarningMailbox quota messag
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the custom system message that you want to modify. You can use any value that uniquely identifies the system message. For example:
 
@@ -122,7 +122,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -143,7 +143,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -163,7 +163,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Name parameter specifies a descriptive name for the system message. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks.
 
@@ -181,7 +181,7 @@ Accept wildcard characters: False
 
 ### -Original
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Original switch specifies whether to stop using the custom system message and start using the default system message. You don't need to specify a value with this switch.
 
@@ -203,7 +203,7 @@ Accept wildcard characters: False
 
 ### -Text
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Text parameter specifies the text in the custom system message. The text should explain why the system message was sent and any actions that the user should take.
 
@@ -242,7 +242,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-TextMessagingAccount.md b/exchange/exchange-ps/ExchangePowerShell/Set-TextMessagingAccount.md
index ee1c667d6f..550a18a31f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-TextMessagingAccount.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-TextMessagingAccount.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.WebClient-Help.xml
 Locale: en-US
@@ -60,7 +60,7 @@ This example sets the region, mobile operator and notification phone number for
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the target mailbox. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -89,7 +89,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -110,7 +110,7 @@ Accept wildcard characters: False
 
 ### -CountryRegionId
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The CountryRegionId parameter specifies the country/region that your mobile phone is registered in. Although this parameter accepts any valid ISO 3166-1 two-letter country code value (for example, AU for Australia), the following values correspond to the country/region selections that are available in the text messaging settings in Outlook on the web (formerly known as Outlook Web App):
 
@@ -134,7 +134,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -154,7 +154,7 @@ Accept wildcard characters: False
 
 ### -IgnoreDefaultScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange PowerShell session, and to use the entire forest as the scope. You don't need to specify a value with this switch.
 
@@ -177,7 +177,7 @@ Accept wildcard characters: False
 
 ### -MobileOperatorId
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MobileOperatorId parameter specifies the mobile operator (carrier) for your phone. Although this parameter accepts any random number, the following values correspond to the country/region and mobile operator selections that are available in the text messaging settings in Outlook on the web (formerly known as Outlook Web App):
 
@@ -211,7 +211,7 @@ Accept wildcard characters: False
 
 ### -NotificationPhoneNumber
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The NotificationPhoneNumber parameter specifies the telephone number to use for your text messaging notifications. This parameter uses the E.164 format: `+<CountryCode><CompleteTelephoneNumber>` (for example, `+15551234567`).
 
@@ -229,7 +229,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ThrottlingPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-ThrottlingPolicy.md
index de0f211360..14a41dfeb7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ThrottlingPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ThrottlingPolicy.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.WebClient-Help.xml
 Locale: en-US
@@ -209,9 +209,13 @@ This example modifies a throttling policy so that it restricts a user to be able
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
-The Identity parameter uniquely identifies the throttling policy that you want to modify values for. The name you use is the name of the throttling policy object in Active Directory.
+The Identity parameter specifies the throttling policy that you want to modify. You can use any value that uniquely identifies the policy. For example:
+
+- Name
+- Distinguished name (DN)
+- GUID
 
 ```yaml
 Type: ThrottlingPolicyIdParameter
@@ -227,7 +231,7 @@ Accept wildcard characters: False
 
 ### -AnonymousCutoffBalance
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AnonymousCutoffBalance parameter specifies the resource consumption limits for an anonymous user before the user is completely blocked from performing operations on a specific component after all available resources have been consumed. There is no preset default value for this parameter but it generally ranges from 600,000 to 3,000,000 in working state depending on the protocol. If for any reason, this value needs to be increased further, you must contact Microsoft Support because a higher value can affect server performance adversely.
 
@@ -245,7 +249,7 @@ Accept wildcard characters: False
 
 ### -AnonymousMaxBurst
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AnonymousMaxBurst parameter specifies the amount of time that an anonymous user can consume an elevated amount of resources before being throttled. This is measured in milliseconds. This value is set separately for each component.
 
@@ -263,7 +267,7 @@ Accept wildcard characters: False
 
 ### -AnonymousMaxConcurrency
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AnonymousMaxConcurrency parameter specifies how many anonymous connections can be made to a user's calendar data at the same time. A connection is held from the moment a request is received until a response is sent in its entirety to the requestor. If anonymous users attempt to make more concurrent requests than their policy allows, the new connection attempt fails. However, the existing connections remain valid. The AnonymousMaxConcurrency parameter has a valid range from 0 through 2147483647 inclusive. The default value is 1. To indicate that the number of concurrent connections should be unthrottled (no limit), this value should be set to $null.
 
@@ -341,7 +345,7 @@ Accept wildcard characters: False
 
 ### -AnonymousRechargeRate
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AnonymousRechargeRate parameter specifies the rate at which an anonymous user's budget is charged (budget grows by) during the budget time.
 
@@ -359,7 +363,7 @@ Accept wildcard characters: False
 
 ### -BookingSelfServiceCutoffBalance
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -377,7 +381,7 @@ Accept wildcard characters: False
 
 ### -BookingSelfServiceMaxBurst
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -395,7 +399,7 @@ Accept wildcard characters: False
 
 ### -BookingSelfServiceMaxConcurrency
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -413,7 +417,7 @@ Accept wildcard characters: False
 
 ### -BookingSelfServiceRechargeRate
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -431,7 +435,7 @@ Accept wildcard characters: False
 
 ### -ComplianceMaxExpansionDGRecipients
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ComplianceMaxExpansionDGRecipients parameter specifies the maximum number of recipients to expand in distribution groups when a discovery search is looking for a specified recipient.
 
@@ -449,7 +453,7 @@ Accept wildcard characters: False
 
 ### -ComplianceMaxExpansionNestedDGs
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ComplianceMaxExpansionNestedDGs parameter specifies the maximum number of nested distribution groups to expand when a discovery search is looking for a specified recipient.
 
@@ -467,7 +471,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -488,7 +492,7 @@ Accept wildcard characters: False
 
 ### -ConsensusCutoffBalance
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -506,7 +510,7 @@ Accept wildcard characters: False
 
 ### -ConsensusMaxBurst
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -524,7 +528,7 @@ Accept wildcard characters: False
 
 ### -ConsensusMaxConcurrency
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -542,7 +546,7 @@ Accept wildcard characters: False
 
 ### -ConsensusRechargeRate
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -560,7 +564,7 @@ Accept wildcard characters: False
 
 ### -CpaCutoffBalance
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The CpaCutoffBalance parameter specifies the resource consumption limits for a cross-premises user before that user is completely blocked from performing operations on a specific component after all available resources have been consumed. There is no preset default value for this parameter but it generally ranges from 600,000 to 3,000,000 in working state depending on the protocol. If for any reason, this value needs to be increased further, you must contact Microsoft Support because a higher value can affect server performance adversely.
 
@@ -578,7 +582,7 @@ Accept wildcard characters: False
 
 ### -CpaMaxBurst
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The CpaMaxBurst parameter specifies the amount of time that a cross-premises user can consume an elevated amount of resources before being throttled. This is measured in milliseconds. This value is set separately for each component.
 
@@ -596,7 +600,7 @@ Accept wildcard characters: False
 
 ### -CPAMaxConcurrency
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The CpaMaxConcurrency parameter specifies how many concurrent connections a cross-premises user can have against an Exchange server at one time. A connection is held from the moment a request is received until a response is sent in its entirety to the requestor. If users attempt to make more concurrent requests than their policy allows, the new connection attempt fails. However, the existing connections remain valid. The CpaMaxConcurrency parameter has a valid range from 0 through 2147483647 inclusive. To indicate that the number of concurrent connections should be unthrottled (no limit), this value should be set to $null.
 
@@ -652,7 +656,7 @@ Accept wildcard characters: False
 
 ### -CpaRechargeRate
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The CpaRechargeRate parameter specifies the rate at which a cross premises user budget is charged (budget grows by) during the budget time.
 
@@ -690,7 +694,7 @@ Accept wildcard characters: False
 
 ### -DiscoveryMaxConcurrency
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DiscoveryMaxConcurrency parameter specifies the number of concurrent discovery search executions that a user can have at the same time. To modify the discovery throttling parameters, create a new policy and name it "DiscoveryThrottlingPolicy".
 
@@ -708,7 +712,7 @@ Accept wildcard characters: False
 
 ### -DiscoveryMaxKeywords
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DiscoveryMaxKeywords parameter specifies the maximum number of keywords that a user can include in a discovery search. For more information, see [Search-Mailbox](https://learn.microsoft.com/powershell/module/exchangepowershell/search-mailbox).
 
@@ -726,7 +730,7 @@ Accept wildcard characters: False
 
 ### -DiscoveryMaxKeywordsPerPage
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DiscoveryMaxKeywordsPerPage parameter specifies the number of keywords for which to show statistics on a single page in the EAC.
 
@@ -744,7 +748,7 @@ Accept wildcard characters: False
 
 ### -DiscoveryMaxMailboxes
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DiscoveryMaxMailboxes parameter specifies the maximum number of source mailboxes that a user can include in a discovery search.
 
@@ -762,7 +766,7 @@ Accept wildcard characters: False
 
 ### -DiscoveryMaxPreviewSearchMailboxes
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DiscoveryMaxPreviewSearchMailboxes parameter specifies the maximum number of mailboxes that a user can include in eDiscovery Search Preview.
 
@@ -780,7 +784,7 @@ Accept wildcard characters: False
 
 ### -DiscoveryMaxRefinerResults
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -798,7 +802,7 @@ Accept wildcard characters: False
 
 ### -DiscoveryMaxSearchQueueDepth
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DiscoveryMaxSearchQueueDepth parameter specifies the maximum number of concurrent discovery search threads that can be active at the same time.
 
@@ -816,7 +820,7 @@ Accept wildcard characters: False
 
 ### -DiscoveryMaxStatsSearchMailboxes
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DiscoveryMaxStatsSearchMailboxes parameter specifies the maximum number of mailboxes that a user can search in an In-Place eDiscovery search without being able to view the statistics. When the number of mailboxes configured with the DiscoveryMaxStatsSearchMailboxes parameter is exceeded, the user must copy the search results to a discovery mailbox to view the statistics for the discovery search. For more information, see [In-Place eDiscovery in Exchange Server](https://learn.microsoft.com/Exchange/policy-and-compliance/ediscovery/ediscovery).
 
@@ -834,7 +838,7 @@ Accept wildcard characters: False
 
 ### -DiscoveryPreviewSearchResultsPageSize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DiscoveryPreviewSearchResultsPageSize parameter specifies the number of messages displayed on a single page in eDiscovery Search Preview.
 
@@ -852,7 +856,7 @@ Accept wildcard characters: False
 
 ### -DiscoverySearchTimeoutPeriod
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DiscoverySearchTimeoutPeriod parameter specifies the number of minutes that a discovery search runs before it times out.
 
@@ -870,7 +874,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -890,7 +894,7 @@ Accept wildcard characters: False
 
 ### -EasCutoffBalance
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The EasCutoffBalance parameter specifies the resource consumption limits for an Exchange ActiveSync user before that user is completely blocked from performing operations on a specific component after all available resources have been consumed. There is no preset default value for this parameter but it generally ranges from 600,000 to 3,000,000 in working state depending on the protocol. If for any reason, this value needs to be increased further, you must contact Microsoft Support because a higher value can affect server performance adversely.
 
@@ -908,7 +912,7 @@ Accept wildcard characters: False
 
 ### -EasMaxBurst
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The EasMaxBurst parameter specifies the amount of time that an Exchange ActiveSync user can consume an elevated amount of resources before being throttled. This is measured in milliseconds. This value is set separately for each component.
 
@@ -926,7 +930,7 @@ Accept wildcard characters: False
 
 ### -EASMaxConcurrency
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The EasMaxConcurrency parameter specifies how many concurrent connections an Exchange ActiveSync user can have against an Exchange server at one time. A connection is held from the moment a request is received until a response is sent in its entirety to the requestor. If users attempt to make more concurrent requests than their policy allows, the new connection attempt fails. However, the existing connections remain valid. The EasMaxConcurrency parameter has a valid range from 0 through 2147483647 inclusive. The default value is 10. To indicate that the number of concurrent connections should be unthrottled (no limit), this value should be set to $null.
 
@@ -944,7 +948,7 @@ Accept wildcard characters: False
 
 ### -EASMaxDeviceDeletesPerMonth
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The EasMaxDeviceDeletesPerMonth parameter specifies a limit to the number of Exchange ActiveSync partnerships that a user can delete per month. By default, each user can delete a maximum of 20 partnerships per calendar month. When the limit is reached, the partnership deletion attempt fails and an error message is displayed to the user.
 
@@ -962,7 +966,7 @@ Accept wildcard characters: False
 
 ### -EASMaxDevices
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The EasMaxDevices parameter specifies a limit to the number of Exchange ActiveSync partnerships that a user can have at one time. By default, each user can create 100 Exchange ActiveSync partnerships with their Exchange account. After users exceed the limit, they must delete one of their existing partnerships before they can create any more new partnerships. An email error message describing the limitation is sent to the user when the limit is exceeded. Additionally, an event is logged in the Application log when a user exceeds the limit.
 
@@ -980,7 +984,7 @@ Accept wildcard characters: False
 
 ### -EasMaxInactivityForDeviceCleanup
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The EasMaxInactivityForDeviceCleanup parameter specifies the length of time that a user's device partnerships remain active. By default, there is no limit to the number of days that a user's device partnerships remain active. Use this value if you want to minimize the amount of inactive device partnerships in your organization. To use this setting, specify a value in days since the user's last sync time to cause the device partnership to be removed.
 
@@ -1058,7 +1062,7 @@ Accept wildcard characters: False
 
 ### -EasRechargeRate
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The EasRechargeRate parameter specifies the rate at which an Exchange ActiveSync user's budget is charged (budget grows by) during the budget time.
 
@@ -1076,7 +1080,7 @@ Accept wildcard characters: False
 
 ### -EncryptionRecipientCutoffBalance
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -1094,7 +1098,7 @@ Accept wildcard characters: False
 
 ### -EncryptionRecipientMaxBurst
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -1112,7 +1116,7 @@ Accept wildcard characters: False
 
 ### -EncryptionRecipientMaxConcurrency
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -1130,7 +1134,7 @@ Accept wildcard characters: False
 
 ### -EncryptionRecipientRechargeRate
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -1148,7 +1152,7 @@ Accept wildcard characters: False
 
 ### -EncryptionSenderCutoffBalance
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -1166,7 +1170,7 @@ Accept wildcard characters: False
 
 ### -EncryptionSenderMaxBurst
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -1184,7 +1188,7 @@ Accept wildcard characters: False
 
 ### -EncryptionSenderMaxConcurrency
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -1202,7 +1206,7 @@ Accept wildcard characters: False
 
 ### -EncryptionSenderRechargeRate
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -1220,7 +1224,7 @@ Accept wildcard characters: False
 
 ### -EwsCostThreshold
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The EwsCostThreshold parameter specifies the cost threshold for Exchange Web Services users.
 
@@ -1238,7 +1242,7 @@ Accept wildcard characters: False
 
 ### -EwsCutoffBalance
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The EwsCutoffBalance parameter specifies the resource consumption limits for an Exchange Web Services user before that user is completely blocked from performing operations on a specific component after all available resources have been consumed. There is no preset default value for this parameter but it generally ranges from 600,000 to 3,000,000 in working state depending on the protocol. If for any reason, this value needs to be increased further, you must contact Microsoft Support because a higher value can affect server performance adversely.
 
@@ -1256,7 +1260,7 @@ Accept wildcard characters: False
 
 ### -EwsMaxBurst
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The EwsMaxBurst parameter specifies the amount of time that an Exchange Web Services user can consume an elevated amount of resources before being throttled. This is measured in milliseconds. This value is set separately for each component.
 
@@ -1314,7 +1318,7 @@ Accept wildcard characters: False
 
 ### -EWSMaxConcurrency
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The EwsMaxConcurrency parameter specifies how many concurrent connections an Exchange Web Services user can have against an Exchange server at one time. A connection is held from the moment a request is received until a response is sent in its entirety to the requestor. If users attempt to make more concurrent requests than their policy allows, the new connection attempt fails. However, the existing connections remain valid. The EwsMaxConcurrency parameter has a valid range from 0 through 2147483647 inclusive. The default value is 10. To indicate that the number of concurrent connections should be unthrottled (no limit), this value should be set to $null.
 
@@ -1332,7 +1336,7 @@ Accept wildcard characters: False
 
 ### -EWSMaxSubscriptions
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The EwsMaxSubscriptions parameter specifies the maximum number of active push and pull subscriptions that an Exchange Web Services user can have on a specified Exchange server at the same time. If a user tries to create more subscriptions than the configured maximum, the subscription fails, and an event is logged in Event Viewer.
 
@@ -1410,7 +1414,7 @@ Accept wildcard characters: False
 
 ### -EwsRechargeRate
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The EwsRechargeRate parameter specifies the rate at which an Exchange Web Services user's budget is charged (budget grows by) during the budget time.
 
@@ -1428,7 +1432,7 @@ Accept wildcard characters: False
 
 ### -ExchangeMaxCmdlets
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExchangeMaxCmdlets parameter specifies the number of cmdlets that can be executed within a specific time period before their execution is slowed down. The value specified by this parameter should be less than the value specified by the PowerShellMaxCmdlets parameter.
 
@@ -1448,7 +1452,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -1468,7 +1472,7 @@ Accept wildcard characters: False
 
 ### -ForwardeeLimit
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ForwardeeLimit parameter specifies the limits for the number of recipients that can be configured in Inbox Rules when using the forward or redirect action. This parameter doesn't limit the number of messages that can be forwarded or redirected to the recipients that are configured.
 
@@ -1486,7 +1490,7 @@ Accept wildcard characters: False
 
 ### -ImapCutoffBalance
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ImapCutoffBalance parameter specifies the resource consumption limits for an IMAP user before that user is completely blocked from performing operations on a specific component after all available resources have been consumed. There is no preset default value for this parameter but it generally ranges from 600,000 to 3,000,000 in working state depending on the protocol. If for any reason, this value needs to be increased further, you must contact Microsoft Support because a higher value can affect server performance adversely.
 
@@ -1504,7 +1508,7 @@ Accept wildcard characters: False
 
 ### -ImapMaxBurst
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ImapMaxBurst parameter specifies the amount of time that an IMAP user can consume an elevated amount of resources before being throttled. This is measured in milliseconds. This value is set separately for each component.
 
@@ -1522,7 +1526,7 @@ Accept wildcard characters: False
 
 ### -IMAPMaxConcurrency
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ImapMaxConcurrency parameter specifies how many concurrent connections an IMAP user can have against an Exchange server at one time. A connection is held from the moment a request is received until a response is sent in its entirety to the requestor. If users attempt to make more concurrent requests than their policy allows, the new connection attempt fails. However, the existing connections remain valid. The ImapMaxConcurrency parameter has a valid range from 0 through 2147483647 inclusive. To indicate that the number of concurrent connections should be unthrottled (no limit), this value should be set to $null.
 
@@ -1600,7 +1604,7 @@ Accept wildcard characters: False
 
 ### -ImapRechargeRate
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ImapRechargeRate parameter specifies the rate at which the IMAP user's budget is charged (budget grows by) during the budget time.
 
@@ -1618,7 +1622,7 @@ Accept wildcard characters: False
 
 ### -IsServiceAccount
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IsServiceAccount switch specifies that the user accounts associated with this policy are moderated by per-user thresholds and the health of system resources (for example, overall CPU usage). You don't need to specify a value with this switch.
 
@@ -1640,7 +1644,7 @@ Accept wildcard characters: False
 
 ### -MessageRateLimit
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MessageRateLimit parameter specifies the number of messages per minute that can be submitted to transport by POP3 or IMAP4 clients that use SMTP. Clients receive a transient error if they submit messages at a rate that exceeds the value of this parameter. Exchange attempts to connect and send the messages at a later time.
 
@@ -1658,7 +1662,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Name parameter specifies the name of the object in Active Directory. The default policy is named `DefaultThrottlingPolicy<GUID>`.
 
@@ -1676,7 +1680,7 @@ Accept wildcard characters: False
 
 ### -OutlookServiceCutoffBalance
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -1694,7 +1698,7 @@ Accept wildcard characters: False
 
 ### -OutlookServiceMaxBurst
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -1712,7 +1716,7 @@ Accept wildcard characters: False
 
 ### -OutlookServiceMaxConcurrency
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -1730,7 +1734,7 @@ Accept wildcard characters: False
 
 ### -OutlookServiceMaxSocketConnectionsPerDevice
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -1748,7 +1752,7 @@ Accept wildcard characters: False
 
 ### -OutlookServiceMaxSocketConnectionsPerUser
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -1766,7 +1770,7 @@ Accept wildcard characters: False
 
 ### -OutlookServiceMaxSubscriptions
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -1784,7 +1788,7 @@ Accept wildcard characters: False
 
 ### -OutlookServiceRechargeRate
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -1802,7 +1806,7 @@ Accept wildcard characters: False
 
 ### -OwaCutoffBalance
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The OwaCutoffBalance parameter specifies the resource consumption limits for an Outlook on the web user before that user is completely blocked from performing operations on a specific component after all available resources have been consumed. There is no preset default value for this parameter but it generally ranges from 600,000 to 3,000,000 in working state depending on the protocol. If for any reason, this value needs to be increased further, you must contact Microsoft Support because a higher value can affect server performance adversely.
 
@@ -1820,7 +1824,7 @@ Accept wildcard characters: False
 
 ### -OwaMaxBurst
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The OwaMaxBurst parameter specifies the amount of time that an Outlook on the web user can consume an elevated amount of resources before being throttled. This is measured in milliseconds. This value is set separately for each component.
 
@@ -1838,7 +1842,7 @@ Accept wildcard characters: False
 
 ### -OWAMaxConcurrency
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The OwaMaxConcurrency parameter specifies how many concurrent connections an Outlook on the web user can have against an Exchange server at one time. A connection is held from the moment a request is received until a response is sent in its entirety to the requestor. If users attempt to make more concurrent requests than their policy allows, the new connection attempt fails. However, the existing connections remain valid.
 
@@ -1920,7 +1924,7 @@ Accept wildcard characters: False
 
 ### -OwaRechargeRate
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The OwaRechargeRate parameter specifies the rate at which an Outlook on the web user's budget is charged (budget grows by) during the budget time.
 
@@ -1938,7 +1942,7 @@ Accept wildcard characters: False
 
 ### -OwaVoiceCutoffBalance
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The OwaVoiceCutoffBalance parameter specifies the resource consumption limits for an Outlook on the web voice user before that user is completely blocked from performing operations on a specific component after all available resources have been consumed. There is no preset default value for this parameter but it generally ranges from 600,000 to 3,000,000 in working state depending on the protocol. If for any reason, this value needs to be increased further, you must contact Microsoft Support because a higher value can affect server performance adversely.
 
@@ -1956,7 +1960,7 @@ Accept wildcard characters: False
 
 ### -OwaVoiceMaxBurst
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The OwaVoiceMaxBurst parameter specifies the amount of time that an Outlook on the web voice user can consume an elevated amount of resources before being throttled. This is measured in milliseconds. This value is set separately for each component.
 
@@ -1974,7 +1978,7 @@ Accept wildcard characters: False
 
 ### -OwaVoiceMaxConcurrency
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The OwaVoiceMaxConcurrency parameter specifies how many concurrent connections an Outlook on the web voice user can have against an Exchange server at one time. A connection is held from the moment a request is received until a response is sent in its entirety to the requestor. If users attempt to make more concurrent requests than their policy allows, the new connection attempt fails. However, the existing connections remain valid. The OwaVoiceMaxConcurrency parameter has a valid range from 0 through 2147483647 inclusive. The default value is 5. To indicate that the number of concurrent connections should be unthrottled (no limit), this value should be set to $null.
 
@@ -1992,7 +1996,7 @@ Accept wildcard characters: False
 
 ### -OwaVoiceRechargeRate
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The OwaVoiceRechargeRate parameter specifies the rate at which an Outlook on the web voice user's budget is charged (budget grows by) during the budget time.
 
@@ -2010,7 +2014,7 @@ Accept wildcard characters: False
 
 ### -PopCutoffBalance
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PopCutoffBalance parameter specifies the resource consumption limits for a user before that user is completely blocked from performing operations on a specific component after all available resources have been consumed. There is no preset default value for this parameter but it generally ranges from 600,000 to 3,000,000 in working state depending on the protocol. If for any reason, this value needs to be increased further, you must contact Microsoft Support because a higher value can affect server performance adversely.
 
@@ -2028,7 +2032,7 @@ Accept wildcard characters: False
 
 ### -PopMaxBurst
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PopMaxBurst parameter specifies the amount of time that a user can consume an elevated amount of resources before being throttled. This is measured in milliseconds. This value is set separately for each component.
 
@@ -2046,7 +2050,7 @@ Accept wildcard characters: False
 
 ### -POPMaxConcurrency
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PopMaxConcurrency parameter specifies how many concurrent connections a POP user can have against an Exchange server at one time. A connection is held from the moment a request is received until a response is sent in its entirety to the requestor. If users attempt to make more concurrent requests than their policy allows, the new connection attempt fails. However, the existing connections remain valid. The PopMaxConcurrency parameter has a valid range from 0 through 2147483647 inclusive. The default value is 20. To indicate that the number of concurrent connections should be unthrottled (no limit), this value should be set to $null.
 
@@ -2124,7 +2128,7 @@ Accept wildcard characters: False
 
 ### -PopRechargeRate
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PopRechargeRate parameter specifies the rate at which the user budget is charged (budget grows by) during the budget time.
 
@@ -2142,7 +2146,7 @@ Accept wildcard characters: False
 
 ### -PowerShellCutoffBalance
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PowerShellCutoffBalance parameter specifies the resource consumption limits for a user before that user is completely blocked from performing operations on a specific component after all available resources have been consumed. There is no preset default value for this parameter but it generally ranges from 600,000 to 3,000,000 in working state depending on the protocol. If for any reason, this value needs to be increased further, you must contact Microsoft Support because a higher value can affect server performance adversely.
 
@@ -2160,7 +2164,7 @@ Accept wildcard characters: False
 
 ### -PowerShellMaxBurst
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PowerShellMaxBurst parameter specifies the amount of time that a user can consume an elevated amount of resources before being throttled. This is measured in milliseconds. This value is set separately for each component.
 
@@ -2178,7 +2182,7 @@ Accept wildcard characters: False
 
 ### -PowerShellMaxCmdletQueueDepth
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PowerShellMaxCmdletQueueDepth parameter specifies the number of operations allowed to be executed by the user. This value directly affects the behavior of the PowerShellMaxCmdlets and PowerShellMaxConcurrency parameters. For example, the PowerShellMaxConcurrency parameter consumes at least two operations defined by the PowerShellMaxCmdletQueueDepth parameter but additional operations are also consumed per cmdlet execution. The number of operations depends on the cmdlets executed. We recommend that the value for the PowerShellMaxCmdletQueueDepth parameter be at least three times larger than the value of the PowerShellMaxConcurrency parameter. This parameter doesn't affect Exchange admin center operations or Exchange Web Services operations.
 
@@ -2196,7 +2200,7 @@ Accept wildcard characters: False
 
 ### -PowerShellMaxCmdlets
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PowerShellMaxCmdlets parameter specifies the number of cmdlets that can be executed within a specific time period before their execution is stopped. The value specified by this parameter should be more than the value specified by the ExchangeMaxCmdlets parameter. The time period used for this limit is specified by the PowerShellMaxCmdletsTimePeriod parameter. Both values should be set at the same time.
 
@@ -2214,7 +2218,7 @@ Accept wildcard characters: False
 
 ### -PowerShellMaxCmdletsTimePeriod
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PowerShellMaxCmdletsTimePeriod parameter specifies the time period, in seconds, that the throttling policy uses to determine whether the number of cmdlets being executed exceeds the limits specified by the PowerShellMaxCmdlets and ExchangeMaxCmdlets parameters.
 
@@ -2232,7 +2236,7 @@ Accept wildcard characters: False
 
 ### -PowerShellMaxConcurrency
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PowerShellMaxConcurrency parameter specifies different information depending on context:
 
@@ -2255,7 +2259,7 @@ Accept wildcard characters: False
 
 ### -PowerShellMaxDestructiveCmdlets
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PowerShellMaxDestructiveCmdlets parameter specifies the number of destructive cmdlets that can be executed within a specific time period before their execution is stopped. Destructive cmdlets are cmdlets that can make significant changes to user data and configuration settings in your Exchange organization. Throttling these cmdlets might help prevent accidental data loss. The following cmdlets are designated as destructive:
 
@@ -2285,7 +2289,7 @@ Accept wildcard characters: False
 
 ### -PowerShellMaxDestructiveCmdletsTimePeriod
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PowerShellMaxDestructiveCmdletsTimePeriod parameter specifies the time period, in seconds, that the throttling policy uses to determine how many destructive cmdlets can be run. You set a value for this parameter when you set the PowerShellMaxDestructiveCmdlets parameter. Both values should be set at the same time. For more information, see the description for the PowerShellMaxDestructiveCmdlets parameter.
 
@@ -2303,7 +2307,7 @@ Accept wildcard characters: False
 
 ### -PowerShellMaxOperations
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PowerShellMaxOperations parameter specifies the protocol-level operations that are used to send and receive data. If the execution of a cmdlet results in a significant number of operations (for example, if there is a lot of input/output occurring), throttling might occur. The default setting is Unlimited.
 
@@ -2321,7 +2325,7 @@ Accept wildcard characters: False
 
 ### -PowerShellMaxRunspaces
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PowerShellMaxRunspaces parameter specifies the number of concurrent Windows PowerShell sessions that a user is allowed to have. The default setting is Unlimited.
 
@@ -2339,7 +2343,7 @@ Accept wildcard characters: False
 
 ### -PowerShellMaxRunspacesTimePeriod
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PowerShellMaxRunspacesTimePeriod parameter specifies the time period, in seconds, that the throttling policy uses to determine how many Windows PowerShell sessions can be run. You set this value when you set the PowerShellMaxRunspaces parameter.
 
@@ -2357,7 +2361,7 @@ Accept wildcard characters: False
 
 ### -PowerShellMaxTenantConcurrency
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PowerShellMaxTenantConcurrency parameter limits the number of concurrent Windows PowerShell connections per tenant organization. By default, the limit for concurrent Windows PowerShell connections per tenant organization is set to 9. If users in a tenant organization try to make more concurrent requests than the limit set by the PowerShellMaxTenantConcurrency parameter, the new connection attempt fails. However, the existing connections remain valid. This limit is enforced even if a single user hasn't exceeded the per-user limit set by the PowerShellMaxConcurrency parameter. The PowerShellMaxTenantConcurrency parameter has a valid range from 0 through 100 inclusive. To indicate that the number of concurrent connections should be unthrottled (no limit), this value should be set to $null.
 
@@ -2377,7 +2381,7 @@ Accept wildcard characters: False
 
 ### -PowerShellMaxTenantRunspaces
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PowerShellMaxTenantRunspaces parameter specifies the number of concurrent Windows PowerShell sessions that a tenant is allowed to have.
 
@@ -2395,7 +2399,7 @@ Accept wildcard characters: False
 
 ### -PowerShellRechargeRate
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PowerShellRechargeRate parameter specifies the rate at which the user budget is charged (budget grows by) during the budget time.
 
@@ -2413,7 +2417,7 @@ Accept wildcard characters: False
 
 ### -PswsMaxConcurrency
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PswsMaxConcurrency parameter specifies how many concurrent connections a Windows PowerShell Web Services user can have against an Exchange server at one time. A connection is held from the moment a request is received until a response is sent in its entirety to the requestor. If users attempt to make more concurrent requests than their policy allows, the new connection attempt fails. However, the existing connections remain valid.
 
@@ -2433,7 +2437,7 @@ Accept wildcard characters: False
 
 ### -PswsMaxRequest
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PswsMaxRequest parameter specifies how many requests a Windows PowerShell Web Services user can have against an Exchange server at one time. The default setting is Unlimited.
 
@@ -2451,7 +2455,7 @@ Accept wildcard characters: False
 
 ### -PswsMaxRequestTimePeriod
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PswsMaxRequestTimePeriod parameter specifies the period of time, in seconds, that the throttling policy uses to determine how many requests can be run. The default setting is Unlimited.
 
@@ -2469,7 +2473,7 @@ Accept wildcard characters: False
 
 ### -PushNotificationCutoffBalance
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -2487,7 +2491,7 @@ Accept wildcard characters: False
 
 ### -PushNotificationMaxBurst
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -2505,7 +2509,7 @@ Accept wildcard characters: False
 
 ### -PushNotificationMaxBurstPerDevice
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -2523,7 +2527,7 @@ Accept wildcard characters: False
 
 ### -PushNotificationMaxConcurrency
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -2541,7 +2545,7 @@ Accept wildcard characters: False
 
 ### -PushNotificationRechargeRate
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -2559,7 +2563,7 @@ Accept wildcard characters: False
 
 ### -PushNotificationRechargeRatePerDevice
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -2577,7 +2581,7 @@ Accept wildcard characters: False
 
 ### -PushNotificationSamplingPeriodPerDevice
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -2595,7 +2599,7 @@ Accept wildcard characters: False
 
 ### -RcaCutoffBalance
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RcaCutoffBalance parameter specifies the resource consumption limits for a user before that user is completely blocked from performing operations on a specific component after all available resources have been consumed. There is no preset default value for this parameter but it generally ranges from 600,000 to 3,000,000 in working state depending on the protocol. If for any reason, this value needs to be increased further, you must contact Microsoft Support because a higher value can affect server performance adversely.
 
@@ -2613,7 +2617,7 @@ Accept wildcard characters: False
 
 ### -RcaMaxBurst
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RcaMaxBurst parameter specifies the amount of time that a user can consume an elevated amount of resources before being throttled. This is measured in milliseconds. This value is set separately for each component.
 
@@ -2631,7 +2635,7 @@ Accept wildcard characters: False
 
 ### -RCAMaxConcurrency
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RcaMaxConcurrency parameter specifies how many concurrent connections an RPC Client Access user can have against an Exchange server at one time. A connection is held from the moment a request is received until the connection is closed or the connection is otherwise disconnected (for example, if the user goes offline). If users attempt to make more concurrent requests than their policy allows, the new connection attempt fails. However, the existing connections remain valid.
 
@@ -2713,7 +2717,7 @@ Accept wildcard characters: False
 
 ### -RcaRechargeRate
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RcaRechargeRate parameter specifies the rate at which the budget for the user is charged (how much the budget grows by) during the budget time.
 
@@ -2731,7 +2735,7 @@ Accept wildcard characters: False
 
 ### -RcaSharedCutoffBalance
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RcaSharedCutoffBalance parameter specifies the resource consumption limits for all users before they're completely blocked from performing operations on a specific component after all available resources have been consumed. There is no preset default value for this parameter but it generally ranges from 600,000 to 3,000,000 in working state depending on the protocol. If for any reason, this value needs to be increased further, you must contact Microsoft Support because a higher value can affect server performance adversely.
 
@@ -2749,7 +2753,7 @@ Accept wildcard characters: False
 
 ### -RcaSharedMaxBurst
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RcaShardMaxBurst parameter specifies the amount of time that all users can consume elevated amounts of resources before being throttled. This is measured in milliseconds. This value is set separately for each component.
 
@@ -2767,7 +2771,7 @@ Accept wildcard characters: False
 
 ### -RcaSharedMaxConcurrency
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RcaSharedMaxConcurrency parameter specifies how many concurrent connections all RPC Client Access users can have against an Exchange server at one time. A connection is held from the moment a request is received until the connection is closed or the connection is otherwise disconnected (for example, if users go offline). If there are more concurrent requests than the policy allows, new connection attempts fail. However, the existing connections remain valid.
 
@@ -2787,7 +2791,7 @@ Accept wildcard characters: False
 
 ### -RcaSharedRechargeRate
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RcaSharedRechargeRate parameter specifies the rate at which the budget for all users is charged (how much the budget grows by) during the budget time.
 
@@ -2805,7 +2809,7 @@ Accept wildcard characters: False
 
 ### -RecipientRateLimit
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RecipientRateLimit parameter specifies the limits on the number of recipients that a user can address in a 24-hour period.
 
@@ -2823,7 +2827,7 @@ Accept wildcard characters: False
 
 ### -SchedulesCutoffBalance
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -2841,7 +2845,7 @@ Accept wildcard characters: False
 
 ### -SchedulesMaxBurst
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -2859,7 +2863,7 @@ Accept wildcard characters: False
 
 ### -SchedulesMaxConcurrency
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -2877,7 +2881,7 @@ Accept wildcard characters: False
 
 ### -SchedulesRechargeRate
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -2895,7 +2899,7 @@ Accept wildcard characters: False
 
 ### -ThrottlingPolicyScope
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ThrottlingPolicyScope parameter specifies the scope of the throttling policy. You can use the following values:
 
@@ -2919,7 +2923,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ThrottlingPolicyAssociation.md b/exchange/exchange-ps/ExchangePowerShell/Set-ThrottlingPolicyAssociation.md
index 9c9408f002..07e8f891fd 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-ThrottlingPolicyAssociation.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-ThrottlingPolicyAssociation.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -63,7 +63,7 @@ You don't need to use the Set-ThrottlingPolicyAssociation cmdlet to associate a
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the object to which you want to associate a throttling policy. The object can be a user with a mailbox, a user without a mailbox, a contact, or a computer account.
 
@@ -81,7 +81,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -102,7 +102,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -122,7 +122,7 @@ Accept wildcard characters: False
 
 ### -ThrottlingPolicy
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ThrottlingPolicy parameter specifies the throttling policy that you want the object specified by the Identity parameter to be associated with.
 
@@ -140,7 +140,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-TransportAgent.md b/exchange/exchange-ps/ExchangePowerShell/Set-TransportAgent.md
index d41b3a6694..da20218a86 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-TransportAgent.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-TransportAgent.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -47,7 +47,7 @@ This example modifies the priority of a fictitious agent named Test App in the F
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the name (Identity property value) of the transport agent that you want to modify. If the name contains spaces, enclose the name in quotation marks (").
 
@@ -65,7 +65,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -86,7 +86,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -106,7 +106,7 @@ Accept wildcard characters: False
 
 ### -Priority
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Priority parameter specifies the priority of the transport agent. The priority of the transport agent controls the order in which the transport agents process email messages. The priority must be a value between 0 and the maximum number of transport agents. The default behavior is to append a new transport agent to the end of the priority list. Transport agents with a priority closest to 0 process email messages first.
 
@@ -124,7 +124,7 @@ Accept wildcard characters: False
 
 ### -TransportService
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TransportService parameter specifies the transport service that you want to view or modify. Valid values for this parameter are:
 
@@ -148,7 +148,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-TransportConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-TransportConfig.md
index b4837dae87..a084e229ad 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-TransportConfig.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-TransportConfig.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -116,7 +116,7 @@ To avoid journaling issues, we recommend that you set JournalingReportNdrTo to a
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -136,7 +136,7 @@ Accept wildcard characters: False
 
 ### -AddressBookPolicyRoutingEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AddressBookPolicyRoutingEnabled parameter controls how recipients are resolved in an organization that uses address book policies to create separate virtual organizations within the same Exchange organization. Specifically, the global address list (GAL) that's specified in the user's address book policy controls how recipients are resolved. When the value of this parameter is $true, users that are assigned different GALs appear as external recipients. When the value of this parameter is $false, users that are assigned different GALs appear as internal recipients.
 
@@ -156,7 +156,7 @@ Accept wildcard characters: False
 
 ### -AgentGeneratedMessageLoopDetectionInSubmissionEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -180,7 +180,7 @@ Accept wildcard characters: False
 
 ### -AgentGeneratedMessageLoopDetectionInSmtpEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -224,7 +224,7 @@ Accept wildcard characters: False
 
 ### -ClearCategories
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ClearCategories parameter keeps or removes Microsoft Outlook message categories during content conversion. Valid input for this parameter is $true or $false. The default value is $true. This means that by default, Outlook message categories are removed during content conversion.
 
@@ -242,7 +242,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -263,7 +263,7 @@ Accept wildcard characters: False
 
 ### -ConvertDisclaimerWrapperToEml
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ConvertDisclaimerWrapperToEml parameter specifies whether the original message is added as a TNEF attachment or a regular EML attachment to a disclaimer when all of the following are true:
 
@@ -289,7 +289,7 @@ Accept wildcard characters: False
 
 ### -DiagnosticsAggregationServicePort
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -309,7 +309,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -331,7 +331,7 @@ Accept wildcard characters: False
 
 ### -DSNConversionMode
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The DSNConversionMode parameter controls how Exchange handles delivery status notifications (also known as DSNs, non-delivery reports, NDRs, or bounce messages) that are generated by earlier versions of Exchange or other email systems. Valid values are:
 
@@ -355,7 +355,7 @@ Accept wildcard characters: False
 
 ### -ExternalDelayDsnEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ExternalDelayDsnEnabled parameter specifies whether a delay delivery status notification (DSN) message should be created for external messages that couldn't be immediately delivered. Valid input for this parameter is $true or $false. The default value is $true.
 
@@ -373,7 +373,7 @@ Accept wildcard characters: False
 
 ### -ExternalDsnDefaultLanguage
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ExternalDsnDefaultLanguage parameter specifies which Exchange server language should be used by default when you create external DSN messages. The default value is the default Windows server language.
 
@@ -391,7 +391,7 @@ Accept wildcard characters: False
 
 ### -ExternalDsnLanguageDetectionEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ExternalDsnLanguageDetectionEnabled parameter specifies whether the server should try to send an external DSN message in the same language as the original message that generated the notification. Valid input for this parameter is $true or $false.The default value is $true.
 
@@ -409,7 +409,7 @@ Accept wildcard characters: False
 
 ### -ExternalDsnMaxMessageAttachSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -441,7 +441,7 @@ Accept wildcard characters: False
 
 ### -ExternalDsnReportingAuthority
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ExternalDsnReportingAuthority parameter specifies the domain in the machine-readable part of external DSN messages. The default value is blank ($null), which means the value is the authoritative domain that you specified during the creation of the organization.
 
@@ -459,7 +459,7 @@ Accept wildcard characters: False
 
 ### -ExternalDsnSendHtml
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ExternalDsnSendHtml parameter specifies whether external DSN messages should be HTML or plain text. Valid values are:
 
@@ -480,7 +480,7 @@ Accept wildcard characters: False
 
 ### -ExternalPostmasterAddress
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ExternalPostmasterAddress parameter specifies the email address in the From header field of an external DSN message. The default value is blank ($null).
 
@@ -508,7 +508,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -528,7 +528,7 @@ Accept wildcard characters: False
 
 ### -GenerateCopyOfDSNFor
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -567,7 +567,7 @@ Accept wildcard characters: False
 
 ### -HeaderPromotionModeSetting
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The HeaderPromotionModeSetting parameter specifies whether named properties are created for custom X-headers on messages received. Valid values are:
 
@@ -589,7 +589,7 @@ Accept wildcard characters: False
 
 ### -InternalDelayDsnEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The InternalDelayDsnEnabled parameter specifies whether a delay DSN message should be created for messages sent to or from recipients or senders in the same Exchange organization that couldn't be immediately delivered. Valid input for this parameter is $true or $false. The default value is $true.
 
@@ -607,7 +607,7 @@ Accept wildcard characters: False
 
 ### -InternalDsnDefaultLanguage
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The InternalDsnDefaultLanguage parameter specifies which Exchange server language should be used by default when you create internal DSN messages. The default value is the default Windows server language.
 
@@ -625,7 +625,7 @@ Accept wildcard characters: False
 
 ### -InternalDsnLanguageDetectionEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The InternalDsnLanguageDetectionEnabled parameter specifies whether the server should try to send an internal DSN message in the same language as the original message that generated the notification. Valid input for this parameter is $true or $false. The default value is $true.
 
@@ -643,7 +643,7 @@ Accept wildcard characters: False
 
 ### -InternalDsnMaxMessageAttachSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -674,7 +674,7 @@ Accept wildcard characters: False
 
 ### -InternalDsnReportingAuthority
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The InternalDsnReportingAuthority parameter specifies the domain in the machine-readable part of internal DSN messages. The default value is blank ($null), which means the value is the authoritative domain that you specified during the creation of the organization.
 
@@ -692,7 +692,7 @@ Accept wildcard characters: False
 
 ### -InternalDsnSendHtml
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The InternalDsnSendHtml parameter specifies whether internal DSN messages should be HTML or plain text. Valid values are:
 
@@ -713,7 +713,7 @@ Accept wildcard characters: False
 
 ### -InternalSMTPServers
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -757,7 +757,7 @@ Accept wildcard characters: False
 
 ### -JournalingReportNdrTo
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The JournalingReportNdrTo parameter specifies the email address to which journal reports are sent if the journaling mailbox is unavailable. By default, if this parameter is left empty, Exchange continues to try to deliver the journal report to the journaling mailbox. We recommended that you use a dedicated (non-user) mailbox as the value for this parameter. Like the journaling mailbox, the alternate journaling mailbox can't be an Exchange Online mailbox.
 
@@ -797,7 +797,7 @@ Accept wildcard characters: False
 
 ### -MaxAllowedAgentGeneratedMessageDepth
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -817,7 +817,7 @@ Accept wildcard characters: False
 
 ### -MaxAllowedAgentGeneratedMessageDepthPerAgent
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -839,7 +839,7 @@ Accept wildcard characters: False
 
 ### -MaxDumpsterSizePerDatabase
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -875,7 +875,7 @@ Accept wildcard characters: False
 
 ### -MaxDumpsterTime
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -905,7 +905,7 @@ Accept wildcard characters: False
 
 ### -MaxReceiveSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -940,7 +940,7 @@ Accept wildcard characters: False
 
 ### -MaxRecipientEnvelopeLimit
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The MaxRecipientEnvelopeLimit parameter specifies the maximum number of recipients in a message. Exchange treats an unexpanded distribution group as one recipient.
 
@@ -962,7 +962,7 @@ Accept wildcard characters: False
 
 ### -MaxRetriesForLocalSiteShadow
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -988,7 +988,7 @@ Accept wildcard characters: False
 
 ### -MaxRetriesForRemoteSiteShadow
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1014,7 +1014,7 @@ Accept wildcard characters: False
 
 ### -MaxSendSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1100,7 +1100,7 @@ Accept wildcard characters: False
 
 ### -QueueDiagnosticsAggregationInterval
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1122,7 +1122,7 @@ Accept wildcard characters: False
 
 ### -RejectMessageOnShadowFailure
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1227,7 +1227,7 @@ Accept wildcard characters: False
 
 ### -Rfc2231EncodingEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Rfc2231EncodingEnabled parameter specifies whether the RFC 2231 encoding of MIME parameters for outbound messages is enabled in your organization. Valid input for this parameter is $true or $false. The default value is $false.
 
@@ -1245,7 +1245,7 @@ Accept wildcard characters: False
 
 ### -SafetyNetHoldTime
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1269,7 +1269,7 @@ Accept wildcard characters: False
 
 ### -ShadowHeartbeatFrequency
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1293,7 +1293,7 @@ Accept wildcard characters: False
 
 ### -ShadowHeartbeatRetryCount
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1317,7 +1317,7 @@ Accept wildcard characters: False
 
 ### -ShadowHeartbeatTimeoutInterval
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1345,7 +1345,7 @@ Accept wildcard characters: False
 
 ### -ShadowMessageAutoDiscardInterval
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1369,7 +1369,7 @@ Accept wildcard characters: False
 
 ### -ShadowMessagePreferenceSetting
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1395,7 +1395,7 @@ Accept wildcard characters: False
 
 ### -ShadowRedundancyEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1415,7 +1415,7 @@ Accept wildcard characters: False
 
 ### -ShadowResubmitTimeSpan
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1475,7 +1475,7 @@ Accept wildcard characters: False
 
 ### -SupervisionTags
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1497,7 +1497,7 @@ Accept wildcard characters: False
 
 ### -TLSReceiveDomainSecureList
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1527,7 +1527,7 @@ Accept wildcard characters: False
 
 ### -TLSSendDomainSecureList
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1557,7 +1557,7 @@ Accept wildcard characters: False
 
 ### -TransportRuleAttachmentTextScanLimit
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1590,7 +1590,7 @@ Accept wildcard characters: False
 
 ### -VerifySecureSubmitEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1614,7 +1614,7 @@ Accept wildcard characters: False
 
 ### -VoicemailJournalingEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is functional only in on-premises Exchange.
 
@@ -1634,7 +1634,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
@@ -1652,7 +1652,7 @@ Accept wildcard characters: False
 
 ### -Xexch50Enabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-TransportRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-TransportRule.md
index 51b8d54495..876e36276c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-TransportRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-TransportRule.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -227,7 +227,7 @@ This example modifies the existing rule named Sales Team Disclaimer transport ru
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the rule that you want to modify. You can use any value that uniquely identifies the rule. For example:
 
@@ -249,7 +249,7 @@ Accept wildcard characters: False
 
 ### -ActivationDate
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ActivationDate parameter specifies when the rule starts processing messages. The rule doesn't take any action on messages until the specified date/time.
 
@@ -269,7 +269,7 @@ Accept wildcard characters: False
 
 ### -ADComparisonAttribute
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -323,7 +323,7 @@ Accept wildcard characters: False
 
 ### -ADComparisonOperator
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -348,7 +348,7 @@ Accept wildcard characters: False
 
 ### -AddManagerAsRecipientType
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an action or part of an action for the rule.
 
@@ -377,7 +377,7 @@ Accept wildcard characters: False
 
 ### -AddToRecipients
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an action or part of an action for the rule.
 
@@ -408,7 +408,7 @@ Accept wildcard characters: False
 
 ### -AnyOfCcHeader
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -443,7 +443,7 @@ Accept wildcard characters: False
 
 ### -AnyOfCcHeaderMemberOf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -478,7 +478,7 @@ Accept wildcard characters: False
 
 ### -AnyOfRecipientAddressContainsWords
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -504,7 +504,7 @@ Accept wildcard characters: False
 
 ### -AnyOfRecipientAddressMatchesPatterns
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -530,7 +530,7 @@ Accept wildcard characters: False
 
 ### -AnyOfToCcHeader
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -565,7 +565,7 @@ Accept wildcard characters: False
 
 ### -AnyOfToCcHeaderMemberOf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -600,7 +600,7 @@ Accept wildcard characters: False
 
 ### -AnyOfToHeader
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -635,7 +635,7 @@ Accept wildcard characters: False
 
 ### -AnyOfToHeaderMemberOf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -670,7 +670,7 @@ Accept wildcard characters: False
 
 ### -ApplyClassification
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an action or part of an action for the rule.
 
@@ -694,7 +694,7 @@ Accept wildcard characters: False
 
 ### -ApplyHtmlDisclaimerFallbackAction
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an action or part of an action for the rule.
 
@@ -729,7 +729,7 @@ Accept wildcard characters: False
 
 ### -ApplyHtmlDisclaimerLocation
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an action or part of an action for the rule.
 
@@ -756,7 +756,7 @@ Accept wildcard characters: False
 
 ### -ApplyHtmlDisclaimerText
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an action or part of an action for the rule.
 
@@ -855,7 +855,7 @@ Accept wildcard characters: False
 
 ### -ApplyRightsProtectionTemplate
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an action or part of an action for the rule.
 
@@ -883,7 +883,7 @@ Accept wildcard characters: False
 
 ### -AttachmentContainsWords
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -907,7 +907,7 @@ Accept wildcard characters: False
 
 ### -AttachmentExtensionMatchesWords
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -931,7 +931,7 @@ Accept wildcard characters: False
 
 ### -AttachmentHasExecutableContent
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -958,7 +958,7 @@ Accept wildcard characters: False
 
 ### -AttachmentIsPasswordProtected
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -983,7 +983,7 @@ Accept wildcard characters: False
 
 ### -AttachmentIsUnsupported
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -1014,7 +1014,7 @@ Accept wildcard characters: False
 
 ### -AttachmentMatchesPatterns
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -1040,7 +1040,7 @@ Accept wildcard characters: False
 
 ### -AttachmentNameMatchesPatterns
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -1062,7 +1062,7 @@ Accept wildcard characters: False
 
 ### -AttachmentProcessingLimitExceeded
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -1089,7 +1089,7 @@ Accept wildcard characters: False
 
 ### -AttachmentPropertyContainsWords
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -1130,7 +1130,7 @@ Accept wildcard characters: False
 
 ### -AttachmentSizeOver
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -1164,7 +1164,7 @@ Accept wildcard characters: False
 
 ### -BetweenMemberOf1
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -1195,7 +1195,7 @@ Accept wildcard characters: False
 
 ### -BetweenMemberOf2
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -1226,7 +1226,7 @@ Accept wildcard characters: False
 
 ### -BlindCopyTo
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an action or part of an action for the rule.
 
@@ -1257,7 +1257,7 @@ Accept wildcard characters: False
 
 ### -Comments
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Comments parameter specifies optional descriptive text for the rule (for example, what the rule is used for, or how it has changed over time). The length of the comment can't exceed 1024 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -1275,7 +1275,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -1296,7 +1296,7 @@ Accept wildcard characters: False
 
 ### -ContentCharacterSetContainsWords
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -1320,7 +1320,7 @@ Accept wildcard characters: False
 
 ### -CopyTo
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an action or part of an action for the rule.
 
@@ -1351,7 +1351,7 @@ Accept wildcard characters: False
 
 ### -DeleteMessage
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an action or part of an action for the rule.
 
@@ -1376,7 +1376,7 @@ Accept wildcard characters: False
 
 ### -Disconnect
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter is functional only on Edge Transport servers in on-premises Exchange.
 
@@ -1401,7 +1401,7 @@ Accept wildcard characters: False
 
 ### -DlpPolicy
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 **Note**: This parameter is functional only in on-premises Exchange.
 
@@ -1421,7 +1421,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1443,7 +1443,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfADComparisonAttribute
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -1497,7 +1497,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfADComparisonOperator
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -1522,7 +1522,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfAnyOfCcHeader
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -1557,7 +1557,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfAnyOfCcHeaderMemberOf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -1592,7 +1592,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfAnyOfRecipientAddressContainsWords
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -1618,7 +1618,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfAnyOfRecipientAddressMatchesPatterns
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -1644,7 +1644,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfAnyOfToCcHeader
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -1679,7 +1679,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfAnyOfToCcHeaderMemberOf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -1714,7 +1714,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfAnyOfToHeader
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -1749,7 +1749,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfAnyOfToHeaderMemberOf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -1784,7 +1784,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfAttachmentContainsWords
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -1808,7 +1808,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfAttachmentExtensionMatchesWords
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -1832,7 +1832,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfAttachmentHasExecutableContent
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -1859,7 +1859,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfAttachmentIsPasswordProtected
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -1884,7 +1884,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfAttachmentIsUnsupported
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -1915,7 +1915,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfAttachmentMatchesPatterns
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -1941,7 +1941,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfAttachmentNameMatchesPatterns
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -1963,7 +1963,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfAttachmentProcessingLimitExceeded
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -1990,7 +1990,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfAttachmentPropertyContainsWords
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -2031,7 +2031,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfAttachmentSizeOver
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -2063,7 +2063,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfBetweenMemberOf1
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -2094,7 +2094,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfBetweenMemberOf2
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -2125,7 +2125,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfContentCharacterSetContainsWords
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -2149,7 +2149,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfFrom
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -2182,7 +2182,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfFromAddressContainsWords
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -2206,7 +2206,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfFromAddressMatchesPatterns
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -2232,7 +2232,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfFromMemberOf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -2265,7 +2265,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfFromScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -2290,7 +2290,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfHasClassification
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -2318,7 +2318,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfHasNoClassification
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -2343,7 +2343,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfHasSenderOverride
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 **Note:** This parameter is functional only in on-premises Exchange.
 
@@ -2370,7 +2370,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfHeaderContainsMessageHeader
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -2392,7 +2392,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfHeaderContainsWords
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -2418,7 +2418,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfHeaderMatchesMessageHeader
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -2440,7 +2440,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfHeaderMatchesPatterns
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -2464,7 +2464,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfManagerAddresses
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -2497,7 +2497,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfManagerForEvaluatedUser
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -2524,7 +2524,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfMessageContainsDataClassifications
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 **Note:** This parameter is functional only in on-premises Exchange.
 
@@ -2552,7 +2552,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfMessageSizeOver
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -2584,7 +2584,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfMessageTypeMatches
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -2616,7 +2616,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfRecipientADAttributeContainsWords
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -2674,7 +2674,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfRecipientADAttributeMatchesPatterns
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -2730,7 +2730,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfRecipientAddressContainsWords
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -2752,7 +2752,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfRecipientAddressMatchesPatterns
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -2776,7 +2776,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfRecipientDomainIs
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -2820,7 +2820,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfSCLOver
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -2847,7 +2847,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfSenderADAttributeContainsWords
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -2905,7 +2905,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfSenderADAttributeMatchesPatterns
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -2961,7 +2961,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfSenderDomainIs
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -3007,7 +3007,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfSenderIpRanges
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -3037,7 +3037,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfSenderManagementRelationship
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -3062,7 +3062,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfSentTo
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -3093,7 +3093,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfSentToMemberOf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -3122,7 +3122,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfSentToScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -3149,7 +3149,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfSubjectContainsWords
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -3175,7 +3175,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfSubjectMatchesPatterns
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -3197,7 +3197,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfSubjectOrBodyContainsWords
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -3223,7 +3223,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfSubjectOrBodyMatchesPatterns
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -3245,7 +3245,7 @@ Accept wildcard characters: False
 
 ### -ExceptIfWithImportance
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -3271,7 +3271,7 @@ Accept wildcard characters: False
 
 ### -ExpiryDate
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an exception or part of an exception for the rule. The name of the corresponding condition parameter doesn't include the ExceptIf prefix.
 
@@ -3293,7 +3293,7 @@ Accept wildcard characters: False
 
 ### -From
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -3326,7 +3326,7 @@ Accept wildcard characters: False
 
 ### -FromAddressContainsWords
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -3350,7 +3350,7 @@ Accept wildcard characters: False
 
 ### -FromAddressMatchesPatterns
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -3376,7 +3376,7 @@ Accept wildcard characters: False
 
 ### -FromMemberOf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -3409,7 +3409,7 @@ Accept wildcard characters: False
 
 ### -FromScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -3434,7 +3434,7 @@ Accept wildcard characters: False
 
 ### -GenerateIncidentReport
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an action or part of an action for the rule.
 
@@ -3465,7 +3465,7 @@ Accept wildcard characters: False
 
 ### -GenerateNotification
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an action or part of an action for the rule.
 
@@ -3498,7 +3498,7 @@ Accept wildcard characters: False
 
 ### -HasClassification
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -3526,7 +3526,7 @@ Accept wildcard characters: False
 
 ### -HasNoClassification
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -3551,7 +3551,7 @@ Accept wildcard characters: False
 
 ### -HasSenderOverride
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 **Note:** This parameter is functional only in on-premises Exchange.
 
@@ -3578,7 +3578,7 @@ Accept wildcard characters: False
 
 ### -HeaderContainsMessageHeader
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -3600,7 +3600,7 @@ Accept wildcard characters: False
 
 ### -HeaderContainsWords
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -3626,7 +3626,7 @@ Accept wildcard characters: False
 
 ### -HeaderMatchesMessageHeader
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -3648,7 +3648,7 @@ Accept wildcard characters: False
 
 ### -HeaderMatchesPatterns
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -3672,7 +3672,7 @@ Accept wildcard characters: False
 
 ### -IncidentReportContent
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an action or part of an action for the rule.
 
@@ -3740,7 +3740,7 @@ Accept wildcard characters: False
 
 ### -LogEventText
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter is functional only on Edge Transport servers in on-premises Exchange.
 
@@ -3770,7 +3770,7 @@ Accept wildcard characters: False
 
 ### -ManagerAddresses
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -3803,7 +3803,7 @@ Accept wildcard characters: False
 
 ### -ManagerForEvaluatedUser
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -3830,7 +3830,7 @@ Accept wildcard characters: False
 
 ### -MessageContainsDataClassifications
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 **Note:** This parameter is functional only in on-premises Exchange.
 
@@ -3860,7 +3860,7 @@ Accept wildcard characters: False
 
 ### -MessageSizeOver
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -3892,7 +3892,7 @@ Accept wildcard characters: False
 
 ### -MessageTypeMatches
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -3924,7 +3924,7 @@ Accept wildcard characters: False
 
 ### -Mode
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Mode parameter specifies how the rule operates. Valid values are:
 
@@ -3946,7 +3946,7 @@ Accept wildcard characters: False
 
 ### -ModerateMessageByManager
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an action or part of an action for the rule.
 
@@ -3973,7 +3973,7 @@ Accept wildcard characters: False
 
 ### -ModerateMessageByUser
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an action or part of an action for the rule.
 
@@ -4006,7 +4006,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Name parameter specifies the display name of the transport rule to be created. The length of the name canThe Name parameter specifies the unique name of the rule. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -4024,7 +4024,7 @@ Accept wildcard characters: False
 
 ### -NotifySender
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 **Note:** This parameter is functional only in on-premises Exchange.
 
@@ -4060,7 +4060,7 @@ Accept wildcard characters: False
 
 ### -PrependSubject
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an action or part of an action for the rule.
 
@@ -4084,7 +4084,7 @@ Accept wildcard characters: False
 
 ### -Priority
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Priority parameter specifies a priority value for the rule that determines the order of rule processing. A lower integer value indicates a higher priority, the value 0 is the highest priority, and rules can't have the same priority value.
 
@@ -4110,7 +4110,7 @@ Accept wildcard characters: False
 
 ### -Quarantine
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an action or part of an action for the rule.
 
@@ -4137,7 +4137,7 @@ Accept wildcard characters: False
 
 ### -RecipientADAttributeContainsWords
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -4195,7 +4195,7 @@ Accept wildcard characters: False
 
 ### -RecipientADAttributeMatchesPatterns
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -4251,7 +4251,7 @@ Accept wildcard characters: False
 
 ### -RecipientAddressContainsWords
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -4273,7 +4273,7 @@ Accept wildcard characters: False
 
 ### -RecipientAddressMatchesPatterns
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -4320,7 +4320,7 @@ Accept wildcard characters: False
 
 ### -RecipientDomainIs
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -4364,7 +4364,7 @@ Accept wildcard characters: False
 
 ### -RedirectMessageTo
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an action or part of an action for the rule.
 
@@ -4395,7 +4395,7 @@ Accept wildcard characters: False
 
 ### -RejectMessageEnhancedStatusCode
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an action or part of an action for the rule.
 
@@ -4423,7 +4423,7 @@ Accept wildcard characters: False
 
 ### -RejectMessageReasonText
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an action or part of an action for the rule.
 
@@ -4455,7 +4455,7 @@ Accept wildcard characters: False
 
 ### -RemoveHeader
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an action or part of an action for the rule.
 
@@ -4580,7 +4580,7 @@ Accept wildcard characters: False
 
 ### -RouteMessageOutboundRequireTls
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an action or part of an action for the rule.
 
@@ -4605,7 +4605,7 @@ Accept wildcard characters: False
 
 ### -RuleErrorAction
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The RuleErrorAction parameter specifies what to do if rule processing can't be completed on messages. Valid values are:
 
@@ -4626,7 +4626,7 @@ Accept wildcard characters: False
 
 ### -RuleSubType
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The RuleSubType parameter specifies the rule type. Valid values are:
 
@@ -4647,7 +4647,7 @@ Accept wildcard characters: False
 
 ### -SCLOver
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -4674,7 +4674,7 @@ Accept wildcard characters: False
 
 ### -SenderADAttributeContainsWords
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -4732,7 +4732,7 @@ Accept wildcard characters: False
 
 ### -SenderADAttributeMatchesPatterns
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -4788,7 +4788,7 @@ Accept wildcard characters: False
 
 ### -SenderAddressLocation
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The SenderAddressLocation parameter specifies where to look for sender addresses in conditions and exceptions that examine sender email addresses. Valid values are:
 
@@ -4818,7 +4818,7 @@ Accept wildcard characters: False
 
 ### -SenderDomainIs
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -4864,7 +4864,7 @@ Accept wildcard characters: False
 
 ### -SenderIpRanges
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -4894,7 +4894,7 @@ Accept wildcard characters: False
 
 ### -SenderManagementRelationship
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -4919,7 +4919,7 @@ Accept wildcard characters: False
 
 ### -SentTo
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -4950,7 +4950,7 @@ Accept wildcard characters: False
 
 ### -SentToMemberOf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -4983,7 +4983,7 @@ Accept wildcard characters: False
 
 ### -SentToScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -5010,7 +5010,7 @@ Accept wildcard characters: False
 
 ### -SetAuditSeverity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an action or part of an action for the rule.
 
@@ -5037,7 +5037,7 @@ Accept wildcard characters: False
 
 ### -SetHeaderName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an action or part of an action for the rule.
 
@@ -5059,7 +5059,7 @@ Accept wildcard characters: False
 
 ### -SetHeaderValue
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an action or part of an action for the rule.
 
@@ -5081,7 +5081,7 @@ Accept wildcard characters: False
 
 ### -SetSCL
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an action or part of an action for the rule.
 
@@ -5106,7 +5106,7 @@ Accept wildcard characters: False
 
 ### -SmtpRejectMessageRejectStatusCode
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter is functional only on Edge Transport servers in on-premises Exchange.
 
@@ -5130,7 +5130,7 @@ Accept wildcard characters: False
 
 ### -SmtpRejectMessageRejectText
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter is functional only on Edge Transport servers in on-premises Exchange.
 
@@ -5154,7 +5154,7 @@ Accept wildcard characters: False
 
 ### -StopRuleProcessing
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies an action or part of an action for the rule.
 
@@ -5179,7 +5179,7 @@ Accept wildcard characters: False
 
 ### -SubjectContainsWords
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -5205,7 +5205,7 @@ Accept wildcard characters: False
 
 ### -SubjectMatchesPatterns
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -5227,7 +5227,7 @@ Accept wildcard characters: False
 
 ### -SubjectOrBodyContainsWords
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -5253,7 +5253,7 @@ Accept wildcard characters: False
 
 ### -SubjectOrBodyMatchesPatterns
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
@@ -5275,7 +5275,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
@@ -5293,7 +5293,7 @@ Accept wildcard characters: False
 
 ### -WithImportance
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 This parameter specifies a condition or part of a condition for the rule. The name of the corresponding exception parameter starts with ExceptIf.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-TransportServer.md b/exchange/exchange-ps/ExchangePowerShell/Set-TransportServer.md
index 73dbb0b6d9..5fc2ac7ac3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-TransportServer.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-TransportServer.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -152,7 +152,7 @@ This example sets the ReceiveProtocolLogPath parameter to C:\\SMTP Protocol Logs
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the Transport server that you want to modify. You can use any value that uniquely identifies the server. For example:
 
@@ -175,7 +175,7 @@ Accept wildcard characters: False
 
 ### -ActiveUserStatisticsLogMaxAge
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ActiveUserStatisticsLogMaxAge parameter specifies the maximum duration that the per user activity statistics log files are kept. Log files older than the specified value are deleted. The default value is 30 days.
 
@@ -197,7 +197,7 @@ Accept wildcard characters: False
 
 ### -ActiveUserStatisticsLogMaxDirectorySize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ActiveUserStatisticsLogMaxDirectorySize parameter specifies the cap on the size of the per user activity statistics log directory. When the maximum directory size is reached, the server deletes the oldest log files first. The minimum value is 1 megabyte (MB). The default value is 250 MB.
 
@@ -227,7 +227,7 @@ Accept wildcard characters: False
 
 ### -ActiveUserStatisticsLogMaxFileSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ActiveUserStatisticsLogMaxFileSize parameter specifies the maximum file size for the per user activity statistics log files. When a log file reaches its maximum file size, a new log file is created. The default value is 10 MB.
 
@@ -257,7 +257,7 @@ Accept wildcard characters: False
 
 ### -ActiveUserStatisticsLogPath
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ActiveUserStatisticsLogPath parameter specifies the location of per user activity statistics log storage. The default location depends on your version of Exchange:
 
@@ -280,7 +280,7 @@ Accept wildcard characters: False
 
 ### -AgentLogEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AgentLogEnabled parameter specifies whether the agent log is enabled. The default value is $true.
 
@@ -298,7 +298,7 @@ Accept wildcard characters: False
 
 ### -AgentLogMaxAge
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AgentLogMaxAge parameter specifies the maximum age for the agent log file. Log files older than the specified value are deleted. The default value is 7.00:00:00 or 7 days.
 
@@ -320,7 +320,7 @@ Accept wildcard characters: False
 
 ### -AgentLogMaxDirectorySize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AgentLogMaxDirectorySize parameter specifies the maximum size of all agent logs in the agent log directory. When a directory reaches its maximum file size, the server deletes the oldest log files first. The default value is 250 MB.
 
@@ -350,7 +350,7 @@ Accept wildcard characters: False
 
 ### -AgentLogMaxFileSize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AgentLogMaxFileSize parameter specifies the maximum size of each agent log file. When a log file reaches its maximum file size, a new log file is created. The default value is 10 MB.
 
@@ -380,7 +380,7 @@ Accept wildcard characters: False
 
 ### -AgentLogPath
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AgentLogPath parameter specifies the default agent log directory location. The default location is %ExchangeInstallPath%TransportRoles\\Logs\\Hub\\AgentLog. Setting the value of this parameter to $null disables agent logging. However, setting this parameter to $null when the value of the AgentLogEnabled attribute is $true generates event log errors.
 
@@ -398,7 +398,7 @@ Accept wildcard characters: False
 
 ### -AntispamAgentsEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AntispamAgentsEnabled parameter specifies whether anti-spam agents are installed on the server specified with the Identity parameter. The default value is $false for the Transport service on Mailbox servers and $true on Edge servers.
 
@@ -418,7 +418,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -439,7 +439,7 @@ Accept wildcard characters: False
 
 ### -ConnectivityLogEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ConnectivityLogEnabled parameter specifies whether the connectivity log is enabled. The default value is $true.
 
@@ -457,7 +457,7 @@ Accept wildcard characters: False
 
 ### -ConnectivityLogMaxAge
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ConnectivityLogMaxAge parameter specifies the maximum age for the connectivity log file. Log files older than the specified value are deleted. The default value is 30 days.
 
@@ -479,7 +479,7 @@ Accept wildcard characters: False
 
 ### -ConnectivityLogMaxDirectorySize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ConnectivityLogMaxDirectorySize parameter specifies the maximum size of all connectivity logs in the connectivity log directory. When a directory reaches its maximum file size, the server deletes the oldest log files first. The default value is 1000 MB.
 
@@ -509,7 +509,7 @@ Accept wildcard characters: False
 
 ### -ConnectivityLogMaxFileSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ConnectivityLogMaxFileSize parameter specifies the maximum size of each connectivity log file. When a log file reaches its maximum file size, a new log file is created. The default value is 10 MB.
 
@@ -539,7 +539,7 @@ Accept wildcard characters: False
 
 ### -ConnectivityLogPath
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ConnectivityLogPath parameter specifies the default connectivity log directory location. The default location depends on your version of Exchange:
 
@@ -562,7 +562,7 @@ Accept wildcard characters: False
 
 ### -ContentConversionTracingEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ContentConversionTracingEnabled parameter specifies whether content conversion tracing is enabled. Content conversion tracing captures content conversion failures that occur in the Transport service on a Mailbox server or on the Edge server. The default value is $false. Content conversion tracing captures a maximum of 128 MB of content conversion failures. When the 128 MB limit is reached, no more content conversion failures are captured. Content conversion tracing captures the complete contents of messages to the path specified by the PipelineTracingPath parameter. Make sure that you restrict access to this directory. The permissions required on the directory specified by the PipelineTracingPath parameter are as follows:
 
@@ -584,7 +584,7 @@ Accept wildcard characters: False
 
 ### -DelayNotificationTimeout
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DelayNotificationTimeout parameter specifies how long the server waits before it generates a delayed delivery status notification (DSN) message. The default value is 4 hours.
 
@@ -606,7 +606,7 @@ Accept wildcard characters: False
 
 ### -DnsLogEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DnsLogEnabled parameter specifies whether the DNS log is enabled. The default value is $false.
 
@@ -624,7 +624,7 @@ Accept wildcard characters: False
 
 ### -DnsLogMaxAge
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DnsLogMaxAge parameter specifies the maximum age for the DNS log file. Log files older than the specified value are deleted. The default value is 7.00:00:00 or 7 days.
 
@@ -646,7 +646,7 @@ Accept wildcard characters: False
 
 ### -DnsLogMaxDirectorySize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DnsLogMaxDirectorySize parameter specifies the maximum size of all DNS logs in the DNS log directory. When a directory reaches its maximum file size, the server deletes the oldest log files first. The default value is 100 MB.
 
@@ -676,7 +676,7 @@ Accept wildcard characters: False
 
 ### -DnsLogMaxFileSize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DnsLogMaxFileSize parameter specifies the maximum size of each DNS log file. When a log file reaches its maximum file size, a new log file is created. The default value is 10 MB.
 
@@ -706,7 +706,7 @@ Accept wildcard characters: False
 
 ### -DnsLogPath
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DnsLogPath parameter specifies the DNS log directory location. The default value is blank ($null), which indicates no location is configured. If you enable DNS logging, you need to specify a local file path for the DNS log files by using this parameter. If the path contains spaces, enclose the entire path value in quotation marks (").
 
@@ -724,7 +724,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -744,7 +744,7 @@ Accept wildcard characters: False
 
 ### -ExternalDNSAdapterEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExternalDNSAdapterEnabled parameter specifies one or more Domain Name System (DNS) servers that Exchange uses for external DNS lookups. When the ExternalDNSAdapterEnabled parameter is set to $true, DNS lookups of destinations outside the Exchange organization are performed by using the DNS settings of the external network adapter specified by the value of the ExternalDNSAdapterGuid parameter. If you want to specify a custom list of DNS servers used for external Exchange DNS lookups only, you must specify the DNS servers by using the ExternalDNSServers parameter, and you must also set the value of the ExternalDNSAdapterEnabled parameter to $false. The default value of the ExternalDNSAdapterEnabled parameter is $true.
 
@@ -762,7 +762,7 @@ Accept wildcard characters: False
 
 ### -ExternalDNSAdapterGuid
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExternalDNSAdapterGuid parameter specifies the network adapter that has the DNS settings used for DNS lookups of destinations that exist outside the Exchange organization. The concept of an external network adapter and an internal network adapter is only applicable in a multi-homed Exchange server environment. When no particular network adapter is specified as the network adapter for external DNS lookups, the value of the ExternalDNSAdapterGuid parameter is 00000000-0000-0000-0000-000000000000, and external DNS lookups are performed by using the DNS settings of any available network adapter. You might enter the GUID of a specific network adapter to use for external DNS lookups. The default value of the ExternalDNSAdapterGuid parameter is 00000000-0000-0000-0000-000000000000.
 
@@ -782,7 +782,7 @@ Accept wildcard characters: False
 
 ### -ExternalDNSProtocolOption
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExternalDNSProtocolOption parameter specifies which protocol to use when querying external DNS servers. The valid options for this parameter are Any, UseTcpOnly, and UseUdpOnly. The default value is Any.
 
@@ -800,7 +800,7 @@ Accept wildcard characters: False
 
 ### -ExternalDNSServers
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExternalDNSServers parameter specifies the list of external DNS servers that the server queries when resolving a remote domain. DNS servers are specified by IP address. The default value is an empty list ({}).
 
@@ -824,7 +824,7 @@ Accept wildcard characters: False
 
 ### -ExternalIPAddress
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExternalIPAddress parameter specifies the IP address used in the Received message header field for every message that travels through the Edge server or the Transport service on a Mailbox server. The IP address in the Received header field is used for hop count and routing loop detection. The IP address specified by the ExternalIPAddress parameter overrides the external network adapter's actual IP address. Typically, you would want to set the value of the ExternalIPAddress parameter to match the value of your domain's public MX record. The default value of the ExternalIPAddress parameter is blank. This means the actual IP address of the external network adapter is used in the Received header field.
 
@@ -842,7 +842,7 @@ Accept wildcard characters: False
 
 ### -InternalDNSAdapterEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The InternalDNSAdapterEnabled parameter specifies one or more DNS servers that Exchange uses for internal DNS lookups. When the InternalDNSAdapterEnabled parameter is set to $true, DNS lookups of destinations inside the Exchange organization are performed by using the DNS settings of the internal network adapter specified by the value of the InternalDNSAdapterGuid parameter. If you want to specify a custom list of DNS servers used for internal Exchange DNS lookups only, you must specify the DNS servers by using the InternalDNSServers parameter, and you must also set the value of the InternalDNSAdapterEnabled parameter to $false. The default value of the InternalDNSAdapterEnabled parameter is $true.
 
@@ -860,7 +860,7 @@ Accept wildcard characters: False
 
 ### -InternalDNSAdapterGuid
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The InternalDNSAdapterGuid parameter specifies the network adapter that has the DNS settings used for DNS lookups of servers that exist inside the Exchange organization. The concept of an internal network adapter and an external network adapter is only applicable in a multi-homed Exchange server environment. When no particular network adapter is specified as the network adapter for external DNS lookups, the value of the InternalDNSAdapterGuid parameter is 00000000-0000-0000-0000-000000000000, and internal DNS lookups are performed by using the DNS settings of any available network adapter. You might enter the GUID of a specific network adapter to use for internal DNS lookups. The default value of the InternalDNSAdapterGuid parameter is 00000000-0000-0000-0000-000000000000.
 
@@ -880,7 +880,7 @@ Accept wildcard characters: False
 
 ### -InternalDNSProtocolOption
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The InternalDNSProtocolOption parameter specifies which protocol to use when you query internal DNS servers. Valid options for this parameter are Any, UseTcpOnly, or UseUdpOnly.
 
@@ -900,7 +900,7 @@ Accept wildcard characters: False
 
 ### -InternalDNSServers
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The InternalDNSServers parameter specifies the list of DNS servers that should be used when resolving a domain name. DNS servers are specified by IP address. The default value is any empty list ({}).
 
@@ -924,7 +924,7 @@ Accept wildcard characters: False
 
 ### -IntraOrgConnectorProtocolLoggingLevel
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IntraOrgConnectorProtocolLoggingLevel parameter enables or disables SMTP protocol logging on the implicit and invisible intra-organization Send connectors that are used to transmit messages between Exchange servers in the Exchange organization.
 
@@ -944,7 +944,7 @@ Accept wildcard characters: False
 
 ### -IntraOrgConnectorSmtpMaxMessagesPerConnection
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IntraOrgConnectorSmtpMaxMessagesPerConnection parameter specifies the maximum number of messages per connection limit on the implicit and invisible intra-organization Send connectors that are used to transmit messages between Exchange servers in the Exchange organization.
 
@@ -962,7 +962,7 @@ Accept wildcard characters: False
 
 ### -IrmLogEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IrmLogEnabled parameter enables logging of Information Rights Management (IRM) transactions. IRM logging is enabled by default. Values include:
 
@@ -983,7 +983,7 @@ Accept wildcard characters: False
 
 ### -IrmLogMaxAge
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IrmLogMaxAge parameter specifies the maximum age for the IRM log file. Log files that are older than the specified value are deleted. The default value is 30 days.
 
@@ -1005,7 +1005,7 @@ Accept wildcard characters: False
 
 ### -IrmLogMaxDirectorySize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This IrmLogMaxDirectorySize parameter specifies the maximum size of all IRM logs in the connectivity log directory. When a directory reaches its maximum file size, the server deletes the oldest log files first. The default value is 250 MB.
 
@@ -1035,7 +1035,7 @@ Accept wildcard characters: False
 
 ### -IrmLogMaxFileSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This IrmLogMaxFileSize parameter specifies the maximum size of each IRM log file. When a log file reaches its maximum file size, a new log file is created. The default value is 10 MB.
 
@@ -1065,7 +1065,7 @@ Accept wildcard characters: False
 
 ### -IrmLogPath
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IrmLogPath parameter specifies the default IRM log directory location. The default location is %ExchangeInstallPath%Logging\\IRMLogs.
 
@@ -1085,7 +1085,7 @@ Accept wildcard characters: False
 
 ### -MaxConcurrentMailboxDeliveries
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MaxConcurrentMailboxDeliveries parameter specifies the maximum number of delivery threads that the transport service can have open at the same time to deliver messages to mailboxes. The default value is 20. The valid input range for this parameter is from 1 through 256. We recommend that you don't modify the default value unless Microsoft Customer Service and Support advises you to do this.
 
@@ -1103,7 +1103,7 @@ Accept wildcard characters: False
 
 ### -MaxConcurrentMailboxSubmissions
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MaxConcurrentMailboxSubmissions parameter specifies the maximum number of submission threads that the transport service can have open at the same time to send messages from mailboxes. The default value is 20. The valid input range for this parameter is from 1 through 256.
 
@@ -1121,7 +1121,7 @@ Accept wildcard characters: False
 
 ### -MaxConnectionRatePerMinute
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MaxConnectionRatePerMinute parameter specifies the maximum rate that connections are allowed to be opened with the transport service. If many connections are attempted with the transport service at the same time, the MaxConnectionRatePerMinute parameter limits the rate that the connections are opened so that the server's resources aren't overwhelmed. The default value is 1200 connections per minute. The valid input range for this parameter is from 1 through 2147483647.
 
@@ -1139,7 +1139,7 @@ Accept wildcard characters: False
 
 ### -MaxOutboundConnections
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MaxOutboundConnections parameter specifies the maximum number of outbound connections that can be open at a time. The default value is 1000. The valid input range for this parameter is from 1 through 2147483647. If you enter a value of unlimited, no limit is imposed on the number of outbound connections. The value of the MaxOutboundConnections parameter must be greater than or equal to the value of the MaxPerDomainOutboundConnections parameter.
 
@@ -1157,7 +1157,7 @@ Accept wildcard characters: False
 
 ### -MaxPerDomainOutboundConnections
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MaxPerDomainOutboundConnections parameter specifies the maximum number of concurrent connections to any single domain. The default value is 40. The valid input range for this parameter is from 1 through 2147483647. If you enter a value of unlimited, no limit is imposed on the number of outbound connections per domain. The value of the MaxPerDomainOutboundConnections parameter must be less than or equal to the value of the MaxOutboundConnections parameter.
 
@@ -1175,7 +1175,7 @@ Accept wildcard characters: False
 
 ### -MessageExpirationTimeout
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MessageExpirationTimeout parameter specifies the maximum time that a particular message can remain in a queue. If a message remains in the queue for longer than this period of time, the message is returned to the sender as a permanent failure. The default value is 2 days.
 
@@ -1197,7 +1197,7 @@ Accept wildcard characters: False
 
 ### -MessageRetryInterval
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MessageRetryInterval parameter specifies the retry interval for individual messages after a connection failure with a remote server. The default value is 5 minutes.
 
@@ -1219,7 +1219,7 @@ Accept wildcard characters: False
 
 ### -MessageTrackingLogEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MessageTrackingLogEnabled parameter specifies whether message tracking is enabled. The default value is $true.
 
@@ -1237,7 +1237,7 @@ Accept wildcard characters: False
 
 ### -MessageTrackingLogMaxAge
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MessageTrackingLogMaxAge parameter specifies the message tracking log maximum file age. Log files older than the specified value are deleted. The default value is 30 days.
 
@@ -1259,7 +1259,7 @@ Accept wildcard characters: False
 
 ### -MessageTrackingLogMaxDirectorySize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MessageTrackingLogMaxDirectorySize parameter specifies the maximum size of the message tracking log directory. When the maximum directory size is reached, the server deletes the oldest log files first.
 
@@ -1295,7 +1295,7 @@ Accept wildcard characters: False
 
 ### -MessageTrackingLogMaxFileSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MessageTrackingLogMaxFileSize parameter specifies the maximum size of the message tracking log files. When a log file reaches its maximum file size, a new log file is created. The default value is 10 MB.
 
@@ -1324,7 +1324,7 @@ Accept wildcard characters: False
 
 ### -MessageTrackingLogPath
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MessageTrackingLogPath parameter specifies the location of the message tracking logs. The default location is %ExchangeInstallPath%TransportRoles\\Logs\\MessageTracking. Setting the value of this parameter to $null disables message tracking. However, setting this parameter to $null when the value of the MessageTrackingLogEnabled attribute is $true generates event log errors. The preferred method to disable message tracking is to use the MessageTrackingLogEnabled parameter.
 
@@ -1342,7 +1342,7 @@ Accept wildcard characters: False
 
 ### -MessageTrackingLogSubjectLoggingEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MessageTrackingLogSubjectLoggingEnabled parameter specifies whether the message subject should be included in the message tracking log. The default value is $true.
 
@@ -1360,7 +1360,7 @@ Accept wildcard characters: False
 
 ### -OutboundConnectionFailureRetryInterval
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The OutboundConnectionFailureRetryInterval parameter specifies the retry interval for subsequent connection attempts to a remote server where previous connection attempts have failed. The previously failed connection attempts are controlled by the TransientFailureRetryCount and TransientFailureRetryInterval parameters. For the Transport service on a Mailbox server, the default value of the OutboundConnectionFailureRetryInterval parameter is 10 minutes. On an Edge server, the default value is 30 minutes.
 
@@ -1382,7 +1382,7 @@ Accept wildcard characters: False
 
 ### -PickupDirectoryMaxHeaderSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PickupDirectoryMaxHeaderSize parameter specifies the maximum message header size that can be submitted to the Pickup directory. The default value is 64 KB.
 
@@ -1411,7 +1411,7 @@ Accept wildcard characters: False
 
 ### -PickupDirectoryMaxMessagesPerMinute
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PickupDirectoryMaxMessagesPerMinute parameter specifies the maximum number of messages processed per minute by the Pickup directory and by the Replay directory. Each directory can independently process message files at the rate specified by the PickupDirectoryMaxMessagesPerMinute parameter. The default value is 100. The valid input range for this parameter is from 1 through 20000.
 
@@ -1429,7 +1429,7 @@ Accept wildcard characters: False
 
 ### -PickupDirectoryMaxRecipientsPerMessage
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PickupDirectoryMaxRecipientsPerMessage parameter specifies the maximum number of recipients that can be included on an message. The default value is 100. The valid input range for this parameter is from 1 through 10000.
 
@@ -1447,7 +1447,7 @@ Accept wildcard characters: False
 
 ### -PickupDirectoryPath
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PickupDirectoryPath parameter specifies the location of the Pickup directory. The Pickup directory is used by administrators and non-Microsoft applications to create and submit messages. The default location is %ExchangeInstallPath%TransportRoles\\Pickup. If the value of the PickupDirectoryPath parameter is set to $null, the Pickup directory is disabled.
 
@@ -1465,7 +1465,7 @@ Accept wildcard characters: False
 
 ### -PipelineTracingEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PipelineTracingEnabled parameter specifies whether to enable pipeline tracing. Pipeline tracing captures message snapshot files that record the changes made to the message by each transport agent configured in the transport service on the server. Pipeline tracing creates verbose log files that accumulate quickly. Pipeline tracing should only be enabled for a short time to provide in-depth diagnostic information that enables you to troubleshoot problems. In addition to troubleshooting, you can use pipeline tracing to validate changes that you make to the configuration of the transport service where you enable pipeline tracing. The default value is $false.
 
@@ -1483,7 +1483,7 @@ Accept wildcard characters: False
 
 ### -PipelineTracingPath
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PipelineTracingPath parameter specifies the location of the pipeline tracing logs. The default location depends on your version of Exchange:
 
@@ -1514,7 +1514,7 @@ Accept wildcard characters: False
 
 ### -PipelineTracingSenderAddress
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PipelineTracingSenderAddress parameter specifies the sender address that invokes pipeline tracing. Only messages from this address generate pipeline tracing output. The address can be either inside or outside the Exchange organization. Depending on your requirements, you might have to set this parameter to different sender addresses and send new messages to start the transport agents or routes that you want to test. The default value of this parameter is $null.
 
@@ -1532,7 +1532,7 @@ Accept wildcard characters: False
 
 ### -PoisonMessageDetectionEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PoisonMessageDetectionEnabled parameter specifies whether poison messages should be detected. The default value is $true. Poison messages are messages determined to be potentially harmful to the Exchange system after a server failure. Poison messages are put in the poison message queue. We recommend that you don't modify the default value unless Customer Service and Support advises you to do this.
 
@@ -1550,7 +1550,7 @@ Accept wildcard characters: False
 
 ### -PoisonThreshold
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PoisonThreshold parameter specifies the number of times a message can be rejected before it's classified as a poison message. The default value is 2. We recommend that you don't modify the default value unless Customer Service and Support advises you to do this. The valid input range for this parameter is from 1 through 10.
 
@@ -1568,7 +1568,7 @@ Accept wildcard characters: False
 
 ### -QueueMaxIdleTime
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The QueueMaxIdleTime parameter specifies the period of time an empty delivery queue can exist before the queue is removed. The default value is 3 minutes.
 
@@ -1590,7 +1590,7 @@ Accept wildcard characters: False
 
 ### -QueueLogMaxAge
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The QueueLogMaxAge parameter specifies the maximum age of the queue log files. Log files that are older than the specified value are deleted. The default value is 7 days.
 
@@ -1612,7 +1612,7 @@ Accept wildcard characters: False
 
 ### -QueueLogMaxDirectorySize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The QueueLogMaxDirectorySize parameter specifies the maximum size of the queue log directory. When the maximum directory size is reached, the server deletes the oldest log files first. The default value is 200 MB.
 
@@ -1642,7 +1642,7 @@ Accept wildcard characters: False
 
 ### -QueueLogMaxFileSize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The QueueLogMaxFileSize parameter specifies the maximum size of the queue log files. When a log file reaches its maximum file size, a new log file is created. The default value is 10 MB.
 
@@ -1672,7 +1672,7 @@ Accept wildcard characters: False
 
 ### -QueueLogPath
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The QueueLogPath parameter specifies the path of the queue log directory. The default location is %ExchangeInstallPath%TransportRoles\\Logs\\Hub\\QueueViewer. Setting the value of this parameter to $null disables queue logging.
 
@@ -1690,7 +1690,7 @@ Accept wildcard characters: False
 
 ### -ReceiveProtocolLogMaxAge
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ReceiveProtocolLogMaxAge parameter specifies the maximum age of the Receive connector protocol log file. Log files that are older than the specified value are deleted. The default value is 30 days.
 
@@ -1712,7 +1712,7 @@ Accept wildcard characters: False
 
 ### -ReceiveProtocolLogMaxDirectorySize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ReceiveProtocolLogMaxDirectorySize parameter specifies the maximum size of the Receive connector protocol log directory shared by all the Receive connectors that exist on the server. When the maximum directory size is reached, the server deletes the oldest log files first. The default value is 250 MB.
 
@@ -1742,7 +1742,7 @@ Accept wildcard characters: False
 
 ### -ReceiveProtocolLogMaxFileSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ReceiveProtocolLogMaxFileSize parameter specifies the maximum size of the Receive connector protocol log files shared by all the Receive connectors that exist on the server. When a log file reaches its maximum file size, a new log file is created. The default value is 10 MB.
 
@@ -1772,7 +1772,7 @@ Accept wildcard characters: False
 
 ### -ReceiveProtocolLogPath
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ReceiveProtocolLogPath parameter specifies the path of the protocol log directory for all the Receive connectors that exist on the server. The default location depends on your version of Exchange:
 
@@ -1795,7 +1795,7 @@ Accept wildcard characters: False
 
 ### -RecipientValidationCacheEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RecipientValidationCacheEnabled parameter specifies whether the recipient addresses used by transport agents, such as the Recipient Filtering agent, are cached. The default value is $true on Edge servers and $false for the Transport service on Mailbox servers.
 
@@ -1813,7 +1813,7 @@ Accept wildcard characters: False
 
 ### -ReplayDirectoryPath
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ReplayDirectoryPath parameter specifies the path of the Replay directory. The Replay directory is used to resubmit exported messages and to receive messages from foreign gateway servers. The default location is %ExchangeInstallPath%TransportRoles\\Replay. If the value of the ReplayDirectoryPath parameter is set to $null, the Replay directory is disabled.
 
@@ -1831,7 +1831,7 @@ Accept wildcard characters: False
 
 ### -RootDropDirectoryPath
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RootDropDirectoryPath parameter specifies the top-level location of the Drop directory used by all Foreign connectors defined in the Transport service on a Mailbox server. The value of the RootDropDirectoryPath parameter might be a local path, or a Universal Naming Convention (UNC) path to a remote server. By default, the RootDropDirectoryPath parameter is blank. This indicates the value of RootDropDirectoryPath is the Exchange installation folder. The RootDropDirectoryPath parameter is used with the DropDirectory parameter in the Set-ForeignConnector cmdlet to specify the location for outgoing messages going to the address spaces defined on the Foreign connector.
 
@@ -1849,7 +1849,7 @@ Accept wildcard characters: False
 
 ### -RoutingTableLogMaxAge
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RoutingTableLogMaxAge parameter specifies the maximum routing table log age. Log files older than the specified value are deleted. The default value is 7 days.
 
@@ -1871,7 +1871,7 @@ Accept wildcard characters: False
 
 ### -RoutingTableLogMaxDirectorySize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RoutingTableLogMaxDirectorySize parameter specifies the maximum size of the routing table log directory. When the maximum directory size is reached, the server deletes the oldest log files first. The default value is 50 MB.
 
@@ -1901,7 +1901,7 @@ Accept wildcard characters: False
 
 ### -RoutingTableLogPath
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RoutingTableLogPath parameter specifies the directory location where routing table log files should be stored. The default location depends on your version of Exchange:
 
@@ -1924,7 +1924,7 @@ Accept wildcard characters: False
 
 ### -SendProtocolLogMaxAge
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SendProtocolLogMaxAge parameter specifies the Send connector protocol log file maximum age. Log files older than the specified value are deleted. The default value is 30 days.
 
@@ -1946,7 +1946,7 @@ Accept wildcard characters: False
 
 ### -SendProtocolLogMaxDirectorySize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SendProtocolLogMaxDirectorySize parameter specifies the maximum size of the Send connector protocol log directory. When the maximum directory size is reached, the server deletes the oldest log files first. The minimum value is 1 MB. The default value is 250 MB.
 
@@ -1976,7 +1976,7 @@ Accept wildcard characters: False
 
 ### -SendProtocolLogMaxFileSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SendProtocolLogMaxFileSize parameter specifies the maximum size of the Send connector protocol log files shared by all the Send connectors that exist on a server. When a log file reaches its maximum file size, a new log file is created. The default value is 10 MB.
 
@@ -2006,7 +2006,7 @@ Accept wildcard characters: False
 
 ### -SendProtocolLogPath
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SendProtocolLogPath parameter specifies the location of protocol log storage for the Send connectors. The default location depends on your version of Exchange:
 
@@ -2029,7 +2029,7 @@ Accept wildcard characters: False
 
 ### -ServerStatisticsLogMaxAge
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is functional only in Exchange Server 2010 and Exchange 2013 CU6 or earlier.
 
@@ -2053,7 +2053,7 @@ Accept wildcard characters: False
 
 ### -ServerStatisticsLogMaxDirectorySize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is functional only in Exchange Server 2010 and Exchange 2013 CU6 or earlier.
 
@@ -2083,7 +2083,7 @@ Accept wildcard characters: False
 
 ### -ServerStatisticsLogMaxFileSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is functional only in Exchange Server 2010 and Exchange 2013 CU6 or earlier.
 
@@ -2113,7 +2113,7 @@ Accept wildcard characters: False
 
 ### -ServerStatisticsLogPath
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is functional only in Exchange Server 2010 and Exchange 2013 CU6 or earlier.
 
@@ -2138,7 +2138,7 @@ Accept wildcard characters: False
 
 ### -TransientFailureRetryCount
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TransientFailureRetryCount parameter specifies the maximum number of immediate connection retries attempted when the server encounters a connection failure with a remote server. The default value is 6. The valid input range for this parameter is from 0 through 15. When the value of this parameter is set to 0, the server doesn't immediately attempt to retry an unsuccessful connection, and the next connection attempt is controlled by the OutboundConnectionFailureRetryInterval parameter.
 
@@ -2156,7 +2156,7 @@ Accept wildcard characters: False
 
 ### -TransientFailureRetryInterval
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TransientFailureRetryInterval parameter controls the connection interval between each connection attempt specified by the TransientFailureRetryCount parameter. For the Transport service on a Mailbox server, the default value of the TransientFailureRetryInterval parameter is 5 minutes. On an Edge server, the default value is 10 minutes.
 
@@ -2178,7 +2178,7 @@ Accept wildcard characters: False
 
 ### -UseDowngradedExchangeServerAuth
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The UseDowngradedExchangeServerAuth parameter specifies whether the Generic Security Services application programming interface (GSSAPI) authentication method is used on connections where Transport Layer Security (TLS) is disabled.
 
@@ -2200,7 +2200,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
@@ -2218,7 +2218,7 @@ Accept wildcard characters: False
 
 ### -WlmLogMaxAge
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -2236,7 +2236,7 @@ Accept wildcard characters: False
 
 ### -WlmLogMaxDirectorySize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -2254,7 +2254,7 @@ Accept wildcard characters: False
 
 ### -WlmLogMaxFileSize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -2272,7 +2272,7 @@ Accept wildcard characters: False
 
 ### -WlmLogPath
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-TransportService.md b/exchange/exchange-ps/ExchangePowerShell/Set-TransportService.md
index 60535549df..1c8982c109 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-TransportService.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-TransportService.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -194,7 +194,7 @@ This example sets the ReceiveProtocolLogPath parameter to C:\\SMTP Protocol Logs
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the Mailbox server that hosts the Transport service configuration you want to modify. You can use any value that uniquely identifies the server. For example:
 
@@ -219,7 +219,7 @@ Accept wildcard characters: False
 
 ### -ActiveUserStatisticsLogMaxAge
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ActiveUserStatisticsLogMaxAge parameter specifies the maximum duration that the per user activity statistics log files are kept. Log files older than the specified value are deleted. The default value is 30 days.
 
@@ -241,7 +241,7 @@ Accept wildcard characters: False
 
 ### -ActiveUserStatisticsLogMaxDirectorySize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ActiveUserStatisticsLogMaxDirectorySize parameter specifies the cap on the size of the per user activity statistics log directory. When the maximum directory size is reached, the server deletes the oldest log files first. The minimum value is 1 megabyte (MB). The default value is 250 MB.
 
@@ -271,7 +271,7 @@ Accept wildcard characters: False
 
 ### -ActiveUserStatisticsLogMaxFileSize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ActiveUserStatisticsLogMaxFileSize parameter specifies the maximum file size for the per user activity statistics log files. When a log file reaches its maximum file size, a new log file is created. The default value is 10 MB.
 
@@ -301,7 +301,7 @@ Accept wildcard characters: False
 
 ### -ActiveUserStatisticsLogPath
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ActiveUserStatisticsLogPath parameter specifies the location of per user activity statistics log storage. The default location is %ExchangeInstallPath%TransportRoles\\Logs\\Hub\\ActiveUsersStats. Setting the value of this parameter to $null disables server statistics logging.
 
@@ -319,7 +319,7 @@ Accept wildcard characters: False
 
 ### -AgentLogEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AgentLogEnabled parameter specifies whether the agent log is enabled. The default value is $true.
 
@@ -337,7 +337,7 @@ Accept wildcard characters: False
 
 ### -AgentLogMaxAge
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AgentLogMaxAge parameter specifies the maximum age for the agent log file. Log files older than the specified value are deleted. The default value is 7.00:00:00 or 7 days.
 
@@ -359,7 +359,7 @@ Accept wildcard characters: False
 
 ### -AgentLogMaxDirectorySize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AgentLogMaxDirectorySize parameter specifies the maximum size of all agent logs in the agent log directory. When a directory reaches its maximum file size, the server deletes the oldest log files first. The default value is 250 MB.
 
@@ -389,7 +389,7 @@ Accept wildcard characters: False
 
 ### -AgentLogMaxFileSize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AgentLogMaxFileSize parameter specifies the maximum size of each agent log file. When a log file reaches its maximum file size, a new log file is created. The default value is 10 MB.
 
@@ -419,7 +419,7 @@ Accept wildcard characters: False
 
 ### -AgentLogPath
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AgentLogPath parameter specifies the default agent log directory location. The default location is %ExchangeInstallPath%TransportRoles\\Logs\\Hub\\AgentLog. Setting the value of this parameter to $null disables agent logging. However, setting this parameter to $null when the value of the AgentLogEnabled attribute is $true generates event log errors.
 
@@ -437,7 +437,7 @@ Accept wildcard characters: False
 
 ### -AntispamAgentsEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AntispamAgentsEnabled parameter specifies whether anti-spam agents are installed on the server specified with the Identity parameter. The default value is $false for the Transport service on Mailbox servers and $true on Edge Transport servers.
 
@@ -457,7 +457,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -478,7 +478,7 @@ Accept wildcard characters: False
 
 ### -ConnectivityLogEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ConnectivityLogEnabled parameter specifies whether the connectivity log is enabled. The default value is $true.
 
@@ -496,7 +496,7 @@ Accept wildcard characters: False
 
 ### -ConnectivityLogMaxAge
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ConnectivityLogMaxAge parameter specifies the maximum age for the connectivity log file. Log files older than the specified value are deleted. The default value is 30 days.
 
@@ -518,7 +518,7 @@ Accept wildcard characters: False
 
 ### -ConnectivityLogMaxDirectorySize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ConnectivityLogMaxDirectorySize parameter specifies the maximum size of all connectivity logs in the connectivity log directory. When a directory reaches its maximum file size, the server deletes the oldest log files first. The default value is 1000 MB.
 
@@ -548,7 +548,7 @@ Accept wildcard characters: False
 
 ### -ConnectivityLogMaxFileSize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ConnectivityLogMaxFileSize parameter specifies the maximum size of each connectivity log file. When a log file reaches its maximum file size, a new log file is created. The default value is 10 MB.
 
@@ -578,7 +578,7 @@ Accept wildcard characters: False
 
 ### -ConnectivityLogPath
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ConnectivityLogPath parameter specifies the default connectivity log directory location. The default location is %ExchangeInstallPath%TransportRoles\\Logs\\Hub\\Connectivity. Setting the value of this parameter to $null disables connectivity logging. However, setting this parameter to $null when the value of the ConnectivityLogEnabled attribute is $true generates event log errors.
 
@@ -596,7 +596,7 @@ Accept wildcard characters: False
 
 ### -ContentConversionTracingEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ContentConversionTracingEnabled parameter specifies whether content conversion tracing is enabled. Content conversion tracing captures content conversion failures that occur in the Transport service on a Mailbox server or on the Edge Transport server. The default value is $false. Content conversion tracing captures a maximum of 128 MB of content conversion failures. When the 128 MB limit is reached, no more content conversion failures are captured. Content conversion tracing captures the complete contents of email messages to the path specified by the PipelineTracingPath parameter. Make sure that you restrict access to this directory. The permissions required on the directory specified by the PipelineTracingPath parameter are as follows:
 
@@ -618,7 +618,7 @@ Accept wildcard characters: False
 
 ### -DelayNotificationTimeout
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DelayNotificationTimeout parameter specifies how long the server waits before it generates a delayed delivery status notification (DSN) message. The default value is 4 hours.
 
@@ -640,7 +640,7 @@ Accept wildcard characters: False
 
 ### -DnsLogEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DnsLogEnabled parameter specifies whether the DNS log is enabled. The default value is $false.
 
@@ -658,7 +658,7 @@ Accept wildcard characters: False
 
 ### -DnsLogMaxAge
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DnsLogMaxAge parameter specifies the maximum age for the DNS log file. Log files older than the specified value are deleted. The default value is 7.00:00:00 or 7 days.
 
@@ -680,7 +680,7 @@ Accept wildcard characters: False
 
 ### -DnsLogMaxDirectorySize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DnsLogMaxDirectorySize parameter specifies the maximum size of all DNS logs in the DNS log directory. When a directory reaches its maximum file size, the server deletes the oldest log files first. The default value is 100 MB.
 
@@ -710,7 +710,7 @@ Accept wildcard characters: False
 
 ### -DnsLogMaxFileSize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DnsLogMaxFileSize parameter specifies the maximum size of each DNS log file. When a log file reaches its maximum file size, a new log file is created. The default value is 10 MB.
 
@@ -740,7 +740,7 @@ Accept wildcard characters: False
 
 ### -DnsLogPath
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DnsLogPath parameter specifies the DNS log directory location. The default value is blank ($null), which indicates no location is configured. If you enable DNS logging, you need to specify a local file path for the DNS log files by using this parameter. If the path contains spaces, enclose the entire path value in quotation marks (").
 
@@ -758,7 +758,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -778,7 +778,7 @@ Accept wildcard characters: False
 
 ### -ExternalDNSAdapterEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExternalDNSAdapterEnabled parameter specifies one or more Domain Name System (DNS) servers that Exchange uses for external DNS lookups. When the ExternalDNSAdapterEnabled parameter is set to $true, DNS lookups of destinations outside the Exchange organization are performed by using the DNS settings of the external network adapter specified by the value of the ExternalDNSAdapterGuid parameter. If you want to specify a custom list of DNS servers used for external Exchange DNS lookups only, you must specify the DNS servers by using the ExternalDNSServers parameter, and you must also set the value of the ExternalDNSAdapterEnabled parameter to $false. The default value of the ExternalDNSAdapterEnabled parameter is $true.
 
@@ -796,7 +796,7 @@ Accept wildcard characters: False
 
 ### -ExternalDNSAdapterGuid
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExternalDNSAdapterGuid parameter specifies the network adapter that has the DNS settings used for DNS lookups of destinations that exist outside the Exchange organization. The concept of an external network adapter and an internal network adapter is only applicable in a multi-homed Exchange server environment. When no particular network adapter is specified as the network adapter for external DNS lookups, the value of the ExternalDNSAdapterGuid parameter is 00000000-0000-0000-0000-000000000000, and external DNS lookups are performed by using the DNS settings of any available network adapter. You might enter the GUID of a specific network adapter to use for external DNS lookups. The default value of the ExternalDNSAdapterGuid parameter is 00000000-0000-0000-0000-000000000000.
 
@@ -816,7 +816,7 @@ Accept wildcard characters: False
 
 ### -ExternalDNSProtocolOption
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExternalDNSProtocolOption parameter specifies which protocol to use when querying external DNS servers. The valid options for this parameter are Any, UseTcpOnly, and UseUdpOnly. The default value is Any.
 
@@ -834,7 +834,7 @@ Accept wildcard characters: False
 
 ### -ExternalDNSServers
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExternalDNSServers parameter specifies the list of external DNS servers that the server queries when resolving a remote domain. DNS servers are specified by IP address. The default value is an empty list ({}).
 
@@ -858,7 +858,7 @@ Accept wildcard characters: False
 
 ### -ExternalIPAddress
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExternalIPAddress parameter specifies the IP address used in the Received message header field for every message that travels through the Edge Transport server or the Transport service on a Mailbox server. The IP address in the Received header field is used for hop count and routing loop detection. The IP address specified by the ExternalIPAddress parameter overrides the external network adapter's actual IP address. Typically, you would want to set the value of the ExternalIPAddress parameter to match the value of your domain's public MX record. The default value of the ExternalIPAddress parameter is blank. This means the actual IP address of the external network adapter is used in the Received header field.
 
@@ -876,7 +876,7 @@ Accept wildcard characters: False
 
 ### -InternalDNSAdapterEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The InternalDNSAdapterEnabled parameter specifies one or more DNS servers that Exchange uses for internal DNS lookups. When the InternalDNSAdapterEnabled parameter is set to $true, DNS lookups of destinations inside the Exchange organization are performed by using the DNS settings of the internal network adapter specified by the value of the InternalDNSAdapterGuid parameter. If you want to specify a custom list of DNS servers used for internal Exchange DNS lookups only, you must specify the DNS servers by using the InternalDNSServers parameter, and you must also set the value of the InternalDNSAdapterEnabled parameter to $false. The default value of the InternalDNSAdapterEnabled parameter is $true.
 
@@ -894,7 +894,7 @@ Accept wildcard characters: False
 
 ### -InternalDNSAdapterGuid
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The InternalDNSAdapterGuid parameter specifies the network adapter that has the DNS settings used for DNS lookups of servers that exist inside the Exchange organization. The concept of an internal network adapter and an external network adapter is only applicable in a multi-homed Exchange server environment. When no particular network adapter is specified as the network adapter for external DNS lookups, the value of the InternalDNSAdapterGuid parameter is 00000000-0000-0000-0000-000000000000, and internal DNS lookups are performed by using the DNS settings of any available network adapter. You might enter the GUID of a specific network adapter to use for internal DNS lookups. The default value of the InternalDNSAdapterGuid parameter is 00000000-0000-0000-0000-000000000000.
 
@@ -914,7 +914,7 @@ Accept wildcard characters: False
 
 ### -InternalDNSProtocolOption
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The InternalDNSProtocolOption parameter specifies which protocol to use when you query internal DNS servers. Valid options for this parameter are Any, UseTcpOnly, or UseUdpOnly.The default value is Any.
 
@@ -932,7 +932,7 @@ Accept wildcard characters: False
 
 ### -InternalDNSServers
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The InternalDNSServers parameter specifies the list of DNS servers that should be used when resolving a domain name. DNS servers are specified by IP address. The default value is any empty list ({}).
 
@@ -956,7 +956,7 @@ Accept wildcard characters: False
 
 ### -IntraOrgConnectorProtocolLoggingLevel
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IntraOrgConnectorProtocolLoggingLevel parameter enables or disables SMTP protocol logging for the implicit and invisible intra-organization Send connector in the following transport services on the server:
 
@@ -982,7 +982,7 @@ Accept wildcard characters: False
 
 ### -IntraOrgConnectorSmtpMaxMessagesPerConnection
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IntraOrgConnectorSmtpMaxMessagesPerConnection parameter specifies the maximum number of messages per connection that are allowed on the implicit and invisible intra-organization Send connector in the Transport service on the server.
 
@@ -1002,7 +1002,7 @@ Accept wildcard characters: False
 
 ### -IrmLogEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IrmLogEnabled parameter enables logging of Information Rights Management (IRM) transactions. IRM logging is enabled by default. Values include:
 
@@ -1023,7 +1023,7 @@ Accept wildcard characters: False
 
 ### -IrmLogMaxAge
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IrmLogMaxAge parameter specifies the maximum age for the IRM log file. Log files that are older than the specified value are deleted. The default value is 30 days.
 
@@ -1045,7 +1045,7 @@ Accept wildcard characters: False
 
 ### -IrmLogMaxDirectorySize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This IrmLogMaxDirectorySize parameter specifies the maximum size of all IRM logs in the connectivity log directory. When a directory reaches its maximum file size, the server deletes the oldest log files first. The default value is 250 MB.
 
@@ -1075,7 +1075,7 @@ Accept wildcard characters: False
 
 ### -IrmLogMaxFileSize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This IrmLogMaxFileSize parameter specifies the maximum size of each IRM log file. When a log file reaches its maximum file size, a new log file is created. The default value is 10 MB.
 
@@ -1105,7 +1105,7 @@ Accept wildcard characters: False
 
 ### -IrmLogPath
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IrmLogPath parameter specifies the default IRM log directory location. The default value is %ExchangeInstallPath%IRMLogs.
 
@@ -1125,7 +1125,7 @@ Accept wildcard characters: False
 
 ### -MaxConcurrentMailboxDeliveries
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MaxConcurrentMailboxDeliveries parameter specifies the maximum number of delivery threads that the transport service can have open at the same time to deliver messages to mailboxes. The default value is 20. The valid input range for this parameter is from 1 through 256. We recommend that you don't modify the default value unless Microsoft Customer Service and Support advises you to do this.
 
@@ -1143,7 +1143,7 @@ Accept wildcard characters: False
 
 ### -MaxConcurrentMailboxSubmissions
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MaxConcurrentMailboxSubmissions parameter specifies the maximum number of submission threads that the transport service can have open at the same time to send messages from mailboxes. The default value is 20. The valid input range for this parameter is from 1 through 256.
 
@@ -1161,7 +1161,7 @@ Accept wildcard characters: False
 
 ### -MaxConnectionRatePerMinute
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MaxConnectionRatePerMinute parameter specifies the maximum rate that connections are allowed to be opened with the transport service. If many connections are attempted with the transport service at the same time, the MaxConnectionRatePerMinute parameter limits the rate that the connections are opened so that the server's resources aren't overwhelmed. The default value is 1200 connections per minute. The valid input range for this parameter is from 1 through 2147483647.
 
@@ -1179,7 +1179,7 @@ Accept wildcard characters: False
 
 ### -MaxOutboundConnections
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MaxOutboundConnections parameter specifies the maximum number of outbound connections that can be open at a time. The default value is 1000. The valid input range for this parameter is from 1 through 2147483647. If you enter a value of unlimited, no limit is imposed on the number of outbound connections. The value of the MaxOutboundConnections parameter must be greater than or equal to the value of the MaxPerDomainOutboundConnections parameter.
 
@@ -1197,7 +1197,7 @@ Accept wildcard characters: False
 
 ### -MaxPerDomainOutboundConnections
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MaxPerDomainOutboundConnections parameter specifies the maximum number of concurrent connections to any single domain. The default value is 40. The valid input range for this parameter is from 1 through 2147483647. If you enter a value of unlimited, no limit is imposed on the number of outbound connections per domain. The value of the MaxPerDomainOutboundConnections parameter must be less than or equal to the value of the MaxOutboundConnections parameter.
 
@@ -1215,7 +1215,7 @@ Accept wildcard characters: False
 
 ### -MessageExpirationTimeout
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MessageExpirationTimeout parameter specifies the maximum time that a particular message can remain in a queue. If a message remains in the queue for longer than this period of time, the message is returned to the sender as a permanent failure. The default value is 2 days.
 
@@ -1237,7 +1237,7 @@ Accept wildcard characters: False
 
 ### -MessageRetryInterval
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MessageRetryInterval parameter specifies the retry interval for individual messages after a connection failure with a remote server. The default value is 5 minutes.
 
@@ -1259,7 +1259,7 @@ Accept wildcard characters: False
 
 ### -MessageTrackingLogEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MessageTrackingLogEnabled parameter specifies whether message tracking is enabled. The default value is $true.
 
@@ -1277,7 +1277,7 @@ Accept wildcard characters: False
 
 ### -MessageTrackingLogMaxAge
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MessageTrackingLogMaxAge parameter specifies the message tracking log maximum file age. Log files older than the specified value are deleted. The default value is 30 days.
 
@@ -1299,7 +1299,7 @@ Accept wildcard characters: False
 
 ### -MessageTrackingLogMaxDirectorySize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MessageTrackingLogMaxDirectorySize parameter specifies the maximum size of the message tracking log directory. When the maximum directory size is reached, the server deletes the oldest log files first.
 
@@ -1335,7 +1335,7 @@ Accept wildcard characters: False
 
 ### -MessageTrackingLogMaxFileSize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MessageTrackingLogMaxFileSize parameter specifies the maximum size of the message tracking log files. When a log file reaches its maximum file size, a new log file is created. The default value is 10 MB.
 
@@ -1364,7 +1364,7 @@ Accept wildcard characters: False
 
 ### -MessageTrackingLogPath
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MessageTrackingLogPath parameter specifies the location of the message tracking logs. The default location is %ExchangeInstallPath%TransportRoles\\Logs\\MessageTracking. Setting the value of this parameter to $null disables message tracking. However, setting this parameter to $null when the value of the MessageTrackingLogEnabled attribute is $true generates event log errors. The preferred method to disable message tracking is to use the MessageTrackingLogEnabled parameter.
 
@@ -1382,7 +1382,7 @@ Accept wildcard characters: False
 
 ### -MessageTrackingLogSubjectLoggingEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MessageTrackingLogSubjectLoggingEnabled parameter specifies whether the message subject should be included in the message tracking log. The default value is $true.
 
@@ -1400,7 +1400,7 @@ Accept wildcard characters: False
 
 ### -OutboundConnectionFailureRetryInterval
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The OutboundConnectionFailureRetryInterval parameter specifies the retry interval for subsequent connection attempts to a remote server where previous connection attempts have failed. The previously failed connection attempts are controlled by the TransientFailureRetryCount and TransientFailureRetryInterval parameters. For the Transport service on a Mailbox server, the default value of the OutboundConnectionFailureRetryInterval parameter is 10 minutes. On an Edge Transport server, the default value is 30 minutes.
 
@@ -1422,7 +1422,7 @@ Accept wildcard characters: False
 
 ### -PickupDirectoryMaxHeaderSize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PickupDirectoryMaxHeaderSize parameter specifies the maximum message header size that can be submitted to the Pickup directory. The default value is 64 KB.
 
@@ -1451,7 +1451,7 @@ Accept wildcard characters: False
 
 ### -PickupDirectoryMaxMessagesPerMinute
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PickupDirectoryMaxMessagesPerMinute parameter specifies the maximum number of messages processed per minute by the Pickup directory and by the Replay directory. Each directory can independently process message files at the rate specified by the PickupDirectoryMaxMessagesPerMinute parameter. The default value is 100. The valid input range for this parameter is from 1 through 20000.
 
@@ -1469,7 +1469,7 @@ Accept wildcard characters: False
 
 ### -PickupDirectoryMaxRecipientsPerMessage
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PickupDirectoryMaxRecipientsPerMessage parameter specifies the maximum number of recipients that can be included on an email message. The default value is 100. The valid input range for this parameter is from 1 through 10000.
 
@@ -1487,7 +1487,7 @@ Accept wildcard characters: False
 
 ### -PickupDirectoryPath
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PickupDirectoryPath parameter specifies the location of the Pickup directory. The Pickup directory is used by administrators and non-Microsoft applications to create and submit messages. The default location is %ExchangeInstallPath%TransportRoles\\Pickup. If the value of the PickupDirectoryPath parameter is set to $null, the Pickup directory is disabled.
 
@@ -1505,7 +1505,7 @@ Accept wildcard characters: False
 
 ### -PipelineTracingEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PipelineTracingEnabled parameter specifies whether to enable pipeline tracing. Pipeline tracing captures message snapshot files that record the changes made to the message by each transport agent configured in the transport service on the server. Pipeline tracing creates verbose log files that accumulate quickly. Pipeline tracing should only be enabled for a short time to provide in-depth diagnostic information that enables you to troubleshoot problems. In addition to troubleshooting, you can use pipeline tracing to validate changes that you make to the configuration of the transport service where you enable pipeline tracing. The default value is $false.
 
@@ -1523,7 +1523,7 @@ Accept wildcard characters: False
 
 ### -PipelineTracingPath
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PipelineTracingPath parameter specifies the location of the pipeline tracing logs. The default location is %ExchangeInstallPath%TransportRoles\\Logs\\Hub\\PipelineTracing. The path must be local to the Exchange server.
 
@@ -1549,7 +1549,7 @@ Accept wildcard characters: False
 
 ### -PipelineTracingSenderAddress
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PipelineTracingSenderAddress parameter specifies the sender email address that invokes pipeline tracing. Only messages from this address generate pipeline tracing output. The address can be either inside or outside the Exchange organization. Depending on your requirements, you might have to set this parameter to different sender addresses and send new messages to start the transport agents or routes that you want to test. The default value of this parameter is $null.
 
@@ -1567,7 +1567,7 @@ Accept wildcard characters: False
 
 ### -PoisonMessageDetectionEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PoisonMessageDetectionEnabled parameter specifies whether poison messages should be detected. The default value is $true. Poison messages are messages determined to be potentially harmful to the Exchange system after a server failure. Poison messages are put in the poison message queue. We recommend that you don't modify the default value unless Customer Service and Support advises you to do this.
 
@@ -1585,7 +1585,7 @@ Accept wildcard characters: False
 
 ### -PoisonThreshold
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PoisonThreshold parameter specifies the number of times a message can be rejected before it's classified as a poison message. The default value is 2. We recommend that you don't modify the default value unless Customer Service and Support advises you to do this. The valid input range for this parameter is from 1 through 10.
 
@@ -1603,7 +1603,7 @@ Accept wildcard characters: False
 
 ### -QueueLogMaxAge
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The QueueLogMaxAge parameter specifies the maximum age of the queue log files. Log files that are older than the specified value are deleted. The default value is 7 days.
 
@@ -1625,7 +1625,7 @@ Accept wildcard characters: False
 
 ### -QueueLogMaxDirectorySize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The QueueLogMaxDirectorySize parameter specifies the maximum size of the queue log directory. When the maximum directory size is reached, the server deletes the oldest log files first. The default value is 200 MB.
 
@@ -1655,7 +1655,7 @@ Accept wildcard characters: False
 
 ### -QueueLogMaxFileSize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The QueueLogMaxFileSize parameter specifies the maximum size of the queue log files. When a log file reaches its maximum file size, a new log file is created. The default value is 10 MB.
 
@@ -1685,7 +1685,7 @@ Accept wildcard characters: False
 
 ### -QueueLogPath
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The QueueLogPath parameter specifies the path of the queue log directory. The default location is %ExchangeInstallPath%TransportRoles\\Logs\\Hub\\QueueViewer. Setting the value of this parameter to $null disables queue logging.
 
@@ -1703,7 +1703,7 @@ Accept wildcard characters: False
 
 ### -QueueMaxIdleTime
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The QueueMaxIdleTime parameter specifies the period of time an empty delivery queue can exist before the queue is removed. The default value is 3 minutes.
 
@@ -1725,7 +1725,7 @@ Accept wildcard characters: False
 
 ### -ReceiveProtocolLogMaxAge
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ReceiveProtocolLogMaxAge parameter specifies the maximum age of a protocol log file that's shared by all Receive connectors in the Transport service on the server. Log files that are older than the specified value are automatically deleted.
 
@@ -1749,7 +1749,7 @@ Accept wildcard characters: False
 
 ### -ReceiveProtocolLogMaxDirectorySize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ReceiveProtocolLogMaxDirectorySize parameter specifies the maximum size of the protocol log directory that's shared by all Receive connectors in the Transport service on the server. When the maximum directory size is reached, the server deletes the oldest log files first.
 
@@ -1783,7 +1783,7 @@ Accept wildcard characters: False
 
 ### -ReceiveProtocolLogMaxFileSize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ReceiveProtocolLogMaxFileSize parameter specifies the maximum size of a protocol log file that's shared by all Receive connectors in the Transport on the server. When a log file reaches its maximum file size, a new log file is created.
 
@@ -1817,7 +1817,7 @@ Accept wildcard characters: False
 
 ### -ReceiveProtocolLogPath
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ReceiveProtocolLogPath parameter specifies the location of the protocol log directory for all Receive connectors in the Transport service on the server. The default location is %ExchangeInstallPath%TransportRoles\\Logs\\Hub\\ProtocolLog\\SmtpReceive.
 
@@ -1837,7 +1837,7 @@ Accept wildcard characters: False
 
 ### -RecipientValidationCacheEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RecipientValidationCacheEnabled parameter specifies whether the recipient addresses used by transport agents, such as the Recipient Filtering agent, are cached. The default value is $true on Edge Transport servers and $false for the Transport service on Mailbox servers.
 
@@ -1855,7 +1855,7 @@ Accept wildcard characters: False
 
 ### -ReplayDirectoryPath
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ReplayDirectoryPath parameter specifies the path of the Replay directory. The Replay directory is used to resubmit exported messages and to receive messages from foreign gateway servers. The default location is %ExchangeInstallPath%TransportRoles\\Replay. If the value of the ReplayDirectoryPath parameter is set to $null, the Replay directory is disabled.
 
@@ -1873,7 +1873,7 @@ Accept wildcard characters: False
 
 ### -RequestBrokerLogEnabled
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -1891,7 +1891,7 @@ Accept wildcard characters: False
 
 ### -RequestBrokerLogMaxAge
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -1909,7 +1909,7 @@ Accept wildcard characters: False
 
 ### -RequestBrokerLogMaxDirectorySize
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -1927,7 +1927,7 @@ Accept wildcard characters: False
 
 ### -RequestBrokerLogMaxFileSize
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -1945,7 +1945,7 @@ Accept wildcard characters: False
 
 ### -RequestBrokerLogPath
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -1963,7 +1963,7 @@ Accept wildcard characters: False
 
 ### -ResourceLogEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -1981,7 +1981,7 @@ Accept wildcard characters: False
 
 ### -ResourceLogMaxAge
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -1999,7 +1999,7 @@ Accept wildcard characters: False
 
 ### -ResourceLogMaxDirectorySize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -2017,7 +2017,7 @@ Accept wildcard characters: False
 
 ### -ResourceLogMaxFileSize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -2035,7 +2035,7 @@ Accept wildcard characters: False
 
 ### -ResourceLogPath
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -2053,7 +2053,7 @@ Accept wildcard characters: False
 
 ### -RootDropDirectoryPath
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RootDropDirectoryPath parameter specifies the top-level location of the Drop directory used by all Foreign connectors defined in the Transport service on a Mailbox server. The value of the RootDropDirectoryPath parameter might be a local path, or a Universal Naming Convention (UNC) path to a remote server. By default, the RootDropDirectoryPath parameter is blank. This indicates the value of RootDropDirectoryPath is the Exchange installation folder. The RootDropDirectoryPath parameter is used with the DropDirectory parameter in the Set-ForeignConnector cmdlet to specify the location for outgoing messages going to the address spaces defined on the Foreign connector.
 
@@ -2071,7 +2071,7 @@ Accept wildcard characters: False
 
 ### -RoutingTableLogMaxAge
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RoutingTableLogMaxAge parameter specifies the maximum routing table log age. Log files older than the specified value are deleted. The default value is 7 days.
 
@@ -2093,7 +2093,7 @@ Accept wildcard characters: False
 
 ### -RoutingTableLogMaxDirectorySize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RoutingTableLogMaxDirectorySize parameter specifies the maximum size of the routing table log directory. When the maximum directory size is reached, the server deletes the oldest log files first. The default value is 50 MB.
 
@@ -2123,7 +2123,7 @@ Accept wildcard characters: False
 
 ### -RoutingTableLogPath
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RoutingTableLogPath parameter specifies the directory location where routing table log files should be stored. The default location is %ExchangeInstallPath%TransportRoles\\Logs\\Hub\\Routing. Setting the value of the RoutingTableLogPath parameter to $null disables routing table logging.
 
@@ -2141,7 +2141,7 @@ Accept wildcard characters: False
 
 ### -SendProtocolLogMaxAge
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SendProtocolLogMaxAge parameter specifies the maximum age of a protocol log file that's shared by all Send connectors in the Transport service that have this server configured as a source server. Log files that are older than the specified value are automatically deleted.
 
@@ -2165,7 +2165,7 @@ Accept wildcard characters: False
 
 ### -SendProtocolLogMaxDirectorySize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SendProtocolLogMaxDirectorySize parameter specifies the maximum size of the protocol log directory that's shared by all Send connectors in the Transport service that have this server configured as a source server. When the maximum directory size is reached, the server deletes the oldest log files first.
 
@@ -2199,7 +2199,7 @@ Accept wildcard characters: False
 
 ### -SendProtocolLogMaxFileSize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SendProtocolLogMaxFileSize parameter specifies the maximum size of a protocol log file that's shared by all Send connectors in the Transport service that have this server configured as a source server. When a log file reaches its maximum file size, a new log file is created.
 
@@ -2233,7 +2233,7 @@ Accept wildcard characters: False
 
 ### -SendProtocolLogPath
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SendProtocolLogPath parameter specifies the location of the protocol log directory for all Send connectors in the Transport service on the server. The default location is %ExchangeInstallPath%TransportRoles\\Logs\\Hub\\ProtocolLog\\SmtpSend.
 
@@ -2256,7 +2256,7 @@ Accept wildcard characters: False
 
 ### -ServerStatisticsLogMaxAge
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is functional only in Exchange Server 2013 CU6 or earlier.
 
@@ -2280,7 +2280,7 @@ Accept wildcard characters: False
 
 ### -ServerStatisticsLogMaxDirectorySize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is functional only in Exchange Server 2013 CU6 or earlier.
 
@@ -2312,7 +2312,7 @@ Accept wildcard characters: False
 
 ### -ServerStatisticsLogMaxFileSize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is functional only in Exchange Server 2013 CU6 or earlier.
 
@@ -2344,7 +2344,7 @@ Accept wildcard characters: False
 
 ### -ServerStatisticsLogPath
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is functional only in Exchange Server 2013 CU6 or earlier.
 
@@ -2364,7 +2364,7 @@ Accept wildcard characters: False
 
 ### -TransientFailureRetryCount
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TransientFailureRetryCount parameter specifies the maximum number of immediate connection retries attempted when the server encounters a connection failure with a remote server. The default value is 6. The valid input range for this parameter is from 0 through 15. When the value of this parameter is set to 0, the server doesn't immediately attempt to retry an unsuccessful connection, and the next connection attempt is controlled by the OutboundConnectionFailureRetryInterval parameter.
 
@@ -2382,7 +2382,7 @@ Accept wildcard characters: False
 
 ### -TransientFailureRetryInterval
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TransientFailureRetryInterval parameter controls the connection interval between each connection attempt specified by the TransientFailureRetryCount parameter. For the Transport service on a Mailbox server, the default value of the TransientFailureRetryInterval parameter is 5 minutes. On an Edge Transport server, the default value is 10 minutes.
 
@@ -2404,7 +2404,7 @@ Accept wildcard characters: False
 
 ### -TransportHttpLogEnabled
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -2422,7 +2422,7 @@ Accept wildcard characters: False
 
 ### -TransportHttpLogMaxAge
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -2440,7 +2440,7 @@ Accept wildcard characters: False
 
 ### -TransportHttpLogMaxDirectorySize
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -2458,7 +2458,7 @@ Accept wildcard characters: False
 
 ### -TransportHttpLogMaxFileSize
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -2476,7 +2476,7 @@ Accept wildcard characters: False
 
 ### -TransportHttpLogPath
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -2494,7 +2494,7 @@ Accept wildcard characters: False
 
 ### -TransportMaintenanceLogEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -2512,7 +2512,7 @@ Accept wildcard characters: False
 
 ### -TransportMaintenanceLogMaxAge
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -2530,7 +2530,7 @@ Accept wildcard characters: False
 
 ### -TransportMaintenanceLogMaxDirectorySize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -2548,7 +2548,7 @@ Accept wildcard characters: False
 
 ### -TransportMaintenanceLogMaxFileSize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -2566,7 +2566,7 @@ Accept wildcard characters: False
 
 ### -TransportMaintenanceLogPath
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -2584,7 +2584,7 @@ Accept wildcard characters: False
 
 ### -TransportSyncAccountsPoisonAccountThreshold
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -2602,7 +2602,7 @@ Accept wildcard characters: False
 
 ### -TransportSyncAccountsPoisonDetectionEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -2620,7 +2620,7 @@ Accept wildcard characters: False
 
 ### -TransportSyncAccountsPoisonItemThreshold
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -2638,7 +2638,7 @@ Accept wildcard characters: False
 
 ### -TransportSyncAccountsSuccessivePoisonItemThreshold
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -2656,7 +2656,7 @@ Accept wildcard characters: False
 
 ### -TransportSyncEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -2674,7 +2674,7 @@ Accept wildcard characters: False
 
 ### -TransportSyncExchangeEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -2692,7 +2692,7 @@ Accept wildcard characters: False
 
 ### -TransportSyncHubHealthLogEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -2710,7 +2710,7 @@ Accept wildcard characters: False
 
 ### -TransportSyncHubHealthLogFilePath
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -2728,7 +2728,7 @@ Accept wildcard characters: False
 
 ### -TransportSyncHubHealthLogMaxAge
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -2746,7 +2746,7 @@ Accept wildcard characters: False
 
 ### -TransportSyncHubHealthLogMaxDirectorySize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -2764,7 +2764,7 @@ Accept wildcard characters: False
 
 ### -TransportSyncHubHealthLogMaxFileSize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -2782,7 +2782,7 @@ Accept wildcard characters: False
 
 ### -TransportSyncImapEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -2800,7 +2800,7 @@ Accept wildcard characters: False
 
 ### -TransportSyncLogEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -2818,7 +2818,7 @@ Accept wildcard characters: False
 
 ### -TransportSyncLogFilePath
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -2836,7 +2836,7 @@ Accept wildcard characters: False
 
 ### -TransportSyncLogLoggingLevel
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -2854,7 +2854,7 @@ Accept wildcard characters: False
 
 ### -TransportSyncLogMaxAge
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -2872,7 +2872,7 @@ Accept wildcard characters: False
 
 ### -TransportSyncLogMaxDirectorySize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -2890,7 +2890,7 @@ Accept wildcard characters: False
 
 ### -TransportSyncLogMaxFileSize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -2908,7 +2908,7 @@ Accept wildcard characters: False
 
 ### -TransportSyncMaxDownloadItemsPerConnection
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -2926,7 +2926,7 @@ Accept wildcard characters: False
 
 ### -TransportSyncMaxDownloadSizePerConnection
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -2944,7 +2944,7 @@ Accept wildcard characters: False
 
 ### -TransportSyncMaxDownloadSizePerItem
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -2962,7 +2962,7 @@ Accept wildcard characters: False
 
 ### -TransportSyncPopEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -2980,7 +2980,7 @@ Accept wildcard characters: False
 
 ### -TransportSyncRemoteConnectionTimeout
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -2998,7 +2998,7 @@ Accept wildcard characters: False
 
 ### -UseDowngradedExchangeServerAuth
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The UseDowngradedExchangeServerAuth parameter specifies whether the Generic Security Services application programming interface (GSSAPI) authentication method is used on connections where Transport Layer Security (TLS) is disabled.
 
@@ -3020,7 +3020,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
@@ -3038,7 +3038,7 @@ Accept wildcard characters: False
 
 ### -WindowsLiveHotmailTransportSyncEnabled
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -3056,7 +3056,7 @@ Accept wildcard characters: False
 
 ### -WlmLogMaxAge
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -3074,7 +3074,7 @@ Accept wildcard characters: False
 
 ### -WlmLogMaxDirectorySize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -3092,7 +3092,7 @@ Accept wildcard characters: False
 
 ### -WlmLogMaxFileSize
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -3110,7 +3110,7 @@ Accept wildcard characters: False
 
 ### -WlmLogPath
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-User.md b/exchange/exchange-ps/ExchangePowerShell/Set-User.md
index cbb748981c..262220b5ea 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-User.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-User.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -120,7 +120,7 @@ Performing this procedure on a linked mailbox removes all permissions on the mai
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the user that you want to modify. You can use any value that uniquely identifies the user. For example:
 
@@ -145,7 +145,7 @@ Accept wildcard characters: False
 
 ### -AllowUMCallsFromNonUsers
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -165,7 +165,7 @@ Accept wildcard characters: False
 
 ### -Arbitration
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -187,7 +187,7 @@ Accept wildcard characters: False
 
 ### -AssistantName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The AssistantName parameter specifies the name of the user's assistant.
 
@@ -205,7 +205,7 @@ Accept wildcard characters: False
 
 ### -AuthenticationPolicy
 
-> Applicable: Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The AuthenticationPolicy parameter specifies the authentication policy to apply to the user. You can use any value that uniquely identifies the policy. For example:
 
@@ -271,7 +271,7 @@ Accept wildcard characters: False
 
 ### -CertificateSubject
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -291,7 +291,7 @@ Accept wildcard characters: False
 
 ### -City
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The City parameter specifies the user's city.
 
@@ -329,7 +329,7 @@ Accept wildcard characters: False
 
 ### -Company
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Company parameter specifies the user's company.
 
@@ -347,7 +347,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -368,7 +368,7 @@ Accept wildcard characters: False
 
 ### -CountryOrRegion
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The CountryOrRegion parameter specifies the user's country or region. A valid value is a valid ISO 3166-1 two-letter country code (for example, AU for Australia) or the corresponding friendly name for the country (which might be different from the official ISO 3166 Maintenance Agency short name).
 
@@ -390,7 +390,7 @@ Accept wildcard characters: False
 
 ### -CreateDTMFMap
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -413,7 +413,7 @@ Accept wildcard characters: False
 
 ### -Department
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Department parameter specifies the user's department.
 
@@ -451,7 +451,7 @@ Accept wildcard characters: False
 
 ### -DisplayName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The DisplayName parameter specifies the display name of the user. The display name is visible in the Exchange admin center and in Active Directory. The maximum length is 256 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -469,7 +469,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -516,7 +516,7 @@ Accept wildcard characters: False
 
 ### -Fax
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Fax parameter specifies the user's fax number.
 
@@ -534,7 +534,7 @@ Accept wildcard characters: False
 
 ### -FirstName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The FirstName parameter specifies the user's first name.
 
@@ -574,7 +574,7 @@ Accept wildcard characters: False
 
 ### -GeoCoordinates
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The GeoCoordinates parameter specifies the user's location in latitude, longitude and (optionally) altitude coordinates. A valid value for this parameter uses one of the following formats:
 
@@ -597,7 +597,7 @@ Accept wildcard characters: False
 
 ### -HomePhone
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The HomePhone parameter specifies the user's home telephone number.
 
@@ -615,7 +615,7 @@ Accept wildcard characters: False
 
 ### -IgnoreDefaultScope
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -640,7 +640,7 @@ Accept wildcard characters: False
 
 ### -Initials
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Initials parameter specifies the user's middle initials.
 
@@ -678,7 +678,7 @@ Accept wildcard characters: False
 
 ### -LastName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The LastName parameter specifies the user's last name.
 
@@ -696,7 +696,7 @@ Accept wildcard characters: False
 
 ### -LinkedCredential
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -720,7 +720,7 @@ Accept wildcard characters: False
 
 ### -LinkedDomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -742,7 +742,7 @@ Accept wildcard characters: False
 
 ### -LinkedMasterAccount
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -835,7 +835,7 @@ Accept wildcard characters: False
 
 ### -Manager
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Manager parameter specifies the user's manager.
 
@@ -853,7 +853,7 @@ Accept wildcard characters: False
 
 ### -MobilePhone
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The MobilePhone parameter specifies the user's primary mobile phone number.
 
@@ -873,7 +873,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Name parameter specifies the unique name of the user. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -891,7 +891,7 @@ Accept wildcard characters: False
 
 ### -Notes
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Notes parameters specifies additional information about the object. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -909,7 +909,7 @@ Accept wildcard characters: False
 
 ### -Office
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Office parameter specifies the user's physical office name or number.
 
@@ -927,7 +927,7 @@ Accept wildcard characters: False
 
 ### -OtherFax
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The OtherFax parameter specifies the user's alternative fax number.
 
@@ -945,7 +945,7 @@ Accept wildcard characters: False
 
 ### -OtherHomePhone
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The OtherHomePhone parameter specifies the user's alternative home telephone number.
 
@@ -963,7 +963,7 @@ Accept wildcard characters: False
 
 ### -OtherTelephone
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The OtherTelephone parameter specifies the user's alternative telephone number.
 
@@ -981,7 +981,7 @@ Accept wildcard characters: False
 
 ### -Pager
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Pager parameter specifies the user's pager number.
 
@@ -999,7 +999,7 @@ Accept wildcard characters: False
 
 ### -PermanentlyClearPreviousMailboxInfo
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is functional only in the cloud-based service.
 
@@ -1023,7 +1023,7 @@ Accept wildcard characters: False
 
 ### -Phone
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Phone parameter specifies the user's office telephone number.
 
@@ -1043,7 +1043,7 @@ Accept wildcard characters: False
 
 ### -PhoneticDisplayName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The PhoneticDisplayName parameter specifies an alternate spelling of the user's name that's used for text to speech in Unified Messaging (UM) environments. Typically, you use this parameter when the pronunciation and spelling of the user's name don't match. The maximum length is 256 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -1061,7 +1061,7 @@ Accept wildcard characters: False
 
 ### -PostalCode
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The PostalCode parameter specifies the user's zip code or postal code.
 
@@ -1079,7 +1079,7 @@ Accept wildcard characters: False
 
 ### -PostOfficeBox
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The PostOfficeBox parameter specifies the user's post office box number.
 
@@ -1097,7 +1097,7 @@ Accept wildcard characters: False
 
 ### -PublicFolder
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The PublicFolder switch is required to modify public folder mailboxes. You don't need to specify a value with this switch.
 
@@ -1117,7 +1117,7 @@ Accept wildcard characters: False
 
 ### -RemotePowerShellEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 **Note**: In cloud-based environments, this parameter is being deprecated, so use the EXOModuleEnabled parameter instead.
 
@@ -1166,7 +1166,7 @@ Accept wildcard characters: False
 
 ### -ResetPasswordOnNextLogon
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The ResetPasswordOnNextLogon parameter specifies whether the user must change their password the next time they log on. Valid values are:
 
@@ -1187,7 +1187,7 @@ Accept wildcard characters: False
 
 ### -SamAccountName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1207,7 +1207,7 @@ Accept wildcard characters: False
 
 ### -SeniorityIndex
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The SeniorityIndex parameter specifies the order in which this user is displayed in a hierarchical address book. A user with a value of 2 is displayed higher in an address book than a user with a value of 1.
 
@@ -1225,7 +1225,7 @@ Accept wildcard characters: False
 
 ### -SimpleDisplayName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The SimpleDisplayName parameter is used to display an alternative description of the object when only a limited set of characters is permitted. Valid characters are:
 
@@ -1249,7 +1249,7 @@ Accept wildcard characters: False
 
 ### -SkipDualWrite
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1269,7 +1269,7 @@ Accept wildcard characters: False
 
 ### -StateOrProvince
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The StateOrProvince parameter specifies the user's state or province.
 
@@ -1287,7 +1287,7 @@ Accept wildcard characters: False
 
 ### -StreetAddress
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The StreetAddress parameter specifies the user's physical address.
 
@@ -1327,7 +1327,7 @@ Accept wildcard characters: False
 
 ### -TelephoneAssistant
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1347,7 +1347,7 @@ Accept wildcard characters: False
 
 ### -Title
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Title parameter specifies the user's title.
 
@@ -1365,7 +1365,7 @@ Accept wildcard characters: False
 
 ### -UMCallingLineIds
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1385,7 +1385,7 @@ Accept wildcard characters: False
 
 ### -UMDtmfMap
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1417,7 +1417,7 @@ Accept wildcard characters: False
 
 ### -UserPrincipalName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -1462,7 +1462,7 @@ Accept wildcard characters: False
 
 ### -WebPage
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WebPage parameter specifies the user's Web page.
 
@@ -1480,7 +1480,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch doesn't work on this cmdlet.
 
@@ -1498,7 +1498,7 @@ Accept wildcard characters: False
 
 ### -WindowsEmailAddress
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WindowsEmailAddress parameter specifies the Windows email address for this recipient. This is a common Active Directory attribute that's present in all environments, including environments without Exchange. Using the WindowsEmailAddress parameter on a recipient has one of the following results:
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-UserPhoto.md b/exchange/exchange-ps/ExchangePowerShell/Set-UserPhoto.md
index 52522938ff..b9c4c20062 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-UserPhoto.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-UserPhoto.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -131,7 +131,7 @@ This example deletes the preview photo that was uploaded in the previous example
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the identity of the user. You can use any value that uniquely identifies the user. For example:
 
@@ -160,7 +160,7 @@ Accept wildcard characters: False
 
 ### -Cancel
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Cancel switch deletes the current preview photo. You don't need to specify a value with this switch.
 
@@ -180,7 +180,7 @@ Accept wildcard characters: False
 
 ### -PictureData
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PictureData parameter specifies the photo file to upload to the user's account.
 
@@ -200,7 +200,7 @@ Accept wildcard characters: False
 
 ### -PictureStream
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PictureStream parameter specifies the photo to upload to the user's account. This parameter is used by client applications such as Outlook on the web when users add a photo. To upload a photo using PowerShell, use the PictureData parameter to specify the photo file.
 
@@ -218,7 +218,7 @@ Accept wildcard characters: False
 
 ### -Preview
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Preview switch uploads a preview photo for the user account. You don't need to specify a value with this switch.
 
@@ -238,7 +238,7 @@ Accept wildcard characters: False
 
 ### -Save
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Save switch specifies the uploaded photo is saved as the user's photo. You don't need to specify a value with this switch.
 
@@ -256,7 +256,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -279,7 +279,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -297,7 +297,7 @@ Accept wildcard characters: False
 
 ### -GroupMailbox
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The GroupMailbox switch is required to modify Microsoft 365 Groups. You don't need to specify a value with this switch.
 
@@ -315,7 +315,7 @@ Accept wildcard characters: False
 
 ### -IgnoreDefaultScope
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IgnoreDefaultScope switch tells the command to ignore the default recipient scope setting for the Exchange PowerShell session, and to use the entire forest as the scope. You don't need to specify a value with this switch.
 
@@ -338,7 +338,7 @@ Accept wildcard characters: False
 
 ### -PhotoType
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -356,7 +356,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-WebServicesVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Set-WebServicesVirtualDirectory.md
index f96a79084a..af15a221bb 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-WebServicesVirtualDirectory.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-WebServicesVirtualDirectory.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -75,7 +75,7 @@ This example enables MRSProxy on the EWS default website. MRSProxy is the servic
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the EWS virtual directory that you want to modify. You can use any value that uniquely identifies the virtual directory. For example:
 
@@ -99,7 +99,7 @@ Accept wildcard characters: False
 
 ### -BasicAuthentication
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The BasicAuthentication parameter specifies whether Basic authentication is enabled on the virtual directory. Valid values are:
 
@@ -120,7 +120,7 @@ Accept wildcard characters: False
 
 ### -CertificateAuthentication
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The CertificateAuthentication parameter specifies whether certificate authentication is enabled. This parameter affects the `<Servername>/ews/management/` virtual directory. It doesn't affect the `<Servername>/ews/` virtual directory.
 
@@ -138,7 +138,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -159,7 +159,7 @@ Accept wildcard characters: False
 
 ### -DigestAuthentication
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DigestAuthentication parameter specifies whether Digest authentication is enabled on the virtual directory. Valid values are:
 
@@ -180,7 +180,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -198,7 +198,7 @@ Accept wildcard characters: False
 
 ### -ExtendedProtectionFlags
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExtendedProtectionFlags parameter specifies custom settings for Extended Protection for Authentication on the virtual directory. Valid values are:
 
@@ -222,7 +222,7 @@ Accept wildcard characters: False
 
 ### -ExtendedProtectionSPNList
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExtendedProtectionSPNList parameter specifies a list of valid Service Principal Names (SPNs) if you're using Extended Protection for Authentication on the virtual directory. Valid values are:
 
@@ -243,7 +243,7 @@ Accept wildcard characters: False
 
 ### -ExtendedProtectionTokenChecking
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExtendedProtectionTokenChecking parameter defines how you want to use Extended Protection for Authentication on the virtual directory. Extended Protection for Authentication isn't enabled by default. Valid values are:
 
@@ -267,7 +267,7 @@ Accept wildcard characters: False
 
 ### -ExternalUrl
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExternalURL parameter specifies the URL that's used to connect to the virtual directory from outside the firewall.
 
@@ -287,7 +287,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -307,7 +307,7 @@ Accept wildcard characters: False
 
 ### -GzipLevel
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The GzipLevel parameter sets the Gzip configuration for the Exchange Web Services virtual directory. Valid values are:
 
@@ -330,7 +330,7 @@ Accept wildcard characters: False
 
 ### -InternalNLBBypassUrl
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 **Note:** This parameter applies only to Exchange 2010. By default, Exchange 2013 or later already has the InternalNLBBypassUrl value configured on the backend Exchange Web Services (EWS) virtual directory on Mailbox servers.
 
@@ -352,7 +352,7 @@ Accept wildcard characters: False
 
 ### -InternalUrl
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The InternalURL parameter specifies the URL that's used to connect to the virtual directory from inside the firewall.
 
@@ -372,7 +372,7 @@ Accept wildcard characters: False
 
 ### -MRSProxyEnabled
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MRSProxyEnabled parameter specifies whether to enable MRSProxy for the Exchange Web Services virtual directory on Exchange servers that have the Client Access server role installed. MRSProxy helps to proxy mailbox moves between Active Directory forests. The default value is $false.
 
@@ -410,7 +410,7 @@ Accept wildcard characters: False
 
 ### -OAuthAuthentication
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The OAuthAuthentication parameter specifies whether OAuth authentication is enabled on the virtual directory. Valid values are:
 
@@ -431,7 +431,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
@@ -449,7 +449,7 @@ Accept wildcard characters: False
 
 ### -WindowsAuthentication
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WindowsAuthentication parameter specifies whether Integrated Windows authentication is enabled on the virtual directory. Valid values are:
 
@@ -470,7 +470,7 @@ Accept wildcard characters: False
 
 ### -WSSecurityAuthentication
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WSSecurityAuthentication parameter specifies whether WS-Security (Web Services Security) authentication is enabled on the virtual directory. Valid values are:
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-X400AuthoritativeDomain.md b/exchange/exchange-ps/ExchangePowerShell/Set-X400AuthoritativeDomain.md
index 1cd18367dd..3091a8391f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-X400AuthoritativeDomain.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-X400AuthoritativeDomain.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -85,7 +85,7 @@ This example makes the following changes to an existing X.400 authoritative doma
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the X.400 authoritative domain that you want to modify. You can use any value that uniquely identifies the domain. For example:
 
@@ -107,7 +107,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -128,7 +128,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -148,7 +148,7 @@ Accept wildcard characters: False
 
 ### -Name
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Name parameter specifies the unique name for the X.400 authoritative domain. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks (").
 
@@ -166,7 +166,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
@@ -184,7 +184,7 @@ Accept wildcard characters: False
 
 ### -X400DomainName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The X400DomainName parameter specifies the X.400 namespace that can only include the X.400 organizational components. Specifically, only the following attribute types are supported:
 
@@ -213,7 +213,7 @@ Accept wildcard characters: False
 
 ### -X400ExternalRelay
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The X400ExternalRelay parameter specifies whether this authoritative domain is an external relay domain. If you set the X400ExternalRelay parameter to $true, Exchange routes to the external address and doesn't treat resolution failures to this subdomain as errors.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Start-ComplianceSearch.md b/exchange/exchange-ps/ExchangePowerShell/Start-ComplianceSearch.md
index 2d08dc0fc9..69a49182af 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Start-ComplianceSearch.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Start-ComplianceSearch.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 author: chrisda
 external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
 Locale: en-US
@@ -50,7 +50,7 @@ This example starts the compliance search named Case 1234
 
 ### -Identity
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The Identity parameter specifies the compliance search that you want to start.
 
@@ -75,7 +75,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -96,7 +96,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -116,7 +116,7 @@ Accept wildcard characters: False
 
 ### -RetryOnError
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The RetryOnError switch specifies whether to retry the search on any items that failed without re-running the entire search all over again. You don't need to specify a value with this switch.
 
@@ -134,7 +134,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The WhatIf parameter doesn't work in the Microsoft Purview compliance portal.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Start-DatabaseAvailabilityGroup.md b/exchange/exchange-ps/ExchangePowerShell/Start-DatabaseAvailabilityGroup.md
index d2675e5692..fedd062276 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Start-DatabaseAvailabilityGroup.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Start-DatabaseAvailabilityGroup.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -66,7 +66,7 @@ This example starts the members of the DAG DAG1 in the Active Directory site Red
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the name of the DAG being started.
 
@@ -84,7 +84,7 @@ Accept wildcard characters: False
 
 ### -ActiveDirectorySite
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ActiveDirectorySite parameter specifies whether to start all DAG members in the specified site.
 
@@ -102,7 +102,7 @@ Accept wildcard characters: False
 
 ### -MailboxServer
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MailboxServer parameter specifies whether to start a single DAG member.
 
@@ -120,7 +120,7 @@ Accept wildcard characters: False
 
 ### -ConfigurationOnly
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ConfigurationOnly switch specifies whether to update the Active Directory properties with the start action, but doesn't perform a start of the DAG or any members. You don't need to specify a value with this switch.
 
@@ -138,7 +138,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -159,7 +159,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -177,7 +177,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Start-EdgeSynchronization.md b/exchange/exchange-ps/ExchangePowerShell/Start-EdgeSynchronization.md
index f3be145a64..942cf46484 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Start-EdgeSynchronization.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Start-EdgeSynchronization.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -49,7 +49,7 @@ This example starts edge synchronization on the Mailbox server named Mailbox01.
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -70,7 +70,7 @@ Accept wildcard characters: False
 
 ### -ForceFullSync
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ForceFullSync switch specifies whether to initiate a full edge synchronization. You don't need to specify a value with this switch.
 
@@ -90,7 +90,7 @@ Accept wildcard characters: False
 
 ### -ForceUpdateCookie
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ForceUpdateCookie switch specifies whether to force the Microsoft Exchange EdgeSync service to update the replication cookie even if it encounters an error. You don't need to specify a value with this switch.
 
@@ -110,7 +110,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
 
@@ -135,7 +135,7 @@ Accept wildcard characters: False
 
 ### -TargetServer
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TargetServer parameter specifies an Edge Transport server to initiate edge synchronization with. If omitted, all Edge Transport servers are synchronized.
 
@@ -155,7 +155,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Start-MailboxAssistant.md b/exchange/exchange-ps/ExchangePowerShell/Start-MailboxAssistant.md
index cb4f85e871..1af287cc35 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Start-MailboxAssistant.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Start-MailboxAssistant.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2019
+applicable: Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -48,7 +48,7 @@ This example starts the `BigFunnelRetryFeederTimeBasedAssistant` assistant and l
 
 ### -Identity
 
-> Applicable: Exchange Server 2019
+> Applicable: Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the user whose mailbox should be processed by the Mailbox Assistant. Valid values are:
 
@@ -70,7 +70,7 @@ Accept wildcard characters: False
 
 ### -AssistantName
 
-> Applicable: Exchange Server 2019
+> Applicable: Exchange Server 2019, Exchange Server SE
 
 The AssistantName parameter specifies the assistant that should process the mailbox. Valid values are:
 
@@ -92,7 +92,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2019
+> Applicable: Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -113,7 +113,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2019
+> Applicable: Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -131,7 +131,7 @@ Accept wildcard characters: False
 
 ### -Parameters
 
-> Applicable: Exchange Server 2019
+> Applicable: Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -149,7 +149,7 @@ Accept wildcard characters: False
 
 ### -SoftDeletedMailbox
 
-> Applicable: Exchange Server 2019
+> Applicable: Exchange Server 2019, Exchange Server SE
 
 The SoftDeletedMailbox switch specifies that the mailbox to be processed by the assistant is a soft-deleted mailbox.
 
@@ -169,7 +169,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2019
+> Applicable: Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Start-MailboxSearch.md b/exchange/exchange-ps/ExchangePowerShell/Start-MailboxSearch.md
index a547ae884e..4da8c127b8 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Start-MailboxSearch.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Start-MailboxSearch.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
 Locale: en-US
@@ -58,7 +58,7 @@ This example starts the mailbox search ProjectContoso.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the name of the search. The name is referenced when starting, stopping, or removing the search.
 
@@ -76,7 +76,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -97,7 +97,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -117,7 +117,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -137,7 +137,7 @@ Accept wildcard characters: False
 
 ### -Resume
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Resume switch resumes a stopped, failed, or partially succeeded search from the point it stopped. You don't need to specify a value with this switch.
 
@@ -157,7 +157,7 @@ Accept wildcard characters: False
 
 ### -StatisticsStartIndex
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The StatisticsStartIndex parameter is used by the EAC to retrieve keyword statistics in a paged operation.
 
@@ -175,7 +175,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Start-ManagedFolderAssistant.md b/exchange/exchange-ps/ExchangePowerShell/Start-ManagedFolderAssistant.md
index 46ebde84f6..c3b0d8267e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Start-ManagedFolderAssistant.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Start-ManagedFolderAssistant.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
 Locale: en-US
@@ -139,7 +139,7 @@ This example uses the Get-Mailbox command to retrieve all the mailboxes that res
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the mailbox to be processed. In cross-premises deployments, you can also specify a mail user who has a mailbox in the cloud. You can use any value that uniquely identifies the mailbox or mail user. For example:
 
@@ -190,7 +190,7 @@ Accept wildcard characters: False
 
 ### -AggMailboxCleanup
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AggMailboxCleanup switch specifies aggregate mailbox cleanup. You don't need to specify a value with this switch.
 
@@ -270,7 +270,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -311,7 +311,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -351,7 +351,7 @@ Accept wildcard characters: False
 
 ### -HoldCleanup
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The HoldCleanup switch instructs the Managed Folder Assistant to clean up duplicate versions of items in the Recoverable Items folder that might have been created when a mailbox is on In-Place Hold, Litigation Hold, or has Single Item Recovery enabled. You don't need to specify a value with this switch.
 
@@ -417,7 +417,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Start-MigrationBatch.md b/exchange/exchange-ps/ExchangePowerShell/Start-MigrationBatch.md
index 2057afd43e..50807eac36 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Start-MigrationBatch.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Start-MigrationBatch.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -53,7 +53,7 @@ This example starts the migration batch SEM1.
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter identifies the migration batch that you want to start. Use the migration batch Name parameter as the value for this parameter. Use the Get-MigrationBatch cmdlet to identify the name of the migration batch.
 
@@ -71,7 +71,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -92,7 +92,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -132,7 +132,7 @@ Accept wildcard characters: False
 
 ### -Validate
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -154,7 +154,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Start-MigrationUser.md b/exchange/exchange-ps/ExchangePowerShell/Start-MigrationUser.md
index 2a837896b8..59b9123568 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Start-MigrationUser.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Start-MigrationUser.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -46,7 +46,7 @@ This example starts the migration of the user named laura@contoso.com
 
 ### -Identity
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the email address of the user that's being migrated.
 
@@ -66,7 +66,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -87,7 +87,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -127,7 +127,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Stop-ComplianceSearch.md b/exchange/exchange-ps/ExchangePowerShell/Stop-ComplianceSearch.md
index 2d60f04091..50dc351ba7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Stop-ComplianceSearch.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Stop-ComplianceSearch.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 author: chrisda
 external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
 Locale: en-US
@@ -48,7 +48,7 @@ This example stops the active compliance search named Case 1234
 
 ### -Identity
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The Identity parameter specifies the compliance search that you want to stop.
 
@@ -73,7 +73,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -94,7 +94,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 The WhatIf switch doesn't work in Security & Compliance PowerShell.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Stop-DatabaseAvailabilityGroup.md b/exchange/exchange-ps/ExchangePowerShell/Stop-DatabaseAvailabilityGroup.md
index 3731c78feb..fd68e66f9e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Stop-DatabaseAvailabilityGroup.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Stop-DatabaseAvailabilityGroup.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -73,7 +73,7 @@ This example stops the Mailbox server MBX3, which is currently offline, in the D
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the name of the DAG being stopped.
 
@@ -91,7 +91,7 @@ Accept wildcard characters: False
 
 ### -ActiveDirectorySite
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ActiveDirectorySite parameter specifies the Active Directory site containing the DAG members to stop (for example, stop all DAG members in a particular Active Directory site).
 
@@ -109,7 +109,7 @@ Accept wildcard characters: False
 
 ### -MailboxServer
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MailboxServer parameter specifies a single DAG member to stop. If Datacenter Activation Coordination mode is enabled for the DAG and all DAG members are in the same Active Directory site, use the MailboxServer parameter to stop individual DAG members instead of the ActiveDirectorySite parameter when stopping failed DAG members.
 
@@ -127,7 +127,7 @@ Accept wildcard characters: False
 
 ### -ConfigurationOnly
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ConfigurationOnly switch updates the Active Directory properties with the stop action, but doesn't perform a stop of the DAG or any members. You don't need to specify a value with this switch.
 
@@ -147,7 +147,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -168,7 +168,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -186,7 +186,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Stop-MailboxSearch.md b/exchange/exchange-ps/ExchangePowerShell/Stop-MailboxSearch.md
index ddfbcd46a5..3033128657 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Stop-MailboxSearch.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Stop-MailboxSearch.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
 Locale: en-US
@@ -49,7 +49,7 @@ This example stops the mailbox search Project Contoso.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the name of the mailbox search.
 
@@ -67,7 +67,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -88,7 +88,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -108,7 +108,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Stop-ManagedFolderAssistant.md b/exchange/exchange-ps/ExchangePowerShell/Stop-ManagedFolderAssistant.md
index da5e553d14..24ece5e1b7 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Stop-ManagedFolderAssistant.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Stop-ManagedFolderAssistant.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
 Locale: en-US
@@ -54,7 +54,7 @@ This example stops the Managed Folder Assistant on the servers ExchSrvr1 and Exc
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
 
@@ -79,7 +79,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -100,7 +100,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -118,7 +118,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Stop-MigrationBatch.md b/exchange/exchange-ps/ExchangePowerShell/Stop-MigrationBatch.md
index 56da49cbe3..f4acf68ecd 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Stop-MigrationBatch.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Stop-MigrationBatch.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -55,7 +55,7 @@ This example stops the migration batch MigrationBatch1.
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter identifies the name of the current migration batch. The value for this parameter is specified by the Name parameter of the New-MigrationBatch cmdlet.
 
@@ -73,7 +73,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -94,7 +94,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -134,7 +134,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 

From a9eb5f7270ba7378251941fe60039260e3d63ef9 Mon Sep 17 00:00:00 2001
From: Chris Davis <chris.davis@microsoft.com>
Date: Thu, 7 Aug 2025 15:50:18 -0700
Subject: [PATCH 136/145] Add Exchange Server SE 9

---
 .../ExchangePowerShell/Stop-MigrationUser.md  | 10 ++---
 .../Suspend-MailboxDatabaseCopy.md            | 16 +++----
 .../Suspend-MailboxExportRequest.md           | 12 ++---
 .../Suspend-MailboxImportRequest.md           | 12 ++---
 .../Suspend-MailboxRestoreRequest.md          | 12 ++---
 .../ExchangePowerShell/Suspend-Message.md     | 12 ++---
 .../ExchangePowerShell/Suspend-MoveRequest.md | 12 ++---
 ...end-PublicFolderMailboxMigrationRequest.md | 12 ++---
 .../Suspend-PublicFolderMigrationRequest.md   | 12 ++---
 .../Suspend-PublicFolderMoveRequest.md        | 12 ++---
 .../ExchangePowerShell/Suspend-Queue.md       | 12 ++---
 .../Test-ActiveSyncConnectivity.md            | 32 +++++++-------
 .../Test-ArchiveConnectivity.md               | 12 ++---
 .../Test-AssistantHealth.md                   | 18 ++++----
 .../Test-CalendarConnectivity.md              | 26 +++++------
 .../Test-ClientAccessRule.md                  | 18 ++++----
 .../Test-DataClassification.md                | 10 ++---
 .../Test-EcpConnectivity.md                   | 28 ++++++------
 .../Test-EdgeSynchronization.md               | 20 ++++-----
 .../ExchangePowerShell/Test-ExchangeSearch.md | 20 ++++-----
 .../Test-FederationTrust.md                   | 12 ++---
 .../Test-FederationTrustCertificate.md        |  8 ++--
 .../Test-IPAllowListProvider.md               | 14 +++---
 .../Test-IPBlockListProvider.md               | 14 +++---
 .../Test-IRMConfiguration.md                  | 14 +++---
 .../Test-ImapConnectivity.md                  | 30 ++++++-------
 .../Test-MAPIConnectivity.md                  | 28 ++++++------
 .../ExchangePowerShell/Test-MRSHealth.md      | 18 ++++----
 .../ExchangePowerShell/Test-Mailflow.md       | 34 +++++++-------
 .../Test-MigrationServerAvailability.md       | 26 +++++------
 .../Test-OAuthConnectivity.md                 | 18 ++++----
 .../Test-OrganizationRelationship.md          | 12 ++---
 .../Test-OutlookConnectivity.md               | 14 +++---
 .../Test-OutlookWebServices.md                | 18 ++++----
 .../Test-PopConnectivity.md                   | 30 ++++++-------
 .../Test-PowerShellConnectivity.md            | 28 ++++++------
 .../Test-ReplicationHealth.md                 | 20 ++++-----
 .../ExchangePowerShell/Test-SenderId.md       | 16 +++----
 .../ExchangePowerShell/Test-ServiceHealth.md  | 14 +++---
 .../ExchangePowerShell/Test-SiteMailbox.md    | 16 +++----
 .../Test-SmtpConnectivity.md                  | 12 ++---
 .../ExchangePowerShell/Test-TextExtraction.md | 10 ++---
 .../Test-WebServicesConnectivity.md           | 20 ++++-----
 .../Uninstall-TransportAgent.md               | 12 ++---
 .../ExchangePowerShell/Update-AddressList.md  | 10 ++---
 .../Update-DatabaseSchema.md                  | 12 ++---
 .../Update-DistributionGroupMember.md         | 14 +++---
 .../Update-EmailAddressPolicy.md              | 14 +++---
 .../ExchangePowerShell/Update-ExchangeHelp.md |  4 +-
 .../Update-GlobalAddressList.md               | 10 ++---
 .../Update-HybridConfiguration.md             | 16 +++----
 .../Update-MailboxDatabaseCopy.md             | 44 +++++++++----------
 .../Update-OfflineAddressBook.md              | 12 ++---
 .../Update-PublicFolderMailbox.md             | 24 +++++-----
 .../ExchangePowerShell/Update-Recipient.md    | 12 ++---
 .../Update-RoleGroupMember.md                 | 14 +++---
 .../ExchangePowerShell/Update-SafeList.md     | 16 +++----
 .../ExchangePowerShell/Update-SiteMailbox.md  | 18 ++++----
 .../Update-StoreMailboxState.md               | 10 ++---
 .../ExchangePowerShell/Write-AdminAuditLog.md | 10 ++---
 60 files changed, 498 insertions(+), 498 deletions(-)

diff --git a/exchange/exchange-ps/ExchangePowerShell/Stop-MigrationUser.md b/exchange/exchange-ps/ExchangePowerShell/Stop-MigrationUser.md
index 966fa96a5a..dcc2733a46 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Stop-MigrationUser.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Stop-MigrationUser.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -46,7 +46,7 @@ This example stops the migration of the user laura@contoso.com.
 
 ### -Identity
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the email address of the user that's being migrated.
 
@@ -66,7 +66,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -87,7 +87,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -127,7 +127,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Suspend-MailboxDatabaseCopy.md b/exchange/exchange-ps/ExchangePowerShell/Suspend-MailboxDatabaseCopy.md
index 07496d4408..358bee1cd6 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Suspend-MailboxDatabaseCopy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Suspend-MailboxDatabaseCopy.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -65,7 +65,7 @@ This example only suspends activation for the copy of the database DB3 hosted on
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the name of the database copy being suspended.
 
@@ -83,7 +83,7 @@ Accept wildcard characters: False
 
 ### -ActivationOnly
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ActivationOnly switch specifies whether to suspend only activation for the mailbox database copy. You don't need to specify a value with this switch.
 
@@ -101,7 +101,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -122,7 +122,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -140,7 +140,7 @@ Accept wildcard characters: False
 
 ### -EnableReplayLag
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -158,7 +158,7 @@ Accept wildcard characters: False
 
 ### -SuspendComment
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SuspendComment parameter specifies the reason that the database copy is being suspended. This parameter is limited to 512 characters.
 
@@ -176,7 +176,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Suspend-MailboxExportRequest.md b/exchange/exchange-ps/ExchangePowerShell/Suspend-MailboxExportRequest.md
index 215f82623c..b8e9238531 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Suspend-MailboxExportRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Suspend-MailboxExportRequest.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -55,7 +55,7 @@ This example suspends all export requests that are in progress by using the Get-
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the identity of the export request. By default, export requests are named `<alias>\MailboxExportX` (where X = 0-9). Use the following syntax: `Alias\Name`.
 
@@ -73,7 +73,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -94,7 +94,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -112,7 +112,7 @@ Accept wildcard characters: False
 
 ### -SuspendComment
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SuspendComment parameter specifies a description about why the request was suspended. You can only use this parameter if you specify the Suspend parameter.
 
@@ -130,7 +130,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Suspend-MailboxImportRequest.md b/exchange/exchange-ps/ExchangePowerShell/Suspend-MailboxImportRequest.md
index 214fd604b0..23e614915e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Suspend-MailboxImportRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Suspend-MailboxImportRequest.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -57,7 +57,7 @@ This example suspends all import requests that are in progress by using the Get-
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the identity of the import request. By default, import requests are named `<alias>\MailboxImportX` (where X = 0-9). If you created the request by using the Name parameter, use the following syntax: `Alias\Name`.
 
@@ -75,7 +75,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -96,7 +96,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -116,7 +116,7 @@ Accept wildcard characters: False
 
 ### -SuspendComment
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SuspendComment parameter specifies a description about why the request was suspended. You can only use this parameter if you specify the Suspend parameter.
 
@@ -134,7 +134,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Suspend-MailboxRestoreRequest.md b/exchange/exchange-ps/ExchangePowerShell/Suspend-MailboxRestoreRequest.md
index 67f90c841e..bee0d5a78f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Suspend-MailboxRestoreRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Suspend-MailboxRestoreRequest.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -53,7 +53,7 @@ This example suspends all restore requests that are in progress by using the Get
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the identity of the restore request. The Identity parameter consists of the alias of the mailbox to be restored and the name that was specified when the restore request was created. The identity of the restore request uses the following syntax: `Alias\Name`.
 
@@ -73,7 +73,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -94,7 +94,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -114,7 +114,7 @@ Accept wildcard characters: False
 
 ### -SuspendComment
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SuspendComment parameter specifies a description about why the request was suspended.
 
@@ -132,7 +132,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Suspend-Message.md b/exchange/exchange-ps/ExchangePowerShell/Suspend-Message.md
index ce944390fa..6f8990c619 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Suspend-Message.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Suspend-Message.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -63,7 +63,7 @@ This example prevents delivery of all messages for which the following condition
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the message. Valid input for this parameter uses the syntax Server\\Queue\\MessageInteger or Queue\\MessageInteger or MessageInteger, for example, Mailbox01\\contoso.com\\5 or 10. For details about message identity, see [Message identity](https://learn.microsoft.com/Exchange/mail-flow/queues/queues-and-messages-in-powershell#message-identity).
 
@@ -81,7 +81,7 @@ Accept wildcard characters: False
 
 ### -Filter
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Filter parameter specifies one or more messages by using OPATH filter syntax. The OPATH filter includes a message property name followed by a comparison operator and value (for example, `"FromAddress -like '*@contoso.com'"`). For details about filterable message properties and comparison operators, see [Properties of messages in queues](https://learn.microsoft.com/Exchange/mail-flow/queues/message-properties) and [Find queues and messages in queues in the Exchange Management Shell](https://learn.microsoft.com/Exchange/mail-flow/queues/queues-and-messages-in-powershell).
 
@@ -101,7 +101,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -122,7 +122,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
 
@@ -149,7 +149,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Suspend-MoveRequest.md b/exchange/exchange-ps/ExchangePowerShell/Suspend-MoveRequest.md
index d9655f431c..a710a4defc 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Suspend-MoveRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Suspend-MoveRequest.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -54,7 +54,7 @@ This example suspends all move requests that are in progress by using the Get-Mo
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the identity of the mailbox or mail user. You can use one of the following values:
 
@@ -80,7 +80,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -101,7 +101,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -152,7 +152,7 @@ Accept wildcard characters: False
 
 ### -SuspendComment
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SuspendComment parameter specifies a description as to why the request was suspended.
 
@@ -170,7 +170,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Suspend-PublicFolderMailboxMigrationRequest.md b/exchange/exchange-ps/ExchangePowerShell/Suspend-PublicFolderMailboxMigrationRequest.md
index 13bad0297d..3fed8dba41 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Suspend-PublicFolderMailboxMigrationRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Suspend-PublicFolderMailboxMigrationRequest.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -46,7 +46,7 @@ This example suspends the specified public folder mailbox migration request.
 
 ### -Identity
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the public folder mailbox migration request that you want to suspend. This value uses the syntax `\PublicFolderMailboxMigration<GUID>` (for example, `\PublicFolderMailboxMigrationac6d9eb4-ee49-405f-b90d-04e9a258bd7e`).
 
@@ -64,7 +64,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -85,7 +85,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -105,7 +105,7 @@ Accept wildcard characters: False
 
 ### -SuspendComment
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SuspendComment parameter specifies a descriptive reason for why you suspended the public folder mailbox migration. If the value contains spaces, enclose the value in quotation marks.
 
@@ -123,7 +123,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Suspend-PublicFolderMigrationRequest.md b/exchange/exchange-ps/ExchangePowerShell/Suspend-PublicFolderMigrationRequest.md
index a699004778..e0b3bf7472 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Suspend-PublicFolderMigrationRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Suspend-PublicFolderMigrationRequest.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -55,7 +55,7 @@ This example suspends all migration requests that are in progress by using the G
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the migration request that you want to suspend. You can use the following values:
 
@@ -76,7 +76,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -97,7 +97,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -115,7 +115,7 @@ Accept wildcard characters: False
 
 ### -SuspendComment
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SuspendComment parameter specifies a description as to why the request was suspended.
 
@@ -133,7 +133,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Suspend-PublicFolderMoveRequest.md b/exchange/exchange-ps/ExchangePowerShell/Suspend-PublicFolderMoveRequest.md
index 42a675cbdb..8e0c073d7e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Suspend-PublicFolderMoveRequest.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Suspend-PublicFolderMoveRequest.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -46,7 +46,7 @@ This example suspends the public folder move request \\PublicFolderMove.
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the identity of the public folder move request. The default identity is \\PublicFolderMove.
 
@@ -64,7 +64,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -85,7 +85,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -103,7 +103,7 @@ Accept wildcard characters: False
 
 ### -SuspendComment
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SuspendComment parameter specifies a description about why the request was suspended. You can only use this parameter if you specify the Suspend parameter.
 
@@ -121,7 +121,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Suspend-Queue.md b/exchange/exchange-ps/ExchangePowerShell/Suspend-Queue.md
index 120227683d..b5f271cc28 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Suspend-Queue.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Suspend-Queue.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -65,7 +65,7 @@ This example suspends processing on all queues on the server Server1.contoso.com
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the queue. Valid input for this parameter uses the syntax Server\\Queue or Queue, for example, Mailbox01\\contoso.com or Unreachable. For details about queue identity, see [Queue identity](https://learn.microsoft.com/Exchange/mail-flow/queues/queues-and-messages-in-powershell#queue-identity).
 
@@ -83,7 +83,7 @@ Accept wildcard characters: False
 
 ### -Filter
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Filter parameter specifies one or more queues by using OPATH filter syntax. The OPATH filter includes a queue property name followed by a comparison operator and value (for example, `"NextHopDomain -eq 'contoso.com'"`). For details about filterable queue properties and comparison operators, see [Queue properties in Exchange Server](https://learn.microsoft.com/Exchange/mail-flow/queues/queue-properties) and [Find queues and messages in queues in the Exchange Management Shell](https://learn.microsoft.com/Exchange/mail-flow/queues/queues-and-messages-in-powershell).
 
@@ -103,7 +103,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -124,7 +124,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
 
@@ -151,7 +151,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-ActiveSyncConnectivity.md b/exchange/exchange-ps/ExchangePowerShell/Test-ActiveSyncConnectivity.md
index df131fd9b3..4f1a49368e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-ActiveSyncConnectivity.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-ActiveSyncConnectivity.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.MediaAndDevices-Help.xml
 Locale: en-US
@@ -81,7 +81,7 @@ This example tests the Exchange ActiveSync connectivity for the mailbox PaulS us
 
 ### -ClientAccessServer
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ClientAccessServer parameter specifies the Exchange server to test. This server has the Client Access server role installed and is responsible for accepting client connections.
 
@@ -108,7 +108,7 @@ Accept wildcard characters: False
 
 ### -URL
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The URL parameter specifies the URL that's used to connect to the Exchange ActiveSync virtual directory.
 
@@ -128,7 +128,7 @@ Accept wildcard characters: False
 
 ### -AllowUnsecureAccess
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AllowUnsecureAccess switch allows the test to continue over an unsecured channel that doesn't require Secure Sockets Layer (SSL). You don't need to specify a value with this switch.
 
@@ -146,7 +146,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -167,7 +167,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -185,7 +185,7 @@ Accept wildcard characters: False
 
 ### -LightMode
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The LightMode switch tells the command to perform only a subset of the tests. You don't need to specify a value with this switch.
 
@@ -207,7 +207,7 @@ Accept wildcard characters: False
 
 ### -MailboxCredential
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MailboxCredential parameter specifies the mailbox credential to use for a single mailbox test.
 
@@ -227,7 +227,7 @@ Accept wildcard characters: False
 
 ### -MailboxServer
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MailboxServer parameter specifies the Exchange Mailbox server that you want to test. This parameter identifies the backend server that accepts proxied connections from the frontend server where clients connect.
 
@@ -254,7 +254,7 @@ Accept wildcard characters: False
 
 ### -MonitoringContext
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MonitoringContext switch includes the associated monitoring events and performance counters in the results. You don't need to specify a value with this switch.
 
@@ -274,7 +274,7 @@ Accept wildcard characters: False
 
 ### -MonitoringInstance
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MonitoringInstance parameter specifies an identifier for this task when the test is run from Microsoft System Center Operations Manager (SCOM). This parameter is important because SCOM might run multiple instances of the test from the same server at the same time.
 
@@ -292,7 +292,7 @@ Accept wildcard characters: False
 
 ### -ResetTestAccountCredentials
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ResetTestAccountCredentials switch resets the password for the test account that's used to run this command. You don't need to specify a value with this switch.
 
@@ -312,7 +312,7 @@ Accept wildcard characters: False
 
 ### -Timeout
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Timeout parameter specifies the amount of time (in seconds) to wait for a response from the command.
 
@@ -330,7 +330,7 @@ Accept wildcard characters: False
 
 ### -TrustAnySSLCertificate
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TrustAnySSLCertificate switch allows Exchange to accept certificates from untrusted certification authorities (CAs). You don't need to specify a value with this switch.
 
@@ -350,7 +350,7 @@ Accept wildcard characters: False
 
 ### -UseAutodiscoverForClientAccessServer
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The UseAutodiscoverForClientAccessServer switch specifies whether the test should use the Autodiscover service to locate the Exchange ActiveSync virtual directory. You don't need to specify a value with this switch.
 
@@ -368,7 +368,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-ArchiveConnectivity.md b/exchange/exchange-ps/ExchangePowerShell/Test-ArchiveConnectivity.md
index eaa3c1bee5..07d2cfe24b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-ArchiveConnectivity.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-ArchiveConnectivity.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -55,7 +55,7 @@ This command retrieves mailboxes that have a cloud-based archive provisioned and
 
 ### -UserSmtp
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The UserSmtp parameter specifies the SMTP address of the mailbox.
 
@@ -73,7 +73,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -94,7 +94,7 @@ Accept wildcard characters: False
 
 ### -IncludeArchiveMRMConfiguration
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IncludeArchiveMRMConfiguration switch retrieves retention tags that are provisioned in the user's archive mailbox and the last time the archive was processed by the Managed Folder Assistant. You don't need to specify a value with this switch.
 
@@ -112,7 +112,7 @@ Accept wildcard characters: False
 
 ### -MessageId
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -130,7 +130,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-AssistantHealth.md b/exchange/exchange-ps/ExchangePowerShell/Test-AssistantHealth.md
index 020c9680a2..9ef180021a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-AssistantHealth.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-AssistantHealth.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -60,7 +60,7 @@ This example detects the mailbox assistant's health on the local Mailbox server.
 
 ### -ServerName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ServerName parameter specifies the Mailbox server where you want to run this command. You can use any value that uniquely identifies the server. For example:
 
@@ -85,7 +85,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -106,7 +106,7 @@ Accept wildcard characters: False
 
 ### -IncludeCrashDump
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IncludeCrashDump switch specifies that the command should take an error report prior to taking any recovery actions. You don't need to specify a value with this switch.
 
@@ -126,7 +126,7 @@ Accept wildcard characters: False
 
 ### -MaxProcessingTimeInMinutes
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MaxProcessingTimeInMinutes parameter specifies the maximum amount of time the MSExchangeMailboxAssistants service is allowed to process an event without responding. You can specify a value from 1 through 3600 minutes. The default value is 15 minutes.
 
@@ -144,7 +144,7 @@ Accept wildcard characters: False
 
 ### -MonitoringContext
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MonitoringContext switch includes the associated monitoring events and performance counters in the results. You don't need to specify a value with this switch.
 
@@ -164,7 +164,7 @@ Accept wildcard characters: False
 
 ### -ResolveProblems
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This ResolveProblems switch specifies that if the command detects an issue, it attempts to fix it. You don't need to specify a value with this switch.
 
@@ -187,7 +187,7 @@ Accept wildcard characters: False
 
 ### -WatermarkBehindWarningThreholdInMinutes
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WatermarkBehindWarningThreholdInMinutes parameter specifies the threshold for watermark age. Event watermarks indicate the last time that events were successfully processed by an assistant. An event watermark that hasn't been updated in a while might indicate a problem. For each Mailbox Assistant, the Test-AssistantHealth cmdlet compares the current time with the time stamp of the last event watermark to determine the watermark age. If that age exceeds the value set by the WatermarkBehindWarningThreholdInMinutes parameter, a warning is generated.
 
@@ -207,7 +207,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-CalendarConnectivity.md b/exchange/exchange-ps/ExchangePowerShell/Test-CalendarConnectivity.md
index 159c954cd1..f7db94b064 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-CalendarConnectivity.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-CalendarConnectivity.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -74,7 +74,7 @@ This example tests the anonymous calendar sharing for the server named MBX01.
 
 ### -ClientAccessServer
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ClientAccessServer parameter specifies the Exchange server to test. This server has the Client Access server role installed, and is responsible for accepting client connections.
 
@@ -99,7 +99,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -120,7 +120,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -138,7 +138,7 @@ Accept wildcard characters: False
 
 ### -LightMode
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter isn't implemented for this diagnostic command. Using this parameter doesn't change the behavior of this command.
 
@@ -156,7 +156,7 @@ Accept wildcard characters: False
 
 ### -MailboxServer
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MailboxServer parameter specifies the Exchange Mailbox server that you want to test. This parameter identifies the backend server that accepts proxied connections from the frontend server where clients connect.
 
@@ -183,7 +183,7 @@ Accept wildcard characters: False
 
 ### -MonitoringContext
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MonitoringContext switch includes the associated monitoring events and performance counters in the results. You don't need to specify a value with this switch.
 
@@ -203,7 +203,7 @@ Accept wildcard characters: False
 
 ### -ResetTestAccountCredentials
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ResetTestAccountCredentials switch resets the password for the test account that's used to run this command. You don't need to specify a value with this switch.
 
@@ -223,7 +223,7 @@ Accept wildcard characters: False
 
 ### -TestType
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TestType parameter specifies whether the command tests internal or external URLs. Values are Internal and External. The default value is Internal.
 
@@ -241,7 +241,7 @@ Accept wildcard characters: False
 
 ### -Timeout
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter isn't implemented for this diagnostic command. Using this parameter doesn't change the behavior of this command.
 
@@ -259,7 +259,7 @@ Accept wildcard characters: False
 
 ### -TrustAnySSLCertificate
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter isn't implemented for this diagnostic command. Using this parameter doesn't change the behavior of this command.
 
@@ -277,7 +277,7 @@ Accept wildcard characters: False
 
 ### -VirtualDirectoryName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The VirtualDirectoryName parameter specifies the name of the Outlook on the web virtual directory that you want to test. Enclose values that contain spaces in quotation marks (").
 
@@ -297,7 +297,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-ClientAccessRule.md b/exchange/exchange-ps/ExchangePowerShell/Test-ClientAccessRule.md
index 8eb927c992..c6cb852390 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-ClientAccessRule.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-ClientAccessRule.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.WebClient-Help.xml
 Locale: en-US
@@ -63,7 +63,7 @@ This example tests client access by using the following client properties:
 
 ### -AuthenticationType
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The AuthenticationType parameter specifies the client authentication type to test.
 
@@ -91,7 +91,7 @@ Accept wildcard characters: False
 
 ### -Protocol
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Protocol parameter specifies the client protocol to test.
 
@@ -125,7 +125,7 @@ Accept wildcard characters: False
 
 ### -RemoteAddress
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The RemoteAddress parameter specifies the client IP address to test. Valid input for this parameter is an IP address. For example, 192.168.1.50.
 
@@ -145,7 +145,7 @@ Accept wildcard characters: False
 
 ### -RemotePort
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The RemotePort parameter specifies the client TCP port to test. Valid input for this parameter is an integer from 1 to 65535.
 
@@ -163,7 +163,7 @@ Accept wildcard characters: False
 
 ### -User
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The User parameter specifies the user account to test.
 
@@ -201,7 +201,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -222,7 +222,7 @@ Accept wildcard characters: False
 
 ### -OAuthClaims
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The OAuthClaims parameter specifies the OAuth claims token of a middle-tier app.
 
@@ -240,7 +240,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-DataClassification.md b/exchange/exchange-ps/ExchangePowerShell/Test-DataClassification.md
index ce07e02eed..5126151cb5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-DataClassification.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-DataClassification.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance
+applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -51,7 +51,7 @@ This example lists all sensitive info types, their count, and confidence in the
 
 ### -ClassificationNames
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance
 
 The ClassificationNames parameter specifies the sensitive information type that you want to find in the text specified by the TextToClassify parameter. Valid values are:
 
@@ -74,7 +74,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance
 
 This parameter is functional only in on-premises Exchange.
 
@@ -114,7 +114,7 @@ Accept wildcard characters: False
 
 ### -TestTextExtractionResults
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance
 
 The TestTextExtractionResults parameter specifies the extracted text from the Test-TextExtraction cmdlet as the input text stream.
 
@@ -132,7 +132,7 @@ Accept wildcard characters: False
 
 ### -TextToClassify
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance
 
 The TextToClassify parameter specifies the text string for which classification results need to be shown.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-EcpConnectivity.md b/exchange/exchange-ps/ExchangePowerShell/Test-EcpConnectivity.md
index 8ee2056293..e9a4a9e8e6 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-EcpConnectivity.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-EcpConnectivity.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -73,7 +73,7 @@ This example tests user connectivity to the Exchange admin center on Server01.
 
 ### -ClientAccessServer
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ClientAccessServer parameter specifies the Exchange server to test. This server has the Client Access server role installed and is responsible for accepting client connections.
 
@@ -98,7 +98,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -119,7 +119,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -137,7 +137,7 @@ Accept wildcard characters: False
 
 ### -LightMode
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter isn't implemented for this diagnostic command. Using this parameter doesn't change the behavior of this command.
 
@@ -155,7 +155,7 @@ Accept wildcard characters: False
 
 ### -MailboxServer
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MailboxServer parameter specifies the Exchange Mailbox server that you want to test. This parameter identifies the backend server that accepts proxied connections from the frontend server where clients connect.
 
@@ -182,7 +182,7 @@ Accept wildcard characters: False
 
 ### -MonitoringContext
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MonitoringContext switch includes the associated monitoring events and performance counters in the results. You don't need to specify a value with this switch.
 
@@ -202,7 +202,7 @@ Accept wildcard characters: False
 
 ### -ResetTestAccountCredentials
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ResetTestAccountCredentials switch resets the password for the test account that's used to run this command. You don't need to specify a value with this switch.
 
@@ -222,7 +222,7 @@ Accept wildcard characters: False
 
 ### -RSTEndpoint
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -240,7 +240,7 @@ Accept wildcard characters: False
 
 ### -TestType
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TestType parameter specifies whether the command tests internal or external URLs. Values are Internal and External. The default value is Internal.
 
@@ -258,7 +258,7 @@ Accept wildcard characters: False
 
 ### -Timeout
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Timeout parameter specifies the amount of time, in seconds, to wait for the test operation to finish. The default value for the Timeout parameter is 30 seconds. You must specify a time-out value greater than 0 seconds and less than 1 hour (3,600 seconds). We recommend that you always configure this parameter with a value of 5 seconds or more.
 
@@ -276,7 +276,7 @@ Accept wildcard characters: False
 
 ### -TrustAnySSLCertificate
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TrustAnySSLCertificate switch allows Exchange to accept certificates from untrusted certification authorities (CAs). You don't need to specify a value with this switch.
 
@@ -296,7 +296,7 @@ Accept wildcard characters: False
 
 ### -VirtualDirectoryName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The VirtualDirectoryName parameter specifies the name of the EAC virtual directory that you want to test. Enclose values that contain spaces in quotation marks (").
 
@@ -316,7 +316,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-EdgeSynchronization.md b/exchange/exchange-ps/ExchangePowerShell/Test-EdgeSynchronization.md
index 6d52fd1d73..2565e0d1c4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-EdgeSynchronization.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-EdgeSynchronization.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -70,7 +70,7 @@ This example verifies the synchronization status of the single recipient kate@co
 
 ### -VerifyRecipient
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The VerifyRecipient parameter specifies a single recipient with which to verify the synchronization status. You identify the recipient by specifying a proxy address assigned to the recipient. The proxy address is the recipient's email address. The recipient verification test is mutually exclusive of the test that verifies synchronization of configuration data.
 
@@ -88,7 +88,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -109,7 +109,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -127,7 +127,7 @@ Accept wildcard characters: False
 
 ### -ExcludeRecipientTest
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExcludeRecipientTest switch specifies whether to exclude validation of recipient data synchronization. You don't need to specify a value with this switch.
 
@@ -147,7 +147,7 @@ Accept wildcard characters: False
 
 ### -FullCompareMode
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The FullCompareMode switch specifies whether a full comparison of the configuration data between Active Directory and AD LDS instance on the target Edge Transport server is performed. You don't need to specify a value with this switch.
 
@@ -167,7 +167,7 @@ Accept wildcard characters: False
 
 ### -MaxReportSize
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MaxReportSize parameter specifies the total number of objects and properties listed in the results. The results output by this command include a list of all out-of-sync objects and properties in both AD LDS and Active Directory. If the directory services aren't synchronized, a large amount of data can result. If you don't specify a value for this parameter, the default value of 1,000 is used. The minimum value for this parameter is 1. The maximum value for this parameter is unlimited.
 
@@ -185,7 +185,7 @@ Accept wildcard characters: False
 
 ### -MonitoringContext
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MonitoringContext parameter specifies whether to include the associated monitoring events and performance counters in the results. Valid values are:
 
@@ -206,7 +206,7 @@ Accept wildcard characters: False
 
 ### -TargetServer
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TargetServer parameter specifies an Edge Transport server to initiate edge synchronization with. If omitted, all Edge Transport servers are synchronized.
 
@@ -226,7 +226,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-ExchangeSearch.md b/exchange/exchange-ps/ExchangePowerShell/Test-ExchangeSearch.md
index 2e3de30489..ea1a930da9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-ExchangeSearch.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-ExchangeSearch.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.WebClient-Help.xml
 Locale: en-US
@@ -82,7 +82,7 @@ This example tests Exchange Search results for the mailbox database on which the
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the mailbox that you want to test Exchange Search against. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -113,7 +113,7 @@ Accept wildcard characters: False
 
 ### -Archive
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Archive switch specifies that the test is run against the archive mailbox for the mailbox user specified by the Identity parameter. You don't need to specify a value with this switch.
 
@@ -131,7 +131,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -152,7 +152,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -170,7 +170,7 @@ Accept wildcard characters: False
 
 ### -IndexingTimeoutInSeconds
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IndexingTimeoutInSeconds parameter specifies, in seconds, the maximum amount of time to wait between adding the new email message to the test mailbox and waiting for it to be returned in a search result. The default value is 120 seconds. If this parameter isn't specified, the default interval is used.
 
@@ -188,7 +188,7 @@ Accept wildcard characters: False
 
 ### -MailboxDatabase
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is functional only in Exchange Server 2010 and 2013.
 
@@ -214,7 +214,7 @@ Accept wildcard characters: False
 
 ### -MonitoringContext
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MonitoringContext switch includes the associated monitoring events and performance counters in the results. You don't need to specify a value with this switch.
 
@@ -234,7 +234,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Exchange server for the recipient that you want to test Exchange Search against. You can use any value that uniquely identifies the server. For example:
 
@@ -259,7 +259,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-FederationTrust.md b/exchange/exchange-ps/ExchangePowerShell/Test-FederationTrust.md
index 1337a5ab35..eaf1f69594 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-FederationTrust.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-FederationTrust.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
 Locale: en-US
@@ -58,7 +58,7 @@ This example validates the federation trust deployed in the Exchange organizatio
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -79,7 +79,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -97,7 +97,7 @@ Accept wildcard characters: False
 
 ### -MonitoringContext
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MonitoringContext parameter specifies whether to include the associated monitoring events and performance counters in the results. Valid values are:
 
@@ -118,7 +118,7 @@ Accept wildcard characters: False
 
 ### -UserIdentity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The UserIdentity parameter specifies a mailbox user to request a token for. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -145,7 +145,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-FederationTrustCertificate.md b/exchange/exchange-ps/ExchangePowerShell/Test-FederationTrustCertificate.md
index 96a42d4b29..781666803b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-FederationTrustCertificate.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-FederationTrustCertificate.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
 Locale: en-US
@@ -46,7 +46,7 @@ This example reports the status of federation certificates.
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -67,7 +67,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -85,7 +85,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-IPAllowListProvider.md b/exchange/exchange-ps/ExchangePowerShell/Test-IPAllowListProvider.md
index 4d368590b2..6c5899366a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-IPAllowListProvider.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-IPAllowListProvider.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailControl-Help.xml
 Locale: en-US
@@ -48,7 +48,7 @@ This example tests the existing IP Allow list provider named Contoso,com by send
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the IP Allow list provider that you want to test. You can use any value that uniquely identifies the IP Allow list provider. For example:
 
@@ -70,7 +70,7 @@ Accept wildcard characters: False
 
 ### -IPAddress
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IPAddress parameter specifies an IP address to be used in testing the IP Allow list provider. You need to use a known allowed IP address.
 
@@ -88,7 +88,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -109,7 +109,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -129,7 +129,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
 
@@ -156,7 +156,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-IPBlockListProvider.md b/exchange/exchange-ps/ExchangePowerShell/Test-IPBlockListProvider.md
index bd4bab5f58..dbfb72bf09 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-IPBlockListProvider.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-IPBlockListProvider.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailControl-Help.xml
 Locale: en-US
@@ -48,7 +48,7 @@ This example tests the existing IP Block list provider named Contoso.com by send
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the IP Block list provider that you want to test. You can use any value that uniquely identifies the IP Block list provider. For example:
 
@@ -70,7 +70,7 @@ Accept wildcard characters: False
 
 ### -IPAddress
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IPAddress parameter specifies an IP address to be used in testing the IP Block list provider. You need to use a known blocked IP address.
 
@@ -88,7 +88,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -109,7 +109,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -129,7 +129,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
 
@@ -156,7 +156,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-IRMConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Test-IRMConfiguration.md
index cae7553941..9d4926513f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-IRMConfiguration.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-IRMConfiguration.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailControl-Help.xml
 Locale: en-US
@@ -56,7 +56,7 @@ This example tests the IRM configuration in the cloud-based service for messages
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -76,7 +76,7 @@ Accept wildcard characters: False
 
 ### -Sender
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Sender parameter specifies the email address of the sender to test.
 
@@ -94,7 +94,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -115,7 +115,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -135,7 +135,7 @@ Accept wildcard characters: False
 
 ### -Recipient
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Recipient parameter specifies the email address of the recipient to test. You can specify multiple email addresses separated by commas.
 
@@ -177,7 +177,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-ImapConnectivity.md b/exchange/exchange-ps/ExchangePowerShell/Test-ImapConnectivity.md
index ed70baf7d5..47fd7ae231 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-ImapConnectivity.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-ImapConnectivity.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -87,7 +87,7 @@ This example tests the client IMAP4 connectivity of the server named Contoso12 a
 
 ### -ClientAccessServer
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ClientAccessServer parameter specifies the Exchange server to test. This server has the Client Access server role installed, and is responsible for accepting client connections.
 
@@ -112,7 +112,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -133,7 +133,7 @@ Accept wildcard characters: False
 
 ### -ConnectionType
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ConnectionType parameter specifies the type of connection that's used to connect to the IMAP4 service. Valid values are:
 
@@ -155,7 +155,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -173,7 +173,7 @@ Accept wildcard characters: False
 
 ### -LightMode
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The LightMode switch tells the command to perform only a test logon to the server by using the IMAP4 protocol. You don't need to specify a value with this switch.
 
@@ -193,7 +193,7 @@ Accept wildcard characters: False
 
 ### -MailboxCredential
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MailboxCredential parameter specifies the mailbox credential to use for a single mailbox test.
 
@@ -213,7 +213,7 @@ Accept wildcard characters: False
 
 ### -MailboxServer
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MailboxServer parameter specifies the Exchange Mailbox server that you want to test. This parameter identifies the backend server that accepts proxied connections from the frontend server where clients connect.
 
@@ -240,7 +240,7 @@ Accept wildcard characters: False
 
 ### -MonitoringContext
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MonitoringContext switch includes the associated monitoring events and performance counters in the results. You don't need to specify a value with this switch.
 
@@ -260,7 +260,7 @@ Accept wildcard characters: False
 
 ### -PerConnectionTimeout
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PerConnectionTimeout parameter specifies the amount of time, in seconds, to wait per connection for the test operation to finish. Valid values are between 0 and 120 seconds. The default value is 120 seconds.
 
@@ -280,7 +280,7 @@ Accept wildcard characters: False
 
 ### -PortClientAccessServer
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PortClientAccessServer parameter specifies the port to use to connect to the Client Access server. The default port is 143 for IMAP4. The valid range is from 0 through 65,535.
 
@@ -298,7 +298,7 @@ Accept wildcard characters: False
 
 ### -ResetTestAccountCredentials
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ResetTestAccountCredentials switch resets the password for the test account that's used to run this command. You don't need to specify a value with this switch.
 
@@ -318,7 +318,7 @@ Accept wildcard characters: False
 
 ### -Timeout
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Timeout parameter specifies the amount of time, in seconds, to wait for the test operation to finish. Valid values are between 0 and 3600 seconds (1 hour). The default value is 180 seconds (3 minutes).
 
@@ -338,7 +338,7 @@ Accept wildcard characters: False
 
 ### -TrustAnySSLCertificate
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TrustAnySSLCertificate switch allows Exchange to accept certificates from untrusted certification authorities (CAs). You don't need to specify a value with this switch.
 
@@ -358,7 +358,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-MAPIConnectivity.md b/exchange/exchange-ps/ExchangePowerShell/Test-MAPIConnectivity.md
index b144800754..cfd7f7fb0e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-MAPIConnectivity.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-MAPIConnectivity.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -97,7 +97,7 @@ This example tests connectivity to a mailbox, specified as a domain name and use
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies a mailbox to test. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -132,7 +132,7 @@ Accept wildcard characters: False
 
 ### -Database
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -160,7 +160,7 @@ Accept wildcard characters: False
 
 ### -ActiveDirectoryTimeout
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -180,7 +180,7 @@ Accept wildcard characters: False
 
 ### -AllConnectionsTimeout
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -200,7 +200,7 @@ Accept wildcard characters: False
 
 ### -Archive
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Archive switch specifies whether to test the MAPI connectivity of the personal archive that's associated with the specified mailbox. You don't need to specify a value with this switch.
 
@@ -220,7 +220,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -241,7 +241,7 @@ Accept wildcard characters: False
 
 ### -CopyOnServer
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -268,7 +268,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -288,7 +288,7 @@ Accept wildcard characters: False
 
 ### -IncludePassive
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -310,7 +310,7 @@ Accept wildcard characters: False
 
 ### -MonitoringContext
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -333,7 +333,7 @@ Accept wildcard characters: False
 
 ### -PerConnectionTimeout
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -353,7 +353,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -382,7 +382,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-MRSHealth.md b/exchange/exchange-ps/ExchangePowerShell/Test-MRSHealth.md
index ab340d8e87..d5513b2862 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-MRSHealth.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-MRSHealth.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -58,7 +58,7 @@ This example tests the health of the Mailbox Replication service on the Mailbox
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the server on which to perform the health test. You can use any value that uniquely identifies the server. For example:
 
@@ -83,7 +83,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -104,7 +104,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -122,7 +122,7 @@ Accept wildcard characters: False
 
 ### -MaxQueueScanAgeSeconds
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MaxQueueScanAgeSeconds parameter specifies the threshold for the last queue scan property. If the time stamp on the last queue scan property is older than the value specified by this parameter, an error event is created that shows the Mailbox Replication service isn't scanning mailbox database queues. The default value is 1800 seconds (30 minutes).
 
@@ -140,7 +140,7 @@ Accept wildcard characters: False
 
 ### -MonitoringContext
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MonitoringContext parameter specifies whether to include the associated monitoring events and performance counters in the results. Valid values are:
 
@@ -161,7 +161,7 @@ Accept wildcard characters: False
 
 ### -MRSProxyCredentials
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MRSProxyCredentials parameter specifies the credentials that are required for the MRSProxyPingCheck test on the server that's specified by the MRSProxyServer parameter.
 
@@ -181,7 +181,7 @@ Accept wildcard characters: False
 
 ### -MRSProxyServer
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MRSProxyServer parameter specifies the fully qualified domain name (FQDN) of the target server for the MRSProxyPingCheck test.
 
@@ -205,7 +205,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-Mailflow.md b/exchange/exchange-ps/ExchangePowerShell/Test-Mailflow.md
index cd3071a0cd..02e216dd65 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-Mailflow.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-Mailflow.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -137,7 +137,7 @@ This example tests message flow from the local Mailbox server where you're runni
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the source Mailbox server name from which a test message is sent. You can use any value that uniquely identifies the server. For example:
 
@@ -162,7 +162,7 @@ Accept wildcard characters: False
 
 ### -AutoDiscoverTargetMailboxServer
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AutoDiscoverTargetMailboxServer switch specifies whether to automatically populate a list of target Mailbox servers to which to send a test message. You don't need to specify a value with this switch.
 
@@ -184,7 +184,7 @@ Accept wildcard characters: False
 
 ### -CrossPremises
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The CrossPremises parameter specifies whether the mail flow test is conducted in cross-premises mode.
 
@@ -206,7 +206,7 @@ Accept wildcard characters: False
 
 ### -TargetDatabase
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TargetDatabase parameter specifies the mailbox database to which test messages are sent. You can use any value that uniquely identifies the database. For example:
 
@@ -230,7 +230,7 @@ Accept wildcard characters: False
 
 ### -TargetEmailAddress
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TargetEmailAddress parameter specifies the SMTP address of the mailbox to which test messages are sent. Use this parameter to send test messages to a Mailbox server in a remote forest. If this parameter is used, the test is always a remote test.
 
@@ -250,7 +250,7 @@ Accept wildcard characters: False
 
 ### -TargetMailboxServer
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TargetMailboxServer parameter specifies one or more Mailbox servers in the local Exchange organization to send test messages to. You can use any value that uniquely identifies the server. For example:
 
@@ -275,7 +275,7 @@ Accept wildcard characters: False
 
 ### -ActiveDirectoryTimeout
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ActiveDirectoryTimeout parameter specifies the number of seconds that elapse before the task provides an informational message about the delay. The default value is 15 seconds.
 
@@ -293,7 +293,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -314,7 +314,7 @@ Accept wildcard characters: False
 
 ### -CrossPremisesExpirationTimeout
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The CrossPremisesExpirationTimeout parameter is used when this cmdlet is run by Microsoft System Center Operations Manager 2007 agents for asynchronous monitoring. We don't recommend using this parameter when running this cmdlet manually.
 
@@ -332,7 +332,7 @@ Accept wildcard characters: False
 
 ### -CrossPremisesPendingErrorCount
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The CrossPremisesPendingErrorCount parameter is used when this cmdlet is run by System Center Operations Manager 2007 agents for asynchronous monitoring. We don't recommend using this parameter when running this cmdlet manually.
 
@@ -350,7 +350,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -368,7 +368,7 @@ Accept wildcard characters: False
 
 ### -ErrorLatency
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ErrorLatency parameter specifies how long to wait for a test message to be delivered before an error event is logged in Microsoft System Center Operations Manager 2007. The default value when a test message is sent to the local Mailbox server is 15 seconds and 180 seconds when a test message is sent to a remote Mailbox server.
 
@@ -386,7 +386,7 @@ Accept wildcard characters: False
 
 ### -ExecutionTimeout
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ExecutionTimeout parameter specifies the maximum time that this task can run before the test is determined to be a failure. If no test message or delivery report arrives before this time expires, the task ends and an error is reported. When the task is run in the Exchange Management Shell, the default setting is 240 seconds. When the MonitoringContext parameter is used, the default setting is 15 seconds.
 
@@ -404,7 +404,7 @@ Accept wildcard characters: False
 
 ### -MonitoringContext
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MonitoringContext parameter specifies whether to include the associated monitoring events and performance counters in the results. Valid values are:
 
@@ -425,7 +425,7 @@ Accept wildcard characters: False
 
 ### -TargetEmailAddressDisplayName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TargetEmailAddressDisplayName parameter specifies a custom display name that's used on events and reports in Microsoft System Center Operations Manager 2007 when the TargetEmailAddress parameter is used. If you don't use the TargetEmailAddressDisplayName parameter, the events and reports use the email address value specified by the TargetEmailAddress parameter.
 
@@ -445,7 +445,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-MigrationServerAvailability.md b/exchange/exchange-ps/ExchangePowerShell/Test-MigrationServerAvailability.md
index 083393ed0a..06819bf80a 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-MigrationServerAvailability.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-MigrationServerAvailability.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.ProvisioningAndMigration-Help.xml
 Locale: en-US
@@ -228,7 +228,7 @@ This example tests multiple existing endpoints.
 
 ### -Autodiscover
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Autodiscover switch specifies that the command should use the Autodiscover service to obtain the connection settings for the target server. You don't need to specify a value with this switch.
 
@@ -246,7 +246,7 @@ Accept wildcard characters: False
 
 ### -Compliance
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Compliance switch specifies that the endpoint type is compliance. You don't need to specify a value with this switch.
 
@@ -264,7 +264,7 @@ Accept wildcard characters: False
 
 ### -Credentials
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Credentials parameter specifies the username and password for an account that can access mailboxes on the target server. Specify the username in the domain\\username format or the user principal name (UPN) format (for example, `user@contoso.com`).
 
@@ -284,7 +284,7 @@ Accept wildcard characters: False
 
 ### -EmailAddress
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The EmailAddress parameter specifies the email address of an administrator account that can access the remote server. This parameter is required when you use the Autodiscover parameter.
 
@@ -302,7 +302,7 @@ Accept wildcard characters: False
 
 ### -Endpoint
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Endpoint parameter specifies the name of the migration endpoint to connect to. A migration endpoint contains the connection settings and other migration configuration settings. If you include this parameter, the Test-MigrationServerAvailability cmdlet attempts to verify the ability to connect to the remote server using the settings in the migration endpoint.
 
@@ -342,7 +342,7 @@ Accept wildcard characters: False
 
 ### -ExchangeRemoteMove
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ExchangeRemoteMove switch specifies a migration type where mailboxes are moved with full fidelity between two on-premises forests or between an on-premises forest and Exchange Online. You don't need to specify a value with this switch.
 
@@ -448,7 +448,7 @@ Accept wildcard characters: False
 
 ### -PSTImport
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -508,7 +508,7 @@ Accept wildcard characters: False
 
 ### -PublicFolderToUnifiedGroup
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The PublicFolderToUnifiedGroup switch specifies that the endpoint type is public folders to Microsoft 365 Groups. You don't need to specify a value with this switch.
 
@@ -526,7 +526,7 @@ Accept wildcard characters: False
 
 ### -RemoteServer
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The RemoteServer parameter specifies the FQDN of the on-premises mail server. This parameter is required when you want to perform one of the following migration types:
 
@@ -652,7 +652,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -673,7 +673,7 @@ Accept wildcard characters: False
 
 ### -FilePath
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The FilePath parameter specifies the path containing the PST files when testing a PST Import migration endpoint.
 
@@ -778,7 +778,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-OAuthConnectivity.md b/exchange/exchange-ps/ExchangePowerShell/Test-OAuthConnectivity.md
index 1b6bbe9634..3f06edf39c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-OAuthConnectivity.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-OAuthConnectivity.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -50,7 +50,7 @@ This example tests OAuth connectivity with Exchange for Gurinder Singh.
 
 ### -Service
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Service parameter specifies the partner application. Valid values for this parameter are:
 
@@ -72,7 +72,7 @@ Accept wildcard characters: False
 
 ### -TargetUri
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The TargetUri parameter specifies the URL for the service you want to test OAuth connectivity with.
 
@@ -90,7 +90,7 @@ Accept wildcard characters: False
 
 ### -AppOnly
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The AppOnly switch specifies the cmdlet authenticates to the specified service as Exchange without any user context. You don't need to specify a value with this switch.
 
@@ -108,7 +108,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -129,7 +129,7 @@ Accept wildcard characters: False
 
 ### -Mailbox
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Mailbox parameter specifies the mailbox for which you want to test OAuth connectivity to the specified partner application. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -158,7 +158,7 @@ Accept wildcard characters: False
 
 ### -ReloadConfig
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ReloadConfig switch reloads all the configuration settings from the Exchange configuration objects. You don't need to specify a value with this switch.
 
@@ -178,7 +178,7 @@ Accept wildcard characters: False
 
 ### -UseCachedToken
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The UseCachedToken switch specifies that OAuth tries to use an existing, cached authorization token. You don't need to specify a value with this switch.
 
@@ -196,7 +196,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-OrganizationRelationship.md b/exchange/exchange-ps/ExchangePowerShell/Test-OrganizationRelationship.md
index a0ebecd19c..7067d1c473 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-OrganizationRelationship.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-OrganizationRelationship.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
 Locale: en-US
@@ -49,7 +49,7 @@ This example validates the organization relationship deployed in the fabrikam.co
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the organization relationship to be tested. You can use the following values:
 
@@ -71,7 +71,7 @@ Accept wildcard characters: False
 
 ### -UserIdentity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The UserIdentity parameter specifies the mailbox for which a delegation token is requested to access the external organization's configuration information. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -96,7 +96,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -117,7 +117,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -137,7 +137,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-OutlookConnectivity.md b/exchange/exchange-ps/ExchangePowerShell/Test-OutlookConnectivity.md
index cb6b39db02..31fbe709a4 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-OutlookConnectivity.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-OutlookConnectivity.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -185,7 +185,7 @@ Accept wildcard characters: False
 
 ### -ProbeIdentity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ProbeIdentity parameter specifies the probe to use. Valid values are:
 
@@ -349,7 +349,7 @@ Accept wildcard characters: False
 
 ### -Credential
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Credential parameter specifies the credential used by the probe. The system's test credentials are used by default
 
@@ -369,7 +369,7 @@ Accept wildcard characters: False
 
 ### -Hostname
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 TheHostname parameter specifies the protocol endpoint target of the probe. You can use a specific Mailbox server or route through Distributed Name Service server.
 
@@ -409,7 +409,7 @@ Accept wildcard characters: False
 
 ### -MailboxId
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MailboxID parameter specifies the target mailbox.
 
@@ -573,7 +573,7 @@ Accept wildcard characters: False
 
 ### -RunFromServerId
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RunFromServerID parameter specifies the server on which the probe should be run.
 
@@ -591,7 +591,7 @@ Accept wildcard characters: False
 
 ### -TimeOutSeconds
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TimeOutSeconds parameter specifies the timeout period in seconds before the probe is ended. A valid value is an integer. The default value is 30 seconds.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-OutlookWebServices.md b/exchange/exchange-ps/ExchangePowerShell/Test-OutlookWebServices.md
index fab514e05d..5e75a7054c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-OutlookWebServices.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-OutlookWebServices.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -88,7 +88,7 @@ The example tests for a connection to each service. The example also submits a r
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies any valid address in the forest. If you specify this parameter, incorrectly formed addresses and addresses that are outside the forest are rejected. This address is used to test the Outlook provider. This property accepts the domain and username in the domain\\username format or an Active Directory GUID and resolves them to the SMTP address that's needed to authenticate.
 
@@ -106,7 +106,7 @@ Accept wildcard characters: False
 
 ### -AutoDiscoverServer
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AutoDiscoverServer parameter specifies the server with the Client Access server role installed that's used for Autodiscover.
 
@@ -133,7 +133,7 @@ Accept wildcard characters: False
 
 ### -ClientAccessServer
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is functional only in Exchange Server 2010.
 
@@ -162,7 +162,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -201,7 +201,7 @@ Accept wildcard characters: False
 
 ### -MailboxCredential
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MailboxCredential parameter specifies the mailbox credential to use for a single mailbox test.
 
@@ -221,7 +221,7 @@ Accept wildcard characters: False
 
 ### -MonitoringContext
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MonitoringContext parameter specifies whether to include the associated monitoring events and performance counters in the results. Valid values are:
 
@@ -260,7 +260,7 @@ Accept wildcard characters: False
 
 ### -TrustAnySSLCertificate
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TrustAnySSLCertificate switch allows Exchange to accept certificates from untrusted certification authorities (CAs). You don't need to specify a value with this switch.
 
@@ -280,7 +280,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-PopConnectivity.md b/exchange/exchange-ps/ExchangePowerShell/Test-PopConnectivity.md
index 7e5870d3cf..93b78565f1 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-PopConnectivity.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-PopConnectivity.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -81,7 +81,7 @@ This example tests the client POP3 connectivity of the specific server named Con
 
 ### -ClientAccessServer
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ClientAccessServer parameter specifies the Exchange server to test. This server has the Client Access server role installed and is responsible for accepting client connections.
 
@@ -106,7 +106,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -127,7 +127,7 @@ Accept wildcard characters: False
 
 ### -ConnectionType
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ConnectionType parameter specifies the type of connection that's used to connect to the POP3 service. Valid values are:
 
@@ -149,7 +149,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -167,7 +167,7 @@ Accept wildcard characters: False
 
 ### -LightMode
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The LightMode switch tells the command to perform only a test logon to the server by using the POP3 protocol. You don't need to specify a value with this switch.
 
@@ -187,7 +187,7 @@ Accept wildcard characters: False
 
 ### -MailboxCredential
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MailboxCredential parameter specifies the mailbox credential to use for a single mailbox test.
 
@@ -207,7 +207,7 @@ Accept wildcard characters: False
 
 ### -MailboxServer
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MailboxServer parameter specifies the Exchange Mailbox server that you want to test. This parameter identifies the backend server that accepts proxied connections from the frontend server where clients connect.
 
@@ -234,7 +234,7 @@ Accept wildcard characters: False
 
 ### -MonitoringContext
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MonitoringContext switch includes the associated monitoring events and performance counters in the results. You don't need to specify a value with this switch.
 
@@ -254,7 +254,7 @@ Accept wildcard characters: False
 
 ### -PerConnectionTimeout
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PerConnectionTimeout parameter specifies the amount of time, in seconds, to wait per connection for the test operation to finish. Valid values are between 0 and 120 seconds. The default value is 120 seconds.
 
@@ -274,7 +274,7 @@ Accept wildcard characters: False
 
 ### -PortClientAccessServer
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PortClientAccessServer parameter specifies the port to use to connect to the Client Access server. The default port is 110 for POP3. The valid range is from 0 through 65,535.
 
@@ -292,7 +292,7 @@ Accept wildcard characters: False
 
 ### -ResetTestAccountCredentials
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ResetTestAccountCredentials switch resets the password for the test account that's used to run this command. You don't need to specify a value with this switch.
 
@@ -312,7 +312,7 @@ Accept wildcard characters: False
 
 ### -Timeout
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Timeout parameter specifies the amount of time, in seconds, to wait for the test operation to finish. Valid values are between 0 and 3600 seconds (1 hour). The default value is 180 seconds (3 minutes).
 
@@ -332,7 +332,7 @@ Accept wildcard characters: False
 
 ### -TrustAnySSLCertificate
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TrustAnySSLCertificate switch allows Exchange to accept certificates from untrusted certification authorities (CAs). You don't need to specify a value with this switch.
 
@@ -352,7 +352,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-PowerShellConnectivity.md b/exchange/exchange-ps/ExchangePowerShell/Test-PowerShellConnectivity.md
index 45ec1f55f2..c0853084d2 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-PowerShellConnectivity.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-PowerShellConnectivity.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -97,7 +97,7 @@ The credentials that are used to connect to the virtual directory are stored in
 
 ### -ClientAccessServer
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ClientAccessServer parameter specifies the Exchange server to test. This server has the Client Access server role installed, and is responsible for accepting client connections.
 
@@ -124,7 +124,7 @@ Accept wildcard characters: False
 
 ### -ConnectionUri
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ConnectionUri parameter specifies the URL of the remote PowerShell virtual directory to test, for example, `https://contoso.com/powershell`.
 
@@ -144,7 +144,7 @@ Accept wildcard characters: False
 
 ### -TestCredential
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TestCredential parameter specifies the credentials to use for the test.
 
@@ -166,7 +166,7 @@ Accept wildcard characters: False
 
 ### -Authentication
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Authentication parameter specifies the type of authentication that's used to connect. Valid values are:
 
@@ -191,7 +191,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -212,7 +212,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -230,7 +230,7 @@ Accept wildcard characters: False
 
 ### -MailboxServer
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MailboxServer parameter specifies the Exchange Mailbox server that you want to test. This parameter identifies the backend server that accepts proxied connections from the frontend server where clients connect.
 
@@ -257,7 +257,7 @@ Accept wildcard characters: False
 
 ### -MonitoringContext
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MonitoringContext switch includes the associated monitoring events and performance counters in the results. You don't need to specify a value with this switch.
 
@@ -277,7 +277,7 @@ Accept wildcard characters: False
 
 ### -ResetTestAccountCredentials
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ResetTestAccountCredentials switch resets the password for the test account that's used to run this command. You don't need to specify a value with this switch.
 
@@ -297,7 +297,7 @@ Accept wildcard characters: False
 
 ### -TestType
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TestType parameter specifies whether the command tests internal or external URLs. Values are Internal and External. The default value is Internal.
 
@@ -317,7 +317,7 @@ Accept wildcard characters: False
 
 ### -TrustAnySSLCertificate
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TrustAnySSLCertificate switch allows Exchange to accept certificates from untrusted certification authorities (CAs). You don't need to specify a value with this switch.
 
@@ -337,7 +337,7 @@ Accept wildcard characters: False
 
 ### -VirtualDirectoryName
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The VirtualDirectoryName parameter specifies the name of the remote PowerShell virtual directory that you want to test. Enclose values that contain spaces in quotation marks (").
 
@@ -357,7 +357,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-ReplicationHealth.md b/exchange/exchange-ps/ExchangePowerShell/Test-ReplicationHealth.md
index 8e5467e89d..f57ca85a11 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-ReplicationHealth.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-ReplicationHealth.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -52,7 +52,7 @@ This example tests the health of replication for the Mailbox server MBX1.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the Mailbox server that you want to test. You can use any value that uniquely identifies the server. For example:
 
@@ -77,7 +77,7 @@ Accept wildcard characters: False
 
 ### -ActiveDirectoryTimeout
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ActiveDirectoryTimeout parameter specifies the time interval in seconds that's allowed for each directory service operation before the operation times out. The default value is 15 seconds.
 
@@ -95,7 +95,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -116,7 +116,7 @@ Accept wildcard characters: False
 
 ### -DatabaseAvailabilityGroup
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DatabaseAvailabilityGroup parameter specifies whether to test all servers in the specified DAG. You can use any value that uniquely identifies the DAG. For example:
 
@@ -140,7 +140,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -158,7 +158,7 @@ Accept wildcard characters: False
 
 ### -MonitoringContext
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MonitoringContext parameter specifies whether to include the associated monitoring events and performance counters in the results. Valid values are:
 
@@ -179,7 +179,7 @@ Accept wildcard characters: False
 
 ### -OutputObjects
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The OutputObjects switch specifies whether to output an array of information regarding failures. You don't need to specify a value with this switch.
 
@@ -197,7 +197,7 @@ Accept wildcard characters: False
 
 ### -TransientEventSuppressionWindow
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TransientEventSuppressionWindow parameter specifies the number of minutes that the queue lengths can be exceeded before the queue length tests are considered to have failed. This parameter is used to reduce the number of failures due to transient load generation.
 
@@ -215,7 +215,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-SenderId.md b/exchange/exchange-ps/ExchangePowerShell/Test-SenderId.md
index d60fe06337..7ea8aad67f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-SenderId.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-SenderId.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailControl-Help.xml
 Locale: en-US
@@ -49,7 +49,7 @@ This example checks whether the IP address 192.168.0.1 is the legitimate sender
 
 ### -IPAddress
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IPAddress parameter specifies the originating IP address of the sending server.
 
@@ -67,7 +67,7 @@ Accept wildcard characters: False
 
 ### -PurportedResponsibleDomain
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The PurportedResponsibleDomain parameter specifies the domain name that you want to verify with Sender ID.
 
@@ -85,7 +85,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -106,7 +106,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -126,7 +126,7 @@ Accept wildcard characters: False
 
 ### -HelloDomain
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The HelloDomain parameter specifies the domain address displayed in the HELO or EHLO SMTP commands from this sender.
 
@@ -144,7 +144,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
 
@@ -169,7 +169,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-ServiceHealth.md b/exchange/exchange-ps/ExchangePowerShell/Test-ServiceHealth.md
index 833a0a50b2..e9aa727121 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-ServiceHealth.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-ServiceHealth.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -49,7 +49,7 @@ This example uses the Test-ServiceHealth command without parameters to test the
 
 ### -Server
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifies the server. For example:
 
@@ -74,7 +74,7 @@ Accept wildcard characters: False
 
 ### -ActiveDirectoryTimeout
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ActiveDirectoryTimeout parameter specifies the amount of time, in seconds, allowed for each Active Directory operation to complete before the operation times out. The default value is 15 seconds.
 
@@ -92,7 +92,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -113,7 +113,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -133,7 +133,7 @@ Accept wildcard characters: False
 
 ### -MonitoringContext
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MonitoringContext parameter specifies whether to include the associated monitoring events and performance counters in the results. Valid values are:
 
@@ -154,7 +154,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-SiteMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Test-SiteMailbox.md
index 8620f8cc97..20760ca321 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-SiteMailbox.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-SiteMailbox.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -66,7 +66,7 @@ This example tests a specific user's ability to access a SharePoint site by usin
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the site mailbox that you want to test. You can use any value that uniquely identifies the site mailbox. For example:
 
@@ -93,7 +93,7 @@ Accept wildcard characters: False
 
 ### -BypassOwnerCheck
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The BypassOwnerCheck parameter is used when the account that's running the command isn't a member or owner of the site mailbox. You don't need to specify a value with this switch.
 
@@ -113,7 +113,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -134,7 +134,7 @@ Accept wildcard characters: False
 
 ### -RequestorIdentity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The RequestorIdentity parameter specifies the user to test for correct permissions to the SharePoint site mailbox. You can use any value that uniquely identifies the user. For example:
 
@@ -163,7 +163,7 @@ Accept wildcard characters: False
 
 ### -SharePointUrl
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SharePointUrl parameter specifies the SharePoint URL where the site mailbox is hosted, for example, "https://myserver/teams/edu".
 
@@ -183,7 +183,7 @@ Accept wildcard characters: False
 
 ### -UseAppTokenOnly
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The UseAppTokenOnly switch specifies that you want to test the site mailbox by using the identity of the Exchange server. You don't need to specify a value with this switch.
 
@@ -203,7 +203,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-SmtpConnectivity.md b/exchange/exchange-ps/ExchangePowerShell/Test-SmtpConnectivity.md
index 5ad4bb647f..29e06a7f1e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-SmtpConnectivity.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-SmtpConnectivity.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -64,7 +64,7 @@ This example verifies SMTP connectivity for all Receive connectors on all Mailbo
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the transport server for which the cmdlet verifies SMTP connectivity .
 
@@ -91,7 +91,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -112,7 +112,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -132,7 +132,7 @@ Accept wildcard characters: False
 
 ### -MonitoringContext
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MonitoringContext parameter specifies whether to include the associated monitoring events and performance counters in the results. Valid values are:
 
@@ -153,7 +153,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-TextExtraction.md b/exchange/exchange-ps/ExchangePowerShell/Test-TextExtraction.md
index e22bd0b9d2..3327ccacd5 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-TextExtraction.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-TextExtraction.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance
+applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -60,7 +60,7 @@ This example extracts the text from the email message file named "financial data
 
 ### -FileData
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance
 
 The FileData parameter specifies the name and path of the file from which text should be extracted.
 
@@ -80,7 +80,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -101,7 +101,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance
 
 This parameter is available only in on-premises Exchange.
 
@@ -121,7 +121,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-WebServicesConnectivity.md b/exchange/exchange-ps/ExchangePowerShell/Test-WebServicesConnectivity.md
index c156db20d0..6e29d4210f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Test-WebServicesConnectivity.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Test-WebServicesConnectivity.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RemoteConnections-Help.xml
 Locale: en-US
@@ -111,7 +111,7 @@ This example tests the client connection to Exchange Web Services on the server
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the mailbox to use for the test. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -142,7 +142,7 @@ Accept wildcard characters: False
 
 ### -ClientAccessServer
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ClientAccessServer parameter specifies the Exchange server to test. This server has the Client Access server role installed, and is responsible for accepting client connections.
 
@@ -169,7 +169,7 @@ Accept wildcard characters: False
 
 ### -AutoDiscoverServer
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The AutoDiscoverServer parameter specifies the server with the Client Access server role installed that's used for Autodiscover.
 
@@ -216,7 +216,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -257,7 +257,7 @@ Accept wildcard characters: False
 
 ### -LightMode
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The LightMode switch tells the command to perform only a subset of the tests. You don't need to specify a value with this switch.
 
@@ -277,7 +277,7 @@ Accept wildcard characters: False
 
 ### -MailboxCredential
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MailboxCredential parameter specifies the mailbox credential to use for a single mailbox test.
 
@@ -317,7 +317,7 @@ Accept wildcard characters: False
 
 ### -MonitoringContext
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MonitoringContext switch includes the associated monitoring events and performance counters in the results. You don't need to specify a value with this switch.
 
@@ -375,7 +375,7 @@ Accept wildcard characters: False
 
 ### -TrustAnySSLCertificate
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TrustAnySSLCertificate switch allows Exchange to accept certificates from untrusted certification authorities (CAs). You don't need to specify a value with this switch.
 
@@ -415,7 +415,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Uninstall-TransportAgent.md b/exchange/exchange-ps/ExchangePowerShell/Uninstall-TransportAgent.md
index c4dbca1080..16b4f889f2 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Uninstall-TransportAgent.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Uninstall-TransportAgent.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailflow-Help.xml
 Locale: en-US
@@ -52,7 +52,7 @@ This example uninstalls a fictitious application named Test App from the Transpo
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the display name of the transport agent that you want to uninstall. If the value contains spaces, enclose the value in quotation marks.
 
@@ -70,7 +70,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -91,7 +91,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -111,7 +111,7 @@ Accept wildcard characters: False
 
 ### -TransportService
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The TransportService parameter specifies the transport service that you want to view or modify. Valid values for this parameter are:
 
@@ -135,7 +135,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Update-AddressList.md b/exchange/exchange-ps/ExchangePowerShell/Update-AddressList.md
index b9d2e639b6..82e016cadf 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Update-AddressList.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Update-AddressList.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -45,7 +45,7 @@ This example updates the recipients of the address list named building4 that's u
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the address list that you want to update. You can use any value that uniquely identifies the address list. For example:
 
@@ -68,7 +68,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -89,7 +89,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -107,7 +107,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Update-DatabaseSchema.md b/exchange/exchange-ps/ExchangePowerShell/Update-DatabaseSchema.md
index 28b74be06b..57d4333d3b 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Update-DatabaseSchema.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Update-DatabaseSchema.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -44,7 +44,7 @@ This example updates the database schema for database DB1.
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the mailbox database for which you want to set one or more attributes. You can use any value that uniquely identifies the database. For example:
 
@@ -66,7 +66,7 @@ Accept wildcard characters: False
 
 ### -MajorVersion
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -84,7 +84,7 @@ Accept wildcard characters: False
 
 ### -MinorVersion
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -102,7 +102,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -123,7 +123,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Update-DistributionGroupMember.md b/exchange/exchange-ps/ExchangePowerShell/Update-DistributionGroupMember.md
index 77501dbf64..14bace8d2f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Update-DistributionGroupMember.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Update-DistributionGroupMember.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.CalendarsAndGroups-Help.xml
 Locale: en-US
@@ -47,7 +47,7 @@ This example replaces the existing members of the distribution group name Resear
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Identity parameter specifies the distribution group or mail-enabled security group that you want to modify. You can use any value that uniquely identifies the group. For example:
 
@@ -72,7 +72,7 @@ Accept wildcard characters: False
 
 ### -BypassSecurityGroupManagerCheck
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The BypassSecurityGroupManagerCheck switch specifies whether to allow a user who isn't an owner of the group to modify or delete the group. You don't need to specify a value with this switch.
 
@@ -95,7 +95,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -116,7 +116,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -136,7 +136,7 @@ Accept wildcard characters: False
 
 ### -Members
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Members parameter specifies the recipients (mail-enabled objects) that replace the current group members. You can use any value that uniquely identifies the recipient. For example:
 
@@ -167,7 +167,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Update-EmailAddressPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Update-EmailAddressPolicy.md
index c93914c149..ee26653d15 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Update-EmailAddressPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Update-EmailAddressPolicy.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -47,7 +47,7 @@ This example applies the email address policy named Northwest Executives to all
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the email address policy that you want to apply to recipients. You can use any value that uniquely identifies the policy. For example:
 
@@ -69,7 +69,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -90,7 +90,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -108,7 +108,7 @@ Accept wildcard characters: False
 
 ### -FixMissingAlias
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The FixMissingAlias switch repairs recipients that don't have an alias. The alias is generated based on the Name property of the recipient. You don't need to specify a value with this switch.
 
@@ -128,7 +128,7 @@ Accept wildcard characters: False
 
 ### -UpdateSecondaryAddressesOnly
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The UpdateSecondaryAddressesOnly switch specifies that only the proxy email addresses are updated for the recipients. You don't need to specify a value with this switch.
 
@@ -148,7 +148,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Update-ExchangeHelp.md b/exchange/exchange-ps/ExchangePowerShell/Update-ExchangeHelp.md
index 9c99530bbe..2b5969d380 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Update-ExchangeHelp.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Update-ExchangeHelp.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -46,7 +46,7 @@ This example checks for the latest available version of Help for the Exchange Ma
 
 ### -Force
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Update-GlobalAddressList.md b/exchange/exchange-ps/ExchangePowerShell/Update-GlobalAddressList.md
index 4a98c2846a..a5ac3dd34c 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Update-GlobalAddressList.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Update-GlobalAddressList.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -45,7 +45,7 @@ This example updates the recipients in the default GAL.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the global address list that you want to update. You can use any value that uniquely identifies the GAL. For example:
 
@@ -67,7 +67,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -88,7 +88,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -106,7 +106,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Update-HybridConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Update-HybridConfiguration.md
index 32694c56bb..f5c22913e3 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Update-HybridConfiguration.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Update-HybridConfiguration.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -57,7 +57,7 @@ Use the last command to define the credentials that are used to update the hybri
 
 ### -OnPremisesCredentials
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The OnPremisesCredentials parameter specifies the on-premises Active Directory account and password that's used to configure the hybrid configuration object. This account must be a member of the Organization Management role group.
 
@@ -77,7 +77,7 @@ Accept wildcard characters: False
 
 ### -TenantCredentials
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The TenantCredentials parameter specifies the Microsoft 365 organization account and password that's used to configure the hybrid configuration object. This is often the administrator account that's assigned when the Microsoft 365 organization was created. This account must be a member of the Global Administrators role.
 
@@ -100,7 +100,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -121,7 +121,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -141,7 +141,7 @@ Accept wildcard characters: False
 
 ### -ForceUpgrade
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ForceUpgrade switch suppresses the confirmation message that appears if the object was created in a previous version of Exchange. You don't need to specify a value with this switch.
 
@@ -161,7 +161,7 @@ Accept wildcard characters: False
 
 ### -SuppressOAuthWarning
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 This parameter is reserved for internal Microsoft use.
 
@@ -179,7 +179,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Update-MailboxDatabaseCopy.md b/exchange/exchange-ps/ExchangePowerShell/Update-MailboxDatabaseCopy.md
index 67ea153698..0e94dc981e 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Update-MailboxDatabaseCopy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Update-MailboxDatabaseCopy.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.ServerStatus-Help.xml
 Locale: en-US
@@ -123,7 +123,7 @@ This example performs a full server reseed of all of the databases on the Mailbo
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the name or GUID of the mailbox database whose copy is being seeded.
 
@@ -141,7 +141,7 @@ Accept wildcard characters: False
 
 ### -CancelSeed
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The CancelSeed switch specifies whether to cancel an in-progress seeding operation. You don't need to specify a value with this switch.
 
@@ -159,7 +159,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter is used as part of a full server reseed operation. It can be used with the MaximumSeedsInParallel parameter to start reseeds of database copies in parallel across the specified server in batches of up to the value of the MaximumSeedsInParallel parameter copies at a time.
 
@@ -177,7 +177,7 @@ Accept wildcard characters: False
 
 ### -BeginSeed
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The BeginSeed switch asynchronously starts the seeding operation and then exits the cmdlet. You don't need to specify a value with this switch.
 
@@ -197,7 +197,7 @@ Accept wildcard characters: False
 
 ### -CatalogOnly
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The CatalogOnly switch specifies that only the content index catalog for the database copy should be seeded. You don't need to specify a value with this switch.
 
@@ -215,7 +215,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -236,7 +236,7 @@ Accept wildcard characters: False
 
 ### -DatabaseOnly
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DatabaseOnly switch specifies that only the database copy should be seeded. The content index catalog isn't seeded. You don't need to specify a value with this switch.
 
@@ -254,7 +254,7 @@ Accept wildcard characters: False
 
 ### -DeleteExistingFiles
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DeleteExistingFiles switch specifies whether to remove the existing log files at the target location. You don't need to specify a value with this switch.
 
@@ -274,7 +274,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -292,7 +292,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -312,7 +312,7 @@ Accept wildcard characters: False
 
 ### -ManualResume
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The ManualResume switch specifies whether to automatically resume replication on the database copy. You don't need to specify a value with this switch.
 
@@ -332,7 +332,7 @@ Accept wildcard characters: False
 
 ### -MaximumSeedsInParallel
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The MaximumSeedsInParallel parameter is used with the Server parameter to specify the maximum number of parallel seeding operations that should occur across the specified server during a full server reseed operation. The default value is 10.
 
@@ -350,7 +350,7 @@ Accept wildcard characters: False
 
 ### -Network
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Network parameter specifies which DAG network should be used for seeding. Content index catalog seeding always occurs over the MAPI network, even if you use this parameter to specify the DAG network.
 
@@ -368,7 +368,7 @@ Accept wildcard characters: False
 
 ### -NetworkCompressionOverride
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The NetworkCompressionOverride parameter specifies whether to override the current DAG network compression settings.
 
@@ -386,7 +386,7 @@ Accept wildcard characters: False
 
 ### -NetworkEncryptionOverride
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The NetworkEncryptionOverride parameter specifies whether to override the current DAG encryption settings.
 
@@ -404,7 +404,7 @@ Accept wildcard characters: False
 
 ### -NoThrottle
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The NoThrottle switch prevents the seeding operation from being throttled. You don't need to specify a value with this switch.
 
@@ -422,7 +422,7 @@ Accept wildcard characters: False
 
 ### -PrimaryDatabasePartitionOnly
 
-> Applicable: Exchange Server 2019
+> Applicable: Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -440,7 +440,7 @@ Accept wildcard characters: False
 
 ### -SafeDeleteExistingFiles
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SafeDeleteExistingFiles switch specifies a seeding operation with a single copy redundancy pre-check prior to the seed. You don't need to specify a value with this switch.
 
@@ -460,7 +460,7 @@ Accept wildcard characters: False
 
 ### -SecondaryDatabasePartitionOnly
 
-> Applicable: Exchange Server 2019
+> Applicable: Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -478,7 +478,7 @@ Accept wildcard characters: False
 
 ### -SourceServer
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The SourceServer parameter specifies the Mailbox server with a passive copy of the mailbox database to be used as the source for the seed operation.
 
@@ -503,7 +503,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Update-OfflineAddressBook.md b/exchange/exchange-ps/ExchangePowerShell/Update-OfflineAddressBook.md
index a3de0ee78b..7b0a285910 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Update-OfflineAddressBook.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Update-OfflineAddressBook.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -46,7 +46,7 @@ This example updates the OAB MyOAB.
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the GUID, distinguished name (DN), or OAB name that represents a specific OAB. You can also include the path by using the format Server\\OfflineAddressBookName.
 
@@ -66,7 +66,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -87,7 +87,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -105,7 +105,7 @@ Accept wildcard characters: False
 
 ### -Force
 
-> Applicable: Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch.
 
@@ -125,7 +125,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Update-PublicFolderMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Update-PublicFolderMailbox.md
index 0b48213ae6..41d8f95ea9 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Update-PublicFolderMailbox.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Update-PublicFolderMailbox.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.WebClient-Help.xml
 Locale: en-US
@@ -70,7 +70,7 @@ This example updates all public folder mailboxes.
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the public folder mailbox that you want to update. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -99,7 +99,7 @@ Accept wildcard characters: False
 
 ### -FolderId
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The FolderId parameter specifies the GUID or name of the public folder that you want to synchronize. You can also include the path using the format \\TopLevelPublicFolder\\PublicFolder.
 
@@ -117,7 +117,7 @@ Accept wildcard characters: False
 
 ### -InvokeSynchronizer
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The InvokeSynchronizer switch can only be used on secondary hierarchy public folder mailboxes and triggers hierarchy synchronization from the primary public folder mailbox to the specified secondary public folder mailbox. You don't need to specify a value with this switch.
 
@@ -137,7 +137,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -158,7 +158,7 @@ Accept wildcard characters: False
 
 ### -CreateAssociatedDumpster
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The CreateAssociatedDumpster switch specifies whether to create the associated dumpster before synchronizing the folder. You don't need to specify a value with this switch.
 
@@ -176,7 +176,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -196,7 +196,7 @@ Accept wildcard characters: False
 
 ### -ForceOnlineSync
 
-> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ForceOnlineSync switch specifies whether to force the secondary public folder mailbox to synchronize with the primary public folder mailbox. You don't need to specify a value with this switch.
 
@@ -214,7 +214,7 @@ Accept wildcard characters: False
 
 ### -FullSync
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The FullSync switch specifies that you want to perform a full synchronization of the public folder mailbox. You don't need to specify a value with this switch.
 
@@ -232,7 +232,7 @@ Accept wildcard characters: False
 
 ### -ReconcileFolders
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The ReconcileFolders switch specifies whether to look closely for differences in the folder hierarchy between the primary public folder mailbox and the secondary public folder mailbox. Folders that exist in the primary public folder mailbox and not in the secondary are recreated. You don't need to specify a value with this switch.
 
@@ -266,7 +266,7 @@ Accept wildcard characters: False
 
 ### -SuppressStatus
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The SuppressStatus switch specifies that the output of this cmdlet is suppressed and that the command runs asynchronously in the background from the Exchange Management Shell. You don't need to specify a value with this switch.
 
@@ -288,7 +288,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Update-Recipient.md b/exchange/exchange-ps/ExchangePowerShell/Update-Recipient.md
index df0c783950..1da8470535 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Update-Recipient.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Update-Recipient.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -59,7 +59,7 @@ In on-premises Exchange, this example updates all contacts in a specific organiz
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Identity parameter specifies the recipient that you want to update. You can use any value that uniquely identifies the recipient. For example:
 
@@ -84,7 +84,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -105,7 +105,7 @@ Accept wildcard characters: False
 
 ### -Credential
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The Credential parameter specifies the username and password to use to access Active Directory.
 
@@ -125,7 +125,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The parameter is available only in on-premises Exchange.
 
@@ -145,7 +145,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Update-RoleGroupMember.md b/exchange/exchange-ps/ExchangePowerShell/Update-RoleGroupMember.md
index c9a3ecf00f..d1c9b5f696 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Update-RoleGroupMember.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Update-RoleGroupMember.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -77,7 +77,7 @@ Mail-enabled security group: If you want to add or remove a mail-enabled securit
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The Identity parameter specifies the role group whose membership you want to modify. If the name of the role group contains spaces, enclose the name in quotation marks (").
 
@@ -95,7 +95,7 @@ Accept wildcard characters: False
 
 ### -BypassSecurityGroupManagerCheck
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The BypassSecurityGroupManagerCheck switch specifies whether to allow a user who isn't an owner of the group to modify or delete the group. You don't need to specify a value with this switch.
 
@@ -118,7 +118,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -139,7 +139,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -159,7 +159,7 @@ Accept wildcard characters: False
 
 ### -Members
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The Members parameter specifies the mailboxes or mail-enabled USGs to add as a member of the role group. You can identify the user or group by the name, DN, or primary SMTP address value. You can specify multiple members separated by commas (`Value1,Value2,...ValueN`). If the value contains spaces, enclose the value in quotation marks (`"Value 1","Value 2",..."Value N"`).
 
@@ -179,7 +179,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Security & Compliance, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Security & Compliance, Exchange Online Protection
 
 The WhatIf switch doesn't work in Security & Compliance PowerShell.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Update-SafeList.md b/exchange/exchange-ps/ExchangePowerShell/Update-SafeList.md
index 9317fb9dd9..da2acef985 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Update-SafeList.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Update-SafeList.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.TransportMailControl-Help.xml
 Locale: en-US
@@ -61,7 +61,7 @@ This example updates safelist data for all user mailboxes in your Exchange organ
 
 ### -Identity
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the mailbox from which you want to collect safelist aggregation data. You can use any value that uniquely identifies the mailbox. For example:
 
@@ -90,7 +90,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -111,7 +111,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.
 
@@ -129,7 +129,7 @@ Accept wildcard characters: False
 
 ### -EnsureJunkEmailRule
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The EnsureJunkEmailRule switch forces the junk email rule to be turned on for the mailbox if the rule isn't turned on already. You don't need to specify a value with this switch.
 
@@ -149,7 +149,7 @@ Accept wildcard characters: False
 
 ### -IncludeDomains
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The IncludeDomains switch specifies whether to include the sender domains specified by users in Outlook in the safelist aggregation data. You don't need to specify a value with this switch.
 
@@ -171,7 +171,7 @@ Accept wildcard characters: False
 
 ### -Type
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Type parameter specifies which user-generated list is updated to the user object. Valid values for this parameter are SafeSenders, SafeRecipients, and Both. The default value is SafeSenders.
 
@@ -191,7 +191,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Update-SiteMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Update-SiteMailbox.md
index 36d54dd832..66e33b2771 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Update-SiteMailbox.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Update-SiteMailbox.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -60,7 +60,7 @@ This example updates the site mailbox WinterHoliday@tailspintoys.com and perform
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the site mailbox that you want to update. You can use any value that uniquely identifies the site mailbox. For example:
 
@@ -85,7 +85,7 @@ Accept wildcard characters: False
 
 ### -BypassOwnerCheck
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The BypassOwnerCheck parameter is used when the account that's running the command isn't a member or owner of the site mailbox. You don't need to specify a value with this switch.
 
@@ -105,7 +105,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -126,7 +126,7 @@ Accept wildcard characters: False
 
 ### -FullSync
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The FullSync switch specifies a full synchronization. You don't need to specify a value with this switch.
 
@@ -146,7 +146,7 @@ Accept wildcard characters: False
 
 ### -Organization
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is reserved for internal Microsoft use.
 
@@ -164,7 +164,7 @@ Accept wildcard characters: False
 
 ### -Server
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Server parameter specifies the fully qualified domain name (FQDN) or the Microsoft SharePoint server on which the site mailbox is located.
 
@@ -182,7 +182,7 @@ Accept wildcard characters: False
 
 ### -Target
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Target parameter specifies whether to update the SharePoint documents, the site mailbox's membership list or both. This parameter accepts the following values:
 
@@ -206,7 +206,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Update-StoreMailboxState.md b/exchange/exchange-ps/ExchangePowerShell/Update-StoreMailboxState.md
index 8c97f75874..58865bb16f 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Update-StoreMailboxState.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Update-StoreMailboxState.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 author: chrisda
 external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
 Locale: en-US
@@ -60,7 +60,7 @@ This example updates the mailbox state for all disconnected mailboxes on the mai
 
 ### -Database
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Database parameter specifies the mailbox database that contains the mailbox. You can use any value that uniquely identifies the database. For example:
 
@@ -82,7 +82,7 @@ Accept wildcard characters: False
 
 ### -Identity
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Identity parameter specifies the mailbox that you want to update. Use the mailbox GUID as the value for this parameter.
 
@@ -102,7 +102,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -123,7 +123,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/ExchangePowerShell/Write-AdminAuditLog.md b/exchange/exchange-ps/ExchangePowerShell/Write-AdminAuditLog.md
index c4eb0f5b84..1d92073322 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Write-AdminAuditLog.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Write-AdminAuditLog.md
@@ -1,5 +1,5 @@
 ---
-applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 author: chrisda
 external help file: Microsoft.Exchange.RecordsandEdge-Help.xml
 Locale: en-US
@@ -49,7 +49,7 @@ This example adds a comment to the administrator audit log.
 
 ### -Comment
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Comment parameter specifies the comment to add to the administrator audit log. The maximum length is 500 characters.
 
@@ -69,7 +69,7 @@ Accept wildcard characters: False
 
 ### -Confirm
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
 
@@ -90,7 +90,7 @@ Accept wildcard characters: False
 
 ### -DomainController
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE
 
 This parameter is available only in on-premises Exchange.
 
@@ -110,7 +110,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection
+> Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection
 
 The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
 

From 1c1715ae7698bbcd8c9977b64858ccb2cd950474 Mon Sep 17 00:00:00 2001
From: bwinzenz <38508824+bwinzenz@users.noreply.github.com>
Date: Fri, 8 Aug 2025 10:55:14 -0500
Subject: [PATCH 137/145] Update Set-CalendarProcessing.md

Adding more context to AutoUpdate and AutoAccept as some people don't seem to understand that if Rooms are not configured with AutoAccept, RBA will not process messages and they will not be forwarded to Resource Delegates.
---
 .../exchange-ps/ExchangePowerShell/Set-CalendarProcessing.md  | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-CalendarProcessing.md b/exchange/exchange-ps/ExchangePowerShell/Set-CalendarProcessing.md
index 2412c29cdc..f9c4977228 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-CalendarProcessing.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-CalendarProcessing.md
@@ -388,8 +388,8 @@ Accept wildcard characters: False
 The AutomateProcessing parameter enables or disables calendar processing on the mailbox. Valid values are:
 
 - None: Calendar processing is disabled on the mailbox. Both the resource booking attendant and the Calendar Attendant are disabled on the mailbox.
-- AutoUpdate: Only the Calendar Attendant processes meeting requests and responses. Meeting requests are tentative in the calendar until they're approved by a delegate. Meeting organizers receive only decisions from delegates.
-- AutoAccept: Both the Calendar Attendant and resource booking attendant are enabled on the mailbox. This means that the Calendar Attendant updates the calendar, and then the resource booking assistant accepts the meeting based upon the policies. Eligible meeting organizers receive the decision directly without human intervention (free = accept; busy = decline).
+- AutoUpdate: Only the Calendar Attendant processes meeting requests and responses. Meeting requests are tentative in the calendar until they're approved by a delegate. Meeting organizers receive only decisions from delegates. Note: If a Room mailbox is set to AutoUpdate, ResourceDelegates will not be forwarded requests.
+- AutoAccept: Both the Calendar Attendant and resource booking attendant are enabled on the mailbox. This means that the Calendar Attendant updates the calendar, and then the resource booking assistant accepts the meeting based upon the policies. If AllBookInPolicy or BookInPolicy are configured, Eligible meeting organizers receive the decision directly without human intervention (free = accept; busy = decline). If AllRequestInPolicy or RequestInPolicy are configured and ForwardRequestsToDelegates is True, then meeting requests are forwarded to the Resource delegates for approval. Additionally, other resource-specific settings such as DeleteSubject, AddOrganizerToSubject, DeleteComments, etc. are evaluated.
 
 In on-premises Exchange, resource mailboxes created in the Exchange admin center (EAC) have the default value AutoAccept, while resource mailboxes created in PowerShell have the default value AutoUpdate.
 

From 75d215cb076d9311805bd2812a84e74afe96b266 Mon Sep 17 00:00:00 2001
From: Chris Davis <chris.davis@microsoft.com>
Date: Fri, 8 Aug 2025 10:19:00 -0700
Subject: [PATCH 138/145] Update Set-CalendarProcessing.md

---
 .../exchange-ps/ExchangePowerShell/Set-CalendarProcessing.md  | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-CalendarProcessing.md b/exchange/exchange-ps/ExchangePowerShell/Set-CalendarProcessing.md
index f9c4977228..c17075c1cd 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-CalendarProcessing.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-CalendarProcessing.md
@@ -388,8 +388,8 @@ Accept wildcard characters: False
 The AutomateProcessing parameter enables or disables calendar processing on the mailbox. Valid values are:
 
 - None: Calendar processing is disabled on the mailbox. Both the resource booking attendant and the Calendar Attendant are disabled on the mailbox.
-- AutoUpdate: Only the Calendar Attendant processes meeting requests and responses. Meeting requests are tentative in the calendar until they're approved by a delegate. Meeting organizers receive only decisions from delegates. Note: If a Room mailbox is set to AutoUpdate, ResourceDelegates will not be forwarded requests.
-- AutoAccept: Both the Calendar Attendant and resource booking attendant are enabled on the mailbox. This means that the Calendar Attendant updates the calendar, and then the resource booking assistant accepts the meeting based upon the policies. If AllBookInPolicy or BookInPolicy are configured, Eligible meeting organizers receive the decision directly without human intervention (free = accept; busy = decline). If AllRequestInPolicy or RequestInPolicy are configured and ForwardRequestsToDelegates is True, then meeting requests are forwarded to the Resource delegates for approval. Additionally, other resource-specific settings such as DeleteSubject, AddOrganizerToSubject, DeleteComments, etc. are evaluated.
+- AutoUpdate: Only the Calendar Attendant processes meeting requests and responses. Meeting requests are tentative in the calendar until approval by a delegate. Meeting organizers receive only decisions from delegates. **Note**: If you set this value on a room mailbox, delegates don't get requests.
+- AutoAccept: Both the Calendar Attendant and resource booking attendant are enabled on the mailbox. The Calendar Attendant updates the calendar, and then the resource booking assistant accepts the meeting based upon the policies. If AllBookInPolicy or BookInPolicy are configured, eligible meeting organizers receive the decision directly without human intervention (free = accept; busy = decline). If AllRequestInPolicy or RequestInPolicy are configured and the ForwardRequestsToDelegates value is True, meeting requests are forwarded to delegates for approval. Other resource-specific settings (for example, DeleteSubject, AddOrganizerToSubject, DeleteComments, etc.) are also evaluated.
 
 In on-premises Exchange, resource mailboxes created in the Exchange admin center (EAC) have the default value AutoAccept, while resource mailboxes created in PowerShell have the default value AutoUpdate.
 

From b1440959e18dc16f3c68fce1e9a99bbc644759b2 Mon Sep 17 00:00:00 2001
From: Chris Davis <chris.davis@microsoft.com>
Date: Fri, 8 Aug 2025 12:03:21 -0700
Subject: [PATCH 139/145] Update Set-SafeLinksPolicy.md

---
 exchange/exchange-ps/ExchangePowerShell/Set-SafeLinksPolicy.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-SafeLinksPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-SafeLinksPolicy.md
index 828b4ef04b..b14a396945 100644
--- a/exchange/exchange-ps/ExchangePowerShell/Set-SafeLinksPolicy.md
+++ b/exchange/exchange-ps/ExchangePowerShell/Set-SafeLinksPolicy.md
@@ -166,7 +166,7 @@ Accept wildcard characters: False
 
 The DeliverMessageAfterScan parameter specifies whether to deliver email messages only after Safe Links scanning is complete. Valid values are:
 
-- $true: Wait until Safe Links scanning is complete before delivering the message. This value is the default. Messages that contain malicious links are not delivered.
+- $true: Wait until Safe Links scanning is complete before delivering the message. Messages that contain malicious links are not delivered. This value is the default.
 - $false: If Safe Links scanning can't complete, deliver the message anyway.
 
 ```yaml

From c5f39995a7a943ce9caef5a82640c7a7f6b5da32 Mon Sep 17 00:00:00 2001
From: Chris Davis <chris.davis@microsoft.com>
Date: Fri, 8 Aug 2025 17:18:03 -0700
Subject: [PATCH 140/145] Update exchange-online-powershell-v2.md

Windows version updates
---
 .../exchange-online-powershell-v2.md          | 76 +++++++++++++++----
 1 file changed, 60 insertions(+), 16 deletions(-)

diff --git a/exchange/docs-conceptual/exchange-online-powershell-v2.md b/exchange/docs-conceptual/exchange-online-powershell-v2.md
index 0f362ffe35..38b1cbcba7 100644
--- a/exchange/docs-conceptual/exchange-online-powershell-v2.md
+++ b/exchange/docs-conceptual/exchange-online-powershell-v2.md
@@ -3,7 +3,7 @@ title: About the Exchange Online PowerShell V3 module
 ms.author: chrisda
 author: chrisda
 manager: deniseb
-ms.date: 07/31/2025
+ms.date: 08/08/2025
 ms.audience: Admin
 audience: Admin
 ms.topic: article
@@ -269,28 +269,70 @@ Now you can do the [regular PowerShell prerequisites](#prerequisites-for-the-exc
 
 - **Windows PowerShell 5.1**:
   - All versions of the module are supported.
-  - Version 2.0.5 (May 2021) or later versions of the module require the Microsoft .NET Framework 4.7.2 or later to connect. Otherwise, you get a `System.Runtime.InteropServices.OSPlatform` error. For more information about versions of Windows that support the .NET Framework 4.7.2, see [this article](/dotnet/framework/migration-guide/versions-and-dependencies#net-framework-472).
-
-  > [!TIP]
-  > Current versions of Windows include the required versions of .NET and/or the .NET Framework, so you don't need to install .NET or the .NET Framework to use the module in Windows PowerShell 5.1.
+  - Current versions of Windows include the required versions of the .NET Framework, so you don't need to install the .NET Framework to use the module in Windows PowerShell 5.1.
 
 - **PowerShell 7**:
   - Module versions 3.5.1 (July 2024) or later require PowerShell 7 version 7.4.0 (November 2023) or later. Earlier versions of PowerShell 7 might encounter compatibility issues due to missing .NET 8.0 assemblies (v3.5.1 is built on .NET 8.0).
   - Module versions 2.0.4 (February 2021) to 3.5.0 (May 2024) are supported in PowerShell 7 version 7.0.3 (July 2020) or later.
 
-Windows PowerShell requirements and module support **in older versions of Windows** are described in the following list:
+Specific module version support in Windows depends on Windows PowerShell support and .NET Framework and/or .NET support as described in the following list:
+
+> [!TIP]
+> As stated previously, only REST API connections are supported in Exchange Online PowerShell and Security & Compliance PowerShell:
+>
+> - Version 2.0.4 of the module (February 2021) supports the REST API only for the [nine exclusive **Get-EXO\*** cmdlets](#cmdlets-in-the-exchange-online-powershell-module).
+> - Version 2.0.5 of the module (May 2021) offers partial support for REST API cmdlets only in Exchange Online PowerShell.
+> - Version 3.0.0 (September 2022) is the first version of the module that fully supports REST API cmdlets in Exchange Online PowerShell.
+> - Version 3.2.0 (June 2023) is the first version of the module that fully supports REST API cmdlets in Security & Compliance PowerShell.
+
+- **Windows 11**:
+
+  |Module version|PowerShell version|.NET requirement|
+  |---|---|---|
+  |2.0.5 or later|5.1|.NET Framework 4.7.2 (4.8.x is included, so you don't need to install the .NET Framework)|
+  |3.5.1 or later|7.4.0 or later|.NET 8.0<br/>Included in 24H2 or later.|
+  |2.0.4 to 3.5.0|7.2.x to 7.3.x|.NET 6.0 (7.2.x)<br/>.NET 7.0 (7.3.x)|
+
+- **Windows Server 2022**:
+
+  |Module version|PowerShell version|.NET requirement|
+  |---|---|---|
+  |2.0.5 or later|5.1|.NET Framework 4.7.2 (4.8 is included, so you don't need to install the .NET Framework)|
+  |3.5.1 or later|7.4.0 or later|.NET 8.0|
+  |2.0.4 to 3.5.0|7.2.x to 7.3.6|.NET 6.0 (7.2.x)<br/>.NET 7.0 (7.3.x)|
+
+- **Windows 10**:
 
-- Windows 10¹
-- Windows 8.1² ³
-- Windows Server 2012 or Windows Server 2012 R2² ³
-- Windows 7 Service Pack 1 (SP1)² ⁴ ⁵
-- Windows Server 2008 R2 SP1² ⁴ ⁵
+  |Module version|PowerShell version|Supported Windows version|.NET requirement|
+  |---|---|---|---|
+  |2.0.5 or later|5.1|Anniversary Update (version 1607; August 2016) or later|.NET Framework 4.7.2<br/>April 2018 Update (version 1803) is the first version that includes the .NET Framework 4.7.2.|
+  |3.5.1 or later|7.4.0 or later|October 2018 Update (version 1809) or later |.NET 8.0|
+  |2.0.4 to 3.5.0|7.0.3 to 7.3.6|October 2018 Update (version 1809) or later|.NET Core 3.1 (7.0.x)<br/>.NET 5.0 (7.1.x)<br/>.NET 6.0 (7.2.x)<br/>.NET 7.0 (7.3.x)|
+  |2.0.4 to 3.5.0|7.0.3 to 7.2.19|Anniversary Update (version 1607; August 2016) or later|.NET Core 3.1 (7.0.x)<br/>.NET 5.0 (7.1.x)<br/>.NET 6.0 (7.2.x)|
 
-¹ Windows 10 Anniversary Update (version 1607 from August 2016) is the earliest version of Windows 10 that's reliably compatible with the .NET Framework 4.7.2 (v2.0.5 or later versions of the module in Windows PowerShell 5.1).<br/>
-² Support for this version of Windows is over. This version of Windows is supported only in Azure virtual machines.<br/>
-³ PowerShell 7 on this version of Windows requires a compatible version of .NET Core or .NET runtime and the [Windows 10 Universal C Runtime (CRT)](https://support.microsoft.com/topic/c0514201-7fe6-95a3-b0a5-287930f3560c). The last officially supported version of PowerShell 7 on this version of Windows is 7.2 (7.2.19 from August 2024), which means the last supported version of the module in PowerShell 7 is v3.5.0 (May 2024).<br/>
-⁴ The latest version of the module supported on this version of Windows is v2.0.3 (September 2020).<br/>
-⁵ Windows PowerShell 5.1 on this version of Windows requires the .NET Framework 4.5 or later and the Windows Management Framework 5.1. For more information, see [Windows Management Framework 5.1](https://aka.ms/wmf5download).
+- **Windows Server 2016** and **Windows Server 2019**:
+
+  |Module version|PowerShell version|.NET requirement|
+  |---|---|---|
+  |2.0.5 or later|5.1|.NET Framework 4.7.2<br/>Included in Windows Server 2019.|
+  |3.5.1 or later|7.4.0 or later|.NET 8.0|
+  |2.0.4 to 3.5.0|7.0.3 to 7.3.6|.NET Core 3.1 (7.0.x)<br/>.NET 5.0 (7.1.x)<br/>.NET 6.0 (7.2.x)<br/>.NET 7.0 (7.3.x)|
+
+- **Windows 8.1**, **Windows Server 2012**, and **Windows Server 2012 R2**:
+
+  |Module version|PowerShell version.|NET requirement|
+  |---|---|---|
+  |2.0.5 or later|5.1|.NET Framework 4.7.2|
+  |2.0.4 to 3.5.0|7.0.3 to 7.2.19|.NET Core 3.1 (7.0.x)<br/>.NET 5.0 (7.1.x)<br/>.NET 6.0 (7.2.x)|
+
+- **Windows 7.1 SP1** and **Windows Server 2008 R2 SP1**:
+
+  |Module version|PowerShell version.|NET requirement|
+  |---|---|---|
+  |2.0.3|5.1|.NET Framework 4.7.1|
+
+  > [!NOTE]
+  > Although you can install this version of the module, you can't connect to Exchange Online PowerShell, because version 7.0.3 lacks support for REST API connections.
 
 ### Prerequisites for the Exchange Online PowerShell module
 
@@ -317,6 +359,8 @@ For more information about execution policies, see [About Execution Policies](/p
 
 As of October 2023, REST API connections replaced basic authentication (remote PowerShell) connections in [Exchange Online PowerShell](https://techcommunity.microsoft.com/blog/exchange/deprecation-of-remote-powershell-in-exchange-online-%e2%80%93-re-enabling-or-extending-r/3779692) and [Security & Compliance PowerShell](https://techcommunity.microsoft.com/blog/exchange/deprecation-of-remote-powershell-rps-protocol-in-security-and-compliance-powersh/3815432). REST API connections don't require Basic authentication in WinRM.
 
+Version 3.2.0 (June 2023) and later version of the module fully support REST API cmdlets in Exchange Online PowerShell and Security & Compliance PowerShell.
+
 <a name='powershellget-for-rest-api-connections-in-windows'></a>
 
 ### PowerShellGet required in Windows

From 36081bccfb75585abef32f97f6eed2538eb252db Mon Sep 17 00:00:00 2001
From: Chris Davis <chris.davis@microsoft.com>
Date: Fri, 8 Aug 2025 17:27:01 -0700
Subject: [PATCH 141/145] Update exchange-online-powershell-v2.md

---
 exchange/docs-conceptual/exchange-online-powershell-v2.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/exchange/docs-conceptual/exchange-online-powershell-v2.md b/exchange/docs-conceptual/exchange-online-powershell-v2.md
index 38b1cbcba7..9a507eca53 100644
--- a/exchange/docs-conceptual/exchange-online-powershell-v2.md
+++ b/exchange/docs-conceptual/exchange-online-powershell-v2.md
@@ -305,7 +305,7 @@ Specific module version support in Windows depends on Windows PowerShell support
 
   |Module version|PowerShell version|Supported Windows version|.NET requirement|
   |---|---|---|---|
-  |2.0.5 or later|5.1|Anniversary Update (version 1607; August 2016) or later|.NET Framework 4.7.2<br/>April 2018 Update (version 1803) is the first version that includes the .NET Framework 4.7.2.|
+  |2.0.5 or later|5.1|Anniversary Update (version 1607; August 2016) or later|.NET Framework 4.7.2<br/>April 2018 Update (version 1803) or later includes the .NET Framework 4.7.2, so you don't need to download it.|
   |3.5.1 or later|7.4.0 or later|October 2018 Update (version 1809) or later |.NET 8.0|
   |2.0.4 to 3.5.0|7.0.3 to 7.3.6|October 2018 Update (version 1809) or later|.NET Core 3.1 (7.0.x)<br/>.NET 5.0 (7.1.x)<br/>.NET 6.0 (7.2.x)<br/>.NET 7.0 (7.3.x)|
   |2.0.4 to 3.5.0|7.0.3 to 7.2.19|Anniversary Update (version 1607; August 2016) or later|.NET Core 3.1 (7.0.x)<br/>.NET 5.0 (7.1.x)<br/>.NET 6.0 (7.2.x)|

From ca8a2a939db3eef1756fdbc75fb634226defe3f3 Mon Sep 17 00:00:00 2001
From: Chris Davis <chris.davis@microsoft.com>
Date: Fri, 8 Aug 2025 17:31:04 -0700
Subject: [PATCH 142/145] Update exchange-online-powershell-v2.md

---
 exchange/docs-conceptual/exchange-online-powershell-v2.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/exchange/docs-conceptual/exchange-online-powershell-v2.md b/exchange/docs-conceptual/exchange-online-powershell-v2.md
index 9a507eca53..08715345d7 100644
--- a/exchange/docs-conceptual/exchange-online-powershell-v2.md
+++ b/exchange/docs-conceptual/exchange-online-powershell-v2.md
@@ -320,14 +320,14 @@ Specific module version support in Windows depends on Windows PowerShell support
 
 - **Windows 8.1**, **Windows Server 2012**, and **Windows Server 2012 R2**:
 
-  |Module version|PowerShell version.|NET requirement|
+  |Module version|PowerShell version|NET requirement|
   |---|---|---|
   |2.0.5 or later|5.1|.NET Framework 4.7.2|
   |2.0.4 to 3.5.0|7.0.3 to 7.2.19|.NET Core 3.1 (7.0.x)<br/>.NET 5.0 (7.1.x)<br/>.NET 6.0 (7.2.x)|
 
 - **Windows 7.1 SP1** and **Windows Server 2008 R2 SP1**:
 
-  |Module version|PowerShell version.|NET requirement|
+  |Module version|PowerShell version|NET requirement|
   |---|---|---|
   |2.0.3|5.1|.NET Framework 4.7.1|
 

From 7be31c39a1b52b99d658f968c16d56c7469d2f71 Mon Sep 17 00:00:00 2001
From: Chris Davis <chris.davis@microsoft.com>
Date: Fri, 8 Aug 2025 17:31:53 -0700
Subject: [PATCH 143/145] Update exchange-online-powershell-v2.md

---
 exchange/docs-conceptual/exchange-online-powershell-v2.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/exchange/docs-conceptual/exchange-online-powershell-v2.md b/exchange/docs-conceptual/exchange-online-powershell-v2.md
index 08715345d7..e082fbfdf7 100644
--- a/exchange/docs-conceptual/exchange-online-powershell-v2.md
+++ b/exchange/docs-conceptual/exchange-online-powershell-v2.md
@@ -320,14 +320,14 @@ Specific module version support in Windows depends on Windows PowerShell support
 
 - **Windows 8.1**, **Windows Server 2012**, and **Windows Server 2012 R2**:
 
-  |Module version|PowerShell version|NET requirement|
+  |Module version|PowerShell version|.NET requirement|
   |---|---|---|
   |2.0.5 or later|5.1|.NET Framework 4.7.2|
   |2.0.4 to 3.5.0|7.0.3 to 7.2.19|.NET Core 3.1 (7.0.x)<br/>.NET 5.0 (7.1.x)<br/>.NET 6.0 (7.2.x)|
 
 - **Windows 7.1 SP1** and **Windows Server 2008 R2 SP1**:
 
-  |Module version|PowerShell version|NET requirement|
+  |Module version|PowerShell version|.NET requirement|
   |---|---|---|
   |2.0.3|5.1|.NET Framework 4.7.1|
 

From 95a658bff110e64401275cbc1fc4366f9a56d89e Mon Sep 17 00:00:00 2001
From: Chris Davis <chris.davis@microsoft.com>
Date: Fri, 8 Aug 2025 18:47:20 -0700
Subject: [PATCH 144/145] Update exchange-online-powershell-v2.md

Updates to the updates
---
 .../exchange-online-powershell-v2.md          | 33 ++++++++++++-------
 1 file changed, 21 insertions(+), 12 deletions(-)

diff --git a/exchange/docs-conceptual/exchange-online-powershell-v2.md b/exchange/docs-conceptual/exchange-online-powershell-v2.md
index e082fbfdf7..6c001a00cb 100644
--- a/exchange/docs-conceptual/exchange-online-powershell-v2.md
+++ b/exchange/docs-conceptual/exchange-online-powershell-v2.md
@@ -272,8 +272,9 @@ Now you can do the [regular PowerShell prerequisites](#prerequisites-for-the-exc
   - Current versions of Windows include the required versions of the .NET Framework, so you don't need to install the .NET Framework to use the module in Windows PowerShell 5.1.
 
 - **PowerShell 7**:
-  - Module versions 3.5.1 (July 2024) or later require PowerShell 7 version 7.4.0 (November 2023) or later. Earlier versions of PowerShell 7 might encounter compatibility issues due to missing .NET 8.0 assemblies (v3.5.1 is built on .NET 8.0).
-  - Module versions 2.0.4 (February 2021) to 3.5.0 (May 2024) are supported in PowerShell 7 version 7.0.3 (July 2020) or later.
+  - Module versions 3.5.0 (May 2024) or later require PowerShell 7.4.0 (November 2023) or later due to .NET 8.0 assembly dependencies. Earlier versions of PowerShell 7 might encounter compatibility issues.
+  - Module versions 3.0.0 (September 2022) to 3.4.0 (October 2023) require PowerShell 7.2.0 (November 2021) or later due to .NET 6.0 assembly dependencies in REST API cmdlets and connections.
+  - Support for the module in PowerShell 7 started with version 2.0.4 (February 2021) in PowerShell 7.0.3 (July 2020).
 
 Specific module version support in Windows depends on Windows PowerShell support and .NET Framework and/or .NET support as described in the following list:
 
@@ -290,40 +291,48 @@ Specific module version support in Windows depends on Windows PowerShell support
   |Module version|PowerShell version|.NET requirement|
   |---|---|---|
   |2.0.5 or later|5.1|.NET Framework 4.7.2 (4.8.x is included, so you don't need to install the .NET Framework)|
-  |3.5.1 or later|7.4.0 or later|.NET 8.0<br/>Included in 24H2 or later.|
-  |2.0.4 to 3.5.0|7.2.x to 7.3.x|.NET 6.0 (7.2.x)<br/>.NET 7.0 (7.3.x)|
+  |3.5.0 or later|7.4.0 or later|.NET 8.0<br/>Included in 24H2 or later.|
+  |3.0.0 to 3.4.0|7.2.0 to 7.3.7 (or later)|.NET 6.0 (7.2.x)<br/>.NET 7.0 (7.3.x)|
+
+  PowerShell 7.2.0 is the earliest supported version in Windows 11.
 
 - **Windows Server 2022**:
 
   |Module version|PowerShell version|.NET requirement|
   |---|---|---|
   |2.0.5 or later|5.1|.NET Framework 4.7.2 (4.8 is included, so you don't need to install the .NET Framework)|
-  |3.5.1 or later|7.4.0 or later|.NET 8.0|
-  |2.0.4 to 3.5.0|7.2.x to 7.3.6|.NET 6.0 (7.2.x)<br/>.NET 7.0 (7.3.x)|
+  |3.5.0 or later|7.4.0 or later|.NET 8.0|
+  |3.0.0 to 3.4.0|7.2.0 to 7.3.7 (or later)|.NET 6.0 (7.2.x)<br/>.NET 7.0 (7.3.x)|
+
+  PowerShell 7.2.0 (.NET 6.0) is the earliest supported version in Windows Server 2022.
 
 - **Windows 10**:
 
   |Module version|PowerShell version|Supported Windows version|.NET requirement|
   |---|---|---|---|
   |2.0.5 or later|5.1|Anniversary Update (version 1607; August 2016) or later|.NET Framework 4.7.2<br/>April 2018 Update (version 1803) or later includes the .NET Framework 4.7.2, so you don't need to download it.|
-  |3.5.1 or later|7.4.0 or later|October 2018 Update (version 1809) or later |.NET 8.0|
-  |2.0.4 to 3.5.0|7.0.3 to 7.3.6|October 2018 Update (version 1809) or later|.NET Core 3.1 (7.0.x)<br/>.NET 5.0 (7.1.x)<br/>.NET 6.0 (7.2.x)<br/>.NET 7.0 (7.3.x)|
-  |2.0.4 to 3.5.0|7.0.3 to 7.2.19|Anniversary Update (version 1607; August 2016) or later|.NET Core 3.1 (7.0.x)<br/>.NET 5.0 (7.1.x)<br/>.NET 6.0 (7.2.x)|
+  |3.5.0 or later|7.4.0 or later|October 2018 Update (version 1809) or later |.NET 8.0|
+  |3.0.0 to 3.4.0|7.2.0 to 7.3.7 (or later)|October 2018 Update (version 1809) or later|.NET 6.0 (7.2.x)<br/>.NET 7.0 (7.3.x)|
+  |2.0.4 and 2.0.5|7.0.3 to 7.1.5 (or later)|Anniversary Update (version 1607; August 2016) or later|.NET Core 3.1 (7.0.x)<br/>.NET 5.0 (7.1.x)|
 
 - **Windows Server 2016** and **Windows Server 2019**:
 
   |Module version|PowerShell version|.NET requirement|
   |---|---|---|
   |2.0.5 or later|5.1|.NET Framework 4.7.2<br/>Included in Windows Server 2019.|
-  |3.5.1 or later|7.4.0 or later|.NET 8.0|
-  |2.0.4 to 3.5.0|7.0.3 to 7.3.6|.NET Core 3.1 (7.0.x)<br/>.NET 5.0 (7.1.x)<br/>.NET 6.0 (7.2.x)<br/>.NET 7.0 (7.3.x)|
+  |3.5.0 or later|7.4.0 or later|.NET 8.0|
+  |3.0.0 to 3.4.0|7.2.0 to 7.3.7 (or later)|.NET 6.0 (7.2.x)<br/>.NET 7.0 (7.3.x)|
+  |2.0.4 and 2.0.5|7.0.3 to 7.1.5 (or later)|.NET Core 3.1 (7.0.x)<br/>.NET 5.0 (7.1.x)|
 
 - **Windows 8.1**, **Windows Server 2012**, and **Windows Server 2012 R2**:
 
   |Module version|PowerShell version|.NET requirement|
   |---|---|---|
   |2.0.5 or later|5.1|.NET Framework 4.7.2|
-  |2.0.4 to 3.5.0|7.0.3 to 7.2.19|.NET Core 3.1 (7.0.x)<br/>.NET 5.0 (7.1.x)<br/>.NET 6.0 (7.2.x)|
+  |3.0.0 to 3.4.0|7.2.x|.NET 6.0|
+  |2.0.4 and 2.0.5|7.0.3 to 7.1.5 (or later)|.NET Core 3.1 (7.0.x)<br/>.NET 5.0 (7.1.x)|
+
+  PowerShell 7.2.22 (.NET 6.0) is the latest supported version in Windows 8.1, Windows Server 2012, and Windows Server 2012 R2.
 
 - **Windows 7.1 SP1** and **Windows Server 2008 R2 SP1**:
 

From a6be8c81f3c5960da548011f15472c124e7095d7 Mon Sep 17 00:00:00 2001
From: Chris Davis <chris.davis@microsoft.com>
Date: Fri, 8 Aug 2025 18:49:22 -0700
Subject: [PATCH 145/145] Update exchange-online-powershell-v2.md

---
 exchange/docs-conceptual/exchange-online-powershell-v2.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/exchange/docs-conceptual/exchange-online-powershell-v2.md b/exchange/docs-conceptual/exchange-online-powershell-v2.md
index 6c001a00cb..ffacee5da3 100644
--- a/exchange/docs-conceptual/exchange-online-powershell-v2.md
+++ b/exchange/docs-conceptual/exchange-online-powershell-v2.md
@@ -272,7 +272,7 @@ Now you can do the [regular PowerShell prerequisites](#prerequisites-for-the-exc
   - Current versions of Windows include the required versions of the .NET Framework, so you don't need to install the .NET Framework to use the module in Windows PowerShell 5.1.
 
 - **PowerShell 7**:
-  - Module versions 3.5.0 (May 2024) or later require PowerShell 7.4.0 (November 2023) or later due to .NET 8.0 assembly dependencies. Earlier versions of PowerShell 7 might encounter compatibility issues.
+  - Module versions 3.5.0 (May 2024) or later require PowerShell 7.4.0 (November 2023) or later due to .NET 8.0 assembly dependencies. Earlier versions of PowerShell 7 might encounter compatibility issues (PowerShell 7.3.6 is more compatible than 7.3.7).
   - Module versions 3.0.0 (September 2022) to 3.4.0 (October 2023) require PowerShell 7.2.0 (November 2021) or later due to .NET 6.0 assembly dependencies in REST API cmdlets and connections.
   - Support for the module in PowerShell 7 started with version 2.0.4 (February 2021) in PowerShell 7.0.3 (July 2020).