Update business-continuity-disaster-recovery.md

Author: sericks007

power-platform/admin/business-continuity-disaster-recovery.md

@@ -2,7 +2,7 @@
 title: Business continuity and disaster recovery for Dynamics 365 SaaS apps
 description: Microsoft provides business continuity and disaster recovery for Dynamics 365 SaaS applications' production environments if there's a region-wide Azure outage. 
 author: shpradha
-ms.date: 05/04/2026
+ms.date: 05/05/2026
 ms.reviewer: sericks
 ms.topic: concept-article
 ms.subservice: admin
@@ -154,8 +154,11 @@ With the implementation of [availability zones](/azure/reliability/availability-
 - Pay-as-you-go is designed to generate various alerts and warnings at various thresholds to warn administrators of depleting storage. Use the alert mechanism to your advantage.
 - Pay-as-you-go links the selected environment to the Azure subscription by using a billing policy. Once you link an environment to an Azure subscription, the usage of apps and any Dataverse or Power Platform usage that goes above the included storage amounts are billed against the Azure subscription by using Azure meters. For more information, go to [Pay-as-you-go meters](pay-as-you-go-meters.md). If you acquire more storage entitlements, the pay-as-you-go plan stops running the meters and consuming from available free storage and entitlements take precedence. 
 
-###Recovery point and recovery time objectives with business continuity and disaster recovery
-Power Platform and Dataverse are designed with high availability built into every region. Within a region, the platform targets approximately near zero RPO (recovery point objective) and a recovery time of under 5 minutes across availability zones and data centers within a region. For cross-region resiliency, Microsoft provides Self-Service Disaster Recovery (SSDR), which gives customers full visibility and control over the failover process. In this model, typical replication lag is under 15 minutes (often under 5 minutes), and the platform is designed to complete failover within minutes once initiated. Because customers retain control of when and whether to trigger a cross-region failover, Microsoft does not publish a cross-region RTO commitment— however, customers can monitor real-time replication lag directly in the Power Platform Admin Center (PPAC) to inform their own recovery decisions. It is also important to note that when Power Platform solutions connect to external systems — such as SQL Server, REST APIs, or other third-party services — the RPO of those integrations are governed by the availability and recovery capabilities of the respective target systems, and fall outside the scope of Power Platform's resiliency commitments.
+### What are the recovery point and recovery time objectives with business continuity and disaster recovery?
+
+Power Platform and Dataverse are designed with high availability built into every region. Within a region, the platform targets approximately near zero recovery point objective (RPO) and a recovery time of under five minutes across availability zones and data centers within a region. For cross-region resiliency, Microsoft provides self-service disaster recovery, which gives customers full visibility and control over the failover process. 
+
+In this model, typical replication lag is under 15 minutes (often under five minutes), and the platform is designed to complete failover within minutes once initiated. Because customers retain control of when and whether to trigger a cross-region failover, Microsoft doesn't publish a cross-region RTO commitment. However, customers can monitor real-time replication lag directly in the Power Platform admin center to inform their own recovery decisions. It's also important to note that when Power Platform solutions connect to external systems, such as SQL Server, REST APIs, or other third-party services, the RPO of those integrations are governed by the availability and recovery capabilities of the respective target systems, and fall outside the scope of Power Platform's resiliency commitments.
 
 ### How does billing work for self-service disaster recovery?