Merge pull request #274004 from ApnaLakshay/Adding-delete-assignment-scenario

Adding delete assignment scenario

Author: prmerger-automator[bot]

articles/update-manager/troubleshoot.md

@@ -87,16 +87,30 @@ The subscriptions in which the Arc-enabled servers are onboarded aren't producin
 #### Resolution
 Ensure that the Arc servers subscriptions are registered to Microsoft.Compute resource provider so that the periodic assessment data is generated periodically as expected. [Learn more](../azure-resource-manager/management/resource-providers-and-types.md#register-resource-provider)
 
-### Maintenance configuration isn't applied when VM is moved to a different subscription
+### Maintenance configuration isn't applied when VM is moved to a different subscription or resource group
 
 #### Issue
 
-When a VM is moved to another subscription, the scheduled maintenance configuration associated to the VM isn't running.
+When a VM is moved to another subscription or resource group, the scheduled maintenance configuration associated to the VM isn't running.
 
 #### Resolution
 
-If you move a VM to a different resource group or subscription, the scheduled patching for the VM stops working as this scenario is currently unsupported by the system. You can delete the older association of the moved VM and create the new association to include the moved VMs in a maintenance configuration.
+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.
 
+If you're using a `static` scope:
+
+1. Remove the resource assignment.
+1. Move the resource to a different resource group or subscription.
+1. Re-create the resource assignment.
+
+If you're using a `dynamic` scope:
+
+1. Remove the resource assignment.
+1. Initiate or wait for the next scheduled run. This action prompts the system to completely remove the assignment, so you can proceed with the next steps.
+1. Move the resource to a different resource group or subscription.
+1. Re-create the resource assignment.
+
+If you miss any of the preceding steps, please reach out to the support team for mitigation.
 ### Unable to change the patch orchestration option to manual updates from automatic updates
 
 #### Issue

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

@@ -45,6 +45,21 @@ Scheduled patching fails with a `TimeOut` or `Failed` error after you move a VM
 
 This is a known bug, and we're working on resolving it. If you encounter this problem, contact the support team for assistance.
 
+### Unable to delete configuration assignment
+
+#### Problem
+
+Configuration assignment couldn't be removed or deleted from a particular maintenance configuration
+
+#### Resolution
+
+Use the following steps to mitigate this issue:
+
+1. Delete the existing maintenance configuration in which you are encountering this issue.
+1. Create a new maintenance configuration and assign the required set of dynamic scope and VMs as attached in the deleted maintenance configuration.
+
+If you want to create new maintenance configuration with the same name as the deleted maintenance configuration, you will have to wait 20 minutes for the cleanup to take place in the backend. The system won't allow the creation of maintenance configuration with the same name if cleanup is not performed in the backend. 
+
 ### Scheduled patching stops working after the resource is moved
 
 #### Problem
@@ -55,20 +70,20 @@ If you move a resource to a different resource group or subscription, scheduled
 
 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.
 
-If you're using a static scope:
+If you're using a `static` scope:
 
 1. Remove the resource assignment.
 1. Move the resource to a different resource group or subscription.
 1. Re-create the resource assignment.
 
-If you're using a dynamic scope:
+If you're using a `dynamic` scope:
 
 1. Remove the resource assignment.
 1. Initiate or wait for the next scheduled run. This action prompts the system to completely remove the assignment, so you can proceed with the next steps.
 1. Move the resource to a different resource group or subscription.
 1. Re-create the resource assignment.
 
-If you miss any of the preceding steps, you can reassign the resource to the original assignment and repeat the steps sequentially.
+If you miss any of the preceding steps, please reach out to the support team for mitigation.
 
 ### Creation of a dynamic scope fails