Unanswered

Dataverse Storage Best Practices

(0) Share

Report

Posted on by asoguero

Hi All,

I'm working on several solutions that use mainly Power Automate and Power Apps. I'm concerned about Dataverse running out of capacity, specially because all the data that my automations are saving.

I would like to know if there are any official recommendations released by Microsoft on best practices when consuming Dataverse capacity?

Housekeeping
Data rentention policies
Use of external SQL systems
Roles and accesses

Thanks for your help

Please like the post if you find it useful

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (2)

Answers (0)

Shashank Bhide 942 Moderator on at

Like (1)

Report

From cost perspective nothing beats azure storage ($0.15 per GB), however it's not OOB and you need to build some custom work around it.

Was this reply helpful? Yes No
Drew Poggemann 9,287 Most Valuable Professional on at

Like (1)

Report
Hi @asoguero ,

Freeing up Dataverse Storage Space: https://learn.microsoft.com/en-us/power-platform/admin/free-storage-space

Retention Policies (not specifically best practice as this will depend organization by organization, but, good info: https://learn.microsoft.com/en-us/power-apps/maker/data-platform/data-retention-overview

Use of External SQL systems - I know of nothing specific here... I would suggest looking at Fabric / Synapse and when you archive / purge from Dataverse to store the information to a data lake / lakehouse / etc.

Roles and Accessing - Once you move the data out of the Dataverse the security will not be the same. Example is you could have User level security setup for the transactional / master data in Dataverse and if you move this to another type of storage you will need to work through the security model. No best practices I know of here.

Was this reply helpful? Yes No