MC1394998 Low
Finance and operations apps - Information regarding the end of support for Secondary internal copies
Summary AI-generated
On July 22, 2026, internal system maintained secondary remote copies will be removed as SSDR reaches GA, leveraging intra-region availability zones for redundancy.
Suggested actions AI-generated
- Enable SSDR on production environments
- Review and update BCDR plans
Written by Azure OpenAI (gpt-4.1) from the text of the post below. It can be incomplete or wrong; the original post is authoritative.
Similar posts
Search for more like this- MC1293709 Power Platform - PayGo not required with Self-Service Disaster Recovery (SSDR)
- MC1483576 Finance and operations apps - Migrate F&O environments from Lifecycle Services to Power Platform admin center
- MC1253577 Power Platform - Information regarding the end of support for Global Discovery Service (GDS) API
- MC1465298 Dynamics 365 Finance - Streamline Dynamics 365 finance and operations apps integration
- MC1474128 Power Platform - Information regarding the end of support for Global Discovery Service (GDS) API
- MC1464762 Dynamics 365 Project Operations – Copy externally scheduled projects
Original post from Microsoft
On July 22, 2026, platform created internal system maintained secondary remote copies will be removed.
How does this affect me?
With Self-Service Disaster Recovery (SSDR) reaching general availability (GA) on June 22, 2026, we will begin deprecating the platform created internal cross-region copies. With the implementation of Availability zones, we maintain at least two, and in some cases, three synchronous copies of production environments within a region at no extra cost to you. These are hosted in physically separated data centers with independent power, cooling, and networking, in compliance with legislated data residency regulations. Since the replication across the zones is synchronous, if there is any failure in a zone or loss of a zone, customer traffic will seamlessly and automatically move to the other zones, and customers will not experience a service interruption.
What action do I need to take?
We encourage you to enable SSDR on your production environments for your workloads including finance and operations apps.
Please maintain documented business continuity and disaster recovery (BCDR) plans for your implementation, and take any necessary actions aligned to your organization's BCDR policies.
How does this affect me?
With Self-Service Disaster Recovery (SSDR) reaching general availability (GA) on June 22, 2026, we will begin deprecating the platform created internal cross-region copies. With the implementation of Availability zones, we maintain at least two, and in some cases, three synchronous copies of production environments within a region at no extra cost to you. These are hosted in physically separated data centers with independent power, cooling, and networking, in compliance with legislated data residency regulations. Since the replication across the zones is synchronous, if there is any failure in a zone or loss of a zone, customer traffic will seamlessly and automatically move to the other zones, and customers will not experience a service interruption.
What action do I need to take?
We encourage you to enable SSDR on your production environments for your workloads including finance and operations apps.
Please maintain documented business continuity and disaster recovery (BCDR) plans for your implementation, and take any necessary actions aligned to your organization's BCDR policies.