Revise VM watch description and add signal categories

[tfishler1]

Updated the VM watch section to clarify its purpose and functionality, including a new introduction to VMWatch and its signal categories.

[prmerger-automator]

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

[learn-build-service-prod]

Learn Build status updates of commit 0a1a178:

✅ Validation status: passed

File	Status	Preview URL	Details
articles/virtual-machines/azure-vm-watch.md	✅Succeeded

For more details, please refer to the build report.

[Copilot]

Pull request overview

This pull request updates the Azure VM watch documentation to reflect the service's general availability (removing the "preview" designation) and provides enhanced descriptions of its capabilities. The changes introduce a more comprehensive explanation of VMWatch as a testing framework and add a new section describing signal categories.

Key changes:

• Removed "(preview)" from the main title to reflect general availability status
• Completely rewrote the introductory description to position VMWatch as an open-sourced testing framework with expanded details about its purpose and capabilities
• Added a new "VMWatch Signal Categories" section that introduces the different types of health signals collected

[Copilot]

This paragraph is not a complete sentence - it lacks a main verb. The text begins with "VMWatch, a standardized..." but never completes the sentence structure. Consider rephrasing to form a complete sentence, such as "VMWatch is a standardized, lightweight, and open-sourced testing framework..."

[tfishler1]

@copilot open a new pull request to apply changes based on this feedback

[tfishler1]

@copilot open a new pull request to apply changes based on this feedback

[Copilot]

Inconsistent terminology: The title and rest of the document use "VM watch" (two words, lowercase 'watch'), but this new section header and content use "VMWatch" (one word, camelCase). Maintain consistency throughout the document by using "VM watch" as established in the title and other sections.

[Copilot]

According to the Microsoft Writing Style Guide, avoid using "and so on" or leaving lists open-ended. Either provide the complete list of signal categories or rephrase to indicate these are examples by using "such as" instead of "including". For example: "VMWatch measures VM health by emitting signals in different categories, such as Network, Disk, CPU, Process, IMDS, Clock, AzBlob, and Hardware."

[v-dirichards]

Hi @tfishler1 - 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!

---

@iamwilliew

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.

[tfishler1]

Hi Diana, Thank you for sharing the information. I’ll be making additional changes soon, so let’s keep it open for now. I’m still getting familiar with this system and policy, so apologies for any confusion.

…

________________________________ From: Diana Richards ***@***.***> Sent: Tuesday, January 6, 2026 1:44 PM To: MicrosoftDocs/azure-compute-docs ***@***.***> Cc: Tal Fishler ***@***.***>; Mention ***@***.***> Subject: Re: [MicrosoftDocs/azure-compute-docs] Revise VM watch description and add signal categories (PR #405) [https://avatars.githubusercontent.com/u/103777760?s=20&v=4]v-dirichards left a comment (MicrosoftDocs/azure-compute-docs#405)<#405 (comment)> Hi @tfishler1- 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!

________________________________ @iamwilliew<https://github.com/iamwilliew> 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<https://github.com/orgs/MicrosoftDocs/teams/public-repo-pr-review-team> — Reply to this email directly, view it on GitHub<#405 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BHQNWPFX3IWCMYHLLGPMQN34FQUFLAVCNFSM6AAAAACQ4CIGUKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOMJWGQ3TKMRTG4>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[v-dirichards]

@tfishler1 If you need help getting set up to work in the private repo, see Get started contributing to the Microsoft Learn platform.

[learn-build-service-prod]

Learn Build status updates of commit 908e195:

✅ Validation status: passed

File	Status	Preview URL	Details
articles/virtual-machines/azure-vm-watch.md	✅Succeeded

For more details, please refer to the build report.

[learn-build-service-prod]

Learn Build status updates of commit 399ec83:

✅ Validation status: passed

File	Status	Preview URL	Details
articles/virtual-machines/azure-vm-watch.md	✅Succeeded

For more details, please refer to the build report.

[learn-build-service-prod]

Learn Build status updates of commit 2289b30:

✅ Validation status: passed

File	Status	Preview URL	Details
articles/virtual-machines/azure-vm-watch.md	✅Succeeded

For more details, please refer to the build report.

[tfishler1]

@tfishler1 please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.

@microsoft-github-policy-service agree [company="{your company}"]

Options:

• (default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.

@microsoft-github-policy-service agree

• (when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.

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

Contributor License Agreement

Contribution License Agreement

This Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”), and conveys certain license rights to Microsoft Corporation and its affiliates (“Microsoft”) for Your contributions to Microsoft open source projects. This Agreement is effective as of the latest signature date below.

1. Definitions.
   “Code” means the computer software code, whether in human-readable or machine-executable form,
   that is delivered by You to Microsoft under this Agreement.
   “Project” means any of the projects owned or managed by Microsoft and offered under a license
   approved by the Open Source Initiative (www.opensource.org).
   “Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to any
   Project, including but not limited to communication on electronic mailing lists, source code control
   systems, and issue tracking systems that are managed by, or on behalf of, the Project for the purpose of
   discussing and improving that Project, but excluding communication that is conspicuously marked or
   otherwise designated in writing by You as “Not a Submission.”
   “Submission” means the Code and any other copyrightable material Submitted by You, including any
   associated comments and documentation.
2. Your Submission. You must agree to the terms of this Agreement before making a Submission to any
   Project. This Agreement covers any and all Submissions that You, now or in the future (except as
   described in Section 4 below), Submit to any Project.
3. Originality of Work. You represent that each of Your Submissions is entirely Your original work.
   Should You wish to Submit materials that are not Your original work, You may Submit them separately
   to the Project if You (a) retain all copyright and license information that was in the materials as You
   received them, (b) in the description accompanying Your Submission, include the phrase “Submission
   containing materials of a third party:” followed by the names of the third party and any licenses or other
   restrictions of which You are aware, and (c) follow any other instructions in the Project’s written
   guidelines concerning Submissions.
4. Your Employer. References to “employer” in this Agreement include Your employer or anyone else
   for whom You are acting in making Your Submission, e.g. as a contractor, vendor, or agent. If Your
   Submission is made in the course of Your work for an employer or Your employer has intellectual
   property rights in Your Submission by contract or applicable law, You must secure permission from Your
   employer to make the Submission before signing this Agreement. In that case, the term “You” in this
   Agreement will refer to You and the employer collectively. If You change employers in the future and
   desire to Submit additional Submissions for the new employer, then You agree to sign a new Agreement
   and secure permission from the new employer before Submitting those Submissions.
5. Licenses.

• Copyright License. You grant Microsoft, and those who receive the Submission directly or
  indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license in the
  Submission to reproduce, prepare derivative works of, publicly display, publicly perform, and distribute
  the Submission and such derivative works, and to sublicense any or all of the foregoing rights to third
  parties.
• Patent License. You grant Microsoft, and those who receive the Submission directly or
  indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license under
  Your patent claims that are necessarily infringed by the Submission or the combination of the
  Submission with the Project to which it was Submitted to make, have made, use, offer to sell, sell and
  import or otherwise dispose of the Submission alone or with the Project.
• Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement.
  No additional licenses or rights whatsoever (including, without limitation, any implied licenses) are
  granted by implication, exhaustion, estoppel or otherwise.

6. Representations and Warranties. You represent that You are legally entitled to grant the above
   licenses. You represent that each of Your Submissions is entirely Your original work (except as You may
   have disclosed under Section 3). You represent that You have secured permission from Your employer to
   make the Submission in cases where Your Submission is made in the course of Your work for Your
   employer or Your employer has intellectual property rights in Your Submission by contract or applicable
   law. If You are signing this Agreement on behalf of Your employer, You represent and warrant that You
   have the necessary authority to bind the listed employer to the obligations contained in this Agreement.
   You are not expected to provide support for Your Submission, unless You choose to do so. UNLESS
   REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING, AND EXCEPT FOR THE WARRANTIES
   EXPRESSLY STATED IN SECTIONS 3, 4, AND 6, THE SUBMISSION PROVIDED UNDER THIS AGREEMENT IS
   PROVIDED WITHOUT WARRANTY OF ANY KIND, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY OF
   NONINFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.
7. Notice to Microsoft. You agree to notify Microsoft in writing of any facts or circumstances of which
   You later become aware that would make Your representations in this Agreement inaccurate in any
   respect.
8. Information about Submissions. You agree that contributions to Projects and information about
   contributions may be maintained indefinitely and disclosed publicly, including Your name and other
   information that You submit with Your Submission.
9. Governing Law/Jurisdiction. This Agreement is governed by the laws of the State of Washington, and
   the parties consent to exclusive jurisdiction and venue in the federal courts sitting in King County,
   Washington, unless no federal subject matter jurisdiction exists, in which case the parties consent to
   exclusive jurisdiction and venue in the Superior Court of King County, Washington. The parties waive all
   defenses of lack of personal jurisdiction and forum non-conveniens.
10. Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and
    supersedes any and all prior agreements, understandings or communications, written or oral, between
    the parties relating to the subject matter hereof. This Agreement may be assigned by Microsoft.

@microsoft-github-policy-service agree

[learn-build-service-prod]

Learn Build status updates of commit 83ae212:

✅ Validation status: passed

File	Status	Preview URL	Details
articles/virtual-machines/azure-vm-watch.md	✅Succeeded

For more details, please refer to the build report.

[github-actions]

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.
Get Help
Docs Support Teams Channel
Resolve Merge Conflict