Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.
Before moving a VM to a new resource group, verify that any existing maintenance configuration assignments are removed. This is important because the system does not support transferring resources with active configurations between resource groups or subscriptions.
After moving the VM, create a new maintenance configuration. When doing this, check that you assign the VM from its new resource group to the new maintenance configuration. If you try to use the same name for the configuration as before, allow at least 20 minutes for backend cleanup before recreating it.
If you are using dynamic scopes in your maintenance configuration, initiate or wait for the next scheduled run. This can help in completely removing any stale assignments related to the VM before re-adding it.
Reference:
https://learn.microsoft.com/en-us/azure/virtual-machines/troubleshoot-maintenance-configurations
https://learn.microsoft.com/en-us/azure/virtual-machines/maintenance-configurations-portal
Feel free to reach out if you have any further questions or need additional information—I’m happy to assist!
Please provide your valuable comments
Please do not forget to "Accept the answer” and “upvote it” wherever the information provided helps you, this can be beneficial to other community members.it would be greatly appreciated and helpful to others.