Skip to content

Update availability zone description for private cloud #128400

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
HendrikTilleman wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update availability zone description for private cloud #128400

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion articles/azure-vmware/native-introduction.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -43,7 +43,7 @@ With the Azure VMware Solution Gen 2 private clouds offering, you get the follow

### Other features and capabilities unlocked
- Ability to select Private DNS resolution for your private cloud, enabling businesses to communicate across Azure and on-premises environments without being exposed to the internal.
- Ability to select which availability zone to deploy your private cloud in to minimize latency to on-premises environments. Availability zones are typically specified when a customer wants their private cloud to be geographically closest to their on-premises data center. If availability zone selection is not required, no zone should be specified.
- Ability to specify the Availability Zone in which the private cloud is deployed to optimise connectivity and latency with zonal Azure resources or ExpressRoute gateways within the same region. If no zonal alignment is required, the private cloud can be deployed without specifying an Availability Zone.
Copy link

Copilot AI Apr 13, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This bullet introduces 'optimise' (UK spelling) while the rest of Azure documentation is typically US English. Recommend changing 'optimise' to 'optimize' (and keeping spelling consistent across the doc set).

Suggested change
- Ability to specify the Availability Zone in which the private cloud is deployed to optimise connectivity and latency with zonal Azure resources or ExpressRoute gateways within the same region. If no zonal alignment is required, the private cloud can be deployed without specifying an Availability Zone.
- Ability to specify the Availability Zone in which the private cloud is deployed to optimize connectivity and latency with zonal Azure resources or ExpressRoute gateways within the same region. If no zonal alignment is required, the private cloud can be deployed without specifying an Availability Zone.

Copilot uses AI. Check for mistakes.

## Supported SKU type

Expand Down