For organizations running Windows 365 Cloud PCs in geographies where only one Azure region is supported, disaster recovery has been a persistent challenge. You need geographic redundancy for resilience, but data sovereignty rules may prevent you from replicating to a region in a different country or legal jurisdiction. Microsoft’s latest update to Windows 365 addresses this gap head-on.
As of the week of July 20, 2026, Windows 365 now supports alternate Azure regions for Business Continuity and Disaster Recovery (BCDR) scenarios in public preview. This includes new alternate regions like Australia Southeast and South India, giving administrators in those geographies a viable cross-region DR option for the first time.
What Changed: Alternate Regions for BCDDR
Until now, Windows 365’s cross-region disaster recovery capabilities — Cross-region Disaster Recovery (CRDR) and Disaster Recovery Plus (DR+) — required that both the primary and backup regions be Windows 365-supported Azure regions within the same geography. For organizations in geographies with only a single supported region, this meant cross-region DR was effectively impossible without crossing geographic boundaries, which could violate data residency requirements.
This update adds alternate regions that can be used specifically for disaster recovery configurations. The key constraint: these alternate regions are available for DR scenarios only — they cannot be used for primary Cloud PC provisioning.
Supported Alternate Regions
The initial alternate regions include:
- Australia Southeast
- South India
These regions join the existing set of Windows 365-supported Azure regions, but with a scoped purpose: they exist in the BCDR configuration options as backup targets for CRDR and DR+ policies.
CRDR vs. DR+: A Quick Refresher
If you’re not deeply familiar with Windows 365’s two BCDR options, here’s how they compare:
Cross-region Disaster Recovery (CRDR)
CRDR is the baseline cross-region DR offering for Windows 365 Enterprise and Windows 365 Flex (Dedicated mode). It works by:
- Periodically creating restore points — snapshots of the Cloud PC disk, including OS, apps, and user data — in a geographically separated backup region
- Activating temporary Cloud PCs in that backup region during a regional outage, using the replicated restore points
Key characteristics:
- RPO (Recovery Point Objective) target: < 4 hours
- RTO (Recovery Time Objective) target: < 4 hours
- Capacity in the backup region is not pre-reserved — temporary Cloud PCs are created at activation time, subject to available capacity
- Restore points are resilient and stored in the alternate region regardless of capacity constraints
Disaster Recovery Plus (DR+)
DR+ is the advanced tier, designed for organizations with stricter DR requirements:
- Pre-allocates a secondary Cloud PC in the backup region at configuration time — essentially a warm standby
- On failover, Microsoft swaps the latest replicated disk onto the standby Cloud PC, so users can resume work almost immediately
Key characteristics:
- Guaranteed capacity — compute is reserved up front, eliminating the capacity risk that CRDR carries
- Significantly better RTO than CRDR — no waiting for new instances to spin up or capacity checks
- CRDR and DR+ are mutually exclusive per user — a user with multiple Cloud PCs must have either one or the other, not both
- You can mix CRDR and DR+ across users at the tenant level — some users protected with CRDR, others with DR+
Why This Matters: Data Sovereignty Meets Disaster Recovery
The real significance of this update isn’t just “more regions.” It’s about solving a specific architectural problem that has affected Windows 365 customers in single-region geographies since CRDR was first introduced.
The Single-Region Problem
Consider an organization in Australia. Before this update, if their Cloud PCs were hosted in the only Windows 365-supported Australia region, configuring cross-region DR meant either:
- Choosing a backup region in a different geography — potentially violating Australian data residency requirements
- Going without cross-region DR — leaving Cloud PCs vulnerable to regional outages
Neither option is acceptable for regulated industries, government contractors, or organizations subject to local data protection laws.
The Alternate Region Solution
With Australia Southeast now available as an alternate region for BCDR, organizations can:
- Keep primary Cloud PCs in their existing Australia region
- Configure CRDR or DR+ to use Australia Southeast as the backup target
- Maintain all data within the same legal geography while achieving geographic separation for disaster recovery
The same applies to organizations in India with the addition of South India as an alternate region.
How to Configure Alternate Regions for BCDR
Configuration happens in the Microsoft Intune admin center, in the same location where existing CRDR/DR+ policies are managed:
- Navigate to Devices → Windows 365 → User Settings in the Intune admin center
- Create or edit a user settings policy
- Under the cross-region disaster recovery section, select your geography
- Choose the alternate region as your backup target (e.g., Australia Southeast or South India)
- Select whether to use CRDR or DR+ for the policy
- Assign the policy to the appropriate user groups
The alternate regions will appear in the region selector for DR configurations. They will not appear as options for primary Cloud PC provisioning — only for disaster recovery.
Practical Recommendations
Evaluate Your Current BCDR Posture
If you’re operating Windows 365 in a geography that previously had only one supported region, now is the time to reassess your disaster recovery strategy. This update removes the primary blocker that may have prevented you from implementing cross-region DR.
Choose CRDR or DR+ Based on Workload Criticality
- CRDR is appropriate for most users where a < 4-hour RPO/RTO is acceptable and cost optimization matters
- DR+ is worth the investment for power users, executives, or anyone whose downtime directly impacts revenue or compliance
Consider Mixed Deployments
Since CRDR and DR+ can be mixed across users at the tenant level, consider a tiered approach:
- DR+ for critical roles (executives, developers, finance)
- CRDR for standard users
- No DR for non-critical or temporary Cloud PCs
Verify Data Sovereignty Requirements
Even though alternate regions are within the same geography, verify that your specific regulatory requirements are met. Some regulations have granular requirements about data location that go beyond geography-level boundaries.
What’s Next
This is a public preview, which means:
- Features are functional but may have limitations
- The alternate region list may expand over time
- General availability timeline has not been announced
Microsoft has been steadily expanding Windows 365’s BCDR capabilities throughout 2026. The addition of alternate regions fills a critical gap in the DR story and makes cross-region recovery viable for organizations that previously had no compliant path to geographic redundancy.
If you’re managing Windows 365 Cloud PCs in Australia, India, or any single-region geography, this update deserves immediate attention. Your disaster recovery options just got significantly better.
For more information, see the Windows 365 requirements documentation and the Cross-region disaster recovery documentation.
Follow @kkaminski on X for daily Windows 365 updates and analysis.