edit pass: maintenance-configurations

Author: ShawnJackson

articles/virtual-machines/maintenance-configurations-portal.md

@@ -54,7 +54,7 @@ With the Maintenance Configurations feature, you can control when to apply updat
 
 ## Assign the configuration
 
-1. On the details page of the maintenance configuration, select **Machines**, and then select **Add Machine**.
+1. On the details page of the maintenance configuration, select **Machines**, and then select **Add machine**.
 
     ![Screenshot that shows the button for adding a machine.](media/virtual-machines-maintenance-control-portal/maintenance-configurations-add-assignment.png)
 

articles/virtual-machines/maintenance-configurations-powershell.md

@@ -22,21 +22,21 @@ If you're looking for information about using Maintenance Configurations for sca
 > [!IMPORTANT]
 > Specific *scopes* support certain machine types and schedules. Be sure to select the right scope for your VM.
 
-## Enable the PowerShell module
+## Enable the Azure PowerShell module
 
 Make sure that `PowerShellGet` is up to date:
 
 ```azurepowershell-interactive
 Install-Module -Name PowerShellGet -Repository PSGallery -Force
 ```
 
-Install the `Az.Maintenance` PowerShell module:
+Install the `Az.Maintenance` Azure PowerShell module:
 
 ```azurepowershell-interactive
 Install-Module -Name Az.Maintenance
 ```
 
-Check that you're running the latest version of the `Az.Maintenance` PowerShell module (version 1.2.0):
+Check that you're running the latest version of `Az.Maintenance` (version 1.2.0):
 
 ```azurepowershell-interactive
 Get-Module -ListAvailable -Name Az.Maintenance
@@ -48,7 +48,7 @@ Ensure that you're running the appropriate version of `Az.Maintenance`:
 Import-Module -Name Az.Maintenance -RequiredVersion 1.2.0
 ```
 
-If you're installing locally, be sure to open your PowerShell prompt as an administrator.
+If you're installing locally, be sure to open your Azure PowerShell prompt as an administrator.
 
 You might be asked to confirm that you want to install from an untrusted repository. Enter **Y** or select **Yes to All** to install the module.
 
@@ -99,7 +99,7 @@ New-AzMaintenanceConfiguration
    -RecurEvery $recurEvery
 ```  
 
-Using `$scope = "Host"` ensures that the maintenance configuration is used for controlling updates on host machines. Ensure that you're creating a configuration for the specific scope of the machines that you're targeting. [Learn more about scopes](maintenance-configurations.md#scopes).
+Using `$scope = "Host"` ensures that the maintenance configuration is used for controlling updates on host machines. Be sure to create a configuration for the specific scope of the machines that you're targeting. [Learn more about scopes](maintenance-configurations.md#scopes).
 
 ### OS image
 
@@ -132,7 +132,7 @@ New-AzMaintenanceConfiguration
 
 ### Guest
 
-The most recent addition to the Maintenance Configurations feature is the `InGuestPatch` scope. This example shows how to create a maintenance configuration for a guest scope by using PowerShell. For more information about this scope, see [Guest](maintenance-configurations.md#guest).
+The most recent addition to the Maintenance Configurations feature is the `InGuestPatch` scope. This example shows how to create a maintenance configuration for a guest scope by using Azure PowerShell. For more information about this scope, see [Guest](maintenance-configurations.md#guest).
 
 ```azurepowershell-interactive
 $RGName = "myMaintenanceRG"
@@ -185,7 +185,7 @@ Get-AzMaintenanceConfiguration | Format-Table -Property Name,Id
 
 ## Assign the configuration
 
-After you create your configuration, you might want to also assign machines to it by using PowerShell. You can use the [New-AzConfigurationAssignment](/powershell/module/az.maintenance/new-azconfigurationassignment) cmdlet.
+After you create your configuration, you might want to also assign machines to it by using Azure PowerShell. You can use the [New-AzConfigurationAssignment](/powershell/module/az.maintenance/new-azconfigurationassignment) cmdlet.
 
 ### Isolated VM
 

articles/virtual-machines/troubleshoot-maintenance-configurations.md

@@ -13,45 +13,45 @@ ms.author: lnagpal
 
 This article outlines common problems and errors that might arise during the deployment or use of Maintenance Configurations for scheduled patching on virtual machines (VMs), along with strategies to address them.
 
-## A VM shuts down and is unresponsive when you use a dynamic scope in guest maintenance
+### A VM shuts down and is unresponsive when you use a dynamic scope in guest maintenance
 
-### Problem
+#### Problem
 
 A maintenance configuration doesn't install a scheduled patch on the VMs and gives a `ShutdownOrUnresponsive` error.
 
-### Resolution
+#### Resolution
 
 It takes 12 hours to complete the cleanup process for the maintenance configuration assignment. Be sure to keep a buffer of 12 hours before you create a VM with the same name.
 
 If you create a VM with the same name before the cleanup, Maintenance Configurations can't trigger the schedule.
 
-## A VM shuts down and is unresponsive when you use a static scope in guest maintenance
+### A VM shuts down and is unresponsive when you use a static scope in guest maintenance
 
-### Problem
+#### Problem
 
 A maintenance configuration doesn't install a scheduled patch on the VMs and gives a `ShutdownOrUnresponsive` error.
 
-### Resolution
+#### Resolution
 
 In a static scope, it's crucial to avoid relying on outdated VM configurations. Instead, prioritize reassigning configurations after you re-create instances.
 
-## Scheduled patching times out or fails
+### Scheduled patching times out or fails
 
-### Problem
+#### Problem
 
 Scheduled patching fails with a `TimeOut` or `Failed` error after you move a VM by re-creating it with the same name in a different region. The portal might show the same VM twice because the previously created VM is removed from the back end.
 
-### Resolution
+#### Resolution
 
 This is a known bug, and we're working on resolving it. If you encounter this problem, contact the support team for assistance.
 
-## Scheduled patching stops working after the resource is moved
+### Scheduled patching stops working after the resource is moved
 
-### Problem
+#### Problem
 
 If you move a resource to a different resource group or subscription, scheduled patching for the resource stop working.
 
-### Resolution
+#### Resolution
 
 The system currently doesn't support moving resources across resource groups or subscriptions. As a workaround, use the following steps for the resource that you want to move.
 
@@ -70,121 +70,121 @@ If you're using a dynamic scope:
 
 If you miss any of the preceding steps, you can reassign the resource to the original assignment and repeat the steps sequentially.
 
-## Creation of a dynamic scope fails
+### Creation of a dynamic scope fails
 
-### Problem
+#### Problem
 
 You can't create a dynamic scope because of role-based access control (RBAC).
 
-### Resolution
+#### Resolution
 
 To create a dynamic scope, you must have the permission at the subscription level or at a resource group level. For more information, see the [list of permissions list for various resources](../update-manager/overview.md#permissions).
 
-## An update is stuck and not progressing
+### An update is stuck and not progressing
 
-### Problem
+#### Problem
 
 **Applies to:** :heavy_check_mark: Dedicated Hosts :heavy_check_mark: VMs
 
 If you redeploy a resource to a different cluster, and you create a pending update request by using the old cluster value, the request becomes stuck indefinitely.
 
-### Resolution
+#### Resolution
 
 If the status of an operation to apply an update is closed or not found, retry after 120 hours. If the problem persists, contact the support team for assistance.
 
-## A dedicated host is updated after a maintenance configuration is attached
+### A dedicated host is updated after a maintenance configuration is attached
 
-### Problem
+#### Problem
 
 A maintenance configuration doesn't block the update of a dedicated host, and the host is updated even after you attach a maintenance configuration.
 
-### Resolution
+#### Resolution
 
 If you re-create a dedicated host with the same name, Maintenance Configurations retains the old dedicated host ID, which prevents it from blocking updates. You can resolve this problem by removing the maintenance configuration and reassigning it. If the problem persists, contact the support team for assistance.
 
-## Patch installation fails for an invalid classification type
+### Patch installation fails for an invalid classification type
 
-### Problem
+#### Problem
 
 Patch installation fails because of an invalid classification type in a maintenance configuration.
 
 A previous bug prevented the system's patch operation from performing validation, and the maintenance configuration contained an invalid classification type.
 
-### Resolution
+#### Resolution
 
 The bug is fixed. Update the maintenance configuration and set the correct classification type.
 
-## A schedule isn't triggered
+### A schedule isn't triggered
 
-### Problem
+#### Problem
 
 If a resource has two maintenance configurations with the same trigger time and patch installation configuration, and both are assigned to the same VM or resource, only one maintenance configuration is triggered.
 
-### Resolution
+#### Resolution
 
 Modify the start time of one of the maintenance configurations to mitigate the problem. This is a workaround to a current system limitation in which Maintenance Configurations can't identify which maintenance configuration to trigger.
 
-## You can't create a dynamic scope for a resource group
+### You can't create a dynamic scope for a resource group
 
-### Problem
+#### Problem
 
 Dynamic scope validation fails because of a null value in the location.
 
-### Resolution
+#### Resolution
 
 This problem with dynamic scope validation causes regression in the validation process. We recommend that you provide the required set of locations for a dynamic scope at the resource-group level.
 
-## A dynamic scope isn't executed and no resources are patched
+### A dynamic scope isn't executed and no resources are patched
 
-### Problem
+#### Problem
 
 Dynamic scope flattening fails because of throttling, and the service can't determine which VMs are associated with the VM.
 
-### Resolution
+#### Resolution
 
 Make sure that the number of subscriptions per dynamic scope is less than 30. [Learn more about the service limits of dynamic scoping](../virtual-machines/maintenance-configurations.md#service-limits).
 
-## Configuration assignment of a dedicated host isn't cleaned up after the host's removal
+### Configuration assignment of a dedicated host isn't cleaned up after the host's removal
 
-### Problem
+#### Problem
 
 After you delete the dedicated hosts, configuration assignments that are attached to dedicated hosts still exist.
 
-### Resolution
+#### Resolution
 
 Before you delete a dedicated host, be sure to delete the maintenance configuration that's associated with it. If the dedicated host is deleted but still appears in the portal, contact the support team for assistance. Cleanup processes are currently in place for dedicated hosts, to help prevent any impact on customers.
 
-## You can't provide multiple tag values for dynamic scopes
+### You can't provide multiple tag values for dynamic scopes
 
-### Problem
+#### Problem
 
 If you use the Azure portal, you can't provide multiple tag values for dynamic scopes.
 
-### Resolution
+#### Resolution
 
 This feature currently isn't available in the portal. As a workaround, you can use the Azure CLI or Azure PowerShell to create a dynamic scope. The system accepts multiple values for tags when you use the Azure CLI or Azure PowerShell option.
 
-## A maintenance configuration is triggered again with an older trigger time
+### A maintenance configuration is triggered again with an older trigger time
 
-### Problem
+#### Problem
 
 There's a known issue in Maintenance Configurations related to the caching of old maintenance policies. If an old policy is cached, and a new instance moves the new policy processing, the old machine might trigger the schedule with the outdated start time.
 
-### Resolution
+#### Resolution
 
 We recommend that you update the maintenance configuration at least 1 hour before the scheduled time. If the problem persists, contact the support team for assistance.
 
-## A maintenance configuration times out while waiting for an ongoing update to finish on a resource
+### A maintenance configuration times out while waiting for an ongoing update to finish on a resource
 
-### Problem
+#### Problem
 
 In rare cases, if the host update window happens to coincide with the VM guest patching window, and if the guest patching window doesn't have sufficient time to run after the host update, the system shows this error message: "Schedule timeout, waiting for an ongoing update to complete the resource." The reason is that the platform allows only one update at a time.
 
-### Resolution
+#### Resolution
 
 Change the maintenance configuration schedule for the guest update for a time after the ongoing update is finished.
 
-## Maintenance Configurations doesn't support an API
+### Maintenance Configurations doesn't support an API
 
 The feature currently doesn't support the following APIs: