Skip to content

Commit f3d796b

Browse files
authored
Merge pull request #100795 from shants123/patch-10
Edit to redirect to correct Activity Log Alerts
2 parents 6e8f96b + de6f4ef commit f3d796b

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/virtual-machines/maintenance-notifications.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ Azure periodically performs updates to improve the reliability, performance, and
2525

2626
Planned maintenance that requires a reboot is scheduled in waves. Each wave has different scope (regions).
2727

28-
- A wave starts with a notification to customers. By default, notification is sent to subscription owner and co-owners. You can add more recipients and messaging options like email, SMS, and webhooks, using [Activity Log Alerts](../azure-monitor/platform/platform-logs-overview.md).
28+
- A wave starts with a notification to customers. By default, notification is sent to subscription owner and co-owners. You can add more recipients and messaging options like email, SMS, and webhooks, using [Activity Log Alerts](../service-health/alerts-activity-log-service-notifications.md).
2929
- Once a notification goes out, a *self-service window* is made available. During this window, you can query which of your virtual machines are affected and start maintenance based on your own scheduling needs. The self-service window is typically about 35 days.
3030
- After the self-service window, a *scheduled maintenance window* begins. At some point during this window, Azure schedules and applies the required maintenance to your virtual machine.
3131

0 commit comments

Comments
 (0)