Merge pull request #10345 from MicrosoftDocs/pnghub-patch-5

Update data-retention-overview.md

Author: Mattp123

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

@@ -6,7 +6,7 @@ author: pnghub
 ms.author: gned
 ms.reviewer: matp
 ms.topic: overview
-ms.date: 05/10/2024
+ms.date: 08/02/2024
 ms.custom: template-overview
 ---
 # Dataverse long term data retention overview
@@ -46,7 +46,7 @@ Application admins set up custom policies for a table with criterion to retain d
 
 > [!IMPORTANT]
 > - Once data is retained with Dataverse long term retention it can't be moved back to the Dataverse live (active) application state.
-> - Customers using self-managed encryption key (BYOK) should be aware that long term retained data in the Azure data lake is encrypted with Microsoft managed key. Consider migrating to customer managed key. More information: [Migrate bring-your-own-key environments to customer-managed key](/power-platform/admin/cmk-migrate-from-byok)
+> - You can't use the long term data retention feature with environments that have either self-managed encryption key [bring your own key](/power-platform/admin/cmk-migrate-from-byok) or [customer managed key](/power-platform/admin/cmk-migrate-from-byok) enabled.
 > - When a retention policy is run, the process makes API requests in Microsoft Power Platform. These requests are counted towards the existing API requests available with your plan. More information: [Requests limits and allocations](/power-platform/admin/api-request-limits-allocations)
 
 Dataverse provides read-only access to the retained data via: