-
Notifications
You must be signed in to change notification settings - Fork 231
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
base: main
Are you sure you want to change the base?
Conversation
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.
@microsoft-github-policy-service agree company="Microsoft" |
@travishankins : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
Learn Build status updates of commit b417e9f: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
@mattmcinnes - Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
This pull request has been inactive for at least 14 days. If you are finished with your changes, don't forget to sign off. See the contributor guide for instructions. |
@mattmcinnes Could you review this proposed update to your article and enter Thanks! |
I sent an email to the content owner today. @MicrosoftDocs/public-repo-pr-review-team |
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.