Understanding Mercury Dataverse Storage

This article outlines key information to help your organisation effectively manage Dataverse storage as part of your Mercury deployment: 

• Where Mercury data is stored and key Microsoft terminology 
• How to check current storage capacity and utilisation 
• Who is responsible for maintaining sufficient capacity 
• The consequences of exceeding storage limits 
• How your organisation can manage and monitor storage 
   

1. Where Your Mercury Data Is Stored

Mercury is a Power App deployed within your Microsoft Power Platform environment. All data is stored in Dataverse, the secure database layer within your Microsoft 365 tenant. 

Unlike traditional recruitment or staffing platforms that rely on proprietary servers, Mercury leverages your existing Microsoft infrastructure. This ensures enterprise-grade security, compliance, and availability—aligned with the rest of your Microsoft 365 environment. 

2. How to Check Your Current Storage Utilisation

You can check Dataverse storage usage via the Power Platform Admin Center: 

1. Visit Power Platform Admin Center
2. Navigate to Resources > Capacity > Summary 
3. Review storage indicators (green, amber, red) and usage percentages 
    

3. Storage Types in Dataverse

Dataverse storage is divided into three types. Each has a base allocation and scales based on the number of licensed users. Additional capacity can also be purchased per gigabyte. 

In addition, each Power Apps Premium license adds the following per user: 

• +250MB Database 
• +2GB File 
• +0.5GB Log 

📌 See Microsoft's Dataverse storage documentation for details and pricing. 

4. Responsibility for Managing Dataverse Storage

Because your Mercury data resides within your Microsoft 365 tenant—and may be impacted by other applications and environments—your organisation is ultimately responsible for ensuring sufficient storage capacity. 

Mercury can assist by: 

• Recommending one-time or scheduled deletion jobs (e.g., removing low-value records like mass emails) 
• Offering archiving or deletion options for non-critical data 
• Guiding your team in purchasing storage add-ons through Microsoft 

However, ongoing capacity monitoring and management remain your responsibility as the Microsoft account holder. 

5. Consequences of Exceeding Storage Capacity

If your organisation exceeds Dataverse storage entitlements, Microsoft applies usage restrictions. You may be blocked from performing the following actions: 

• Creating new environments (requires at least 1GB free capacity) 
• Copying, restoring, or recovering environments 
• Converting trial environments to paid 
• Adding a Dataverse database to an existing environment 

📌 For updates, refer to Microsoft’s storage capacity limits page. 

6. How to Manage Storage Capacity

If you're near or over capacity: 

• Option 1: Purchase additional storage (monthly cost based on Microsoft pricing) 
• Option 2: Free up existing space via cleanup or archiving 

Tenant administrators will receive weekly Microsoft alerts when storage thresholds are nearing or exceeded. Prompt action is advised. 

7. Freeing Up Capacity

To free space, administrators can follow this Microsoft guide: 

• 👉 Free up storage space 
• ⚠️ Important: Some deletions are irreversible. Please consult Mercury before performing data deletions. Mercury can carry out these cleanups on a chargeable basis. 
• 📬 Contact your Customer Success Manager or email success@wearemercury.com for assistance. 
• 🔒 Mercury also recommends retaining at least 3 months of audit logs to support system troubleshooting and issue resolution.