Open
Conversation
fix: downmerge from main to dev
fix: update VM size to Standard_D2s_v5 and update related documentation
There was a problem hiding this comment.
Pull request overview
This PR updates the default Jumpbox VM size to Standard_D2s_v5 across the infrastructure templates and aligns documentation/parameterization to support overriding the VM size via AZURE_ENV_VM_SIZE, along with improved troubleshooting guidance for SKU availability errors.
Changes:
- Updated Jumpbox VM size default from
Standard_DS2_v2toStandard_D2s_v5in Bicep and generated ARM templates. - Added
vmSizeparameter wiring in the WAF parameters file to support override viaAZURE_ENV_VM_SIZE. - Refreshed documentation to include the new default and add SKU availability troubleshooting guidance.
Reviewed changes
Copilot reviewed 6 out of 6 changed files in this pull request and generated 3 comments.
Show a summary per file
| File | Description |
|---|---|
| infra/modules/virtualNetwork.bicep | Updates VM size guidance comments to recommend Standard_D2s_v5 and list alternatives. |
| infra/main.waf.parameters.json | Adds vmSize parameter sourced from AZURE_ENV_VM_SIZE for WAF deployments. |
| infra/main.json | Updates generated ARM template metadata and changes vmSize defaults/fallbacks to Standard_D2s_v5. |
| infra/main.bicep | Changes the default vmSize to Standard_D2s_v5 and updates Jumpbox module parameter defaulting. |
| docs/TroubleShootingSteps.md | Expands SkuNotAvailable troubleshooting with guidance specific to the new default VM size and override. |
| docs/CustomizingAzdParameters.md | Documents AZURE_ENV_VM_SIZE and its default value. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
…aiPrivateEndpoint and docIntelPrivateEndpoint module
refactor: refactor private endpoint configuration to deploy separately via openaiPrivateEndpoint and docIntelPrivateEndpoint module
fix: downmerge from main to dev
fix: Updated azure.yaml file to exclude the 1.23.9 azd version
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
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 updates the default virtual machine (VM) size for the Jumpbox VM to
Standard_D2s_v5across the deployment templates, documentation, and parameter files. It also improves troubleshooting documentation for SKU availability errors and provides clearer guidance and parameterization for VM sizing.Jumpbox VM Size Default Update and Documentation Improvements:
Infrastructure and Parameterization
Standard_DS2_v2toStandard_D2s_v5ininfra/main.bicep,infra/main.json, and the Jumpbox VM module, ensuring new deployments use a more current and performant VM size. [1] [2] [3] [4]AZURE_ENV_VM_SIZEenvironment variable, and reflected this ininfra/main.waf.parameters.jsonanddocs/CustomizingAzdParameters.md. [1] [2]Documentation and Troubleshooting
Standard_D2s_v5), providing alternative VM sizes, and giving explicit instructions for overriding the default if unavailable in a region.infra/modules/virtualNetwork.bicepto highlightStandard_D2s_v5as the recommended option, with notes on previous generation alternatives.Does this introduce a breaking change?
Golden Path Validation
Deployment Validation
What to Check
Verify that the following are valid
Other Information