Update availability zone description for private cloud#128400
Update availability zone description for private cloud#128400HendrikTilleman wants to merge 1 commit intoMicrosoftDocs:mainfrom
Conversation
Clarified the explanation of availability zone selection for private cloud deployment.
|
@HendrikTilleman : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit 534db4b: ✅ Validation status: passed
For more details, please refer to the build report. |
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
Clarifies documentation around when and why to select an Availability Zone for Azure VMware Solution Gen 2 private cloud deployments.
Changes:
- Reworded the Availability Zone bullet to emphasize aligning with zonal Azure resources / ExpressRoute gateways.
- Clarified that omitting a zone is appropriate when no zonal alignment is needed.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| ### 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. |
There was a problem hiding this comment.
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).
| - 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. |
|
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
prmerger-automator
Bot
added
the
aq-pr-triaged
Clarified the explanation of availability zone selection for private cloud deployment.