Merge branch 'master' into paramsetplcy

Author: Kateyanne

exchange/docs-conceptual/connect-to-exchange-online-protection-powershell.md

@@ -56,7 +56,7 @@ If you account uses multi-factor authentication, use the steps in this section.
 2. The command that you need to run uses the following syntax:
 
    ```powershell
-   <Connect-IPPSSession | Connect-ExchangeOnline> -UserPrincipalName <UPN> -ShowProgress $true [-ConnectionUri <URL>] [-AzureADAuthorizationEndPointUri <URL>]
+   <Connect-IPPSSession | Connect-ExchangeOnline> -UserPrincipalName <UPN> [-ConnectionUri <URL>] [-AzureADAuthorizationEndPointUri <URL>]
    ```
 
    - _\<UPN\>_ is your account in user principal name format (for example, `[email protected]`).
@@ -65,13 +65,13 @@ If you account uses multi-factor authentication, use the steps in this section.
    **This example connects to Exchange Online Protection PowerShell in a Microsoft 365 organization**:
 
    ```powershell
-   Connect-IPPSSession -UserPrincipalName [email protected] -ShowProgress $true -ConnectionUri https://ps.protection.outlook.com/powershell-liveid/
+   Connect-IPPSSession -UserPrincipalName [email protected] -ConnectionUri https://ps.protection.outlook.com/powershell-liveid/
    ```
 
    **This example connects to Exchange Online Protection PowerShell in an Office 365 Germany organization**:
 
    ```powershell
-   Connect-IPPSSession -UserPrincipalName [email protected] -ShowProgress $true -ConnectionUri https://ps.protection.outlook.de/powershell-liveid/ -AzureADAuthorizationEndPointUri https://login.microsoftonline.de/common
+   Connect-IPPSSession -UserPrincipalName [email protected] -ConnectionUri https://ps.protection.outlook.de/powershell-liveid/ -AzureADAuthorizationEndPointUri https://login.microsoftonline.de/common
    ```
 
    **This example connects to Exchange Online Protection PowerShell in an Exchange Enterprise CAL with Services organization**:
@@ -110,21 +110,21 @@ If your account doesn't use multi-factor authentication, use the steps in this s
 3. The command that you need to run uses the following syntax:
 
    ```powershell
-   <Connect-IPPSSession | Connect-ExchangeOnline> -Credential $UserCredential -ShowProgress $true -ConnectionUri <URL>
+   <Connect-IPPSSession | Connect-ExchangeOnline> -Credential $UserCredential -ConnectionUri <URL>
    ```
 
   The required cmdlet and _ConnectionUri_ parameter values are described in the table in the [What do you need to know before you begin?](#what-do-you-need-to-know-before-you-begin) section.
 
    **This example connects to Exchange Online Protection PowerShell in a Microsoft 365 organization**:
 
    ```powershell
-   Connect-IPPSSession -Credential $UserCredential -ShowProgress $true -ConnectionUri https://ps.protection.outlook.com/powershell-liveid/
+   Connect-IPPSSession -Credential $UserCredential -ConnectionUri https://ps.protection.outlook.com/powershell-liveid/
    ```
 
    **This example connects to Exchange Online Protection PowerShell in an Office 365 Germany organization**:
 
    ```powershell
-   Connect-IPPSSession -Credential $UserCredential -ShowProgress $true -ConnectionUri https://ps.protection.outlook.de/powershell-liveid/
+   Connect-IPPSSession -Credential $UserCredential -ConnectionUri https://ps.protection.outlook.de/powershell-liveid/
    ```
 
    **This example connects to Exchange Online Protection PowerShell in an Exchange Enterprise CAL with Services organization**:

exchange/docs-conceptual/connect-to-scc-powershell.md

@@ -35,7 +35,7 @@ To use the older Exchange Online Remote PowerShell Module to connect to Security
 
   |Microsoft 365 offering|_ConnectionUri_ value|_AzureADAuthorizationEndPointUri_ value|
   |---|---|---|
-  |Microsoft 365 or Microsoft 365 GCC|`https://ps.compliance.protection.outlook.com/powershell-liveid/`|Not used|
+  |Microsoft 365 or Microsoft 365 GCC|Not used|Not used|
   |Microsoft 365 GCC High|`https://ps.compliance.protection.office365.us/powershell-liveid/`|`https://login.microsoftonline.us/common`|
   |Microsoft 365 DoD|`https://l5.ps.compliance.protection.office365.us/powershell-liveid/`|`https://login.microsoftonline.us/common`|
   |Office 365 Germany|`https://ps.compliance.protection.outlook.de/PowerShell-LiveID`|`https://login.microsoftonline.de/common`|
@@ -54,7 +54,7 @@ If you account uses multi-factor authentication, use the steps in this section.
 2. The command that you need to run uses the following syntax:
 
    ```powershell
-   Connect-IPPSSession -UserPrincipalName <UPN> -ShowProgress $true [-ConnectionUri <URL>] [-AzureADAuthorizationEndPointUri <URL>]
+   Connect-IPPSSession -UserPrincipalName <UPN> [-ConnectionUri <URL>] [-AzureADAuthorizationEndPointUri <URL>]
    ```
 
    - \<UPN\> is your account in user principal name format (for example, `[email protected]`).
@@ -63,25 +63,25 @@ If you account uses multi-factor authentication, use the steps in this section.
    **This example connects to Security & Compliance Center PowerShell in a Microsoft 365 or Microsoft 365 GCC organization**.
 
    ```powershell
-   Connect-IPPSSession -UserPrincipalName [email protected] -ShowProgress $true -ConnectionUri https://ps.compliance.protection.outlook.com/powershell-liveid/
+   Connect-IPPSSession -UserPrincipalName [email protected] -ConnectionUri https://ps.compliance.protection.outlook.com/powershell-liveid/
    ```
 
    **This example connects to Security & Compliance Center PowerShell in an Office 365 Germany organization**.
 
    ```powershell
-   Connect-IPPSSession -UserPrincipalName [email protected] -ShowProgress $true -ConnectionUri https://ps.compliance.protection.outlook.de/PowerShell-LiveID -AzureADAuthorizationEndPointUri https://login.microsoftonline.de/common
+   Connect-IPPSSession -UserPrincipalName [email protected] -ConnectionUri https://ps.compliance.protection.outlook.de/PowerShell-LiveID -AzureADAuthorizationEndPointUri https://login.microsoftonline.de/common
    ```
 
    **This example connects to Security & Compliance Center PowerShell in a Microsoft GCC High organization**.
 
    ```powershell
-   Connect-IPPSSession -UserPrincipalName [email protected] -ShowProgress $true -ConnectionUri https://l5.ps.compliance.protection.office365.us/powershell-liveid/ -AzureADAuthorizationEndPointUri https://login.microsoftonline.us/common
+   Connect-IPPSSession -UserPrincipalName [email protected] -ConnectionUri https://l5.ps.compliance.protection.office365.us/powershell-liveid/ -AzureADAuthorizationEndPointUri https://login.microsoftonline.us/common
    ```
 
    **This example connects to Security & Compliance Center PowerShell in a Microsoft 365 DoD organization**.
 
    ```powershell
-   Connect-IPPSSession -UserPrincipalName [email protected] -ShowProgress $true -ConnectionUri https://l5.ps.compliance.protection.office365.us/powershell-liveid/ -AzureADAuthorizationEndPointUri https://login.microsoftonline.us/common
+   Connect-IPPSSession -UserPrincipalName [email protected] -ConnectionUri https://l5.ps.compliance.protection.office365.us/powershell-liveid/ -AzureADAuthorizationEndPointUri https://login.microsoftonline.us/common
    ```
 
 For detailed syntax and parameter information, see [Connect-IPPSSession](https://docs.microsoft.com/powershell/module/exchange/connect-exchangeonline).
@@ -114,33 +114,33 @@ If your account doesn't use multi-factor authentication, use the steps in this s
 3. The command that you need to run uses the following syntax:
 
    ```powershell
-   Connect-IPPSSession -Credential $UserCredential -ShowProgress $true -ConnectionUri <URL>
+   Connect-IPPSSession -Credential $UserCredential -ConnectionUri <URL>
    ```
 
    The _ConnectionUri_ values are described in the table in the [What do you need to know before you begin?](#what-do-you-need-to-know-before-you-begin) section.
 
    **This example connects to Security & Compliance Center PowerShell in a Microsoft 365 or Microsoft 365 GCC organization**.
 
    ```powershell
-   Connect-IPPSSession -Credential $UserCredential -ShowProgress $true -ConnectionUri https://ps.compliance.protection.outlook.com/powershell-liveid/
+   Connect-IPPSSession -Credential $UserCredential -ConnectionUri https://ps.compliance.protection.outlook.com/powershell-liveid/
    ```
 
    **This example connects to Security & Compliance Center PowerShell in an Office 365 Germany organization**.
 
    ```powershell
-   Connect-IPPSSession -Credential $UserCredential -ShowProgress $true -ConnectionUri https://ps.compliance.protection.outlook.de/
+   Connect-IPPSSession -Credential $UserCredential -ConnectionUri https://ps.compliance.protection.outlook.de/
    ```
 
    **This example connects to Security & Compliance Center PowerShell in a Microsoft GCC High organization**.
 
    ```powershell
-   Connect-IPPSSession -Credential $UserCredential -ShowProgress $true -ConnectionUri https://l5.ps.compliance.protection.office365.us/powershell-liveid/
+   Connect-IPPSSession -Credential $UserCredential -ConnectionUri https://l5.ps.compliance.protection.office365.us/powershell-liveid/
    ```
 
    **This example connects to Security & Compliance Center PowerShell in a Microsoft 365 DoD organization**.
 
    ```powershell
-   Connect-IPPSSession -Credential $UserCredential -ShowProgress $true -ConnectionUri https://l5.ps.compliance.protection.office365.us/powershell-liveid/
+   Connect-IPPSSession -Credential $UserCredential -ConnectionUri https://l5.ps.compliance.protection.office365.us/powershell-liveid/
    ```
 
 For detailed syntax and parameter information, see [Connect-IPPSSession](https://docs.microsoft.com/powershell/module/exchange/connect-exchangeonline).

exchange/docs-conceptual/exchange-online-powershell-v2.md

@@ -237,10 +237,10 @@ The **Get-EXO\*** cmdlets in the module have categorized output properties. Inst
 
 In the biggest and most used **Get-EXO\*** cmdlets:
 
-- [Get-EXOCasMailbox](../exchange-ps/exchange/Get-EXOCasMailbox.md)
-- [Get-EXOMailbox](../exchange-ps/exchange/Get-EXOMailbox.md)
-- [Get-EXOMailboxStatistics](../exchange-ps/exchange/Get-EXOMailboxStatistics.md)
-- [Get-EXORecipient](../exchange-ps/exchange/Get-EXORecipient.md)
+- [Get-EXOCasMailbox](https://docs.microsoft.com/powershell/module/exchange/get-exocasmailbox)
+- [Get-EXOMailbox](https://docs.microsoft.com/powershell/module/exchange/get-exomailbox.md)
+- [Get-EXOMailboxStatistics](https://docs.microsoft.com/powershell/module/exchange/get-exomailboxstatistics.md)
+- [Get-EXORecipient](https://docs.microsoft.com/powershell/module/exchange/get-exorecipient.md)
 
 Property sets are controlled by the following parameters:
 

exchange/docs-conceptual/scc-powershell.md

@@ -21,6 +21,6 @@ Security & Compliance Center PowerShell is the administrative interface that ena
 
 - To learn about the structure and layout of the cmdlet reference topics in Security & Compliance Center PowerShell, see [Exchange cmdlet syntax](exchange-cmdlet-syntax.md).
 
-Many of the cmdlets that are available in Security & Compliance Center PowerShell correspond to features that are only available in the Security & Compliance Center, so the related cmdlets are exclusive to Security & Compliance Center PowerShell. But, some cmdlets that are available in Security & Compliance Center PowerShell have the same names and functionality as those in Exchange Online PowerShell (for example, [Get-User](../exchange-ps/exchange/Get-User.md)).
+Many of the cmdlets that are available in Security & Compliance Center PowerShell correspond to features that are only available in the Security & Compliance Center, so the related cmdlets are exclusive to Security & Compliance Center PowerShell. But, some cmdlets that are available in Security & Compliance Center PowerShell have the same names and functionality as those in Exchange Online PowerShell (for example, [Get-User](https://docs.microsoft.com/powershell/module/exchange/get-user.md)).
 
 Also, some features that are available in the Security & Compliance Center (for example, [anti-spam and anti-malware](https://docs.microsoft.com/microsoft-365/security/office-365-security/anti-spam-and-anti-malware-protection?view=o365-worldwide) cmdlets are only available in [Exchange Online PowerShell](exchange-online-powershell.md)). Check the **Applies to** value in the cmdlet reference topic to verify where the cmdlet actually resides.