Update azure-stack-compute-add-scalesets.md#4234
Update azure-stack-compute-add-scalesets.md#4234xizhuang wants to merge 1 commit intoMicrosoftDocs:mainfrom
Conversation
All the screenshots and steps in this document are taken from the Azure Stack Hub Admin portal and use the Default Provider Subscription. However, the document does not explicitly state which portal (Admin or Tenant) should be used to create Virtual Machine Scale Sets (VMSS). This lack of clarity may cause confusion for readers, as VMSS can also be created from the Tenant portal using the same workflow. The documentation should clearly specify: That the screenshots reflect actions performed in the Admin portal using the Default Provider Subscription, and That the same steps can also be followed from the Tenant portal when creating VM Scale Sets. Adding this clarification will improve usability and prevent ambiguity for operators and tenants following the guide.
|
@xizhuang : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
@xizhuang : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit 53313e8: ✅ Validation status: passed
For more details, please refer to the build report. |
|
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
There was a problem hiding this comment.
Pull request overview
This PR updates the Azure Stack Hub operator documentation for creating Virtual Machine Scale Sets (VMSS) to clarify which portal can be used, aiming to reduce ambiguity for operators vs. tenants following the same workflow.
Changes:
- Updated the first step in “Use the Azure Stack Hub portal” to mention signing in via the admin portal or tenant portal.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| ## Use the Azure Stack Hub portal | ||
|
|
||
| 1. Sign in to the Azure Stack Hub portal. Then, go to **All services**, then **Virtual machine scale sets**, and then under **COMPUTE**, select **Virtual machine scale sets**. | ||
| 1. Sign in to the Azure Stack Hub admin portal or tenant portal. Then, go to **All services**, then **Virtual machine scale sets**, and then under **COMPUTE**, select **Virtual machine scale sets**. |
There was a problem hiding this comment.
The PR description says the doc should explicitly clarify that the screenshots/steps are from the admin portal using the Default Provider Subscription, while the same workflow can be followed in the tenant portal. This update only says “admin portal or tenant portal” and doesn’t indicate which portal/subscription the screenshots reflect, which can still confuse readers (and tenant users won’t see “Default Provider Subscription”). Consider rewording this step (or adding a short note before the steps) to state that screenshots are from the admin portal with Default Provider Subscription, and that tenant-portal users should select their own subscription.
All the screenshots and steps in this document are taken from the Azure Stack Hub Admin portal and use the Default Provider Subscription. However, the document does not explicitly state which portal (Admin or Tenant) should be used to create Virtual Machine Scale Sets (VMSS).
This lack of clarity may cause confusion for readers, as VMSS can also be created from the Tenant portal using the same workflow. The documentation should clearly specify:
That the screenshots reflect actions performed in the Admin portal using the Default Provider Subscription, and That the same steps can also be followed from the Tenant portal when creating VM Scale Sets. Adding this clarification will improve usability and prevent ambiguity for operators and tenants following the guide.