Skip to content

Commit 5558c9e

Browse files
Link updates
1 parent 8ad47ae commit 5558c9e

2 files changed

Lines changed: 4 additions & 4 deletions

File tree

articles/backup/guidance-best-practices.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Guidance and best practices
33
description: Discover the best practices and guidance for backing up cloud and on-premises workload to the cloud
44
ms.topic: overview
5-
ms.date: 06/09/2025
5+
ms.date: 11/26/2025
66
ms.reviewer: dapatil
77
ms.service: azure-backup
88
author: AbhishekMallick-MS
@@ -365,7 +365,7 @@ You can configure such critical alerts and route them to any preferred notificat
365365

366366
- If you need to **create custom alerts** (for example, alerts of successful jobs) then use Log Analytics. In Azure Monitor, you can create your own alerts in a Log Analytics workspace. Hybrid workloads (DPM/MABS) can also send data to LA and use LA to provide common alerts across workloads supported by Azure Backup.
367367

368-
- You can also get notifications through built-in Recovery Services vault **activity logs**. However, it supports limited scenarios and isn't suitable for operations such as scheduled backup, which aligns better with resource logs than with activity logs. To learn more about these limitations and how you can use Log Analytics workspace for monitoring and alerting at scale for all your workloads that are protected by Azure Backup, refer to this [article](backup-azure-monitoring-use-azuremonitor.md#using-log-analytics-to-monitor-at-scale).
368+
- You can also get notifications through built-in Recovery Services vault **activity logs**. However, it supports limited scenarios and isn't suitable for operations such as scheduled backup, which aligns better with resource logs than with activity logs. To learn more about these limitations and how you can use Log Analytics workspace for monitoring and alerting at scale for all your workloads that are protected by Azure Backup, refer to this [article](backup-azure-monitoring-use-azuremonitor.md#monitor-at-scale-using-log-analytics-workspace).
369369

370370
#### Automatic Retry of Failed Backup Jobs
371371

articles/backup/move-to-azure-monitor-alerts.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Backup Classic Alerts using Azure Backup
33
description: Learn how to back up Classic Alerts in the Azure Recovery Services vault.
44
ms.topic: how-to
5-
ms.date: 03/17/2025
5+
ms.date: 11/26/2025
66
ms.service: azure-backup
77
author: AbhishekMallick-MS
88
ms.author: v-mallicka
@@ -91,7 +91,7 @@ If the frequency was set to an hourly digest, and an alert was raised and resolv
9191

9292
> [!NOTE]
9393
>- If a destructive operation, such as **stop protection with delete data** is performed, an alert is raised and an email is sent to subscription owners, admins, and co-admins even if notifications aren't configured for the Recovery Services vault.
94-
>- To configure notification for successful jobs, use [Log Analytics](backup-azure-monitoring-use-azuremonitor.md#using-log-analytics-workspace).
94+
>- To configure notification for successful jobs, use [Log Analytics](backup-azure-monitoring-use-azuremonitor.md#monitor-backup-jobs-using-log-analytics-workspace).
9595
9696
## Inactivating alerts
9797

0 commit comments

Comments
 (0)