Merge branch 'master' into patch-3

Author: Kateyanne

exchange/docs-conceptual/cmdlet-property-sets.md

@@ -27,6 +27,8 @@ For more information about filtering in the EXO V2 module, see [Filters in the E
 
 The available property sets for the **Get-EXOCasMailbox** cmdlet and the properties they contain are described in the following table:
 
+<br>
+
 ****
 
 |PropertySet|Properties|
@@ -56,6 +58,10 @@ For more information, see:
 
 The available property sets for the **Get-EXOMailbox** cmdlet and the properties they contain are described in the following table:
 
+<br>
+
+****
+
 |PropertySet|Properties|
 |---|---|
 |**Minimum**|Alias <br> DisplayName <br> DistinguishedName <br> EmailAddresses <br> ExchangeVersion <br> ExternalDirectoryObjectId <br> Guid <br> Id <br> Name <br> OrganizationId <br> PrimarySmtpAddress <br> RecipientType <br> RecipientTypeDetails <br> UserPrincipalName|
@@ -94,6 +100,8 @@ For more information, see:
 
 The available property sets for the **Get-EXOMailboxStatistics** cmdlet and the properties they contain are described in the following table:
 
+<br>
+
 ****
 
 |PropertySet|Properties|
@@ -111,6 +119,8 @@ For more information, see:
 
 The available property sets for the **Get-EXORecipient** cmdlet and the properties they contain are described in the following table:
 
+<br>
+
 ****
 
 |PropertySet|Properties|

exchange/docs-conceptual/exchange-cmdlet-syntax.md

@@ -27,6 +27,10 @@ This article explains these conventions, and also the syntax that's required to
 
 Exchange PowerShell help follows conventions that indicate what's required or optional, and how to enter parameters and values when you run a command. These command conventions are listed in the following table.
 
+<br>
+
+****
+
 |Symbol|Description|
 |---|---|
 |`-`|A hyphen indicates a parameter. For example, `-Identity`.|
@@ -107,6 +111,10 @@ If you enclose the string in single quotation marks, the only special character
 
 The following table shows the valid operators that you can use in an Exchange command. Some of these symbols were also described in the earlier [Command conventions in Exchange PowerShell](#command-conventions-in-exchange-powershell) section. However, these symbols have different meanings when they're used on the command line as operators. For example, the minus sign that's used to indicate a parameter can also be used in a command as a mathematical operator.
 
+<br>
+
+****
+
 |Operator|Description|
 |---|---|
 |`=`|The equal sign is used as an assignment character. The value on the right side of the equal sign is assigned to the variable on the left side of the equal sign. The following characters are also assignment characters: <ul><li>`+=`: Add the value on the right side of the equal sign to the current value that's contained in the variable on the left side of the equal sign.</li><li>`-=`: Subtract the value on the right side of the equal sign from the current value that's contained in the variable on the left side of the equal sign.</li><li>`*=`: Multiply the current value of the variable on the left side of the equal sign by the value that's specified on the right side of the equal sign.</li><li>`/=`: Divide the current value of the variable on the left side of the equal sign by the value that's specified on the right side of the equal sign.</li><li> `%=`: Modify the current value of the variable on the left side of the equal sign by the value that's specified on the right side of the equal sign.</li></ul>|

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

@@ -24,16 +24,14 @@ The Exchange Online PowerShell V2 module (abbreviated as the EXO V2 module) uses
 For connection instructions using the EXO V2 module, see the following articles:
 
 - [Connect to Exchange Online PowerShell](connect-to-exchange-online-powershell.md)
-
 - [Connect to Security & Compliance Center PowerShell](connect-to-scc-powershell.md)
-
 - [Connect to Exchange Online Protection PowerShell](connect-to-exchange-online-protection-powershell.md)
 
 The rest of this article explains how the module works, how to install and maintain the module, and the optimized Exchange Online cmdlets that are available in the module.
 
 ## Report bugs and issues for the EXO V2 module
 
-When you report an issue, be sure to include the log files in your email message. To generate the log files, replace \<Path to store log file\> with the output folder you want, and run the following command:
+When you report an issue at `exocmdletpreview[at]service[dot]microsoft[dot]com`, be sure to include the log files in your email message. To generate the log files, replace \<Path to store log file\> with the output folder you want, and run the following command:
 
 ```powershell
 Connect-ExchangeOnline -EnableErrorReporting -LogDirectoryPath <Path to store log file> -LogLevel All
@@ -49,6 +47,8 @@ The Exchange Online cmdlets in the EXO V2 module are meant to replace their olde
 
 The improved Exchange Online PowerShell cmdlets that are only available in the EXO V2 module are listed in the following table:
 
+<br>
+
 ****
 
 |EXO V2 module cmdlet|Older related cmdlet|
@@ -66,6 +66,8 @@ The improved Exchange Online PowerShell cmdlets that are only available in the E
 
 The connection-related cmdlets that are available in the EXO V2 module are listed in the following table:
 
+<br>
+
 ****
 
 |EXO V2 module cmdlet|Older related cmdlet|
@@ -77,14 +79,20 @@ The connection-related cmdlets that are available in the EXO V2 module are liste
 
 Miscellaneous Exchange Online cmdlets that happen to be in the EXO V2 module are listed in the following table:
 
+<br>
+
 ****
 
 |EXO V2 module cmdlet|Comments|
 |---|---|
-|[Get-MyAnalyticsFeatureConfig](/powershell/module/exchange/get-myanalyticsfeatureconfig)|This cmdlet is available in v2.0.4 or later.|
-|[Set-MyAnalyticsFeatureConfig](/powershell/module/exchange/set-myanalyticsfeatureconfig)|This cmdlet is available in v2.0.4 or later.|
-|[Get-UserBriefingConfig](/powershell/module/exchange/get-userbriefingconfig)|This cmdlet is being replaced by [Get-UserAnalyticsConfig](/powershell/module/exchange/get-useranalyticsconfig).|
-|[Set-UserBriefingConfig](/powershell/module/exchange/set-userbriefingconfig)|This cmdlet is being replaced by [Set-UserAnalyticsConfig](/powershell/module/exchange/set-useranalyticsconfig).|
+|[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-OwnerlessGroupPolicy](/powershell/module/exchange/get-ownerlessgrouppolicy)|Available in v2.0.5-Preview1 or later.|
+|[Get-VivaInsightsSettings](/powershell/module/exchange/get-vivainsightssettings)|Available in v2.0.5-Preview2 or later.|
+|[Set-OwnerlessGroupPolicy](/powershell/module/exchange/set-ownerlessgrouppolicy)|Available in v2.0.5-Preview1 or later.|
+|[Get-UserBriefingConfig](/powershell/module/exchange/get-userbriefingconfig)|Being replaced by [Get-UserAnalyticsConfig](/powershell/module/exchange/get-useranalyticsconfig).|
+|[Set-UserBriefingConfig](/powershell/module/exchange/set-userbriefingconfig)|Being replaced by [Set-UserAnalyticsConfig](/powershell/module/exchange/set-useranalyticsconfig).|
+|[Set-VivaInsightsSettings](/powershell/module/exchange/set-vivainsightssettings)|Available in v2.0.5-Preview2 or later.|
 |
 
 ## Install and maintain the EXO V2 module

exchange/docs-conceptual/filter-properties.md

@@ -61,6 +61,8 @@ The properties that have been _confirmed_ to work with the _Filter_ parameter in
 
 - For filtering considerations for connections using the Exchange Online PowerShell v2 module, see [Filters in the EXO V2 module](filters-v2.md).
 
+<br>
+
 ****
 
 |Property name|LDAP display name|Available on cmdlets|Value|Comments|

exchange/docs-conceptual/filters-v2.md

@@ -33,6 +33,8 @@ Generally, you get much better performance in PowerShell cmdlets with server-sid
 
 Although the EXO V2 module supports the majority of filterable attributes, the following attributes are currently not supported for filtering:
 
+<br>
+
 ****
 
 |Cmdlet|Attribute|LDAP Display Name|

exchange/docs-conceptual/recipient-filters.md

@@ -196,6 +196,8 @@ When creating your own custom OPath filters, consider the following items:
 
   The compatibility of search criteria and the valid characters that you can use to enclose the whole OPath filter are summarized in the following table:
 
+  <br>
+
   ****
 
   |Search value|OPath filter <br> enclosed in <br> double quotation marks|OPath filter <br> enclosed in <br> single quotation marks|OPath filter enclosed in <br> braces|
@@ -235,11 +237,13 @@ When creating your own custom OPath filters, consider the following items:
 
 The following table contains links to articles that will help you learn more about the filterable properties that you can use with Exchange recipient commands.
 
+<br>
+
 ****
 
 |Article|Description|
 |---|---|
 |[Filterable properties for the RecipientFilter parameter on Exchange cmdlets](recipientfilter-properties.md)|Learn more about the filterable properties that are available for the _RecipientFilter_ parameter.|
 |[Filterable properties for the Filter parameter on Exchange cmdlets](filter-properties.md) |Learn more about the filterable properties that are available for the _Filter_ parameter.|
 |[Filters in the EXO V2 module](filters-v2.md)|Learn about the considerations for filters when you connect to Exchange Online PowerShell using the Exchange Online PowerShell V2 module.|
-|
+|

exchange/docs-conceptual/recipientfilter-properties.md

@@ -48,6 +48,8 @@ The recipient properties that have been *confirmed* to work with the _RecipientF
 
 - For filtering considerations for connections using the Exchange Online PowerShell v2 module, see [Filters in the EXO V2 module](filters-v2.md).
 
+<br>
+
 ****
 
 |Property name|LDAP display name|Value|Comments|

exchange/docs-conceptual/v1-module-mfa-connect-to-exo-powershell.md

@@ -100,6 +100,8 @@ You need to do the following steps in a browser that supports ClickOnce (for exa
 
    - The _\<ConnectionUri\>_ and _\<AzureADUri\>_ values depend on the nature of your Microsoft 365 organization as described in the following table:
 
+     <br>
+
      ****
 
      |Microsoft 365 offering|_ConnectionUri_ parameter value|_AzureADAuthorizationEndPointUri_ parameter value|

exchange/docs-conceptual/v1-module-mfa-connect-to-scc-powershell.md

@@ -104,6 +104,8 @@ You need to do the following steps in a browser that supports ClickOnce (for exa
 
    - The _\<ConnectionUri\>_ and _\<AzureADUri\>_ values depend on the location of your Microsoft 365 organization as described in the following table:
 
+     <br>
+
      ****
 
      |Microsoft 365 offering|_ConnectionUri_ parameter value|_AzureADAuthorizationEndPointUri_ parameter value|

exchange/docs-conceptual/values-for-custompropertynames-parameter.md

@@ -23,7 +23,7 @@ The _CustomPropertyNames_ parameter on the [Get-CalendarDiagnosticObjects](/powe
 
 The article describes the valid values for the _CustomPropertyNames_ parameter.
 
-<br><br>
+<br>
 
 ****
 

exchange/exchange-ps/exchange/Connect-ExchangeOnline.md

@@ -155,7 +155,7 @@ Accept wildcard characters: False
 
 The AzureADAuthorizationEndpointUri parameter specifies the Azure AD Authorization endpoint that can issue OAuth2 access tokens. The following Exchange Online PowerShell environments and related values are supported:
 
-- Microsoft 365 or Microsoft 365 GCC: Don't use this parameter.
+- Microsoft 365 or Microsoft 365 GCC: Don't use this parameter. The required value is `https://login.microsoftonline.com/common`, but that's also the default value, so you don't need to use this parameter.
 - Office 365 Germany: `https://login.microsoftonline.de/common`
 - Microsoft 365 GCC High or Microsoft 365 DoD: `https://login.microsoftonline.us/common`
 

exchange/exchange-ps/exchange/Connect-IPPSSession.md

@@ -71,7 +71,7 @@ This example connects to standalone Exchange Online Protection PowerShell in an
 ### -ConnectionUri
 The ConnectionUri parameter specifies the connection endpoint for the remote PowerShell session. The following PowerShell environments and related values are supported:
 
-- Security & Compliance Center PowerShell in Microsoft 365 or Microsoft 365 GCC: Don't use this parameter.
+- Security & Compliance Center PowerShell in Microsoft 365 or Microsoft 365 GCC: Don't use this parameter. The required value is `https://ps.compliance.protection.outlook.com/powershell-liveid/`, but that's also the default value, so you don't need to use this parameter.
 - Security & Compliance Center PowerShell in Office 365 Germany: `https://ps.compliance.protection.outlook.de/PowerShell-LiveID`
 - Security & Compliance Center PowerShell in Microsoft GCC High: `https://ps.compliance.protection.office365.us/powershell-liveid/`
 - Security & Compliance Center PowerShell in Microsoft DoD: `https://l5.ps.compliance.protection.office365.us/powershell-liveid/`
@@ -93,7 +93,7 @@ Accept wildcard characters: False
 ### -AzureADAuthorizationEndpointUri
 The AzureADAuthorizationEndpointUri parameter specifies the Azure AD Authorization endpoint that can issue OAuth2 access tokens. The following PowerShell environments and related values are supported:
 
-- Security & Compliance Center PowerShell in Microsoft 365 or Microsoft 365 GCC: Don't use this parameter.
+- Security & Compliance Center PowerShell in Microsoft 365 or Microsoft 365 GCC: Don't use this parameter. The required value is `https://login.microsoftonline.com/common`, but that's also the default value, so you don't need to use this parameter.
 - Security & Compliance Center PowerShell in Office 365 Germany: `https://login.microsoftonline.de/common`
 - Security & Compliance Center PowerShell in Microsoft GCC High or Microsoft DoD: `https://login.microsoftonline.us/common`
 

exchange/exchange-ps/exchange/Disable-OutlookProtectionRule.md

@@ -12,6 +12,8 @@ ms.reviewer:
 # 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.
 
 Use the Disable-OutlookProtectionRule cmdlet to disable an existing Microsoft Outlook protection rule.

exchange/exchange-ps/exchange/Enable-OutlookProtectionRule.md

@@ -12,6 +12,8 @@ ms.reviewer:
 # 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.
 
 Use the Enable-OutlookProtectionRule cmdlet to enable an existing Outlook protection rule.

exchange/exchange-ps/exchange/Get-AccessToCustomerDataRequest.md

@@ -85,8 +85,8 @@ The CreatedAfter parameter filters the results by the creation date in Coordinat
 
 To specify a date/time value for this parameter, use either of the following options:
 
-- Specify the date/time value in UTC: For example, "2016-05-06 14:30:00z".
-- Specify the date/time value as a formula that converts the date/time in your local time zone to UTC: For example, `(Get-Date "5/6/2016 9:30 AM").ToUniversalTime()`. For more information, see [Get-Date](https://docs.microsoft.com/powershell/module/Microsoft.PowerShell.Utility/Get-Date).
+- Specify the date/time value in UTC: For example, "2021-05-06 14:30:00z".
+- Specify the date/time value as a formula that converts the date/time in your local time zone to UTC: For example, `(Get-Date "5/6/2021 9:30 AM").ToUniversalTime()`. For more information, see [Get-Date](https://docs.microsoft.com/powershell/module/Microsoft.PowerShell.Utility/Get-Date).
 
 ```yaml
 Type: ExDateTime

exchange/exchange-ps/exchange/Get-MigrationUserStatistics.md

@@ -55,10 +55,10 @@ This example displays the number of mailbox items that failed to migrate, which
 
 ### Example 3
 ```powershell
-Get-MigrationUserStatistics -Identity [email protected] -LimitSkippedItemsTo 20 | Format-List SkippedItemCount,SkippedItems
+Get-MigrationUserStatistics -Identity [email protected] -IncludeSkippedItems | Select-Object -ExpandProperty SkippedItems | Format-List DateReceived, Subject
 ```
 
-This example displays results information in the SkippedItems property for a maximum of 20 skipped items.
+This example displays results information in the SkippedItems property.
 
 ### Example 4
 ```powershell

exchange/exchange-ps/exchange/Get-OutlookProtectionRule.md

@@ -12,6 +12,8 @@ ms.reviewer:
 # 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.
 
 Use the Get-OutlookProtectionRule cmdlet to retrieve Microsoft Outlook protection rules configured in an organization.

exchange/exchange-ps/exchange/Get-OwnerlessGroupPolicy.md

@@ -0,0 +1,74 @@
+---
+external help file: Microsoft.Exchange.Management.RestApiClient.dll-Help.xml
+Module Name: ExchangeOnlineManagement
+online version: https://docs.microsoft.com/powershell/module/exchange/get-ownerlessgrouppolicy
+applicable: Exchange Online
+title: Get-OwnerlessGroupPolicy
+schema: 2.0.0
+author: chrisda
+ms.author: chrisda
+---
+
+# Get-OwnerlessGroupPolicy
+
+## SYNOPSIS
+This cmdlet is available only in the Exchange Online PowerShell V2 module. For more information, see [About the Exchange Online PowerShell V2 module](https://docs.microsoft.com/powershell/exchange/exchange-online-powershell-v2).
+
+**Note**: This cmdlet is available only in version 2.0.5-Preview1 or later of the EXO V2 module.
+
+Use the Get-OwnerlessGroupPolicy cmdlet to view the ownerless group policy in Exchange Online.
+
+For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
+
+## SYNTAX
+
+```
+Get-OwnerlessGroupPolicy
+ [-ResultSize <Unlimited>]
+ [<CommonParameters>]
+```
+
+## DESCRIPTION
+Use this cmdlet to verify if the ownerless group policy for Microsoft 365 Groups is enabled or disabled in your organization. You can also view additional parameters as part of the policy, including: sender email address, number of weeks you want to notify active members of ownerless groups, number of members within a ownerless group you want to notify, and specific groups within the tenant on which ownerless group policy is enabled. 
+
+## EXAMPLES
+
+### Example 1
+```powershell
+Get-OwnerlessGroupPolicy
+```
+
+This example returns the settings of the one and only ownerless group policy for Microsoft 365 Groups.
+
+## PARAMETERS
+
+### -ResultSize
+This parameter is reserved for internal Microsoft use.
+
+```yaml
+Type: Unlimited
+Parameter Sets: (All)
+Aliases:
+Applicable: Exchange Online
+
+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/p/?LinkID=113216).
+
+## INPUTS
+
+###  
+
+## OUTPUTS
+
+###  
+
+## NOTES
+
+## RELATED LINKS

exchange/exchange-ps/exchange/Get-SCInsights.md

@@ -61,8 +61,8 @@ The EndDate parameter specifies the end date of the date range.
 
 To specify a date/time value for this parameter, use either of the following options:
 
-- Specify the date/time value in UTC: For example, "2016-05-06 14:30:00z".
-- Specify the date/time value as a formula that converts the date/time in your local time zone to UTC: For example, `(Get-Date "5/6/2016 9:30 AM").ToUniversalTime()`. For more information, see [Get-Date](https://docs.microsoft.com/powershell/module/Microsoft.PowerShell.Utility/Get-Date).
+- Specify the date/time value in UTC: For example, "2021-05-06 14:30:00z".
+- Specify the date/time value as a formula that converts the date/time in your local time zone to UTC: For example, `(Get-Date "5/6/2021 9:30 AM").ToUniversalTime()`. For more information, see [Get-Date](https://docs.microsoft.com/powershell/module/Microsoft.PowerShell.Utility/Get-Date).
 
 ```yaml
 Type: DateTime

exchange/exchange-ps/exchange/Get-TenantAllowBlockListItems.md

@@ -128,7 +128,7 @@ The ExpirationDate parameter filters the results by expiration date in Coordinat
 
 To specify a date/time value for this parameter, use either of the following options:
 
-- Specify the date/time value in UTC: For example, `"2016-05-06 14:30:00z"`.
+- Specify the date/time value in UTC: For example, `"2021-05-06 14:30:00z"`.
 - Specify the date/time value as a formula that converts the date/time in your local time zone to UTC: For example, `(Get-Date "5/6/2020 9:30 AM").ToUniversalTime()`. For more information, see [Get-Date](https://docs.microsoft.com/powershell/module/Microsoft.PowerShell.Utility/Get-Date).
 
 ```yaml