Merge pull request #107427 from adityabalaji-msft/adbalaji-wb-diagnostics

minor addition to diagnostics article

Author: PRMerger12

articles/backup/backup-azure-diagnostic-events.md

@@ -51,7 +51,9 @@ Once data flows into the LA Workspace, dedicated tables for each of these events
 
 Traditionally, all backup-related diagnostics data for a vault has been contained in a single event called ‘AzureBackupReport’. The six events described above are, in essence, a decomposition of all the data contained in AzureBackupReport. 
 
-Currently, we continue to support the AzureBackupReport event for backward-compatibility, in cases where users have existing custom queries on this event, for example, custom log alerts, custom visualizations etc. However, we recommend choosing the new events for all new diagnostics settings on the vault since this makes the data much easier to work with in log queries, provides better discoverability of schemas and their structure, improves performance across both ingestion latency and query times. Support for using the Azure Diagnostics mode will eventually be phased out and hence choosing the new events may help you to avoid complex migrations at a later date.
+Currently, we continue to support the AzureBackupReport event for backward-compatibility, in cases where users have existing custom queries on this event, for example, custom log alerts, custom visualizations etc. However, **we recommend moving to the new events as early as possible**, since this makes the data much easier to work with in log queries, provides better discoverability of schemas and their structure, improves performance across both ingestion latency and query times. **Support for using the Azure Diagnostics mode will eventually be phased out and hence choosing the new events may help you to avoid complex migrations at a later date**.
+
+Use Azure Backup's built-in policy to add a new diagnostics setting with the 6 new events, for all your vaults in a specified scope: [Configure Vault Diagnostics Settings at scale](https://docs.microsoft.com/azure/backup/azure-policy-configure-diagnostics)
 
 You may choose to create separate diagnostics settings for AzureBackupReport and the six new events, until you have migrated all of your custom queries to use data from the new tables. The below image shows an example of a vault having two diagnostic settings. The first setting, named **Setting1** sends data of AzureBackupReport event to an LA Workspace in AzureDiagnostics mode. The second setting, named **Setting2** sends data of the six new Azure Backup events to an LA Workspace in Resource Specific mode.