more updates

AbhishekMallick01 · AbhishekMallick01 · commit 359f2de5ef81 · 2023-03-29T17:24:07.000+05:30
diff --git a/articles/backup/backup-azure-monitoring-use-azuremonitor.md b/articles/backup/backup-azure-monitoring-use-azuremonitor.md
@@ -57,9 +57,9 @@ For more information, see [Create, view, and manage log alerts by using Azure Mo
 
 ### Sample Kusto queries
 
-The default graphs give you Kusto queries for basic scenarios on which you can build alerts. You can also modify the queries to get the data you want to be alerted on. Paste the following sample Kusto queries in the **Logs** page and then create alerts on the queries.
+The default graphs give you Kusto queries for basic scenarios on which you can build alerts. You can also modify the queries to fetch the data you want to be alerted on. Paste the following sample Kusto queries on the **Logs** page, and then create alerts on the queries.
 
-Recovery Services vaults and Backup vaults send data to a common set of tables that are listed in this article. However, there are slight differences in the schema for Recovery Services vaults and Backup vaults (refer [this page](backup-azure-monitoring-built-in-monitor.md) for more details). Hence this section is split into multiple sub-sections, so that you can use the right queries depending on which workload or vault types you are looking to query.
+Recovery Services vaults and Backup vaults send data to a common set of tables that are listed in this article. However, there are slight differences in the schema for Recovery Services vaults and Backup vaults ([learn more](backup-azure-monitoring-built-in-monitor.md)). So, this section is split into multiple sub-sections that helps you to use the right queries depending on which workload or vault types you want to query.
 
 #### Queries common across Recovery Services vaults and Backup vaults 
 
diff --git a/articles/backup/backup-reports-email.md b/articles/backup/backup-reports-email.md
@@ -27,7 +27,7 @@ To configure email tasks via Backup Reports, perform the following steps:
 3.	After you click **Submit** and **Confirm**, the logic app will get created. The logic app and the associated API connections are created with the tag **UsedByBackupReports: true** for easy discoverability. You'll need to perform a one-time authorization step for the logic app to run successfully, as described in the section below.
 
 > [!NOTE]
-> Support for Backup vault workloads (Azure Database for PostgreSQL Server, Azure Blobs, Azure Disks) was added to the logic app templates in April 2023. Hence, if you have deployed these logic apps on an earlier date, you will have to redeploy these using the above steps if you wish to see data for Backup vault workloads in your email reports.
+> Support for Backup vault workloads (Azure Database for PostgreSQL Server, Azure Blobs, Azure Disks) is added to the logic app templates in April 2023. So, if you've deployed these logic apps on an earlier date, you'll have to redeploy these using the above steps if you want to see data for Backup vault workloads in your email reports.
 
 ## Authorize connections to Azure Monitor Logs and Office 365
 
diff --git a/articles/backup/configure-reports.md b/articles/backup/configure-reports.md
@@ -25,7 +25,9 @@ Today, Azure Backup provides a reporting solution that uses [Azure Monitor logs]
 - For MABS workloads, Backup reports are supported for MABS Version 13.0.415.0 and above and Agent Version 2.0.9170.0 and above.
 - Backup reports can be viewed across all backup items, vaults, subscriptions, and regions as long as their data is being sent to a Log Analytics workspace that the user has access to. To view reports for a set of vaults, you only need to have reader access to the Log Analytics workspace to which the vaults are sending their data. You don't need to have access to the individual vaults.
 - If you're an [Azure Lighthouse](../lighthouse/index.yml) user with delegated access to your customers' subscriptions, you can use these reports with Azure Lighthouse to view reports across all your tenants.
-- Currently, data can be viewed in Backup Reports across a maximum of 100 Log Analytics Workspaces (across tenants). However, please note that depending on the complexity of queries and the volume of data processed, it is possible that you might face errors when selecting a large number of workspaces that is less than 100, in some cases. We recommend that you limit the number of workspaces being queried at a time.
+- Currently, data can be viewed in Backup Reports across a maximum of 100 Log Analytics Workspaces (across tenants).
+  >[!Note]
+  >Depending on the complexity of queries and the volume of data processed, it's possible that you might see errors when selecting a large number of workspaces that is less than 100, in some cases. We recommend that you limit the number of workspaces being queried at a time.
 - Data for log backup jobs currently isn't displayed in the reports.
 
 [!INCLUDE [backup-center.md](../../includes/backup-center.md)]
@@ -44,7 +46,7 @@ By default, the data in a Log Analytics workspace is retained for 30 days. To se
 
 ### 2. Configure diagnostics settings for your vaults
 
-Azure Resource Manager resources, such as Recovery Services vaults, record information about scheduled operations and user-triggered operations as diagnostics data. To configure diagnostics settings for your vaults, follow the below steps:
+Azure Resource Manager resources, such as Recovery Services vaults, record information about scheduled operations and user-triggered operations as diagnostics data. To configure diagnostics settings for your vaults, follow these steps:
 
 **Choose a vault type**:
 
@@ -54,20 +56,22 @@ In the monitoring section of your Recovery Services vault, select **Diagnostics
 
 ![Diagnostics settings pane for RS Vault](./media/backup-azure-configure-backup-reports/recovery-services-vault-diagnostics-settings.png)
 
-Azure Backup also provides a built-in Azure Policy definition, which automates the configuration of diagnostics settings for all Recovery services vaults in a given scope. To learn how to use this policy, see [Configure vault diagnostics settings at scale](./azure-policy-configure-diagnostics.md).
+Azure Backup also provides a built-in Azure Policy definition, which automates the configuration of diagnostics settings for all Recovery Services vaults in a given scope. To learn how to use this policy, see [Configure vault diagnostics settings at scale](./azure-policy-configure-diagnostics.md).
 
 # [Backup vaults](#tab/backup-vaults)
 
 In the monitoring section of your Backup vault, select **Diagnostics settings** and specify the target for the Backup vault's diagnostic data.
 
 ![Diagnostics settings pane for Backup vault](./media/backup-azure-configure-backup-reports/backup-vault-diagnostics-settings.png)
 
+---
+
 > [!NOTE]
 > After you configure diagnostics, it might take up to 24 hours for the initial data push to complete. After data starts flowing into the Log Analytics workspace, you might not see data in the reports immediately because data for the current partial day isn't shown in the reports. For more information, see [Conventions used in Backup reports](#conventions-used-in-backup-reports). We recommend that you start viewing the reports two days after you configure your vaults to send data to Log Analytics.
 
 #### 3. View reports in the Azure portal
 
-After you've configured your vaults to send data to Log Analytics, view your Backup reports by going to Backup center and selecting **Backup Reports**. Select the relevant workspace(s) in the **Get started** tab.
+After you've configured your vaults to send data to Log Analytics, view your Backup reports by going to Backup center and selecting **Backup Reports**. Select the relevant workspace(s) on the **Get started** tab.
 
 ![Backup center dashboard](./media/backup-azure-configure-backup-reports/backup-reports-entry.png)
 
@@ -92,8 +96,8 @@ Use this tab to view key billing parameters for your backups. The information sh
    ![Usage tab](./media/backup-azure-configure-backup-reports/usage.png)
 
 > [!NOTE]
-> For Azure File, Azure Blob and Azure Disk workloads, storage consumed will show up as zero. This is because field refers to the storage consumed in the vault, and for Azure File, Azure Blob and Azure Disk, only the snapshot based backup solution is supported in the reports today.
-> For DPM workloads, users might see a slight difference (of the order of 20 MB per DPM server) between the usage values shown in the reports as compared to the aggregate usage value as shown in the Recovery Services vault **Overview** tab. This difference is accounted for by the fact that every DPM server being registered for backup has an associated 'metadata' datasource which isn't surfaced as an artifact for reporting.
+>- For Azure File, Azure Blob and Azure Disk workloads, storage consumed shows as *zero*. This is because field refers to the storage consumed in the vault, and for Azure File, Azure Blob, and Azure Disk; only the snapshot-based backup solution is currently supported in the reports.
+>- For DPM workloads, users might see a slight difference (of the order of 20 MB per DPM server) between the usage values shown in the reports as compared to the aggregate usage value as shown on the Recovery Services vault **Overview** tab. This difference is accounted for by the fact that every DPM server being registered for backup has an associated 'metadata' datasource, which isn't surfaced as an artifact for reporting.
 
 ##### Jobs
 
@@ -102,7 +106,7 @@ Use this tab to view long-running trends on jobs, such as the number of failed j
    ![Jobs tab](./media/backup-azure-configure-backup-reports/jobs.png)
 
 > [!NOTE]
-> For Azure Database for PostgreSQL, Azure Blob and Azure Disk workloads, data transferred field is currently not available in the Jobs table.
+> For Azure Database for PostgreSQL, Azure Blob, and Azure Disk workloads, data transferred field is currently not available in the *Jobs* table.
 
 ##### Policies
 
@@ -125,7 +129,7 @@ Once you've identified an inactive resource, you can investigate the issue furth
 ![Optimize tab - Inactive Resources](./media/backup-azure-configure-backup-reports/optimize-inactive-resources.png)
 
 > [!NOTE]
-> For Azure Database for PostgreSQL, Azure Blob and Azure Disk workloads, Inactive Resources view is currently not supported.
+> For Azure Database for PostgreSQL, Azure Blob, and Azure Disk workloads, Inactive Resources view is currently not supported.
 
 ###### Backup Items with a large retention duration
 
@@ -138,7 +142,7 @@ For database workloads like SQL and SAP HANA, the retention periods shown in the
 ![Optimize tab - Retention Optimizations](./media/backup-azure-configure-backup-reports/optimize-retention.png)
 
 > [!NOTE]
-> For backup instances which are using the vault-standard tier, the Retention Optimizations grid takes into consideration the retention duration in the vault-standard tier. For backup instances which are not using the vault tier (for example, items protected by Azure Disk Backup solution), the grid takes into consideration the snapshot tier retention.
+> For backup instances that are using the vault-standard tier, the Retention Optimizations grid takes into consideration the retention duration in the vault-standard tier. For backup instances that aren't using the vault tier (for example, items protected by Azure Disk Backup solution), the grid takes into consideration the snapshot tier retention.
 
 ###### Databases configured for daily full backup
 
diff --git a/articles/backup/move-to-azure-monitor-alerts.md b/articles/backup/move-to-azure-monitor-alerts.md
@@ -49,8 +49,8 @@ The following table lists the differences between classic backup alerts and buil
 | **Pricing** | There are no additional charges for this solution. | Alerts for critical operations/failures generate by default (that you can view in the Azure portal or via non-portal interfaces) at no additional charge. However, to route these alerts to a notification channel (such as email), it incurs a minor charge for notifications beyond the *free tier* (of 1000 emails per month). Learn more about [Azure Monitor pricing](https://azure.microsoft.com/pricing/details/monitor/). |
 
 > [!NOTE]
-> If you have existing custom Azure Resource Graph (ARG) queries written on classic alerts data, you will need to update these queries to fetch information from Azure Monitor based alerts. You can use the "AlertsManagementResources" table in ARG to query Azure Monitor alerts data.
-> If you are sending classic alerts to Log Analytics workspace/Storage account/Event Hub via diagnostics settings, you will need to update these automations as well. To send the fired Azure Monitor based alerts to a destination of your choice, you can create an alert processing rule and action group that routes these alerts to a logic app, webhook, or runbook that in turn sends these alerts to the required destination.
+>- If you've existing custom Azure Resource Graph (ARG) queries written on classic alerts data, you'll need to update these queries to fetch information from Azure Monitor-based alerts. You can use the *AlertsManagementResources* table in ARG to query Azure Monitor alerts data.
+>- If you send classic alerts to Log Analytics workspace/Storage account/Event Hub via diagnostics settings, you'll also need to update these automation. To send the fired Azure Monitor based alerts to a destination of your choice, you can create an alert processing rule and action group that routes these alerts to a logic app, webhook, or runbook that in turn sends these alerts to the required destination.
 
 Azure Backup now provides a guided experience via Backup center that allows you to switch to built-in Azure Monitor alerts and notifications with just a few selects. To perform this action, you need to have access to the *Backup Contributor* and *Monitoring Contributor* Azure role-based access control (Azure RBAC) roles to the subscription.
 
