fix: add westus3 in replicaRegionPairs#43
Merged
Roopan-Microsoft merged 1 commit intodevfrom Nov 6, 2025
Merged
Conversation
Shreyas-Microsoft
requested review from
Avijit-Microsoft,
Dongbumlee,
Prajwal-Microsoft,
Roopan-Microsoft,
Vinay-Microsoft,
aniaroramsft and
sethsteenken
as code owners
Roopan-Microsoft
approved these changes
Nov 6, 2025
|
🎉 This PR is included in version 1.0.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Purpose
This pull request makes a small update to the region pairing configuration in the
infra/main.bicepfile. The main change is the addition of a new region mapping forwestus3toeastusin both the general replica region pairs and the Cosmos DB high-availability region pairs. This ensures that deployments in thewestus3region will have an appropriate paired region for redundancy and high availability.westus3toeastusin thereplicaRegionPairsvariable to support redundancy for resources deployed inwestus3.westus3toeastusin thecosmosDbZoneRedundantHaRegionPairsvariable to ensure Cosmos DB high-availability deployments inwestus3are paired witheastus.Does this introduce a breaking change?
Golden Path Validation
Deployment Validation
What to Check
Verify that the following are valid
Other Information