Skip to content

Fix incorrect active vCPU counts for E_v6 constrained-core VMs in documentation #214

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.

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
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

travishankins
Copy link

Corrected the active vCPU values for constrained-core Standard_E_v6 SKUs (e.g., Standard_E32-8s_v6, Standard_E64-16s_v6, etc.).

Previous documentation incorrectly listed the base vCPUs instead of the reduced active vCPUs as indicated by the SKU naming convention.

This update aligns the E_v6 SKU active vCPU counts with actual Azure deployment behavior, improving sizing, licensing, and planning accuracy.

v6 of E-Family Sizes had incorrect CPU sizes. Since they are constrained they should be the second listed number like all the other entires and not the actual.
@travishankins
Copy link
Author

@microsoft-github-policy-service agree company="Microsoft"

Copy link
Contributor

@travishankins : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

Copy link
Contributor

Learn Build status updates of commit b417e9f:

✅ Validation status: passed

File Status Preview URL Details
articles/virtual-machines/constrained-vcpu.md ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

@v-regandowner
Copy link
Contributor

@mattmcinnes - Can you review the proposed changes?

IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@prmerger-automator prmerger-automator bot added the aq-pr-triaged C+L Pull Request Review Team label label Apr 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment