You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/virtual-machines/troubleshoot-maintenance-configurations.md
+15-4Lines changed: 15 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -68,22 +68,33 @@ If you move a resource to a different resource group or subscription, scheduled
68
68
69
69
#### Resolution
70
70
71
-
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.
71
+
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.**As a pre requisite, first remove the assignment before following the steps.**
72
72
73
73
If you're using a `static` scope:
74
74
75
-
1. Remove the resource assignment.
76
75
1. Move the resource to a different resource group or subscription.
77
76
1. Re-create the resource assignment.
78
77
79
78
If you're using a `dynamic` scope:
80
79
81
-
1. Remove the resource assignment.
82
80
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.
83
81
1. Move the resource to a different resource group or subscription.
84
82
1. Re-create the resource assignment.
85
83
86
-
If you miss any of the preceding steps, please reach out to the support team for mitigation.
84
+
If any of the steps are missed, please move the resource to the previous resource group or subscription ID and reattempt the steps.
85
+
86
+
> [!NOTE]
87
+
> If the resource group is deleted, recreate it with the same name. If the subscription ID is deleted, reach out to the support team for mitigation.
88
+
89
+
### Maintenance Configuration didn't trigger on the configured date time
90
+
91
+
#### Problem
92
+
93
+
After creating a Maintenance Configuration with a repeat value of either week or month, you expect the schedule to start at the specified date and time and then recur based on the chosen interval. However, the schedule didn't trigger at the start date and time.
94
+
95
+
#### Resolution
96
+
97
+
The Maintenance Configuration first run occurs on the first recurrence value following the specified start date, not necessarily on the start date itself. For example, if the maintenance configuration starts on January 17th (Wednesday) and is set to recur every Monday, the first run of the schedule will be on the first Monday after January 17th, which is January 22nd.
0 commit comments