Update connect-to-scc-powershell.md

Added AzureAdAuthorizationEndpoint to Gallatin example per IM request. Also converted table to list.

Author: chrisda

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

@@ -61,18 +61,19 @@ For detailed syntax and parameter information, see [Connect-IPPSSession](/powers
 
 - _\<UPN\>_ is your account in user principal name format (for example, `[email protected]`).
 
-- The required _ConnectionUri_ and _AzureADAuthorizationEndpointUri_ values depend on the nature of your Microsoft 365 organization. Common values are described in the following table:
-
-  |Environment|_ConnectionUri_|_AzureADAuthorizationEndpointUri_|
-  |---|---|---|
-  |Microsoft 365 or Microsoft 365 GCC|n/a<sup>\*</sup>|n/a<sup>\*\*</sup>|
-  |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 operated by 21Vianet|`https://ps.compliance.protection.partner.outlook.cn/powershell-liveid`|`https://login.chinacloudapi.cn/common`|
-
-  <sup>\*</sup> The required value `https://ps.compliance.protection.outlook.com/powershell-liveid/` is also the default value, so you don't need to use the _ConnectionUri_ parameter in Microsoft 365 or Microsoft 365 GCC environments.
-
-  <sup>\*\*</sup> The required value `https://login.microsoftonline.com/common` is also the default value, so you don't need to use the _AzureADAuthorizationEndpointUri_ parameter in Microsoft 365 or Microsoft 365 GCC environments.
+- The required _ConnectionUri_ and _AzureADAuthorizationEndpointUri_ values depend on the nature of your Microsoft 365 organization. Common values are described in the following list:
+  - **Microsoft 365 or Microsoft 365 GCC**:
+    - _ConnectionUri_: None. The required value `https://ps.compliance.protection.outlook.com/powershell-liveid/` is also the default value, so you don't need to use the _ConnectionUri_ parameter in Microsoft 365 or Microsoft 365 GCC environments.
+    - _AzureADAuthorizationEndpointUri_: None. The required value `https://login.microsoftonline.com/common` is also the default value, so you don't need to use the _AzureADAuthorizationEndpointUri_ parameter in Microsoft 365 or Microsoft 365 GCC environments.
+  - **Microsoft 365 GCC High**:
+    - _ConnectionUri_: `https://ps.compliance.protection.office365.us/powershell-liveid/`
+    - _AzureADAuthorizationEndpointUri_: `https://login.microsoftonline.us/common`
+  - **Microsoft 365 DoD**:
+    - _ConnectionUri_: `https://l5.ps.compliance.protection.office365.us/powershell-liveid/`
+    - _AzureADAuthorizationEndpointUri_: `https://login.microsoftonline.us/common`
+  - **Office 365 operated by 21Vianet**:
+    - _ConnectionUri_: `https://ps.compliance.protection.partner.outlook.cn/powershell-liveid`
+    - _AzureADAuthorizationEndpointUri_: `https://login.chinacloudapi.cn/common`
 
 - If you're behind a proxy server, you can use the _PSSessionOption_ parameter in the connection command. First, run this command: `$ProxyOptions = New-PSSessionOption -ProxyAccessType <Value>`, where \<Value\> is `IEConfig`, `WinHttpConfig`, or `AutoDetect`. Then, use the value `$ProxyOptions` for the _PSSessionOption_ parameter. For more information, see [New-PSSessionOption](/powershell/module/microsoft.powershell.core/new-pssessionoption).
 
@@ -105,7 +106,7 @@ For detailed syntax and parameter information, see [Connect-IPPSSession](/powers
    - **This example connects to Security & Compliance PowerShell in an Office 365 operated by 21Vianet organization**:
 
      ```powershell
-     Connect-IPPSSession -UserPrincipalName [email protected] -ConnectionUri https://ps.compliance.protection.partner.outlook.cn/powershell-liveid
+     Connect-IPPSSession -UserPrincipalName [email protected] -ConnectionUri https://ps.compliance.protection.partner.outlook.cn/powershell-liveid -AzureADAuthorizationEndpointUri https://login.chinacloudapi.cn/common
      ```
 
 2. In the sign-in window that opens, enter your password, and then click **Sign in**.