Category: Dataverse

Self-Service Disaster Recovery for Power Platform and D365

Microsoft provides Business Continuity and Disaster Recovery (BCDR) across all production environments as part of the Dynamics 365 and Power Platform offerings. This aims to minimize outages and disruptions and ensure that your data is protected at all times.

Infrastructure is deployed to an Azure Geography, and a geography is made up of between 2 to 3 Azure Availability Zones (generally located 300 miles / 482 kms away from each other). An Azure Availability Zone deploys critical data center infrastructure such as network, power, and cooling. To ensure resilience across a geography, your environments are replicated across to at least two Availability Zones in real time.

The diagram shows a typical architecture of a geography that serves a single or multiple countries/regions.

Figure 1 – Example of Azure Geography and Availability Zones

If a failure is detected within an availability zone, disaster recovery will route traffic to the unaffected availability zone. Recovery Point Objective (RPO) is stated to be near zero, and the Recovery Time Objective (RTO) is stated to be less than 5 minutes.

As part of Wave 1 Release 2025, Microsoft released Self-Service Disaster Recovery for Power Platform as a public preview.

Today we’ll be further exploring this capability by running a Disaster Recovery Drill.

Continue reading

Navigating Updates: Your Guide to Microsoft Power Platform Updates

This article provides a high-level overview of managing updates for the Microsoft Power Platform and Dynamics 365. It is important to stay informed about the latest updates and understanding the different types of updates that are deployed to ensure platform stability and minimize disruptions.

New features, optimisations, bug fixes, deprecations, and security patches are constantly being deployed, making this guide essential for anyone whose role involves managing Power Platform environments. It covers both new and existing information that is crucial for effective management.

In this article I will be focusing on four core concepts:

  • Release Wave Updates – Major updates to the Power Platform service that are generally available twice per year in April and October. These updates are deployed automatically.
  • Early Access Updates – Updates designed for testing functionality in test environments, available ahead of the automatic wave updates. These updates are deployed manually.
  • Refresh Cadence (Incremental Updates) – Updates that occur between Wave Release cycles and can be deployed weekly or monthly. These updates occur automatically.
  • Release Channels (for Model Driven Apps) – Semi Annual (twice yearly) or Monthly updates to the Unified Interface that drives Model Driven Power Apps.

Continue reading

© 2025 365lyf.com

Theme by Anders NorenUp ↑