[CoE Starter Kit - QUESTION] Alto consumo de almacenamiento en la tabla admin_EnvironmentSecurityRolePermissionBase

[Eusemazo]

Does this question already exist in our backlog?

• I have checked and confirm this is a new question.

What is your question?

We have identified that the table [admin_EnvironmentSecurityRolePermissionBase] is consuming a significant amount of storage and shows continuous growth over time.
The goal of this issue is to confirm whether this behavior is expected and to define a supported approach to reduce its size without impacting the tool’s functionality.

Is this growth expected, or is it considered anomalous behavior?

Is there a recommended retention policy for this table?

Which data can be safely deleted or archived without impacting the tool?

Are there automatic cleanup jobs that should be enabled?

Is it recommended to partition, compress, or move part of the data?

Is there official documentation covering this type of maintenance?

What solution are you experiencing the issue with?

Core

What solution version are you using?

4.50.7

What app or flow are you having the issue with?

Dataver

What method are you using to get inventory and telemetry?

None

[harini-2-y]

Hi @Eusemazo ,
Thanks for raising this question!

Is this growth expected, or is it considered anomalous behavior?
Yes — this behavior is expected. The admin_EnvironmentSecurityRolePermissionBase table stores full security‑role permission snapshots each time the Security Role sync runs. The data is insert‑only, so the table will continue to grow over time as more snapshots are collected.

Is there a recommended retention policy for this table?
There is no official retention policy for this specific table. However, most customers retain 30–90 days of data, as only recent snapshots are needed for the CoE dashboards and insights.

Which data can be safely deleted or archived without impacting the tool?
You can safely delete older snapshot records (for example, anything older than 30–90 days based on createdon). Removing historical data does not impact the CoE functionality because the dashboards use only the latest snapshots.

Are there automatic cleanup jobs that should be enabled?
No — the CoE Starter Kit does not include any automatic cleanup jobs for this table. If cleanup is required, you will need to create a Dataverse Bulk Delete job or a scheduled cleanup flow to enforce retention.

Is it recommended to partition, compress, or move part of the data?
Dataverse does not support custom partitioning or compression for this table. The supported approach is:
Delete older rows, and
Optionally archive them externally (such as Azure SQL or Data Lake) before deletion, if long‑term storage is required.

Is there official documentation covering this type of maintenance?
There is currently no dedicated documentation for retention or cleanup of this table. Existing CoE documentation only explains how Security Role tracking works, not how to manage table size or historical snapshot growth.

[Eusemazo]

Hello Harini, thank you very much for your valuable response. Do you have any documentation or guidance on how to remove older data, or on how the data cleanup/purging flow should be designed? Any material or information you can share would be extremely helpful and would contribute greatly to my learning and improvement. Thank you again for your time, support, and assistance. Enviado desde mi iPhone

…

El 12/01/2026, a la(s) 5:09 a.m., harini-2-y ***@***.***> escribió: Are there automatic cleanup jobs that should be enabled? No — the CoE Starter Kit does not include any automatic cleanup jobs for this table. If cleanup is required, you will need to create a Dataverse Bulk Delete job or a scheduled cleanup flow to enforce retention. Is it recommended to partition, compress, or move part of the data? Dataverse does not support custom partitioning or compression for this table. The supported approach is: Delete older rows, and Optionally archive them externally (such as Azure SQL or Data Lake) before deletion, if long‑term storage is required. Is there official documentation covering this type of maintenance? There is currently no dedicated documentation for retention or cleanup of this table. Existing CoE documentation only explains how Security Role tracking works, not how to manage table size or historical snapshot growth.

[harini-2-y]

Hi @Eusemazo ,
Apologies for the late response, and thanks for the follow‑up!

At this time, the CoE Starter Kit does not include official documentation or a built‑in cleanup/purging flow for removing older records from the admin_EnvironmentSecurityRolePermission table.
However, you can still safely implement cleanup using standard Dataverse tools. The recommended approach is:
Dataverse Bulk Delete – Official Microsoft Documentation
You can create a recurring Bulk Delete job to automatically remove older snapshot records (e.g., older than 30–90 days):
https://learn.microsoft.com/power-platform/admin/delete-bulk-records
This is the Microsoft‑supported method for removing large volumes of historical data from Dataverse.

[harini-2-y]

Dear User,
This issue is being closed as the documentation updates have been completed and the related PR has been squash‑merged.
The merged PR includes the full troubleshooting steps and the complete solution for this issue, which you can review at your convenience.
If you experience any further issues or need additional assistance, please feel free to open a new ticket. We are always here to help and happy to support you.