Add Enterprise L1 network resources in South Central US - #335
Merged
Merged
Conversation
jwmossmoz
enabled auto-merge (squash)
September 14, 2026 15:01
jwmossmoz
disabled auto-merge
September 14, 2026 15:02
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
1 participant
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.
Enterprise Server 2022 VM creation fails in South Central US because
enterprise-1/b-win2022referencessn-south-central-us-enterprise-1, but the Enterprise L1 Terraform region list omits South Central US. Azure confirms thatrg-south-central-us-enterprise-1does not exist.Add the region to the existing network module so Terraform creates the resource group, VNet, subnet, network security group, subnet association, and storage account with the names used by the worker pool.
Validation: pre-commit and
terraform validatepassed. A fresh live plan forterraform/azure_fxci/enterprise-1reported 6 to add, 0 to change, 0 to destroy, all in South Central US. Applied that saved plan successfully: 6 added, 0 changed, 0 destroyed. Azure confirms that the exact subnet referenced by the worker pool exists with provisioning stateSucceededand its network security group attached.Found during the worker checks for fxci-config #1209; deployment record: Bug 2071896.