Update troubleshooting guidance for Linux VM provisioning

[raulalvarezg]

Fix: Make Scope Explicit

Added this immediately after Symptoms

[!IMPORTANT]> This article focuses on Linux VM provisioning failures, most commonly seen when deploying from custom images.>> If the deployment fails due to capacity, SKU availability, or regional allocation, see:> - Troubleshoot Azure VM allocation failures> - Troubleshoot issues when creating virtual machines in Azure

This single block eliminates cross‑pollination complaints without removing content.

Fix the misleading Symptoms opener (this is critical) Current problem
The opening implies all deployment failures, but the entire article is image‑centric.

Replace this paragraph under Symptoms
Current
A typical provisioning failure scenario occurs after you create a custom image and then deploy a virtual machine (VM) from that image.

This is actually correct, but it needs to be declared as the primary scenario, not an example.

Changed to:
Most Linux VM provisioning failures described in this article occur when you deploy a virtual machine (VM) from a custom image that wasn't prepared or generalized correctly.

No logic change — just removes ambiguity.

Fix typo:
Diff- toutputext + json

Improves rendering and linting.

Pull request guidance

Thank you for submitting your contribution to our support content! Our team works closely with subject matter experts in CSS and PMs in the product group to review all content requests to ensure technical accuracy and the best customer experience. This process can sometimes take one or more days, so we greatly appreciate your patience.

We also need your help in order to process your request as soon as possible:

• We won't act on your pull request (PR) until you type "#sign-off" in a new comment in your pull request (PR) to indicate that your changes are complete.

• After you sign off in your PR, the article will be tech reviewed by the PM or SME if it has more than minor changes. Once the article is approved, it will undergo a final editing pass before being merged.

[prmerger-automator]

@raulalvarezg : 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 d118c9c:

💡 Validation status: suggestions

File	Status	Preview URL	Details
support/azure/virtual-machines/linux/troubleshoot-deployment-new-vm-linux.md	💡Suggestion		Details

support/azure/virtual-machines/linux/troubleshoot-deployment-new-vm-linux.md

• Line 27, Column 5: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://learn.microsoft.com/troubleshoot/azure/virtual-machines/allocation-failure' will be broken in isolated environments. Replace with a relative link.
• Line 28, Column 5: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://learn.microsoft.com/troubleshoot/azure/virtual-machines/troubleshoot-deployment-overview' will be broken in isolated environments. Replace with a relative link.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

[mries]

Looks like a pretty simple update. just a note and syntax change.