Live publish for 11 May 2024.

Author: bishalgoswami

powerapps-docs/maker/canvas-apps/media/share-app/guest-my-account.png

@@ -80,7 +80,10 @@ After you share an app for guest access, guests can discover and access apps sha
   - In the Azure public cloud, they're recognized across tenants in guest scenarios because they aren't bound to a specific environment.
   - In Azure national or sovereign clouds, they're recognized across tenants in guest scenarios. More information: [National clouds](/azure/active-directory/develop/authentication-national-cloud), [Azure geographies](https://azure.microsoft.com/global-infrastructure/geographies/#geographies)
   - Licenses are not recognized across tenants in difference Azure clouds.
-  - Not all connectors create connections in the resource tenant by default. 
+  - Not all connectors create connections in the resource tenant by default.
+  - A user that signs in to an app using Azure B2B, won't see their identity information when the go to **My account**. 
+    
+    ![Power Apps Azure B2B user profile known issue](media/share-app/guest-my-account.png "My account")
 
 ## Frequently asked questions
 

powerapps-docs/maker/canvas-apps/share-app-guests.md

@@ -6,7 +6,7 @@ author: pnghub
 ms.author: gned
 ms.reviewer: matp
 ms.topic: overview
-ms.date: 05/01/2024
+ms.date: 05/10/2024
 ms.custom: template-overview
 ---
 # Dataverse long term data retention overview
@@ -125,6 +125,7 @@ When you include your retention policies in a solution, their definitions become
 > [!NOTE]
 > - The data retained by retention policies isn't portable as part of solutions, only the retention policy definitions are. You must run the retention policy in an environment to retain the data in Dataverse long term storage.
 > - Only retention policies created in Power Platform environments can be solution-aware.
+> - When long term retention, is enabled through a solution import process, the related child tables aren't automatically enabled.
 
 You create a solution before you add a retention policy to it. Exporting and importing solutions containing retention policies is the same as with other solution components.
 

powerapps-docs/maker/data-platform/data-retention-overview.md

@@ -6,7 +6,7 @@ ms.author: gned
 ms.reviewer: matp
 ms.service: powerapps
 ms.topic: how-to 
-ms.date: 02/29/2024
+ms.date: 05/10/2024
 ms.custom: template-how-to
 ---
 # Set a data retention policy for a table
@@ -26,6 +26,7 @@ Before you set up a retention policy, enable the parent (root) table for long te
 
 > [!NOTE]
 > When a parent (root) table is enabled for long term retention, all the related child tables are automatically enabled. You can't disable retention for a child table when the parent table is already enabled for retention. For example, assume a custom table and notes table are child tables of the case table. These child tables can't be disabled for retention when the parent case table is enabled. A maker can always disable the parent table for long term retention and separately enable the child tables for retention.
+> However, there's an exception to this related child tables behavior when long term retention is enabled through a solution import process. In this case, the related child tables aren't automatically enabled.
 
 1. Sign into [Power Apps](https://make.powerapps.com/?utm_source=padocs&utm_medium=linkinadoc&utm_campaign=referralsfromdoc), go to **Tables**, and then open the table you want. [!INCLUDE [left-navigation-pane](../../includes/left-navigation-pane.md)]
 1. Select **Properties** on the command bar, expand **Advanced options**, and then select **Enable long term retention**.