| IMPERIUM DYNAMICS
Managing data, solutions, and customizations in Power
Platform environments is key for Microsoft users.
Accidental deletions or failures can cause big problems.
Fortunately, Microsoft offers backup and restore tools
to help administrators recover their environments.
But, many wonder:
Does restoring a Power Platform environment recover
all customizations and solutions?
In this guide, we'll explore how restoration works. We'll see what gets restored, what challenges you might face, and the best ways to ensure a smooth recovery.
Understanding Power Platform Environment Restores
Before we dive into what gets restored, let's understand the basics. We'll look at the types of backups and how restoration works in Power Platform.
Types of Backups
1. System Backups
System backups are automatically made by Microsoft for environments with a Dataverse database. They occur regularly to facilitate quick recoveries.
-
Retention: Kept for
7 days.
-
Eligible Environments: Production and
sandbox environments.
-
Exclusions: Trial environments
usually aren't eligible for system backups.
2. Manual Backups
Manual backups are started by admins. They're great before big updates or changes.
-
Retention: Varies by environment
type.
-
Production with Dynamics 365 apps:
Up to 28 days.
-
Sandbox: Offers limited retention
but is flexible for testing purposes.
Manual backups provide administrators with more control over when to recover, especially before significant changes.
Components Restored During Environment Restoration
The big question is: Are customizations and solutions restored?
Let's see what's restored during the process.
Included in Restoration:
-
Customizations and Solutions:
All managed and unmanaged solutions are restored. This includes custom tables, forms, views, and more.
-
Apps and Flows:
Canvas and model-driven apps are restored if backed up correctly.
-
Security Roles and User Settings:
Security settings, like teams and business units, are also restored.
-
Dataverse Data:
Dataverse tables, records, and metadata are included.
Not Included in Restoration:
-
Audit Logs:
Audit data is not restored by default. However, admins can choose to include it, which slows down the restore process.
-
External Files and SharePoint Integrations:
External files and SharePoint integrations are not backed up. Only metadata is saved in Dataverse.
-
Connection References:
Connection references may require manual re-authentication after restoration.
-
Canvas App Sharing Permissions:
Sharing permissions for apps might reset, especially for "Everyone."
-
Custom Connectors and API Connections:
Metadata is backed up, but connection authentication may need to be reconfigured after restoration.
Restoration Process: Step-by-Step Guide
To restore an environment, follow specific steps in the Power Platform Admin Center.
Step 1: Accessing the Admin Center
-
Visit the Power Platform Admin Center.
-
Log in with an administrator account, such as Global
Admin or Dynamics 365 Admin.
Step 2: Selecting the Environment
-
Go to Environments.
-
Pick the environment you want to restore.
Step 3: Initiating Restoration
-
Click on
Backup & Restore.
-
In the Backups tab, choose a backup
for restoration.
-
Under Restore or Manage, click
Restore.
Step 4: Choosing Target Environment
-
Restorations are for
sandbox or developer environments
only.
-
To restore to a production environment:
-
First, convert the production environment to a
sandbox.
- Then, restore the backup.
-
Finally, switch the sandbox back to production.
Step 5: Finalizing and Monitoring
-
Check the details before confirming.
- Start the restoration.
-
Watch the progress in the Admin Center. The time it
takes depends on the data and if audit logs were
included.
Post-Restoration Considerations
Restoring an environment doesn't mean you're back to normal right away. Some tasks are crucial after restoration.
Flows and Automations
-
Flows may become disabled after
restoration.
-
Admins must manually review and
re-enable flows.
-
Ensure that all flow connections, particularly
external ones, are functioning properly.
Reconfigure Connection References
-
Verify that all flow, app, and automation connections
are functioning properly.
-
Re-authenticate any connections that need it.
Canvas App Sharing Settings
-
Double-check app-sharing permissions.
-
In some cases, apps shared with “Everyone”
need to be reshared manually.
App Identifiers
-
Canvas apps get new App IDs after
restoration.
-
If deep links or external systems are linked to apps,
update those links to the new App ID.
Testing
-
Do a detailed test of key processes after
restoration.
-
Ensure that integrations, plugins, workflows, and
notifications are functioning correctly.
Best Practices for Backup and Restoration
To avoid surprises during and after a restore, follow best practices.
1. Schedule Regular Manual Backups
Even with automated backups, manual backups give you control over recovery points.
Example: Always make a manual backup before a major software upgrade.
2. Maintain Documentation
Keep records of your environment settings, installed solutions, and essential connections.
Tip: Keep a list of key App IDs, solution versions, and essential connection details.
3. Periodically Test Restoration
Use sandbox environments to test the restoration process. This helps ensure everything works right and spots any missing parts early on.
4. Adjust Retention Policies
Ensure that your data retention settings align with your company's rules and requirements.
For example, Finance or healthcare companies may need to retain data for longer periods for audit purposes.
5. Backup External Data
If you use SharePoint, Azure, or other services, create backup plans for that data too.
Conclusion
So, does restoring a Power Platform environment recover customizations and solutions?
Yes — but with important caveats.
Customizations, apps, Dataverse
data, and solutions are brought back. This restores the
environment to its previous state. However, admins need
to handle tasks such as connection setup, flow
activation, app sharing, and external integrations after
the restore.
By following best practices such as regular backups, clear documentation, and testing, you can ensure that restoration is easy and effective.
Understanding the process thoroughly and preparing in advance helps protect your Power Platform environments. This way, you can keep your business running smoothly without significant interruptions.
