Merge pull request #10890 from MicrosoftDocs/P4-chrisda

chrisda · web-flow · commit c457aa7c8eed · 2023-05-26T10:23:06.000-07:00
P4-chrisda to Main
diff --git a/exchange/docs-conceptual/connect-to-scc-powershell.md b/exchange/docs-conceptual/connect-to-scc-powershell.md
@@ -35,7 +35,7 @@ To use the older Exchange Online Remote PowerShell Module (the V1 module) to con
 
   > [!NOTE]
   >
-  > If you're using version 3.2.0-Preview3 of the module, and you use `-UseRPSSession:$false` in the **Connect-IPPSSession** command, you have access to REST API cmdlets _only_. For more information, see [Updates for the EXO V3 module)](exchange-online-powershell-v2.md#updates-for-the-exo-v3-module).
+  > If you're using version 3.2.0-Preview4 or later of the module, and you don't use the _UseRPSSession_ switch in the **Connect-IPPSSession** command, you have access to REST API cmdlets _only_. For more information, see [Updates for the EXO V3 module)](exchange-online-powershell-v2.md#updates-for-the-exo-v3-module).
 
 - After you connect, the cmdlets and parameters that you have or don't have access to is controlled by role-based access control (RBAC). For more information, see [Permissions in the Microsoft 365 Defender portal](/microsoft-365/security/office-365-security/mdo-portal-permissions) and [Permissions in the Microsoft Purview compliance portal](/microsoft-365/compliance/microsoft-365-compliance-center-permissions).
 
@@ -58,14 +58,14 @@ Import-Module ExchangeOnlineManagement
 The command that you need to run uses the following syntax:
 
 ```powershell
-Connect-IPPSSession -UserPrincipalName <UPN> [-ConnectionUri <URL>] [-UseRPSSession:$false] [-AzureADAuthorizationEndpointUri <URL>] [-DelegatedOrganization <String>] [-PSSessionOption $ProxyOptions]
+Connect-IPPSSession -UserPrincipalName <UPN> [-ConnectionUri <URL>] [-UseRPSSession] [-AzureADAuthorizationEndpointUri <URL>] [-DelegatedOrganization <String>] [-PSSessionOption $ProxyOptions]
 ```
 
 For detailed syntax and parameter information, see [Connect-IPPSSession](/powershell/module/exchange/connect-ippssession).
 
 - _\<UPN\>_ is your account in user principal name format (for example, `navin@contoso.onmicrosoft.com`).
 
-- In v3.2.0-Preview3 of the module, if you use `-UseRPSSession:$false` in the **Connect-IPPSSession** command, you connect in REST API mode. To connect in remote PowerShell mode, don't use the _UseRPSSession_ switch. For more information, see [Updates for the EXO V3 module)](exchange-online-powershell-v2.md#updates-for-the-exo-v3-module).
+- In v3.2.0-Preview4 or later of the module, if you don't use the _UseRPSSession_ switch in the **Connect-IPPSSession** command, you connect in REST API mode. To connect in remote PowerShell mode, use the _UseRPSSession_ switch. For more information, see [Updates for the EXO V3 module)](exchange-online-powershell-v2.md#updates-for-the-exo-v3-module).
 
 - The required _ConnectionUri_ and _AzureADAuthorizationEndpointUri_ values depend on the nature of your Microsoft 365 organization. Common values are described in the following table:
 
diff --git a/exchange/docs-conceptual/exchange-online-powershell-v2.md b/exchange/docs-conceptual/exchange-online-powershell-v2.md
@@ -41,7 +41,7 @@ Version 3.0.0 or later is known as the EXO V3 module. The EXO V3 module improves
 
 - Cmdlets backed by the REST API are available in the following PowerShell environments based on the version of the EXO V3 module:
   - **Exchange Online PowerShell**: v3.0.0 or later.
-  - **Security & Compliance PowerShell**: v3.2.0-Preview3 or later.
+  - **Security & Compliance PowerShell**: v3.2.0-Preview4 or later.
 
   REST API cmdlets have the following advantages over their historical counterparts:
 
@@ -64,11 +64,9 @@ Version 3.0.0 or later is known as the EXO V3 module. The EXO V3 module improves
 
   - In Exchange Online PowerShell, virtually all of the available remote PowerShell cmdlets are backed by the REST API.
 
-    In Exchange Online PowerShell, REST API connections are used by default. You need to use the _UseRPSSession_ switch in the **Connect-ExchangeOnline** command to access cmdlets in remote PowerShell mode.
+  - In Security & Compliance Center PowerShell using v3.2.0-Preview4 or later of the module, many, but not all of the available remote PowerShell cmdlets are backed by the REST API.
 
-  - In Security & Compliance Center PowerShell using v3.2.0-Preview3 of the module, many of the available remote PowerShell cmdlets are backed by the REST API.
-
-    In Security & Compliance Center PowerShell, remote PowerShell connections are used by default. You need to use `-UseRPSSession:$false` to access cmdlets in REST API mode. This behavior will change to match **Connect-ExchangeOnline** in a later version of the module as more Security & Compliance cmdlets are available in REST API mode.
+  - In Exchange Online PowerShell and in Security & Compliance PowerShell, REST API connections are used by default. You need to use the _UseRPSSession_ switch in the **Connect-ExchangeOnline** or **Connect-IPPSSession** command to access cmdlets in remote PowerShell mode.
 
 - Consider the following items if you connect to Exchange Online PowerShell or Security & Compliance PowerShell in remote PowerShell mode:
   - [Basic authentication in WinRM](#turn-on-basic-authentication-in-winrm) is required on your client computer.
diff --git a/exchange/docs-conceptual/whats-new-in-the-exo-module.md b/exchange/docs-conceptual/whats-new-in-the-exo-module.md
@@ -22,6 +22,15 @@ description: "Learn about the new features and functionality available in the la
 
 This article lists new features in the Exchange Online PowerShell module that's used for connecting to Exchange Online PowerShell, Security & Compliance PowerShell, and standalone Exchange Online Protection (EOP) PowerShell. Features that are currently in preview are denoted with **(preview)**.
 
+## May 2023
+
+- [Version 3.2.0-Preview4](https://www.powershellgallery.com/packages/ExchangeOnlineManagement/3.2.0-Preview4) has been released.
+
+  This version supports the Preview of Security & Compliance cmdlets backed by the REST API. Some, but not all cmdlets are supported. Basic authentication in WinRM is not required in Security & Compliance PowerShell for REST API cmdlets.
+
+  > [!NOTE]
+  > The default value of the _UseRPSSession_ switch in **Connect-IPSSession** is now the same as **Connect-ExchangeOnline**. To connect in REST API mode, don't use the _UseRPSSession_ switch in the **Connect-IPPSSession** command. To connect using remote PowerShell mode (which requires [Basic authentication in WinRM](exchange-online-powershell-v2.md#turn-on-basic-authentication-in-winrm)), use the _UseRPSSession_ switch in the **Connect-IPPSSession** command.
+
 ## April 2023
 
 - [Version 3.2.0-Preview3](https://www.powershellgallery.com/packages/ExchangeOnlineManagement/3.2.0-Preview3) has been released.
diff --git a/exchange/exchange-ps/exchange/Connect-ExchangeOnline.md b/exchange/exchange-ps/exchange/Connect-ExchangeOnline.md
@@ -15,7 +15,7 @@ ms.reviewer:
 ## SYNOPSIS
 This cmdlet is available only in the Exchange Online PowerShell module. For more information, see [About the Exchange Online PowerShell module](https://aka.ms/exov3-module).
 
-Use the Connect-ExchangeOnline cmdlet in the Exchange Online PowerShell module to connect to Exchange Online PowerShell or standalone Exchange Online Protection PowerShell using modern authentication. This cmdlet works for MFA or non-MFA enabled accounts.
+Use the Connect-ExchangeOnline cmdlet in the Exchange Online PowerShell module to connect to Exchange Online PowerShell or standalone Exchange Online Protection PowerShell using modern authentication. This cmdlet works for accounts with or without multi-factor authentication (MFA).
 
 To connect to Security & Compliance PowerShell, use the [Connect-IPPSSession](https://learn.microsoft.com/powershell/module/exchange/connect-ippssession) cmdlet.
 
@@ -52,6 +52,7 @@ Connect-ExchangeOnline
  [-PageSize <UInt32>]
  [-ShowBanner]
  [-ShowProgress <Boolean>]
+ [-SigningCertificate <X509Certificate2>]
  [-SkipLoadingFormatData]
  [-TrackPerformance <Boolean>]
  [-UseMultithreading <Boolean>]
@@ -656,6 +657,28 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
+### -SigningCertificate
+**Note**: This parameter is available in version 3.2.0-Preview4 or later of the module.
+
+The SigningCertificate parameter specifies the client certificate that's used to sign the format files (\*.Format.ps1xml) or script module files (.psm1) in the temporary module that Connect-ExchangeOnline creates.
+
+A valid value for this parameter is a variable that contains the certificate, or a command or expression that gets the certificate.
+
+To find the certificate, use the Get-PfxCertificate cmdlet in the Microsoft.PowerShell.Security module or use the Get-ChildItem cmdlet in the certificate (Cert:) drive. If the certificate isn't valid or doesn't have sufficient authority, the command will fail.
+
+```yaml
+Type: X509Certificate2
+Parameter Sets: (All)
+Aliases:
+Applicable: Exchange Online
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
 ### -SkipLoadingFormatData
 The SkipLoadingFormatData switch avoids downloading the format data for REST API connections. You don't need to specify a value with this switch.
 
diff --git a/exchange/exchange-ps/exchange/Connect-IPPSSession.md b/exchange/exchange-ps/exchange/Connect-IPPSSession.md
@@ -17,7 +17,7 @@ This cmdlet is available only in the Exchange Online PowerShell module. For more
 
 Use the Connect-IPPSSession cmdlet in the Exchange Online PowerShell module to connect to Security & Compliance PowerShell PowerShell using modern authentication. The cmdlet works for MFA or non-MFA enabled accounts.
 
-**Note**: Version 3.2.0-Preview3 or later of the module supports REST API mode for most Security & Compliance PowerShell cmdlets (Basic authentication in WinRM on the local computer isn't required for REST API mode). For more information, see [Prerequisites for the Exchange Online PowerShell module](https://learn.microsoft.com/powershell/exchange/exchange-online-powershell-v2#prerequisites-for-the-exchange-online-powershell-module).
+**Note**: Version 3.2.0-Preview4 or later of the module supports REST API mode for most Security & Compliance PowerShell cmdlets (Basic authentication in WinRM on the local computer isn't required for REST API mode). For more information, see [Prerequisites for the Exchange Online PowerShell module](https://learn.microsoft.com/powershell/exchange/exchange-online-powershell-v2#prerequisites-for-the-exchange-online-powershell-module).
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
@@ -55,15 +55,15 @@ For detailed connection instructions, including prerequisites, see [Connect to S
 Connect-IPPSSession -UserPrincipalName michelle@contoso.onmicrosoft.com
 ```
 
-This example connects to Security & Compliance PowerShell in a Microsoft 365 organization. You're prompted for the password of the michelle@contoso.onmicrosoft.com account. In v3.2.0-Preview3 of the module, we're connecting in remote PowerShell mode, so Basic authentication in WinRM is required on the local computer.
+This example connects to Security & Compliance PowerShell using the specified account and modern authentication, with or without MFA. In v3.2.0-Preview4 or later of the module, we're connecting in REST API mode, so Basic authentication in WinRM isn't required on the local computer.
 
 
 ### Example 2
 ```powershell
-Connect-IPPSSession -UserPrincipalName michelle@contoso.onmicrosoft.com -UseRPSSession:$false
+Connect-IPPSSession -UserPrincipalName michelle@contoso.onmicrosoft.com -UseRPSSession
 ```
 
-This example connects to Security & Compliance using modern authentication, with or without MFA. In v3.2.0-Preview3 of the module, we're connecting in REST API mode, so Basic authentication in WinRM isn't required on the local computer.
+This example connects to Security & Compliance PowerShell using the specified account and modern authentication, with or without MFA. In v3.2.0-Preview4 or later of the module, we're connecting in remote PowerShell mode, so Basic authentication in WinRM is required on the local computer.
 
 ### Example 3
 ```powershell
@@ -396,11 +396,13 @@ Accept wildcard characters: False
 ```
 
 ### -UseRPSSession
-This parameter is available in version 3.2.0-Preview3 or later of the module.
+This parameter is available in version 3.2.0-Preview4 or later of the module.
 
-The UseRPSSession switch allows you to connect to Security & Compliance PowerShell using REST API mode. To connect to Security & Compliance PowerShell in REST API mode, use this exact syntax: `-UseRPSSession:$false`.
+The UseRPSSession switch allows you to connect to Security & Compliance PowerShell using traditional remote PowerShell access to all cmdlets. You don't need to specify a value with this switch.
 
-If you don't use this switch, you connect in traditional remote PowerShell access mode, and Basic authentication in WinRM is required on your local computer. For more information, see [Prerequisites in the Exchange Online PowerShell module](https://aka.ms/exov3-module#turn-on-basic-authentication-in-winrm).
+This switch requires that Basic authentication is enabled in WinRM on the local computer. For more information, see [Turn on Basic authentication in WinRM](https://aka.ms/exov3-module#turn-on-basic-authentication-in-winrm).
+
+If you don't use this switch, Basic authentication in WinRM is not required.
 
 ```yaml
 Type: SwitchParameter
@@ -410,7 +412,7 @@ Applicable: Exchange Online
 
 Required: False
 Position: Named
-Default value: True
+Default value: False
 Accept pipeline input: False
 Accept wildcard characters: False
 ```
diff --git a/exchange/exchange-ps/exchange/Get-DefaultTenantMyAnalyticsFeatureConfig.md b/exchange/exchange-ps/exchange/Get-DefaultTenantMyAnalyticsFeatureConfig.md
@@ -22,7 +22,7 @@ For information about the parameter sets in the Syntax section below, see [Excha
 ## SYNTAX
 
 ```
-Get-DefaultTenantMyAnalyticsFeatureConfig [-ResultSize <Unlimited]>] [<CommonParameters>]
+Get-DefaultTenantMyAnalyticsFeatureConfig [-ResultSize <Unlimited>] [<CommonParameters>]
 ```
 
 ## DESCRIPTION
@@ -34,7 +34,7 @@ To run this cmdlet, you need to be a member of one of the following directory ro
 - Exchange Administrator
 - Insights Administrator
 
-For more information, see, see [Azure AD built-in roles](https://learn.microsoft.com/azure/active-directory/roles/permissions-reference).
+For more information, see [Azure AD built-in roles](https://learn.microsoft.com/azure/active-directory/roles/permissions-reference).
 
 ## EXAMPLES
 
@@ -72,8 +72,6 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable
 
 ## NOTES
 
-We're in the process of verifying that this cmdlet works for guest user, DAP, and GDAP scenarios.
-
 ## RELATED LINKS
 
 [Deploy personal insights](https://learn.microsoft.com/viva/insights/personal/setup/deployment-guide)
diff --git a/exchange/exchange-ps/exchange/Set-DefaultTenantMyAnalyticsFeatureConfig.md b/exchange/exchange-ps/exchange/Set-DefaultTenantMyAnalyticsFeatureConfig.md
@@ -23,7 +23,6 @@ For information about the parameter sets in the Syntax section below, see [Excha
 
 ```
 Set-DefaultTenantMyAnalyticsFeatureConfig
- [-PrivacyMode <String>]
  [-Feature <String>]
  [-IsEnabled <Boolean>]
  [-ResultSize <Unlimited>]
@@ -40,40 +39,25 @@ To run this cmdlet, you need to be a member of one of the following directory ro
 - Exchange Administrator
 - Insights Administrator
 
-For more information, see, see [Azure AD built-in roles](https://learn.microsoft.com/azure/active-directory/roles/permissions-reference).
+For more information, see [Azure AD built-in roles](https://learn.microsoft.com/azure/active-directory/roles/permissions-reference).
 
 ## EXAMPLES
 
 ### Example 1
 ```powershell
-Set-DefaultTenantMyAnalyticsFeatureConfig -PrivacyMode Opt-in
+Set-DefaultTenantMyAnalyticsFeatureConfig -Feature All -IsEnabled $true
 ```
 
 This example enables all available Viva Insights features for the organization: add-in, dashboard, digest email, meeting effectiveness survey, schedule send suggestions.
 
 ### Example 2
 ```powershell
-Set-DefaultTenantMyAnalyticsFeatureConfig -Feature All -IsEnabled $true
-```
-
-This example also enables all available Viva Insights features for the organization: add-in, dashboard, digest email, meeting effectiveness survey, schedule send suggestions.
-
-### Example 3
-```powershell
 Set-DefaultTenantMyAnalyticsFeatureConfig -Feature Add-in -IsEnabled $false
 ```
 
 This example disables Viva Insight add-in feature for the organization.
 
-### Example 4
-```powershell
-Set-DefaultTenantMyAnalyticsFeatureConfig -PrivacyMode Opt-out -Feature Add-in -IsEnabled $true
-```
-
-This example enables the Viva Insight add-in feature for the organization while disabling the other features.
-
-
-### Example 5
+### Example 3
 ```powershell
 Set-DefaultTenantMyAnalyticsFeatureConfig -Feature Meeting-Effectiveness-Survey-Sampling-Rate -SamplingRate 0.2
 ```
@@ -126,34 +110,6 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
-### -PrivacyMode
-The PrivacyMode parameter enables or disables all of the available Viva Insights features in this cmdlet:
-
-- Add-in
-- Digest email
-- Dashboard
-- Meeting effectiveness survey
-- Schedule send suggestions
-
-Valid values for this parameter are:
-
-- Opt-in: The features are enabled.
-- Opt-out: The features are disabled.
-
-```yaml
-Type: String
-Parameter Sets: (All)
-Aliases:
-Accepted values: Opt-in, Opt-out
-Applicable: Exchange Online
-
-Required: False
-Position: Named
-Default value: None
-Accept pipeline input: False
-Accept wildcard characters: False
-```
-
 ### -ResultSize
 This parameter is reserved for internal Microsoft use.
 
@@ -197,8 +153,6 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable
 
 ## NOTES
 
-We're in the process of verifying that this cmdlet works for guest user, DAP, and GDAP scenarios.
-
 ## RELATED LINKS
 
 [Deploy personal insights](https://learn.microsoft.com/viva/insights/personal/setup/deployment-guide)
