Skip to content

Commit c4aea10

Browse files
committed
Revised per conversation with PM
1 parent 354ddd5 commit c4aea10

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -49,7 +49,7 @@ Application admins set up custom policies for a table with criterion to retain d
4949

5050
> [!IMPORTANT]
5151
> - Once data is retained in the Dataverse long term (inactive) store it can't be moved back to the Dataverse live (active) data store.
52-
> - Customers that bring own key (BYOK), note that long term retained data in the Dataverse managed data lake is encrypted with Microsoft managed key only.
52+
> - 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)
5353
> - 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)
5454
5555
Dataverse provides read-only access to the retained data via:

0 commit comments

Comments
 (0)