Skip to content

Commit ee19f47

Browse files
authored
Fixing section link1
1 parent 509a941 commit ee19f47

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/azure-monitor/platform/alerts-using-migration-tool.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ The migration process converts classic alert rules to new, equivalent alert rule
3232

3333
- Both the notification payload format and the APIs to create and manage new alert rules are different from those of the classic alert rules because they support more features. [Learn how to prepare for the migration](alerts-prepare-migration.md).
3434

35-
- Some classic alert rules cannot be migrated by using the tool. [Learn which rules cannot be migrated and what to do with them](alerts-understand-migration.md#which-classic-alert-rules-can-be-migrated).
35+
- Some classic alert rules cannot be migrated by using the tool. [Learn which rules cannot be migrated and what to do with them](alerts-understand-migration.md#which-classic-alert-rules-cannot-be-migrated).
3636

3737
> [!NOTE]
3838
> The migration process won't impact the evaluation of your classic alert rules. They'll continue to run and send alerts until they're migrated and the new alert rules take effect.

0 commit comments

Comments
 (0)