Merge branch 'new-tools' of https://github.com/scottazure/supportarticles-docs-pr into pr/ScottAzure/10161

Author: ryanberg-aquent

support/azure/virtual-machines/linux/extensions-stop-running.md

@@ -17,9 +17,9 @@ _Original KB number:_   4099558
 
 ## Symptoms
 
-The Linux VM Agent fails to process extensions. This causes some extensions to stop running, which affects some dependent Azure services, such as Azure Backup Azure Site Recovery.
+The Linux VM Agent doesn't process extensions. Because of this failure, some extensions stop running. This issue affects some dependent Azure services, such as Azure Backup Azure Site Recovery.
 
-You will see extension downgrade errors similar to this recorded in /var/log/waagent.log:
+When this issue occurs, you see extension downgrade error entries in /var/log/waagent.log that resemble the following example:
 
 > 2018/03/16 12:00:46.196121 ERROR Event: name=extensionName, op=None, message=[ExtensionError] Downgrade not allowed, duration=0
 
@@ -28,7 +28,7 @@ You will see extension downgrade errors similar to this recorded in /var/log/wa
 
 ## Status
 
-Microsoft is taking steps to automatically resolve this issue for affected VMs. On those VMs you will see an additional Microsoft extension installed:  
+Microsoft is taking steps to automatically resolve this issue for affected VMs. On those VMs, an additional Microsoft extension is being installed:
 
 - Extension Publisher: Microsoft.CPlat.Core
 - Extension Type: RunCommandLinux  

support/azure/virtual-machines/linux/linux-image-provisioning-agent-update-awareness.md

@@ -1,5 +1,5 @@
 ---
-title: Linux Image Provisioning Agent update awareness
+title: Linux Image Provisioning Agent Update Awareness
 description: Provides the update awareness and frequently asked questions about Linux Image Provisioning Agent.
 ms.date: 09/15/2025
 ms.service: azure-virtual-machines
@@ -17,38 +17,38 @@ _Original KB number:_   4538386
 
 ## Summary
 
-Many Linux Azure Marketplace images contain an **Azure Linux Agent**, which is responsible for completing the setup of the newly created Virtual Machine (VM), such as setting the hostname, username, password/ ssh keys, and mounting an ephemeral disk. This setup process is known as 'provisioning'. In addition, the agent provides support for Azure VM Extensions.
+Many Linux Azure Marketplace images contain an **Azure Linux Agent** that's responsible for completing the setup of the newly created virtual machine (VM). The setup includes setting the hostname, username, and password/ ssh keys, and mounting an ephemeral disk. This setup process is known as 'provisioning'. Additionally, the agent provides support for Azure VM extensions.
 
-The images themselves will be updated to be provisioned using an open-source provisioning agent, [cloud-init](/azure/virtual-machines/linux/using-cloud-init). cloud- init offers many additional benefits over the Linux Agent, including:
+The images themselves are updated to be provisioned by using an open source provisioning agent, [cloud-init](/azure/virtual-machines/linux/using-cloud-init). The cloud- init agent offers many additional benefits over the Linux Agent, including:
 
 - Performance - Using cloud-init with Azure, you can see improved reduced VM creation times in most cases.
-- VM customization - cloud-init allows you to pass down VM configurations to cloud-init via [custom-data](/azure/virtual-machines/linux/using-cloud-init#deploying-a-cloud-init-enabled-virtual-machine), such as running scripts, installing packages, and adding users.
-- Migration - If you are migrating from other clouds, you can migrate cloud- init configurations, and modify them where necessary to work with your Azure deployments.
+- VM customization - cloud-init enables you to pass down VM configurations to cloud-init through [custom-data](/azure/virtual-machines/linux/using-cloud-init#deploying-a-cloud-init-enabled-virtual-machine). This process includes such actions as running scripts, installing packages, and adding users.
+- Migration - If you're migrating from other clouds, you can migrate cloud-init configurations, and modify them where necessary to work with together your Azure deployments.
 
 [!INCLUDE [VM assist troubleshooting tools](~/includes/azure/vmassist-include.md)]
 
 ## More information
 
-### What do you need to do?
+### Necessary actions
 
-- If you deploy these Azure Marketplace images, then there is nothing further that you need to do. You can immediately take advantage of the benefits after the update.
-- If you are creating custom images that derive from these images, and use the Linux Agent to process custom-data, check that your images still work correctly.
+- If you deploy these Azure Marketplace images, then there is nothing more that you have to do. You can immediately take advantage of the benefits after the update.
+- If you create custom images from these images, and use the Linux Agent to process custom data, verify that your images still work correctly.
 
-    cloud- init supports multiple input types, including a bash script or a cloud- init config. Review the 'cloud- init'[user-data](https://cloudinit.readthedocs.io/en/latest/topics/format.html) documentation.
-- See [this](/azure/virtual-machines/linux/using-cloud-init#cloud-init-overview) page for details on which images will be updated, and the timeline on when the updates will take place.
+    cloud-init supports multiple input types, including a bash script or a cloud-init config. Review the 'cloud-init'[user-data](https://cloudinit.readthedocs.io/en/latest/topics/format.html) documentation.
+- See [this](/azure/virtual-machines/linux/using-cloud-init#cloud-init-overview) page for details about which images will be updated, and the timeline for when the updates occur.
 
 ## Frequently asked questions
 
-Q1. Will the Azure Linux Agent still be installed in the images?  
+Q1. Is the Azure Linux Agent still installed in the images?  
 
-A1. Yes, the Azure Linux Agent is required for Azure VM extensions. The provisioning functionality will be disabled.  
+A1. Yes, the Azure Linux Agent is required for Azure VM extensions. The provisioning functionality is disabled.  
 
 Q2. Can the Azure Linux Agent and cloud-init be installed in the same image?  
 
-A2. Yes. To ensure that there is no conflict, the Linux Agent provisioning code is disabled and will not run.  
+A2. Yes. To ensure that there is no conflict, the Linux Agent provisioning code is disabled and won't run.  
 
-Q3. How can I tell if my image has been provisioned by cloud-init?  
+Q3. How can I tell whether my image is provisioned by cloud-init?  
 
-A3. Run `cloud-init status` to see if cloud-init has run.
+A3. Run `cloud-init status` to learn whether cloud-init ran.
 
 [!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]

support/azure/virtual-machines/linux/linux-vm-extension-status-not-reported.md

@@ -1,5 +1,5 @@
 ---
-title: Linux VM extension status isn't reported after Azure Linux Agent 2.2.19 update
+title: Linux VM Extension Status Isn't Reported After Azure Linux Agent 2.2.19 Update
 description: Discusses a problem in which the Linux VM extension status is not reported after an Azure Linux Agent update to version 2.2.19.
 ms.date: 07/21/2020
 ms.reviewer: danis, danis
@@ -15,24 +15,24 @@ _Original KB number:_   4077547
 
 [!INCLUDE [VM assist troubleshooting tools](~/includes/azure/vmassist-include.md)]
 
-This article provides a solution to an issue in which the Linux VM extension status is not reported after an Azure Linux Agent update to version 2.2.19.
+This article provides a solution to a problem in which the Linux VM extension status is not reported after an Azure Linux Agent update to version 2.2.19.
 
 ## Symptoms
 
-On a Linux virtual machine (VM) that's running on an instance of Microsoft Azure that has Azure Linux Agent 2.2.19 installed, you don't see the extension status being reported by using either the portal or Azure Command-Line Interface (Azure CLI).
+On a Linux virtual machine (VM) that's running on an instance of Microsoft Azure that has Azure Linux Agent 2.2.19 installed, you don't see the extension status reported. This problem occurs in both the Azure portal or Azure Command-Line Interface (Azure CLI).
 
 ## Cause
 
 This problem occurs because of a [known issue](https://github.com/Azure/WALinuxAgent/wiki/Known-Issues#2219---protocolerror-varlibwaagentgoalstate1xml-is-missing).
 
 ## Resolution
 
-Microsoft is taking steps to automatically resolve this problem. For VMs that have been automatically resolved, you will see the following additional Microsoft extension installed on the affected VMs:
+Microsoft is taking steps to automatically resolve this problem. For VMs that were automatically resolved, you see the following additional Microsoft extension installed on the affected VMs:
 
 - **Extension publisher:** Microsoft.CPlat.Core
 - **Extension type:** RunCommandLinux
 
-You can use [Azure CLI](/cli/azure/install-azure-cli)  to query the extensions that are assigned to a VM. To do this, run the following command:
+You can use [Azure CLI](/cli/azure/install-azure-cli) to query the extensions that are assigned to a VM. To use this query, run the following command:
 
 ```Azure CLI
 az vm extension list --vm-name <vmName> -g <resGroupName>