Skip to content

Commit ff2ac93

Browse files
Merge pull request #274496 from ApnaLakshay/Move-update-and-recurrence-value-mention-in-documentation
added changes
2 parents 6b46022 + 0f3f907 commit ff2ac93

File tree

1 file changed

+15
-4
lines changed

1 file changed

+15
-4
lines changed

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

Lines changed: 15 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -68,22 +68,33 @@ If you move a resource to a different resource group or subscription, scheduled
6868

6969
#### Resolution
7070

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.**
7272

7373
If you're using a `static` scope:
7474

75-
1. Remove the resource assignment.
7675
1. Move the resource to a different resource group or subscription.
7776
1. Re-create the resource assignment.
7877

7978
If you're using a `dynamic` scope:
8079

81-
1. Remove the resource assignment.
8280
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.
8381
1. Move the resource to a different resource group or subscription.
8482
1. Re-create the resource assignment.
8583

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.
8798

8899
### Creation of a dynamic scope fails
89100

0 commit comments

Comments
 (0)