Which Windows web apps qualify?
Microsoft Learn lists four eligible App Service SKUs: Pv3, PMv3, Pv4, and PMv4. The initial regions are East Asia, West Central US, North Europe, and West US 2. This is a non-production preview for Windows web apps in multitenant App Service. Linux, containers, App Service Environment, Azure Functions, and Logic Apps are outside its scope.
Several omissions matter even if your app runs on the right plan. The preview does not support deployment slots, built-in App Service Authentication, custom domains and certificates, or Bring Your Own Storage. For a team whose release process depends on slot swaps, or whose test needs to reproduce a custom hostname and certificate setup, those limits narrow what a successful trial can prove.
One deployment target, two ways to route traffic
The primary web app remains your deployment target. Its regional replicas, which Microsoft calls silos, run a site revision: a snapshot of supported published content and configuration. Automatic mode advances replicas when the primary app is updated. Fixed mode lets you keep a replica on a known-good revision until you promote another one. That pins the application version, not the database schema, secrets, or APIs it relies on. FTP uploads and direct filesystem edits don’t synchronize automatically, either.
Revision control is separate from traffic routing. In Active mode, multiple healthy regions can serve traffic, with weights influencing which endpoints DNS returns. In Passive mode, Traffic Manager prefers a designated region and uses configured priorities to choose among failover destinations. Active makes sense only if the app and its dependencies can serve users concurrently from multiple regions. Passive avoids that requirement during normal operation, but the standby still has to handle the workload when called upon.
The DNS detail is important: Traffic Manager returns a regional endpoint, and the client connects to it directly. It does not proxy HTTP requests, terminate TLS, or transfer an existing connection to another region. Health detection, DNS cache expiration, and client retry behavior all affect when users recover. That’s a different design from Microsoft Learn’s separately managed App Service architecture, which puts Azure Front Door in front of regional apps and uses access restrictions to prevent clients from bypassing it. If your architecture requires that kind of front end, don’t assume the managed Traffic Manager profile replaces it.
Test whether a user can finish the job
For a useful trial, start with an eligible non-production app and one replica. Check quota for the chosen SKU in both regions and, if the primary uses virtual network integration, provide an eligible integration subnet for the replica. Confirm the expected revision is running, then test what happens when the primary endpoint becomes unavailable. A green health indicator is a starting point: try signing in, reading and writing test data, and completing a workflow that calls a downstream service. Repeat after restoring the primary so you can see how clients behave during recovery, not just during failover.
A replica can answer its health probe and still fail every database-backed request if the only database is in the affected region. App Service geo-redundancy does not replicate Azure SQL Database, Cosmos DB, Storage, Key Vault, or live application state. It also doesn’t replace zone redundancy, which spreads plan instances within one region, or backups, which preserve recoverable copies rather than keeping a regional endpoint running. Budget for compute in the primary and replica regions plus a monthly charge for each web app with geo-redundancy enabled, even if you choose Passive routing. The preview takes regional app deployment and routing off your team’s plate; the end-to-end recovery test tells you what’s still on it.
References
- (In preview) Public Preview: Geo-redundancy on Azure App Service Azure Updates · 2026-11-17T20:00:32Z
- Public Preview of Geo-redundancy in Azure App Service - Azure App Service azure.github.io
- Introducing Geo-redundancy in Azure App Service: Simplify multi-region application resilience | Microsoft Community Hub techcommunity.microsoft.com