Conversation
Changed the third bullet and added the forth bullet
|
@kerimhanif : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit e228f89: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Hi @kerimhanif - This pull request was opened in the public repo. PMs should work in the private repo, per the Microsoft Docs contributor guide. We can keep this PR open for review and merge, but would you make future content updates in the private repo? Thank you! @alkohli Can you take a look? Thanks. |
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
Updates the “Notes” guidance to clarify which VM operations performed via local tools are reflected in the Azure portal, and to expand the definition of what counts as a “local tool.”
Changes:
- Reworded the bullet about portal state updates to improve clarity.
- Added a new bullet defining “local tools” based on where commands execute.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| > - We recommend that you use the Azure portal or the Azure CLI to manage Azure Local VMs. Use the local tools only if these operations are included in the [list of supported operations for local tools](#local-tools) later in this article. | ||
| > - Though the supported operations for local tools don't affect the management of Azure Local VMs, the changes aren't reflected in the Azure portal. | ||
| > - Only the following operations update the state of an Azure Local VM in the portal, when you perform them by using local tools: change the power state (start or stop a VM) resulting from the power cycle operation. | ||
| > - When performed using local tools, only a VM power state change (start or stop) resulting from a power cycle operation updates the Azure Local VM state in the Azure portal. |
There was a problem hiding this comment.
This sentence mixes 'power state change (start or stop)' with 'resulting from a power cycle operation', which is potentially contradictory/unclear (power cycle is commonly understood as restart). Consider rephrasing to match the exact supported operation(s) (for example, explicitly listing start/stop/restart if applicable, or removing 'power cycle operation' if the intent is strictly start/stop).
| > - When performed using local tools, only a VM power state change (start or stop) resulting from a power cycle operation updates the Azure Local VM state in the Azure portal. | |
| > - When performed using local tools, only a VM power state change (start or stop) updates the Azure Local VM state in the Azure portal. |
| > - Though the supported operations for local tools don't affect the management of Azure Local VMs, the changes aren't reflected in the Azure portal. | ||
| > - Only the following operations update the state of an Azure Local VM in the portal, when you perform them by using local tools: change the power state (start or stop a VM) resulting from the power cycle operation. | ||
| > - When performed using local tools, only a VM power state change (start or stop) resulting from a power cycle operation updates the Azure Local VM state in the Azure portal. | ||
| > - Any tool, regardless of where its control plane resides, is considered a local tool if it executes commands locally (for example, the Windows Admin Center extension in the Azure portal). |
There was a problem hiding this comment.
The new definition may be overly broad and may read as contradictory to the prior recommendation to use the Azure portal (since this example is 'in the Azure portal' but labeled a local tool). Consider tightening the definition to align with how 'local tools' is used elsewhere in the doc (for example, emphasizing that the management action is executed on/against the local host/cluster via local execution context), and clarify the example so readers don’t interpret 'Azure portal' itself as a local tool.
| > - Any tool, regardless of where its control plane resides, is considered a local tool if it executes commands locally (for example, the Windows Admin Center extension in the Azure portal). | |
| > - A tool is considered a local tool when the management action runs in a local execution context on or against the local host or cluster, rather than through the Azure control plane. For example, the Windows Admin Center extension can be surfaced in the Azure portal, but operations it executes locally are treated as local-tool operations. |
Changed the third bullet and added the forth bullet