Added links for cross referencing recommendations

Author: AbbyMSFT

articles/azure-monitor/alerts-plan.md renamed to articles/azure-monitor/alerts/alerts-plan.md

@@ -10,14 +10,14 @@ ms.date: 09/04/2023
 
 > [!div class="checklist"]
 > - activity log alerts, service health alerts, and resource health alerts are free of charge. 
-> - When using log alerts, mimimize log alert frequency.
+> - When using log alerts, minimize log alert frequency.
 > - When using metric alerts, minimize the number of resources being monitored.
 
 ### Configuration recommendations
 
 | Recommendation | Benefit |
 |:---|:---|
-|Keep in mind that activity log alerts, service health alerts, and resource health alerts are free of charge|Azure Monitor activity alerts, service health alerts and resource health alerts are free. If what you want to monitor can be achieved with these alert types, use them.|
-|When using log alerts, mimimize log alert frequency|When configuring log alerts, keep in mind that the more frequent the rule evaluation, the higher the cost. Configure your rules accordingly.|
-|When using metric alerts, minimize the number of resources being monitored|Some resource types support metric alert rules that can monitor multiple resources of the same type. For these resource types, keep in mind that the rule can become expensive if the rule monitors many resources. To reduce costs, you can either reduce the scope of the metric alert rule or use log alert rules, which are less expensive to monitor a large number of resources. |
+|Keep in mind that activity log alerts, service health alerts, and resource health alerts are free of charge.|Azure Monitor activity alerts, service health alerts and resource health alerts are free. If what you want to monitor can be achieved with these alert types, use them.|
+|When using log alerts, minimize log alert frequency.|When configuring log alerts, keep in mind that the more frequent the rule evaluation, the higher the cost. Configure your rules accordingly.|
+|When using metric alerts, minimize the number of resources being monitored.|Some resource types support metric alert rules that can monitor multiple resources of the same type. For these resource types, keep in mind that the rule can become expensive if the rule monitors many resources. To reduce costs, you can either reduce the scope of the metric alert rule or use log alert rules, which are less expensive to monitor a large number of resources. |
 

articles/azure-monitor/includes/waf-alerts-cost.md

@@ -19,8 +19,8 @@ ms.date: 09/04/2023
 
 | Recommendation | Benefit |
 |:---|:---|
-|Use dynamic thresholds in metric alert rules where appropriate| Dynamic thresholds are use machine learning to determine the correct threshold, so you do not need to know the correct threshold to configure. Dynamic thresholds are also useful for rules that monitor multiple resources, and a single threshold cannot be configured for all of the resources. See [Dynamic thresholds in metric alerts](../alerts/alerts-dynamic-thresholds.md).|
-|Whenever possible, use one alert rule to monitor multiple resources|Using alert rules that monitor multiple resources reduces management overhead, by allowing you to manage one rule to monitor a large number of resources. |
-|To control behavior at scale, use alert processing rules|Alert processing rules can be used to reduce the number of alert rules you need to create and manage. See [Alert processing rules](../alerts/alerts-processing-rules.md) |
-|Leverage custom properties to enhance diagnostics |If the alert rule uses action groups, you can add your own properties to include in the alert notification payload. You can use these properties in the actions called by the action group, such as webhook, Azure function or logic app actions |
-| Leverage Logic Apps to customize the notification workflow and integrate with a variety of systems    |You can use Azure Logic Apps to build and customize workflows for integration. Use Logic Apps to customize your alert notifications. You can:<br/> - Customize the alerts email by using your own email subject and body format.<br/> - Customize the alert metadata by looking up tags for affected resources or fetching a log query search result.<br/> - Integrate with external services by using existing connectors like Outlook, Microsoft Teams, Slack, and PagerDuty. You can also configure the logic app for your own services.    |
+|Use [dynamic thresholds](../alerts/alerts-dynamic-thresholds.md) in metric alert rules where appropriate.| Dynamic thresholds are use machine learning to determine the correct threshold, so you do not need to know the correct threshold to configure. Dynamic thresholds are also useful for rules that monitor multiple resources, and a single threshold cannot be configured for all of the resources. See [Dynamic thresholds in metric alerts](../alerts/alerts-dynamic-thresholds.md).|
+|Whenever possible, use one alert rule to monitor multiple resources.|Using alert rules that monitor multiple resources reduces management overhead, by allowing you to manage one rule to monitor a large number of resources. |
+|To control behavior at scale, use [alert processing rules](../alerts/alerts-processing-rules.md).|Alert processing rules can be used to reduce the number of alert rules you need to create and manage.|
+|Leverage [custom properties](../alerts/alerts-create-new-alert-rule.md#custom-props) to enhance diagnostics.|If the alert rule uses action groups, you can add your own properties to include in the alert notification payload. You can use these properties in the actions called by the action group, such as webhook, Azure function or logic app actions.|
+| Leverage [Logic Apps](../alerts/alerts-logic-apps.md) to customize the notification workflow and integrate with a variety of systems.|You can use Azure Logic Apps to build and customize workflows for integration. Use Logic Apps to customize your alert notifications. You can:<br/> - Customize the alerts email by using your own email subject and body format.<br/> - Customize the alert metadata by looking up tags for affected resources or fetching a log query search result.<br/> - Integrate with external services by using existing connectors like Outlook, Microsoft Teams, Slack, and PagerDuty. You can also configure the logic app for your own services.    |

articles/azure-monitor/includes/waf-alerts-operation.md

@@ -19,6 +19,6 @@ Azure Monitor alerts offer a high degree of reliability without any design decis
 
 | Recommendation | Benefit |
 |:---|:---|
-| Configure service health alert rules| Service health alerts will send you notifications for outages, service disruptions, planned maintenance and security advisories. |
-| Configure resource health alert rules|Resource Health alerts can notify you in near real-time when these resources have a change in their health status. |
-| Avoid service limits for alert rules that produce large scale notifications|Depending on the service you use to send email or SMS notifications, if you have alert rules that would send a large amount of notifications, you may reach your service limits. Configure programmatic actions or choose an alternate notification method or provider to handle large scale notifications. See [Service limits for notifications](../alerts/action-groups.md#service-limits-for-notifications).|
+|Configure service health alert rules.| Service health alerts will send you notifications for outages, service disruptions, planned maintenance and security advisories. See [Create or edit an alert rule](../alerts/alerts-create-new-alert-rule.md).|
+|Configure resource health alert rules.|Resource Health alerts can notify you in near real-time when these resources have a change in their health status. See [Create or edit an alert rule](../alerts/alerts-create-new-alert-rule.md).|
+|Avoid service limits for alert rules that produce large scale notifications.|Depending on the service you use to send email or SMS notifications, if you have alert rules that would send a large amount of notifications, you may reach your service limits. Configure programmatic actions or choose an alternate notification method or provider to handle large scale notifications. See [Service limits for notifications](../alerts/action-groups.md#service-limits-for-notifications).|

articles/azure-monitor/includes/waf-alerts-reliability.md

@@ -21,8 +21,8 @@ ms.date: 09/04/2023
 
 | Recommendation | Benefit |
 |:---|:---|
-| Use customer managed keys if you need your own encryption key to protect data and saved queries in your workspaces.|Azure Monitor ensures that all data and saved queries are encrypted at rest using Microsoft-managed keys (MMK). If you require your own encryption key and collect enough data for a dedicated cluster, use customer-managed key for greater flexibility and key lifecycle control. If you use Microsoft Sentinel, then make sure that you're familiar with the considerations at Set up Microsoft Sentinel customer-managed key. |
-|To control permissions for log alert rules, use managed identity for your log alert rules.   | A common challenge for developers is the management of secrets, credentials, certificates, and keys used to secure communication between services. [Managed identities](../../active-directory/managed-identities-azure-resources/overview.md) eliminate the need for developers to manage these credentials. Setting a managed identity for your log alert rules gives you control and visibility into the exact permissions of your alert rule. At any time, you can view your rule’s query permissions and add or remove permissions directly from its managed identity. In addition, using a managed identity is required if your rule’s query is accessing Azure Data Explorer (ADX) or Azure Resource Graph (ARG). See [Managed identities](../alerts/alerts-create-new-alert-rule.md#managed-id).|
-|Assign the monitoring reader role for all users who don’t need configuration privileges  |Enhance security by giving users the least amount of privileges required for their role.    |
-|Where possible, use secure webhook actions    | If your alert rule contains an action group that uses webhook actions, prefer using secure webhook actions for additional authentication. See [Configure authentication for Secure webhook](../alerts/action-groups.md#configure-authentication-for-secure-webhook) |
+|Use [customer managed keys](../logs/customer-managed-keys.md) if you need your own encryption key to protect data and saved queries in your workspaces.|Azure Monitor ensures that all data and saved queries are encrypted at rest using Microsoft-managed keys (MMK). If you require your own encryption key and collect enough data for a dedicated cluster, use customer-managed keys for greater flexibility and key lifecycle control. If you use Microsoft Sentinel, then make sure that you're familiar with the considerations at Set up Microsoft Sentinel customer-managed key. |
+|To control permissions for log alert rules, use [managed identities](../../active-directory/managed-identities-azure-resources/overview.md) for your log alert rules.|A common challenge for developers is the management of secrets, credentials, certificates, and keys used to secure communication between services. Managed identities eliminate the need for developers to manage these credentials. Setting a managed identity for your log alert rules gives you control and visibility into the exact permissions of your alert rule. At any time, you can view your rule’s query permissions and add or remove permissions directly from its managed identity. In addition, using a managed identity is required if your rule’s query is accessing Azure Data Explorer (ADX) or Azure Resource Graph (ARG). See [Managed identities](../alerts/alerts-create-new-alert-rule.md#managed-id).|
+|Assign the monitoring reader role for all users who don’t need configuration privileges.|Enhance security by giving users the least amount of privileges required for their role. See [Roles, permissions, and security in Azure Monitor](../roles-permissions-security.md).|
+|Where possible, use secure webhook actions.| If your alert rule contains an action group that uses webhook actions, prefer using secure webhook actions for additional authentication. See [Configure authentication for Secure webhook](../alerts/action-groups.md#configure-authentication-for-secure-webhook) |
 |When using action groups that use private links, use Event hub actions    |When using private links in Azure, use Event hub actions for alerts. Due to the increased security for private links, event hub actions are the only actions supported by private links. |