Dataverse Size to be Reduced

(1) Share

Report

Posted on by Jenn_N

We are trying to archive custom activities and attachments from Dataverse to blob storage through Logic Apps or Function Apps to offload dataverse using blob connector then retrieve data back on canvas app.

Is there a better way to accomplish to reduce the dataverse size where custom activities taken up most storage and if long-term reduction policy is not used. What is the best format to archive both custom activities and attachment in blob.

Thanks.

Categories:

Dynamics 365 general

Power Platform integration

I have the same question (0)

All responses (1)

Answers (0)

Suggested answer

Sohail Ahmed 11,086 Super User 2025 Season 2 on at

Like (1)

Report
Dataverse Size to be Reduced

Better Approaches:

Long-term retention policies - Enable in Power Platform Admin Center (simplest solution)

Dataverse archival solution - Native feature for automatic cold storage

Power Automate + Azure Data Lake - More cost-effective than blob storage for large volumes

For Your Current Approach:

Best format: Parquet for activities (efficient compression + queryable)

Attachments: Keep as-is but compress large files

Metadata: Store in separate JSON files for quick retrieval

Retrieval Strategy:

Canvas app: Use custom connector to Azure Function

Pre-load metadata in Dataverse for search, fetch full data on-demand

Cost Optimization:

Use Azure Data Lake Gen2 instead of blob storage

Implement tiered storage (hot/cool/archive)

Recommendation: Start with native Dataverse long-term retention if possible - it's designed exactly for this scenario and requires minimal custom development.

Mark below checkbox to make this answer Verified if it helps you.

Was this reply helpful? Yes No