Merge branch 'master' into FindTime-chrisda

Author: chrisda

exchange/docs-conceptual/app-only-auth-powershell-v2.md

@@ -193,7 +193,7 @@ Create a self-signed x.509 certificate using one of the following methods:
 
   ```powershell
   # Create certificate
-  $mycert = New-SelfSignedCertificate -DnsName "contoso.org" -CertStoreLocation "cert:\LocalMachine\My" -NotAfter (Get-Date).AddYears(1) -KeySpec KeyExchange
+  $mycert = New-SelfSignedCertificate -DnsName "contoso.org" -CertStoreLocation "cert:\CurrentUser\My" -NotAfter (Get-Date).AddYears(1) -KeySpec KeyExchange
 
   # Export certificate to .pfx file
   $mycert | Export-PfxCertificate -FilePath mycert.pfx -Password $(ConvertTo-SecureString -String "P@ssw0Rd1234" -AsPlainText -Force)

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

@@ -37,6 +37,9 @@ When you report an issue at `exocmdletpreview[at]service[dot]microsoft[dot]com`,
 Connect-ExchangeOnline -EnableErrorReporting -LogDirectoryPath <Path to store log file> -LogLevel All
 ```
 
+> [!NOTE]
+> The latest version of EXO V2 module and 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.
+
 ## How the EXO V2 module works
 
 The module contains a small set of exclusive Exchange Online PowerShell cmdlets that are optimized for bulk data retrieval scenarios (think: thousands and thousands of objects). When you first open the module, you'll only see these exclusive cmdlets. After you [connect to your Exchange Online organization](connect-to-exchange-online-powershell.md), you'll see all of the familiar cmdlets that are available in Exchange Online PowerShell.
@@ -310,13 +313,13 @@ For detailed syntax and parameter information, see [Update-Module](/powershell/m
   - x64:
 
     ```powershell
-    Set-ItemProperty -Path 'HKLM:\SOFTWARE\Wow6432Node\Microsoft.NetFramework\v4.0.30319' -Name 'SchUseStrongCrypto' -Type DWord -Value '1'
+    Set-ItemProperty -Path 'HKLM:\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319' -Name 'SchUseStrongCrypto' -Type DWord -Value '1'
     ```
 
   - x86
 
     ```powershell
-    Set-ItemProperty -Path 'HKLM:\SOFTWARE\Microsoft.NetFramework\v4.0.30319' -Name 'SchUseStrongCrypto' -Type DWord -Value '1'
+    Set-ItemProperty -Path 'HKLM:\SOFTWARE\Microsoft\.NETFramework\v4.0.30319' -Name 'SchUseStrongCrypto' -Type DWord -Value '1'
     ```
 
   For more information, see [SchUseStrongCrypto](/dotnet/framework/network-programming/tls#schusestrongcrypto).
@@ -383,7 +386,18 @@ For more information about filtering in the EXO V2 module, see [Filters in the E
 
 Unless otherwise noted, the current release of the EXO V2 module contains all features of previous releases.
 
-### Current release: Version 2.0.4
+### Current release: Version 2.0.5
+
+- New **Get-OwnerlessGroupPolicy** and **Set-OwnerlessGroupPolicy** cmdlet to manage ownerless Microsoft 365 groups.
+
+  > [!NOTE]
+  > Although the _cmdlets_ are available in the module, the _feature_ is only available to members of a Private Preview.
+
+- New **Get-VivaInsightsSettings** and **Set-VivaInsightsSettings** cmdlets to control user access to Headspace features in Viva Insights.
+
+### Previous releases
+
+#### Version 2.0.4
 
 - PowerShell 7 is officially supported in Windows, Linux, and Apple macOS as described in the [Prerequisites for the EXO V2 module](#prerequisites-for-the-exo-v2-module) section in this article.
 
@@ -397,8 +411,6 @@ Unless otherwise noted, the current release of the EXO V2 module contains all fe
 
 - The interactive sign-in process now uses a more secure method to fetch access tokens using safe reply URLs.
 
-### Previous releases
-
 #### Version 2.0.3
 
 - General availability of certificate based authentication (CBA), which enables using modern authentication in unattended scripting or background automation scenarios. The available certificate storage locations are:

exchange/docs-conceptual/recipientfilter-properties.md

@@ -229,7 +229,7 @@ The recipient properties that have been *confirmed* to work with the _RecipientF
 |_PublicFolderContacts_|_pFContacts_|String (wildcards accepted in dynamic distribution groups).||
 |_PurportedSearchUI_|_msExchPurportedSearchUI_|String (wildcards accepted).||
 |_QueryBaseDN_|_msExchQueryBaseDN_|String (wildcards accepted in dynamic distribution groups).||
-|_RawCanonicalName_|_canonicalName_|String (wildcards accepted).||
+|_RawCanonicalName_|_canonicalName_|String (wildcards accepted).|This property is based on a constructed Active Directory attribute, and does not correctly resolve all members when used in `Get-Recipient -RecipientPreviewFilter`.|
 |_RawExternalEmailAddress_|_targetAddress_|String (wildcards accepted).||
 |_RawName_|_name_|String (wildcards accepted).||
 |_RecipientContainer_|_msExchDynamicDLBaseDN_|String (wildcards accepted).|The Active Directory container or organizational unit (OU) that holds the recipient object.|

exchange/exchange-ps/exchange/Add-IPAllowListEntry.md

@@ -81,10 +81,10 @@ Accept wildcard characters: False
 ```
 
 ### -IPRange
-The IPRange parameter specifies a range of IP addresses to add to the IP Allow list. You can use the following formats:
+The IPRange parameter specifies a range of IP addresses to add to the IP Allow list. Valid values are:
 
-- CIDR IP:192.168.0.1/24
-- IP address range:192.168.0.1-192.168.0.254.
+- IP address range: 192.168.0.1-192.168.0.254.
+- Classless Inter-Domain Routing (CIDR) IP address range: For example, 192.168.0.1/24.
 
 ```yaml
 Type: IPRange

exchange/exchange-ps/exchange/Add-IPBlockListEntry.md

@@ -80,10 +80,10 @@ Accept wildcard characters: False
 ```
 
 ### -IPRange
-The IPRange parameter specifies a range of IP addresses to add to the IP Block list. You can use the following formats:
+The IPRange parameter specifies a range of IP addresses to add to the IP Block list. Valid values are:
 
-- CIDR IP:192.168.0.1/24
-- IP address range:192.168.0.1-192.168.0.254.
+- IP address range: 192.168.0.1-192.168.0.254.
+- Classless Inter-Domain Routing (CIDR) IP address range: 192.168.0.1/24.
 
 ```yaml
 Type: IPRange

exchange/exchange-ps/exchange/Add-MailboxFolderPermission.md

@@ -115,10 +115,10 @@ The roles that are available, along with the permissions that they assign, are d
 - Contributor: CreateItems, FolderVisible
 - Editor: CreateItems, DeleteAllItems, DeleteOwnedItems, EditAllItems, EditOwnedItems, FolderVisible, ReadItems
 - None: FolderVisible
-- NonEditingAuthor: CreateItems, FolderVisible, ReadItems
+- NonEditingAuthor: CreateItems, DeleteOwnedItems, FolderVisible, ReadItems
 - Owner: CreateItems, CreateSubfolders, DeleteAllItems, DeleteOwnedItems, EditAllItems, EditOwnedItems, FolderContact, FolderOwner, FolderVisible, ReadItems
-- PublishingEditor: CreateItems, CreateSubfolders, DeleteAllItems, DeleteOwnedItems, EditAllItems, EditOwnedItems, FolderVisible, ReadItems
 - PublishingAuthor: CreateItems, CreateSubfolders, DeleteOwnedItems, EditOwnedItems, FolderVisible, ReadItems
+- PublishingEditor: CreateItems, CreateSubfolders, DeleteAllItems, DeleteOwnedItems, EditAllItems, EditOwnedItems, FolderVisible, ReadItems
 - Reviewer: FolderVisible, ReadItems
 
 The following roles apply specifically to calendar folders:

exchange/exchange-ps/exchange/Add-PublicFolderClientPermission.md

@@ -75,28 +75,28 @@ You can specify individual folder permissions or roles, which are combinations o
 
 The following individual permissions are available:
 
-- ReadItems: The user has the right to read items within the specified public folder.
 - CreateItems: The user has the right to create items within the specified public folder.
-- EditOwnedItems: The user has the right to edit the items that the user owns in the specified public folder.
+- CreateSubfolders: The user has the right to create subfolders in the specified public folder.
+- DeleteAllItems: The user has the right to delete all items in the specified public folder.
 - DeleteOwnedItems: The user has the right to delete items that the user owns in the specified public folder.
 - EditAllItems: The user has the right to edit all items in the specified public folder.
-- DeleteAllItems: The user has the right to delete all items in the specified public folder.
-- CreateSubfolders: The user has the right to create subfolders in the specified public folder.
-- FolderOwner: The user is the owner of the specified public folder. The user has the right to view and move the public folder and create subfolders. The user can't read items, edit items, delete items, or create items.
+- EditOwnedItems: The user has the right to edit the items that the user owns in the specified public folder.
 - FolderContact: The user is the contact for the specified public folder.
+- FolderOwner: The user is the owner of the specified public folder. The user has the right to view and move the public folder and create subfolders. The user can't read items, edit items, delete items, or create items.
 - FolderVisible: The user can view the specified public folder, but can't read or edit items within the specified public folder.
+- ReadItems: The user has the right to read items within the specified public folder.
 
 In addition to access rights, you can create rights based upon roles, which includes multiple access rights. This parameter accepts the following values for roles:
 
-- None: FolderVisible
-- Owner: CreateItems, ReadItems, CreateSubfolders, FolderOwner, FolderContact, FolderVisible, EditOwnedItems, EditAllItems, DeleteOwnedItems, DeleteAllItems
-- PublishingEditor: CreateItems, ReadItems, CreateSubfolders, FolderVisible, EditOwnedItems, EditAllItems, DeleteOwnedItems, DeleteAllItems
-- Editor: CreateItems, ReadItems, FolderVisible, EditOwnedItems, EditAllItems, DeleteOwnedItems, DeleteAllItems
-- PublishingAuthor: CreateItems, ReadItems, CreateSubfolders, FolderVisible, EditOwnedItems, DeleteOwnedItems
-- Author: CreateItems, ReadItems, FolderVisible, EditOwnedItems, DeleteOwnedItems
-- NonEditingAuthor: CreateItems, ReadItems, FolderVisible
-- Reviewer: ReadItems, FolderVisible
+- Author: CreateItems, DeleteOwnedItems, EditOwnedItems, FolderVisible, ReadItems
 - Contributor: CreateItems, FolderVisible
+- Editor: CreateItems, DeleteAllItems, DeleteOwnedItems, EditAllItems, EditOwnedItems, FolderVisible, ReadItems
+- None: FolderVisible
+- NonEditingAuthor: CreateItems, DeleteOwnedItems, FolderVisible, ReadItems
+- Owner: CreateItems, CreateSubfolders, DeleteAllItems, DeleteOwnedItems, EditAllItems, EditOwnedItems, FolderContact, FolderOwner, FolderVisible, ReadItems
+- PublishingAuthor: CreateItems, CreateSubfolders, DeleteOwnedItems, EditOwnedItems, FolderVisible, ReadItems
+- PublishingEditor: CreateItems, CreateSubfolders, DeleteAllItems, DeleteOwnedItems, EditAllItems, EditOwnedItems, FolderVisible, ReadItems
+- Reviewer: FolderVisible, ReadItems
 
 ```yaml
 Type: MultiValuedProperty

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

@@ -113,9 +113,7 @@ Accept wildcard characters: False
 ```
 
 ### -DelegatedOrganization
-The DelegatedOrganization parameter specifies the customer organization that you want to manage (for example, contosoelectronics.onmicrosoft.com). This parameter only works if the customer organization has agreed to your delegated management via the CSP program.
-
-After you successfully authenticate, the cmdlets in this session are mapped to the customer organization, and all operations in this session are done on the customer organization.
+This parameter is reserved for internal Microsoft use.
 
 ```yaml
 Type: String

exchange/exchange-ps/exchange/Disable-OutlookAnywhere.md

@@ -167,12 +167,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable
 ## INPUTS
 
 ###  
-To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data.
+To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=2081749). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data.
 
 ## OUTPUTS
 
 ###  
-To see the return types, which are also known as output types, that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Output Type field is blank, the cmdlet doesn't return data.
+To see the return types, which are also known as output types, that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=2081749). If the Output Type field is blank, the cmdlet doesn't return data.
 
 ## NOTES
 

exchange/exchange-ps/exchange/Disable-RemoteMailbox.md

@@ -14,7 +14,7 @@ ms.reviewer:
 ## SYNOPSIS
 This cmdlet is available only in on-premises Exchange.
 
-Use the Disable-RemoteMailbox cmdlet to remove mailboxes from the cloud-based service but keep the associated user objects in the on-premises Active Directory.
+Use the Disable-RemoteMailbox cmdlet to remove user mailboxes from the cloud-based service but keep the associated user objects in the on-premises Active Directory.
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://docs.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
@@ -41,7 +41,11 @@ If you want to remove both the cloud-based mailbox and the associated on-premise
 
 Directory synchronization must be configured correctly for a mailbox to be removed from the cloud. Removal of the cloud-based mailbox isn't immediate and depends on the directory synchronization schedule.
 
-**Note**: 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.
+**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.
+- 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://docs.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
 

exchange/exchange-ps/exchange/Disable-SafeAttachmentRule.md

@@ -14,7 +14,7 @@ ms.reviewer:
 ## SYNOPSIS
 This cmdlet is available only in the cloud-based service.
 
-Use the Disable-SafeAttachmentRule cmdlet to disable safe attachment rules in your cloud-based organization.
+Use the Disable-SafeAttachmentRule cmdlet to disable safe attachment rules in your cloud-based organization. This cmdlet is also responsible for disabling complete Safe Attachments policies in the admin center, which consist of the safe attachment rule and the corresponding assigned safe attachment policy in PowerShell.
 
 **Note**: We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Connect to Exchange Online PowerShell](https://docs.microsoft.com/powershell/exchange/connect-to-exchange-online-powershell).
 

exchange/exchange-ps/exchange/Enable-OutlookAnywhere.md

@@ -331,12 +331,12 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable
 ## INPUTS
 
 ###  
-To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data.
+To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=2081749). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data.
 
 ## OUTPUTS
 
 ###  
-To see the return types, which are also known as output types, that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Output Type field is blank, the cmdlet doesn't return data.
+To see the return types, which are also known as output types, that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?LinkId=2081749). If the Output Type field is blank, the cmdlet doesn't return data.
 
 ## NOTES
 

exchange/exchange-ps/exchange/Enable-SafeAttachmentRule.md

@@ -14,7 +14,7 @@ ms.reviewer:
 ## SYNOPSIS
 This cmdlet is available only in the cloud-based service.
 
-Use the Enable-SafeAttachmentRule cmdlet to enable safe attachment rules in your cloud-based organization.
+Use the Enable-SafeAttachmentRule cmdlet to enable safe attachment rules in your cloud-based organization. This cmdlet is also responsible for disabling complete Safe Attachments policies in the admin center, which consist of the safe attachment rule and the corresponding assigned safe attachment policy in PowerShell.
 
 **Note**: We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Connect to Exchange Online PowerShell](https://docs.microsoft.com/powershell/exchange/connect-to-exchange-online-powershell).
 

exchange/exchange-ps/exchange/Get-AdvancedThreatProtectionDocumentDetail.md

@@ -117,7 +117,12 @@ Accept wildcard characters: False
 ```
 
 ### -EventType
-The EventType parameter filters the report by the event type. The event type you specify must correspond to the report. For example, you can only specify "Anti-malware engine" or "Advanced Threat Protection" events for malware reports.
+The EventType parameter filters the report by the event type. Valid values are:
+
+- Advanced Threat Protection
+- Advanced Threat Protection clean
+- Anti-malware engine
+- Anti-malware engine clean
 
 You can specify multiple values separated by commas.
 

exchange/exchange-ps/exchange/Get-AdvancedThreatProtectionDocumentReport.md

@@ -132,7 +132,12 @@ Accept wildcard characters: False
 ```
 
 ### -EventType
-The EventType parameter filters the report by the event type. The event type you specify must correspond to the report. For example, you can only specify "Anti-malware engine" or "Advanced Threat Protection" events for malware reports.
+The EventType parameter filters the report by the event type.  Valid values are:
+
+- Advanced Threat Protection
+- Advanced Threat Protection clean
+- Anti-malware engine
+- Anti-malware engine clean
 
 You can specify multiple values separated by commas.
 

exchange/exchange-ps/exchange/Get-AdvancedThreatProtectionTrafficReport.md

@@ -14,6 +14,8 @@ ms.reviewer:
 ## SYNOPSIS
 This cmdlet is available only in the cloud-based service.
 
+This cmdlet will be deprecated. Use the **Get-MailTrafficATPReport** cmdlet instead.
+
 Use the Get-AdvancedThreatProtectionTrafficReport cmdlet to view the results of Safe Attachments and Safe Links actions in your cloud-based organization for the last 90 days.
 
 **Note**: We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Connect to Exchange Online PowerShell](https://docs.microsoft.com/powershell/exchange/connect-to-exchange-online-powershell).
@@ -177,7 +179,12 @@ Accept wildcard characters: False
 ```
 
 ### -EventType
-The EventType parameter filters the report by the event type. To view the complete list of valid values for this parameter, run the command: `Get-MailFilterListReport -SelectionTarget EventTypes`. The event type you specify must correspond to the report. For example, you can only specify malware filter events for malware reports.
+The EventType parameter filters the report by the event type. Valid values are:
+
+- AdvancedProtectionMalware
+- AtpGoodMail
+
+To view the potential list of valid values for this parameter, run the command: `Get-MailFilterListReport -SelectionTarget EventTypes`. The event type you specify must correspond to the report. For example, you can only specify Microsoft Defender for Office 365 (formerly known as Advanced Threat Protection or ATP) event types for Defender for Office 365 reports.
 
 You can specify multiple values separated by commas.