Merging changes synced from https://github.com/MicrosoftDocs/OfficeDo…

…cs-Support-pr (branch live)

.openpublishing.redirection.json

@@ -6203,6 +6203,11 @@
       "source_path": "Viva/learning/provider-content-ingestion-errors.md",
       "redirect_url": "/previous-versions/troubleshoot/content-retirement",
       "redirect_document_id": false
+    },
+    {
+      "source_path": "Microsoft365/compliance/holds/litigation-hold-mailbox-not-turn-into-inactive.md",
+      "redirect_url": "/exchange/troubleshoot/user-and-shared-mailboxes/litigation-hold-mailbox-not-turn-into-inactive",
+      "redirect_document_id": false
     }
   ]
 }

Exchange/ExchangeOnline/onlinetoc/toc.yml

@@ -613,7 +613,7 @@
           href: ../public-folders/pf-migration-fails-sourcepfprimarymailboxguid.md
         - name: '"Number of public folder mailboxes cannot exceed more than 100" error'
           href: ../public-folders/migration-batch-error-too-many-public-folders.md
-        - name: Permissions and settings don't propagate in EAC
+        - name: Permissions and settings don't propagate to all subfolders
           href: ../public-folders/permissions-settings-not-propagate-eac.md
         - name: Public folder couldn't be mail-enabled
           href: ../public-folders/public-folder-not-be-mail-enabled.md
@@ -669,6 +669,8 @@
           href: ../user-and-shared-mailboxes/could-not-find-database-running-cmdlets-for-different-region-mailbox.md
         - name: Enable or disable POP3, IMAP, MAPI, OWA or ActiveSync
           href: ../user-and-shared-mailboxes/pop3-imap-owa-activesync-office-365.md
+        - name: Errors after unassigning a user license
+          href: ../user-and-shared-mailboxes/litigation-hold-mailbox-not-turn-into-inactive.md
         - name: How to access other user's mailboxes
           href: ../user-and-shared-mailboxes/how-to-access-other-mailboxes.md
         - name: How to create and manage resource mailboxes

Exchange/ExchangeOnline/public-folders/permissions-settings-not-propagate-eac.md

@@ -1,145 +1,126 @@
 ---
-title: Public folder permissions and settings don't propagate to subfolders in the Exchange admin center (EAC)
-description: When you apply permissions to a public folder and its subfolders in the EAC, the permissions aren't applied to some or all subfolders. When you apply other settings, you receive errors.
+title: Public folder permissions and settings don't propagate to all subfolders
+description: Provides workarounds for an issue in which the EAC doesn't apply public folder permissions or settings on all subfolders.
 author: cloud-writer
 ms.author: meerak
 manager: dcscontentpm
 audience: ITPro
 ms.topic: troubleshooting
-ms.custom: 
+ms.custom:
   - sap:Groups, Lists, Contacts, Public Folders
   - Exchange Online
-  - CI 150274
   - CSSTroubleshoot
-ms.reviewer: batre, v-six
-appliesto: 
+  - CI 2580
+ms.reviewer: batre, meerak, v-shorestris
+appliesto:
   - Exchange Online
-  - Exchange Server 2013
-  - Exchange Server 2016
   - Exchange Server 2019
-search.appverid: 
-  - MET150
-ms.date: 07/17/2024
+  - Exchange Server 2016
+search.appverid: MET150
+ms.date: 12/04/2024
 ---
-# Public folder permissions and settings don't propagate in EAC
 
-When you use the Exchange admin center (EAC) to apply permissions or settings to a public folder and its subfolders, the actions don't finish, or you experience errors. This article describes the following issues that affect common tasks, and provides workarounds to complete the tasks by using PowerShell.
+# Public folder permissions and settings don't propagate to all subfolders
+
+You try to use the Exchange admin center (EAC) to update the permissions or other settings of a public folder and all its subfolders. However, you encounter any of the following issues:
+
+- Microsoft Exchange Server (on-premises):
+   - The EAC doesn't apply your changes to all subfolders.
+   - The EAC displays an error message and the operation fails.
 
-- [Permissions not applied to some or all subfolders](#permissions-not-applied-to-some-or-all-subfolders)
-- [The read and unread setting not applied](#the-read-and-unread-setting-not-applied)
-- [Age limit settings not applied to subfolders](#age-limit-settings-not-applied-to-subfolders)
+- Microsoft Exchange Online:
+   - The EAC doesn't provide an option to apply your changes to subfolders.
 
-## Permissions not applied to some or all subfolders
+The following sections provide PowerShell workarounds for multiple scenarios.
 
-When you apply permissions to a public folder and its subfolders by selecting the **Apply changes to this public folder and all its subfolders** check box in the EAC, the permissions aren't applied to some or all subfolders.
+## Permissions aren't applied to all subfolders
 
-:::image type="content" source="media/permissions-settings-not-propagate-eac/public-folder-permission.png" alt-text="Screenshot of applying permissions to a public folder and its subfolders.":::
+The EAC in Exchange Online doesn't provide an option to update subfolders when you change permissions on a public folder. This functionality is by design.
 
-The issue occurs if the parent folder and its subfolders are in different public folder mailboxes.
+The EAC in Exchange Server provides an option to **Apply changes to this public folder and all its subfolders** when you update permissions on a public folder. However, for subfolders that are in a different public folder mailbox than the parent public folder, the operation might silently fail or not work reliably, depending on the number of public folder mailboxes in your organization.
 
 ### Workaround
 
-To work around this issue, follow these steps:
+Select one of the following workarounds, depending on the Exchange environment for the affected public folders:
 
-1. Open PowerShell in the Exchange environment where the public folder is active. You can do this in either [Exchange Server (on-premises)](/powershell/exchange/open-the-exchange-management-shell?view=exchange-ps&preserve-view=true) or [Exchange Online](/powershell/exchange/connect-to-exchange-online-powershell?view=exchange-ps&preserve-view=true).
-1. Run the [Update-PublicFolderPermissions.ps1](https://www.microsoft.com/download/details.aspx?id=48689) script by specifying the parameters that are shown in the following example:
+- For public folders in Exchange Online, run the [Update-PublicFolderPermissions.ps1](https://aka.ms/PFPermissionScript) script in [Exchange Online PowerShell](/powershell/exchange/connect-to-exchange-online-powershell). Include the PowerShell parameters that are shown in the following example:
 
-   ```powershell
-   .\Update-PublicFolderPermissions.ps1 -IncludeFolders "\MyFolder" -AccessRights "Owner" -Users "John", "Administrator" -Recurse -Confirm:$false
+   ```PowerShell
+   .\Update-PublicFolderPermissions.ps1 -Users user1@contoso.com -AccessRights Owner -IncludeFolders "\FolderA" -Recurse -Confirm:$false
    ```
 
-   This example script does the following:
-
-   - Replaces the current client permissions on the "_\MyFolder_" public folder and all its child folders for users "John" and "Administrator".
-   - Grants "Owner" access rights to the users.
-   - Doesn't request confirmation from the user.
+   This command grants `user1@contoso.com` the Owner role on the `\FolderA` public folder and its entire subtree.
 
-   The script has detailed help documentation. To view the documentation for the script, run the following command:
+- For public folders in Exchange Server, run the [Update-PublicFolderPermissions.ps1](https://www.microsoft.com/download/details.aspx?id=48689) script in the Exchange Management Shell (EMS). Include the PowerShell parameters that are shown in the following example:
 
-   ```powershell
-   Get-Help .\Update-PublicFolderPermissions.ps1 -Full
+   ```PowerShell
+   .\Update-PublicFolderPermissions.ps1 -IncludeFolders "\FolderA" -AccessRights "Owner" -Users "user1@contoso.com", "user2@contoso.com" -Recurse -Confirm:$false
    ```
 
-## The read and unread setting not applied
+   This command grants `user1@contoso.com` and `user2@contoso.com` the Owner role on the `\FolderA` public folder and its entire subtree.
+
+## Maintain per-user read setting isn't applied to all subfolders
 
-When you select the **Apply the read and unread setting to this folder and all its subfolders** check box on a parent public folder in the EAC, you receive the following error message:
+The EAC in Exchange Online doesn't provide an option to update the **Maintain per-user** **read and unread information** setting.
 
-> The operation couldn't be performed because '\public folder identity' couldn't be found.
+The EAC in Exchange Server provides an option to **Apply changes to this public folder and all its subfolders** when you update the **Maintain per-user** **read and unread information** setting for a public folder. However, the operation might fail and return the following error message:
 
-:::image type="content" source="media/permissions-settings-not-propagate-eac/public-folder-error.png" alt-text="Screenshot of the error when applying read and unread setting.":::
+> The operation couldn't be performed because '\<\public folder\>' couldn't be found.
 
 ### Workaround
 
 To work around this issue, follow these steps:
 
-1. Open PowerShell in the Exchange environment where the public folder is active, either in [Exchange Server (on-premises)](/powershell/exchange/open-the-exchange-management-shell?view=exchange-ps&preserve-view=true) or [Exchange Online](/powershell/exchange/connect-to-exchange-online-powershell?view=exchange-ps&preserve-view=true).
-1. Apply read and unread information tracking on the parent public folder by running the following cmdlet to set the `PerUserReadStateEnabled` value to **True**:
+1. Open PowerShell in [Exchange Server](/powershell/exchange/open-the-exchange-management-shell) or [Exchange Online](/powershell/exchange/connect-to-exchange-online-powershell), depending on the Exchange environment in which the public folders are active.
 
-   ```powershell
-   Set-PublicFolder -Identity "<\PF>" -PerUserReadStateEnabled $True
-   ```
-
-   **Note**: Replace \<\PF> with your parent public folder identity.
-1. Apply read and unread information tracking on the child public folders by running the following cmdlet to set the `PerUserReadStateEnabled` value to **True** or **False** (depending on your requirement):
+2. Run the following cmdlet. The cmdlet uses the [PerUserReadStateEnabled](/powershell/module/exchange/set-publicfolder#-peruserreadstateenabled) parameter to apply a **Maintain per-user read and unread information** setting for the parent public folder and all child public folders. Set the parameter value to `$true` or `$false`, depending on your requirement.
 
-   ```powershell
-   Get-PublicFolder "<\PF>" -Recurse -ResultSize Unlimited | Set-PublicFolder -PerUserReadStateEnabled:<$True or $False>
+   ```PowerShell
+   Get-PublicFolder -Identity "<\ParentPF>" -Recurse -ResultSize Unlimited | Set-PublicFolder -PerUserReadStateEnabled <$true or $false>
    ```
 
-   **Note**: Replace \<\PF> with your parent public folder identity.
+   **Note**: Replace \<\ParentPF\> with the identity of the parent public folder.
 
-## Age limit settings not applied to subfolders
+## Age limit setting isn't applied to subfolders
 
-When you apply age limit settings to a public folder and its subfolders by selecting the **Apply setting to this folder and all its subfolders** check box in the EAC, you receive the following error message:
+The EAC in Exchange Online doesn't provide an option to update subfolders when you change the **Age limit for folder content** setting for a public folder.
 
-> The operation couldn't be performed because '\public folder identity' couldn't be found.
+The EAC in Exchange Server provides an option to **Apply changes to this public folder and all its subfolders** when you update the **Age limit for folder content** setting for a public folder. However, the operation might fail and return the following error message:
 
-:::image type="content" source="media/permissions-settings-not-propagate-eac/set-age-limit-error.png" alt-text="Screenshot of the error when you apply age limit settings.":::
+> The operation couldn't be performed because '\<\public folder\>' couldn't be found.
 
 ### Workaround
 
 To work around this issue, follow these steps:
 
-1. Open PowerShell in the Exchange environment where the public folder is active, either in [Exchange Server (on-premises)](/powershell/exchange/open-the-exchange-management-shell?view=exchange-ps&preserve-view=true) or [Exchange Online](/powershell/exchange/connect-to-exchange-online-powershell?view=exchange-ps&preserve-view=true).
-2. Run the following cmdlet to apply age limit settings to subfolders:
+1. Open PowerShell in [Exchange Server](/powershell/exchange/open-the-exchange-management-shell) or [Exchange Online](/powershell/exchange/connect-to-exchange-online-powershell), depending on the Exchange environment in which the public folders are active.
 
-   ```powershell
-   Get-PublicFolder "<\ParentPF>" -Recurse -ResultSize Unlimited | Set-PublicFolder -AgeLimit <newagelimit>
+2. Run the following cmdlet. The cmdlet uses the [AgeLimit](/powershell/module/exchange/set-publicfolder#-agelimit) parameter to apply an **Age limit for folder content** setting on the parent public folder and all child public folders. For example, set the parameter value to `10.00:00:00` to specify 10 days.
+
+   ```PowerShell
+   Get-PublicFolder "<\ParentPF>" -Recurse -ResultSize Unlimited | Set-PublicFolder -AgeLimit <age limit>
    ```
-
-   **Note**: Replace \<\ParentPF> with your parent public folder identity.
 
-   For example, the following command applies an age limit of 10 days to all subfolders under Root1:
+   **Note**: Replace \<\ParentPF\> with the identity of the parent public folder.
 
-   ```powershell
-   Get-PublicFolder \Root1 -Recurse -ResultSize Unlimited | foreach {Set-PublicFolder -Identity $_.identity -AgeLimit "10.00:00:00"}
-   ```
+## Retain deleted items setting isn't applied to subfolders
 
-## RetainDeletedItemsFor settings not applied to subfolders
+The EAC in Exchange Online doesn't provide an option to update subfolders when you change the **Retain deleted items** setting for a public folder.
 
-When you apply RetainDeletedItemsFor settings to a public folder and its subfolders by selecting the **Apply setting to this folder and all its subfolders** check box in the EAC, you receive the following error message:
+The EAC in Exchange Server provides an option to **Apply changes to this public folder and all its subfolders** when you update the **Retain deleted items** setting for a public folder. However, the operation might fail and return the following error message:
 
-> The operation couldn't be performed because '\public folder identity' couldn't be found.
+> The operation couldn't be performed because '\<\public folder\>' couldn't be found.
 
 ### Workaround
 
 To work around this issue, follow these steps:
 
-1. Open PowerShell in the Exchange environment where the public folder is active, either in [Exchange Server (on-premises)](/powershell/exchange/open-the-exchange-management-shell?view=exchange-ps&preserve-view=true) or [Exchange Online](/powershell/exchange/connect-to-exchange-online-powershell?view=exchange-ps&preserve-view=true).
-2. Run the following cmdlet to apply RetainDeletedItemsFor settings to subfolders:
-
-   ```powershell
-   Get-PublicFolder "<\ParentPF>" -Recurse  -ResultSize Unlimited | Set-PublicFolder -RetainDeletedItemsFor "<newRetainDeletedItemsFor>"
-   ```
-
-   **Note**: Replace \<\ParentPF> with your parent public folder identity.
+1. Open PowerShell in [Exchange Server](/powershell/exchange/open-the-exchange-management-shell) or [Exchange Online](/powershell/exchange/connect-to-exchange-online-powershell), depending on the Exchange environment in which the public folders are active.
 
-   For example, the following command applies RetainDeletedItemsFor 10 days to all subfolders under Root1:
+2. Run the following cmdlet. The cmdlet uses the [RetainDeletedItemsFor](/powershell/module/exchange/set-publicfolder#-retaindeleteditemsfor) parameter to apply a **Retain deleted items** setting on the parent public folder and all child public folders. Set the parameter value depending on your requirement. For example, set the value to `30.00:00:00` to specify 30 days.
 
-   ```powershell
-   Get-PublicFolder \Root1 -Recurse -ResultSize Unlimited | Set-PublicFolder -RetainDeletedItemsFor "10.00:00:00"
+   ```PowerShell
+   Get-PublicFolder "<\ParentPF>" -Recurse -ResultSize Unlimited | Set-PublicFolder -RetainDeletedItemsFor <retention period>
    ```
-
-## Status
 
-Microsoft is aware of these issues and will post more information in this article when a fix becomes available.
+   **Note**: Replace \<\ParentPF\> with the identity of the parent public folder.